On January 8, 2019 at 9:33:49 AM, [email protected] ( [email protected]) wrote:
Bruno: Hi! .... But I’m wondering why error handling is that specific to BGP-LS. It is just in this thread... Why is that point not been raised on, let’s say, draft-ietf-ospf-ospfv3-segment-routing-extensions which is currently under IESG review? I can see that the specific are (a bit) different, but the big picture seems the same: the information is incomplete, how do we handle this? [AD Note: draft-ietf-ospf-ospfv3-segment-routing-extensions is pending a new revision to clear an outstanding DISCUSS. If you (or anyone) has specific issues about this document, please let me know as I’m ready to approve the publication.] I didn’t specifically raise the question of error handling for BGP-LS with SR against the current document I’m reviewing (draft-ietf-idr-bgp-ls-segment-routing-ext) because I don’t think the solution explicitly belongs there…so I started the discussion on the idr/spring lists. If there are issues with the OSPFv3 transport then the solution probably doesn’t belong in the extensions draft. [This part of the discussion belongs on a different list…] I think that the link state protocols have different characteristics (than BGP-LS) when it comes to try to ensure common information between the nodes: reliability at the LSA/LSP level, db synchronization, etc.. That difference brought me to not bring up the question of incomplete information when I was reviewing the SR extension drafts. I may of course be missing an important piece. If this point needs to be discussed, we should move to lsr. Then, I’m not sure that the problem is specific/limited to SR/SID information. Right. I think it’s easier to discuss specific problems first and then generalize…than start with the general problem. That is one of the reasons for this thread. In the specific case of BGP-LS, rfc7752 makes assumptions about about the nature of the information, which I think are broken with SR…. I think there’s an SR-specific issue that needs to be addressed somewhere. As you mentioned before, other applications, like lsvr, could have the same issues. Thanks! Alvaro.
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
