RE: Looking for a TEXTUAL-CONVENTION to reference

["Eduardo Cardona" <e.cardona@CableLabs.com>]

Bert, 

Just check RFC 3231 as you suggested, the object Types defined in the
rFC was in general what I was looking for, but rather than replicating
same sort of  OBJECT-TYPEs, I was looking for straigth TCs. 

Also some extra TC in enumeration forms (rather than BITS) could be
defined in parallel for convenience where the cases may not merit having
BITS.

What I've seen could be better is having the Disman group normalize the
diverse OBJECT-TYPEs to TCs so others like the AToMMIB group and others
can use.


Thanks, 

Eduardo

Will propose something later to disman Group 




 






-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
Sent: Tuesday, November 04, 2003 1:52 PM
To: Eduardo Cardona
Cc: mibs@ops.ietf.org
Subject: RE: Looking for a TEXTUAL-CONVENTION to reference


Some discussion on "day Counter" is just taking place on atommib WG. Not
that it helps much I suspect... but you may want to chime in.

Did you also take a look at the Scheduling related objects in RFC3231?
Not sure that is what you are looking for...  Maybe you should explain
what you want to achieve.

Thanks,
Bert 

> -----Original Message-----
> From: Eduardo Cardona [mailto:e.cardona@CableLabs.com]
> Sent: maandag 3 november 2003 22:02
> To: mibs@ops.ietf.org
> Subject: Looking for a TEXTUAL-CONVENTION to reference
> 
> 
> 
> Good Afternoon,
> 
> I am posting to the OPS group unsure if would be better use
> tht AToMMIB
> or RMON group, 
> 
> I am looking for a TC to represent only the time of day instead of the

> full DateAndTime from RFC 2579 I've seen a draft (below) that does 
> that, but I could not find any formal RFC pointing to that or if 
> redefined elsewhere.
> 
> Was that defined in any other group/ MIB or a reason for not consider 
> that?
> 
> 
> 
> Thanks
> 
> Eduardo
> 
> 
> From  draft-kchapman-perfhist-sup-TC-00.txt
> 
> 
> HourOfDay ::= TEXTUAL-CONVENTION
>     DISPLAY-HINT "1d1a1d:1d"
>     STATUS       current
>     DESCRIPTION
>        "A time-of-day specification at an hour boundary.  This is used
>         to specify an event that is to occure at precisely
> the same time
>         each day, on the hour; for example, the time to save an
>         interface's current 1-day counter as the previous 
> 1-day counter
>         and reset the current 1-day counter to zero.
> 
>              octet  contents                  range
>              -----  --------                  -----
>                1    hour                      0..23
>                2    direction from UTC        '+' | '-'
>                3    hours from UTC            0..11
>                4    minutes from UTC          0..59
> 
>         For example, 1 PM EDT would be displayed as:
> 
>              13-4:0
> 
>         Note that if only local time is known, then timezone
> information
>         (octes 2-4) is not present."
>     SYNTAX       OCTET STRING (SIZE (1 | 4))
>