I don't think this is joining an address with a prefix - this is joining an
address with a prefix *length*.
If it was two separate values, it would still be constraining the address to be
covered by the prefix, since there would be no way to define a prefix that the
address didn't cover.
Also
As I understand it,the only purpose for the candidate and startup datastores is
to indirectly set the contents of the running datastore.
Therefore it wouldn't make sense to have different factory defaults for the
running, startup and candidate datastores. And those are the only writable ones.
Support.
From: netmod on behalf of Kent Watsen
Sent: Tuesday, 26 March 2019 9:34 a.m.
To: netmod@ietf.org
Subject: [netmod] Adoption poll for draft-wu-netmod-factory-default-02
This email begins a 2-week adoption poll for:
In that case, why not make it so the tags are actually valid URIs, similar to
XML namespaces?
From: netmod on behalf of William Lupton
Sent: Friday, 8 March 2019 7:37 a.m.
To: Andy Bierman
Cc: Datatracker on behalf of Elwyn Davies; IETF discussion list;
Hi,
By my understanding both annotations should be included in one JSON object,
like this.
{
"example:interface" : [
{
"name" : "eth1",
"mtu" : 1500,
"@mtu" : {
"ietf-netconf-with-defaults:default" : true,
Does a percentage really need a single standard type in the first place? How
about "units percent;"?
From: netmod on behalf of Acee Lindem (acee)
Sent: Wednesday, 14 November 2018 5:03 a.m.
To: Juergen Schoenwaelder; Balázs Lengyel
Cc: NETMOD WG
Hi,
I was not at the IETF meeting unfortunately.
I see that the technical issues raised in the WGLC have been fixed, which is
good.
However I still have reservations about the utility of the proposed standard.
It seems to me like a solution in search of a problem, and I can't understand
why
.
From: Christian Hopps
Sent: Thursday, 18 October 2018 11:16 p.m.
To: Alex Campbell
Cc: Christian Hopps; joel jaeggli; NETMOD Working Group
Subject: EXTERNAL: Re: [netmod] WG LC draft-ietf-netmod-module-tags-02 -
10/2/18 - 10/16/18
A router has no use for it's capability/feature
../type = 'ipv4'"
Is that intentional? It seems more like an omission to me.
From: Andy Bierman
Sent: Thursday, 18 October 2018 10:54 a.m.
To: Alex Campbell
Cc: Michael Rehder; netmod@ietf.org
Subject: Re: [netmod] WHEN statement within mandatory objects does
e for my PC *on my
PC* instead of adding needless external dependencies.
Alex
From: Christian Hopps
Sent: Wednesday, 17 October 2018 9:56 p.m.
To: Alex Campbell
Cc: Christian Hopps; joel jaeggli; NETMOD Working Group
Subject: Re: [netmod] WG LC draf
> At the abstract level I do not understand how when-stmt would work
> differently.
> IMO deviation-stmt already allows enough flexibility to rewrite the model to
> fit the implementation.
FWIW: deviation statements cannot be used to modify when statements - "when" is
missing from the list of
ards, Alex
From: Christian Hopps
Sent: Wednesday, 17 October 2018 1:04 a.m.
To: Alex Campbell
Cc: Christian Hopps; joel jaeggli; NETMOD Working Group
Subject: Re: [netmod] WG LC draft-ietf-netmod-module-tags-02 - 10/2/18 -
10/16/18
>
> On Oct 3, 2018, at 8:22 PM, Alex
Do not support.
This document does not make a good case for why tags should exist.
The introduction does not explain what they are useful for, it just makes a
comparison to #hashtags (which is something I would expect to see in an April
1st RFC).
The initial registry values, section 8.2, also
Hi,
It seems to be that the rule you quoted specifically states that expanding the
value space is not okay:
o A "type" statement may be replaced with another "type" statement
that does not change the syntax or semantics of the type. For
example, an inline type definition may
Hi,
[Note I haven't tested these answers. Also this is a source level view, with no
regards for compatibility]
[1] If you want to make a node optional (not mandatory), the way to do that is:
deviation "/a:a" {
deviate replace {
mandatory false;
}
}
[2] Deviation
Hi Bo,
My comments: (ignoring simple typos and placeholder values as this is a first
draft)
* What is a TACACS+ template? To my knowledge this is not a standard concept.
The word "template" does not appear in draft-ietf-opsawg-tacacs-10.
* What is a domain name, in the context of usernames?
Hi,
Since nobody else has answered I'll have a go.
I'm not familiar with subtree filtering, but I am with XPath. Assuming your
XPath translation is accurate, it will return no data (response A).
From: netmod on behalf of Shiva Kumar
I haven't seen any previous discussions on the topic, but we have a similar
problem.
Note this is not really to do with YANG itself, so much as the practical
limitations of the software package that provides our CLI interface.
In NETCONF, the existence of extra unused identities doesn't pose
__
From: Sterne, Jason (Nokia - CA/Ottawa) <jason.ste...@nokia.com>
Sent: Thursday, 29 March 2018 5:11 a.m.
To: Alex Campbell; netmod@ietf.org
Subject: RE: YANG 'must' Xpaths, predicates and wildcards
Thanks Alex. Sorry about those sloppy mistakes. I agree about the ../a-list
and
Hi,
For one thing, it should be ../a-list since a-list is not a child of foo.
Also - if foo is not configured and has no default value, then any must
expressions in foo are not evaluated because it is not part of the "accessible
tree". (I tested this in ConfD)
Apart from these issues, yes it
Hi,
I'm currently looking at draft-ietf-netmod-sub-intf-vlan-model-03 to see
whether we can use this as our main model for VLAN forwarding, and it appears
the answer is no.
There is no way to configure forwarding in this model; it is strictly about
interfaces.
The appendix gives the
Presumably you will have to decide on a sensible default value to use.
What value will your actual device use after the software upgrade? That should
be the value it stores in the data tree when performing the upgrade.
From: netmod
Hi,
Perhaps not directly relevant, but the following sentence stuck out to me:
> Why not use the syslog/TLS specification, with the security features
> administratively turned off within secure environments?
I was under the impression that the IETF tries to ensure that TLS security is
not
Hi,
Good point - adding on to that, I'd like to point out that there are more
protocols that use ports besides TCP and UDP, such as SCTP and DCCP.
If the port number was not protocol-specific then devices would also have to
match SCTP ports, DCCP ports, and other protocol ports, even for
Hi,
'when' does not affect schema nodes, only data nodes.
The schema nodes is essentially the YANG itself, without reference to any
particular instance data.
Given an example YANG fragment:
list widgets {
key name;
leaf name {type string;}
leaf can-frob {type
On page 37, "duplex" is mistyped as "duplexx".
Other than this minor error, I believe this draft is ready for publication.
From: netmod on behalf of Kent Watsen
Sent: Wednesday, 29 November 2017 8:29 a.m.
Hi,
I noticed the table in section 3 has been mangled - it has extra blank lines,
entries in the wrong side of the table, and a missing pipe in the bottom right
corner.
Apart from that this draft looks good to me.
From: netmod
Resending as I previously sent this to i-d-announces by mistake and it appears
the whole message was rejected (i.e. it didn't get sent to netmod either)
Hi Xiaojian,
* The published module ietf-ip (RFC 7277) overlaps the data being provided in
this module.
Especially
Hi Xiaojian,
* The published module ietf-ip (RFC 7277) overlaps the data being provided in
this module.
Especially your /arp/arp-tables and /arp/arp-static-tables seem to correspond
to /interfaces-state/interface/ipv4/neighbor and
/interfaces/interface/ipv4/neighbor from ietf-ip.
I think
Hi,
I've reviewed the draft and found the following issues.
* YANG enumeration values are conventionally lowercase, but the
delay-mechanism-enumeration and port-state-enumeration types in the draft have
uppercase values.
* Similarly, hyphens should be used rather than underscores (pre-master
Hi,
I'd be very wary of adding guidelines that restrict the regex syntax.
A tool that supports YANG must implement the full regex language anyway (or
ignore regexes altogether if they are not relevant to the tool's function).
However, these guidelines will inevitably encourage some tool
Hi,
I'm not Rob, but my understanding is that if a module author wanted to migrate
to YANG 2.0, they could merge their submodules back into the main module -
which is not a difficult procedure and does not break compatibility with
clients.
Alex
From:
Why would it not make sense? Is your question about the datastores proposal?
Usually an action will refer to some object that is defined as configuration
and/or state, and may depend on the particular properties of that object.
Here is a YANG fragment showing one possible application:
list
Hi,
I would very much like to see this happen.
However I recommend at least splitting up "ethernet-like" into
"ethernet-mac-like" and "ethernet-phy-like". At Aviat we have microwave radio
interfaces that behave like Ethernet at the MAC level but have totally
different PHYs. The distinction is
Doesn't this mean that if a new protocol is defined, then it won't be usable in
ACLs until the server's data model is upgraded? (And with many devices, that is
quite likely never)
From: netmod on behalf of Mahesh Jethanandani
There are many different layers and all, or none of them could be called
configuration depending on your perspective.
Consider the current set of routes on a router. I think we can all agree that
from the point of view of the Linux kernel, or a hardware routing chip, this is
configuration data.
Presumably a device is free to not implement an optional config=false node if
that node would never be returned in a response anyway - as this will make no
externally visible difference.
However, if the model states or implies that the node is present under certain
conditions (for example,
Hi,
I noticed that the ietf-routing YANG (published in RFC 8022) allows for
multiple instances of each control plane protocol, as well as multiple RIBs per
address family.
However I don't see any way to associate one with the other. Without additional
configuration, protocols will only place
Hi,
In the description of /hardware-state/component, which describes the procedure
for matching newly added hardware components with pre-configured entries in
/hardware/component:
What happens if hardware-config is supported, and there is no entry with
matching values for the nodes 'class',
Hi,
I believe you misunderstood the intention.
A "when" statement inside a deviation would simply add/remove/update a "when"
statement in the target module. It would not make the deviation conditional.
I asked this some time ago, and for some reason I was told that it would be
overly
Hi,
It means exactly what the summary says. In YANG 1.0 (RFC 6020) we have:
A leaf that is part of the key can be of any built-in or derived
type, except it MUST NOT be the built-in type "empty".
and in YANG 1.1 (RFC 7950) we have:
A leaf that is part of the key can be of any
Shafer <p...@juniper.net>
Sent: Thursday, 19 January 2017 12:51 p.m.
To: Alex Campbell
Cc: Ladislav Lhotka; NETMOD WG
Subject: Re: [netmod] top-level mandatory nodes
I was really looking for a use case. What's is a specific scenario
where one would want a device to always repor
The purpose of a mandatory config=false node is to say that the data is
_always_ needed.
In the case where the node is also top-level, if your server fails to provide
that data, then your server is not compliant with the YANG.
If the data is sometimes not needed, then the module author should
IMO it should be treated like any other protocol error.
Which means that an ideal client will report an error - but in practice they'll
end up ignoring the constraint violation because it's easier to not do
validation.
This problem isn't specific to YANG - what happens if I make a request to an
his.
Alex
From: Clyde Wildes (cwildes) <cwil...@cisco.com>
Sent: Friday, 16 December 2016 7:29 a.m.
To: Alex Campbell
Cc: netmod@ietf.org; Kent Watsen; Juergen Schoenwaelder
Subject: Re: [netmod] WG Last Call for draft-ietf-netmod-syslog-model-11
Hi Alex,
Thanks for your rev
___
From: Andy Bierman <a...@yumaworks.com>
Sent: Tuesday, 10 January 2017 11:20 a.m.
To: Alex Campbell
Cc: netmod@ietf.org
Subject: Re: [netmod] "when" statement deviation
Hi,
This is not allowed because it is too complicated to implement.
Changing the schema tree based on valu
Hi,
I have a module that adds some configuration to interfaces (the specific
feature being configured isn't important here, so I'll just call it "feature").
I want to implement this module, but the device I'm working on only supports
the feature on some kinds of interfaces.
So I want to add
Yes/support
The main issue I have with this draft, that I would like to be addressed at
some point, is the way it uses heavily restricted lists to model sequences of
VLAN tags.
It seems to me that something like the following would be much simpler, without
losing any expressive power, in most
I am considering to implement the data model in this draft.
I have reviewed this draft and found the following issues. In approximately
decreasing order of severity:
* In the "selector-facility" choice statement the cases have misleading names -
the case where no facility is matched is named
IMO using an action or rpc is an okay solution for now, certainly better than
than not including the data at all.
Perhaps in the future the client could specify which YANG modules it cares
about, in addition to a subtree filter. Then you could put the extended
diagnostic information into
Hi,
If you are referring to the circular reference in the expresssion
'derived-from-or-self(../class, "iana-entity", "sensor")', I would rather see
sensor-data separated into another module than see entity-physical-class moved
to iana-entity.
This would be more consistent with the RFC 7223
> Dale R. Worley writes:
>> Ladislav Lhotka writes:
>>> typedef Compression-Method {
>>> ...
>>> }
>>>
>>> list node {
>>> config true;
>>> key name;
>>>
>>> string name;
>>>
>>> leaf-list supported-compression-methods {
>>> type
What prevents features from being units of conformance?
From: netmod on behalf of Juergen Schoenwaelder
Sent: Friday, 2 September 2016 5:06 a.m.
To: Andy Bierman
Cc: netmod@ietf.org
Subject:
The intention in this case is obviously to evaluate the 'must' statement if
the container contains any values; what would break if we said that
A non-presence container exists in the data tree if and only if it has
any children which exist in the data tree.
thus disallowing the existence
I think in this case it would make sense to implement both the hypothetical
standard module's state data (which would be device-agnostic, such as a boolean
value indicating whether each configured rule is active) and also a
device-specific module providing access to the more detailed internal
Isn't that exactly what the proposed applied configuration datastore is for?
If a device doesn't allow management stations to create or remove list entries,
but still creates or removes list entries itself, then it can publish them
through the applied configuration datastore, while leaving the
My preference is not to add schema nodes that are not useful.
If it is foreseen that other nodes will be added in the container then the
container is fine; otherwise I see no reason to have one.
From: netmod on behalf of Andy Bierman
57 matches
Mail list logo