> -----Original Message-----
(B> From: [EMAIL PROTECTED]
(B
(B[ ... ]
(B
(B> Thus, I'd now rather be more concrete on this. My latest proposal to
(B> this part is as follows:
(B>
(B> A link-local address is formed by prepending the well-known link-
(B> local prefix FE80::0/10 [RFC3513] to the interface identifier. If
(B> the interface identifier has a length of N bits, the interface
(B> identifier replaces the right-most N zero bits of the link-local
(B> prefix. If the interface identifier is more than 118 bits in
(B> length, autoconfiguration fails and manual configuration is
(B> required.
(B
(BA slight reword, because I get confused with being told N bits, and no limits on N.
(B
(B A link-local address is formed by prepending the well-known link-
(B local prefix FE80::0/10 [RFC3513] to the interface identifier. If
(B the interface identifier has a length of N bits, where N <= 118 bits,
(B the interface identifier replaces the right-most N zero bits of the
(B link-local prefix. If the interface identifier is more than 118 bits
(B in length, autoconfiguration fails and manual configuration is
(B required.
(B
(BAnother point. Any reason why autoconfiguration with DAD is not possible even if N is
(B> 118? Maybe this was already discussed.
(B
(BBert
(B
(B--------------------------------------------------------------------
(BIETF IPv6 working group mailing list
(B[EMAIL PROTECTED]
(BAdministrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
(B--------------------------------------------------------------------
