Re: [spring] How to carry metadata/context in an MPLS packet
<l.wood@surrey.ac.uk> Fri, 18 July 2014 03:22 UTC
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC8611B286B; Thu, 17 Jul 2014 20:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 tYvBqc935G2I; Thu, 17 Jul 2014 20:22:31 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.150]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 777A41A0418; Thu, 17 Jul 2014 20:22:30 -0700 (PDT)
Received: from [195.245.231.67:51838] by server-14.bemta-5.messagelabs.com id 1C/47-11783-5F298C35; Fri, 18 Jul 2014 03:22:29 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-12.tower-82.messagelabs.com!1405653747!39396238!6
X-Originating-IP: [131.227.200.39]
X-StarScan-Received:
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5082 invoked from network); 18 Jul 2014 03:22:28 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-12.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 18 Jul 2014 03:22:28 -0000
Received: from EXHY011V.surrey.ac.uk (131.227.200.103) by EXHT012P.surrey.ac.uk (131.227.200.39) with Microsoft SMTP Server (TLS) id 8.3.348.2; Fri, 18 Jul 2014 04:22:27 +0100
Received: from emea01-am1-obe.outbound.protection.outlook.com (131.227.200.4) by email365.surrey.ac.uk (131.227.200.103) with Microsoft SMTP Server (TLS) id 14.3.181.6; Fri, 18 Jul 2014 04:22:26 +0100
Received: from AMSPR06MB439.eurprd06.prod.outlook.com (10.242.23.19) by AMSPR06MB437.eurprd06.prod.outlook.com (10.242.23.11) with Microsoft SMTP Server (TLS) id 15.0.985.8; Fri, 18 Jul 2014 03:22:26 +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:22:26 +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+iK9IiUw61Lt1oTZi1TxTMkTltPwACfNZjAAAtuoAAADRSVw==
Date: Fri, 18 Jul 2014 03:22:26 +0000
Message-ID: <1405653745773.33083@surrey.ac.uk>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08294118@NKGEML512-MBS.china.huawei.com> <1405653056176.39234@surrey.ac.uk>, <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08294173@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08294173@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)(51444003)(53754006)(51704005)(13464003)(199002)(189002)(377454003)(83322001)(64706001)(66066001)(20776003)(76176999)(87936001)(15975445006)(50986999)(19580405001)(95666004)(54356999)(101416001)(105586002)(85306003)(107046002)(76482001)(46102001)(92566001)(36756003)(15395725005)(19580395003)(77982001)(74662001)(79102001)(86362001)(74502001)(4396001)(2656002)(106356001)(31966008)(92726001)(85852003)(81542001)(83072002)(81342001)(21056001)(15202345003)(99396002)(74482001)(15198665003)(80022001); DIR:OUT; SFP:; SCL:1; SRVR:AMSPR06MB437; 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: AMSPR06MB437.eurprd06.prod.outlook.com
X-OriginatorOrg: surrey.ac.uk
X-CrossPremisesHeadersPromoted: EXHY011v.surrey.ac.uk
X-CrossPremisesHeadersFiltered: EXHY011v.surrey.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/spring/CKYjz0k6mwqRnOmJXt4Jw20LItU
X-Mailman-Approved-At: Fri, 18 Jul 2014 06:02:37 -0700
Cc: spring@ietf.org, sfc@ietf.org
Subject: Re: [spring] How to carry metadata/context in an MPLS packet
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jul 2014 03:22:33 -0000
No, my "why" is "why have metadata in the MPLS header at all"? Why does this have to be done inband? I am questioning the basis for doing this. There is no "must" here. Lloyd Wood http://about.me/lloydwood ________________________________________ From: Xuxiaohu <xuxiaohu@huawei.com> Sent: Friday, 18 July 2014 1:17 PM To: Wood L Dr (Electronic Eng); mpls@ietf.org Cc: spring@ietf.org; sfc@ietf.org Subject: RE: How to carry metadata/context in an MPLS packet The presence of metadata within an MPLS packet must be indicated in the encapsulation. I think that's the "why" you may want to know. Best regards, Xiaohu > -----Original Message----- > From: l.wood@surrey.ac.uk [mailto:l.wood@surrey.ac.uk] > Sent: Friday, July 18, 2014 11:11 AM > To: Xuxiaohu; mpls@ietf.org > Cc: spring@ietf.org; sfc@ietf.org > Subject: RE: How to carry metadata/context in an MPLS packet > > 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
- [spring] How to carry metadata/context in an MPLS… Xuxiaohu
- Re: [spring] How to carry metadata/context in an … Xuxiaohu
- Re: [spring] How to carry metadata/context in an … Xuxiaohu
- Re: [spring] How to carry metadata/context in an … Xuxiaohu
- Re: [spring] How to carry metadata/context in an … Robert Raszuk
- Re: [spring] How to carry metadata/context in an … Xuxiaohu
- Re: [spring] How to carry metadata/context in an … Robert Raszuk
- Re: [spring] [sfc] How to carry metadata/context … Robert Raszuk
- Re: [spring] [sfc] How to carry metadata/context … Ron Parker
- Re: [spring] [sfc] How to carry metadata/context … Jim Guichard (jguichar)
- Re: [spring] How to carry metadata/context in an … l.wood
- Re: [spring] How to carry metadata/context in an … l.wood
- Re: [spring] [sfc] How to carry metadata/context … Robert Raszuk