[OPSAWG]Re: Call for adoption: draft-mahesh-opsawg-veloce-yang-01 (Ends 2026-06-26)

[Qin Wu <[e-mail]>]

Hi, Joe and all:
I think v-01 is a good starting point, I support to adopt this work as a basis.
We all hope VELOCE experimental process can be successful. At the high level, w need to think about 
1. How to update published YANG model without republishing new RFC?
2. When republished new RFC is required, which part of the process can be further optimized? Template? 
3. When we move YANG data model to the github, how consensus building already defined in IETF Working Group Guidelines and Procedures (RFC2418) can be harmonized with one defined in Working Group GitHub Usage Guidance (RFC8874)?
4. How other process such as Errata reporting process can be integrated for VOLECE

-Qin
-----邮件原件-----
发件人: Joe Clarke via Datatracker [mailto:[e-mail]] 
发送时间: 2026年6月12日 21:07
收件人: [e-mail]; [e-mail]; [e-mail]
主题: [OPSAWG]Call for adoption: draft-mahesh-opsawg-veloce-yang-01 (Ends 2026-06-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 adoption of this Internet-Draft by the opsawg WG. Comments to explain your preference 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 provisions 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 draft.

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=draft-mahesh-opsawg-veloce-yang-01

_______________________________________________
OPSAWG mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]