Talking with NETCONF and NETMOD chairs about the relation with netmod and
netconf, we agree to move draft-wu-netconf-restconf-factory-restore
To netmod with draft name change and reference changes, i.e.,
1.The draft name is changed into draft-wu-netmod-factory-default-00
2.The references to netcon
Capabilities, features and deviations indicate the type of requests the router
can respond to.
The capability advertisement may not affect the router, but the capability
itself directly does.
The capability advertisement tells the client that the router can answer
requests involving the capabil
On Thu, Oct 18, 2018 at 1:32 PM, Martin Bjorklund wrote:
> Andy Bierman wrote:
> > On Thu, Oct 18, 2018 at 12:58 PM, Martin Bjorklund
> wrote:
> >
> > > Andy Bierman wrote:
> > > > Hi,
> > > >
> > > > I strongly agree that a new data type is needed (ypath1.0 or just
> ypath
> > > is
> > > > fi
This message concludes the successful adoption of
draft-clemm-netmod-nmda-diff-00.
Authors, please resubmit this draft, unchanged, other than to rename it as
draft-ietf-netmod-nmda-diff-00.
As is generally the case, this approval signals that the working group is
willing to work on the probl
Andy Bierman wrote:
> On Thu, Oct 18, 2018 at 12:58 PM, Martin Bjorklund wrote:
>
> > Andy Bierman wrote:
> > > Hi,
> > >
> > > I strongly agree that a new data type is needed (ypath1.0 or just ypath
> > is
> > > fine)
> > > Adding new semantics or requirements to published data types is
> > >
On Thu, Oct 18, 2018 at 12:58:33PM -0700, Andy Bierman wrote:
> On Thu, Oct 18, 2018 at 12:50 PM, Juergen Schoenwaelder <
> j.schoenwael...@jacobs-university.de> wrote:
>
> > On Thu, Oct 18, 2018 at 12:45:44PM -0700, Andy Bierman wrote:
> >
> > > No moving it later because the import looks bad. Th
On Thu, Oct 18, 2018 at 12:58 PM, Martin Bjorklund wrote:
> Andy Bierman wrote:
> > Hi,
> >
> > I strongly agree that a new data type is needed (ypath1.0 or just ypath
> is
> > fine)
> > Adding new semantics or requirements to published data types is
> > unacceptable.
> >
> > Also, we must get t
Andy Bierman wrote:
> Hi,
>
> I strongly agree that a new data type is needed (ypath1.0 or just ypath is
> fine)
> Adding new semantics or requirements to published data types is
> unacceptable.
>
> Also, we must get the type and module containing the data type right on the
> first try.
> No mov
On Thu, Oct 18, 2018 at 12:50 PM, Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
> On Thu, Oct 18, 2018 at 12:45:44PM -0700, Andy Bierman wrote:
>
> > No moving it later because the import looks bad. That said, a "quick
> > 6991-bis" is unrealistic, and a multi-year 6991-bis
On Thu, Oct 18, 2018 at 12:45:44PM -0700, Andy Bierman wrote:
> No moving it later because the import looks bad. That said, a "quick
> 6991-bis" is unrealistic, and a multi-year 6991-bis is unhelpful.
https://datatracker.ietf.org/doc/rfc6991/
/js
--
Juergen Schoenwaelder Jacobs Unive
Hi,
I strongly agree that a new data type is needed (ypath1.0 or just ypath is
fine)
Adding new semantics or requirements to published data types is
unacceptable.
Also, we must get the type and module containing the data type right on the
first try.
No moving it later because the import looks bad
Support.
> On Oct 18, 2018, at 6:03 AM, Lou Berger wrote:
>
> All,
>
> This is start of a two week poll on making
> draft-kwatsen-netmod-artwork-folding-08 a working group
> document. Please send email to the list indicating "yes/support" or
> "no/do not support". If indicating no, please stat
Hi,
Seems this discussion affects 10 draft modules using the xpath1.0 type.
The proposed boilerplate description text that was not added to some RFC
modules like ietf-netconf-monitor...@2010-10-04.yang
should be as consistent as possible (or skipped based on the
ietf-netconf-monitoring prece
Yes/support.
Thanks,
Rob
On 18/10/2018 14:03, Lou Berger wrote:
All,
This is start of a two week poll on making
draft-kwatsen-netmod-artwork-folding-08 a working group
document. Please send email to the list indicating "yes/support" or
"no/do not support". If indicating no, please state your
Yes/support.
-Qin
-Original Message-
From: Lou Berger
Date: Thursday, October 18, 2018 at 9:11 AM
To: "netmod@ietf.org"
Cc: "netmod-cha...@ietf.org"
Subject: WG adoption poll draft-kwatsen-netmod-artwork-folding-08
Resent-From:
Resent-To: , ,
Resent-Date: Thursday, October 18, 2018
[fixed the date in Lou's message below]
No objection.
Kent // contributor
-Original Message-
From: Lou Berger
Date: Thursday, October 18, 2018 at 9:11 AM
To: "netmod@ietf.org"
Cc: "netmod-cha...@ietf.org"
Subject: WG adoption poll draft-kwatsen-netmod-artwork-folding-08
Resent-From:
Poll ends Nov 1 - sorry about that...
On 10/18/2018 9:03 AM, Lou Berger wrote:
All,
This is start of a two week poll on making
draft-kwatsen-netmod-artwork-folding-08 a working group
document. Please send email to the list indicating "yes/support" or
"no/do not support". If indicating no, ple
We can't time travel and as you mentioned option A has consistency within each
encoding, so I'm also for option A.
Regards,
Reshad.
On 2018-10-18, 6:30 AM, "netmod on behalf of Martin Bjorklund"
wrote:
Hi,
Going back to the most urgent issue, what is this WG's recommendation
All,
This is start of a two week poll on making
draft-kwatsen-netmod-artwork-folding-08 a working group
document. Please send email to the list indicating "yes/support" or
"no/do not support". If indicating no, please state your reservations
with the document. If yes, please also feel free to p
Given where we are, I also agree that A is the better choice.
I would also like to have a context-independent encoding of all YANG
types in the future.
Thanks,
Rob
On 18/10/2018 11:30, Martin Bjorklund wrote:
Hi,
Going back to the most urgent issue, what is this WG's recommendation
for the
On Thu, 2018-10-18 at 12:30 +0200, Martin Bjorklund wrote:
> Hi,
>
> Going back to the most urgent issue, what is this WG's recommendation
> for the subscribed-notifications draft in NETCONF wrt/ their usage of
> yang:xpath1.0 in filters?
>
> To summarize:
>
> We already have
>
> o instance-
Hi,
Going back to the most urgent issue, what is this WG's recommendation
for the subscribed-notifications draft in NETCONF wrt/ their usage of
yang:xpath1.0 in filters?
To summarize:
We already have
o instance-identifier in XML uses prefixes from the XML document
o instance-identifier in
A router has no use for it's capability/feature/deviation advertisements
either; module-tags are no different in this respect.
Thanks,
Chris.
Alex Campbell writes:
Hi,
The server implements the tags (at least the predefined ones), and the use
cases that come to my mind at least involve
23 matches
Mail list logo
