Date: Mon, 15 Oct 2018 16:55:15 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>, BESS <bess@ietf.org>, 
 "=?utf-8?Q?Rabadan=2C_Jorge_(Nokia_-_US/Mountain_View)?="
 <jorge.rabadan@nokia.com>
Message-ID: <331b0259-89fb-4b5c-80bd-482c10b64c47@Spark>
In-Reply-To: <0E8EAD5C-E7E3-4BE6-9F2E-4B617D9D7D37@nokia.com>
References: <0E8EAD5C-E7E3-4BE6-9F2E-4B617D9D7D37@nokia.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5bc528e8_22221a70_4f6d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/bDLo4JAu-KSzYg_DCp6vN5LWmM4>
Subject: Re: [bess] Encoding a 20 bit label in a 24 bit field.
Precedence: list

--5bc528e8_22221a70_4f6d
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

+1

Cheers,
Jeff
On Oct 15, 2018, 4:41 PM -0700, Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com>, wrote:
> I personally agree that it is good to make this explicit (although many implementations already interpreted it this way).
> Thanks,
> Jorge
>
>
> -----Original Message-----
> From: BESS <bess-bounces@ietf.org> on behalf of "Jakob Heitz (jheitz)" <jheitz@cisco.com>
> Date: Monday, October 15, 2018 at 3:22 PM
> To: BESS <bess@ietf.org>
> Subject: [bess] Encoding a 20 bit label in a 24 bit field.
>
> We have proposed the following erratum for RFC 7432.
>
> Opinions?
>
> Regards,
> Jakob.
>
>
> -----Original Message-----
> From: RFC Errata System <rfc-editor@rfc-editor.org>
> Sent: Friday, October 12, 2018 12:37 PM
> To: Ali Sajassi (sajassi) <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; Giles Heron (giheron) <giheron@cisco.com>; nabil.n.bitar@verizon.com
> Cc: Krishnamoorthy Arumugham (karumugh) <karumugh@cisco.com>; l2vpn@ietf.org; rfc-editor@rfc-editor.org
> Subject: [Technical Errata Reported] RFC7432 (5523)
>
> 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/eid5523
>
> --------------------------------------
> 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."
>
>
> Notes
> -----
> 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.
>
> 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
>
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess
>
>
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess

--5bc528e8_22221a70_4f6d
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns=3D=22http://www.w3.org/1999/xhtml=22>
<head>
<title></title>
</head>
<body>
<div name=3D=22messageBodySection=22 style=3D=22font-size: 14px; font-fam=
ily: -apple-system, BlinkMacSystem=46ont, sans-serif;=22>+1</div>
<div name=3D=22messageSignatureSection=22 style=3D=22font-size: 14px; fon=
t-family: -apple-system, BlinkMacSystem=46ont, sans-serif;=22><br />
Cheers,
<div>Jeff</div>
</div>
<div name=3D=22messageReplySection=22 style=3D=22font-size: 14px; font-fa=
mily: -apple-system, BlinkMacSystem=46ont, sans-serif;=22>On Oct 15, 2018=
, 4:41 PM -0700, Rabadan, Jorge (Nokia - US/Mountain View) &lt;jorge.raba=
dan=40nokia.com&gt;, wrote:<br />
<blockquote type=3D=22cite=22 style=3D=22margin: 5px 5px; padding-left: 1=
0px; border-left: thin solid =231abc9c;=22>I personally agree that it is =
good to make this explicit (although many implementations already interpr=
eted it this way).<br />
Thanks,<br />
Jorge<br />
<br />
<br />
=EF=BB=BF-----Original Message-----<br />
=46rom: BESS &lt;bess-bounces=40ietf.org&gt; on behalf of =22Jakob Heitz =
(jheitz)=22 &lt;jheitz=40cisco.com&gt;<br />
Date: Monday, October 15, 2018 at 3:22 PM<br />
To: BESS &lt;bess=40ietf.org&gt;<br />
Subject: =5Bbess=5D Encoding a 20 bit label in a 24 bit field.<br />
<br />
We have proposed the following erratum for R=46C 7432.<br />
<br />
Opinions=3F<br />
<br />
Regards,<br />
Jakob.<br />
<br />
<br />
-----Original Message-----<br />
=46rom: R=46C Errata System &lt;rfc-editor=40rfc-editor.org&gt;<br />
Sent: =46riday, October 12, 2018 12:37 PM<br />
To: Ali Sajassi (sajassi) &lt;sajassi=40cisco.com&gt;; raggarwa=5F1=40yah=
oo.com; nabil.n.bitar=40verizon.com; aisaac71=40bloomberg.net; uttaro=40a=
tt.com; jdrake=40juniper.net; wim.henderickx=40alcatel-lucent.com; db3546=
=40att.com; aretana.ietf=40gmail.com; martin.vigoureux=40nokia.com; Giles=
 Heron (giheron) &lt;giheron=40cisco.com&gt;; nabil.n.bitar=40verizon.com=
<br />
Cc: Krishnamoorthy Arumugham (karumugh) &lt;karumugh=40cisco.com&gt;; l2v=
pn=40ietf.org; rfc-editor=40rfc-editor.org<br />
Subject: =5BTechnical Errata Reported=5D R=46C7432 (5523)<br />
<br />
The following errata report has been submitted for R=46C7432,<br />
=22BGP MPLS-Based Ethernet VPN=22.<br />
<br />
--------------------------------------<br />
You may review the report below and at:<br />
http://www.rfc-editor.org/errata/eid5523<br />
<br />
--------------------------------------<br />
Type: Technical<br />
Reported by: Krishnamoorthy Arumugham &lt;karumugh=40cisco.com&gt;<br />
<br />
Section: 7<br />
<br />
Original Text<br />
-------------<br />
Clarifications to following sub-sections:<br />
Section 7.1<br />
Section 7.2<br />
Section 7.5<br />
<br />
<br />
Corrected Text<br />
--------------<br />
Section 7.1:<br />
Add below text to the section 7.1 regarding the encoding<br />
of MPLS label:<br />
<br />
=22The value of the 20-bit MPLS label is encoded in the<br />
high-order 20 bits of the 3 bytes MPLS Label field.=22<br />
<br />
Section 7.2:<br />
Add below text to the section 7.2 regarding the encoding<br />
of both the MPLS label fields:<br />
<br />
=22The value of the 20-bit MPLS label is encoded in the<br />
high-order 20 bits of the 3 bytes MPLS Label field for<br />
both MPLS Label1 and MPLS Label2.=22<br />
<br />
Section 7.5:<br />
Add below text to the section 7.5 regarding the encoding<br />
of ESI Label fields:<br />
<br />
=22The value of the 20-bit MPLS label is encoded in the<br />
high-order 20 bits of the ESI Label field.=22<br />
<br />
<br />
Notes<br />
-----<br />
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 R=46C 7432 under s=
ection 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=
.<br />
<br />
Instructions:<br />
-------------<br />
This erratum is currently posted as =22Reported=22. If necessary, please<=
br />
use =22Reply All=22 to discuss whether it should be verified or<br />
rejected. When a decision is reached, the verifying party<br />
can log in to change the status and edit the report, if necessary.<br />
<br />
--------------------------------------<br />
R=46C7432 (draft-ietf-l2vpn-evpn-11)<br />
--------------------------------------<br />
Title : BGP MPLS-Based Ethernet VPN<br />
Publication Date : =46ebruary 2015<br />
Author(s) : A. Sajassi, Ed., R. Aggarwal, N. Bitar, A. Isaac, J. Uttaro, =
J. Drake, W. Henderickx<br />
Category : PROPOSED STANDARD<br />
Source : Layer 2 Virtual Private Networks<br />
Area : Routing<br />
Stream : IET=46<br />
Verifying Party : IESG<br />
<br />
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br />
BESS mailing list<br />
BESS=40ietf.org<br />
https://www.ietf.org/mailman/listinfo/bess<br />
<br />
<br />
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br />
BESS mailing list<br />
BESS=40ietf.org<br />
https://www.ietf.org/mailman/listinfo/bess<br /></blockquote>
</div>
</body>
</html>

--5bc528e8_22221a70_4f6d--