On Jun 3, 2014, at 4:02 PM, Brian E Carpenter <[email protected]> wrote:
> On 04/06/2014 01:34, Michael Richardson wrote: >> Steven Barth <[email protected]> wrote: >>> Well maybe it was worded a bit ambiguously. The main idea behind this was >>> that an HNCP router should provide "basic connectivity" in the form of >>> DHCPv4 and DHCPv6-PD to non-HNCP-routers. 7084 routers should not do >>> anything fancy >>> and just work as legacy devices believing the homenet is their ISP. >> >> If the person connects things in the wrong order, should we be documenting >> the heuristics that would permit the HNCP router to detect this situation? > > Let's get real. Users *will* mix and match RFC7084, RFC6204 and neither-of- > the-above IPv6 routers with HNCP-capable routers. If we can't deal with > routers that are blind to HNCP in a reasonable way, those users will > be unhappy. Indeed, the first stage is for HNCP routers to discover > the existence of HNCP-blind routers. > > Brian The following draft can from the homenet design team (http://tools.ietf.org/html/draft-winters-homenet-sper-interaction-01) tries to cover the border scenarios for 6204, 7084 and other routers (SPERs) when interacting with the Homenet. It doesn't cover the case for routers inside a homenet but as Steven pointed out that can be two separate border router. ~Tim > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
