>>>>> On Thu, 2 Sep 2004 23:29:09 +0200 ,
>>>>> "Elwyn Davies" <[EMAIL PROTECTED]> said:
> In Section 5.3:
> A link-local address is formed by prepending the well-known
> link-local prefix [RFC3513] (of appropriate length) to the interface
> identifier. If the interface identifier has a length of N bits, the
> interface identifier replaces the right-most N zero bits of the
> link-local prefix. If the sum of the link-local prefix length and N
> is larger than 128,...
> Using both the phrases 'of appropriate length' and 'the link local prefix
> length' is confusing.
> The link-local prefix length is fixed in RFC 3513 - it might be clearer to
> say:
> A link-local address is formed by prepending the well-known
> link-local prefix [RFC3513] (padded to the appropriate length with zero
> bits) to the interface
> identifier. If the interface identifier has a length of N bits, the
> interface identifier replaces the right-most N zero bits of the
> link-local prefix extended to 128 bits with zero bits. If the sum of the
> link-local prefix length and N
> is larger than 128,...
Ack.
> In Section 5.5.3 (d) [not (e) as the previous message said], last para:
> If an address is formed successfully, the host adds it to the list
> of addresses assigned to the interface, initializing its preferred
> and valid lifetime values from the Prefix Information option.
> I guess it ought to be mentioned that the address also has to pass DAD
> before being added to the list of addresses:
> If an address is formed successfully and DAD shows that it is unique,
> the host adds it to the list
> of addresses assigned to the interface, initializing its preferred
> and valid lifetime values from the Prefix Information option.
I personally think this is pretty obvious, but I'm fine with the
additional note as a pre-submit comment. I'll apply the change to rev
06.
Thanks for the pre-review.
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------