[bess] [Editorial Errata Reported] RFC9135 (7683)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 19 October 2023 07:56 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89AB4C1519AC for <bess@ietfa.amsl.com>; Thu, 19 Oct 2023 00:56:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.534
X-Spam-Level:
X-Spam-Status: No, score=0.534 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, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, 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 ttSUcA5YNU6c for <bess@ietfa.amsl.com>; Thu, 19 Oct 2023 00:56:04 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [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 BA725C14CE42 for <bess@ietf.org>; Thu, 19 Oct 2023 00:56:04 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 78AA618FB8DF; Thu, 19 Oct 2023 00:56:04 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: vrkic.denis@gmail.com, sajassi@cisco.com, ssalam@cisco.com, sthoria@cisco.com, jdrake@juniper.net, jorge.rabadan@nokia.com, bess@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20231019075604.78AA618FB8DF@rfcpa.amsl.com>
Date: Thu, 19 Oct 2023 00:56:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/KPQHWtIIBvMqy0GHdRwPpRQwtgo>
Subject: [bess] [Editorial Errata Reported] RFC9135 (7683)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Oct 2023 07:56:08 -0000
The following errata report has been submitted for RFC9135, "Integrated Routing and Bridging in Ethernet VPN (EVPN)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7683 -------------------------------------- Type: Editorial Reported by: Denis Vrkic <vrkic.denis@gmail.com> Section: 4.2. Original Text ------------- 2. However, if PE2 is configured for asymmetric IRB mode, PE2 will advertise TS4 MAC/IP information in a MAC/IP Advertisement route with a zero Label2 field and no Route Target identifying IP-VRF1. In this case, PE2 will install TS4 information in its ARP table and BT1. When a packet from TS2 to TS4 arrives at PE1, a longest prefix match on IP-VRF1's route table will yield the local IRB interface to BT1, where a subsequent ARP and bridge table lookup will provide the information for an asymmetric forwarding mode to PE2. Corrected Text -------------- 2. However, if PE2 is configured for asymmetric IRB mode, PE2 will advertise TS4 MAC/IP information in a MAC/IP Advertisement route with a zero Label2 field and no Route Target identifying IP-VRF1. In this case, PE1 will install TS4 information in its ARP table and BT1. When a packet from TS2 to TS4 arrives at PE1, a longest prefix match on IP-VRF1's route table will yield the local IRB interface to BT1, where a subsequent ARP and bridge table lookup will provide the information for an asymmetric forwarding mode to PE2. Notes ----- PE1 will use ARP table for forwarding traffic to PE2 - seems like typo 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. -------------------------------------- RFC9135 (draft-ietf-bess-evpn-inter-subnet-forwarding-15) -------------------------------------- Title : Integrated Routing and Bridging in Ethernet VPN (EVPN) Publication Date : October 2021 Author(s) : A. Sajassi, S. Salam, S. Thoria, J. Drake, J. Rabadan Category : PROPOSED STANDARD Source : BGP Enabled ServiceS Area : Routing Stream : IETF Verifying Party : IESG
- [bess] [Editorial Errata Reported] RFC9135 (7683) RFC Errata System
- Re: [bess] [Editorial Errata Reported] RFC9135 (7… Rebecca VanRheenen
- Re: [bess] [Errata Verified] RFC9135 (7683) Ali Sajassi (sajassi)