I've thought about it some more this morning, and I've changed my mind: I think it's actually not a bad idea, and if done right it might even work.
> 1) pure peering > - homenet -> LLN ::/0 > - LLN -> homenet more specifics for LLN routes and cloud service prefixes Ok. What I'm still not clear about is whether you intend the LLN prefix to be announced by just one homent router, or by all of the homenet neighbours of the LLN edge router. If the former, you get non-optimal routing and brittleness. If the latter, I can see some opportunities for transient routing loops if not done carefully. (And you certainly don't want a routing loop on a link with low-power nodes.) The other issue is how the edge router picks its next hop for its default route. I don't think that you'd want to reflect the routing protocol's metric in HNCP, but you certainly need some way to avoid picking a badly connected nexthop. I see no easy solution here. -- Juliusz _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
