[OPSAWG]Re: Call for adoption: draft-mahesh-opsawg-veloce- yang-01 (Ends 2026-06-26)
"Daniele Ceccarelli \(dceccare\)" <dceccare=40cisco.com-Tr9gZwTxerDR74oF6e/[email protected]> Fri, 26 Jun 2026 13:11:01 +0000
| Newsgroups | gmane.ietf.opsawg,gmane.ietf.ccamp |
|---|---|
| Message-ID | <CY8PR11MB7340BF05DE11D7848209276DD4EB2@CY8PR11MB7340.namprd11.prod.outlook.com> |
--===============8637293331662568462== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_CY8PR11MB7340BF05DE11D7848209276DD4EB2CY8PR11MB7340namp_" --_000_CY8PR11MB7340BF05DE11D7848209276DD4EB2CY8PR11MB7340namp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Thanks for extending the call for adoption Joe. I strongly support the adoption of this document. We've been going through = many BIS drafts in CCAMP just to update yang models, and the process has of= ten been slow and painful. I expect this to happen again in IVY. VELOCE aim= s to solve this problem. Thanks Daniele ________________________________ From: Joe Clarke (jclarke) <jclarke=3D40cisco.com-Tr9gZwTxerDR74oF6e/[email protected]> Sent: Wednesday, June 24, 2026 12:23 To: opsawg <[email protected]>; [email protected] <[email protected]>; [email protected]= <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]= g> Subject: [Ivy] FW: Call for adoption: draft-mahesh-opsawg-veloce-yang-01 (E= nds 2026-06-26) On Italo=92s suggestion, I=92m forwarding this CfA for VELOCE to other, YAN= G-friendly WGs as they might be interested in the experiment itself. We=92= re also extending the CfA one more week to July 3, 2026. Members of TEAS, CCAMP, IVY, and NMOP, please respond to opsawg@ with any c= omments. Joe and Beno=EEt From: Joe Clarke via Datatracker <[email protected]> Date: Friday, June 12, 2026 at 09:10 To: [email protected] <[email protected]>; [email protected] <opsawg-chair= [email protected]>; [email protected] <draft-mahesh-opsawg-= [email protected]> Subject: Call for adoption: draft-mahesh-opsawg-veloce-yang-01 (Ends 2026-0= 6-26) This message starts a two week WG Call for Adoption of: draft-mahesh-opsawg-veloce-yang-01 This Working Group Call for Adoption ends on 2026-06-26 Abstract: This document describes a YANG deVELpment PrOCEss and maintenance (VELOCE) that is more suitable for the development of YANG modules or YANG modules update within the IETF. Discussion Venues This note is to be removed before publishing as an RFC. Source for this draft and an issue tracker can be found at https://github.com/mjethanandani/veloce. Please reply to this message and indicate whether or not you support adopti= on of this Internet-Draft by the opsawg WG. Comments to explain your preferenc= e are greatly appreciated. Please reply to all recipients of this message and include this message in your response. Authors, and WG participants in general, are reminded of the Intellectual Property Rights (IPR) disclosure obligations described in BCP 79 [2]. Appropriate IPR disclosures required for full conformance with the provisio= ns of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. Sanctions available for application to violators of IETF IPR Policy can be found at [3]. To date, the authors have explicitly said there is no IPR related to this d= raft. Thank you. [1] https://datatracker.ietf.org/doc/bcp78/ [2] https://datatracker.ietf.org/doc/bcp79/ [3] https://datatracker.ietf.org/doc/rfc6701/ The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-mahesh-opsawg-veloce-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-mahesh-opsawg-veloce-yang-01.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=3Ddraft-mahesh-opsawg-veloce-yang= -01 --_000_CY8PR11MB7340BF05DE11D7848209276DD4EB2CY8PR11MB7340namp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> <style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo= ttom:0;} </style> </head> <body dir=3D"ltr"> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c= olor: rgb(0, 0, 0);"> Thanks for extending the call for adoption Joe.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c= olor: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c= olor: rgb(0, 0, 0);"> I strongly support the adoption of this document. We've been going through = many BIS drafts in CCAMP just to update yang models, and the process has of= ten been slow and painful. I expect this to happen again in IVY. VELOCE aim= s to solve this problem.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c= olor: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c= olor: rgb(0, 0, 0);"> Thanks</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c= olor: rgb(0, 0, 0);"> Daniele </div> <div id=3D"appendonsend"></div> <div><br> </div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> <br> </div> <hr style=3D"display: inline-block; width: 98%;"> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> <b>From:</b> Joe Clarke (jclarke) <[email protected]= .org><br> <b>Sent:</b> Wednesday, June 24, 2026 12:23<br> <b>To:</b> opsawg <[email protected]>; [email protected] <teas@ietf= .org>; [email protected] <[email protected]>; [email protected] <ivy@ietf.= org>; [email protected] <[email protected]><br> <b>Subject:</b> [Ivy] FW: Call for adoption: draft-mahesh-opsawg-veloc= e-yang-01 (Ends 2026-06-26) </div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> On Italo=92s suggestion, I=92m forwarding this CfA for VELOCE to other, YAN= G-friendly WGs as they might be interested in the experiment itself. = We=92re also extending the CfA one more week to July 3, 2026.</div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> Members of TEAS, CCAMP, IVY, and NMOP, please respond to opsawg@ with any c= omments.</div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> Joe and Beno=EEt</div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div id=3D"x_mail-editor-reference-message-container"> <div style=3D"padding: 3pt 0in 0in; border-top: 1pt solid rgb(181, 196, 223= );"> <div style=3D"text-align: left; font-family: Aptos; font-size: 12pt; color:= black;"> <b>From: </b>Joe Clarke via Datatracker <[email protected]><br> <b>Date: </b>Friday, June 12, 2026 at 09:10<br> <b>To: </b>[email protected] <[email protected]>; [email protected] = <[email protected]>; [email protected] &l= t;[email protected]><br> <b>Subject: </b>Call for adoption: draft-mahesh-opsawg-veloce-yang-01 (Ends= 2026-06-26)<br> <br> </div> </div> <div style=3D"font-size: 11pt;">This message starts a two week WG Call for = Adoption of:<br> draft-mahesh-opsawg-veloce-yang-01<br> <br> This Working Group Call for Adoption ends on 2026-06-26<br> <br> Abstract:<br> This document describes a YANG deVELpment PrOCEss and maintena= nce<br> (VELOCE) that is more suitable for the development of YANG mod= ules or<br> YANG modules update within the IETF.<br> <br> Discussion Venues<br> <br> This note is to be removed before publishing as an RFC.<br> <br> Source for this draft and an issue tracker can be found at<br> <a href=3D"https://github.com/mjethanandani/veloce" id=3D"OWA8= 0387248-e175-419c-11d6-cdb7f9e4d3f3" class=3D"OWAAutoLink" data-auth=3D"Not= Applicable" data-outlook-id=3D"7543423d-a881-4360-b556-a52805323e41"> https://github.com/mjethanandani/veloce</a>.<br> <br> Please reply to this message and indicate whether or not you support adopti= on<br> of this Internet-Draft by the opsawg WG. Comments to explain your preferenc= e<br> are greatly appreciated. Please reply to all recipients of this message and= <br> include this message in your response.<br> <br> Authors, and WG participants in general, are reminded of the Intellectual<b= r> Property Rights (IPR) disclosure obligations described in BCP 79 [2].<br> Appropriate IPR disclosures required for full conformance with the provisio= ns<br> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.<br> Sanctions available for application to violators of IETF IPR Policy can be<= br> found at [3].<br> <br> To date, the authors have explicitly said there is no IPR related to this d= raft.<br> <br> Thank you.<br> [1] <a href=3D"https://datatracker.ietf.org/doc/bcp78/" id=3D"OWAb7932568-1= 577-991b-cf23-c95463693603" class=3D"OWAAutoLink" data-auth=3D"NotApplicabl= e" data-outlook-id=3D"2b9ced15-cc17-4ac4-bfa8-5b91b622e0af"> https://datatracker.ietf.org/doc/bcp78/</a><br> [2] <a href=3D"https://datatracker.ietf.org/doc/bcp79/" id=3D"OWA5a995a1b-8= fa7-7510-cd6b-69aa36cf7906" class=3D"OWAAutoLink" data-auth=3D"NotApplicabl= e" data-outlook-id=3D"5ece4b38-4413-421a-8453-8605fb0e488c"> https://datatracker.ietf.org/doc/bcp79/</a><br> [3] <a href=3D"https://datatracker.ietf.org/doc/rfc6701/" id=3D"OWA331d5e5b= -9b94-cf4d-adde-1fd247484f91" class=3D"OWAAutoLink" data-auth=3D"NotApplica= ble" data-outlook-id=3D"8c0805b6-cfe3-4534-a7cf-717ce6fdb386"> https://datatracker.ietf.org/doc/rfc6701/</a><br> <br> The IETF datatracker status page for this Internet-Draft is:<br> <a href=3D"https://datatracker.ietf.org/doc/draft-mahesh-opsawg-veloce-yang= /" id=3D"OWA27bc8000-2835-f3bd-d64c-1fc749c79c5a" class=3D"OWAAutoLink" dat= a-auth=3D"NotApplicable" data-outlook-id=3D"44607db7-c2ea-4d71-9820-b6781e8= 38f32">https://datatracker.ietf.org/doc/draft-mahesh-opsawg-veloce-yang/</a= ><br> <br> There is also an HTML version available at:<br> <a href=3D"https://www.ietf.org/archive/id/draft-mahesh-opsawg-veloce-yang-= 01.html" id=3D"OWAb88af476-b7f1-593a-2663-0de3d912880e" class=3D"OWAAutoLin= k" data-auth=3D"NotApplicable" data-outlook-id=3D"dda1ae8d-9b27-44f0-ab8f-2= 00a534e6aa7">https://www.ietf.org/archive/id/draft-mahesh-opsawg-veloce-yan= g-01.html</a><br> <br> A diff from the previous version is available at:<br> <a href=3D"https://author-tools.ietf.org/iddiff?url2=3Ddraft-mahesh-opsawg-= veloce-yang-01" id=3D"OWA3d4c675e-c0ce-9a87-288b-6852399beb72" class=3D"OWA= AutoLink" data-auth=3D"NotApplicable" data-outlook-id=3D"949ce069-d40c-4d79= -b804-730da447b507">https://author-tools.ietf.org/iddiff?url2=3Ddraft-mahes= h-opsawg-veloce-yang-01</a></div> </div> </body> </html> --_000_CY8PR11MB7340BF05DE11D7848209276DD4EB2CY8PR11MB7340namp_-- --===============8637293331662568462== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KT1BTQVdHIG1h aWxpbmcgbGlzdCAtLSBvcHNhd2dAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFp bCB0byBvcHNhd2ctbGVhdmVAaWV0Zi5vcmcK --===============8637293331662568462==--