[mpls] Calling authors of draft-ietf-mpls-mldp-yang

[Adrian Farrel <[e-mail]>]

Hi,

 

I know that several of you have changed email addresses since this draft was posted, so I am hoping this reaches you via the mailing list.

 

But others of you are listed as authors and should be seeing these emails.

 

Contributors: please feel free to step in.

 

Thanks,

Adrian

 

From: James Guichard <[e-mail]> 
Sent: 21 September 2026 14:12
To: [e-mail]; [e-mail]
Cc: [e-mail]; Ran Chen <[e-mail]>; mpls-chairs <[e-mail]>
Subject: Re: [Last-Call] draft-ietf-mpls-mldp-yang-16 ietf last call Opsdir review

 

Dear authors,

 

Again, please provide an update for this document and responses to the various DISCUSS points raided during IESG evaluation. Please also provide an update on the status so that this document can be moved forward.

 

Thanks!

 

Jim

 

From: James Guichard <[e-mail] <mailto:[e-mail]> >
Date: Monday, July 27, 2026 at 8:41 AM
To: [e-mail] <mailto:[e-mail]>  <[e-mail] <mailto:[e-mail]> >; [e-mail] <mailto:[e-mail]>  <[e-mail] <mailto:[e-mail]> >
Cc: [e-mail] <mailto:[e-mail]>  <[e-mail] <mailto:[e-mail]> >; Ran Chen <[e-mail] <mailto:[e-mail]> >; mpls-chairs <[e-mail] <mailto:[e-mail]> >
Subject: Re: [Last-Call] draft-ietf-mpls-mldp-yang-16 ietf last call Opsdir review

Dear authors,

 

Please provide an update for this and also for the other DISCUSS ballots on this document.

 

Thanks!

 

Jim

 

From: [e-mail] <mailto:[e-mail]>  <[e-mail] <mailto:[e-mail]> >
Date: Wednesday, June 24, 2026 at 5:44 AM
To: [e-mail] <mailto:[e-mail]>  <[e-mail] <mailto:[e-mail]> >
Cc: [e-mail] <mailto:[e-mail]>  <[e-mail] <mailto:[e-mail]> >; Ran Chen <[e-mail] <mailto:[e-mail]> >
Subject: RE: [Last-Call] draft-ietf-mpls-mldp-yang-16 ietf last call Opsdir review

Hi,

Unless I'm mistaken, I didn't see any follow-up to this review.

Can you please share an update about your plans?

Thank you

Cheers,
Med

> -----Message d'origine-----
> De : Ran Chen via Datatracker <[e-mail] <mailto:[e-mail]> >
> Envoyé : mercredi 6 mai 2026 12:17
> À : [e-mail] <mailto:[e-mail]> 
> Cc : [e-mail] <mailto:[e-mail]> ; [e-mail] <mailto:[e-mail]> ;
> [e-mail] <mailto:[e-mail]> 
> Objet : [Last-Call] draft-ietf-mpls-mldp-yang-16 ietf last call
> Opsdir review
>
>
> Document: draft-ietf-mpls-mldp-yang
> Title: YANG Data Model for MPLS mLDP
> Reviewer: Ran Chen
> Review result: Has Issues
>
> Hi,
>
> I have been selected as the Operational Directorate (opsdir)
> reviewer for this Internet-Draft.
>
> The Operational Directorate reviews all operational and
> management-related Internet-Drafts to ensure alignment with
> operational best practices and that adequate operational
> considerations are covered.
>
> A complete set of _"Guidelines for Considering Operations and
> Management in IETF Specifications"_ can be found at
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffra01.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252F <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F> &data=05%7C02%7Cjames.n.guichard%40futurewei.com%7Cb21180587a454a051ad208ded1d52caf%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C639178910685294499%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=f%2BpcY%2FHd2Ny07zl1ENpHxHuLvLLMaH2u8%2B9DqODzHxY%3D&reserved=0
> datatracker.ietf.org%2Fdoc%2Fdraft-ietf-opsawg-
> rfc5706bis%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cdc74
> c29e21ef4a12af1308deab58cd08%7C90c7a20af34b40bfbc48b9253b6f5d20%7C
> 0%7C0%7C639136595052107027%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk
> iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI
> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=SrgtI7IqFItD0Gn8%2FJxLpBZe%2Fi05ehf
> OTxmNaAKNWmQ%3D&reserved=0.
>
> While these comments are primarily for the Operations and
> Management Area Directors (Ops ADs), the authors should consider
> them alongside other feedback received.
>
> - Document: draft-ietf-mpls-mldp-yang-16
>
> - Reviewer: Ran Chen
>
> - Review Date: 2026-05-06
>
> - Intended Status: Standards Track
>
> ---
>
> ## Summary
>
> Choose one:
>
> - Has Issues: I have some minor concerns about this document that
> I think should be resolved before publication.
>
> ## General Operational Comments Alignment with RFC 5706bis
>
> Provide an overview of the draft’s operational feasibility,
> readability, and alignment with RFC5706bis guidelines. Example:
>
> > This document defines a YANG model for mLDP. While the technical
> > approach is
> sound, the document lacks an "Operational Considerations" section
> as required by RFC5706bis for new protocol extensions (including
> YANG models).
>
> > The Operational Considerations section (to be added before
> Security
> Considerations) could be expanded to discuss the migration path
> from the base LDP YANG model (RFC 9070).
>
> ## Major Issues
>
>  > No major issues found.
>
> ---
>
> ## Minor Issues
>
> 1.MBB and MoFRR statistics – While the model already provides
> configuration and state (active/standby role) for MBB and MoFRR,
> it does not yet include counters for MBB switch events, last
> switch time, or MoFRR primary/backup switches. The authors may
> wish to consider adding these statistics to help operators monitor
> the health of protection mechanisms.
>
> 2.RFC 9070 already provides message‑level statistics, which are
> helpful for monitoring the general health of LDP sessions. In
> operational practice, it can also be valuable to understand, per
> LDP session, how many FECs of specific types (e.g., P2MP, MP2MP
> Upstream, MP2MP Downstream) are sent or received. Such information
> could be useful for capacity planning and detecting anomalous
> trends. The current mLDP model does not yet include per‑session
> FEC counters broken down by these types. If the authors consider
> adding such counters, it would offer extra benefits for capacity
> planning and anomaly detection. This is entirely at their
> discretion and is not a requirement of this review.
> ---
>
> ## Nits
>
> section 3.1
> - "Transit Birdir"->"Transit Bidir"
> - "specifc" -> "specific".
> section 6.2.1
> -"a opaque"->"an opaque"
> ---
>
> Thanks!
> Ran
>
>
> --
> last-call mailing list -- [e-mail] <mailto:[e-mail]>  To unsubscribe send
> an email to [e-mail] <mailto:[e-mail]> 
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.