Re: IANA considerations update for NETCONF protocol draft

[Phil Shafer <phil@juniper.net>]

"Wijnen, Bert (Bert)" writes:
>But even then, how do you avoid conflicts between multiple enterprises,
>and how do you you which capability is from which enterprise?

The normal rules for XML namespaces should be used, where an URL
starts with an identifying domain name:

<hello>
  <capabilities>
    <capability>urn:ietf:params:xml:ns:netconf:base:1.0</capability>
    <capability>urn:ietf:params:xml:ns:netconf:capability:candidate:1.0</capability>
    <capability>urn:ietf:params:xml:ns:netconf:capability:confirmed-commit:1.0</capability>
    <capability>urn:ietf:params:xml:ns:netconf:capability:validate:1.0</capability>
    <capability>urn:ietf:params:xml:ns:netconf:capability:url:1.0?protocol=http,ftp,file</capability>
    <capability>http://xml.juniper.net/netconf/junos/1.0</capability>
  </capabilities>
  <session-id>36908</session-id>
</hello>

Thanks,
 Phil

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>