Re: [netmod] tree diagrams - flags

Martin Bjorklund writes: > Aha, ok. This description is not a correct description of the YANG > data tree (in which XPath expressions etc are evaluated). There is > not a single "list node" called "interfaces". Look at an example of ^ I'm

Re: [netmod] uses and augment

ut any XPath context. See also > section 6.5 OK, "context node" isn't the right term, but the idea still applies -- if the schema node identifier is descendant, the starting point for reckoning the descending path has to be specified. Juergen Schoenwaelder <j.schoenwael...@jacobs-u

Re: [netmod] Interaction of 'when' and 'default' statements

Martin Bjorklund writes: > William Ivory wrote: >> Thanks. Can you point me at the part of RFC 6020 that explicitly >> states that 'when' wins over 'default'? > > Section 7.6.1 of RFC 7950 says: > >Note that if the leaf or any of its ancestors has a

[netmod] uses and augment

I've got a couple of questions about the interaction of "uses" and "augment". I hope that these have straightforward answers that the old hands can tell me easily enough. 1. Augmenting a grouping I notice that "augment" is not allowed to target a "grouping", despite that naively seems to be an

Re: [netmod] tree diagrams - flags

Martin Bjorklund writes: > Hmm, "*" was choosen b/c people are used to read it as > "zero or more". So for example: > > +---c server* [name] > +--c name string > ... > > means zero or more "server" elements. Each indexed by "name". >From RFC

Re: [netmod] augment and if-feature

Robert Wilton writes: > To quote Joey's example, I think that both of the following modules are > valid (presuming that they are both implemented by a device) regardless > of which features are enabled. Do you agree? > > module base-module { >prefix bmod; > >feature

Re: [netmod] augment and if-feature

Robert Wilton writes: > It isn't just any if-feature on the container that is being augmented > that needs to be considered. You would have to consider all if-feature > statements by walking up the augmented node's ancestors to the top of > the tree and combine them, or

Re: [netmod] augment and if-feature

JOEY BOYD writes: > module base-module { > prefix bmod; > > feature do-things; > > container things { > if-feature do-things; > ... > } > } > > module augment-module { > prefix amod; > > augment "/bmod:do-things" { > container other-things { > } >

Re: [netmod] WG Last Call for draft-ietf-netmod-syslog-model-11

"Clyde Wildes (cwildes)" writes: > Thanks for the simplification. I have incorporated this in the next > draft-ietf-netmod-syslog-model revision. Ah, thanks! Looking at -13, I see this: A syslog message is processed if: There is an element of facility-list (F, S)

Re: [netmod] WG Last Call for draft-ietf-netmod-syslog-model-11

(We seem to be well beyond the original LC date, but this is only an editorial comment...) The algorithm in section 3 isn't clear to me (possibly because I'm not very familiar with syslog in practice): Selector processing (input is syslog message): 1. Loop through facility-list

Re: [netmod] How to constrain a leaf to a read-only list of supported values?

Andy Bierman writes: > Back before there was YANG 1.0 I proposed the concept of constants in YANG > but this was seen as too complicated. This is the exact use-case I had in > mind. > The YANG module would #define the constants (maybe with a default or no > value) > and they

Re: [netmod] How to constrain a leaf to a read-only list of supported values?

Ladislav Lhotka writes: >> typedef Compression-Method { >> ... >> } >> >> list node { >> config true; >> key name; >> >> string name; >> >> leaf-list supported-compression-methods { >> type Compression-Method; >> config false; >> } >> >> Compression-Method

Re: [netmod] Using an empty type in a list key

Andy Bierman writes: > Using a key of type empty is utterly pointless unless the point > is to make the instance identifier longer. IMO using a key of type empty (or any type with only one value) is *pointless* but should be *valid*. Things should be valid unless processing

Re: [netmod] How to constrain a leaf to a read-only list of supported values?

Balazs Lengyel writes: > Problem: how do you restrict values for (3) - file-compression so that > it is one of the nodes-supported-compression-types. The natural solution > would be to use a must expression or a leaf-ref, but as > nodes-supported-compression-types

Re: [netmod] RFC 6087bis guidance re use of revision statements in drafts

Andy Bierman writes: > An Internet-Draft is NOT a means of "publishing" a specification; As I said, that's the theory, but practice is considerably different. Dale ___ netmod mailing list netmod@ietf.org

Re: [netmod] RFC 6087bis guidance re use of revision statements in drafts

William Lupton writes: > Regardless of the discussion about “published”, other organisations > may be planning to use YANG modules that are currently within > IDs. Obviously it’s vastly preferable if such IDs become RFCs before > these other organisations publish any

Re: [netmod] YANG 1.1: XML naming restriction

William Lupton writes: > But the errata at https://www.w3.org/XML/xml-V10-5e-errata > say the following. There > are also related changes to Section 2.6 (processing instructions) and > Section 3 (logical structures). >>

Re: [netmod] YANG 1.1: XML naming restriction

Andy Bierman writes: > The YANG 1.1 ABNF says: > >;; An identifier MUST NOT start with (('X'|'x') ('M'|'m') ('L'|'l')) >identifier = (ALPHA / "_") > *(ALPHA / DIGIT / "_" / "-" / ".") > > > There is no explanation given why. > The same

Re: [netmod] grouping if-feature

Martin Bjorklund writes: > Michal Vasko wrote: >> in NETCONF server draft [1] there is ietf-ssh-server model. It defines >> feature "ssh-x509-certs" and then uses it twice in a >> grouping. Referring to RFC 6020 [2] (I haven't noticed any difference >> in the

Re: [netmod] Request to review the YANG compiler annotations draft.

Martin Bjorklund writes: > "vinods.kumar" wrote: >> We have written a draft, to add annotation in YANG definition which can >> be used by the YANG compilers. > > 1) What you propose is not valid YANG. This new syntax would > require a new

Re: [netmod] Must on actions without input or output parameters

Balazs Lengyel writes: [edited] > container myThing { > leaf enabled { type boolean;} > action start { >input { > // optional so I can just ignore it > leaf dummy-leaf-never-use-it { type empty; } > must "../enabled =

Re: [netmod] list keys out of order

Andy Bierman writes: > Where does is say the server MUST reject list keys provided by the client > that are out of order? Where does is say what error-tag is returned? Maybe this is due to my inexperience, but I read the text of 7.8.4, "A list is encoded ..." as "When

Re: [netmod] Must on actions without input or output parameters

Balazs Lengyel writes: > We only want to allow starting myThing (calling the start action) if > it is enabled. > However we > - can not put a must under action according to the RFC/draft > - while the RFC would allow us to put an empty input under action with > only

Re: [netmod] Tokenizing and strings (was: Gen-ART IETF Last Call review of draft-ietf-netmod-rfc6020bis-12 (part 2))

Juergen Schoenwaelder writes: > I think we should consider this for a future version of YANG but not > now. I am not aware what implementors had problems to implement YANG > strings in YANG 1 or YANG 1.1 and we are at a point in the process > where I like to

[netmod] The Restconf root

Looking at draft-ietf-netconf-restconf-13, it looks like the RFC 7320 mechanism is used to find the root URL, from which all the Restconf URLs are derived by appending path components as specified in the draft. But looking at RFC 6570, which is referenced by both 7320 and the draft, it seems like

Re: [netmod] update on "rdns" URN for enterprise YANG models

When I see a requirement for globally unique names, I always think fondly of the "oid" series of URNs, which are based on the ITU object identifiers. See RFC 3001. You write to IANA to get an assignment of a "private enterprise number", which you can use to coin object identifiers which are

Re: [netmod] Tokenizing and strings

"Jernej Tuljak" writes: > You are also forgetting the fact that the existing 'string' production > expects an "unquoted string as returned by the scanner" (no quotes, > no concats, no pretty printing whitespace). I must admit I've never understood what that bit of the

[netmod] Tokenizing and strings (was: Gen-ART IETF Last Call review of draft-ietf-netmod-rfc6020bis-12 (part 2))

At this point, I think there are some aspects of the use of strings and identifiers that aren't completely specified, but I'd have to check the current text to know for certain. However, that's a minor matter. The issue that concerns me is that the ABNF doesn't specify what is allowed as a

Re: [netmod] [Gen-art] Gen-ART IETF Last Call review of draft-ietf-netmod-rfc6020bis-12 (part 1)

Martin Bjorklund writes: > Do you have an suggestion for what to write? These kinds of > multi-line strings are almost always 'description' statements, > used for human consumption. It is not clear to me what the warning > would be. >> So you can't write an isolated CR in most

Re: [netmod] Replacing a YANG submodule with a module

Martin Bjorklund writes: >> If I understand Yang correctly, that error can't be fixed by revising >> the new module test to clone mod:util as test:util, because though the >> new grouping is semantically identical to the old grouping, it's still a >> change in its definition: > >

Re: [netmod] [Gen-art] Gen-ART IETF Last Call review of draft-ietf-netmod-rfc6020bis-12 (part 2)

From: Juergen Schoenwaelder > An unquoted string is any sequence of characters and does not > contain any space, tab, or newline characters, a single or double > quote character, a semicolon (";"), braces ("{" or "}"), or > comment sequences

Re: [netmod] [Gen-art] Gen-ART IETF Last Call review of draft-ietf-netmod-rfc6020bis-12 (part 1)

Martin Bjorklund writes: >> > > > > It is worth noting (either here or in 6.1.3) how line-breaks inside >> > > > > quoted strings are transcribed into the string's value. As now >> > > > > written, it seems that the line-break is transcribed identically to >> > > > > how it is

Re: [netmod] leafref value space and constraint

Martin Bjorklund writes: > The text for "path" already says: > > It takes as an argument a > string that MUST refer to a leaf or leaf-list node. Given what the text must mean, that's sufficient for me. Ladislav Lhotka writes: > Which of the two "foo" leaf

Re: [netmod] Replacing a YANG submodule with a module

William Lupton writes: > Consider the YANG module, submodule and tree files shown > below. Suppose that I regret the decision to make "submod" be a > submodule and want to replace it with a module (see listings further > down). This works, the tree file is identical,

Re: [netmod] leafref value space and constraint

Ladislav Lhotka <lho...@nic.cz> writes: > "Dale R. Worley" <wor...@ariadne.com> writes: >> A difficulty I have with the current wording is that it doesn't point >> out the crucial fact about leafref that the XPath expression can only >> select element

Re: [netmod] [Gen-art] Gen-ART IETF Last Call review of draft-ietf-netmod-rfc6020bis-12 (part 2)

(This is the second part of my response.) > > > > - section 6.1 > > > > > > > >This section details the rules for recognizing tokens from an input > > > >stream. > > > > > > > > Generally, language definitions intersperse the narrative text with > > > > the relevant grammar definitions.

Re: [netmod] [Gen-art] Gen-ART IETF Last Call review of draft-ietf-netmod-rfc6020bis-12 (part 1)

(This is the first part of my response, which I am sending seperately to speed things up.) Martin Bjorklund <m...@tail-f.com> wrote: > wor...@ariadne.com (Dale R. Worley) wrote: > > Martin Bjorklund <m...@tail-f.com> wrote on Mon, 23 May 2016 15:43:09 +0200 > > (CEST

Re: [netmod] leafref value space and constraint

A difficulty I have with the current wording is that it doesn't point out the crucial fact about leafref that the XPath expression can only select elements that are instantiations of one particular data node. I don't know XPath, but it seems that that is not a general property of XPath