RE: [Syslog-sec] Naming Style for SD-PARAMs

["Rainer Gerhards" <rgerhards@hq.adiscon.com>]

David,

I've been hesitant to put a specific recommendation in because we had so
many discussions about the paper being to precise. And if someone
implements -protocol but does not use consistent case for his SD-IDs
.... nothing is broken at all... 

Based on your suggestion, however, I think it would be worth putting a
note into the non-normative "implementors notes" appendix. 

What does the WG say?

Rainer 

> -----Original Message-----
> From: David B Harrington [mailto:ietfdbh@comcast.net] 
> Sent: Friday, January 14, 2005 10:37 PM
> To: Rainer Gerhards; 'Sharon Chisholm'; syslog-sec@employees.org
> Subject: RE: [Syslog-sec] Naming Style for SD-PARAMs
> 
> Hi,
> 
> The case-consistency was overlooked by the WG. It will be easy to
> overlook by others.
> I suggest we add a guideline to implementers suggesting the use of
> lower camel for consistency.
> 
> dbh 
> 
> > -----Original Message-----
> > From: syslog-sec-bounces@www.employees.org 
> > [mailto:syslog-sec-bounces@www.employees.org] On Behalf Of 
> > Rainer Gerhards
> > Sent: Friday, January 14, 2005 4:41 AM
> > To: Sharon Chisholm; syslog-sec@employees.org
> > Subject: RE: [Syslog-sec] Naming Style for SD-PARAMs
> > 
> > Sharon,
> > 
> > I agree to your comment. I will change it consistently to 
> > all-lowercase
> > in the draft, but I will not include any requirement to do 
> > so. Hopefully
> > the consistent lowercase will be guidiance enough to implementors ;)
> > 
> > Rainer 
> > 
> > > -----Original Message-----
> > > From: syslog-sec-bounces@www.employees.org 
> > > [mailto:syslog-sec-bounces@www.employees.org] On Behalf Of 
> > > Sharon Chisholm
> > > Sent: Tuesday, January 11, 2005 10:13 PM
> > > To: syslog-sec@employees.org
> > > Subject: [Syslog-sec] Naming Style for SD-PARAMs
> > > 
> > > hi
> > > 
> > > I was looking through version 8 of the protocol specification 
> > > to see what
> > > sort of naming style was being used for SD-PARAMs and it 
> > > seems all over the
> > > map. Should set a best practice and use it consistently 
> > throughout the
> > > document? I don't think we want an actual requirement though 
> > > as it would
> > > turn into a CLR (crappy little rule)
> > > 
> > > 1. Upper Camel
> > > 
> > > EventSource, EventID
> > > 
> > > 2. Lower Camel
> > > 
> > > enterpriseID
> > > 
> > > 3. all lower case
> > > 
> > > tzknown, issynced, issynced
> > > 
> > > 4. Hyphenated
> > > 
> > > sw-version
> > > 
> > > Sharon Chisholm
> > > Nortel Networks
> > > Ottawa, Ontario
> > > Canada
> > > _______________________________________________
> > > Syslog-sec mailing list
> > > Syslog-sec@www.employees.org
> > > http://www.employees.org/mailman/listinfo/syslog-sec
> > > 
> > _______________________________________________
> > Syslog-sec mailing list
> > Syslog-sec@www.employees.org
> > http://www.employees.org/mailman/listinfo/syslog-sec
> > 
> 
> 
> 
_______________________________________________
Syslog-sec mailing list
Syslog-sec@www.employees.org
http://www.employees.org/mailman/listinfo/syslog-sec