In your previous mail you wrote:
draft-ietf-malloc-ipv6-guide-04 Section 4.2 describes this for
IPv6 multicast. The same thing could be done for anycast and/or
unicast.
=> this is exactly what I'd like to get with a little difference:
IMHO we should not reserve space (other than all zeros) and rely
on probability to avoid collisions with RFC 3041 (an alternative is
to set the group/7th bit for private/temporary addresses but this seems
to be overkilling because the issue already exists with manual IIDs).
I believe something like this should be fine:
- :: reserved for router subnet anycast
- ::1-::FFFF free for manual & lazzy numbering
- ::1:1-::1:FFFF for well known services (DNS discovery, etc)
- ::2:1-::2:FFFF for local services
- ::FDFF:FFFF:FFFF:FF80-::FDFF:FFFF:FFFF:FFFF for anycasts (RFC 2526)
Regards
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
