Andrew,
>The other issue is cascading these setups. Currently, I am unaware of a
>deployed solution for automatically telling a gateway home router what it's
>IPv6 network is (Haberman has written a draft, however, and there may be
>others). A second issue occurs with cascading. I have built a zeroconf
>system for doing peer-peer routing, but that's different from hierarchical
>delegation. These issues are very soluble, but it's a matter of how the
>market wishes to deploy the solutions.
As has been pointed out for prefix delegation there is the requirements
document:
<draft-ietf-ipv6-prefix-delegation-requirement-03.txt>
and the DHCPv6 prefix delegation option:
<draft-ietf-dhc-dhcpv6-opt-prefix-delegation-04.txt>
Both of these are now in the IESG.
One cut at the cascading problem is:
<draft-thaler-ipv6-ndproxy-00.txt>
It would be good to get some discussion on this draft. It was intended to
meet the ND proxy part of prefix delegation, but there hasn't been very
much discussion to date.
Bob
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------