Re: [CCAMP] AD review of draft-ietf-ccamp-swcaps-update

Lou Berger <lberger@labn.net> Fri, 23 August 2013 15:22 UTC

Return-Path: <lberger@labn.net>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5DF511E8105 for <ccamp@ietfa.amsl.com>; Fri, 23 Aug 2013 08:22:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.252
X-Spam-Level:
X-Spam-Status: No, score=-102.252 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BsesCF+-uw9N for <ccamp@ietfa.amsl.com>; Fri, 23 Aug 2013 08:22:06 -0700 (PDT)
Received: from oproxy7-pub.mail.unifiedlayer.com (oproxy7-pub.mail.unifiedlayer.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id E8AD711E80D2 for <ccamp@ietf.org>; Fri, 23 Aug 2013 08:22:05 -0700 (PDT)
Received: (qmail 31308 invoked by uid 0); 23 Aug 2013 15:21:42 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy7.mail.unifiedlayer.com with SMTP; 23 Aug 2013 15:21:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=eRGjtaosVy6AUTd8UTeoDsbyrQRrsreMNl5ZOA44G+4=; b=mgsHxO2V/0XX5pXxw+4nVSjhoBnpCtl6s3GpM1/cMCwR7fsD2SKXPR7Qw8dBSwzX3sRcnUmsTUvFkYEfkw1HNfkw+AKeHCCCCKfG0t1aL9U8Srv5v7mdsFuQBj7YjCvK;
Received: from box313.bluehost.com ([69.89.31.113]:54219 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1VCtBG-0000AN-FB; Fri, 23 Aug 2013 09:21:42 -0600
Message-ID: <52177E05.3040509@labn.net>
Date: Fri, 23 Aug 2013 11:21:41 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: adrian@olddog.co.uk
References: <00a501ce9e5d$017b7ba0$047272e0$@olddog.co.uk> <52153E45.1030505@labn.net> <025701ce9f5c$185bcc80$4001a8c0@gateway.2wire.net> <521765CC.4030306@labn.net> <045f01cea00b$573700f0$05a502d0$@olddog.co.uk>
In-Reply-To: <045f01cea00b$573700f0$05a502d0$@olddog.co.uk>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: draft-ietf-ccamp-swcaps-update.all@tools.ietf.org, ccamp@ietf.org
Subject: Re: [CCAMP] AD review of draft-ietf-ccamp-swcaps-update
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 15:22:11 -0000

On 08/23/2013 10:16 AM, Adrian Farrel wrote:
> Really good catch, Tom.
> 
> What Lou suggests looks the best way to handle it.
> 

Great.  Look for the publication announcement in a few minutes.

Lou

> A
> 
>> -----Original Message-----
>> From: Lou Berger [mailto:lberger@labn.net]
>> Sent: 23 August 2013 14:38
>> To: t.petch; adrian@olddog.co.uk
>> Cc: draft-ietf-ccamp-swcaps-update.all@tools.ietf.org; ccamp@ietf.org
>> Subject: Re: [CCAMP] AD review of draft-ietf-ccamp-swcaps-update
>>
>> Tom,
>> 	See below.
>>
>> ...
>>
>>>> On 8/21/2013 6:55 AM, Adrian Farrel wrote:
>> ...
>>
>>>>>
>>>>> Please add a note to the IANA considerations section to request an
>>>>> update to
>>>>>
>>> https://www.iana.org/assignments/ianagmplstc-mib/ianagmplstc-mib.xhtml
>>>>>
>>>>> Possibly you should refer to it as IANA-GMPLS-TC-MIB rather than
>>> through
>>>>> the URL.
>>>> The proposed text to be added to the end of the section is:
>>>>
>>>>    A parallel change to IANA-GMPLS-TC-MIB is also required. In
>>>>    particular, under IANAGmplsSwitchingTypeTC a reference to this
>>>>    document should be added as item 3. Also the following changes
>>> should
>>>>    be made to the related values:
>>>>
>>>>           deprecated(2),      -- Deprecated
>>>>           deprecated(3),      -- Deprecated
>>>>           deprecated(4),      -- Deprecated
>>>
>>> Mmmmm RFC4181 says
>>>
>>> "Therefore, labels of named numbers and named
>>>   bits MUST NOT be changed when revising IETF MIB modules (except to
>>>   correct typographical errors), and they SHOULD NOT be changed when
>>>   revising enterprise MIB modules.
>>> "
>>>
>>> so I do not think that you can do that.  Change of STATUS (which applies
>>> to the whole TC) yes, label no. (Don't you love SNMP?)
>>>
>>> Tom Petch
>>>
>>
>> Looks like you're right.
>>
>> Perhaps the following is the "right" middle ground:
>> Existing:
>>                   psc2(2),      -- Packet-Switch-Capable 2
>>                   psc3(3),      -- Packet-Switch-Capable 3
>>                   psc4(4),      -- Packet-Switch-Capable 4
>> Revised:
>>                   psc2(2),      -- Deprecated [This.document]
>>                   psc3(3),      -- Deprecated [This.document]
>>                   psc4(4),      -- Deprecated [This.document]
>>
>> Adrian,
>>
>> Do you agree with the above?  This is a bit different than your request.
>>
>> Much thanks,
>> Lou
> 
>