FYI, draft-qin-pppext-ipv6-addr-pref-00//FW: I-D Action:draft-huang-ipv6cp-options-00.txt

sorry that i missed the discussion,

we also think that the necessary extensions of IPv6CP should be done,
and a draft has been posted in Jan.

please refer to:
http://tools.ietf.org/html/draft-qin-pppext-ipv6-addr-pref-00

regards,

-Jacni


-----------------------------------
Thanks for the pointer. And you are right that an archive search could
have been done...

I understand your point of RS/RA and DHCPv6 being already available and
can/should be used for these configuration events on IP layer. In fact,
these are actually the way Softwire Hub and Spoke [RFC5571] works. They
are also the motivations behind this I-D: to avoid having to relying on
them over the PPP link. Bringing in other subsystems can bring
additional system complexity, as well as overhead such as DAD. While PPP
is a link layer protocol, it is also used to negotiate higher layer
protocol parameters such as address [RFC1332] and DNS server [RFC1877]
information, so I figured  that IPv6 address (instead of just the
interface ID, RFC5072), gateway information, IPv6 DNS information, even
prefix assignment are reasonable parameters to negotiate over PPP. I saw
that as a more efficient model over PPP link than RA and DHCPv6
combined.

In any case, thanks for the feedback. The point was to see if there is
interest in pursuing it further but I suppose that could have been found
out another way.

Thanks,
--
Jerry Huang, AT&T Labs, +1 630 719 4389

...

_______________________________________________
Pppext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pppext