Joel,
The only needed edit is the addition of the -state appendix,
right? Or is something else needed?
Thanks,
Lou
(as co-author)
On 7/27/2019 5:54 PM, Joel Jaeggli wrote:
Folks Ignas,
draft-ietf-netmod-module-tags, currently in IESG review is in need of a
a fairly significant edit,
Lou Berger has requested publication of draft-ietf-netmod-artwork-folding-07 as
Best Current Practice on behalf of the NETMOD working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-netmod-artwork-folding
On 7/23/2019 12:03 PM, Ladislav Lhotka wrote:
this morning I attended the side meeting "Next Step of IETF YANG". I was
somewhat misled ...
This IETF's "side-meeting" approach to non-WG meetings is quite
confusing. This meeting was *not* a WG nor was it part of any NetMod WG
coordinated
by (4c) in the link you provided. Please let me
know if any adjustments are needed.
Thanks,
Kent (as an author)
On Jul 10, 2019, at 5:40 PM, Lou Berger wrote:
Hi Kent, Authors,
Sorry for the delay in processing this. WRT your comments, see below:
On 6/27/2019 5:35 PM, Kent Watsen wrote:
This
Hi Kent, Authors,
Sorry for the delay in processing this. WRT your comments, see below:
On 6/27/2019 5:35 PM, Kent Watsen wrote:
This update primarily regards the non-normative script:
- renamed to "rfcfold"
- now only uses sed one-liners
- auto-detects if platforms `[g]sed` and
.
Thank you!
Lou
On 5/12/2019 5:19 PM, Lou Berger wrote:
All,
This starts a two-week working group last call for
draft-ietf-netmod-artwork-folding-02
The working group last call ends on May 27.
Please send your comments to the working group mailing list.
Positive comments, e.g., "I've rev
Authors, Contributors, WG,
As part of WG Last Call
Are you aware of any IPR that applies to drafts identified above?
Please state either:
"No, I'm not aware of any IPR that applies to this draft"
or
"Yes, I'm aware of IPR that applies to this draft"
If so, has this IPR been disclosed in
All,
This starts a two-week working group last call for
draft-ietf-netmod-artwork-folding-02
The working group last call ends on May 27.
Please send your comments to the working group mailing list.
Positive comments, e.g., "I've reviewed this document
and believe it is ready for
Having worked with UIs that have the behavior of accepting an
address/prefix-len and mapping it to a prefix, (i.e., network/prefix-len
and zeroing out the non-significant bits) - some users really like it
as they don't have to do the transformation from address to network,
notably for odd
Hi,
Thank you all for the good input on this thread.
With the understanding that a 00 working group document is a starting
point for the working group rather than a document that is ready for
last call - we believe there is sufficient support to adopt this
document as a starting point for
the comments raised in this mail, update the
draft and then go to LC. Please note that the document status should be
changed Informational to Standards Track.
On 11/13/2018 11:55 AM, John Messenger wrote:
Hi,
At the 802.1 TSN meeting this morning, Lou Berger made a presentation on behalf
of Rob
Hi,
We have shuffled the slots a bit in order to allow for more
discussion in the second session. Specifically, the following are now
in the first session:
Title: A YANG Data model for Event Management
Presenter: Michael Wang
Draft:
Hi,
All received slides received to date have been uploaded to
https://datatracker.ietf.org/meeting/103/session/netmod
If you are on the agenda, please send your slides ASAP. If you have
already sent them, please confirm that they are posted at the above link.
Thank you!
Lou
an open issues section.)
Thank you,
Lou(and co-chairs)
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
Hi,
A draft agenda is available at:
https://datatracker.ietf.org/meeting/103/materials/agenda-103-netmod
Please take a look and send any question/comments/corrections you may have.
Thank you,
Lou (Kent and Joel)
___
netmod mailing list
and the file name changed to
draft-ietf-netmod-yang-instance-file-format-00.txt. Please note the
file name change. If you object to this change please propose an
alternative.
Thank you,
Lou (and co-chairs)
On 10/8/2018 7:38 AM, Lou Berger wrote:
All,
This is start of a two week poll
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&q
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
Authors, Contributors, WG,
As part of preparation for WG Adoption
Are you aware of any IPR that applies to drafts identified above?
Please state either:
"No, I'm not aware of any IPR that applies to this draft"
or
"Yes, I'm aware of IPR that applies to this draft"
If so, has this IPR been
Hi Rob,
On 10/8/2018 9:51 AM, Robert Wilton wrote:
Hi Lou,
On 08/10/2018 13:57, Lou Berger wrote:
Hi Rob/All,
Keep in mind that the document says what it says and that to change
text really requires a new version.
On 10/8/2018 6:01 AM, Robert Wilton wrote:
So there seem to be two
On 10/8/2018 10:13 AM, Juergen Schoenwaelder wrote:
On Mon, Oct 08, 2018 at 08:57:33AM -0400, Lou Berger wrote:
I think it's clear that the reviewers, notably myself as shepherd, missed
that this is a lowercase "must" and should have asked for clarification
during the review proces
On 10/8/2018 9:23 AM, Balázs Lengyel wrote:
Hello Martin,
Thanks for the info.
Yang-Catalog does not allow the download of modules. AFAIK it only gives
you metadata about the modules.
You mentioned download from pyang. How does that work?
I used https://github.com/YangModels/yang for some
Hi Rob/All,
Keep in mind that the document says what it says and that to change text
really requires a new version.
On 10/8/2018 6:01 AM, Robert Wilton wrote:
So there seem to be two available solutions here:
(i) The server MUST provide an origin value for the top level datanode,
This is
All,
This is start of a two week poll on making
draft-lengyel-netmod-yang-instance-data-04 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
Authors, Contributors, WG,
As part of preparation for WG Adoption
Are you aware of any IPR that applies to drafts identified above?
Please state either:
"No, I'm not aware of any IPR that applies to this draft"
or
"Yes, I'm aware of IPR that applies to this draft"
If so, has this IPR been
use/scope of errata is wrong.
Lou
On 10/5/2018 10:28 AM, Juergen Schoenwaelder wrote:
Well, if you think an errata does not work, we can file a one page
document with N pages of boilerplate around it.
/js
On Fri, Oct 05, 2018 at 08:14:33AM -0400, Lou Berger wrote:
Juergen
Juergen,
The document says what it says, i.e., "The origin for any top-level
configuration data nodes must be specified." Changes to this would
require a BIS or an RFC that updates this document.
Lou
On 10/5/2018 6:14 AM, Juergen Schoenwaelder wrote:
Hi,
the authors have been
At this point I think it's mature enough to be a yang DR or NETMOD wg thing?
Thoughts, objections?
Lou
--
On October 1, 2018 2:32:34 PM Kent Watsen wrote:
Benoit is the progenitor of the template. I took it to be an "AD thing"
has since passed to Ignas.
Kent
?-Original
No, I'm not aware of any IPR that applies to this draft
Lou
On 9/26/2018 11:26 AM, joel jaeggli wrote:
Authors, Contributors, WG,
Regarding the document
draft-ietf-netmod-module-tags-02
https://tools.ietf.org/html/draft-ietf-netmod-module-tags-02
Are you aware of any IPR that applies to draft
Hi,
Draft minutes have been posted based on the current etherpad
http://etherpad.tools.ietf.org:9000/p/notes-ietf-102-netmod
Thanks to all who contributed!
Please feel free to make corrections (based on what was actually said)
and let the list know that you made changes...
Cheers,
Lou
Hi,
hopefully others will chime in too, but here's my view (as a user
of schema mount, see
https://tools.ietf.org/html/draft-ietf-rtgwg-ni-model)...
On 7/30/2018 7:27 PM, Hayden Brown wrote:
Hi everyone,
I just wanted to ask if it would be possible to clarify the intentions
around
Hi,
A draft agenda for IETF is now available, please take a look to
ensure your request is included:
https://datatracker.ietf.org/meeting/102/materials/agenda-102-netmod
Comments/corrections should be sent to the WG chairs alias (cc'ed above).
Thank you,
Lou (Joel and Kent)
Hi,
As discussed at the NETMOD WG session in IETF 101, London, we would like
to set up a design team for YANG versioning.
The proposed charter for the design team is as follows:
The YANG Model Versioning Design Team is chartered to propose a revised
approach to supporting YANG module updates.
Hi,
I have a suggested minor clarification below.
--
On April 11, 2018 2:47:24 AM Martin Bjorklund wrote:
Juergen Schoenwaelder wrote:
On Tue, Apr 10, 2018 at 10:58:00PM +0200, Martin Bjorklund wrote:
> Juergen
Hi,
Thanks to Michael, we have updated minutes available for review at
https://etherpad.tools.ietf.org/p/notes-ietf-101-netmod
There are still some missing names, so if you made comments, please
review and ensure that both your names and comments are properly recorded.
Final minutes
Hi,
A draft agenda has been uploaded (a couple of days ago). See
https://datatracker.ietf.org/meeting/101/materials/agenda-101-netmod.txt
I just updated it with a recent request, and there is one additional
topic that may be added.
Please take a look and verify that your request has
On 3/6/2018 7:10 AM, Martin Bjorklund wrote:
Lou Berger <lber...@labn.net> wrote:
Martin,
On March 6, 2018 4:44:47 AM Martin Bjorklund <m...@tail-f.com> wrote:
Hi,
After thinking some more about this, realizing that this document is
in AUTH48, and looking at the fi
Martin,
On March 6, 2018 4:44:47 AM Martin Bjorklund wrote:
Hi,
After thinking some more about this, realizing that this document is
in AUTH48, and looking at the first sentence in the Abstract:
This document captures the current syntax used in YANG module tree
Hi,
The IETF agenda has been posted:
https://datatracker.ietf.org/meeting/101/agenda.html
We're scheduled to meet:
TUESDAY, March 20, 2018
1550-1820 Afternoon Session II
WEDNESDAY, March 21, 2018
1330-1500 Afternoon Session I
Please send any slot requests to the chairs alias (see
a model that we think will work well in
the post NMDA world that all of the IETF YANG models are moving to.
Thanks,
Rob
On 23/02/2018 14:36, Lou Berger wrote:
Rob,
I think we're going in circles here. We have one camp that wants to
replace the current module with pre 09 and is unwilling
Rob,
I think we're going in circles here. We have one camp that wants to replace
the current module with pre 09 and is unwilling to discuss compromise, and
another camp that wants 08 published as is and has been waiting for the
working group and authors to submit aversion to the IESG for
Martin,
On 2/23/2018 7:55 AM, Martin Bjorklund wrote:
Hi,
Lou Berger <lber...@labn.net> wrote:
Martin/Rob,
Back when the topic was raised for the first time publicly
(Yokahama) and discussed in the WG [1] *any* solution would have been
workable. At this point > 2 years late
appendix if that helps progress the document in a
more expedient fashion.
Thanks,
Rob
On 22/02/2018 16:18, Lou Berger wrote:
Hi,
(I have a bunch of different roles WRT this work. This mail is being
sent as an individual - as chair, I fully support the previous chair
statements on this draft.)
Chris a
Hi,
(I have a bunch of different roles WRT this work. This mail is being
sent as an individual - as chair, I fully support the previous chair
statements on this draft.)
Chris and I have come up with a proposal on how to provide full NMDA as
part the existing schema-mount module. Our
of the
discussions in the -01 rev. Finally, I believe the -01 rev should
indicate that the document updates RFC8040.
Thank you,
Lou (and co-chairs)
On 1/25/2018 8:26 AM, Lou Berger wrote:
Hi,
This is the start of a *two* week poll on making
draft-bierman-netmod-yang-data-ext a working group document
yes/support
no, I don't know of any IPR that applies to this document...
Lou
(as co-author)
On 2/6/2018 6:57 PM, joel jaeggli wrote:
Sorry, Feb 20th is the end date for the adoption call.
regards
joel
On 2/6/18 3:47 PM, joel jaeggli wrote:
Hi,
This is the start of a *two* week poll
Hi,
This is the start of a *two* week poll on making
draft-bierman-netmod-yang-data-ext 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
On 01/23/2018 03:26 PM, Juergen Schoenwaelder wrote:
> On Mon, Jan 22, 2018 at 08:05:54PM +, Kent Watsen wrote:
>>
>> Thank you all for the important discussion since the completion of WGLC on
>> Nov 6th.
>>
>> Per normal process, drafts typically progress once LC comments are address
>>
One additional point below.
n 01/24/2018 09:35 AM, joel jaeggli wrote:
>
>
> On 1/24/18 8:07 AM, Ladislav Lhotka wrote:
>> Hi,
>>
>> Kent Watsen writes:
>>
>>> Thank you all for the important discussion since the completion of WGLC on
>>> Nov 6th.
>>>
>>> Per normal
Authors, Contributors, WG,
As part of the preparation for WG adoption:
Are you aware of any IPR that applies to drafts identified above?
Please state either:
"No, I'm not aware of any IPR that applies to this draft"
or
"Yes, I'm aware of IPR that applies to this draft"
If so, has this IPR
Rob,
On January 19, 2018 1:05:46 PM Robert Wilton wrote:
On 17/01/2018 16:40, Martin Bjorklund wrote:
Ladislav Lhotka wrote:
Ok. I'm ok with keeping the inline case as it is. However, I think
I don't agree. The metadata annotation solves real
rrently we are focusing on getting the new yang library
>>> finalized. If no major isses pop up, the NMDA work may be complete by
>>> the London IETF. Hence the 3 months lower bound mentioned above.
>> I agree, and will try to help.
>>
>> Thanks, Lada
>&
order.
Lou
On January 18, 2018 2:57:23 AM Martin Bjorklund <m...@tail-f.com> wrote:
Lou Berger <lber...@labn.net> wrote:
On 1/17/2018 11:18 AM, Martin Bjorklund wrote:
...
>>> My main concern is actually the YL version. I strongly think SM need
>>> to use YL-
On 1/17/2018 11:18 AM, Martin Bjorklund wrote:
...
My main concern is actually the YL version. I strongly think SM need
to use YL-bis rather that the old YL, so that it can support NMDA.
Right now to SM is independent of Yang Library version and can run
with either.
No this is not correct.
On 1/17/2018 11:57 AM, Ladislav Lhotka wrote:
Ok. I'm ok with keeping the inline case as it is. However, I think
I don't agree. The metadata annotation solves real issues.
One issue with the annotation is that since the schema might be
different in different datastores, it means that the
On 1/17/2018 11:26 AM, Ladislav Lhotka wrote:
But when we discussed this the last time having inline schema
available at the top level (in the SM module), the general consensus
was that having YL under inline was the preferred approach.
What is new now is that we have an indirection; each
On 1/17/2018 11:06 AM, Ladislav Lhotka wrote:
I thought that the problem with the current solution and NMDA, was that
there is no way to find out what the LNE schema is if the LNE isn't
booted, and hence isn't providing . But I'm not sure what
issues that actually causes. E.g. does it cause
On January 17, 2018 9:42:43 AM Martin Bjorklund <m...@tail-f.com> wrote:
Lou Berger <lber...@labn.net> wrote:
On 1/17/2018 3:20 AM, Martin Bjorklund wrote:
> Lou Berger <lber...@labn.net> wrote:
>>
>> On 1/16/2018 11:15 AM, Robert Wilton wrote:
>>
On 1/17/2018 3:20 AM, Martin Bjorklund wrote:
Lou Berger <lber...@labn.net> wrote:
On 1/16/2018 11:15 AM, Robert Wilton wrote:
On 16/01/2018 15:50, Martin Bjorklund wrote:
Lou Berger <lber...@labn.net> wrote:
On 1/16/2018 10:13 AM, Martin Bjorklund wrote:
... (trimm
On 1/17/2018 1:59 AM, Ladislav Lhotka wrote:
...
I think
it is incumbent upon those revisiting past/closed WG decisions (in
this case, inline schema being represented by YL) to argue why the
decision needs to be revisited.
I'm repeating my self: b/c the current solution doesn't work well with
On 1/16/2018 11:15 AM, Robert Wilton wrote:
On 16/01/2018 15:50, Martin Bjorklund wrote:
Lou Berger <lber...@labn.net> wrote:
On 1/16/2018 10:13 AM, Martin Bjorklund wrote:
... (trimming to topic)
rejectected by the WG multiple times. FWIW there are drafts already
with
No
That's a fine idea, but ultimately we'll need to discuss/understand the
impact to the other dependent drafts, including the two already with the
IESG. If you can look at those and comment now, that would be helpful.
Lou
On 1/16/2018 10:55 AM, Ladislav Lhotka wrote:
I propose that we update
On 1/16/2018 10:22 AM, Ladislav Lhotka wrote:
I think
it is incumbent upon those revisiting past/closed WG decisions (in
this case, inline schema being represented by YL) to argue why the
decision needs to be revisited.
I'm repeating my self: b/c the current solution doesn't work well with
On 1/16/2018 10:08 AM, Vladimir Vassilev wrote:
4. This bit I found confusing. I propose this change to unambiguously
describe the current pyang format.
OLD:
* for a leaf-list or list
[] for a list's keys
NEW:
* for a leaf-list or list without keys
On 1/16/2018 10:13 AM, Martin Bjorklund wrote:
... (trimming to topic)
rejectected by the WG multiple times. FWIW there are drafts already
with
No at all. The first and last time I proposed this was on 15 December
2017:
https://www.ietf.org/mail-archive/web/netmod/current/msg19753.html
On 1/16/2018 8:50 AM, Martin Bjorklund wrote:
Lou Berger <lber...@labn.net> wrote:
On January 16, 2018 8:24:42 AM Martin Bjorklund <m...@tail-f.com>
wrote:
Lou Berger <lber...@labn.net> wrote:
Lada,
On January 16, 2018 7:07:15 AM Ladislav Lhotka <lho...@nic.cz>
in different datastores.
I strongly believe that these changes (along with the new YANG library schema
and NMDA) make for a simple and elegant datastore architecture in which schema
mount would be an optional feature.
Lada
On Mon, 2018-01-15 at 16:20 -0500, Lou Berger wrote:
Lada/Martin
On January 16, 2018 8:24:42 AM Martin Bjorklund <m...@tail-f.com> wrote:
Lou Berger <lber...@labn.net> wrote:
Lada,
On January 16, 2018 7:07:15 AM Ladislav Lhotka <lho...@nic.cz> wrote:
> On Tue, 2018-01-16 at 06:30 -0500, Lou Berger wrote:
>> Lada,
>>
&g
Lada,
On January 16, 2018 7:07:15 AM Ladislav Lhotka <lho...@nic.cz> wrote:
On Tue, 2018-01-16 at 06:30 -0500, Lou Berger wrote:
Lada,
It sounds like you are proposing in (1) a fairly significant change in the
direction of the draft and in (2) a basic approach that ha
legant datastore architecture in which schema
mount would be an optional feature.
Lada
On Mon, 2018-01-15 at 16:20 -0500, Lou Berger wrote:
Lada/Martin,
I don't believe we reached closure on this discussion. The open issues
relate to proposed new text (slightly modified):
at the end of the s
that the Schema Mount module itself parallels the
YANG Library module and only defines operational state data.
Is this change acceptable?
What other issues related to SM are outstanding?
Thank you,
Lou
On 12/19/2017 8:26 AM, Ladislav Lhotka wrote:
On Tue, 2017-12-19 at 07:49 -0500, Lou Berger wrote
Rob,
Thanks for all the helpful feedback!
On 01/15/2018 10:07 AM, Robert Wilton wrote:
...
>> NEW:
>>
>> If the node is augmented into the tree from another module,
>> its name is printed as :, where is the
>> prefix defined in the module where the node is defined.
No, I'm not aware of any IPR that applies to this draft
Lou
(co-author)
On 12/19/2017 1:39 PM, joel jaeggli wrote:
> Authors, Contributors, WG,
>
> As part of the preparation for WG Last Call:
>
> Are you aware of any IPR that applies to drafts identified above?
>
> Please state either:
>
> "No,
On 12/20/2017 4:25 PM, Martin Bjorklund wrote:
> Chairs, should I post a new version with these fixes?
Please, but only once you have addressed/closed Vladimir's comment.
Thanks,
Lou
___
netmod mailing list
netmod@ietf.org
Lou Berger has requested publication of draft-ietf-netmod-revised-datastores-08
as Proposed Standard on behalf of the NETMOD working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-netmod-revised-datastores
On 12/20/2017 07:06 AM, Juergen Schoenwaelder wrote:
> On Wed, Dec 20, 2017 at 06:25:04AM -0500, Lou Berger wrote:
>>
>> If the text above is accurate, I think something along its lined along its
>> lined should be added. If not accurate, then I think you have a ne
On December 19, 2017 3:31:34 PM Martin Bjorklund <m...@tail-f.com> wrote:
Hi Lou,
Lou Berger <lber...@labn.net> wrote:
Hi,
...
3) A minor point, the document uses the terms boot and reboot. I
suspect that these terms are intended to cover any full or partial,
e.g., proto
is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Network Modeling WG of the IETF.
>>
>> Title : YANG Tree Diagrams
>> Authors : Martin Bjorklund
>>
On 12/19/2017 7:36 AM, Ladislav Lhotka wrote:
> On Tue, 2017-12-19 at 06:43 -0500, Lou Berger wrote:
>> Hi Lada,
>>
>> On 12/19/2017 6:23 AM, Ladislav Lhotka wrote:
>>> On Tue, 2017-12-19 at 06:20 -0500, Lou Berger wrote:
>>>> Lada,
>>>>
>
Hi Lada,
On 12/19/2017 6:23 AM, Ladislav Lhotka wrote:
> On Tue, 2017-12-19 at 06:20 -0500, Lou Berger wrote:
>> Lada,
>>
>>
>> On December 19, 2017 1:12:35 AM Ladislav Lhotka <lho...@nic.cz> wrote:
>>
>>> On Mon, 2017-12-18 at 15:30 -0500, Lou
Woops that should be rw...
On December 19, 2017 6:21:22 AM Lou Berger <lber...@labn.net> wrote:
Lada,
On December 19, 2017 1:12:35 AM Ladislav Lhotka <lho...@nic.cz> wrote:
On Mon, 2017-12-18 at 15:30 -0500, Lou Berger wrote:
lada,
See below.
On 12/15/2017 8:59 AM, Lad
Lada,
On December 19, 2017 1:12:35 AM Ladislav Lhotka <lho...@nic.cz> wrote:
On Mon, 2017-12-18 at 15:30 -0500, Lou Berger wrote:
lada,
See below.
On 12/15/2017 8:59 AM, Ladislav Lhotka wrote:
> Hi,
>
> unfortunately, using an action for querying embedded YANG library
Lou Berger has requested publication of draft-ietf-netmod-entity-06 as Proposed
Standard on behalf of the NETMOD working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-netmod-entity/
___
netmod mailing list
On 12/18/2017 4:11 PM, Andy Bierman wrote:
>
>
> On Mon, Dec 18, 2017 at 1:03 PM, Lou Berger <lber...@labn.net
> <mailto:lber...@labn.net>> wrote:
>
> On 12/18/2017 04:01 PM, Andy Bierman wrote:
> >
> >
> > On Mon,
On 12/18/2017 04:01 PM, Andy Bierman wrote:
>
>
> On Mon, Dec 18, 2017 at 12:56 PM, Juergen Schoenwaelder
> <j.schoenwael...@jacobs-university.de
> <mailto:j.schoenwael...@jacobs-university.de>> wrote:
>
> On Mon, Dec 18, 2017 at 03:35:55PM -0500, Lou Be
On 12/18/2017 3:22 PM, Martin Bjorklund wrote:
> Lou Berger <lber...@labn.net> wrote:
>>
>> On 12/18/2017 3:06 PM, Juergen Schoenwaelder wrote:
>>> See RFC 3688 section 4.
>> cool, dueling BCPs.
> cool indeed.
>
>> Is there a reason
>> https
lada,
See below.
On 12/15/2017 8:59 AM, Ladislav Lhotka wrote:
> Hi,
>
> unfortunately, using an action for querying embedded YANG library data
> (needed for the "inline" case of schema mount) doesn't work either
> because now under NMDA actions can be used only on instances in the
>
On 12/18/2017 3:06 PM, Juergen Schoenwaelder wrote:
> See RFC 3688 section 4.
cool, dueling BCPs.
Is there a reason
https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-14#section-5
doesn't apply?
Lou
> /js
>
> On Mon, Dec 18, 2017 at 03:00:26PM -0500, Lou Berger wrot
Martin, Authors,
is there a reason that the draft says:
Registrant Contact: The IESG.
vs the typical:
Registrant Contact: The NETMOD WG of the IETF.
Thanks,
Lou
On 12/18/2017 4:39 AM, Martin Bjorklund wrote:
> Hi,
>
> This version addresses the WGLC comments received.
the WG know when you have published a version ready for
publication. Also please let the WG know what has changed in the
document since the start of LC (rev -01)
Thank you,
NetMod Chairs
On 11/29/2017 12:26 PM, Lou Berger wrote:
> All,
>
> This starts a two-week working group
L" in this document are to be interpreted as
described in BCP 14 [RFC2119] [RFC8174] when, and only when, they
appear in all capitals, as shown here.
Thank you
Lou (and co-chairs)
On 11/29/2017 12:35 PM, Lou Berger wrote:
> All,
>
> This starts a two-week working gr
Joel,
Welcome aboard!
Lou
On 12/15/2017 12:21 PM, Benoit Claise wrote:
> Dear all,
>
> A lot is happening these days in the world of data modeling-driven
> management at the IETF:
> NMDA architecture, NETCONF, RESTCONF
> NMDA-compliant YANG modules: some RFC bis modules but also
FYI - keep in mind that the discussion on rfc7895bis is taking place in
*netconf*...
Forwarded Message
Subject:[Netconf] Virtual Interim meeting minutes
Date: Wed, 13 Dec 2017 22:25:25 -0800
From: Mahesh Jethanandani
To: netconf
to submit to the IESG for
publication.
Thank you,
Lou
On 12/04/2017 09:35 AM, Lou Berger wrote:
> All,
>
> This starts a second working group last call on
> draft-ietf-netmod-revised-datastores.
>
> As this is a 2nd LC that is focused on changes since the last LC, it close
oot and reboot.
Thank you,
Lou
(As Shepherd)
On 12/04/2017 09:35 AM, Lou Berger wrote:
> All,
>
> This starts a second working group last call on
> draft-ietf-netmod-revised-datastores.
>
> As this is a 2nd LC that is focused on changes since the last LC, it closes
> in *one*
On 12/08/2017 06:15 AM, Juergen Schoenwaelder wrote:
>
>> In talking to some others on this topic, they suggested using a library per
>> datastore. I haven't look into this enough to know if that is a good or bad
>> idea, but it seems functionally equivalent to your first option but realized
>>
Martin,
Thanks for raising this, there's definitely some open issues as well as
confusion on this topic. In the different options listed below you say that
each datastore refers to a schema, correct? What is the mechanism you would
use to do this?
In talking to some others on this topic,
uot;?
/js
On Fri, Nov 17, 2017 at 07:36:58AM +0800, Lou Berger wrote:
Martin,
I think you are correct. We should leave as is.
I'm sure Kent/the document Shepherd makes sure whatever we do is right
before publication in any case.
Lou (as contributor)
On 11/15/2017 8:58 PM, Martin Bjork
which points to the relevant documents. A
> wiki pointing to RFCs and ID, not RFC pointing to wikis. So this does not
> affect the documents.
>
> /js
>
> PS: I am happy to add pointers to guidelines as a section to the
> wikipedia page.
>
> On Fri, Nov 17, 2017
right now, the document says standards track, Martin's proposal was to
> move to informational. So how do I parse "I think you are correct. We
> should leave as is."?
>
> /js
>
> On Fri, Nov 17, 2017 at 07:36:58AM +0800, Lou Berger wrote:
>> Martin,
>> I think y
101 - 200 of 414 matches
Mail list logo