Thank you for re-opening this. I will point out that what you’re really hitting on is the known architectural deficiency of IP: how does a multi-homed network deal with multiple locators? We’ve discussed this to death previously and effectively came to the conclusion that we didn’t want to change the architecture.
What’s changed? Are we now open to changing the architecture? Routing based on source address is a band-aid fix for the specific symptoms. I think that if we are open to making changes, we should not assume that routing based on source address is the solution, and that this draft we be better served by focusing on highlighting the architectural issue and should avoid talking about solutions. Regards, Tony > On Jul 6, 2022, at 3:41 PM, Jen Linkova <[email protected]> wrote: > > Hello, > > Some of you might remember draft-ietf-rtgwg-dst-src-routing [1] which > expired a while ago. We'd like to revive the draft and get that work > done finally, so we've just submitted a replacement draft, > draft-llsyang-rtgwg-dst-src-routing. There are almost no changes to > the original draft, ex. the authors list and the name (as the original > draft expired, the new one is not a WG document but an individual > submission). > > Review, comments, ideas are highly appreciated/ > > References > [1] https://datatracker.ietf.org/doc/draft-ietf-rtgwg-dst-src-routing/ > [2] https://datatracker.ietf.org/doc/draft-llsyang-rtgwg-dst-src-routing/ > > -- > SY, Jen Linkova on behalf of draft-llsyang-rtgwg-dst-src-routing-00 authors. > > _______________________________________________ > rtgwg mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/rtgwg _______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
