Op 16 okt. 2012, om 10:56 heeft Mark Townsley het volgende geschreven: > > On Oct 11, 2012, at 7:03 PM, Teco Boot wrote: > >> >> Op 11 okt. 2012, om 13:50 heeft Ole Trøan het volgende geschreven: >> >>>>> PS: I'd also be quite happy to see BRDP go out as an >>>>> Experimental status RFC initially, whether through >>>>> the IETF track, IRTF Routing RG, or the ISE-track. >>>>> BRDP seems very useful and useful protocols tend >>>>> to self-deploy into environments where they are useful. >>>> >>>> We also have Eric Kline's draft in similar space: >>>> draft-kline-default-perimeter-00. >>>> >>>> Both can hopefully contribute to the solution for this problem space in >>>> homenet. >>> >>> I have read the BRDP framework document, but I failed to understand how >>> BRDP solves the problem of how a border is discovered. >>> it explains well how to act when a border has been established, but I don't >>> understand how BRDP helps getting to that point. pointers? >> >> I merge the old BRDP drafts into one, to be submitted soon. Now I have to >> tweak a bit for Homenet. I do this in slack time, I hope to do some of it >> before Atlanta. > > If you would like to present this in Atlanta, it would be nice to have a > homenet targeted document for people to review. > >> >> In a MANET and in general, uplink interfaces (wired, cellular, satcom) are >> distinguished easily from MANET interfaces. In homenet and ethernet, we >> could have fixed assigned and color marked interfaces, but this is not our >> target. So here we need an additional tool. >> >> After an interface is discovered as an uplink interface, and it has received >> a prefix (e.g. DHCP-PD), then > >> BRDP propagates this information downstream in the edge network. > > In this way, BRDP sounds more like what is being done in > draft-arkko-homenet-prefix-assignment. Yes. The BRDP info could be distributed with the routing protocol. I chose for RA because it is IGP agnostic and info is delivered to hosts also. Hosts can benefit from knowledge about the multi-homed network. For MPTCP, this is essential.
I moved BRDP towards centralized prefix management with DHCP-PD, where the CPE = border router = DHCP server that manages the to be assigned /64 prefixes. This would remove the non-volatile requirement from non-CPE routers. And would provide an information base for a (web-based) management tool. The boot-homenet-brdp draft includes the mechanism for SA based routing. Can be used with arkko-homenet-prefix-assignment also. > >> This could be used for perimeter discovery also. If there is no border >> router upstream, ask for a prefix with DHCP-PD. If it has assigned such >> successfully, start acting as BRDP. Other checks would be useful >> (draft-kline-default-perimeter). > > Right, I don't see anything inconsistent here vs. what draft-kline has been > talking about.... Just one more heuristic. Added in my draft, with pointer to kline-default-perimeter. Teco > > - Mark > >> >> I'll add this in the to be submitted homenet-brdp. >> >> Teco >> >>> >>> cheers, >>> Ole >>> >>> _______________________________________________ >>> homenet mailing list >>> [email protected] >>> https://www.ietf.org/mailman/listinfo/homenet >> >> _______________________________________________ >> homenet mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/homenet > _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
