Re: [Netconf] What to check in cndidate config?

Martin Bjorklund <mbj@tail-f.com> Mon, 16 September 2013 08:30 UTC

Date: Mon, 16 Sep 2013 10:19:01 +0200
Message-Id: <20130916.101901.1139180237571657090.mbj@tail-f.com>
To: balazs.lengyel@ericsson.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <5236BDC6.3050006@ericsson.com>
References: <5236BDC6.3050006@ericsson.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: netconf@ietf.org
Subject: Re: [Netconf] What to check in cndidate config?
Precedence: list

Hi,

Balazs Lengyel <balazs.lengyel@ericsson.com> wrote:
> Hello,
> When editing a candidate config some model constraints may be violated
> temporarily. E.g. mandatory leafs might be added in a later separate
> edit-config. However some constraints are probably checked
> immediately, e.g. the string "XYZ" is not accepted if a leaf's type is
> int32.
> Is there somewhere a list describing which type of checks should or
> should not be checked at edit-config to the candidate, and which
> should only be checked at a validate or commit operation. Ideally this
> list of constraints/checks should be part of the YANG RFC.

See Section 8.3 in RFC 6020.


/martin

[Netconf] What to check in cndidate config? Balazs Lengyel
Re: [Netconf] What to check in cndidate config? Martin Bjorklund