Re: [YANG] insert and key attributes

Andy Bierman <ietf@andybierman.com> Fri, 11 January 2008 23:00 UTC

Return-path: <yang-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JDSr8-0001g4-GV; Fri, 11 Jan 2008 18:00:06 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JDSr7-0001fz-OG for yang-confirm+ok@megatron.ietf.org; Fri, 11 Jan 2008 18:00:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JDSr7-0001fr-Ec for yang@ietf.org; Fri, 11 Jan 2008 18:00:05 -0500
Received: from smtp120.sbc.mail.sp1.yahoo.com ([69.147.64.93]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1JDSr7-0006nV-0b for yang@ietf.org; Fri, 11 Jan 2008 18:00:05 -0500
Received: (qmail 90849 invoked from network); 11 Jan 2008 23:00:04 -0000
Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@67.126.240.103 with plain) by smtp120.sbc.mail.sp1.yahoo.com with SMTP; 11 Jan 2008 23:00:04 -0000
X-YMail-OSG: jHKUUmEVM1kYRKdXWGy631M2KFi9J6qhI8S6Q.TZGewsIRf8
Message-ID: <4787F4F4.6000503@andybierman.com>
Date: Fri, 11 Jan 2008 15:00:04 -0800
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Phil Shafer <phil@juniper.net>
Subject: Re: [YANG] insert and key attributes
References: <200801112039.m0BKdNDl037488@idle.juniper.net>
In-Reply-To: <200801112039.m0BKdNDl037488@idle.juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: yang <yang@ietf.org>
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Errors-To: yang-bounces@ietf.org

Phil Shafer wrote:
> Andy Bierman writes:
>> 1) sec. 7.8.6 mentions the 'key' attribute (great, another
>>    overloaded term ;-) but this is not formally defined anywhere.
>>    The terse definition of the 'insert' attribute is not a formal
>>    definition either.
> 
> Yup, this needs some additional words.
> 
>>    In general, all the new requirements
>>    that YANG places on NETCONF agents is scattered throughout
>>    the document, and not entirely obvious.
> 
> What are you envisioning?  A section for NETCONF agent authors that
> don't want to read the entire document?
> 
>> 2) para 4 in 7.8.6 says if insert is missing, then it defaults
>>    to last.  Even in a list indexed by an integer.  This seems
>>    strange to me, to use an integral key and then ignore the actual
>>    base type, but I guess 'ordered-by-user' implies that the base type
>>    of the key has no meaning to the agent.
> 
> Exactly.  The key gives uniqueness but not order.
> 
>> 3) The last example in 7.8.7 is confusing.
>>    (There is a typo "to move a the new user 'barney'".)
>>    If 'barney' was already inserted after 'fred' (previous page)
>>    then the merge of 'barney' before 'fred' will fail in NETCONF.
>>    There is no move operation in NETCONF.  You cannot edit the
>>    value of a key.  The example would actually have no affect
>>    in NETCONF, since the <name> field was already set to 'barney'.
> 
> YANG uses "merge" w/ insert to move existing data, since not having
> a move operation is a bug.  Do we need to define our own
> "yang:operation='move'" to achieve this?
> 

I do not agree.
The WG did not want a move operation.
The set of operations is decided by consensus.
Whatever DML is used for NETCONF, it needs to work
with the protocol the way it is defined.

I think the DML should be separate from the protocol.
The YANG document should not be defining any protocol extensions or changes.


> Thanks,
>  Phil
> 
> 

Andy


_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang