[bess] [Errata Rejected] RFC9135 (7686)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 12 February 2024 15:28 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 2B206C14E513; Mon, 12 Feb 2024 07:28:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.958
X-Spam-Level:
X-Spam-Status: No, score=-3.958 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, 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=ham 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 sjwAzpUOwemy; Mon, 12 Feb 2024 07:28:26 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [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 DD952C14F61A; Mon, 12 Feb 2024 07:28:26 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id B425119768F6; Mon, 12 Feb 2024 07:28:26 -0800 (PST)
To: vrkic.denis@gmail.com, sajassi@cisco.com, ssalam@cisco.com, sthoria@cisco.com, jdrake@juniper.net, jorge.rabadan@nokia.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: jgs@juniper.net, iesg@ietf.org, bess@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240212152826.B425119768F6@rfcpa.amsl.com>
Date: Mon, 12 Feb 2024 07:28:26 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/U295VRss7cws8aOMM4h72ma-8Ps>
X-Mailman-Approved-At: Tue, 13 Feb 2024 13:44:19 -0800
Subject: [bess] [Errata Rejected] RFC9135 (7686)
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: Mon, 12 Feb 2024 15:28:31 -0000
The following errata report has been rejected for RFC9135, "Integrated Routing and Bridging in Ethernet VPN (EVPN)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7686 -------------------------------------- Status: Rejected Type: Technical Reported by: Denis Vrkic <vrkic.denis@gmail.com> Date Reported: 2023-10-20 Rejected by: John Scudder (IESG) Section: 6.1 Original Text ------------- 6.1. Control Plane - Advertising PE When a PE (e.g., PE1 in Figure 4 above) learns the MAC and IP address of an attached TS (e.g., via an ARP request or ND Neighbor Solicitation), it populates its MAC-VRF/BT, IP-VRF, and ARP table or NDP cache just as in the case for symmetric IRB. Corrected Text -------------- 6.1. Control Plane - Advertising PE When a PE (e.g., PE1 in Figure 4 above) learns the MAC and IP address of an attached TS (e.g., via an ARP request or ND Neighbor Solicitation), it populates its MAC-VRF/BT and ARP table or NDP cache. Notes ----- - advertising PE (egress PE) is not advertising Label2 ("the MPLS Label2 field MUST NOT be included in this route.") - so this must be asymmetric egress PE - in 4.2 is stated that: "the asymmetric IRB mode simplifies the forwarding model and saves space in the IP-VRF route table, since host routes are not installed in the route table." - so i guess that, advertising PE in asymmetric mode, is NOT leaning/storing local IP to IP-VRF table only ARP (bound to IP-VRF) and MAC into MAC-VRF --VERIFIER NOTES-- See https://mailarchive.ietf.org/arch/msg/bess/9pvIR6OysyFKso9rDRb-CJj7we8/ -------------------------------------- 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] [Errata Rejected] RFC9135 (7686) RFC Errata System