I can hear from the online meeting
", "time": "2024-11-05T16:30:38Z"}, {"author": "Dhruv Dhody", "text": "https://notes.ietf.org/notes-ietf-121-srv6ops
", "time": "2024-11-05T16:32:16Z"}, {"author": "Boris Khasanov", "text": "How does MEC LEaf creates SR Policy?
", "time": "2024-11-05T16:42:23Z"}, {"author": "Joel Halpern", "text": "Ths usage of a single SID to represent an entire service chain is rather at variance from the defined meanings of source route headers.
", "time": "2024-11-05T16:45:45Z"}, {"author": "Joel Halpern", "text": "Obviously, an operator can do whatever they choose inside their domain.
", "time": "2024-11-05T16:47:28Z"}, {"author": "Daniel Bernier", "text": "@boris did I answer your question ?
", "time": "2024-11-05T16:49:50Z"}, {"author": "Boris Khasanov", "text": "@Daniel, yes, thanks a lot! I like such flexibility for different options.
", "time": "2024-11-05T16:52:49Z"}, {"author": "Dhruv Dhody", "text": "Boris - please ask your question here or mailing list
", "time": "2024-11-05T17:05:26Z"}, {"author": "Boris Khasanov", "text": "@Jiangang: My question was about 1st use case, you mentioned that some old access segments still use a MPLS, does it mean that those your PEs support SRv6-MPLS Interworking (draft-agrawal-spring-srv6-mpls-interworking)?
", "time": "2024-11-05T17:08:13Z"}, {"author": "Jiangang Lu", "text": "@Chris Actually in the existing stage, we take use the fact that all dispatching services operate between substations and the dispatching center. So just upgrade the dispatching backbone network region by region.
", "time": "2024-11-05T17:15:53Z"}, {"author": "Jiangang Lu", "text": "Still thanks for reminding the document, we maybe consider this in other scenarios
", "time": "2024-11-05T17:16:23Z"}, {"author": "Daniel Bernier", "text": "@boris yes we implemented interworking-draft for MPLS interop
", "time": "2024-11-05T17:34:22Z"}, {"author": "Daniel Bernier", "text": "sorry missed your Q in the list
", "time": "2024-11-05T17:34:33Z"}]