Re: [netmod] [Editorial Errata Reported] RFC8519 (7313)
mohamed.boucadair@orange.com Wed, 18 January 2023 19:03 UTC
Return-Path: <mohamed.boucadair@orange.com>
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 2953EC15152C for <netmod@ietfa.amsl.com>; Wed, 18 Jan 2023 11:03:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
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 KD3wMAFNCkFD for <netmod@ietfa.amsl.com>; Wed, 18 Jan 2023 11:03:08 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (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 BAD5CC14CEF9 for <netmod@ietf.org>; Wed, 18 Jan 2023 11:03:07 -0800 (PST)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr27.francetelecom.fr (ESMTP service) with ESMTPS id 4NxwBd4Fglz4wBy; Wed, 18 Jan 2023 20:03:05 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1674068585; bh=XUehRqgj4Njdoixfvq0krHDK5WP3Wdm1PClkhyLjyek=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=ulXaRs2w0sffOZ2Wc2c8HQ+ZoOS6MHqX8LbLN/AzQKDqhddUFnk5MPQuSgCk3rKHK fwMrTZeA5YLnKhbeuh6QVy6kAT6bbC7EUOeItIam2lhsGjrjoOmG4IQUEQN2+y4yfF vJ6wvw8sOSa5kijzN+qnZjnHCcjMRuCZZxcEG2EmZ+VMHFpogIhxUSO97nkRxT0ETA hZ1o9SdlRnjM7lX9emwvw8UWQHt6p8gc008DfzJb0mvTCI1iI/HRt/3yCb/CJlvq6O mmmemabuLtj8C6azlzGrUwhP/bD48v/FpU3GlqdZSKEldqQ4I50xXIzr89N9dZ0jQ3 VjlrOmiJsiZkQ==
From: mohamed.boucadair@orange.com
To: Mahesh Jethanandani <mjethanandani@gmail.com>, netmod <netmod@ietf.org>
CC: Sonal Agarwal <sagarwal12@gmail.com>, "huangyi_99@yahoo.com" <huangyi_99@yahoo.com>, "dana@blairhome.com" <dana@blairhome.com>
Thread-Topic: [Editorial Errata Reported] RFC8519 (7313)
Thread-Index: AQHZK2s55Vppy77NxEGzVBtXqKEI2a6kh1Pg
Content-Class:
Date: Wed, 18 Jan 2023 19:03:04 +0000
Message-ID: <23915_1674068585_63C84269_23915_94_1_492cbf63d10e4ed9b5b8165c0356418f@orange.com>
References: <20230118150200.47D905DC927@rfcpa.amsl.com> <AD517B52-3682-4B93-8683-E34C4675926C@gmail.com>
In-Reply-To: <AD517B52-3682-4B93-8683-E34C4675926C@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2023-01-18T19:00:31Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=7a8214c4-0008-4c87-8cb2-2404ba0e64d1; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.26.50]
Content-Type: multipart/alternative; boundary="_000_492cbf63d10e4ed9b5b8165c0356418forangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/w2sg6DacxsW8rP3HLIHyTnaBaoo>
Subject: Re: [netmod] [Editorial Errata Reported] RFC8519 (7313)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jan 2023 19:03:12 -0000
Hi Mahesh, I also recall some of that discussion... but that is not related to this erratum given the following prefix used in the import: CURRENT: import ietf-access-control-list { prefix acl; } Cheers, Med De : Mahesh Jethanandani <mjethanandani@gmail.com> Envoyé : mercredi 18 janvier 2023 19:32 À : netmod <netmod@ietf.org> Cc : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>; Sonal Agarwal <sagarwal12@gmail.com>; huangyi_99@yahoo.com; dana@blairhome.com Objet : Re: [Editorial Errata Reported] RFC8519 (7313) There was a lot of discussion on the usage of what prefix should be used when importing a module, possibly after this draft was published. However, it is a BCP, and most tools will not complain if a prefix other than what is defined in the module is used. I am not sure if a BCP rises to the level of an errata. Thanks. On Jan 18, 2023, at 7:02 AM, RFC Errata System <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>> wrote: The following errata report has been submitted for RFC8519, "YANG Data Model for Network Access Control Lists (ACLs)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7313 -------------------------------------- Type: Editorial Reported by: Mohamed Boucadair <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> Section: A.1 Original Text ------------- The following figure is the tree diagram of example-newco-acl. In this example, /ietf-acl:acls/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace/ ietf-acl:matches are augmented with two new choices: protocol- payload-choice and metadata. The protocol-payload-choice uses a grouping with an enumeration of all supported protocol values. Metadata matches apply to fields associated with the packet, that are not in the packet header, such as overall packet length. In another example, /ietf-acl:acls/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace/ ietf-acl:actions are augmented with a new choice of actions. Corrected Text -------------- The following figure is the tree diagram of example-newco-acl. In this example, /acl:acls/acl:acl/acl:aces/acl:ace/acl:matches are augmented with two new choices: protocol-payload-choice and metadata. The protocol-payload-choice uses a grouping with an enumeration of all supported protocol values. Metadata matches apply to fields associated with the packet, that are not in the packet header, such as overall packet length. In another example, /acl:acls/acl:acl/acl:aces/acl:ace/acl:actions are augmented with a new choice of actions. Notes ----- The prefix is "acl" not "ietf-acl" == module ietf-access-control-list { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-access-control-list"; prefix acl; ... == Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC8519 (draft-ietf-netmod-acl-model-21) -------------------------------------- Title : YANG Data Model for Network Access Control Lists (ACLs) Publication Date : March 2019 Author(s) : M. Jethanandani, S. Agarwal, L. Huang, D. Blair Category : PROPOSED STANDARD Source : Network Modeling Area : Operations and Management Stream : IETF Verifying Party : IESG Mahesh Jethanandani mjethanandani@gmail.com<mailto:mjethanandani@gmail.com> _________________________________________________________________________________________________________________________ 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.
- [netmod] [Editorial Errata Reported] RFC8519 (731… RFC Errata System
- Re: [netmod] [Editorial Errata Reported] RFC8519 … Eliot Lear
- Re: [netmod] [Editorial Errata Reported] RFC8519 … Mahesh Jethanandani
- Re: [netmod] [Editorial Errata Reported] RFC8519 … mohamed.boucadair
- Re: [netmod] [Editorial Errata Reported] RFC8519 … Mahesh Jethanandani
- Re: [netmod] [Editorial Errata Reported] RFC8519 … Kent Watsen
- Re: [netmod] [Editorial Errata Reported] RFC8519 … Chris Smiley