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

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Wed, 13 April 2016 12:35 UTC

Return-Path: <Alexander.Vainshtein@ecitele.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 55DFF12DFF0 for <mpls@ietfa.amsl.com>; Wed, 13 Apr 2016 05:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level:
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eci365.onmicrosoft.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 dMsJ-zMHS6CJ for <mpls@ietfa.amsl.com>; Wed, 13 Apr 2016 05:35:14 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0121.outbound.protection.outlook.com [104.47.1.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D28BE12DF27 for <mpls@ietf.org>; Wed, 13 Apr 2016 05:35:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ECI365.onmicrosoft.com; s=selector1-ecitele-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=vYnRLsypKA66xf0od5SXaficp78W+xQdno7uSj7JDm8=; b=d5PocykmyL0f6Wnng9Rb11ujHXUFIMjHvIItYM464JxmXvsSYYTmrcyARLaHHT+Gv3Esz7w3EB9b0v5dHN283oFbDOqRPJ+56jR0uJqF4QY+Y71VmMjk/8KWbJrLo2Ma0xN0mfNBNO93XP42sNukpOM+N532Vnlq/nuhvq6i3F8=
Received: from DB3PR03MB0780.eurprd03.prod.outlook.com (10.161.55.12) by DB3PR03MB0779.eurprd03.prod.outlook.com (10.161.55.11) with Microsoft SMTP Server (TLS) id 15.1.453.26; Wed, 13 Apr 2016 12:35:11 +0000
Received: from DB3PR03MB0780.eurprd03.prod.outlook.com ([10.161.55.12]) by DB3PR03MB0780.eurprd03.prod.outlook.com ([10.161.55.12]) with mapi id 15.01.0453.029; Wed, 13 Apr 2016 12:35:11 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Loa Andersson <loa@pi.nu>, "mpls@ietf.org" <mpls@ietf.org>, tom p. <daedulus@btconnect.com>
Thread-Topic: [mpls] [sfc] The first nibble issue associated with MPLS encapsulation
Thread-Index: AQHRlXuiV/nk+9f0n0aBL4+jEZNKHZ+H0XuAgAAFZb0=
Date: Wed, 13 Apr 2016 12:35:11 +0000
Message-ID: <d3948774bx4hysw36letkn43.1460550906394@email.android.com>
References: <570BB266.8090608@juniper.net> <04c801d1957b$2be37ce0$4001a8c0@gateway.2wire.net>,<570E3879.309@pi.nu>
In-Reply-To: <570E3879.309@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: pi.nu; dkim=none (message not signed) header.d=none;pi.nu; dmarc=none action=none header.from=ecitele.com;
x-originating-ip: [176.13.5.237]
x-ms-office365-filtering-correlation-id: edb0d12a-13aa-495a-6f05-08d363980e65
x-microsoft-exchange-diagnostics: 1; DB3PR03MB0779; 5:MCgnXMaHqFiUSYICHctxNIGE4gca3LcZy3BavDdxdCN81GxXUlixYNw3UNw7RmwrxZdJHXECZOz7emh3b6R4hBKR6igeNnO+1Oc9KFq8ul0+I7hpNVgdl/jUF6eWmdY+IlOezXunh29sbo4tB5rv/w==; 24:E38JZ7Rykv/nRqVz5Fno7mlDFhFfhM6KsEHLvEWHamJSjwAGhl0qYewtcHkO1pJQEs1mh4mliPnexD+tNIbtGO0xeR7YpelEuwBsFMaf/Mo=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB3PR03MB0779;
x-microsoft-antispam-prvs: <DB3PR03MB0779338A5A51C0DDD5B49B959D960@DB3PR03MB0779.eurprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(138986009662008);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:DB3PR03MB0779; BCL:0; PCL:0; RULEID:; SRVR:DB3PR03MB0779;
x-forefront-prvs: 0911D5CE78
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(377424004)(13464003)(377454003)(24454002)(3660700001)(1220700001)(92566002)(1096002)(3280700002)(66066001)(2906002)(9686002)(19580395003)(87936001)(86362001)(11100500001)(2950100001)(10400500002)(19580405001)(2501003)(76176999)(50986999)(15975445007)(5008740100001)(5002640100001)(77096005)(106116001)(189998001)(81166005)(107886002)(6116002)(54356999)(586003)(5001770100001)(5004730100002)(102836003)(122556002)(33646002)(51650200001)(7059030); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR03MB0779; H:DB3PR03MB0780.eurprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2016 12:35:11.5516 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR03MB0779
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/tBvZBChu15nos2nIoj5HzKpMW5U>
Subject: Re: [mpls] [sfc] 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: Wed, 13 Apr 2016 12:35:17 -0000

I concur with Loa - with a qualifier:
AFAIK there is no such thing as an "Early IANA De-allocation" processūüėČ.
So we may still have to wait some time until these values become formally available for reuse.

My 2c.

Thumb typed on my cellphone
Regards,
Sasha

-------- Original Message --------
From: Loa Andersson <loa@pi.nu>
Date: Wed, April 13, 2016 3:16 PM +0300
To: mpls@ietf.org, "tom p." <daedulus@btconnect.com>
Subject: Re: [mpls] [sfc] The first nibble issue associated with MPLS encapsulation


Tom,


On 2016-04-13 19:53, t.petch wrote:
> ----- Original Message -----
> From: "Eric C Rosen" <erosen@juniper.net>
> Sent: Monday, April 11, 2016 3:19 PM
>
>
>> (Removed sfc from the cc-list, this seems out of scope for that WG.)
>>
>> In designing the BIER header, the BIER WG is free to mandate any value
>> it chooses in the first nibble.  These values do not come from a
> "first
>> nibble" registry.
>>
>> It seems prudent to put a value like 5 for the following reasons:
>>
>> - If a BIER packet is being parsed by an off-line tool, this is a good
>> hint (though just a hint) that the packet is actually a BIER packet;
>>
>> - If a BIER packet is traveling through an MPLS tunnel, and it
> traverses
>> a node that does its MPLS load splitting by guessing at the type of
> the
>> payload, then this is  a good hint that the MPLS payload is not IPv4,
>> IPv6, or PW.
>>
>> This strategy does incur a risk.  Suppose IPv5 gets designed,
>> implemented, and deployed, and folks start to deploy hardware that
> does
>
> Too late;  see
>
>
> https://tools.ietf.org/html/draft-boucadair-ip-version-5-8-9-historic-00

Isn't this just in time - if IPv5 is made historic - we can safely use
it.

/Loa
>
> Discussion on the int-area list.
>
> Tom Petch
>
>
>
>> MPLS load balancing by inspecting the IPv5 headers of the MPLS
>> payloads.  If a BIER packet is traversing an MPLS tunnel,
> inappropriate
>> load splitting may occur if the hardware thinks the payload is IPv5
>> rather than BIER.
>>
>> This particular risk doesn't seem very significant to me.
>>
>> Thus I don't think there's anything here that needs fixing.
>>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls