RE: Second Example in section 7.2 of netconf-proto

["Sharon Chisholm" <schishol@nortel.com>]

hi

Did we agree we were adding this clarifying text as a note to the RFC
editor?

Also, another clarifying question. If I have a record with a key and I
send it a replace command, are the non-key fields not included in the
replace snippet deleted or just not modified? I've seen one
implementations that does the latter, and I think based on the following
excerpt it is what is expected, but I wanted to confirm.

"Unlike a <copy-config> operation, which replaces
the entire target configuration, only the configuration
actually present in the config parameter is affected."

<bowler>
<name>Fred</name>
<location>Bedrock</location>
<status>single</status>
</bowler>

+

<bowler operation="replace">
<name>Fred</name>
<status>married</status>
</bowler>

=

<bowler>
<name>Fred</name>
<location>Bedrock</location>
<status>married</status>
</bowler>

Sharon

-----Original Message-----
From: Andy Bierman [mailto:ietf@andybierman.com] 
Sent: Thursday, March 09, 2006 9:50 AM
To: Chisholm, Sharon [CAR:ZZ00:EXCH]
Cc: Netconf (E-mail)
Subject: Re: Second Example in section 7.2 of netconf-proto


Sharon Chisholm wrote:
> hi
>
> In section 7.2, the second example indicates it will add an interface,

> but uses the operator of replace. The definition of replace does not 
> actually say that if the entry does not exist, it is created. Should 
> it, or should the operator of create be used instead in this example?
>
> I also wonder with these examples if there is an implicit assumption 
> that the key is name and this somehow defines whether something exists

> or not?
>
>   

How about some text that says:

"The manager must understand the data model being used.
In these examples, the manager knows a priori that the 'name' element is
used for instance identification to distinguish multiple instances of
the 'interface' element.


<clip>

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