[102288] in North American Network Operators' Group
Re: Aggregation for IPv4-compatible IPv6 address space
daemon@ATHENA.MIT.EDU (Fred Baker)
Sun Feb 3 23:33:21 2008
In-Reply-To: <709078.42135.qm@web38111.mail.mud.yahoo.com>
Cc: nanog@merit.edu
From: Fred Baker <fred@cisco.com>
Date: Mon, 4 Feb 2008 06:18:54 +0200
To: snort bsd <snortbsd@yahoo.com.au>
Errors-To: owner-nanog@merit.edu
in the most recent architecture, rfc 4291, that was deprecated. The
exact statement is
2.5.5.1. IPv4-Compatible IPv6 Address
The "IPv4-Compatible IPv6 address" was defined to assist in the IPv6
transition. The format of the "IPv4-Compatible IPv6 address" is as
follows:
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|0000| IPv4 address |
+--------------------------------------+----+---------------------+
Note: The IPv4 address used in the "IPv4-Compatible IPv6 address"
must be a globally-unique IPv4 unicast address.
The "IPv4-Compatible IPv6 address" is now deprecated because the
current IPv6 transition mechanisms no longer use these addresses.
New or updated implementations are not required to support this
address type.
I should think you are within bounds to not announce it at all.
On Feb 4, 2008, at 6:09 AM, snort bsd wrote:
>
> Hi all:
>
> With IPv4-compatible IPv6 address space, could I aggregate the
> address space?
>
> say 192.168.0.0/16 become ::192.168/112? or It must be converted to
> native IPv6 address space?
>
> Just wondering,
>
>
>
>
> Get the name you always wanted with the new y7mail email
> address.
> www.yahoo7.com.au/y7mail
>
>
