Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP Flow Information Export (IPFIX) Entities registry
Andrew Feren <andrewf@plixer.com> Thu, 11 September 2014 11:06 UTC
Return-Path: <andrewf@plixer.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED1D71A893E for <ipfix@ietfa.amsl.com>; Thu, 11 Sep 2014 04:06:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.551
X-Spam-Level:
X-Spam-Status: No, score=-3.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.652] 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 gjmalQOFD3WB for <ipfix@ietfa.amsl.com>; Thu, 11 Sep 2014 04:06:50 -0700 (PDT)
Received: from mx1.plixer.com (mx1.plixer.com [64.140.243.154]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EAD81A8924 for <ipfix@ietf.org>; Thu, 11 Sep 2014 04:06:49 -0700 (PDT)
Received: from PLXRDC01.plxr.local ([::1]) by PLXRDC01.plxr.local ([::1]) with mapi id 14.03.0181.006; Thu, 11 Sep 2014 07:06:48 -0400
From: Andrew Feren <andrewf@plixer.com>
To: Benoit Claise <bclaise@cisco.com>, Gregory Mirsky <gregory.mirsky@ericsson.com>, "ipfix@ietf.org" <ipfix@ietf.org>
Thread-Topic: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP Flow Information Export (IPFIX) Entities registry
Thread-Index: AQHPzYaiZ1ddE2nNUECh3SyxCUPORpv7xRaL
Date: Thu, 11 Sep 2014 11:06:47 +0000
Message-ID: <8E7542283B89BB4DB672EB49CEE5AAB70682D90D@PLXRDC01.plxr.local>
References: <7347100B5761DC41A166AC17F22DF1121B82E898@eusaamb103.ericsson.se> <5410C1A7.6000509@plixer.com> <7347100B5761DC41A166AC17F22DF1121B82EA53@eusaamb103.ericsson.se> <5410C5F9.9030307@plixer.com>,<54113BFC.3050507@cisco.com>
In-Reply-To: <54113BFC.3050507@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [24.91.78.244]
Content-Type: multipart/alternative; boundary="_000_8E7542283B89BB4DB672EB49CEE5AAB70682D90DPLXRDC01plxrloc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipfix/m4gvHrrTAREsWIpla2OUgvH6Beo
Subject: Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP Flow Information Export (IPFIX) Entities registry
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 11:06:53 -0000
Hi Benoit, Thanks for the clarification. I don't really know the RFCs in question and took the previous reply that the interpretation of the bits had changed at face value. If Exp has effectively always been TC then I also don't see a need to deprecate all of them. -Andrew ________________________________ From: Benoit Claise [bclaise@cisco.com] Sent: Thursday, September 11, 2014 2:06 AM To: Andrew Feren; Gregory Mirsky; ipfix@ietf.org Subject: Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP Flow Information Export (IPFIX) Entities registry Two points: - The EXP bits have been used for QoS mapping for years, even before 2009 (RFC 5462 publication date) - Do you believe that deprecating/replacing all these IEs will imply that exporter implementations will update their code, just for new ElementID? :-) I would use the procedure in http://tools.ietf.org/html/rfc7013#section-5.2 Something like: OLD: The Label, Exp, and S fields from the label stack entry that was pushed immediately before the label stack entry that would be reported by mplsTopLabelStackSection. See the definition of mplsTopLabelStackSection for further details. The size of this Information Element is 3 octets. NEW: The Label, Traffic Class (previously called Exp in RFC3032<http://www.iana.org/go/rfc3032>), and S fields from the label stack entry that was pushed immediately before the label stack entry that would be reported by mplsTopLabelStackSection. See the definition of mplsTopLabelStackSection for further details. The size of this Information Element is 3 octets. And change - the reference from RFC3032<http://www.iana.org/go/rfc3032> to RFC5462 - the revision +1 Regards, Benoit Then perhaps the right thing is to deprecate the lot and replace them all. Thanks, -Andrew On 09/10/2014 05:28 PM, Gregory Mirsky wrote: Hi Andrew, you’re right, the RFC 5462 changed the interpretation of this field as well (section 2 Details of Change): 2.1<http://tools.ietf.org/html/rfc5462#section-2.1>. RFC 3032<http://tools.ietf.org/html/rfc3032> RFC 3032<http://tools.ietf.org/html/rfc3032> states on page 4: 3. Experimental Use This three-bit field is reserved for experimental use. This paragraph is now changed to: 3. Traffic Class (TC) field This three-bit field is used to carry traffic class information, and the change of the name is applicable to all places it occurs in IETF RFCs and other IETF documents. Regards, Greg From: Andrew Feren [mailto:andrewf@plixer.com] Sent: Wednesday, September 10, 2014 2:25 PM To: ipfix@ietf.org<mailto:ipfix@ietf.org> Cc: Gregory Mirsky Subject: Re: [IPFIX] MPLS IEs in IANA's IP Flow Information Export (IPFIX) Entities registry Hi Greg, On 09/10/2014 03:22 PM, Gregory Mirsky wrote: Dear All, in several places of describing MPLS Label element IEs the registry still refers to the EXP field even though the RFC 5462 updated RFC 3032 and renamed it “Traffic Class” (TC). Below is the list of IEs that may benefit from updating Description and Reference information: · mplsTopLabelStackSection · mplsTopLabelStackSection2 · mplsTopLabelStackSection3 · mplsTopLabelStackSection4 · mplsTopLabelStackSection5 · mplsTopLabelStackSection6 · mplsTopLabelStackSection7 · mplsTopLabelStackSection8 · mplsTopLabelStackSection9 · mplsTopLabelStackSection10 · mplsTopLabelExp (should this be deprecated and mplsTopLabelTc be created instead?) · postMplsTopLabelExp (should this be deprecated and postMplsTopLabelTc be created instead?) Did 5462 change just the name from Exp to TC or did the interpretation of the bits change? -Andrew _______________________________________________ IPFIX mailing list IPFIX@ietf.org<mailto:IPFIX@ietf.org> https://www.ietf.org/mailman/listinfo/ipfix
- [IPFIX] MPLS IEs in IANA's IP Flow Information Ex… Gregory Mirsky
- Re: [IPFIX] MPLS IEs in IANA's IP Flow Informatio… Andrew Feren
- Re: [IPFIX] MPLS IEs in IANA's IP Flow Informatio… Gregory Mirsky
- Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP… Andrew Feren
- Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP… Benoit Claise
- Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP… Gregory Mirsky
- Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP… Benoit Claise
- Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP… Brian Trammell
- Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP… Benoit Claise
- Re: [IPFIX] [Ie-doctors] [SPAM I AM] RE: MPLS IEs… Brian Trammell
- Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP… Andrew Feren
- Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP… Gregory Mirsky
- Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP… Brian Trammell
- Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP… Gregory Mirsky
- Re: [IPFIX] MPLS IEs in IANA's IP Flow Informatio… Paul Aitken
- Re: [IPFIX] [Ie-doctors] MPLS IEs in IANA's IP Fl… Brian Trammell
- Re: [IPFIX] [mpls] MPLS IEs in IANA's IP Flow Inf… Gregory Mirsky
- Re: [IPFIX] [MIB-DOCTORS] [mpls] MPLS IEs in IANA… Juergen Schoenwaelder
- Re: [IPFIX] [mpls] MPLS IEs in IANA's IP Flow Inf… Loa Andersson
- Re: [IPFIX] [MIB-DOCTORS] [mpls] MPLS IEs in IANA… ietfdbh
- Re: [IPFIX] [MIB-DOCTORS] [mpls] MPLS IEs in IANA… Benoit Claise