Re: [Autoconf] Using DHCPv6 without link-local? Support only EUI-64 interfaces?

Le 30/07/2010 13:57, Teco Boot a écrit :
> RFC3315: ...     The client MUST use a link-local address assigned
> to the interface for which it is requesting configuration information
> as the source address in the header of the IP datagram.
>
> Question: can we get around a MUST in a standards track RFC? I don't
> think so.

I think it wouldn't be good to get around that MUST.

I was thinking about the same thing as you say: if RFC5889 forbids link
local addresses and new Charter wants DHCP then how could both work?

Maybe RFC5889 just discourages the AUTOCONF mechanism from configuring
link-local addresses.  I.e. let DHCP configure global addresses, even
though during the initial DHCP exchanges the link-local addresses are used.

(wondering...)

> The to be posted proposed text for to be RFC5889 would say that if
> link-locals are used, there are potential problems when using other
> than modified EUI-64 IIDs, and therefore must be based on modified
> EUI-64 IIDs.

I wouldn't go that far with requiring modified EUI-64 IIDs - why do you
think rfc5889 requires use of modified IIDs?

Let's see first what is the recommendation of RFC5889-to-be with respect
to link-local addresses, and following the WG meeting discussion.

> Second question, on first item in charter: do we limit ourself to
> MANET routers that has modified EUI-64 link-locals? I think: better
> think twice.

I am trying to see where the modified EUI64 ideas come from, I don't see
currently...

Alex

>
> Opinions?
>
> Teco.
>
>
> _______________________________________________ Autoconf mailing list
> Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf
>