Re: [IPFIX] [MIB-DOCTORS] [mpls] MPLS IEs in IANA's IP Flow Information Export (IPFIX) Entities registry

Benoit Claise <bclaise@cisco.com> Mon, 22 September 2014 12:25 UTC

Return-Path: <bclaise@cisco.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 5F4BC1A1AAC; Mon, 22 Sep 2014 05:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.687
X-Spam-Level:
X-Spam-Status: No, score=-14.687 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 rYqydeRgtire; Mon, 22 Sep 2014 05:25:19 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12D3F1A1AB3; Mon, 22 Sep 2014 05:25:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3393; q=dns/txt; s=iport; t=1411388719; x=1412598319; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=gfRB/HC1DsXv4/557YY+jqGSzN/mNxmIFpcoKX3ZvHw=; b=exdPiBxBrXiFLsrs0/p64/7Mn/P9pBlaVzqswlhdcYDm6cDPuS0jssU8 X1V/aGvQrhP1A5aUumgob4IqNaLFJ8DMkyj1CuSFu8EVgsSkVn/LHjjFk Uk2Tjx9t+ZJwggshS+9gKRDhmeTAuwhj2yjlYh+VAUYb26ACg5BWfPfAf E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AswUALgUIFStJssW/2dsb2JhbABdA4NhV8pKCguHPQMCAYEhAXmEAwEBAQQBAQEvAQUzAwoBDAICCxEEAQEBCRYIBwkDAgECAQkMHwkIBgEMAQUCAQGIJgMRDbxXCIc0ARMEBI8gEQFAEAcGC4Q6AQSdFodMhQKJBIIegUU7L4EPgTsBAQE
X-IronPort-AV: E=Sophos;i="5.04,571,1406592000"; d="scan'208";a="185394664"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 22 Sep 2014 12:25:17 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s8MCPH5O024936; Mon, 22 Sep 2014 12:25:17 GMT
Message-ID: <5420152C.2060501@cisco.com>
Date: Mon, 22 Sep 2014 14:25:16 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0
MIME-Version: 1.0
To: ietfdbh <ietfdbh@comcast.net>, "'t.petch'" <ietfc@btconnect.com>, 'Loa Andersson' <loa@pi.nu>, 'Gregory Mirsky' <gregory.mirsky@ericsson.com>, ipfix@ietf.org
References: <7347100B5761DC41A166AC17F22DF1121B82E898@eusaamb103.ericsson.se> <541BF749.6010907@pi.nu> <004a01cfd3ff$da773380$4001a8c0@gateway.2wire.net> <061e01cfd554$bfe4dd50$3fae97f0$@comcast.net>
In-Reply-To: <061e01cfd554$bfe4dd50$3fae97f0$@comcast.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipfix/esF3iQ5dkHqHb8R-6di0MplTlJY
Cc: mpls@ietf.org, "'MIB Doctors (E-mail)'" <mib-doctors@ietf.org>
Subject: Re: [IPFIX] [MIB-DOCTORS] [mpls] 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: Mon, 22 Sep 2014 12:25:21 -0000

We could argue whether the semantic was actually changed since the EXP 
bits were used for QoS.
Anyway, let's quote Jürgen: "The question is whether doing this is worth 
anything.". I'm not convinced...

Regards, Benoit
> Updating the description would be a problem if you change the semantics of
> the object.
>
> David Harrington
> ietfdbh@comcast.net
> +1-603-828-1401
>> -----Original Message-----
>> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
>> t.petch
>> Sent: Friday, September 19, 2014 7:50 AM
>> To: Loa Andersson; Gregory Mirsky; ipfix@ietf.org
>> Cc: mpls@ietf.org; MIB Doctors (E-mail)
>> Subject: Re: [MIB-DOCTORS] [mpls] MPLS IEs in IANA's IP Flow Information
>> Export (IPFIX) Entities registry
>>
>> ----- Original Message -----
>> From: "Loa Andersson" <loa@pi.nu>
>> To: "Gregory Mirsky" <gregory.mirsky@ericsson.com>; <ipfix@ietf.org>
>> Cc: <mpls@ietf.org>; "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
>> Sent: Friday, September 19, 2014 10:28 AM
>>
>> Greg,
>>
>> I'm not sure about this - would changing the names require updating all
>> existing deployed MIBs?
>>
>> <tp>
>>
>> Yes. See RFC2578 s.10.  You cannot reuse an OID so this would need a new
>> OID; messy, best left as one of those quaint, historic anomalies that
>> litter our work.
>>
>> Updating the DESCRIPTION and REFERENCE is not a problem  (but issuing
>> any MIB module is a lot of work).
>>
>> Tom Petch
>> [not a MIB doctor]
>>
>>
>>
>>
>> Can we get an mib doctor advice on this?
>>
>> /Loa
>>
>> On 2014-09-10 21:22, 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?)
>>>
>>> Regards,
>>>
>>>           Greg
>>>
>>>
>>>
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls
>>>
>> --
>>
>>
>> Loa Andersson                        email: loa@mail01.huawei.com
>> Senior MPLS Expert                          loa@pi.nu
>> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>> _______________________________________________
>> MIB-DOCTORS mailing list
>> MIB-DOCTORS@ietf.org
>> https://www.ietf.org/mailman/listinfo/mib-doctors
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
> .
>