[OPSAWG] [Editorial Errata Reported] RFC9291 (7143)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 03 October 2022 12:53 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0336AC1522D4 for <opsawg@ietfa.amsl.com>; Mon, 3 Oct 2022 05:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 Ql_zVaVNrmOB for <opsawg@ietfa.amsl.com>; Mon, 3 Oct 2022 05:53:07 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (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 3593AC1522D6 for <opsawg@ietf.org>; Mon, 3 Oct 2022 05:53:07 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 0E889C88A9; Mon, 3 Oct 2022 05:53:07 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: nmalykh@ieee.org, mohamed.boucadair@orange.com, oscar.gonzalezdedios@telefonica.com, samier.barguilgiraldo.ext@telefonica.com, luis-angel.munoz@vodafone.com, opsawg@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20221003125307.0E889C88A9@rfcpa.amsl.com>
Date: Mon, 03 Oct 2022 05:53:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/8p8eg5FwceAtSy_oDVCFXBygsHA>
Subject: [OPSAWG] [Editorial Errata Reported] RFC9291 (7143)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2022 12:53:11 -0000
The following errata report has been submitted for RFC9291, "A YANG Network Data Model for Layer 2 VPNs". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7143 -------------------------------------- Type: Editorial Reported by: Nikolai Malykh <nmalykh@ieee.org> Section: 4 Original Text ------------- Figure 1 illustrates how the L2NM is used. As a reminder, this figure is an expansion of the architecture presented in Section 3 of [RFC8466] and decomposes the box marked "orchestration" in that figure into three separate functional components called "Service Orchestration", "Network Orchestration", and "Domain Orchestration". Corrected Text -------------- Figure 1 illustrates how the L2NM is used. As a reminder, this figure is an expansion of the architecture presented in Section 4 of [RFC8466] and decomposes the box marked "orchestration" in that figure into three separate functional components called "Service Orchestration", "Network Orchestration", and "Domain Orchestration". Notes ----- Wrong reference to Section 3 [RFC8466] (must be Section 4). 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. -------------------------------------- RFC9291 (draft-ietf-opsawg-l2nm-19) -------------------------------------- Title : A YANG Network Data Model for Layer 2 VPNs Publication Date : September 2022 Author(s) : M. Boucadair, Ed., O. Gonzalez de Dios, Ed., S. Barguil, L. Munoz Category : PROPOSED STANDARD Source : Operations and Management Area Working Group Area : Operations and Management Stream : IETF Verifying Party : IESG
- [OPSAWG] [Editorial Errata Reported] RFC9291 (714… RFC Errata System