On Tue, 30 Jun 2015, Steven Barth wrote:
Hello Mikael,
thanks for your continuous feedback.
Am 30.06.2015 um 14:41 schrieb Mikael Abrahamsson:
6.2.4 "create an on-link route"? What's an on-link route? Also, why is it a
"MAY" that it doesn't create an address for itself to this prefix? An explanation and
rationale here would be good.
6.2.6 The list of things to do there isn't clear to me. "wait for them to be
applied"? Applied where? How? Using the HCNP Prefix Assignment Algorithm? In the
RIB? It implies HNCP Prefix Assignment Algo afterwards, but this isn't clear to me.
Section 11 about the MUST for RFC7084 compliance. What parts of RFC7084 must be
implemented? MUSTs? SHOULDs?
I just pushed an update to our drafts repository which should hopefully address
your comments.
Please see https://github.com/fingon/ietf-drafts/compare/c82f52d...c9f5b57 and
let us know if you have any further issues.
Thanks, yes, that's better.
Hm, regarding section 11, requirements for HNCP routers. How is that size
hint calculated? Also, other kinds of behaviours like null-routing the
delegated PD to avoid ping-pong routing when you receive packets for
subnets currently not in use in the delegated prefix, where is that
specified?
--
Mikael Abrahamsson email: [email protected]
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
