Hi Alex,
Thanks for the updates.
I missed that the IANA Considerations (sec 8), the reference should be to RFC
6020 because that defines the YANG module registry, so please can you fix those
two references from 7950 to 6020, and also add 6020 to the normative references.
A couple of minor nits
Hi all,
Rob, thank you very much for your AD review! We have just posted a new
revision -08 taking your comments into account. Please find attached
and below my reponses to your comments (inline, delimited ;
apologies for having taken so long).
Thanks
--- Alex
Hi,
Here is my AD review for
On Mon, Mar 15, 2021 at 10:29 AM joel jaeggli wrote:
> yeah when there is an update we'll probably drop a reminder in the list
> along with a link to the diff, but unless it looks major there's not
> reason to ask for re-approval.
>
>
It is actually a much more minor change than I thought when
yeah when there is an update we'll probably drop a reminder in the list
along with a link to the diff, but unless it looks major there's not
reason to ask for re-approval.
thanks
joel
On Mon, Mar 15, 2021 at 10:26 AM Rob Wilton (rwilton)
wrote:
> Hi Andy,
>
>
>
> FYI, this issue was discussed
Hi Andy,
FYI, this issue was discussed in the Netmod session on Friday.
My interpretation of the chairs position is
(https://www.youtube.com/watch?v=glLcpQ9kpv0, starts at 6.10) is : As long as
the WG is copied on my AD review comments and proposed changes (which they have
been), then the WG h
On Fri, Mar 5, 2021 at 10:18 AM Rob Wilton (rwilton)
wrote:
> Hi Andy,
>
>
>
> I’m not sure which one you think is s a design change: Do you mean issue
> 3 or issue 4 below?
>
>
>
> I see that my response to issue 4 may not have been clear, so to clarify:
>
>
>
> By “okay”, I meant, that I am ok
Hi Andy,
I’m not sure which one you think is s a design change: Do you mean issue 3 or
issue 4 below?
I see that my response to issue 4 may not have been clear, so to clarify:
By “okay”, I meant, that I am okay with how it is written in the current draft.
My presumption is that this could be
On Fri, Mar 5, 2021 at 5:58 AM Rob Wilton (rwilton)
wrote:
> Hi Andy, authors,
>
>
>
I think you mean to address this to the WG since the redesign issues need
WG approval.
I have no objections to any changes.
Andy
> Sorry for the long delay in replying.
>
>
>
> Please see [RW] inline below
Hi Andy, authors,
Sorry for the long delay in replying.
Please see [RW] inline below …
From: Andy Bierman mailto:a...@yumaworks.com>>
Sent: 30 October 2020 01:43
To: joel jaeggli mailto:joe...@gmail.com>>
Cc: Rob Wilton (rwilton) mailto:rwil...@cisco.com>>;
draft-ietf-netmod-nmda-diff@ietf
Third attempt, this time only attached as a plain text file.
Rob
> -Original Message-
> From: Rob Wilton (rwilton)
> Sent: 02 November 2020 19:42
> To: draft-ietf-netmod-nmda-diff@ietf.org; netmod@ietf.org
> Subject: AD review of draft-ietf-netmod-nmda-diff-07 (part 2)
>
> Part 2,
Part 2, unfortunately my original email (attached) was truncated somewhere
along the way ...
The remainder of my comments are:
Suggest adding an example ", e.g., ."
o filter-spec: This is a choice between different filter constructs
to identify the portions of the datastore t
On Thu, Oct 29, 2020 at 6:09 PM joel jaeggli wrote:
> Rob,
>
> These seem like reasonable suggestions.
>
> Lets see what the authors say.
>
> Thanks for this
> joel
>
> On Thu, Oct 29, 2020 at 6:47 AM Rob Wilton (rwilton)
> wrote:
>
>> Hi,
>>
>> Here is my AD review for draft-ietf-netmod-nmda-di
Rob,
These seem like reasonable suggestions.
Lets see what the authors say.
Thanks for this
joel
On Thu, Oct 29, 2020 at 6:47 AM Rob Wilton (rwilton)
wrote:
> Hi,
>
> Here is my AD review for draft-ietf-netmod-nmda-diff-07. Apologies for
> the delay.
>
> Thank you for writing this document,
Hi,
Here is my AD review for draft-ietf-netmod-nmda-diff-07. Apologies for the
delay.
Thank you for writing this document, I think that it is useful, and looks like
it is in good shape.
Main comments:
1. Should there be any text about how to find out what datastores are supported
by a devi
14 matches
Mail list logo