Hello Ray,
Thanks for the review.
> I've just been testing this feature, which is why I asked ;)
>
> /56 was requested by hnet router to ISP router.
>
> /62 was (correctly) allocated to the 7084 router by the hnet router.
> route to /62was (correctly) advertised by the hnet router into Homenet.
>
> Is it not worth adding a couple of sentences to this draft?
>
> At the end of Section 6:
>
> Proxy: A proxy node is capable of acting on behalf of one or more
> non-participating device(s) (e.g. a downstream RFC7084 compliant router) in
> order to assign new prefixes, adopting, existing ones, making overriding
> assignments and destroying existing ones on behalf of the non-participating
> device(s). The exact mechanism to be deployed is outside the scope of this
> draft. The proxy node SHOULD ensure that any underlying topology discovery
> mechanism is stable and complete, before acting as a proxy node, to avoid
> causing any race conditions. The proxy node SHOULD also check that the
> network topology beyond the proxy node is single attached to the set of
> participating nodes.
Their actually is something about that already. Sub-delegation is one of the
purposes of the so called « Private Links »
Private Link: A Private Link is an abstract concept defined for the
sake of this document. It allows nodes to make assignments for
their private use or delegation. For instance, every DHCPv6-PD
[RFC3633] client MAY be considered as a different Private Link.
Another node, by some mean such as DHCPv6-PD, asks for prefixes. In order to
provide a prefix, the algorithm may be executed on a Private Link representing
that client node. It is true that the proxy needs to be careful when it
provides prefixes this way. Which is why the « Apply Timer » exists.
Applied (Assigned Prefix): When an Assigned Prefix is applied, it
MAY be used (e.g., for host configuration, routing protocol
configuration, prefix delegation). When not applied, it MUST NOT
be used for any other purposes than the prefix assignment
algorithm. […]
In order to help moving forward with specifications, the PA draft was purged
from any purely Homenet specific considerations (Prefix Length considerations,
Prefix Lifetimes, ULA generation, …). These considerations now belong to the
hncp document (draft-ietf-homenet-hncp-04). Particularly, Recursive Prefix
Delegation is described in Section 6.2.6 of the HNCP document.
Thanks,
- Pierre
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
