On Feb 5, 2013, at 10:12 PM, Mark Andrews <[email protected]> wrote: > prefix: A variable-length field containing an IP address or the > prefix of an IP address. An IPv4-mapped address [RFC4291] must > be used to represent an IPv4 address as a prefix value. The > prefix should be left aligned, big-endian, and zero padded on > the right up to the next octet boundary. So the length of this > field should be between 0 and 16 bytes > > is ambigious on the encoding of 2002:1234:8734::/64 > > is it: > 40:20:02:12:34:87:34:00:00:00:00:00:00:00:00:00:00 > or > 40:20:02:12:34:87:34:00:00:00:00:00:00:00:00:00 > or > 40:20:02:12:34:87:34:00:00:00:00:00:00:00:00 > or > 40:20:02:12:34:87:34:00:00:00:00:00:00 > or > 40:20:02:12:34:87:34:00:00:00:00:00 > or > 40:20:02:12:34:87:34:00:00:00:00 > or > 40:20:02:12:34:87:34:00:00:00 > or > 40:20:02:12:34:87:34:00:00 > or > 40:20:02:12:34:87:34:00 > or > 40:20:02:12:34:87:34 > > All appear to be legal. It would be cleaner if the > floor((prefix-len+7)/8) gave the number of octets in > the prefix field.
Mark, You have me confused here. /64 defines a prefix length of 64 bits, exactly 8 octets. Octet for Octet, 20:02:12:34:87:34:00:00 is unambiguously correct and in accordance with the definition cited. Please explain where the leading 40 originates. James R. Cutler [email protected] -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
