[132300] in North American Network Operators' Group
Re: Introducing draft-denog-v6ops-addresspartnaming
daemon@ATHENA.MIT.EDU (Joel Jaeggli)
Fri Nov 19 15:19:48 2010
Date: Fri, 19 Nov 2010 12:19:34 -0800
From: Joel Jaeggli <joelja@bogus.com>
To: Owen DeLong <owen@delong.com>
In-Reply-To: <DE1A42DB-2A5D-45F0-80F0-E620A52DE2D5@delong.com>
Cc: bmanning@vacation.karoshi.com, nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 11/19/10 10:56 AM, Owen DeLong wrote:
>> It is always two bytes. A byte is not always an octet. Some machines do
>
> It is always two OCTETS. A byte is not always an octet...
Assuming you have a v6 stack on your cdc6600 a v6 address fits in 22
bytes not 16.
>> have byte sizes other than 8 bits, although few of them are likely to have
>> IPv6 stacks, so, this may be an academic distinction at this point.
One can define that byte size for the purposes of the human reading of
addresses ipv6 as 8 bits, without getting into machine specific details.
what's important to the machine isn't the division of the address into
parts (they aren't divided in the machine representation it's just one
long row of bits) but rather where the mask falls.
>> Owen
>>
>
>
