Subject: [Errata Rejected] RFC7432 (5746)

From: RFC Errata System <[email-masked]>
Date: Sun, 16 Jun 2019 22:45:51 -0700 (PDT)

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 <[email-masked]>
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