1. Introduction

   Some vendors of consumer electronics and network gear have
   unfortunately chosen to embed, or "hard-code", globally-routable
   Internet Protocol addresses within their products' firmware.  These
   embedded IP addresses are typically individual server IP addresses or
   IP subnet prefixes.  Thus, they are sometimes used as service
   identifiers, to which unsolicted requests are directed, or as subnet
   identifiers, specifying sets of Internet addresses that the given
   product somehow treats specially.

   One recent example was the embedding of the globally-routable IP
   address of a Network Time Protocol server in the firmware of hundreds
   of thousands of Internet hosts that are now in operation worldwide.
   The hosts are primarily, but are not necessarily, limited to low-cost
   routers and middleboxes for personal or residential use.  In another
   case, IP address prefixes that had once been reserved by the Internet
   Assigned Numbers Authority (IANA) were embedded in a router product
   so that it can automatically discard packets that appear to have
   invalid source IP addresses.

   Such "hard-coding" of globally-routable IP addresses as identifiers
   within the host's firmware presents significant problems to the
   operation of the Internet and to the management of its address space.

   Ostensibly, this practice arose as an attempt to simplify IP host
   configuration by pre-loading hosts with IP addresses.  Products that
   rely on such embedded IP addresses initially may appear to be
   convenient to the product's designer and to its operator or user, but
   this dubious benefit comes at the expense of others in the Internet
   community.

   This document denounces the practice of embedding references to
   unique, globally-routable IP addresses in Internet hosts, describes
   some of the resulting problems, and considers selected alternatives.
   It also reminds the Internet community of the ephemeral nature of
   unique, globally-routable IP addresses; the assignment and use of IP
   addresses as identifiers is temporary and therefore should not be
   used in fixed configurations.