Hi Thomas, Thanks a lot for your comments on the draft, and your elaboration on the usage of Path Marking TLV!
Regarding your suggestion of adding a "ECMP" path type, well, the currently defined "0x0004 -- Primary Path" path type should do the work. In fact, the so-called "Primary Path" in this draft refers to all the ECMP paths (including the "Best path"). Of course, we can further work on the naming. Thanks for sharing the ECMP reference: raft-lapukhov-bgp-ecmp-considerations-02. May I ask the use case for your proposal of adding "the reason why it is considered ECMP" reason string? Well, it's easy for me to understand that users may wonder why a path is "non-best". Do you have any specific reason string in mind for the ECMP paths? BR, Yunan -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Friday, July 12, 2019 8:44 PM To: [email protected]; [email protected]; [email protected]; Guyunan (Yunan Gu, IP Technology Research Dept. NW) <[email protected]> Cc: [email protected] Subject: RE: [GROW] Path marking using BMP - TLVs Hi Camilo, Paulo and Yunan, Thank you very much for this exciting and very useful draft. This will make draft-ietf-grow-bmp-local-rib even more useful. On top of having access to all (not only to the best) BGP paths in BGP local RIB, thanks to this draft, we will finally understand how these BGP paths are installed in RIB/FIB. We will be able to get an network wide overview on which routers which paths have redundancy and which not. And that with ONE single query in big data. One remark I like to add to complete all the possible path types. In section 2.1 Path Type, could you add ECMP (Equal-Cost Multipath) as path type and under Section 2.2 Reason String, the reason why it is considered ECMP. For BGP Equal-Cost Multipath reasons, please refer to this current draft: https://www.ietf.org/id/draft-lapukhov-bgp-ecmp-considerations-02.txt Kind regards Thomas Graf ____________________________________________________________________________ Network Engineer Datacenter Functions Telefon +41-58-223 84 01 Mobile +41-79-728 80 12 [email protected] ____________________________________________________________________________ Swisscom (Schweiz) AG IT, Network & Infrastructure Datacenter Functions Binzring 17 8045 Zürich www.swisscom.com Postadresse: Binzring 17 8045 Zürich -----Original Message----- From: GROW <[email protected]> On Behalf Of Camilo Cardona Sent: Saturday, July 6, 2019 5:04 AM To: [email protected] [email protected] <[email protected]> Cc: [email protected] Subject: [GROW] Path marking using BMP - TLVs Hello GROW, We just submitted draft https://www.ietf.org/id/draft-cppy-grow-bmp-path-marking-tlv-00.txt. The idea of the draft is to signal the state of the path in the FIB using the mechanism described in draft-lucente-bmp-tlv-00 (https://www.ietf.org/id/draft-lucente-bmp-tlv-00.txt), which was introduced this week. Feedback is, as always, welcome. If possible, we would like to have a couple of minutes to present it in Montreal (probably better if done next to the presentation of draft-lucente-bmp-tlv-00). A good part of this document was inspired by other draft, https://tools.ietf.org/html/draft-bgp-path-marking-00, that we proposed some years ago. In that draft, similar information was signaled using communities. Back then, there were some concerns of this data potentially messing with the BGP decision process, something that should not be a problem when using BMP. Thanks, Camilo Cardona _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
