Welcome to join idr in IETF 116
", "time": "2023-03-30T00:33:22Z"}, {"author": "Jie Dong", "text": "Please collaborate on the notes: https://notes.ietf.org/notes-ietf-116-idr
", "time": "2023-03-30T00:33:44Z"}, {"author": "Ketan Talaulikar", "text": "@Natrajan Venkataraman , a suggestion. Saying there was an interop of your CT implementation with Cisco is a misrepresentation. You are right to call it an \"experiment\" in sending CT faked as SAFI 128. Would you please care to update/clarify on this to the list and wherever this is posted?
", "time": "2023-03-30T01:06:36Z"}, {"author": "Ketan Talaulikar", "text": "@Natrajan Venkataraman , it is interesting that you choose Cisco implementation for this \"experiment\" instead of some open source implementation. Could you share your reasons behind such a choice?
", "time": "2023-03-30T01:08:08Z"}, {"author": "Susan Hares", "text": "if you wish, Jie can post a revised set of slides for the meeting.
", "time": "2023-03-30T01:08:34Z"}, {"author": "Susan Hares", "text": "Jie Dong will be the shepherd for bgp-module.
", "time": "2023-03-30T01:08:53Z"}, {"author": "Aijun Wang", "text": "Hi, Susan, Jeffrey and Keyur. It seems impossible for the IDR to put forward one unified solution for transport slices instead of two proprieties solutions?
", "time": "2023-03-30T01:11:21Z"}, {"author": "Jeffrey Haas", "text": "Aijun, your question deserves a longer response than we should give in ietf meeting chat. Would you repeat it on the idr mailing list so it can be a full response?
", "time": "2023-03-30T01:18:38Z"}, {"author": "Jeffrey Haas", "text": "Unless the question is intended to be rhetorical.
", "time": "2023-03-30T01:18:53Z"}, {"author": "Aijun Wang", "text": "Will try to ask to on the list later
", "time": "2023-03-30T01:20:10Z"}, {"author": "Jeffrey Haas", "text": "Thank you, Aijun.
", "time": "2023-03-30T01:20:17Z"}, {"author": "Kaliraj Vairavakkalai", "text": "@Ketan Talaulikar, It is indeed mentioned as an \"interop experiment\" in the ietf \"hackathon\" where it was presented.
\nhttps://github.com/IETF-Hackathon/ietf115-project-presentations/blob/main/ietf-115-bgp-ct-junos-ios-xr-hackathon.pptx
pls go thru the link, and demo video - where we clearly mention this is an 'interesting experiment'.
\nThis experiment shows how the procedures of BGP-CT can be implemented easily on another implemention, one step at a time.
Sorry for the microphone issue. My question was can you use template name instead of template ID?
", "time": "2023-03-30T01:26:10Z"}, {"author": "Kaliraj Vairavakkalai", "text": "partial interop (and even End-to-end intent based forwarding) can be achieved even with a device not supporting CT as one of the BNs in the forwarding path. Ofcourse this hackathon experiemnt
\nis done with some hacks (like using SAFI-128).
That just shows the power of re-using RFC-8277 and 4364 procedures!
", "time": "2023-03-30T01:29:48Z"}, {"author": "Aijun Wang", "text": "For template ID draft, because there are many parameters in the SR policy, so there will be many combination of the possible policy template?
", "time": "2023-03-30T01:29:57Z"}, {"author": "Aijun Wang", "text": "The controller and the headend need also synchronize the contents of so many policy templates?
", "time": "2023-03-30T01:31:05Z"}, {"author": "Aijun Wang", "text": "There existing the Path ID, so what's the reason/scenario to define the segment list identifier then?
", "time": "2023-03-30T01:32:34Z"}, {"author": "Cheng Li", "text": "Path segment can be used in control plane I think
", "time": "2023-03-30T01:36:06Z"}, {"author": "Cheng Li", "text": "Btw, I think we see some drafts defining some similar terms...
", "time": "2023-03-30T01:36:39Z"}, {"author": "Liu Yao", "text": "@mengxiao we defined the sid list in draft-lp-idr-sr-path-protection you may want to check that
", "time": "2023-03-30T01:41:50Z"}, {"author": "Jeffrey Haas", "text": "https://datatracker.ietf.org/doc/html/rfc1364 - for the discussion on the current ospf / bgp presentation.
", "time": "2023-03-30T01:41:57Z"}, {"author": "Aijun Wang", "text": "It's better to add some descriptions that why the Path ID can't be used in the the mentioned scenario.
", "time": "2023-03-30T01:42:36Z"}, {"author": "Randy Bush", "text": "it's a little unusual to import from bgp into igp
", "time": "2023-03-30T01:42:58Z"}, {"author": "Jeffrey Haas", "text": "I suspect you have good wisdom to share on this, Randy.
", "time": "2023-03-30T01:43:19Z"}, {"author": "Randy Bush", "text": "no wisdom, just many bad events over decades, remember 7007 incident?
", "time": "2023-03-30T01:43:51Z"}, {"author": "Jeffrey Haas", "text": "indeed.
", "time": "2023-03-30T01:43:57Z"}, {"author": "Ketan Talaulikar", "text": "and those events still happen :-(
", "time": "2023-03-30T01:44:15Z"}, {"author": "Randy Bush", "text": "nah. i never make mistakes
", "time": "2023-03-30T01:44:29Z"}, {"author": "Jeffrey Haas", "text": "RFC 1925, \u00a72.(11)
", "time": "2023-03-30T01:44:57Z"}, {"author": "Keyur Patel", "text": "hmm redistributing/importing bgp routes in igp and then back into bgp. Fun!!
", "time": "2023-03-30T01:45:46Z"}, {"author": "Haibo Wang", "text": "The dual-egress scenario occurs from time to time.
", "time": "2023-03-30T01:46:38Z"}, {"author": "Randy Bush", "text": "the engineer who redistributes bgp into igm is the one who should be egressed
", "time": "2023-03-30T01:48:33Z"}, {"author": "Ketan Talaulikar", "text": "@Kaliraj Vairavakkalai , for your information, I have gone through the hackathon material. Interesting experiment. But calling it \"interop\" is IMO a misrepresentation. Anyway, it was only a suggestion. The choice of doing this experiment with Cisco is also interesting!
", "time": "2023-03-30T01:48:41Z"}, {"author": "Randy Bush", "text": "*igp
", "time": "2023-03-30T01:48:44Z"}, {"author": "Srihari Sangli", "text": "@Rady - I like your comment! :)
", "time": "2023-03-30T01:49:20Z"}, {"author": "Srihari Sangli", "text": "@Randy - I like your comment!
", "time": "2023-03-30T01:49:35Z"}, {"author": "Aijun Wang", "text": "if such mechanism exist, such guys can be saved.
", "time": "2023-03-30T01:51:32Z"}, {"author": "Adrian Farrel", "text": "\"older network engineer\"
", "time": "2023-03-30T01:51:34Z"}, {"author": "Susan Hares", "text": "PC language (age-enhanced engineer) (smile)
", "time": "2023-03-30T01:52:42Z"}, {"author": "Alvaro Retana", "text": "I'm sure he meant \"more experienced\". :-)
", "time": "2023-03-30T01:52:49Z"}, {"author": "Jeffrey Haas", "text": "Whomever has wisdom to share, young or old. Our \"elders\". :-)
", "time": "2023-03-30T01:53:34Z"}, {"author": "Jeffrey Haas", "text": "Or youth-deficient, if it makes you feel better.
", "time": "2023-03-30T01:54:10Z"}, {"author": "Adrian Farrel", "text": "Oh. I'm definitely older, but not sure my experience is so valuable
", "time": "2023-03-30T01:54:31Z"}, {"author": "Tony Li", "text": "Youth challenged?
", "time": "2023-03-30T01:54:34Z"}, {"author": "Jeffrey Haas", "text": "^
", "time": "2023-03-30T01:54:42Z"}, {"author": "Jeff Tantsura", "text": "This:)
", "time": "2023-03-30T01:54:45Z"}, {"author": "Changwang Lin", "text": "The path-seglist id is used to identify the forwarding plane, not the management plane.
\nIn the case that both PCE and YANG are identified by ID and name,
\nit is suggested that the seglist should also have the identification of the management plane.
\nThe application scenario is statistics reporting and configuration delivery
The seglist id chat is looking interesting. May the chairs ask that the conversation be summarized and continued on the idr mail list?
", "time": "2023-03-30T01:56:29Z"}, {"author": "Changwang Lin", "text": "OK
", "time": "2023-03-30T01:58:31Z"}, {"author": "Jeffrey Haas", "text": "Thank you, Changwang Lin.
", "time": "2023-03-30T01:58:58Z"}, {"author": "KaZhang", "text": "@Shraddha Hegde, I think template name may be ok, but template id is enought, and it is shorter and simple to use in this case.
", "time": "2023-03-30T02:01:42Z"}, {"author": "KaZhang", "text": "@Changwang Lin, there is Segment List that is configured in the headnode, and Segment List that is ceated by controller, no matter which method, there may need a segment ID, then how to process the conflict?
", "time": "2023-03-30T02:05:23Z"}, {"author": "Shraddha Hegde", "text": "@KaZhang names are more operationally friendly than the IDs. Also allowing a regular expression for names instead of exact names can be helpful
", "time": "2023-03-30T02:07:51Z"}, {"author": "Jeffrey Haas", "text": "Shraddha, Ka Zhang, may I request you summarize and continue this discussion on the mail list? This sounds like a good discussion about keeping this operationally friendly and how to best handles operations vs. on the wire encoding.
", "time": "2023-03-30T02:09:10Z"}, {"author": "Shraddha Hegde", "text": "Will do Jeff
", "time": "2023-03-30T02:09:47Z"}, {"author": "Jeffrey Haas", "text": "One consideration for names vs. ids is that text strings in the names introduce internationalization considerations. That might make some forms of vendor neutral behavior challenging, even if it's a preferable operational model.
", "time": "2023-03-30T02:10:17Z"}, {"author": "Zhen Tan", "text": "@Jeffrey Haas\uff0cHi Jeff, Is it RFC 1354 that you mentioned related to the Loop-prevention-draft?
", "time": "2023-03-30T02:10:28Z"}, {"author": "Jeffrey Haas", "text": "1364, Zhen Tan.
", "time": "2023-03-30T02:11:11Z"}, {"author": "Jeffrey Haas", "text": "https://datatracker.ietf.org/doc/html/rfc1364
", "time": "2023-03-30T02:11:28Z"}, {"author": "Zhen Tan", "text": "Thanks Jeff
", "time": "2023-03-30T02:13:22Z"}, {"author": "Jeffrey Haas", "text": "https://www.rfc-editor.org/rfc/rfc6368.html - this is the RFC for tunneling path attributes mentioned during the second to last presentation of draft-xie-idr-mpbgp-extension-4map6
", "time": "2023-03-30T02:14:35Z"}, {"author": "KaZhang", "text": "@Shraddha Hegde will think and consider this, thank you for your comments.
", "time": "2023-03-30T02:14:42Z"}, {"author": "KaZhang", "text": "@Jeffrey Haas No problem, will summrize and discuss on the mail list.
", "time": "2023-03-30T02:16:35Z"}, {"author": "Jeffrey Haas", "text": "Thank you!
", "time": "2023-03-30T02:16:50Z"}, {"author": "KaZhang", "text": "@Aijun Wang There won't be too many templates, for example, all the primary path of the headnode may use the same template, and the backup path may use another template. And controller will use netconf/yang to synchronize the contents.
", "time": "2023-03-30T02:21:57Z"}]