Re: merge/replace selection criteria

["Randy Presuhn" <randy_presuhn@mindspring.com>]

Hi -

> From: "Andy Bierman" <abierman@cisco.com>
> To: "Phil Shafer" <phil@juniper.net>
> Cc: "Glenn Waters" <gww@nortelnetworks.com>; "Paul Sangree" <psangree@cisco.com>; <netconf@ops.ietf.org>
> Sent: Tuesday, August 26, 2003 9:03 AM
>Subject: Re: merge/replace selection criteria
...
> what about the <unique> or <key> elements?
>
> In any case, I think this is a data definition issue which is
> outside our charter.  We just need to identify the requirement
> that data naming be done in a consistent manner which allows
> for non-ambiguous identification within our protocol operations.
...

If we require that naming be done "in a consistent manner" but
don't say what that "consistent manner" is, how will we ever attain
interoperability?

Randy



--
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/>