I think this is vitally necessary and ready to go to the IESG.

If proof be needed, I heard yesterday something that I found extraordinary
until I thought about it. It seems that major companies considering
selling a division are now routinely renumbering the entire division into
Net 10 prior to the sale, so that it can be snipped off from the
corporate network in a few seconds, and NATted onto the purchaser's
network just as quickly.

(Please don't shoot the messenger - this is reality, to be dealt with.)

We need to offer a similar ability in IPv6 without creating ambiguous 
addresses and requiring NATs as a result.

   Brian

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Brian E Carpenter 
Distinguished Engineer, Internet Standards & Technology, IBM 

*** I will be on vacation February 3-25, 2004 ***

Brian Haberman wrote:
> 
> All,
>       This is the start of an IPv6 working group last call on:
> 
> >         Title           : Unique Local IPv6 Unicast Addresses
> >         Author(s)       : R. Hinden, B. Haberman
> >         Filename        : draft-ietf-ipv6-unique-local-addr-02.txt
> >         Pages           : 16
> >         Date            : 2004-1-21
> 
> This Last Call will end on Feb 2, 2004.  This document is being
> submitted as a Proposed Standard.  This last call is to verify
> consensus on the text changes made in response to the previous
> last call.  Substantive comments should be directed to the mailing
> list and editorial comments to the authors.
> 
> Regards,
> Brian & Bob
> IPv6 WG co-chairs
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [EMAIL PROTECTED]
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to