Correction on technical note--bad RFC reference

[Howard C. Berkowitz]

When you don't put down the right RFC number, and you wrote it, a coffee
shortage is demonstrated.  Corrected paragraph:

There are no perfect answers to either problem, especially the second.  The
general strategy to deal with the first is to recognize virtually all
enterprises and ISPs will need periodically to renumber for an assortment
of reasons, and to accept this.  Once this is accepted, effort can be
expended to make old and expecially new networks "renumbering friendly."
Techniques for doing this have been the focus of the IETF PIER Working
Group, see http://ds.internic.net/rfc/rfc2071.txt and
http://ds.internic.net/rfc/rfc2072.txt .    The crackers of the world have
helped us in a perverse way; most firewalls can do address translation and
avoid the need to renumber many internal addresses in a provider change.