Re: [sfc] How to carry metadata/context in an MPLS packet
<l.wood@surrey.ac.uk> Fri, 18 July 2014 03:11 UTC
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE1591A0422; Thu, 17 Jul 2014 20:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 DGCejJ-K_QkV; Thu, 17 Jul 2014 20:11:01 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.163]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A02191A0417; Thu, 17 Jul 2014 20:11:00 -0700 (PDT)
Received: from [85.158.137.99:58985] by server-3.bemta-3.messagelabs.com id BC/A8-08876-24098C35; Fri, 18 Jul 2014 03:10:58 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-217.messagelabs.com!1405653058!22628557!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received:
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22524 invoked from network); 18 Jul 2014 03:10:58 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-15.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 18 Jul 2014 03:10:58 -0000
Received: from EXHY022V.surrey.ac.uk (131.227.201.104) by EXHT021P.surrey.ac.uk (131.227.200.35) with Microsoft SMTP Server (TLS) id 8.3.348.2; Fri, 18 Jul 2014 04:10:58 +0100
Received: from emea01-am1-obe.outbound.protection.outlook.com (131.227.201.241) by EXHY022v.surrey.ac.uk (131.227.201.104) with Microsoft SMTP Server (TLS) id 14.3.181.6; Fri, 18 Jul 2014 04:10:57 +0100
Received: from AMSPR06MB439.eurprd06.prod.outlook.com (10.242.23.19) by AMSPR06MB438.eurprd06.prod.outlook.com (10.242.23.15) with Microsoft SMTP Server (TLS) id 15.0.985.8; Fri, 18 Jul 2014 03:10:57 +0000
Received: from AMSPR06MB439.eurprd06.prod.outlook.com ([10.242.23.19]) by AMSPR06MB439.eurprd06.prod.outlook.com ([10.242.23.19]) with mapi id 15.00.0985.008; Fri, 18 Jul 2014 03:10:57 +0000
From: l.wood@surrey.ac.uk
To: xuxiaohu@huawei.com, mpls@ietf.org
Thread-Topic: How to carry metadata/context in an MPLS packet
Thread-Index: Ac+iK9IiUw61Lt1oTZi1TxTMkTltPwACfNZj
Date: Fri, 18 Jul 2014 03:10:56 +0000
Message-ID: <1405653056176.39234@surrey.ac.uk>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08294118@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08294118@NKGEML512-MBS.china.huawei.com>
Accept-Language: en-AU, en-US
Content-Language: en-AU
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [122.200.59.30]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 02760F0D1C
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(53754006)(377454003)(199002)(189002)(107046002)(54356999)(46102001)(19580395003)(50986999)(4396001)(95666004)(74482001)(99396002)(66066001)(86362001)(19580405001)(15395725005)(81342001)(81542001)(105586002)(76482001)(15975445006)(36756003)(20776003)(31966008)(85306003)(74502001)(92566001)(83072002)(83322001)(77982001)(15198665003)(85852003)(79102001)(64706001)(80022001)(74662001)(101416001)(76176999)(21056001)(15202345003)(2656002)(106356001)(87936001)(92726001); DIR:OUT; SFP:; SCL:1; SRVR:AMSPR06MB438; H:AMSPR06MB439.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en;
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: AMSPR06MB438.eurprd06.prod.outlook.com
X-CrossPremisesHeadersFiltered: EXHY022v.surrey.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/V8F-ufK2R2ujBV7P2jbapaHhE_M
X-Mailman-Approved-At: Fri, 18 Jul 2014 03:23:24 -0700
Cc: spring@ietf.org, sfc@ietf.org
Subject: Re: [sfc] How to carry metadata/context in an MPLS packet
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jul 2014 03:11:04 -0000
How? A better question is "why?" What has to be done in MPLS that cannot be done outside it? Lloyd Wood http://about.me/lloydwood ________________________________________ From: mpls <mpls-bounces@ietf.org> on behalf of Xuxiaohu <xuxiaohu@huawei.com> Sent: Friday, 18 July 2014 11:58 AM To: mpls@ietf.org Cc: <spring@ietf.org>; sfc@ietf.org Subject: [mpls] How to carry metadata/context in an MPLS packet Hi all, I'm now considering how to carry metadata/context in an MPLS packet. I just noticed that draft-guichard-mpls-metadata-00 (http://tools.ietf.org/html/draft-guichard-mpls-metadata-00#page-6) proposes a way to carry metadata/context in an MPLS packet (see below): "3. Metadata Channel Header Format The presence of metadata within an MPLS packet must be indicated in the encapsulation. This document defines that the G-ACh Generic Associated Channel Label (GAL) [RFC5586] with label value 13 is utilized for this purpose. The GAL label provides a method to identify that a packet contains an "Associated Channel Header (ACH)" followed by a non-service payload. [RFC5586] identifies the G-ACh Generic Associated Channel by setting the first nibble of the ACH that immediately follows the bottom label in the stack if the GAL label is present, to 0001b. Further [RFC5586] expects that the ACH not be used to carry user data traffic. This document proposes an extension to allow the first nibble of the ACH to be set to 0000b and, when following the GAL, be interpreted using the semantics defined in [I-D.guichard-metadata-header] to allow metadata to be carried through the G-ACh channel." However, it seems that the special usage of the GAL as mentioned above still conflicts with the following statement quoted from [RFC5586]: " The GAL MUST NOT appear in the label stack when transporting normal user-plane packets. Furthermore, when present, the GAL MUST NOT appear more than once in the label stack." I wonder whether the special usage of the GAL as proposed in the above draft would result in any backward compatibility issue. In addition, I wonder whether it's worthwhile to reconsider the possibility of introducing a Protocol Type (PT) field immediately after the bottom of the MPLS label stack. With such PT field, any kind of future MPLS payload (e.g., metadata header or NSH) can be easily identified. Best regards, Xiaohu _______________________________________________ mpls mailing list mpls@ietf.org https://www.ietf.org/mailman/listinfo/mpls
- [sfc] How to carry metadata/context in an MPLS pa… Xuxiaohu
- Re: [sfc] How to carry metadata/context in an MPL… Xuxiaohu
- Re: [sfc] How to carry metadata/context in an MPL… Xuxiaohu
- Re: [sfc] How to carry metadata/context in an MPL… Xuxiaohu
- Re: [sfc] [spring] How to carry metadata/context … Robert Raszuk
- Re: [sfc] [spring] How to carry metadata/context … Xuxiaohu
- Re: [sfc] [spring] How to carry metadata/context … Robert Raszuk
- Re: [sfc] How to carry metadata/context in an MPL… l.wood
- Re: [sfc] How to carry metadata/context in an MPL… l.wood
- Re: [sfc] How to carry metadata/context in an MPL… Jim Guichard (jguichar)
- Re: [sfc] How to carry metadata/context in an MPL… Robert Raszuk
- Re: [sfc] [spring] How to carry metadata/context … Ron Parker
- Re: [sfc] [spring] How to carry metadata/context … Robert Raszuk