[Technical Errata Reported] RFC7432 (5523)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 12 October 2018 19:37 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 3D7D0130E8C for <l2vpn@ietfa.amsl.com>; Fri, 12 Oct 2018 12:37:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id SCHLqYDnkIkF for <l2vpn@ietfa.amsl.com>; Fri, 12 Oct 2018 12:37:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 467E6130E8D for <l2vpn@ietf.org>; Fri, 12 Oct 2018 12:37:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 07906B80A6C; Fri, 12 Oct 2018 12:37:17 -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 (5523)
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: karumugh@cisco.com, l2vpn@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20181012193717.07906B80A6C@rfc-editor.org>
Date: Fri, 12 Oct 2018 12:37:17 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2vpn/e-1Bsn_tmkN1GdH1DZtLlFXChr0>
X-Mailman-Approved-At: Mon, 15 Oct 2018 05:30:30 -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: Fri, 12 Oct 2018 19:37:53 -0000

The following errata report has been submitted for RFC7432,
"BGP MPLS-Based Ethernet VPN".

You may review the report below and at:

Type: Technical
Reported by: Krishnamoorthy Arumugham <karumugh@cisco.com>

Section: 7

Original Text
Clarifications to following sub-sections:
Section 7.1
Section 7.2
Section 7.5

Corrected Text
Section 7.1:
Add below text to the section 7.1 regarding the encoding 
of MPLS label:

"The value of the 20-bit MPLS label is encoded in the 
high-order 20 bits of the 3 bytes MPLS Label field."

Section 7.2:
Add below text to the section 7.2 regarding the encoding
of both the MPLS label fields:

"The value of the 20-bit MPLS label is encoded in the 
high-order 20 bits of the 3 bytes MPLS Label field for
both MPLS Label1 and MPLS Label2."

Section 7.5:
Add below text to the section 7.5 regarding the encoding
of ESI Label fields:

"The value of the 20-bit MPLS label is encoded in the 
high-order 20 bits of the ESI Label field."

MPLS label is a 20-bit value and is stored in a 3 bytes field in a packet. The 20-bit MPLS label value is generally stored in higher order 20 bits of the 3 byte label field. The exact encoding to be followed for storing MPLS label values are not explicitly mentioned in the RFC 7432 under section 7.1, 7.2 and 7.5 for different types of EVPN routes. This lead to ambiguity in different implementations. Hence a clarification is required.

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