[Teas] Re: [OPSAWG]YANG deVELpment PrOCEss & maintenance (VELOCE): CCAMP/LSR/TEAS
Per Andersson <per.ietf@ionio.se> Wed, 08 April 2026 08:23 UTC
Return-Path: <perkietf@gmail.com>
X-Original-To: teas@mail2.ietf.org
Delivered-To: teas@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id EDFEDD7EE7C5 for <teas@mail2.ietf.org>; Wed, 8 Apr 2026 01:23:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1775636581; bh=3d0HmmwSPY0lWjYtuxsoM2m7eKBWLsg5+KFPDC5HQ/w=; h=References:In-Reply-To:From:Date:Subject:To:Cc; b=YrTxLj7Qs1JLUplNqV2EXA2Ct9Ceqy9yQAdoro3lFoV1YLoE7ckh20UcLeRMAMq3J +LkVpgXK9EQnSPKRa43/ay9ydd/mWcg/X+M5KWgn6yck1SNh3XdDzFs8b21lnK24s5 pRWCz4HI04FTzt2WE1BAsSf///0Axxeim6u1APoU=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level:
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZjnfO9GZfQ-z for <teas@mail2.ietf.org>; Wed, 8 Apr 2026 01:23:00 -0700 (PDT)
Received: from mail-pj1-f51.google.com (mail-pj1-f51.google.com [209.85.216.51]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id BB40AD7EE7C0 for <teas@ietf.org>; Wed, 8 Apr 2026 01:23:00 -0700 (PDT)
Received: by mail-pj1-f51.google.com with SMTP id 98e67ed59e1d1-35d9b4f93f0so1399300a91.3 for <teas@ietf.org>; Wed, 08 Apr 2026 01:23:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1775636574; x=1776241374; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=M7USWjgHTR8/aGkvFnqAj7WtSH9Ez4c9MJXmHyTNovw=; b=n4jwWLZRg4PGOUcvtMzjRu5QkXVHA+rSB1LW+fOnaVO2hTJQ2A+tWxN+CEZGLjcCwV vyPucBUtq6N8GBgcVgmCsaBGozo6+I3XT5OdkaxQrdtU7fOplcQYnjLnt2l8pNq+osLE TLE/wMZevZrVmh2GZIt0wx0EyMcKmlMk5XTnxSYdobd6EpaLJRafXPdKu42WXZQXAROv jz2Hjpbede3XDJTvNOtTSeZCGLj3xS3Y+sAaWgbjUQtxrVTD7ZO3x7QZtZkdETQBiTv3 qGepCW9MvJimRPFPLQlThpRZ77lOP1MaSg+VMLGxuwjSZi/41uAuMWVDIASewWzz4dIM rSog==
X-Forwarded-Encrypted: i=1; AJvYcCVdSa6VP4XyxGh3b45idZMBG1hRVXX9LM3cG4iz6uRqCaHk4lh6j4f0yh8Vvy1lrgLr8yHp@ietf.org
X-Gm-Message-State: AOJu0Ywb9JtlhvI7RAWLVd/+h0x+pT9JXwSGl4kzKVXyvBeij+rotCbs /Xvufl5b7Yubh/ENr4U+uDu2hlUjledblHiz/LwSZUBwf1ft0m2vCWCwgwFAo60t
X-Gm-Gg: AeBDievv2i09a6LXpV2G/a7PJfqzCLzNtR7hXiYirru1B01dmIfKGMx3zjHtktmDTaN nXjquvTFqa3gmtZ4gdRCjBNVT6CiB/aqrJDC87e4bNxKIFDdwwV8zUekQ+R+p6iTNKjaceGafS9 DP6LzAYwGSxLc7DNCC630mOxkQ+mWe0HK4eEuV3lbpO6qbPgpIijIYeWXZ9TEaYiq5GkvZAz2Ll 26PYv9SM/J2y0sqojZORHjlaa+/4+r+kdBQr6PspBn3/BxGf1XkKEYjSpikDxMW8lGiVmDhlqRU cqsK/HiZ8Hg4pUm/UJlxk+DVnluQMyWVeN1X99bcxg5LsdgcF8G+sVYY6hjGOOXTM49Jhw+cV7T WwDWbJmn9bHkcVExm9ZqH8LUNAfv8uul5sno/+Q4p313dvYzC0oOcLrrI6INNDeWznGMb19zKaT CbsD1AK/Wd0O/gsuu7OenuezYYkvBatpT9ddxFlskWh0opxhxLq+d8jOI/cpvlI13EdvozNGg=
X-Received: by 2002:a17:902:ccc9:b0:2ae:5d79:a163 with SMTP id d9443c01a7336-2b281855dd2mr127380555ad.5.1775636573603; Wed, 08 Apr 2026 01:22:53 -0700 (PDT)
Received: from mail-pf1-f181.google.com (mail-pf1-f181.google.com. [209.85.210.181]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-2b274978fd7sm261029945ad.39.2026.04.08.01.22.53 for <teas@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 08 Apr 2026 01:22:53 -0700 (PDT)
Received: by mail-pf1-f181.google.com with SMTP id d2e1a72fcca58-82a6fc924e0so130892b3a.2 for <teas@ietf.org>; Wed, 08 Apr 2026 01:22:53 -0700 (PDT)
X-Forwarded-Encrypted: i=1; AJvYcCVsoP04/FXutK/TgEpTHkE6KsE/VVa3FHzcj4WN4r9yawdOhFm7RLT4wQtHBqJdlb0JSlLD@ietf.org
X-Received: by 2002:a05:6a00:148b:b0:824:cb8f:2a06 with SMTP id d2e1a72fcca58-82d0db7f92dmr12384127b3a.3.1775636572867; Wed, 08 Apr 2026 01:22:52 -0700 (PDT)
MIME-Version: 1.0
References: <PATP264MB6765DAB651B926DF83AF9B93885BA@PATP264MB6765.FRAP264.PROD.OUTLOOK.COM>
In-Reply-To: <PATP264MB6765DAB651B926DF83AF9B93885BA@PATP264MB6765.FRAP264.PROD.OUTLOOK.COM>
From: Per Andersson <per.ietf@ionio.se>
Date: Wed, 08 Apr 2026 10:22:40 +0200
X-Gmail-Original-Message-ID: <CACvbXWFQAkJbyuxMrFYCVG4M6i7uuxrdSycS7DLznBmtuwmeWg@mail.gmail.com>
X-Gm-Features: AQROBzCSUduz00DzXlQccuW2-oBcDG3C53ELhPFDE_38M0D6--ny8lIAE90blRc
Message-ID: <CACvbXWFQAkJbyuxMrFYCVG4M6i7uuxrdSycS7DLznBmtuwmeWg@mail.gmail.com>
To: mohamed.boucadair@orange.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: SGWC326QSNAD23DUPSXMJPRTAZMBII3A
X-Message-ID-Hash: SGWC326QSNAD23DUPSXMJPRTAZMBII3A
X-MailFrom: perkietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-teas.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: lsr <lsr@ietf.org>, CCAMP <ccamp@ietf.org>, "TEAS WG (teas@ietf.org)" <teas@ietf.org>, Operations and Management Area Working Group Discussion List <opsawg@ietf.org>, Mahesh Jethanandani <mjethanandani@gmail.com>, Mithun <mithun.ietf@gmail.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Teas] Re: [OPSAWG]YANG deVELpment PrOCEss & maintenance (VELOCE): CCAMP/LSR/TEAS
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/Ea9R8Z6UmI-FOmr9UJdajNWCRy0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>
Hi Med, I am interested in this work and might have a new suitable draft [0] that has been well recieved by the NETCONF WG to work on. This draft will probably only involve IANA and example YANG modules, but my opinion is that it should be possible to streamline the creation and development of those as well. [0] https://datatracker.ietf.org/doc/draft-pamtv-netconf-error-registries/ -- Per On Wed, Apr 8, 2026 at 8:55 AM <mohamed.boucadair@orange.com> wrote: > > Hi CCAMP/LSR/TEAS, > > > > 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]. > > > > 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’t 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. > > > > 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. > > > > 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. > > > > If you are interested to contribute, please send a note to OPSAWG or directly 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 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. > > _______________________________________________ > OPSAWG mailing list -- opsawg@ietf.org > To unsubscribe send an email to opsawg-leave@ietf.org
- [Teas] YANG deVELpment PrOCEss & maintenance (VEL… mohamed.boucadair
- [Teas] Re: [OPSAWG]YANG deVELpment PrOCEss & main… Per Andersson
- [Teas] Re: YANG deVELpment PrOCEss & maintenance … Mahesh Jethanandani