[Lsr] YANG deVELpment PrOCEss & maintenance (VELOCE): CCAMP/LSR/TEAS
[email protected] Wed, 8 Apr 2026 06:53:55 +0000
| Newsgroups | gmane.ietf.ospf,gmane.ietf.ccamp,gmane.ietf.opsawg |
|---|---|
| Message-ID | <PATP264MB6765DAB651B926DF83AF9B93885BA@PATP264MB6765.FRAP264.PROD.OUTLOOK.COM> |
--===============5615283660015749985==
Content-Language: fr-FR
Content-Type: multipart/alternative;
boundary="_000_PATP264MB6765DAB651B926DF83AF9B93885BAPATP264MB6765FRAP_"
--_000_PATP264MB6765DAB651B926DF83AF9B93885BAPATP264MB6765FRAP_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Hi CCAMP/LSR/TEAS,
As you know, there are several issues with the current operation mode for d=
eveloping YANG modules within the IETF. Also, experience with some recent b=
is doc in teas (for example) further revealed to need for a different appro=
ach to handle such maintenance effort. As an attempt to address some those=
, OPSAWG is considering a process experiment called VELOCE for developing Y=
ANG modules [1].
There is on overall sketch of the new VELOCE process, but not all details a=
re set. We still need to agree collectively on the goals of this effort (wh=
ether we are aiming for speed, quality, or enabling others with distinct sk=
ills 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 thin=
gs faster, but differently. We need to find the right balance and frame the=
se goals clearly. I don't expect we will resolve all issues with the first =
version of VELOCE, but we need to start at some point and iterate. The tool=
ing 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>.
Given the LSR/CCAMP/TEAS experience in defining/maintaining YANG modules an=
d that you are familiar with issues with developing YANG modules in RFCs, y=
our perspective and inputs are highly welcomed.
In order to have the new process right, we are looking for candidates of bi=
s 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 an=
d volunteers. I already noted that Italo/Aihua/Oscar has some ideas.
If you are interested to contribute, please send a note to OPSAWG or direct=
ly to Mahesh or myself.
Cheers,
Med
[1] https://datatracker.ietf.org/meeting/125/materials/minutes-125-opsawg-00
___________________________________________________________________________=
_________________________________
Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.
--_000_PATP264MB6765DAB651B926DF83AF9B93885BAPATP264MB6765FRAP_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Courier New";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:11.0pt;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang=3D"FR" link=3D"#467886" vlink=3D"#96607D" style=3D"word-wrap:bre=
ak-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">Hi CCAMP/LSR/TEAS,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">As you know, there are several issues with the current opera=
tion mode for developing YANG modules within the IETF. Also, experience wit=
h some recent bis doc in teas (for example) further
revealed to need for a different approach to handle such maintenance effor=
t. As an attempt to address some those, OPSAWG is considering a proce=
ss experiment called VELOCE for developing YANG modules [1].<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">There is on overall sketch of the new VELOCE process, but no=
t 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 differen=
t 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 fram=
e these goals clearly. I don’t expect we will resolve all issues with=
the first version of VELOCE, but we need to start at some point and iterat=
e. The tooling is also important here.
This is why we started by providing </span><span style=3D"font-family:&quo=
t;Courier New""><a href=3D"https://github.com/IETF-OPS-AD/I-D-with-yan=
g-template"><span lang=3D"EN-US">IETF-OPS-AD/I-D-with-yang-template: A temp=
late repository for Internet-Draft with YANG Modules
management</span></a></span><span lang=3D"EN-US" style=3D"font-family:&quo=
t;Courier New"">.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">Given the LSR/CCAMP/TEAS experience in defining/maintaining =
YANG modules and that you are familiar with issues with developing YANG mod=
ules in RFCs, your perspective and inputs are highly
welcomed.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">In order to have the new process right, we are looking for c=
andidates 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></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">If you are interested to contribute, please send a note to O=
PSAWG or directly to Mahesh or myself.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New"">[1] <a href=3D"https://datatracker.ietf.org/meeting/125/mate=
rials/minutes-125-opsawg-00">
https://datatracker.ietf.org/meeting/125/materials/minutes-125-opsawg-00</a=
> <o:p>
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:"Cour=
ier New""><o:p> </o:p></span></p>
</div>
<pre>_________________<wbr>______________________________<wbr>_____________=
_________________<wbr>______________________________<wbr>_
Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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></body>
</html>
--_000_PATP264MB6765DAB651B926DF83AF9B93885BAPATP264MB6765FRAP_--
--===============5615283660015749985==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTHNyIG1haWxp
bmcgbGlzdCAtLSBsc3JAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byBs
c3ItbGVhdmVAaWV0Zi5vcmcK
--===============5615283660015749985==--