Re: [bess] Encoding a 20 bit label in a 24 bit field.
"Ali Sajassi (sajassi)" <sajassi@cisco.com> Tue, 16 October 2018 17:29 UTC
Return-Path: <sajassi@cisco.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58D00130E01 for <bess@ietfa.amsl.com>; Tue, 16 Oct 2018 10:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.565
X-Spam-Level:
X-Spam-Status: No, score=-14.565 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.064, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 FssV7bMsV26L for <bess@ietfa.amsl.com>; Tue, 16 Oct 2018 10:29:40 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85895130DC7 for <bess@ietf.org>; Tue, 16 Oct 2018 10:29:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6626; q=dns/txt; s=iport; t=1539710980; x=1540920580; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=peJkZFBc0J77afGfRHirLm/mHEqMWpJOyBIYgCMuWWw=; b=dZfFJGYx2Rcz28OUCChSZJrbr7B+RLVX9WqJer60z7seo+rZxEfOxFda vAn+807usRRZWbfAmS01xJrM6z4Bmz6JMy4b7Uf4E5yOOjlOZZj0uCvc+ sDVYgG/LxhDbvWX9NkM+Y0cmTYI7Q03SXEPp7qqBfJmNvtVfaJZlxNiv2 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAADeHsZb/5NdJa1jGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBggNmfygKg2uIF4wugWglgluGGY4TgXoLAQEYC4RJAheEUCE0DQ0BAwEBAgEBAm0cDIU5AQEFAQEhEToXBgEIEQQBAQMCIwMCBB8GCxMBAQgKBAESgyABgWkDFQ+mRoEuh3oNghiBC4pBF4IAgRInDBOCHi6CVkUBAYFhF4JsMYImAoceCIFCJIZwjgAuCQKJaYNNBoMdF4FPhHCJX405iE0CERSBJh04gVVwFRohKgGCQQmCGggSiFuFPm8BilWBHwEB
X-IronPort-AV: E=Sophos;i="5.54,389,1534809600"; d="scan'208";a="467342396"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Oct 2018 17:29:39 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by rcdn-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id w9GHTdkI025292 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 16 Oct 2018 17:29:39 GMT
Received: from xch-rtp-005.cisco.com (64.101.220.145) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 16 Oct 2018 13:29:38 -0400
Received: from xch-rtp-005.cisco.com ([64.101.220.145]) by XCH-RTP-005.cisco.com ([64.101.220.145]) with mapi id 15.00.1395.000; Tue, 16 Oct 2018 13:29:38 -0400
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>, Zhuangshunwan <zhuangshunwan@huawei.com>, BESS <bess@ietf.org>
Thread-Topic: [bess] Encoding a 20 bit label in a 24 bit field.
Thread-Index: AQHUZXXQUdZMwhG1nUinrA2l/1QLWw==
Date: Tue, 16 Oct 2018 17:29:38 +0000
Message-ID: <F78CB1EA-86B9-4496-852A-4E262263E256@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.c.0.180410
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.76.53]
Content-Type: text/plain; charset="utf-8"
Content-ID: <FA3F87C110CFD543A8EC89551AEE49DF@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.152, xch-rtp-012.cisco.com
X-Outbound-Node: rcdn-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/K75CDNRFZXrhQJAptROOPs8R2-A>
Subject: Re: [bess] Encoding a 20 bit label in a 24 bit field.
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Oct 2018 17:29:43 -0000
Yes, just the encoding of label value needs to be clear. Cheers, Ali On 10/15/18, 6:24 PM, "BESS on behalf of Jakob Heitz (jheitz)" <bess-bounces@ietf.org on behalf of jheitz@cisco.com> wrote: How about: The lower order 4 bits SHOULD be sent as 0 and ignored on receipt. Regards, Jakob. -----Original Message----- From: Zhuangshunwan <zhuangshunwan@huawei.com> Sent: Monday, October 15, 2018 6:02 PM To: Jakob Heitz (jheitz) <jheitz@cisco.com>; BESS <bess@ietf.org> Subject: RE: Encoding a 20 bit label in a 24 bit field. It is good to make this explicit. This ambiguity has led to some unnecessary interworking problems. Should we also need to explicitly define the "bottom of stack" bit in the low-order bit of the 3-octet label field? Thanks, Shunwan -----Original Message----- From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of Jakob Heitz (jheitz) Sent: Tuesday, October 16, 2018 4:21 AM 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
- [bess] Encoding a 20 bit label in a 24 bit field. Jakob Heitz (jheitz)
- Re: [bess] Encoding a 20 bit label in a 24 bit fi… Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [bess] Encoding a 20 bit label in a 24 bit fi… Jeff Tantsura
- Re: [bess] Encoding a 20 bit label in a 24 bit fi… Zhuangshunwan
- Re: [bess] Encoding a 20 bit label in a 24 bit fi… Jakob Heitz (jheitz)
- Re: [bess] Encoding a 20 bit label in a 24 bit fi… Zhuangshunwan
- Re: [bess] Encoding a 20 bit label in a 24 bit fi… John E Drake
- Re: [bess] Encoding a 20 bit label in a 24 bit fi… Tapraj Singh (tapsingh)
- Re: [bess] Encoding a 20 bit label in a 24 bit fi… Ali Sajassi (sajassi)
- Re: [bess] Encoding a 20 bit label in a 24 bit fi… stephane.litkowski
- Re: [bess] Encoding a 20 bit label in a 24 bit fi… Acee Lindem (acee)
- Re: [bess] Encoding a 20 bit label in a 24 bit fi… Jakob Heitz (jheitz)
- Re: [bess] Encoding a 20 bit label in a 24 bit fi… Greg Mirsky
- Re: [bess] Encoding a 20 bit label in a 24 bit fi… Ali Sajassi (sajassi)