All,
This last call is now closed. Since the comments
were minor, this last call is considered successful.
Authors,
Please address any/all comments received during
the LC. Once you've published the version that
you believe addresses all comments/pending changes,
I'll perform
> > > -邮件原件-
> > > 发件人: netmod [mailto:netmod-boun...@ietf.org] 代表 Kent Watsen
> > > 发送时间: 2017年11月29日 3:29
> > > 收件人: netmod@ietf.org
> > > 抄送: netmod-cha...@ietf.org
> > > 主题: [netmod] WG Last Call: draft-ietf-netmod-rfc7223bis-00
d] WG Last Call: draft-ietf-netmod-rfc7223bis-00
All,
This starts a two-week working group last call on draft-ietf-netmod-
rfc7223bis-00.
Please recall that this update's intention is to modify the YANG module to
be in line with the NMDA guidelines [1]. Reviewing the diff between the
two dr
;
Thanks,
Eric
> > -邮件原件-
> > 发件人: netmod [mailto:netmod-boun...@ietf.org] 代表 Kent Watsen
> > 发送时间: 2017年11月29日 3:29
> > 收件人: netmod@ietf.org
> > 抄送: netmod-cha...@ietf.org
> > 主题: [netmod] WG Last Call: draft-ietf-netmod-rfc7223bis-00
> >
> > All,
t Watsen
> 发送时间: 2017年11月29日 3:29
> 收件人: netmod@ietf.org
> 抄送: netmod-cha...@ietf.org
> 主题: [netmod] WG Last Call: draft-ietf-netmod-rfc7223bis-00
>
> All,
>
> This starts a two-week working group last call on
> draft-ietf-netmod-rfc7223bis-00.
>
> Pleas
_
> From: netmod <netmod-boun...@ietf.org> on behalf of Kent Watsen
> <kwat...@juniper.net>
> Sent: Wednesday, 29 November 2017 8:29 a.m.
> To: netmod@ietf.org
> Cc: netmod-cha...@ietf.org
> Subject: [netmod] WG Last Call: draft-ietf-netmod-rfc7223bis-00
>
> Al
: netmod [mailto:netmod-boun...@ietf.org] 代表 Kent Watsen
发送时间: 2017年11月29日 3:29
收件人: netmod@ietf.org
抄送: netmod-cha...@ietf.org
主题: [netmod] WG Last Call: draft-ietf-netmod-rfc7223bis-00
All,
This starts a two-week working group last call on
draft-ietf-netmod-rfc7223bis-00.
Please recall
Balazs,
the behaviour you assume is not defined in RFC 7950 and hence
everything is marked explicitely as deprecated. We had a discussion on
this, search the archives if you are interested.
I personally see an advantage with explicit deprecation marks since if
I look at an isolated definition of
Hello,
container interfaces-state is deprecated. I assume that if a container
or list is deprecated, then all its contents are also deprecated. Is
there a need to mark all leafs deprecated too?
regards Balazs
On 2017-11-28 20:29, Kent Watsen wrote:
All,
This starts a two-week working
esday, 29 November 2017 8:29 a.m.
To: netmod@ietf.org
Cc: netmod-cha...@ietf.org
Subject: [netmod] WG Last Call: draft-ietf-netmod-rfc7223bis-00
All,
This starts a two-week working group last call on
draft-ietf-netmod-rfc7223bis-00.
Please recall that this update's intention is to
modify the YANG mo
I have reviewed the draft and support publication.
Thanks,
Acee
On 11/28/17, 2:29 PM, "netmod on behalf of Kent Watsen"
wrote:
>All,
>
>This starts a two-week working group last call on
>draft-ietf-netmod-rfc7223bis-00.
>
>Please
All,
This starts a two-week working group last call on
draft-ietf-netmod-rfc7223bis-00.
Please recall that this update's intention is to
modify the YANG module to be in line with the NMDA
guidelines [1]. Reviewing the diff between the two
drafts [2] should reveal just this.
The working group
12 matches
Mail list logo