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 "...@example.com" 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
Syslog-sec@www....
http://www.employees.org/mailman/listinfo/syslog-sec