Re: MIB Dr. review for draft-ietf-ccamp-gmpls-lsr-mib-13.txt

"Thomas D. Nadeau" <tnadeau@cisco.com> Thu, 27 April 2006 14:58 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZ7wn-0006XO-Dd for ccamp-archive@ietf.org; Thu, 27 Apr 2006 10:58:25 -0400
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZ7wn-0001hp-0l for ccamp-archive@ietf.org; Thu, 27 Apr 2006 10:58:25 -0400
Received: from majordom by psg.com with local (Exim 4.60 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1FZ7op-0009EV-Ab for ccamp-data@psg.com; Thu, 27 Apr 2006 14:50:11 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00, DNS_FROM_RFC_ABUSE,SPF_PASS autolearn=no version=3.1.1
Received: from [64.102.122.148] (helo=rtp-iport-1.cisco.com) by psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from <tnadeau@cisco.com>) id 1FZ7om-0009EE-Us for ccamp@ops.ietf.org; Thu, 27 Apr 2006 14:50:09 +0000
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 27 Apr 2006 07:50:08 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.04,161,1144047600"; d="scan'208"; a="26820685:sNHT25299280"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k3REo7vF025887; Thu, 27 Apr 2006 10:50:07 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 27 Apr 2006 10:50:07 -0400
Received: from [10.83.15.51] ([10.83.15.51]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 27 Apr 2006 10:50:07 -0400
In-Reply-To: <02e901c66994$282dbc00$0500a8c0@jlucianilaptop>
References: <001901c664db$2e1ff6e0$0500a8c0@jlucianilaptop> <6968853B-77E3-4A7C-A5EC-1655C05EA5B0@cisco.com> <02e901c66994$282dbc00$0500a8c0@jlucianilaptop>
Mime-Version: 1.0 (Apple Message framework v749.3)
X-Priority: 3
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <EBBC9031-D6AA-4690-AFD0-E16EC1C0B145@cisco.com>
Cc: Adrian Farrel <adrian@olddog.co.uk>, ccamp@ops.ietf.org, bwijnen@lucent.com, dromasca@avaya.com, kireeti@juniper.net
Content-Transfer-Encoding: 7bit
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: Re: MIB Dr. review for draft-ietf-ccamp-gmpls-lsr-mib-13.txt
Date: Thu, 27 Apr 2006 10:50:19 -0400
To: "<jcucchiara@mindspring.com>" <jcucchiara@mindspring.com>
X-Mailer: Apple Mail (2.749.3)
X-OriginalArrivalTime: 27 Apr 2006 14:50:07.0309 (UTC) FILETIME=[E010DFD0:01C66A09]
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8

	One question below.

> Hello Tom and Adrian,
>
>
> All MIBs compile with smilint and smicngPRO.
>
> Here are my few comments:
>
> draft-ietf-ccamp-gmpls-lsr-mib-13.txt
>
> (#1 should be taken care of the others are NITs and
> could probably be fixed by RFC Editor if you so choose.)
>
> 1)  Think this was probably a place holder...but
> please just remove this:
>
>      OBJECT       gmplsLabelRowStatus
>      SYNTAX       RowStatus { active(1), notInService(2) }
>      WRITE-SYNTAX RowStatus { active(1), notInService(2),
>                               createAndGo(4), destroy(6) }
>      DESCRIPTION
>        "TDN QUestion"

	Thanks for catching this. I remember why I left this.
I was confused by your comments on this, which were:
>>>> 9) Full Compliance:
>>>>
>>>>      OBJECT       gmplsLabelRowStatus
>>>>      SYNTAX       RowStatus { active(1), notInService(2) }
>>>>      WRITE-SYNTAX RowStatus { active(1), notInService(2),
>>>>                               createAndGo(4), destroy(6) }
>>>>      DESCRIPTION
>>>>        "Support for createAndWait and notReady is not required."
>>>>
>>>>
>>>> Would remove this.
>>>>
>>>
>>> The description or the entire object?
>>>
>>
>> Presumably the Description limitation based on the text below.
>>
>>
>>>> Based on the
>>>> gmplsLabelRowStatus object's DESCRIPTION
>>>> believe you should allow createAndWait and also
>>>> Agent could/should be able to report notReady.

	Based on what is listed in RFC3813, for example,
we have the following:

    OBJECT       mplsInSegmentRowStatus
    SYNTAX       RowStatus { active(1), notInService(2) }
    WRITE-SYNTAX RowStatus { active(1), notInService(2),
                             createAndGo(4), destroy(6)
                           }
    DESCRIPTION "Support for createAndWait and notReady is
                 not required."

	I guess I am looking for some explicit instruction on
what you would like to see in the DESCRIPTION for the
gmplsLabelRowStatus in the FullCompliance statement.

> 2) NIT
>
>          January 2003;
>         "
>
> Please change this to:
>
>
>             January 2003."
>
>
> 3) Informative References
>
> NIT:
>
> Change the order so references are in
> ascending order:
>
> Current order is:
>
>    [RFC3472]
>
>
>    [RFC3468]
>
> change to:
>
>    [RFC3468]
>
>    [RFC3472]
>
>
> NIT:
> Fix reference:
>
> Current:
>    [RFC3468]    Andersson, L., Swallow, G., "The Multiprotocol Label
>                 Switching (MPLS) Working Group decision on MPLS
>                 signaling protocols", RFC 3468, February 2003.
>
> Should be:
>
>    [RFC3468]    Andersson, L. and G. Swallow, "The Multiprotocol Label
>
>
> -- end --

	OK, fixed the above nits.

	--Tom