Fred, > Ole Troan and Lorenzo Colitti documented their model, which is strictly > egress routing based on the OSPF AS-prefix-LSA and the assumption of > automated prefix allocation. This is not multi-topology; it in effect tags > the default route advertised as a route from an alternate universe. > > http://tools.ietf.org/html/draft-troan-homenet-sadr > "IPv6 Multihoming with Source Address Dependent Routing (SADR)", Ole > Troan, Lorenzo Colitti, 18-Feb-13
to clarify, the SADR draft: - describes what source constrained / source address dependent routing is - describes a conceptual forwarding model - gives two alternatives to how a routers forwarding table can be populated. a) implicitly via other information learn from the prefix assignment protocol b) explicitly via one of the Baker extensions to routing protocols. neither a nor b has any restriction to just the default route. more specific routes are supported too. b allows flexibility to also advertise internal (S,D) routes, and S,D routes not associated with border routers. I specifically chose single topology. just to make it clear, I think the correct solution is to add support for (S,D) routes in the routing protocol, I just don't want to sit on the fence and wait until that support is added and available. cheers, Ole _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
