[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: naming Textual Conventions

To: nwnetworks@dial.pipex.com
Subject: Re: naming Textual Conventions
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Date: Wed, 17 Apr 2002 16:42:28 +0200
Cc: mibs@ops.ietf.org
In-reply-to: <002501c1e5ec$d01d2ca0$0301a8c0@tom3> (nwnetworks@dial.pipex.com)
References: <002501c1e5ec$d01d2ca0$0301a8c0@tom3>


>>>>> Tom Petch writes:

Tom> TCs should have unique names - as stated in RFC2579 - but how is
Tom> that ensured?  

By human reviews and perhaps by running smilint on all IETF MIBs to
check for duplicate names. Not ideal, but the best we have.

Tom> I was surprised recently to find SnmpPduErrorStatus in the
Tom> Schedule MIB or FailureReason in the Event MIB?  I would never
Tom> have guessed such names would appear in those places from the
Tom> initial character string!

I am not sure why you are surprised. The names are unique (looking at
all IETF MIBs) as far as I can tell. ;-)

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>

References:
- naming Textual Conventions
  - From: "Tom Petch" <nwnetworks@dial.pipex.com>

Prev by Date: naming Textual Conventions
Next by Date: RE: naming Textual Conventions
Previous by thread: naming Textual Conventions
Next by thread: RE: naming Textual Conventions
Index(es):
- Date
- Thread