[Editorial Errata Reported] RFC4762 (4144)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 23 October 2014 11:19 UTC

To: mlasserre@alcatel-lucent.com, vach.kompella@alcatel-lucent.com, brian@innovationslab.net, ted.lemon@nominum.com, giheron@cisco.com, nabil.n.bitar@verizon.com
Subject: [Editorial Errata Reported] RFC4762 (4144)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20141023111845.94496181C71@rfc-editor.org>
Date: Thu, 23 Oct 2014 04:18:45 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/bYrdIL4LjZDqu5DlMUG1wAHkLMs
Cc: l2vpn@ietf.org, rfc-editor@rfc-editor.org
Precedence: list

The following errata report has been submitted for RFC4762,
"Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4762&eid=4144

--------------------------------------
Type: Editorial
Reported by: Alexander ("Sasha") Vainshtein <Alexander.Vainshtein@ecitele.com>

Section: Appendix A

Original Text
-------------
In a VPLS, we use a VCID (which, when using the PWid FEC, has been
substituted with a more general identifier (AGI), to address
extending the scope of a VPLS) to identify an emulated LAN segment.
Note that the VCID as specified in [RFC4447] is a service identifier,
identifying a service emulating a point-to-point virtual circuit. In
a VPLS, the VCID is a single service identifier, so it has global
significance across all PEs involved in the VPLS instance.

Corrected Text
--------------
In a VPLS, we use a PWID (which, when using the Generalized PW ID
FEC, has been substituted with a more general identifier (AGI),
to address
extending the scope of a VPLS) to identify an emulated LAN segment.
Note that the PWID as specified in [RFC4447] is a service identifier,
identifying a service emulating a point-to-point virtual circuit. In
a VPLS, the PWID is a single service identifier, so it has global
significance across all PEs involved in the VPLS instance.

Notes
-----
1. The problematic text follows a diagram depicting the PWID FEC (a.k.a. FEC-128) as it appears in RFC 4447. This diagram includes a 32-bit PWID field, but there is no VCID field. Nor is VCID mentioned anywhere in RFC 4447 - it has been used in the original Martini drafts but has then been replaced by PWID.

2. According to RFC 4447, AGI is used only in the Generalized PW ID FEC (a.k.a. FEC-129) but not in the PWID FEC (a.k.a. FEC-128).

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 (IESG)
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC4762 (draft-ietf-l2vpn-vpls-ldp-09)
--------------------------------------
Title : Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling
Publication Date : January 2007
Author(s) : M. Lasserre, Ed., V. Kompella, Ed.
Category : PROPOSED STANDARD
Source : Layer 2 Virtual Private Networks INT
Area : Internet
Stream : IETF
Verifying Party : IESG

[Editorial Errata Reported] RFC4762 (4144) RFC Errata System
[Errata Verified] RFC4762 (4144) RFC Errata System