Re: [YANG] relation to XML PDUs

Andy Bierman <ietf@andybierman.com> Mon, 21 January 2008 16:21 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 1JGzOl-0006jC-Ry; Mon, 21 Jan 2008 11:21:23 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JGzOl-0006al-2P for yang-confirm+ok@megatron.ietf.org; Mon, 21 Jan 2008 11:21:23 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JGzOk-0006RG-B3 for yang@ietf.org; Mon, 21 Jan 2008 11:21:22 -0500
Received: from smtp119.sbc.mail.sp1.yahoo.com ([69.147.64.92]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1JGzOj-0004Z2-QC for yang@ietf.org; Mon, 21 Jan 2008 11:21:22 -0500
Received: (qmail 27234 invoked from network); 21 Jan 2008 16:21:20 -0000
Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@67.126.240.103 with plain) by smtp119.sbc.mail.sp1.yahoo.com with SMTP; 21 Jan 2008 16:21:20 -0000
X-YMail-OSG: aJCydvQVM1kes14NOxjeZdN.UVS8e8rtFkDjtKTfi4if.GgNmOLZTlxtu1pui3FcnRwFojRzLtmUTcFX7a5AKYR8
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4794C67F.1000303@andybierman.com>
Date: Mon, 21 Jan 2008 08:21:19 -0800
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Martin Bjorklund <mbj@tail-f.com>
Subject: Re: [YANG] relation to XML PDUs
References: <1200921746.6914.176.camel@missotis> <20080121.145054.158522565.mbj@tail-f.com>
In-Reply-To: <20080121.145054.158522565.mbj@tail-f.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: yang@ietf.org, lhotka@cesnet.cz
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

Martin Bjorklund wrote:
> Ladislav Lhotka <lhotka@cesnet.cz> wrote:
>> Hi,
>>
>> I understand that YANG data models describe entire configuration
>> datasets, but do they also pose any restrictions to the NETCONF XML
>> PDUs? For example: the order of children in a YANG model is fixed - does
>> it mean that the corresponding XML elements in PDUs must appear in the
>> same order?
> 
> Currently we do this, mainly b/c of the requirement to be XSD
> compatible, i.e. we want to be able to generate an XSD which can be
> used to validate the PDUs.
> 


Really?  Where is that documented?

Let's review the NETCONF PDUs so we can stop talking about
schema validation in high altitude abstractions.  I don't care about
abstract requirements, I care about running code.

There are 3 types of parameters for RPC operations:

  1) XML represents RPC parameter abstractions (e.g., error-option)
     XSD can validate these RPCs fine.

  2) XML represents subtree filter parameters
     XSD cannot do anything with this.  There are no requirements
     except well formed XML.  Unknown namespaces and elements
     are just 'no-match' conditions, not errors.

  3) XML represents config database fragment
     XSD cannot do much with this unless minOccurs=0 is set for
     every element and the NETCONF operation attribute is added
     everywhere it is allowed.  I have never seen an XSD that
     actually does this.  Instead they all model the config-database
     representation, not any particular PDU.


The <edit-config> and <copy-config> operations allow arbitrary subsets of
config data to be sent in a given PDU, with an almost infinite
number of permutations. A subset of those permutations will
actually be valid for a given data model.   Since YANG models
the data, not the XML, the number of 'extra' permutations in
a YANG schema can be reduced to almost zero.


Andy






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



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