Re: Comments on draft-ietf-bfd-mib-02.txt

"Thomas D. Nadeau" <tnadeau@cisco.com> Mon, 08 August 2005 20:01 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E2Dol-0007Sk-4e; Mon, 08 Aug 2005 16:01:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E2Doj-0007OF-GZ for rtg-bfd@megatron.ietf.org; Mon, 08 Aug 2005 16:01:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15761 for <rtg-bfd@ietf.org>; Mon, 8 Aug 2005 16:01:47 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E2EMR-0002zG-Ik for rtg-bfd@ietf.org; Mon, 08 Aug 2005 16:36:43 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 08 Aug 2005 13:01:37 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.96,89,1122879600"; d="scan'208"; a="5152263:sNHT20703320"
Received: from [161.44.71.222] ([161.44.71.222]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j78K1XT6017130; Mon, 8 Aug 2005 16:01:33 -0400 (EDT)
In-Reply-To: <00a301c59c40$857e15c0$0601a8c0@pc6>
References: <27F4588E-E478-4A94-95EB-0624FC065657@juniper.net> <21A12C12-2C59-427B-857F-1846A1DF411B@cisco.com> <00a301c59c40$857e15c0$0601a8c0@pc6>
Mime-Version: 1.0 (Apple Message framework v733)
X-Priority: 3
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <68BD4818-1602-4FE6-AE1A-6AF1684D973A@cisco.com>
Content-Transfer-Encoding: 7bit
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Date: Mon, 08 Aug 2005 16:01:28 -0400
To: Tom Petch <nwnetworks@dial.pipex.com>
X-Mailer: Apple Mail (2.733)
X-PMX-Version: 4.7.1.128075
X-from-outside-Cisco: [161.44.71.222]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: rtg-bfd@ietf.org, Zafar Ali <zali@cisco.com>
Subject: Re: Comments on draft-ietf-bfd-mib-02.txt
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
Sender: rtg-bfd-bounces@ietf.org
Errors-To: rtg-bfd-bounces@ietf.org

     This is along the lines of what Katz was suggesting
earlier WRT updating the diag section. I like the IANA
control idea.

     --Tom

> Looking at BfdDiag Textual Convention, I wonder if there is a  
> better way of
> doing this.  I suspect that this is a list of diagnostic values  
> that will evolve
> faster than the rest of the MIB module so rather than updating the  
> RFC every
> time, or letting it get out of date, you could extract the Textual  
> Convention
> from the normative part of the MIB and put it under IANA control  
> with whatever
> rules you consider suitable for updating it.
>
> This approach has been sucessfully adopted by disman with Alarm MIB  
> (RFC3877
> s.5), inter alia.
>
> Tom Petch
>