> Allocations on non-nibble boundaries are possible of course.. it could > just mean about 8 different almost identical delegations in the worst > case.
Right. Which should trivially easy to automate for any organization big enough to need to worry about it. > Or are you referring to "Class-less reverse delegation" (RFC2317)? I'm > not sure if that'd help all that much. RFC 2317 describes a hack that's not particularly useful for IPv6. Even for IPv4 it's only useful in situations where there's an allocation boundary within the least significant label; the corresponding situation in the IPv6 case would imply an allocation boundary in the least significant nibble of the 128-bit IPv6 address. -------------------------------------------------------------------- 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] --------------------------------------------------------------------
