Re: [mpls] [bier] The first nibble issue associated with MPLS encapsulation

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Thu, 14 April 2016 12:59 UTC

Return-Path: <cpignata@cisco.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A65FD12D591; Thu, 14 Apr 2016 05:59:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.516
X-Spam-Level:
X-Spam-Status: No, score=-15.516 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, 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 8fZUu6WCUGCo; Thu, 14 Apr 2016 05:59:10 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46F9212D10E; Thu, 14 Apr 2016 05:59:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6861; q=dns/txt; s=iport; t=1460638750; x=1461848350; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=U6M4Fw1qAF6zqUMwTTvEKB+KgnEjQ9CKuJGUiCAO3AA=; b=C27cWAE8QG245XcfrBztl5chMB4kCf0yj4v9ohN9gyIzUS9dRF0TeVaq ZyrZSxLoXmV9dgA3AJj8sWlKuRgJJszxu8Uve0ql0wvfySDo4JiwDNNXX Sjk/+9iuuZLRIooKF1Cjl5AAyJfQ2Nb/vL+yECwmMEzw1yee1IzO3vFN4 A=;
X-Files: signature.asc : 841
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BuAwCrkw9X/5JdJa1egmtNgVAGtTaCZ?= =?us-ascii?q?IIPDoFxhg4CgTQ4FAEBAQEBAQFlJ4RBAQEBAwEjVgULAgEIGCoCAjIlAgQOBQ6?= =?us-ascii?q?IEwiwDZJDAQEBAQEBAQEBAQEBAQEBAQEBAQEBDQiGIYF1glaHPyuCKwEEmAsBg?= =?us-ascii?q?yOBZokDjxCPKAEeAUODZ2yISH4BAQE?=
X-IronPort-AV: E=Sophos;i="5.24,484,1454976000"; d="asc'?scan'208,217";a="91762122"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Apr 2016 12:59:09 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u3ECx8H9002176 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 14 Apr 2016 12:59:09 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 14 Apr 2016 08:59:08 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1104.009; Thu, 14 Apr 2016 08:59:08 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Xuxiaohu <xuxiaohu@huawei.com>
Thread-Topic: [bier] [mpls] The first nibble issue associated with MPLS encapsulation
Thread-Index: AQHRlZN9PVrX2Wi8F0+nxhEebuX+pp+JDVoAgAClZwA=
Date: Thu, 14 Apr 2016 12:59:08 +0000
Message-ID: <6FF3596A-DC0A-4EBE-889D-2FF3DD2A5B8A@cisco.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D53871C@NKGEML515-MBX.china.huawei.com> <B664DB14-0A8C-4437-83E3-F9DA6C0DDA61@cisco.com> <mc51yrrf9n0wxbjsrprt9amf.1460143890063@email.android.com> <CA+RyBmXpZ-Kt77TW-=_kPYmahdw_yUHB5xhy8YtYVq2OcRJxbA@mail.gmail.com> <D32DB725.3F57B%cpignata@cisco.com> <CA+RyBmW+qonpScnLOfsGorayCvsS0vrFcn+o5nPvOqCOv9Jc3g@mail.gmail.com> <AM3PR03MB0775C55E5AD3247F373007139D940@AM3PR03MB0775.eurprd03.prod.outlook.com> <570BB266.8090608@juniper.net> <CFAC7D65-1AF0-4185-B580-2D1BB6728823@cisco.com> <570E5C1A.7010606@juniper.net> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D539EF2@NKGEML515-MBX.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D539EF2@NKGEML515-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.210.95]
Content-Type: multipart/signed; boundary="Apple-Mail=_3957F221-A2E8-42A6-A675-2C7B3AAD2477"; protocol="application/pgp-signature"; micalg=pgp-sha256
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/EpFwHpM2NwOzyv2b7LPhQPN_9iI>
Cc: "bier@ietf.org" <bier@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "Dr. Tony Przygienda" <tonysietf@gmail.com>
Subject: Re: [mpls] [bier] The first nibble issue associated with MPLS encapsulation
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2016 12:59:11 -0000

> On Apr 13, 2016, at 11:07 PM, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> 
>> Well, of course, that's why the nibble is not a protocol type field ;-) In the MPLS
> 
> If we pick different values for the first nibble of different MPLS payloads, the first nibble actually plays the role of a protocol type field.

No. Really no.

> In fact, there is an attempt to have a registry for the first nibble (a.k.a., MPLS payload type field).
> 

Let’s not.

Thanks,

— Carlos.

> Best regards,
> Xiaohu