[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Time to Revise the TC list
Not having heard much more on the below emails, I have now
updated http://www.ops.ietf.org/mib-common-tcs.html
with the following additional TCs.:
The following TCs are defined in ITU-ALARM-TC-MIB [RFC3877]:
ItuPerceivedSeverity enumerated INTEGER
ItuTrendIndication enumerated INTEGER
The following TCs are defined in ENTITY-STATE-TC-MIB [RFC4268]
EntityAdminState enumerated INTEGER
EntityOperState enumerated INTEGER
EntityUsageState enumerated INTEGER
EntityAlarmStatus BITS
EntityStandbyStatus enumerated INTEGER
The following TCs are defined in Q-BRIDGE-MIB [RFC4363]:
VlanId Integer32 (1..4094)
VlanIdOrAny Integer32 (1..4094 | 4095)
VlanIdOrNone Integer32 (0 | 1..4094 | 4095)
Bert
> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: Friday, April 28, 2006 09:59
> To: Wijnen, Bert (Bert); Mreview (E-mail); ietfmibs@ops.ietf.org
> Subject: RE: Time to Revise the TC list
>
>
>
> Yes, I believe that
>
> VlanIdOrAny,
> VlanIdOrNone, and
> VlanIdOrAnyOrNone
>
> from Q-BRIDGE-MIB in RFC 4363 would be useful additions.
>
> Dan
>
>
>
>
> > -----Original Message-----
> > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> > Sent: Friday, April 28, 2006 12:28 AM
> > To: Romascanu, Dan (Dan); Mreview (E-mail); ietfmibs@ops.ietf.org
> > Subject: RE: Time to Revise the TC list
> >
> > Did we not do something fro VlanID and VlanIDOrNone and some
> > such as well, These can also be of generic use I think.
> >
>
>
> -----Original Message-----
> From: owner-mreview@ops.ietf.org [mailto:owner-mreview@ops.ietf.org]On
> Behalf Of Romascanu, Dan (Dan)
> Sent: Tuesday, April 25, 2006 18:08
> To: Mreview (E-mail); ietfmibs@ops.ietf.org
> Subject: Time to Revise the TC list
>
>
>
> Appendix B in "Guidelines for Authors and Reviewers of MIB Documents
> [RFC4181, BCP111]", lists an initial set of Commonly used Textual
> Conventions. The http://www.ops.ietf.org/mib-common-tcs.html
> web page is
> intended to keep that list up-to-date with the most commonly
> used TCs.
>
> I believe that it's time to update and revise this page.
>
> My opinion is that we could add here the TCs defined in RFC 4268 and
> those defined in ITU-ALARM-TC-MIB in RFC 3877.
>
> Please let Bert and myself know if there are more additions or changes
> made here.
>
> Thanks and Regards,
>
> Dan