RE: Persistent loops when mixing rtgwg-enterprise-pa-multihoming and rtgwg-dst-src-routing

David, It seems to me that the example that creates a routing loop depends on having two routes where one non-default source prefix of one route contains the source prefix of the other route Specifically, S=2001:db8::/32 contains S=2001:db8:::/48. I think that we can resolve the

Re: Persistent loops when mixing rtgwg-enterprise-pa-multihoming and rtgwg-dst-src-routing

Matthieu, I believe the tables could be similarly collapsed giving source address higher precedence than destination address. Do you disagree? Thanks, Acee On 7/26/17, 9:05 AM, "Matthieu Boutier" wrote: >Hi, > >David, you're right, and as you remark, the draft says: > >2.5:

Re: Persistent loops when mixing rtgwg-enterprise-pa-multihoming and rtgwg-dst-src-routing

Hi, David, you're right, and as you remark, the draft says: 2.5: « It is also useful to note that the prefixes assigned to the site by different ISPs will not overlap. » This hypothesis breaks your example. But, as you, I think that we should not rely on such hypothesis: it seems