[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Announcing 2003::/16 during tests of "shipworm"
- Subject: Announcing 2003::/16 during tests of "shipworm"
- From: Jan Oravec <[email protected]> (Jan Oravec)
- Date: Fri, 7 Dec 2001 03:03:58 +0100
- In-reply-to: <F66A04C29AD9034A8205949AD0C9010401C0E3F3@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>; from [email protected] on Thu, Dec 06, 2001 at 05:19:38PM -0800
- References: <F66A04C29AD9034A8205949AD0C9010401C0E3F3@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
> You may have observed Microsoft announcing reachability of the prefix
> 2003::/16 over the 6Bone. The appended e-mail sent to the NGTRANS
> working group explains why. We are currently testing the "Shipworm"
> protocol, which carries IPv6 through NAT by using encapsulation over
Although I welcome your will to participate on IPv6 protocol development,
I cannot agree with announcing 2003::/16. There are active production IPv6
networks over the world already which are connected to 6bone and receiving
this non-official prefixe. It is the same as advertising 197.0.0.0/8 over
the Internet which is, according to IANA, reserved prefix.
Anyway, I don't see the point of using the Shipworm. The cleaner solution
is to configure IPv6 on the box, which provide NAT for the private network.
Best Regards,
Jan Oravec
XS26 - 'Access to IPv6'
[email protected]