t's possible to agree
> with one but not the other. I'd also like to point out that the first part
> of the discussion is limited to requirements only so we can focus on the
> former before delving in to the latter .
>
> Lou
>
>
> On September 9, 2015 6:01:20 PM Ju
ically split into 2, either through being
> present in separate running and applied datastores, or through having
> separate cfg-intended/cfg-applied leaves.
> - /if:interfaces-state, which I perceive as logically the derived
> state for an interface.
>
My personal req
esource has a way to maintain and manage meta information,
this is probably the best an implementation will be able to do. Or am
I missing something?
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax:
of
> that conclusion (potentially).
>
> Do folks think we are ready to close this issue down officially?
>
Tom,
what do you think is the outcome of the discussion? This is not at all
clear to me so how can I say we are done with it...
/js
--
Juergen Schoenwaelder
On Thu, Oct 01, 2015 at 09:24:52AM +0200, Ladislav Lhotka wrote:
> Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> writes:
>
> > On Wed, Sep 30, 2015 at 01:01:36PM +0200, Ladislav Lhotka wrote:
> >> Hi Randy,
> >>
> >> thanks for the c
On Thu, Oct 01, 2015 at 10:37:51AM +0100, Robert Wilton wrote:
> Hi Juergen,
>
> On 01/10/2015 09:29, Juergen Schoenwaelder wrote:
> >On Wed, Sep 30, 2015 at 03:58:56PM +, Kent Watsen wrote:
> >>Again, let's tackle a hard issue before tomorrow's interim meeting - this
to
understand what a device is doing, it is necessary to look at all the
state (addresses in the example) of a component (an interface in the
example). I think it is a requirement that it is easy to retrieve all
operational state of a component.
/js
--
Juergen Schoenwaelder Jacobs Univers
On Wed, Sep 23, 2015 at 03:46:27PM +0200, Ladislav Lhotka wrote:
>
> > On 23 Sep 2015, at 15:11, Juergen Schoenwaelder
> > <j.schoenwael...@jacobs-university.de> wrote:
> >
> > On Wed, Sep 23, 2015 at 10:14:52AM +0200, Ladislav Lhotka wrote:
> >>
1.1 virtual interim
meetings that we have allocated.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <http://www.jacobs-university
n this document:
https://svn.tools.ietf.org/svn/wg/netmod/yang-1.1/last-call-comments.html
This is the first WG Last Call for this document.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
; "doesn't exist" would not be appropriate for the example you provide
> > below. It would be incorrect if some of the notifications in your
> > example had already been defined, even though "anydata" would still
> > be necessary to handle others not yet define
als works well by
reviewing issues in an interim online meeting. Perhaps Kent can come
up with a proposal, put it down somewhere (e.g. a revision of the I-D)
and then let the mailing list bash out the details.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200
ecause you still do not like it.
That said, "MUST be known at run-time" may already fall apart with the
mount proposals discussed in NETCONF (or it is sufficiently unclear to
whom it MUST be known).
/js
--
Juergen Schoenwaelder Jacobs University Bremen g
k to multiple servers and in principle the protocol supports
pipelining of requests from a single client to a single server but all
requests are executed serially. I think the same applies to RESTCONF
but I am a bit less confident.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Ph
prefix foo;
}
then you can refer to defined in via
foo:
but if you declare the namespace of the module you are defining an
a prefix for it, that is
module {
namespace ;
prefix bar;
}
and I (a) suggest that modules importing should use the
prefix 'bar' and (b) I allow to r
eas for anydata the phrase "can be modelled
> with YANG" may be interpreted in different ways. We are introducing a
> dubious new concept in YANG 1.1 with no apparent gain.
>
I do not think we are going to repeat that debate. I think we
concluded that anyxml does not mean any JSON.
/js
that might be needed based on this revision of the YANG
1.1 specification. We will try to do most of the word smithing via the
mailing list but if needed we will make use of the YANG 1.1 virtual
interim meetings that we have allocated.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
On Tue, Sep 15, 2015 at 10:00:46AM +0200, Ladislav Lhotka wrote:
> Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> writes:
>
> > On Thu, Sep 10, 2015 at 06:19:20PM -0700, Randy Presuhn wrote:
> >
> >> >> Let's look at a slightly more complex
e details to section 3?
- Some empty lines in the YANG definition would have pleased my eyes.
Editorial
- there are a couple of missing articles throughout the text
- sometimes singular/plural is at odds
- s/this draft/this document/
- you may add another 'e' to my name ;-)
/js
--
Juergen
used? Is there a need
for some prioritization?
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
___
to
> YANG/NETCONF/RESTCONF needs to be backwards compatible with respect to
> existing deployments. Did we miss it or is it too obvious?
>
It may be obvious for many of us but for the sake of completeness I
prefer to have this backwards compatibility assumption explicitely
stated.
/js
--
Juergen
base if:interface-type;
> }
>
> augment "/if:interfaces/if:interface" {
>when "if:type = 'mymod:some-new-iftype'";
>
>leaf mandatory-leaf {
> mandatory true;
> type string;
>}
> }
>
ese requirements, so I want to be sure everyone involved has
> through through this kind of change.
>
> —Tom
Tom,
I think Andy is talking about applicability - to which kind of servers
do these requirements apply. For example, if it takes more time on a
certain class of device
enforced while they actually are not. In other words, an attacker
might be interested in trying to extend the period where intended
configuration differs from applied configuration by finding ways to
prevent the server to apply the intended configuration.
/js
--
Juergen Schoenwaelder Jacobs
ce properties do not match).
Constraining the config by the (dynamic) interface properties would
imply that configurations may become invalid spontaneously, which is
something YANG does not allow. In other words, there can be a mismatch
between 'intended config' and 'applied config' in such situation
so that we can publish the rest in a timely manner. The
alternative is to hold off this document in an attempt to replace #5
with something that is concrete and actionable.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759
and contributor.
If you are on the NETMOD WG email list but are not listed as an author
or contributor, then please explicitly respond only if you are aware
of any IPR that has not yet been disclosed in conformance with IETF
rules.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone
did end on October 12th
2015 and lead to a number of changes. A diff of -07 to -09 can be
found here:
http://tools.ietf.org//rfcdiff?url1=https://tools.ietf.org/id/draft-ietf-netmod-rfc6020bis-07.txt=https://tools.ietf.org/id/draft-ietf-netmod-rfc6020bis-09.txt
/js
--
Juergen Schoenwaelder
On Wed, Jan 06, 2016 at 06:28:41PM +0100, Dean Bogdanovic wrote:
>
> > On Jan 6, 2016, at 10:30 AM, Juergen Schoenwaelder
> > <j.schoenwael...@jacobs-university.de> wrote:
> >
> > On Mon, Jan 04, 2016 at 07:23:38PM +0100, Eliot Lear wrote:
> >
false;
>}
>// + add description that explains what happens if there is no such
>// instance
>
>
> (NOTE: this doesn't work w/ pyang at the momement, I am working on a
> fix)
>
And it would have to be if:interface-ref instead if:interface-state-ref
I think.
/js
-
On Tue, Dec 22, 2015 at 04:23:44PM +0100, Ladislav Lhotka wrote:
>
> > On 22 Dec 2015, at 16:06, Juergen Schoenwaelder
> > <j.schoenwael...@jacobs-university.de> wrote:
> >
> > On Tue, Dec 22, 2015 at 11:34:41AM +0100, Ladislav Lhotka wrote:
> >>
On Fri, Dec 18, 2015 at 04:16:04PM +0100, Ladislav Lhotka wrote:
>
> > On 18 Dec 2015, at 15:49, Juergen Schoenwaelder
> > <j.schoenwael...@jacobs-university.de> wrote:
> >
> > On Fri, Dec 18, 2015 at 03:22:48PM +0100, Ladislav Lhotka wrote:
> >>
with running code behind them (and ideally > 1
independent implementations). The problem might be "us" and not the
update rules.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax:
us back into the mess we
were in with SNMP.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
__
put in a best
guess what the names might be but assignment and registration via IANA
happens during the publication process.
Perhaps it helps to clarify in RFC6020bis that the updates rules apply
to published modules and not to modules under development.
/js
--
Juergen Schoenwaelder
ready done an "ack" back to the client before transition (C) so the
> client may have already sent some additional new config that depends on the
> previous edit. That would mean that new config isn't valid.
>
> Jason
>
> ___
> netmod mail
On Sat, Dec 19, 2015 at 07:50:58AM -0500, Dean Bogdanovic wrote:
> Juergen,
>
> Please see answers inline
>
> Dean
>
> > On Dec 11, 2015, at 12:31 PM, Juergen Schoenwaelder
> > <j.schoenwael...@jacobs-university.de> wrote:
> >
> > On Wed, Dec 0
On Mon, Dec 21, 2015 at 04:07:20PM +0100, Ladislav Lhotka wrote:
>
> > On 21 Dec 2015, at 15:47, Juergen Schoenwaelder
> > <j.schoenwael...@jacobs-university.de> wrote:
> >
> > I believe the model we have agreed on in RFC 6020 is this:
> >
> > - Y
ut or
output parameters?
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
___
netmod m
the purpose of the second sentence? I checked RFC 7159 and it
seems the proposed second sentence simply repeats the set of possible
JSON values listed in section 3 of RFC 7159. So why is this sentence
technically needed?
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGm
ple URN [RFC 6963] or the domain "example.com".
> For example:
>
> urn:example:interfaces
>
> http://example.com/ns/example-system
Adopting urn:example makes sense to me.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587
On Mon, Jan 11, 2016 at 11:21:43AM +0100, Martin Bjorklund wrote:
> Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> wrote:
> > On Mon, Jan 11, 2016 at 10:15:26AM +0100, Martin Bjorklund wrote:
> > > Hi,
> > >
> > > Currently, 60
On Fri, Jan 08, 2016 at 12:52:37PM +0100, Martin Bjorklund wrote:
> Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> wrote:
> > On Thu, Jan 07, 2016 at 04:21:42PM +0100, Martin Bjorklund wrote:
> > >
> > > With YANG 1.1, a leafref can be marked as &quo
ements so I do not follow the logic a
requirements document should not have MAYs.
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <htt
(C) guideline is to not use a container parent
> > (D) something else
>
>
> I prefer (C).
>
Is there a reasoning as well? Or just a question of style and taste?
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
On Wed, Jun 08, 2016 at 01:16:28PM +0200, Martin Bjorklund wrote:
> Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> wrote:
> > On Wed, Jun 08, 2016 at 12:29:59PM +0200, Martin Bjorklund wrote:
> >
> > > > > Note that this is legal YAN
On Mon, Jun 06, 2016 at 03:43:23PM +0200, Ladislav Lhotka wrote:
>
> > On 06 Jun 2016, at 15:09, Juergen Schoenwaelder
> > <j.schoenwael...@jacobs-university.de> wrote:
> >
> > On Mon, Jun 06, 2016 at 10:13:47AM +0200, Ladislav Lhotka wrote:
> >> Hi,
&
tually, the values in the data tree are always in the canonical
form (see Section 9.1).
Section 7.5.3:
Note that since all leaf values in the data tree are conceptually
stored in their canonical form (see Section 9.1), any XPath
comparisons are done on the canonical value.
Do you sugges
FC errata.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
___
netmod mailing list
ient detail? Note also that 9.9.2 is a subsection of
9.9, which describes the leafref type.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103
ose this issue.
> Also, in the lexicon:
>
>o anydata: A data node that can contain an unknown set of nodes that
> can be modelled by YANG, except anyxml.
>
>o anyxml: A data node that can contain an unknown chunk of XML data.
>
> Both definitions sho
On Tue, Jun 07, 2016 at 09:08:56AM -0700, Andy Bierman wrote:
> On Tue, Jun 7, 2016 at 8:52 AM, Juergen Schoenwaelder <
> j.schoenwael...@jacobs-university.de> wrote:
>
> > On Tue, Jun 07, 2016 at 11:26:03AM -0400, Dale R. Worley wrote:
> > > Ladislav Lhotka <lho
correctly. Please check the edits
as soon as possible, any errors found must be raised by Thursday
2016-06-16.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <h
DQUOTE and backslash >
>
> (The existing production for yang-string is removed.)
>
>;; any Unicode or ISO/IEC 10646 character including tab, carriage
>;; return, and line feed, but excluding the other C0 control
>;; characters, the surrogate blocks, and the non
le or double quote character, a semicolon (";"), braces ("{" or
> "}"), or comment sequences ("//", "/*", or "*/").
>
This looks good to me.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421
other editing models
but given the way the RFC is written, I think you can't rely on other
editing models to be supported and to work in an interoperable way.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen
nyway so that they can already be
taken into account.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
___
:= urn:yang:
which gives us
urn:yang:org-acme-interfaces
and this could even make the explicit namespace definition in YANG
modules go away (with the default that the module org-acme-foo uses
the namespace URN urn:yang:org-acme-foo).
--
Juergen Schoenwaelder J
.
>
>must 'key1 != "unspecified" or key2 != "unspecified"';
>
Does this not mean you can't have an interface named 'unspecified'
anymore? Perhaps we should have disallowed zero-length string values
for /interfaces/interface/name and then we would have a handy
On Fri, Jun 10, 2016 at 01:06:42PM +0200, Juergen Schoenwaelder wrote:
> Hi,
>
> Martin has posted revision -13 of the YANG 1.1 specification. This
> revision incorporates all comments that we have received during the
> IESG process. A big thanks in particular to our gen-
operation in the accessible tree.
>
>o Otherwise, the context node is the node in the accessible tree
> for which the "must" statement is defined.
>
I think this resolves the issue.
/js
--
Juergen Schoenwaelder Jacobs Univers
Benoit,
Martin has posted revision -14 and I (in my role as document shepherd)
believe -14 addresses all comments that we received during the IESG
process. Please press any necessary buttons to continue the process.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone
tensible facility concept.
>
> Jason
>
> -Original Message-
> From: Juergen Schoenwaelder [mailto:j.schoenwael...@jacobs-university.de]
> Sent: Friday, June 17, 2016 2:38
> To: Sterne, Jason (Nokia - CA)
> Cc: netmod@ietf.org
> Subject: Re: [netmod] partial review of
On Mon, Jan 11, 2016 at 11:02:30AM +, Robert Wilton wrote:
>
>
> On 10/01/2016 11:21, Juergen Schoenwaelder wrote:
> >On Fri, Jan 08, 2016 at 01:46:44PM +, Acee Lindem (acee) wrote:
> >>The draft is quite succinct and I’m not sure how you and
nd...@gmail.com <mailto:ivand...@gmail.com>> wrote:
> >>
> >>> On Jan 8, 2016, at 1:09 PM, Juergen Schoenwaelder
> >>> <j.schoenwael...@jacobs-university.de> wrote:
> >>>
> >>> On Fri, Jan 08, 2016 at 12:52:37PM +0100, Martin Bjorkl
broaden the title.
In fact, I wonder why 4.B is useful. If we agree that the applied
config (an extended subset of the intended config) is the configration
that determines what the device is doing, then we likely should have a
mapping of the applied config to associated derived state.
/js
s for the applied configuration's data model
and its values".
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <http:/
me.
>
I think filters even today allow you to retrieve both subtrees
(intended and operational state) together if that is desired.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 20
On Mon, Jan 11, 2016 at 02:20:05PM +, Acee Lindem (acee) wrote:
>
>
> On 1/11/16, 3:13 PM, "Juergen Schoenwaelder"
> <j.schoenwael...@jacobs-university.de> wrote:
>
> >On Mon, Jan 11, 2016 at 02:07:13PM +, Acee Lindem (acee) wrote:
> &g
with each new revision of the I-D.
>
Lada, this is not how our current YANG 1.0 versioning and revision
rules work and we are not going to change them in YANG 1.1 either.
The rules we have do make a distinction between published modules and
modules that are unpublished.
/js
--
Juergen Schoe
he _associated_ derived state? My interpretation is that
it is any derived state that is a _direct_ consequence of some applied
config being active but it does not include any state indirectly
associated with some applied config. (For example, if I turn on a VPN
service, then the associated derived state ar
> I generally support this suggestion because I think it solves the
> problem that a server can't indicate a difference between a leaf not
> being configured at all and leaf that is configured with the default
> value.
You may want to read about the 'explicit' mode defined in
to find the minimum number of rules where
we have evidence that they avoid big problems.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3
e format of syslog messages on a wire. But this
> syslog YANG model is more about how devices configure logging.
>
> So I'm strongly in favor of seeing the facilities stay as an identity.
>
> Regards,
> Jason
>
> -Original Message-
> From: netmod [mailto:netmo
On Mon, Feb 08, 2016 at 05:26:13PM +0100, Eliot Lear wrote:
> Juergen,
>
> On 2/8/16 5:20 PM, Juergen Schoenwaelder wrote:
>
> > None of the existing tools that assume YANG defined data is XML
> > encoded according to RFC 6020 will not be able to process da
of the existing tools that assume YANG defined data is XML
encoded according to RFC 6020 will not be able to process data in a
new encoding.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +
ments draft,
> but we can probably find a suitable place.
There is apparently much less agreement on what the problem is, what
the terms mean, and how they related to existing technology than I
thought.
/js
--
Juergen Schoenwaelder
On Mon, Feb 08, 2016 at 01:30:02PM +, Robert Wilton wrote:
> Hi,
>
> On 05/02/2016 17:34, Juergen Schoenwaelder wrote:
> >On Fri, Feb 05, 2016 at 05:22:03PM +, Robert Wilton wrote:
> >>2. Personally, for a datastore solution, I would prefer if the new
> >&
On Tue, Feb 09, 2016 at 11:17:13AM +, Robert Wilton wrote:
>
>
> On 08/02/2016 16:20, Juergen Schoenwaelder wrote:
> >On Mon, Feb 08, 2016 at 01:21:52PM +, Robert Wilton wrote:
> >>So, IIRC, your concern is specifically that a generic YANG client
> >>lib
;. What exactly is a 'top-level module' (and does it matter, why
can I not mount a non-top-level module)? And does 'incorporation of
the data model' imply 'incorporation of the complete data model'?
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587
proposed in
> draft-wilton-netmod-opstate-yang).
A diff is a way to make delta's efficient.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
same, so yes -- unless you are implying
> something I'm missing ;-)
I am trying to understand and I am trying to avoid discussions where
people talk past each other because of different interpretations of
the words they use.
/js
--
Juergen Schoenwaelder Jacobs University B
behavior. All I am looking for is
to make sure that (a) we did not forget any agreed upon edits and (b)
that edits did not introduce any bugs or fatal errors.
The deadline for sending in comments is Monday 2016-02-15.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone
On Thu, Feb 04, 2016 at 12:07:32PM -0500, Lou Berger wrote:
>
>
> On 2/4/2016 12:02 PM, Juergen Schoenwaelder wrote:
> > Can I mount /top/second?
> yes. But in our use case, we wouldn't explicitly do a mount here. but we
> would allow a server may choose to support
On Thu, Feb 04, 2016 at 11:33:12AM -0500, Lou Berger wrote:
> Juergen,
>
> see below
>
> On 2/4/2016 11:12 AM, Juergen Schoenwaelder wrote:
> > On Thu, Feb 04, 2016 at 09:53:11AM -0500, Lou Berger wrote:
> >> Juergen,
> >>
> >> see below.
>
ntended config, e.g. with-config-state=intended+diff-cfg.
>
> Thoughts?
>
> Lou (with Chris)
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Juergen Schoenwaelder Jaco
On Thu, Feb 11, 2016 at 02:52:27PM +, Robert Wilton wrote:
>
> On 11/02/2016 09:29, Juergen Schoenwaelder wrote:
> >We are discussing this text:
> >
> >D. The configuration protocol MUST specify how configuration
> >errors are hand
to get the message, what is easier to process for a client is
largely subjective or a function of the particular client environment
or what I want to do with the data.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 287
are with the notion "intended=running" and “applied”
> config?
Yes (with the caveat that the rollback requirement text is kind of
broken).
/js
> - Gert
>
>
>
>
>
> On 2016-08-02 17:38, "Juergen Schoenwaelder"
> <j.schoenwael...@jacobs-univers
- and most likely people change this constant for a reason).
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
_
proach where an RPC option can simply request that the encoding
defined in the YANG RFC is ignored and replaced with a very different
encoding.
/js (stating a clear opinion as a technical contributor)
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587
elp. It is kind of
funny that YANG does not allow reference statements on imports...
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103
On Mon, Feb 01, 2016 at 08:08:00PM +0100, Martin Bjorklund wrote:
> Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> wrote:
> > On Fri, Jan 29, 2016 at 01:14:27PM +0100, Ladislav Lhotka wrote:
> > >
> > > If an argument starts as unquoted, th
ule barmod (and btw, pay attention to the "import
> foomod") and module exmod
I still believe the text in draft-ietf-netmod-rfc6087bis-05 needs
fixing to distinguish between examples that should be subject to
validation and examples that are just there for documentation purposes
a
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> What is the expected ?
>
> [KENT] this depends on what data is configured on the server
>
>
> More specifically, will CCC’s key (leaf ) be included in rpc-reply? Will
> AAA/BB
defines a
certain behaviour here. There is text about quoted strings but not
much about unquoted strings. So I would not be surprised if
implementations behave differently here.
The text in RFC 6020bis also defines backslash behaviour only inside
quoted strings. It is left to an implementor's imagi
is? If yes, how?
I think the intention was to say at the 'top-level of the schema tree'.
It does not have to be right after the imports.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103
t to the schema
structure, which has its own set of complexities. Yes, the versioning
issues go away since I have to adapt to each implementation
dynamically but there is surely a cost involved with that as well.
Am I missing something?
/js
--
Juergen Schoenwaelder Jacobs University
G and the NETCONF messages, but is carried as a
convenience to implementors.
The position is a 'convenience to implementors' and this convenience
applies equally well to clients and servers.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587
ts bound to the module
> that uses the grouping. I will clarify this in my draft.
>
Thats odd, no? An extension statement (which may be ignored) causes a
constraint on a grouping so that it can only be used once? Why not
refer to the mount point by path to avoid this?
/js
--
Juergen Sch
101 - 200 of 1039 matches
Mail list logo
