[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Enumerations in draft-ietf-ccamp-gmpls-te-mib-08.txt
We'll look at how to do this.
----- Original Message -----
From: "Tom Petch" <firstname.lastname@example.org>
To: "Adrian Farrel" <email@example.com>; <firstname.lastname@example.org>
Sent: Friday, March 18, 2005 8:29 AM
Subject: Enumerations in draft-ietf-ccamp-gmpls-te-mib-08.txt
> This MIB contains several 'enumerations' except they are not
> text in
> DESCRIPTION clauses - gmplsTunnelGPid gmplsTunnelSwitchingType
> gmplsTunnelLSPEncoding - with RFC 3471 (not a MIB) as a reference. So
> not defined anywhere in SMI; and as this points out, these values will
> to in future RFC.
> I think these should be in a MIB under IANA control and there is already
> to do just that, namely to put them in an IANA MIB (as opposed to a
> track MIB) with the RFC specifying under what conditions the IANA MIB
> updated (standards track, IESG, expert etc).
> This procedure is described in
> also points to previous examples of this. And this issue has already
> albeit obliquely, on this list once before in the context of
> IANAItuProbableCause which uses this procedure and is now published as
> the Alarm MIB (RFC 3877).
> Not to do this now creates extra work in the future; when an implementor
> create their own SMI and whenever these values need to be updated.
> Tom Petch