In general, the "@example.company.com" name space is a nice idea.
However, I am concerned about the length that this introduces.  I would
much prefer to have a more compact encoding, resembling what parameters
would look like in SDP more than what they would look like XML (in terms
of compactness).  This is one reason why I actually like the proposal to
use the company identifier (typically 3 digits) as prefix (followed by
some delimiter) as was suggested to denote a private name space.

Just my 2 cents.
--- Alex

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris
Lonvick (clonvick)
Sent: Monday, October 03, 2005 6:25 PM
To: David B Harrington
Cc: [email protected]
Subject: RE: [Syslog-sec] AD Review for draft-ietf-syslog-protocol-14

Hi David,

On Fri, 30 Sep 2005, David B Harrington wrote:

> Hi,
>
> Because I believe we should be working to integrate our network 
> management standards, at least to the point they can secure and 
> correlate data easily across NM interfaces, I would like to see the 
> approach adopted by syslog to be similar to the approaches used by 
> other IETF protocols, especially network management protocols.

I'd like that as well.

>
> SNMP uses the vendor ID approach, managed by IANA.
> Netconf has no data model, so we don't know what they will use for 
> vendor extensions.
> I'm not sure what ipfix is using.
>
> Who will manage the @cisco.com registrations? IANA or another external

> agency? Will the assignments be as stable as IANA assignments?

The "[EMAIL PROTECTED]" namespace for SSH is for private use and will not
be registered with anyone.  It's been working well enough for the SSH
community with the warning of, "It is up to each domain how it manages
its local namespace."  I will say that this practice in SSH is not as
widespread as SNMP but it has been done and it seems to be working.

It would be good to have discussion of this on the mailing list and we
can hopefully finalize what we want in Vancouver.  Your input would be
appreciated.

Thanks,
Chris
_______________________________________________
Syslog-sec mailing list
[email protected]
http://www.employees.org/mailman/listinfo/syslog-sec
_______________________________________________
Syslog-sec mailing list
[email protected]
http://www.employees.org/mailman/listinfo/syslog-sec

Reply via email to