On Mon, Oct 20, 2014 at 10:40:33PM +0200, David Lamparter wrote: > https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-routing-extra-qualifiers/?include_text=1 > https://datatracker.ietf.org/doc/draft-lamparter-rtgwg-dst-src-routing/?include_text=1
rtgwg & homenet: So, these drafts describe the general router behaviour for D/S, without heading into homenet specifics. There are a few points that might be worth going into detail: - the first draft describes adding random kinds of attributes into route lookup. That's very generic, and it didn't add significant complexity, but I don't think we're expecting to insert things in the middle? - we haven't discussed some of the boundaries to other functions. Recursive route handling is unlikely to be relevant for homenet, but might warrant feedback from rtgwg. And the situation is rather complex, the draft has an open "multiple-choices TBD" there. Interesting for both rtgwg & homenet are behaviour with uRPF filtering and multicast RP lookups. The draft says: for uRPF, flip dst & src and match both, if the system supports it. If it doesn't, match packet source against all possible route dst. (This probably needs better wording in the draft) for mcast reverse-path lookup, ignore all D/S routes. Multicast has only (group, source) available, no destination to match against the route source prefix. So, to be explicit on this, D/S routing is conceptually incompatible with multicast reverse path lookups. But that can be dealt with (cue to homenet multicast discussion here.) Hoping for feedback (including, possibly, "I don't care" or "I have no opinion"), -David P.S.: there is an unfortunate scheduling collision between homenet and rtgwg for IETF 91... please convert to mail as much as possible! _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet