[netmod] [IANA #1289473] Revision statements in IANA-maintained YANG modules

Amanda Baber via RT <iana-issues-comment@iana.org> Sat, 01 June 2024 05:22 UTC

Return-Path: <iana-shared@icann.org>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E22ABC15108E for <netmod@ietfa.amsl.com>; Fri, 31 May 2024 22:22:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.624
X-Spam-Level:
X-Spam-Status: No, score=-0.624 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MISSING_HEADERS=1.021, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBtM95H5EgIz for <netmod@ietfa.amsl.com>; Fri, 31 May 2024 22:22:47 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [192.0.33.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98AF9C151079 for <netmod@ietf.org>; Fri, 31 May 2024 22:22:47 -0700 (PDT)
Received: from request6.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id 67772E1960; Sat, 1 Jun 2024 05:22:47 +0000 (UTC)
Received: by request6.lax.icann.org (Postfix, from userid 48) id 535E550214; Sat, 1 Jun 2024 05:22:47 +0000 (UTC)
RT-Owner: amanda.baber
From: Amanda Baber via RT <iana-issues-comment@iana.org>
In-Reply-To: <rt-5.0.3-24091-1717135382-1682.1289473-9-0@icann.org>
References: <RT-Ticket-1289473@icann.org> <rt-5.0.3-1442929-1700610506-1513.1289473-9-0@icann.org> <rt-5.0.3-1170733-1714526356-1617.1289473-9-0@icann.org> <DU2PR02MB10160BD441C48E8415DD91F1788FC2@DU2PR02MB10160.eurprd02.prod.outlook.com> <rt-5.0.3-24091-1717135382-1682.1289473-9-0@icann.org>
Message-ID: <rt-5.0.3-133728-1717219367-959.1289473-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1289473
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Sat, 01 Jun 2024 05:22:47 +0000
MIME-Version: 1.0
Message-ID-Hash: QDBR62QX5J5YIJOGUDTGBPLBWQQNYEG6
X-Message-ID-Hash: QDBR62QX5J5YIJOGUDTGBPLBWQQNYEG6
X-MailFrom: iana-shared@icann.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netmod.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: netmod@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: iana-issues-comment@iana.org
Subject: [netmod] [IANA #1289473] Revision statements in IANA-maintained YANG modules
List-Id: NETMOD WG list <netmod.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/0bk-dzi2g6-K8i272FjcUIdPlUs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Owner: <mailto:netmod-owner@ietf.org>
List-Post: <mailto:netmod@ietf.org>
List-Subscribe: <mailto:netmod-join@ietf.org>
List-Unsubscribe: <mailto:netmod-leave@ietf.org>

Hi Med,

Sorry, I dropped the ball on this one. I'll get you a list of requirements that it looks like IANA needs to be aware of when updating IANA-maintained YANG modules. 

thanks,
Amanda

On Fri May 31 06:03:02 2024, mohamed.boucadair@orange.com wrote:
> Hi Amanda,
> 
> Any update about this point? Do you still think some change is needed?
> 
> Thank you.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : BOUCADAIR Mohamed INNOV/NET
> > Envoyé : lundi 6 mai 2024 17:18
> > À : 'iana-issues-comment@iana.org' <iana-issues-comment@iana.org>
> > Objet : RE: [IANA #1289473] Revision statements in IANA-
> > maintained YANG modules
> >
> > Hi Amanda,
> >
> > Apologies for the delay to reply as I was out of office last
> > week. I will also be unavailable most of this week as well.
> >
> > We do have this section
> > https://boucadair.github.io/rfc8407bis/draft-ietf-netmod-
> > rfc8407bis.html#name-guidance-for-writing-the-ia with a set of
> > instructions that are meant to feed the maintenance. However, I'm
> > not sure if that is what you are looking for.
> >
> > The only change I made so far can be tracked here:
> > https://author-
> > tools.ietf.org/api/iddiff?url_1=https://boucadair.github.io/rfc84
> > 07bis/draft-ietf-netmod-
> > rfc8407bis.txt&url_2=https://boucadair.github.io/rfc8407bis/maint
> > enance-instructions/draft-ietf-netmod-rfc8407bis.txt
> >
> > I can make more changes once I have a better understanding of the
> > concern :-)
> >
> > Thank you.
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De : Amanda Baber via RT <iana-issues-comment@iana.org>
> > Envoyé :
> > > mercredi 1 mai 2024 03:19 Cc : BOUCADAIR Mohamed INNOV/NET
> > > <mohamed.boucadair@orange.com> Objet : [IANA #1289473] Revision
> > > statements in IANA-maintained YANG modules
> > >
> > >
> > > Hi Med,
> > >
> > > A note about draft-ietf-netmod-rfc8407bis:
> > >
> > > It's easy to find information about creating IANA-maintained
> > modules,
> > > but information about maintaining them isn't as easy to find. I
> > wonder
> > > if in addition to telling us what to register, the IANA
> > Considerations
> > > section might also list the points that IANA needs to take away
> > from
> > > the document (perhaps with pointers to the appropriate
> > > section/subsections).
> > >
> > > thanks,
> > > Amanda
> ____________________________________________________________________________________________________________
> 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.