Trying to post this - attempt 2.

Tom Petch

----- Original Message -----
From: "Tom Petch" <[EMAIL PROTECTED]>
To: "Sharon Chisholm" <[EMAIL PROTECTED]>
Sent: Thursday, April 07, 2005 3:16 PM
Subject: Re: [Syslog-sec] Detailed Review Comments on Syslog Protocol -09 - Part
III


> <inline>
> Tom Petch
>
> ----- Original Message -----
> From: "Sharon Chisholm" <[EMAIL PROTECTED]>
> To: <syslog-sec@employees.org>
> Sent: Friday, March 18, 2005 9:40 PM
> Subject: RE: [Syslog-sec] Detailed Review Comments on Syslog Protocol -09 -
Part
> III
>
> ><snip>
> > As far as sysUptime is concerned, I think we should stick with the SNMP
> > definition of the number of milliseconds since boot, with a max value of
> > 4294967295 and automatic reset to zero thereafter. Is this understanding
> > correct?
> >
> I think not;  [RFC 3418] defines sysUpTime as having a SYNTAX of TimeTicks and
> [RFC 2578] defines TimeTicks as
>   "...represents a non-negative integer which represents
>    the time, modulo 2^32 (4294967296 decimal), in hundredths of a second
>    between two epochs."
>
> <snip>
> > If Enterprise is equal to ACME and ACME makes two products: 1) rocket
> > powered roller blades and 2) electronic roadrunner traps, is this field
> > identifying 'acme' in both cases or is it acme.rocket or acme.trap depending
> > on the product? Keep in mind that both products run some of the same
> > software and some software unique to their own unique applications.>
>
> In SNMP, I usually see Enterprise ID followed by several other sub-identifiers
> which identify the (router) model, level of software etc as in
> 1.3.6.1.4.1.company.model.software etc etc
> There is really little constraint on how detailed an enterprise makes its
branch
> and many go to town.  Nice - as long as I can find the details somewhere on
the
> company website - but probably too long to include here.
> <snip>
>

_______________________________________________
Syslog-sec mailing list
Syslog-sec@www.employees.org
http://www.employees.org/mailman/listinfo/syslog-sec

Reply via email to