[Lsr] Re: YANG deVELpment PrOCEss & maintenance (VELOCE ): CCAMP/LSR/TEAS
Mahesh Jethanandani <[email protected]> Wed, 8 Apr 2026 10:53:25 -0700
| Newsgroups | gmane.ietf.ospf,gmane.ietf.ccamp,gmane.ietf.opsawg |
|---|---|
| Message-ID | <[email protected]> |
--===============4438540443029295658== Content-Type: multipart/alternative; boundary="Apple-Mail=_A5778D44-477D-4B34-BE20-479FE1694C6F" --Apple-Mail=_A5778D44-477D-4B34-BE20-479FE1694C6F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 In addition to what Med has already mentioned, here are a couple of = things to watch out for. - An update to the currently published draft on VELOCE - = https://datatracker.ietf.org/doc/draft-mahesh-opsawg-veloce-yang/. The = update will take into consideration the discussion on the = [email protected] mailing list as well as the discussion in IETF 125. If = you have comments, start a new thread on the opsawg mailing list to = discuss the draft or open a issue or PR at = https://github.com/mjethanandani/veloce - A meeting will be set up to meet regularly to discuss the = process-level issues as they relate to VELOCE. Thanks. > On Apr 7, 2026, at 11:53=E2=80=AFPM, [email protected] = wrote: >=20 > Hi CCAMP/LSR/TEAS, > =20 > As you know, there are several issues with the current operation mode = for developing YANG modules within the IETF. Also, experience with some = recent bis doc in teas (for example) further revealed to need for a = different approach to handle such maintenance effort. As an attempt to = address some those, OPSAWG is considering a process experiment called = VELOCE for developing YANG modules [1]. > =20 > There is on overall sketch of the new VELOCE process, but not all = details are set. We still need to agree collectively on the goals of = this effort (whether we are aiming for speed, quality, or enabling = others with distinct skills to contribute). There are different = perspectives from those who write the specifications vs those who code = or review code, so we should consider a range of criteria. The = experiment may not be necessarily about doing things faster, but = differently. We need to find the right balance and frame these goals = clearly. I don=E2=80=99t expect we will resolve all issues with the = first version of VELOCE, but we need to start at some point and iterate. = The tooling is also important here. This is why we started by providing = IETF-OPS-AD/I-D-with-yang-template: A template repository for = Internet-Draft with YANG Modules management = <https://github.com/IETF-OPS-AD/I-D-with-yang-template>. > =20 > Given the LSR/CCAMP/TEAS experience in defining/maintaining YANG = modules and that you are familiar with issues with developing YANG = modules in RFCs, your perspective and inputs are highly welcomed. > =20 > In order to have the new process right, we are looking for candidates = of bis documents but also completely new modules who are willing to = exercise the new process and help adjust it as needed. Hence, this call = for interest and volunteers. I already noted that Italo/Aihua/Oscar has = some ideas. > =20 > If you are interested to contribute, please send a note to OPSAWG or = directly to Mahesh or myself. > =20 > Cheers, > Med > =20 > [1] = https://datatracker.ietf.org/meeting/125/materials/minutes-125-opsawg-00 > =20 > = __________________________________________________________________________= __________________________________ > 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. >=20 > 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. Mahesh Jethanandani [email protected] --Apple-Mail=_A5778D44-477D-4B34-BE20-479FE1694C6F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"content-type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;">In addition to = what Med has already mentioned, here are a couple of things to watch out = for.<div><br></div><div>- An update to the currently published draft on = VELOCE - <a = href=3D"https://datatracker.ietf.org/doc/draft-mahesh-opsawg-veloce-yang/"= >https://datatracker.ietf.org/doc/draft-mahesh-opsawg-veloce-yang/</a>. = The update will take into consideration the discussion on the = [email protected] mailing list as well as the discussion in IETF 125. If = you have comments, start a new thread on the opsawg mailing list to = discuss the draft or open a issue or PR at <a = href=3D"https://github.com/mjethanandani/veloce">https://github.com/mjetha= nandani/veloce</a></div><div>- A meeting will be set up to meet = regularly to discuss the process-level issues as they relate to = VELOCE.</div><div><br></div><div>Thanks.<br = id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote = type=3D"cite"><div>On Apr 7, 2026, at 11:53=E2=80=AFPM, = [email protected] wrote:</div><br = class=3D"Apple-interchange-newline"><div><meta charset=3D"UTF-8"><div = class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, = 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; = font-variant-caps: normal; font-weight: 400; letter-spacing: normal; = text-align: start; text-indent: 0px; text-transform: none; white-space: = normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = text-decoration: none;"><div style=3D"margin: 0cm; font-size: 11pt; = font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier New";">Hi = CCAMP/LSR/TEAS,<o:p></o:p></span></div><div style=3D"margin: 0cm; = font-size: 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier = New";"><o:p> </o:p></span></div><div style=3D"margin: 0cm; = font-size: 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier New";">As you know, there are = several issues with the current operation mode for developing YANG = modules within the IETF. Also, experience with some recent bis doc in = teas (for example) further revealed to need for a different approach to = handle such maintenance effort. As an attempt to address some = those, OPSAWG is considering a process experiment called VELOCE for = developing YANG modules [1].<o:p></o:p></span></div><div style=3D"margin: = 0cm; font-size: 11pt; font-family: Aptos, sans-serif;"><span = lang=3D"EN-US" style=3D"font-family: "Courier = New";"><o:p> </o:p></span></div><div style=3D"margin: 0cm; = font-size: 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier New";">There is on overall = sketch of the new VELOCE process, but not all details are set. We still = need to agree collectively on the goals of this effort (whether we are = aiming for speed, quality, or enabling others with distinct skills to = contribute). There are different perspectives from those who write the = specifications vs those who code or review code, so we should consider a = range of criteria. The experiment may not be necessarily about doing = things faster, but differently. We need to find the right balance and = frame these goals clearly. I don=E2=80=99t expect we will resolve all = issues with the first version of VELOCE, but we need to start at some = point and iterate. The tooling is also important here. This is why we = started by providing<span = class=3D"Apple-converted-space"> </span></span><span = style=3D"font-family: "Courier New";"><a = href=3D"https://github.com/IETF-OPS-AD/I-D-with-yang-template" = style=3D"color: rgb(70, 120, 134); text-decoration: underline;"><span = lang=3D"EN-US">IETF-OPS-AD/I-D-with-yang-template: A template repository = for Internet-Draft with YANG Modules management</span></a></span><span = lang=3D"EN-US" style=3D"font-family: "Courier = New";">.<o:p></o:p></span></div><div style=3D"margin: 0cm; = font-size: 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier = New";"><o:p> </o:p></span></div><div style=3D"margin: 0cm; = font-size: 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier New";">Given the LSR/CCAMP/TEAS = experience in defining/maintaining YANG modules and that you are = familiar with issues with developing YANG modules in RFCs, your = perspective and inputs are highly welcomed.<o:p></o:p></span></div><div = style=3D"margin: 0cm; font-size: 11pt; font-family: Aptos, = sans-serif;"><span lang=3D"EN-US" style=3D"font-family: "Courier = New";"><o:p> </o:p></span></div><div style=3D"margin: 0cm; = font-size: 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier New";">In order to have the new = process right, we are looking for candidates of bis documents but also = completely new modules who are willing to exercise the new process and = help adjust it as needed. Hence, this call for interest and volunteers. = I already noted that Italo/Aihua/Oscar has some = ideas.<o:p></o:p></span></div><div style=3D"margin: 0cm; font-size: = 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier = New";"><o:p> </o:p></span></div><div style=3D"margin: 0cm; = font-size: 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier New";">If you are interested to = contribute, please send a note to OPSAWG or directly to Mahesh or = myself.<o:p></o:p></span></div><div style=3D"margin: 0cm; font-size: = 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier = New";"><o:p> </o:p></span></div><div style=3D"margin: 0cm; = font-size: 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier = New";">Cheers,<o:p></o:p></span></div><div style=3D"margin: 0cm; = font-size: 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier = New";">Med<o:p></o:p></span></div><div style=3D"margin: 0cm; = font-size: 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier = New";"><o:p> </o:p></span></div><div style=3D"margin: 0cm; = font-size: 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier New";">[1]<span = class=3D"Apple-converted-space"> </span><a = href=3D"https://datatracker.ietf.org/meeting/125/materials/minutes-125-ops= awg-00" style=3D"color: rgb(70, 120, 134); text-decoration: = underline;">https://datatracker.ietf.org/meeting/125/materials/minutes-125= -opsawg-00</a><o:p></o:p></span></div><div style=3D"margin: 0cm; = font-size: 11pt; font-family: Aptos, sans-serif;"><span lang=3D"EN-US" = style=3D"font-family: "Courier = New";"><o:p> </o:p></span></div></div><pre style=3D"caret-color:= rgb(0, 0, 0); font-size: 12px; font-style: normal; font-variant-caps: = normal; font-weight: 400; letter-spacing: normal; text-align: start; = text-indent: 0px; text-transform: none; word-spacing: 0px; = -webkit-text-stroke-width: 0px; text-decoration: = none;">_________________<wbr>______________________________<wbr>__________= ____________________<wbr>______________________________<wbr>_ 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.</pre></div></blockquote></div><br><div> <div dir=3D"auto" style=3D"font-family: Helvetica; font-size: 12px; = font-style: normal; font-variant-caps: normal; font-weight: normal; = letter-spacing: normal; orphans: auto; text-align: start; text-indent: = 0px; text-transform: none; white-space: normal; widows: auto; = word-spacing: 0px; -webkit-text-size-adjust: auto; = -webkit-text-stroke-width: 0px; text-decoration: none; caret-color: = rgb(0, 0, 0); color: rgb(0, 0, 0); word-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;"><div = dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); = letter-spacing: normal; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; word-spacing: 0px; = -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: = break-word; -webkit-nbsp-mode: space; line-break: = after-white-space;"><div style=3D"color: rgb(0, 0, 0); letter-spacing: = normal; text-align: start; text-indent: 0px; text-transform: none; = white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = word-wrap: break-word; -webkit-nbsp-mode: space; line-break: = after-white-space;"><div><br class=3D"Apple-interchange-newline">Mahesh = Jethanandani</div><div>[email protected]</div><div><br></div></div><= br class=3D"Apple-interchange-newline"></div><br = class=3D"Apple-interchange-newline"></div><br = class=3D"Apple-interchange-newline" style=3D"caret-color: rgb(0, 0, 0); = color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; = font-style: normal; font-variant-caps: normal; font-weight: normal; = letter-spacing: normal; orphans: auto; text-align: start; text-indent: = 0px; text-transform: none; white-space: normal; widows: auto; = word-spacing: 0px; -webkit-text-size-adjust: auto; = -webkit-text-stroke-width: 0px; text-decoration: none;"><br = class=3D"Apple-interchange-newline"> </div> <br></div></body></html>= --Apple-Mail=_A5778D44-477D-4B34-BE20-479FE1694C6F-- --===============4438540443029295658== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTHNyIG1haWxp bmcgbGlzdCAtLSBsc3JAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byBs c3ItbGVhdmVAaWV0Zi5vcmcK --===============4438540443029295658==--