[Technical Errata Reported] RFC7432 (5746)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 05 June 2019 07:42 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 <l2vpn@ietfa.amsl.com>; 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 <l2vpn@ietfa.amsl.com>; 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 <l2vpn@ietf.org>; 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 <rfc-editor@rfc-editor.org>
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: <https://mailarchive.ietf.org/arch/msg/l2vpn/5NtMhDtp_9aTdA-1WRh8OtTsRPk>
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 <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=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 <hyztcy@126.com>;

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