Re: [IPFIX] [SPAM I AM] RE: MPLS IEs in IANA's IP Flow Information Export (IPFIX) Entities registry

Andrew Feren <andrewf@plixer.com> Wed, 10 September 2014 21:43 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 8C9C81A0184 for <ipfix@ietfa.amsl.com>; Wed, 10 Sep 2014 14:43:18 -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 pLqUKfg0XK7H for <ipfix@ietfa.amsl.com>; Wed, 10 Sep 2014 14:43:16 -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 7E2291A0105 for <ipfix@ietf.org>; Wed, 10 Sep 2014 14:43:16 -0700 (PDT)
Received: from [10.1.14.85] (64.140.243.154) by mx1.plixer.com (10.1.5.1) with Microsoft SMTP Server (TLS) id 14.3.181.6; Wed, 10 Sep 2014 17:43:15 -0400
Message-ID: <5410C5F9.9030307@plixer.com>
Date: Wed, 10 Sep 2014 17:43:21 -0400
From: Andrew Feren <andrewf@plixer.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "ipfix@ietf.org" <ipfix@ietf.org>
References: <7347100B5761DC41A166AC17F22DF1121B82E898@eusaamb103.ericsson.se> <5410C1A7.6000509@plixer.com> <7347100B5761DC41A166AC17F22DF1121B82EA53@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B82EA53@eusaamb103.ericsson.se>
Content-Type: multipart/alternative; boundary="------------090707040204090105040702"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipfix/teOfsm_RS9Qepq-mN7iGCVuPfBk
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: Wed, 10 Sep 2014 21:43:18 -0000

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
> *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
>