Re: Comments on draft-ietf-bfd-mib-02.txt
"Tom Petch" <nwnetworks@dial.pipex.com> Mon, 08 August 2005 18:43 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E2CbJ-0007lB-Ej; Mon, 08 Aug 2005 14:43:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E2CbI-0007kq-6G for rtg-bfd@megatron.ietf.org; Mon, 08 Aug 2005 14:43:52 -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 OAA08494 for <rtg-bfd@ietf.org>; Mon, 8 Aug 2005 14:43:50 -0400 (EDT)
Received: from ranger.systems.pipex.net ([62.241.162.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E2D91-0008O7-MC for rtg-bfd@ietf.org; Mon, 08 Aug 2005 15:18:44 -0400
Received: from pc6 (1Cust172.tnt4.lnd4.gbr.da.uu.net [62.188.133.172]) by ranger.systems.pipex.net (Postfix) with SMTP id B5AF5E0001AB; Mon, 8 Aug 2005 19:43:30 +0100 (BST)
Message-ID: <00a301c59c40$857e15c0$0601a8c0@pc6>
From: Tom Petch <nwnetworks@dial.pipex.com>
To: "Thomas D. Nadeau" <tnadeau@cisco.com>
References: <27F4588E-E478-4A94-95EB-0624FC065657@juniper.net> <21A12C12-2C59-427B-857F-1846A1DF411B@cisco.com>
Date: Mon, 08 Aug 2005 15:40:56 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
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
Reply-To: Tom Petch <nwnetworks@dial.pipex.com>
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
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
- Comments on draft-ietf-bfd-mib-02.txt Dave Katz
- Re: Comments on draft-ietf-bfd-mib-02.txt Thomas D. Nadeau
- Re: Comments on draft-ietf-bfd-mib-02.txt Tom Petch
- Re: Comments on draft-ietf-bfd-mib-02.txt Thomas D. Nadeau