From nobody Wed Jun 5 08:01:55 2019 Return-Path: X-Original-To: l2vpn@ietfa.amsl.com Delivered-To: l2vpn@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2801A12010F for ; Wed, 5 Jun 2019 00:42:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bf3JV3qV6wLW for ; Wed, 5 Jun 2019 00:42:07 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE81B1200F1 for ; Wed, 5 Jun 2019 00:42:07 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id CA77FB81CE7; Wed, 5 Jun 2019 00:41:58 -0700 (PDT) To: sajassi@cisco.com, raggarwa_1@yahoo.com, nabil.n.bitar@verizon.com, aisaac71@bloomberg.net, uttaro@att.com, jdrake@juniper.net, wim.henderickx@alcatel-lucent.com, db3546@att.com, aretana.ietf@gmail.com, martin.vigoureux@nokia.com, giheron@cisco.com, nabil.n.bitar@verizon.com Subject: [Technical Errata Reported] RFC7432 (5746) X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Cc: hyztcy@126.com, l2vpn@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20190605074158.CA77FB81CE7@rfc-editor.org> Date: Wed, 5 Jun 2019 00:41:58 -0700 (PDT) Archived-At: X-Mailman-Approved-At: Wed, 05 Jun 2019 08:01:53 -0700 X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Layer 2 Virtual Private Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jun 2019 07:42:09 -0000 The following errata report has been submitted for RFC7432, "BGP MPLS-Based Ethernet VPN". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5746 -------------------------------------- Type: Technical Reported by: Yang Huang Section: 11.2 Original Text ------------- 11.2. P-Tunnel Identification "...+ If the PE that originates the advertisement uses ingress replication for the P-tunnel for EVPN, the route MUST include the PMSI Tunnel attribute with the Tunnel Type set to Ingress Replication and the Tunnel Identifier set to a routable address of the PE." Corrected Text -------------- a routable address of the PE is not so strict. And does this mean we use the Tunnel Identifier to construct P2P tunnel for ingress replication, or we use the Originating Router's IP Address in the IMET route key, or they are equivalent meaning? This may cause interact problems when it implements differently. Could you clarify this? Thanks. Notes ----- 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. -------------------------------------- RFC7432 (draft-ietf-l2vpn-evpn-11) -------------------------------------- Title : BGP MPLS-Based Ethernet VPN Publication Date : February 2015 Author(s) : A. Sajassi, Ed., R. Aggarwal, N. Bitar, A. Isaac, J. Uttaro, J. Drake, W. Henderickx Category : PROPOSED STANDARD Source : Layer 2 Virtual Private Networks Area : Routing Stream : IETF Verifying Party : IESG From nobody Mon Jun 17 03:12:41 2019 Return-Path: X-Original-To: l2vpn@ietfa.amsl.com Delivered-To: l2vpn@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99EAB12011B; Sun, 16 Jun 2019 22:46:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ncJHjzNR6vKU; Sun, 16 Jun 2019 22:46:10 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4E9A12000E; Sun, 16 Jun 2019 22:46:10 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 8A1E4B8104A; Sun, 16 Jun 2019 22:45:51 -0700 (PDT) To: hyztcy@126.com, sajassi@cisco.com, raggarwa_1@yahoo.com, nabil.n.bitar@verizon.com, aisaac71@bloomberg.net, uttaro@att.com, jdrake@juniper.net, wim.henderickx@alcatel-lucent.com Subject: [Errata Rejected] RFC7432 (5746) X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Cc: martin.vigoureux@nokia.com, iesg@ietf.org, l2vpn@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20190617054551.8A1E4B8104A@rfc-editor.org> Date: Sun, 16 Jun 2019 22:45:51 -0700 (PDT) Archived-At: X-Mailman-Approved-At: Mon, 17 Jun 2019 03:12:40 -0700 X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Layer 2 Virtual Private Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jun 2019 05:46:13 -0000 The following errata report has been rejected for RFC7432, "BGP MPLS-Based Ethernet VPN". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5746 -------------------------------------- Status: Rejected Type: Technical Reported by: Yang Huang Date Reported: 2019-06-05 Rejected by: Martin Vigoureux (IESG) Section: 11.2 Original Text ------------- 11.2. P-Tunnel Identification "...+ If the PE that originates the advertisement uses ingress replication for the P-tunnel for EVPN, the route MUST include the PMSI Tunnel attribute with the Tunnel Type set to Ingress Replication and the Tunnel Identifier set to a routable address of the PE." Corrected Text -------------- a routable address of the PE is not so strict. And does this mean we use the Tunnel Identifier to construct P2P tunnel for ingress replication, or we use the Originating Router's IP Address in the IMET route key, or they are equivalent meaning? This may cause interact problems when it implements differently. Could you clarify this? Thanks. Notes ----- --VERIFIER NOTES-- Errata is not the place to ask questions for clarifications -------------------------------------- RFC7432 (draft-ietf-l2vpn-evpn-11) -------------------------------------- Title : BGP MPLS-Based Ethernet VPN Publication Date : February 2015 Author(s) : A. Sajassi, Ed., R. Aggarwal, N. Bitar, A. Isaac, J. Uttaro, J. Drake, W. Henderickx Category : PROPOSED STANDARD Source : Layer 2 Virtual Private Networks Area : Routing Stream : IETF Verifying Party : IESG From nobody Mon Jun 17 03:12:49 2019 Return-Path: X-Original-To: l2vpn@ietfa.amsl.com Delivered-To: l2vpn@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A258B120100; Mon, 17 Jun 2019 01:47:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p3rVC9-U8NiG; Mon, 17 Jun 2019 01:47:50 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D41A12004E; Mon, 17 Jun 2019 01:47:50 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id DD50CB82252; Mon, 17 Jun 2019 01:47:30 -0700 (PDT) To: kazuhikomino@yahoo.co.jp, sajassi@cisco.com, raggarwa_1@yahoo.com, nabil.n.bitar@verizon.com, aisaac71@bloomberg.net, uttaro@att.com, jdrake@juniper.net, wim.henderickx@alcatel-lucent.com Subject: [Errata Held for Document Update] RFC7432 (5718) X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Cc: martin.vigoureux@nokia.com, iesg@ietf.org, l2vpn@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20190617084730.DD50CB82252@rfc-editor.org> Date: Mon, 17 Jun 2019 01:47:30 -0700 (PDT) Archived-At: X-Mailman-Approved-At: Mon, 17 Jun 2019 03:12:40 -0700 X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Layer 2 Virtual Private Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jun 2019 08:47:52 -0000 The following errata report has been held for document update for RFC7432, "BGP MPLS-Based Ethernet VPN". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5718 -------------------------------------- Status: Held for Document Update Type: Editorial Reported by: Kazuhiko Mino Date Reported: 2019-05-03 Held by: Martin Vigoureux (IESG) Section: 5 Original Text ------------- 5. Ethernet Segment - Type 4 (T=0x04) + Local Discriminator value (4 octets). The Local Discriminator value MUST be encoded in the 4 octets next to the IP address. Corrected Text -------------- + Local Discriminator value (4 octets). The Local Discriminator value MUST be encoded in the 4 octets next to the Router ID. Notes ----- Since the field before that is defined as "Router ID", the notation of "IP address" is not correct. -------------------------------------- RFC7432 (draft-ietf-l2vpn-evpn-11) -------------------------------------- Title : BGP MPLS-Based Ethernet VPN Publication Date : February 2015 Author(s) : A. Sajassi, Ed., R. Aggarwal, N. Bitar, A. Isaac, J. Uttaro, J. Drake, W. Henderickx Category : PROPOSED STANDARD Source : Layer 2 Virtual Private Networks Area : Routing Stream : IETF Verifying Party : IESG