Minutes IETF115: mpls: Tue 16:30
minutes-115-mpls-202211081630-00

IETF 115 MPLS WG Meeting (version 00)

Date/Time: Tuesday Session IV, November 8, 2022 16:30 - 17:30 (local)
Room: Kensington 1

Chairs: Loa Andersson/Tarek Saad/Nicolai Leymann
Secretary: Mach Chen

Slides:
https://datatracker.ietf.org/meeting/115/session/mpls/
Codimd for Notes Taking:
https://codimd.ietf.org/notes-ietf-115-mpls/
Meetecho:
http://www.meetecho.com/ietf115/mpls/
Jabber:
xmpp:mpls@jabber.ietf.org?join

1. Chairs Intro (Agenda Bashing) - 16:30
   Duration: 10 mins
   WG Chairs
   Nic and Tarek give the status update.
   No questions.

2. MPLS WG Wiki Migration - 16:40
   Duration: 10 mins
   Presenter: Tarek
   Tarek gives the introduction about MPLS WG Wiki migration and asks
   volunteers to help for migration.
   No questions.

3. A YANG Model for MPLS MSD - 16:50
   ID: https://datatracker.ietf.org/doc/draft-ietf-mpls-msd-yang-00
   Duration: 10 mins
   Presenter: Yingzhen Qu
   YingZhen presents the slides.
   Ketan: The defined MSD types today are not all MPLS specific, some
   for SRv6, how is that going to be handled?
   Yingzhen: This is MPLS specific.
   Jeff：Agree that MSD type is larger than just MPLS.
   Tarek： Do you consider to have an IANA managed MSD type YANG module,
   rather than defining types in your module?
   Yingzhen: For now, no plan to split the draft yet, but will talk to
   the SRv6 authors to find a solution.
   Jeff: It's not necessary to separate the MSD types into a different
   common YANG module.

4. Simple Two-way Active Measurement Protocol (STAMP) for MPLS Label
   Switched Paths (LSPs) - 17:00
   ID: https://datatracker.ietf.org/doc/draft-mirsky-mpls-stamp-01
   Duration: 10 mins
   Presenter: Greg Mirsky
   Greg presents.
   Loa: Read the draft, it seems to be in a pretty good way. Is it
   ready for WG adoption now?
   Greg：Yes.
   Tarek: We have published in MPLS RFC 6374 and RFC 7876 for use of
   IP/UDP for PM with MPLS without need for bootstrapping. Maybe worth
   highlighting the pros of this appoach.
   Greg: Many interests from the industry on STAMP, STAMP can not only
   implement packet loss and delay monitoring, but detect packets
   reording and duplication. In additon, it can work with TWAMP light
   that is deployed.
   Mathew: Are you going to use LSP Ping for session maintenance as
   well?
   Greg: Yes, but not very clear in this version, will clarify this in
   later versions.
   Rakesh: (follow up on offline discussion) It would be useful if you
   could add more text on STAMP reflector that is stateful.
   Greg: Yes, indeed. It will be clarified in the next revsion.

5. LSP Ping/Traceroute for Enabled In-situ OAM Capabilities - 17:10
   ID:
   https://datatracker.ietf.org/doc/draft-xiao-mpls-lsp-ping-ioam-conf-state-00

   Duration: 10 mins
   Presenter: Xiao Min
   Xiao presents.
   Tarek: It's more common that capablities are desireable to be known
   before establishment of the LSP. Your approch has dependency on LSP
   presents, you can not do the discovery before the LSP establishment.
   When you discovered the capablities, once LSP changed, you have to
   re-discover the capablities.
   Xiao: Yes. Do you know any other candidate solution?
   Tarek: IGP may be a better choice.
   Xiao: Will consider that.