[netmod] Re: WGLC on node-tags-11

[Lou Berger]

WG,

Our general feeling is that there is not sufficient support to advance 
this work as a Standards Track document.  Please speak up if you disagree.


Thank you,

Lou and Kent

On 2/29/2024 6:06 PM, Kent Watsen wrote:

This email begins a two-week WGLC on:

https://datatracker.ietf.org/doc/html/draft-ietf-netmod-node-tags-11

Please take time to review this draft and post comments by March 14. 
 Favorable comments are especially welcomed.


Aside: this draft went through a WGLC six months ago, to which there 
were some objections.  The authors addressed the concerns here [1]. 
 Andy removed his objection here [2].


[1] 
https://mailarchive.ietf.org/arch/msg/netmod/qbB0Z-cMq_zmbNOjYT6ritZ7wxY/
[2] 
https://mailarchive.ietf.org/arch/msg/netmod/7hD9fgGGMyN_VeWyLEYGw98JA1E/



Kent  // co-chair



___
netmod mailing list -- netmod@ietf.org
To unsubscribe send an email to netmod-le...@ietf.org

[netmod] Re: Requesting WG LC for YANG module versioning and YANG Semver

[Lou Berger]

Per,

I'm not parsing your request -- if you want to present something, please 
respond to the 120 slot request...


Thanks,

Lou

On 7/4/2024 4:37 PM, Per Andersson wrote:

...
We request for this work to be included within this 10 minute time
slot to present.


[0]https://datatracker.ietf.org/doc/draft-andersson-netmod-yang-module-filename/
[1]https://mailarchive.ietf.org/arch/msg/netmod/2W9n3HalYRDwnR38oZSYgna6pGM/


--
Per

___
netmod mailing list --netmod@ietf.org
To unsubscribe send an email tonetmod-le...@ietf.org___
netmod mailing list -- netmod@ietf.org
To unsubscribe send an email to netmod-le...@ietf.org

[netmod] IETF 120 Slot Requests

[Lou Berger]

WG,

The *draft* agenda for IETF120 has been posted -
https://datatracker.ietf.org/meeting/120/agenda

We are currently scheduled to meet:
https://datatracker.ietf.org/meeting/120/session/netmod

Monday, July 22, 2024
13:00 - 15:00 (20:00 - 22:00 UTC)

Calendar: https://datatracker.ietf.org/meeting/120/sessions/netmod.ics

This will be an in-person/hybrid meeting.  As usual, we will focus on updates, 
summarizing open issues, and new topics.

IMPORTANT REMINDER:

As discussed at IETF 119 - All authors of working group documents to provided a 
status update to the WG at *every* IETF meeting. Status includes, at a minimum, 
recent changes, open issues, and plan to complete document. Status can be 
provided via:
(A) A report during the IETF session, or
(B) An e-mail to WG list, sent no later than the Internet-Draft submission 
cut-off

Please send slot requests to netmod-cha...@ietf.org before the end of the day 
Sunday, July 7 (any TZ). Please include draft names(s), presenter, desired slot 
length. Also, please let us know if you think the topic would be better covered 
in a Virtual Interim to be held at a future date.

Thank you!

Lou and Kent

Important dates:

https://datatracker.ietf.org/meeting/120/important-dates/

2024-06-26 Wednesday Cut-off date for requests to reschedule Working Group or 
BOF meetings UTC 23:59.
2024-06-28 Friday Final agenda to be published.
2024-07-08 Monday Early registration and payment cut-off at UTC 23:59.
2024-07-08 Monday Internet-Draft submission cut-off (for all Internet-Drafts, 
including -00) by UTC 23:59. Upload using the I-D Submission Tool.
2024-07-10 Wednesday Draft Working Group agendas due by UTC 23:59. Upload using 
the Meeting Materials Management Tool.
2024-07-15 Monday Registration cancellation cut-off at UTC 23:59.
2024-07-15 Monday Revised Working Group agendas due by UTC 23:59. Upload using 
the Meeting Materials Management Tool.
2024-08-16 Friday Proceedings submission cutoff date by UTC 23:59. Upload using 
the Meeting Materials Management Tool.
2024-09-09 Monday Proceedings submission corrections cutoff date by UTC 23:59.
___
netmod mailing list -- netmod@ietf.org
To unsubscribe send an email to netmod-le...@ietf.org

[netmod] Re: WG Last Call: draft-ietf-netmod-acl-extensions-06

[Lou Berger]

Med, Authors,

Thank you for the excellent update.

WG,

Please look at the differences in the documents.  I see the changes as 
editorial, but important. You may find the following helpful in 
reviewing the changes.


https://author-tools.ietf.org/iddiff?url1=draft-ietf-netmod-acl-extensions-06=draft-ietf-netmod-acl-extensions-10=--html

I intend to submit for publication in about 2 weeks -- assuming no new 
objections.


Thank you,

Lou (as Shepherd)

On 5/24/2024 10:27 AM, mohamed.boucad...@orange.com wrote:


Hi Lou,

Thank you for catching this.

Please check the candidate changes here: Diff: 
draft-ietf-netmod-acl-extensions-08.txt - 
draft-ietf-netmod-acl-extensions.txt 
<https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-netmod-acl-extensions_2=https://netmod-wg.github.io/enhanced-acl-netmod/draft-ietf-netmod-acl-extensions.txt>


Let’s know if any further change is needed.

Cheers,

Med

*De :* Lou Berger 
*Envoyé :* vendredi 24 mai 2024 14:51
*À :* BOUCADAIR Mohamed INNOV/NET ; 
draft-ietf-netmod-acl-extensi...@ietf.org
*Cc :* NetMod WG Chairs ; NETMOD Group 

*Objet :* Re: [netmod] Re: WG Last Call: 
draft-ietf-netmod-acl-extensions-06



Thank you Med/Authors!

As part of preparing my write up, I caught the following nit:

References for VLAN are missing in general, and I-SID are missing from 
the module.  I think it would be good add these. (See rfc8519 for an 
example VLAN description/reference.)


WG,

Please review the changes (see, wdiff 
draft-ietf-netmod-acl-extensions-06.txt 
draft-ietf-netmod-acl-extensions-08.txt 
<https://author-tools.ietf.org/iddiff?url1=draft-ietf-netmod-acl-extensions-06=draft-ietf-netmod-acl-extensions-08=--hwdiff>) 
and send any comments you have.  We are NOT planning an additional WG 
last call prior to submission.


Thank you,

Lou

On 5/16/2024 8:08 AM, mohamed.boucad...@orange.com wrote:

Hi Lou,

Already shared on the list how -07 addresses the pending comments from 
Mahesh and Qiufang.

I think -08 is now ready for the next step. Thanks.

Cheers,

Med

-Message d'origine-

        De : Lou Berger  <mailto:lber...@labn.net>

Envoyé : mardi 14 mai 2024 15:10

À : NETMOD Group  <mailto:netmod@ietf.org>

Cc : NetMod WG Chairs  
<mailto:netmod-cha...@ietf.org>

Objet : [netmod] Re: WG Last Call: draft-ietf-netmod-acl-

extensions-06

Hi,

The WG poll has triggered some good comment.

Authors,

Please address all comments received and publish a new version.

Please also let the WG know how each comment is addressed.

Thank you,

Lou

    On 4/29/2024 5:41 PM, Lou Berger wrote:

All,

This starts working group last call on

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2  
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252>

Fdata

tracker.ietf.org%2Fdoc%2Fdraft-ietf-netmod-acl-

extensions%2F=05%7

C02%7Cmohamed.boucadair%40orange.com%7C7c1f244274724a6ae86608dc74

1742a

d%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638512890449213291

%7CUn

known%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6I

k1haW

wiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=KqdX3A0iIOgsaznUd48b9W%2BWgh3

8ZcIu

Zvm5V6oSVSE%3D=0

The working group last call ends on May 13th.

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 publication", are welcome!

This is useful and important, even from authors.

Thank you,

Lou (Co-Chair & doc Shepherd)

___

netmod mailing list --netmod@ietf.org

To unsubscribe send an email tonetmod-le...@ietf.org




Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and 
delete this message and its attachments.

As emails may be altered, Orange is not lia

[netmod] Re: WGLC on draft-ietf-netmod-rfc8407bis

[Lou Berger]

WG, We (the chairs) remain hopeful that some might still comment on this 
document, and are extending this WG LC To help the review, please 
see 
https://author-tools.ietf.org/iddiff?url1=rfc8407=draft-ietf-netmod-rfc8407bis-11=--html 
Positive comments, e.g., "I've reviewed this document and believe it is 
ready for publication", are welcome! This is useful and important, even 
from authors. Thank you, Lou & Kent


On 5/6/2024 9:57 AM, Kent Watsen wrote:

This email begins a two-week WGLC on:

Guidelines for Authors and Reviewers of Documents Containing YANG Data 
Models

https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc8407bis/

Please take time to review this draft and post comments by May 20.
Favorable comments are especially welcomed.

No IPR has been declared for this document:
https://mailarchive.ietf.org/arch/msg/netmod/1LDpkPi_C8cqktc7HXSZgyPDCBE/

Kent & Lou (as co-chairs)






___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod___
netmod mailing list -- netmod@ietf.org
To unsubscribe send an email to netmod-le...@ietf.org

[netmod] Re: WG Last Call: draft-ietf-netmod-acl-extensions-06

[Lou Berger]

Thank you Med/Authors!

As part of preparing my write up, I caught the following nit:

References for VLAN are missing in general, and I-SID are missing from 
the module.  I think it would be good add these. (See rfc8519 for an 
example VLAN description/reference.)


WG,

Please review the changes (see, wdiff 
draft-ietf-netmod-acl-extensions-06.txt 
draft-ietf-netmod-acl-extensions-08.txt 
<https://author-tools.ietf.org/iddiff?url1=draft-ietf-netmod-acl-extensions-06=draft-ietf-netmod-acl-extensions-08=--hwdiff>) 
and send any comments you have.  We are NOT planning an additional WG 
last call prior to submission.


Thank you,

Lou


On 5/16/2024 8:08 AM, mohamed.boucad...@orange.com wrote:

Hi Lou,

Already shared on the list how -07 addresses the pending comments from Mahesh 
and Qiufang.

I think -08 is now ready for the next step. Thanks.

Cheers,
Med


-Message d'origine-
De : Lou Berger
Envoyé : mardi 14 mai 2024 15:10
À : NETMOD Group
Cc : NetMod WG Chairs
Objet : [netmod] Re: WG Last Call: draft-ietf-netmod-acl-
extensions-06

Hi,

The WG poll has triggered some good comment.

Authors,

Please address all comments received and publish a new version.
Please also let the WG know how each comment is addressed.

Thank you,
Lou


On 4/29/2024 5:41 PM, Lou Berger wrote:

All,

This starts working group last call on


https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
Fdata

tracker.ietf.org%2Fdoc%2Fdraft-ietf-netmod-acl-

extensions%2F=05%7
C02%7Cmohamed.boucadair%40orange.com%7C7c1f244274724a6ae86608dc74
1742a
d%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638512890449213291
%7CUn
known%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6I
k1haW
wiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=KqdX3A0iIOgsaznUd48b9W%2BWgh3
8ZcIu

Zvm5V6oSVSE%3D=0

The working group last call ends on May 13th.
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 publication", are welcome!
This is useful and important, even from authors.

Thank you,
Lou (Co-Chair & doc Shepherd)



___
netmod mailing list --netmod@ietf.org
To unsubscribe send an email tonetmod-le...@ietf.org


Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.
___
netmod mailing list -- netmod@ietf.org
To unsubscribe send an email to netmod-le...@ietf.org

[netmod] Re: WG Last Call: draft-ietf-netmod-acl-extensions-06

[Lou Berger]

Hi,

The WG poll has triggered some good comment.

Authors,

Please address all comments received and publish a new version.  Please 
also let the WG know how each comment is addressed.


Thank you,
Lou


On 4/29/2024 5:41 PM, Lou Berger wrote:

All,

This starts working group last call on
https://datatracker.ietf.org/doc/draft-ietf-netmod-acl-extensions/

The working group last call ends on May 13th.
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 publication", are welcome!
This is useful and important, even from authors.

Thank you,
Lou (Co-Chair & doc Shepherd)




___
netmod mailing list -- netmod@ietf.org
To unsubscribe send an email to netmod-le...@ietf.org

Re: [netmod] WGLC on system-config-05

[Lou Berger]

WG,

We'd like to extend this LC for another couple of weeks in the hope that 
we get more feedback from the WG on this document.


Positive comments, e.g., "I've reviewed this document
and believe it is ready for publication", are welcome!
This is useful and important.

Thank you,
Lou and Kent

On 3/29/2024 10:08 AM, Kent Watsen wrote:

This email begins a two-week WGLC on:

System-defined Configuration
https://datatracker.ietf.org/doc/draft-ietf-netmod-system-config/

Please take time to review this draft and post comments by April 12. 
 Favorable comments are especially welcomed.


There is no known IPR for this document:
https://mailarchive.ietf.org/arch/msg/netmod/IpzWIAbgifXoKaNfLhEDmYbyXkY/

Kent  // co-chair


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] WG Last Call: draft-ietf-netmod-acl-extensions-06

[Lou Berger]

All,

This starts working group last call on
https://datatracker.ietf.org/doc/draft-ietf-netmod-acl-extensions/

The working group last call ends on May 13th.
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 publication", are welcome!
This is useful and important, even from authors.

Thank you,
Lou (Co-Chair & doc Shepherd)


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] comments on draft-jouqui-netmod-yang-full-include

[Lou Berger]

Hi

On 3/21/2024 4:15 PM, Jean Quilbeuf wrote:

...

Many thanks for your comments, they make a lot of sense. We will work 
on it and propose a new version of the draft.


 ...

Thanks for the discussion.  One thing that would really help me, and 
perhaps others, is an example of how full include would be used.  
Perhaps showing an alternative approach to what is in RFC8529 or RFC8530?


Thanks,

Lou

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regrading IPR for draft-ietf-netmod-acl-extensions-06

[Lou Berger]

Due to the content change between the last poll on -03 and the current rev:

Authors, Contributors, WG,

As part of the renewed 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 compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
Lou (Co-Chair & doc Shepherd)

PS Please include all listed in the headers of this message in your
response.



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Draft IETF 119 NETMOD Agenda posted

[Lou Berger]

**IMPORTANT**

Authors of WG documents,

If your document has not yet been submitted to the IESG for publication 
*and* your draft is not on the agenda, please either:

(a) request to present status or
(b) send email to the list summarizing status by end of day (any TZ) 
Friday, March 15.


In either case, please include recent changes, open issues, plan to 
resolve open issues/complete the document.


Thank you!

Lou (and Kent)

On 3/7/2024 3:53 PM, Jason Sterne (Nokia) wrote:


Hello NETMOD WG,

A draft NETMOD agenda for IETF 119 has been published. Please review 
and let the chairs know if any changes are needed or additional topics 
should be covered.


The agenda is pasted below, but here's the link to the always-current 
version: 
https://datatracker.ietf.org/meeting/119/materials/agenda-119-netmod


Presenters: please provide slides to netmod-cha...@ietf.org no later 
than Sunday March 17 (any time zone).


Thanks,

Jason (+ chairs Kent and Lou)


  Draft Agenda for the NETMOD 119 WG Session

https://datatracker.ietf.org/meeting/119/materials/agenda-119-netmod
https://datatracker.ietf.org/meeting/119/session/netmod


Session:

Thursday, March 21, 2024
13:00-15:00 Brisbane (Australia - Eastern Time)
03:00-05:00 UTC
23:00-01:00 Wednesday March 20 America - Eastern Time
https://www.timeanddate.com/worldclock/converter.html?iso=20240321T03=47 
<https://www.timeanddate.com/worldclock/converter.html?iso=20240321T03=47>


Room: M2 https://datatracker.ietf.org/meeting/119/floor-plan?room=m2


WG Chairs:

Lou Berger (lberger at labs dot net)
Kent Watsen (kent plus ietf at watsen dot net)


WG Secretary

Jason Sterne (jason dot sterne at nokia dot com)


Available During Session:

MeetEcho: https://meetings.conf.meetecho.com/ietf119/?session=31987
Onsite tool: https://meetings.conf.meetecho.com/onsite119/?session=31987
Audio Only: https://mp3.conf.meetecho.com/ietf119/31987.m3u


Available During and After Session:

Notes: https://notes.ietf.org/notes-ietf-119-netmod?both
Slides: https://datatracker.ietf.org/meeting/119/session/netmod
Zulip (chat): 
https://zulip.ietf.org/#narrow/stream/126-netmod/topic/ietf-119
Drafts (TGZ): 
https://datatracker.ietf.org/meeting/119/agenda/netmod-drafts.tgz
Drafts (PDF): 
https://datatracker.ietf.org/meeting/119/agenda/netmod-drafts.pdf

Datatracker: https://datatracker.ietf.org/group/netmod/about/
ICS: https://datatracker.ietf.org/meeting/119/session/31987.ics


Available After Session:

Recording: http://www.meetecho.com/ietf119/recordings#NETMOD
Jabber Logs: https://www.ietf.org/jabber/logs/netmod


1) Session Intro & WG Status (10 min)

Presenter: Chairs


Chartered items:


  2) YANG Versioning Update (40 min)

Presenter: Rob Wilton and Joe Clarke
Draft: 
https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-module-versioning-11

Draft: https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-semver-14


Non-Chartered items:


  3) Validating anydata in YANG Library context (10 min)

Presenter: Ahmed Elhassany
Draft: 
https://datatracker.ietf.org/doc/draft-aelhassany-anydata-validation-00



  4) Philatelist and YANG time-series db (10 min)

Presenter: Jan Lindblad
Draft: https://datatracker.ietf.org/doc/draft-lindblad-tlm-philatelist-00
Draft: https://datatracker.ietf.org/doc/draft-kll-yang-label-tsdb-00


  5) A YANG model for Device Power Management (10 min)

Presenter: Tony Li
Draft: https://datatracker.ietf.org/doc/draft-li-ivy-power-01


  6) YANG Full Embed (10 min)

Presenter: Jean Quilbeuf or Benoir Claise
Draft: 
https://datatracker.ietf.org/doc/draft-jouqui-netmod-yang-full-include-01



  7) Applying COSE Signatures for YANG Data Provenance (10 min)

Presenter: Diego R. Lopez
Draft: 
https://datatracker.ietf.org/doc/draft-lopez-opsawg-yang-provenance-02



  Unallocated time: 20 min
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] WG Last Call: draft-ietf-netmod-acl-extensions-04

[Lou Berger]

WG, Authors,

Based on the low level of comments/discussion, we would like to

(a) Have the authors give a brief summary of this document during 119

(b) Start last called immediately after the meeting.

Thank you

Lou and Kent

On 12/18/2023 5:48 PM, Lou Berger wrote:

WG, Authors,

The last call has not really received sufficient responses, but we take
this as more to do with the end of the year.  We would like to rerun
this last call after the new year.

Authors,

In the interim, please take a look at the very good comments sent by
Mehesh and address them as soon as possible.  Optimally, the update
would happen by the first week of January so that we can rerun the last
call on the new version.

Thank you,

Lou and Kent

On 12/4/2023 6:00 PM, Lou Berger wrote:

All,

This starts working group last call on
https://datatracker.ietf.org/doc/draft-ietf-netmod-acl-extensions/

The working group last call ends on December 18th (any TZ).
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 publication", are welcome!
This is useful and important, even from authors.

Thank you,
Lou (Co-Chair & doc Shepherd)


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Agenda posted for Jan 23 Interim on system-config-04

[Lou Berger]

Jan,

Sorry about the confusion.  The time posted at 
https://datatracker.ietf.org/meeting/interim-2024-netmod-01/session/netmod 
is the planned meeting time.  It shows as 2024-01-23 14:00-16:00 UTC.  
For convenience add your time zone here to see local: Time Zone 
Converter – Time Difference Calculator (timeanddate.com) 



Lou

On 1/15/2024 4:03 AM, Jan Lindblad (jlindbla) wrote:

Jason, WG,

There seems to be some confusion about the exact time of this interim. Earlier 
in this thread, there was a quite elaborate table evaluating the viability of 
various times of day. In that table, one of the columns is labeled CET. Closer 
scrutiny of the time offsets in that table suggests it should probably have 
been called UTC, however.

I suppose this means that most people (outside the CET zone) have interpreted 
the agreed upon time as 2pm-4pm *UTC* (1500-1700 CET). That is also what the 
calendar invite .ics file provided in the invitation suggests.

In the invitation below, the time is given as 1600 UTC (=1700 CET). This seems 
to be two hours off. Could you please clarify what the exact time will be?

Best Regards,
/jan





On 12 Jan 2024, at 00:19, Jason Sterne 
(Nokia)  wrote:

Hello NETMOD WG,

The (short) agenda for the Jan 23 1600 UTC Virtual Interim on 
draft-ietf-netmod-system-config-04 has been posted.

Some introductory slides from the chairs are posted, but more specific meeting 
materials will follow sometime before the meeting:
https://datatracker.ietf.org/meeting/interim-2024-netmod-01/session/netmod

Calendar link (ICS):
https://datatracker.ietf.org/meeting/interim-2024-netmod-01/sessions/netmod.ics

Hope to see many of you there!

Jason (and chairs Lou and Kent)


-Original Message-
From: Kent Watsen
Sent: Tuesday, December 12, 2023 1:50 PM
To:netmod@ietf.org
Cc: Jason Sterne (Nokia); Per Andersson (perander)

Subject: Re: [netmod] Proposed date for Interim on system-config-04


CAUTION: This is an external email. Please be very careful when clicking links 
or
opening attachments. See the URL nok.it/ext for additional information.



Thank you Per for raising the concern, and Jason for dismissing it.
Since no objections are standing, we will schedule the Interim at the proposed
time.

Thanks again,
Kent (and Lou)



On Dec 5, 2023, at 10:51 AM, Jason Sterne (Nokia)

wrote:

Hi all,

After a quick poll of some weekly YANG versioning call members we think it

would be fine to leave that Jan 23rd slot to the system config interim. We can 
skip
our YANG Ver meeting that week.

Jason


-Original Message-
From: netmod  On Behalf Of Per Andersson
(perander)
Sent: Monday, December 4, 2023 7:05 PM
To: Kent Watsen;netmod@ietf.org
Subject: Re: [netmod] Proposed date for Interim on system-config-04


CAUTION: This is an external email. Please be very careful when clicking links

or

opening attachments. See the URL nok.it/ext for additional information.



Hi!

Tuesdays 3pm-4pm CET conflicts with the module versioning meetings.


--
Per


From: netmod  on behalf of Kent Watsen

Sent: Tuesday, December 5, 2023 00:18
To:netmod@ietf.org
Subject: [netmod] Proposed date for Interim on system-config-04

Dear NETMOD WG,

Following up on an action from the 118 session, the chairs would like to

schedule

an Interim meeting to discuss draft-ietf-netmod-system-config.

Considering various time-options with Qiufang, as author, it seemed that the
following 2-hour slot was best for all (see table at bottom for details):

Tue, Jan 23, 2024:
   - PST: 6am-8am
   - EST: 9am-11am
   - CET: 2pm-4pm
   - CST: 10pm-12am

Please let us know this week if there is a conflict.

Kent and Lou



CET EST PST CST
=== === === ===
10pm 5pm 2pm 6am <- maybe okay?
11pm 6pm 3pm 7am <- a little too late CET
12am 7pm 4pm 8am <- way too late CET
1am 8pm 5pm 9am <- way too late CET
2am 9pm 6pm 10am <- way too late CET
3am 10pm 7pm 11am <- way too late CET
4am 11pm 8pm 12pm <- way too early CET, a little too late EST
5am 12am 9pm 1pm <- too early CET, too late EST
6am 1am 10pm 2pm <- way too late EST
7am 2am 11pm 3pm <- way too late EST
8am 3am 12am 4pm <- way too late EST, too late PST
9am 4am 1am 5pm <- way too late EST, way too late PST
10am 5am 2am 6pm <- a little too early EST, way too late PST
11am 6am 3am 7pm <- way too early PST
12pm 7am 4am 8pm <- way too early PST
1pm 8am 5am 9pm <- a little too early PST
2pm 9am 6am 10pm <- maybe okay?

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod___
netmod mailing list

Re: [netmod] WG Last Call: draft-ietf-netmod-acl-extensions-03

[Lou Berger]

WG, Authors,

The last call has not really received sufficient responses, but we take 
this as more to do with the end of the year.  We would like to rerun 
this last call after the new year.


Authors,

In the interim, please take a look at the very good comments sent by 
Mehesh and address them as soon as possible.  Optimally, the update 
would happen by the first week of January so that we can rerun the last 
call on the new version.


Thank you,

Lou and Kent

On 12/4/2023 6:00 PM, Lou Berger wrote:

All,

This starts working group last call on
https://datatracker.ietf.org/doc/draft-ietf-netmod-acl-extensions/

The working group last call ends on December 18th (any TZ).
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 publication", are welcome!
This is useful and important, even from authors.

Thank you,
Lou (Co-Chair & doc Shepherd)


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] WG Last Call: draft-ietf-netmod-acl-extensions-03

[Lou Berger]

All,

This starts working group last call on
https://datatracker.ietf.org/doc/draft-ietf-netmod-acl-extensions/

The working group last call ends on December 18th (any TZ).
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 publication", are welcome!
This is useful and important, even from authors.

Thank you,
Lou (Co-Chair & doc Shepherd)

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] IETF118 draft minutes posted

[Lou Berger]

WG,

Draft session minutes are available at
https://datatracker.ietf.org/doc/minutes-118-netmod

Please review and send comments/corrections to the list.

Our thanks to Jason and everyone who contributed to the session and note 
taking!


Kent and Lou

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regrading IPR for draft-ietf-netmod-acl-extensions-03

[Lou Berger]

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 compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
Lou (Co-Chair & doc Shepherd)

PS Please include all listed in the headers of this message in your
response.


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Draft agenda for IETF118 NETMOD session posted

[Lou Berger]

FYI a new version of the agenda has been posted.

Presenters please provide slides by Sunday Nov 5.

Authors of WG drafts - if you are not presenting at 118, please send 
status updates to the list ASAP.


Thank you,

Lou

On 10/24/2023 3:08 PM, Jason Sterne (Nokia) wrote:

Hello NETMOD WG,



The draft agenda for the NETMOD IETF118 session has been posted -- please see:

https://datatracker.ietf.org/meeting/118/materials/agenda-118-netmod



Please let us know if you see any needed corrections or missed requests.



A large focus of the meeting will be on discussing the YANG Versioning work


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] WG adoption call: draft-boucadair-netmod-rfc8407bis-02

[Lou Berger]

WG

This document is adopted.

Authors,

Please resubmit with only the name changed to draft-ietf-netmod-rfc8407bis

Thank you!

Lou (and Kent)

On 9/11/2023 6:22 PM, Lou Berger wrote:


Hello,

This email begins a 2-week adoption poll for:
https://datatracker.ietf.org/doc/draft-boucadair-netmod-rfc8407bis/

Please voice your support or technical objections to adoption on the
list by the end of the day (any time zone) Sept 25.

Thank you,
Lou (as Co-chair)


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Poll on YANG Versioning NBC Approach

[Lou Berger]

WG,

Based on the very good discussion on list and the opinions recorded on 
the poll, the Chairs want to state that the WG has agreed to:


"OPTION 1. Publish an RFC based on 
draft-ietf-netmod-yang-module-versioning that updates both YANG 1.0 (RFC 
6020) and YANG 1.1 (RFC 7950) to allow YANG modules to be modified with 
non-backwards-compatible changes – This option does not change the YANG 
version number."


There remain open issues from the last call and there continues to be be 
good discussion on the poll and related to the document. We look to the 
document Editors to continue to move the document to address the open 
issues and gauge their understanding of WG position on this document. 
Once the document is ready, there will be an additional, and hopefully 
final, WG LC.


Kent and Lou

On 9/11/2023 6:39 PM, Kent Watsen wrote:

WG,

Please help the YANG-versioning effort move forward by participating 
in the following poll:


  - https://notes.ietf.org/netmod-2023-sept-poll (Datatracker login 
required)


Kent and Lou


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] WG adoption call: draft-boucadair-netmod-rfc8407bis-02

[Lou Berger]

Hello,

This email begins a 2-week adoption poll for: 
https://datatracker.ietf.org/doc/draft-boucadair-netmod-rfc8407bis/


Please voice your support or technical objections to adoption on the
list by the end of the day (any time zone) Sept 25.

Thank you,
Lou (as Co-chair)

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regarding IPR on draft-boucadair-netmod-rfc8407bis-02

[Lou Berger]

Authors, Contributors, WG,

In 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 disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the above by responding to this email regardless of 
whether or not you are aware of any relevant IPR. This document will not 
advance to the next stage until a response has been received from each 
author.


NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see
https://www.ietf.org/standards/ipr/

Thank you,
Lou (Co-Chair)

PS Please include all listed in the headers of this message in your
response.


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] WGLC on node-tags-09

[Lou Berger]

Authors,

I may have missed it, but was the point below addressed?

On 7/3/2023 2:23 PM, Andy Bierman wrote:

YANG authors should not need to tag nodes with specific metrics at all.
I am not convinced that standard tags like "counter," or "loss," or 
"delay" are useful.

IMO it would be better to keep standard tags in their own RFC(s),
especially something as complicated as metrics classification.


As contributor, I too have a hard time seeing the value of having tags 
that map directly to attributes such as  delay, jitter, and loss - I'd 
expect the tags to map to classes not instances of attributes.


From a process perspective, can you explain why references in IETF 
tags, section 9.2, are not *normative*? (note some are not even lisyted 
in the references section.)


Thanks,

Lou

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] YANG Versioning: Key Issue #1 - Allow NBC changes in YANG 1.0 & YANG 1.1 or not?

[Lou Berger]

Jurgen,

I/we certainly agree that discussion plays an important role in reaching 
consensus. We've reserved an hour for related discussion - which we are looking 
to set the stage for further discussions to close on the open points raised 
during LC.

Again for your comments to the group on this topic,
Lou and Kent

--
On July 17, 2023 2:50:00 PM Jürgen Schönwälder 
 wrote:

Dear Jason,

the three options come with a bunch of details that make it hard to
support any of them. I think what is needed is a dialog, not a choice
of given options (for a yet to be determined set of issues and options
to come).

/js

On Mon, Jul 17, 2023 at 05:52:00PM +, Jason Sterne (Nokia) wrote:

Hi all,

At the request of the NETMOD chairs, and on behalf of the YANG Versioning 
weekly call group, here's a summary of Key Issue #1 for the versioning work 
(i.e. for the Module Versioning and YANG Semver WGLC).

We'd like to suggest that the WG has a strong focus on deciding on this 
specific issue first. Then we'll move on to tackle other key issues. The idea 
is to try and avoid getting tangled in a web of multiple intertwined issues.

Key Issue #1 is the following:  Allow NBC changes in YANG 1.0 & YANG 1.1 or not?

For now please avoid debating other issues in this thread (e.g. multiple vs 
single label schemes, whether YANG semver is a good scheme, etc). Let's focus 
on K1 and work towards a WG decision.

###
K1) Allow NBC changes in YANG 1.0 & YANG 1.1 or not?

Option 1 - Update RFC7950 to Allow NBC Changes
---
- Module Versioning modifies 7950 to allow NBC changes
- guidance that NBC changes SHOULD NOT be done (impact to user base)
- rev:non-backwards-compatible is a YANG extension
- introduction in published YANG does not impact current tooling (ignored until 
recognized)
PROS:
- address fundamental requirement of this versioning work (requirements doc)
- allows gradual adoption in the industry. YANG authors can immeditately start 
publishing with the new extensions.
- move faster to produce modules in the IETF (accept some errors/iteration)
- address the liaison from external standards bodies in a reasonable timeframe
- authors believe work is ready
- broad vendor support
- rough alignment with OpenConfig (use YANG 1.0 + OC Semver)
CONS:
- perception that we're "cheating" by not bumping our own spec's version
- Not fundamentally mandatory for clients or servers using YANG (mandatory for 
YANG claiming conformance to Module Versioning).

Option 2 - RFC7950-bis: Publish a new version of the YANG language to allow NBC 
changes
---
- NBC changes only allowed in a new (future) version of YANG
- TBD: YANG 1.2 vs 2.0 (note YANG 1.1 isn't BC with YANG 1.0)
- Content = Module Versioning + YANG Semver + very limited YANG NEXT items
- rev:non-backwards-compatible tag is a language keyword
- consequence: any use of it breaks all YANG 1.0/1.1 tooling that hasn't been 
updated
- TBD how to handle small NBC changes in IETF in the short term (i.e. non 
conformance to 7950)?
- RFC6991 bis - change the use/meaning of ip-address (or change datetime)
   - YANG date-and-time (because of SEDATE date string changes)

PROS:
- address fundamental requirement of this versioning work (requirements doc)
- clear delineation of changes in the YANG language
- consistent with philosophy that version number changes for significant 
changes in a spec (avoids concern that YANG is changing without bumping the 
version of YANG)
- can do this with mandatory YANG keywords which helps increase conformance to 
the new rules
CONS:
- difficult to roll out in the industry. Tools need upgrading before they won't 
error on a YANG 1.2 module.
- Authors can't publish YANG 1.2 until their users have upgraded their tools. 
Everyone has to move at once.
- likely large delay in producing the work (unclear what would go into YANG 
1.2, may not reach concensus easily on N items)
- delay in follow up work (Packages, Schema Comparison, Version Selection)
- continue dominating WG effort for longer (opportunity cost)

Option 3 - Strict Adherence to Current RFC7950 Rules
---
- IESG will be unable to approve any RFCs that make any changes to IETF YANG 
modules that don't strictly conform to those rules
- RFC6991 bis would not be allowed to change the use/meaning of ip-address (or 
change datetime)
   - YANG date-and-time couldn't change (related to SEDATE date string 
changes)
PROS:
- clear rules for entire industry including IETF
CONS:
- doesn't address agreed/adopted requirements of YANG versioning work
- incorrect assumption in tool chains, etc that NBC changes don't happen. 
Silent failures.

Jason (he/him)


___
netmod mailing list
netmod@ietf.org

Re: [netmod] Call for IETF 117 Slot Requests

[Lou Berger]

A revised agenda has been posted - please review and please let us know 
if you see any needed corrections or (more) missed requests.


Thank you

On 7/12/2023 6:42 PM, Lou Berger wrote:

All,
The draft agenda has been posted -- please see:
https://datatracker.ietf.org/meeting/117/materials/agenda-117-netmod

Please let us know if you see any needed corrections or missed requests.

The main focus of the meeting will be on discussing/getting input on the
WGLC on "semver" and "module-versioning" drafts, see the thread at
https://mailarchive.ietf.org/arch/msg/netmod/3OTBmzoZUkv4X8Kpjous4Hu7uI0/

To authors of WG documents not on the agenda, please send a status
update to the list by COB July 21. Please include planned next steps and
open issue.

Thank you,

Lou (Kent and Jason)




___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Call for IETF 117 Slot Requests

[Lou Berger]

All,
The draft agenda has been posted -- please see:
https://datatracker.ietf.org/meeting/117/materials/agenda-117-netmod

Please let us know if you see any needed corrections or missed requests.

The main focus of the meeting will be on discussing/getting input on the 
WGLC on "semver" and "module-versioning" drafts, see the thread at 
https://mailarchive.ietf.org/arch/msg/netmod/3OTBmzoZUkv4X8Kpjous4Hu7uI0/


To authors of WG documents not on the agenda, please send a status 
update to the list by COB July 21. Please include planned next steps and 
open issue.


Thank you,

Lou (Kent and Jason)


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Updated IETF116 NETMOD Agenda posted

[Lou Berger]

Hi charles,
We made the choice to not have it on the agenda because the agenda was so tight 
and to only mention it in the chair slides. If there's something you'd like to 
say about the liaison please feel free to come up to the mic when that side is 
shown.

Thanks
Lou



On March 29, 2023 6:48:20 PM "Charles Eckel (eckelcu)"  
wrote:

Hi Chairs,

I see this LS from SA5, https://datatracker.ietf.org/liaison/1818/

Are you planning to cover it during the chairs intro? If not, would it be 
possible to add it to the agenda?

Thanks,
Charles

On Mar 29, 2023, at 12:09 AM, Jason Sterne (Nokia) 
mailto:jason.ste...@nokia.com>> wrote:

Hello NETMOD WG,

We have a number of additional topics on the IETF116 NETMOD agenda. You can 
find the latest here:
https://datatracker.ietf.org/meeting/116/materials/agenda-116-netmod

Jason (he/him)

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Regarding IPR on draft-ietf-netmod-yang-module-versioning-08

[Lou Berger]

Authors/All,

One of the authors pointed out that the list of contributors was 
incomplete, and specifically didn't include all listed in the paragraph 
of the contributors section.  We had mistakenly read this paragraph as 
Acknowledgments versus Contributors.  It does appear that some of those 
listed may be Contributors, i.e., materially contributed to the 
technical solution or the text (excluding editorial changes),  while 
others may in fact belong in an Acknowledgement section.  Given this, 
we'd like to ask the authors to refactor the Contributors section into 
separate Acknowledgement and Contributor sections before moving forward 
on this document.  Once we have the new version, we can then judge if 
there are any missing IPR statements.


Thank you,

Lou and Kent

On 1/16/2023 5:53 PM, Lou Berger wrote:

Authors, Contributors, WG,

In preparation for 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 compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see
https://www.ietf.org/standards/ipr/

Thank you,
Lou and Kent

PS Please include all listed in the headers of this message in your
response.




___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Regarding IPR on draft-ietf-netmod-yang-module-versioning-08

[Lou Berger]

I believe we are just missing a response from Ebben.

Lou

--
On February 16, 2023 2:07:20 PM Lou Berger  wrote:

Authors, contributors,

As far as I tell those on the to line and listed below have not
responded to the IPR poll.  Either way, can the following please
respond, even if doing so again:
Ebben Aries
Juergen Schoenwaelder
Mahesh Jethanandani
Michael (Wangzitao)
Jason Sterne

Thank you,

Lou

On 1/16/2023 5:53 PM, Lou Berger wrote:

Authors, Contributors, WG,

In preparation for 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 compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see
https://www.ietf.org/standards/ipr/

Thank you,
Lou and Kent

PS Please include all listed in the headers of this message in your
response.
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Regarding IPR on draft-ietf-netmod-yang-module-versioning-08

[Lou Berger]

Authors, contributors,

As far as I tell those on the to line and listed below have not 
responded to the IPR poll.  Either way, can the following please 
respond, even if doing so again:

    Ebben Aries
    Juergen Schoenwaelder
    Mahesh Jethanandani
    Michael (Wangzitao)
    Jason Sterne

Thank you,

Lou

On 1/16/2023 5:53 PM, Lou Berger wrote:

Authors, Contributors, WG,

In preparation for 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 compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see
https://www.ietf.org/standards/ipr/

Thank you,
Lou and Kent

PS Please include all listed in the headers of this message in your
response.




___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Fwd: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08

[Lou Berger]

Forwarding - this didn't make it into the archive...

 Forwarded Message 
Subject:RE: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08
Date:   Tue, 17 Jan 2023 18:12:37 +
From:   Balázs Lengyel 
To: 	Lou Berger , benoit.cla...@huawei.com 
, lana.w...@huawei.com , 
e...@juniper.net , lind...@cisco.com 
, j.shoenwael...@jacobs-university.de 
, mjethanand...@gmail.com 
, wangzi...@huawei.com , 
peran...@cisco.com , bill...@huawei.com 
, rwil...@cisco.com , 
res...@yahoo.com , jcla...@cisco.com 
, jason.ste...@nokia.com 
CC: 	NetMod WG Chairs , NETMOD Group 





"No, I'm not aware of any IPR that applies to this draft"
Balazs

-Original Message-----
From: Lou Berger  Sent: Monday, 16 January, 2023 23:53
To: benoit.cla...@huawei.com; lana.w...@huawei.com; e...@juniper.net; 
lind...@cisco.com; j.shoenwael...@jacobs-university.de; 
mjethanand...@gmail.com; wangzi...@huawei.com; peran...@cisco.com; 
bill...@huawei.com; rwil...@cisco.com; res...@yahoo.com; Balázs Lengyel 
; jcla...@cisco.com; jason.ste...@nokia.com
Cc: NetMod WG Chairs ; NETMOD Group 


Subject: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08


Authors, Contributors, WG,

In preparation for 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 compliance with IETF IPR rules 
(see RFCs 3669, 5378 and 8179 for more details)?


If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think 
appropriate. If you are listed as a document author or contributor 
please answer the above by responding to this email regardless of 
whether or not you are aware of any relevant IPR. This document will not 
advance to the next stage until a response has been received from each 
author.


NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed 
as an author or contributor, we remind you of your obligations under the 
IETF IPR rules which encourages you to notify the IETF if you are aware 
of IPR of others on an IETF contribution, or to refrain from 
participating in any contribution or discussion related to your 
undisclosed IPR. For more information, please see 
https://www.ietf.org/standards/ipr/


Thank you,
Lou and Kent

PS Please include all listed in the headers of this message in your 
response.
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Fwd: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08

[Lou Berger]

Forwarding - this didn't make it into the archive...


 Forwarded Message 
Subject:Re: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08
Date:   Tue, 17 Jan 2023 14:06:36 +
From:   Joe Clarke (jclarke) 
To: 	Lou Berger , benoit.cla...@huawei.com 
, lana.w...@huawei.com , 
e...@juniper.net , lind...@cisco.com 
, j.shoenwael...@jacobs-university.de 
, mjethanand...@gmail.com 
, wangzi...@huawei.com , 
Per Andersson (perander) , bill...@huawei.com 
, Rob Wilton (rwilton) , 
res...@yahoo.com , balazs.leng...@ericsson.com 
, jason.ste...@nokia.com 

CC: 	NetMod WG Chairs , NETMOD Group 





"No, I'm not aware of any IPR that applies to this draft"

Joe

*From: *Lou Berger 
*Date: *Monday, January 16, 2023 at 17:53
*To: *benoit.cla...@huawei.com , 
lana.w...@huawei.com , e...@juniper.net 
, lind...@cisco.com , 
j.shoenwael...@jacobs-university.de 
, mjethanand...@gmail.com 
, wangzi...@huawei.com , 
Per Andersson (perander) , bill...@huawei.com 
, Rob Wilton (rwilton) , 
res...@yahoo.com , balazs.leng...@ericsson.com 
, Joe Clarke (jclarke) , 
jason.ste...@nokia.com 
*Cc: *NetMod WG Chairs , NETMOD Group 


*Subject: *Regarding IPR on draft-ietf-netmod-yang-module-versioning-08


Authors, Contributors, WG,

In preparation for 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 compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see
https://www.ietf.org/standards/ipr/

Thank you,
Lou and Kent

PS Please include all listed in the headers of this message in your
response.
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Fwd: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08

[Lou Berger]

Forwarding - this didn't make it into the archive...


 Forwarded Message 
Subject:Re: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08
Date:   Tue, 17 Jan 2023 13:58:19 + (UTC)
From:   Reshad Rahman 
Reply-To:   Reshad Rahman 
To: 	benoit.cla...@huawei.com , 
lana.w...@huawei.com , e...@juniper.net 
, lind...@cisco.com , 
j.shoenwael...@jacobs-university.de 
, mjethanand...@gmail.com 
, wangzi...@huawei.com , 
peran...@cisco.com , bill...@huawei.com 
, rwil...@cisco.com , 
balazs.leng...@ericsson.com , 
jcla...@cisco.com , jason.ste...@nokia.com 
, Lou Berger 
CC: 	NetMod WG Chairs , NETMOD Group 





No, I'm not aware of any IPR that applies to this draft.

Regards,
Reshad.

On Monday, January 16, 2023, 05:53:12 PM EST, Lou Berger 
 wrote:




Authors, Contributors, WG,

In preparation for 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 compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see
https://www.ietf.org/standards/ipr/

Thank you,
Lou and Kent

PS Please include all listed in the headers of this message in your
response.

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Fwd: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08

[Lou Berger]

Forwarding - this didn't make it into the archive...



 Forwarded Message 
Subject:RE: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08
Date:   Tue, 17 Jan 2023 10:18:03 +
From:   Rob Wilton (rwilton) 
To: 	Lou Berger , benoit.cla...@huawei.com 
, lana.w...@huawei.com , 
e...@juniper.net , lind...@cisco.com 
, j.shoenwael...@jacobs-university.de 
, mjethanand...@gmail.com 
, wangzi...@huawei.com , 
Per Andersson (perander) , bill...@huawei.com 
, res...@yahoo.com , 
balazs.leng...@ericsson.com , Joe Clarke 
(jclarke) , jason.ste...@nokia.com 

CC: 	NetMod WG Chairs , NETMOD Group 





"No, I'm not aware of any IPR that applies to this draft"

Regards,
Rob



-Original Message-----
From: Lou Berger 
Sent: 16 January 2023 22:53
To: benoit.cla...@huawei.com; lana.w...@huawei.com; e...@juniper.net;
lind...@cisco.com; j.shoenwael...@jacobs-university.de;
mjethanand...@gmail.com; wangzi...@huawei.com; Per Andersson
(perander) ; bill...@huawei.com; Rob Wilton (rwilton)
; res...@yahoo.com; balazs.leng...@ericsson.com; Joe
Clarke (jclarke) ; jason.ste...@nokia.com
Cc: NetMod WG Chairs ; NETMOD Group

Subject: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08


Authors, Contributors, WG,

In preparation for 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 compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see
https://www.ietf.org/standards/ipr/

Thank you,
Lou and Kent

PS Please include all listed in the headers of this message in your
response.

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Fwd: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08

[Lou Berger]

Forwarding - this didn't make it into the archive...

 Forwarded Message 
Subject: 	Re: [netmod] Regarding IPR on 
draft-ietf-netmod-yang-module-versioning-08

Date:   Tue, 17 Jan 2023 11:52:17 +
From:   Jan Lindblad (jlindbla) 
To: Lou Berger 
CC: 	Benoit Claise , Wubo (lana) 
, e...@juniper.net , 
lind...@cisco.com , 
j.shoenwael...@jacobs-university.de 
, Mahesh Jethanandani 
, wangzi...@huawei.com , 
Per Andersson (perander) , Qin Wu 
, Rob Wilton (rwilton) , Reshad 
Rahman , Balazs Lengyel , 
Joe Clarke (jclarke) , Jason Sterne (Nokia) 
, NetMod WG Chairs , 
NETMOD Group 




No, I'm not aware of any IPR that applies to this draft

/Jan Lindblad


On 16 Jan 2023, at 23:53, Lou Berger  wrote:


Authors, Contributors, WG,

In preparation for 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 compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see
https://www.ietf.org/standards/ipr/

Thank you,
Lou and Kent

PS Please include all listed in the headers of this message in your
response.


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Fwd: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08

[Lou Berger]

Forwarding - this didn't make it into the archive...



 Forwarded Message 
Subject:Re: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08
Date:   Tue, 17 Jan 2023 08:52:27 +0100
From:   Benoit Claise 
To: 	Lou Berger , lana.w...@huawei.com, 
e...@juniper.net, lind...@cisco.com, j.shoenwael...@jacobs-university.de, 
mjethanand...@gmail.com, wangzi...@huawei.com, peran...@cisco.com, 
bill...@huawei.com, rwil...@cisco.com, res...@yahoo.com, 
balazs.leng...@ericsson.com, jcla...@cisco.com, jason.ste...@nokia.com
CC: 	NetMod WG Chairs , NETMOD Group 





No, I'm not aware of any IPR that applies to this draft.

Regards, Benoit



On 1/16/2023 11:53 PM, Lou Berger wrote:

Authors, Contributors, WG,

In preparation for 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 compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see
https://www.ietf.org/standards/ipr/

Thank you,
Lou and Kent

PS Please include all listed in the headers of this message in your
response.


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Fwd: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08

[Lou Berger]

Forwarding - this didn't make it into the archive...

 Forwarded Message 
Subject:RE: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08
Date:   Tue, 17 Jan 2023 01:22:26 +
From:   Wubo (lana) 
To: 	Lou Berger , Benoit Claise 
, e...@juniper.net , 
lind...@cisco.com , 
j.shoenwael...@jacobs-university.de 
, mjethanand...@gmail.com 
, wangzitao , 
peran...@cisco.com , Qin Wu , 
rwil...@cisco.com , res...@yahoo.com 
, balazs.leng...@ericsson.com 
, jcla...@cisco.com , 
jason.ste...@nokia.com 
CC: 	NetMod WG Chairs , NETMOD Group 





No, I'm not aware of any IPR that applies to this draft.

Bo Wu

-Original Message-
From: Lou Berger [mailto:lber...@labn.net] Sent: Tuesday, January 17, 
2023 6:53 AM
To: Benoit Claise ; Wubo (lana) 
; e...@juniper.net; lind...@cisco.com; 
j.shoenwael...@jacobs-university.de; mjethanand...@gmail.com; wangzitao 
; peran...@cisco.com; Qin Wu ; 
rwil...@cisco.com; res...@yahoo.com; balazs.leng...@ericsson.com; 
jcla...@cisco.com; jason.ste...@nokia.com
Cc: NetMod WG Chairs ; NETMOD Group 


Subject: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08


Authors, Contributors, WG,

In preparation for 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 compliance with IETF IPR rules 
(see RFCs 3669, 5378 and 8179 for more details)?


If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think 
appropriate. If you are listed as a document author or contributor 
please answer the above by responding to this email regardless of 
whether or not you are aware of any relevant IPR. This document will not 
advance to the next stage until a response has been received from each 
author.


NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed 
as an author or contributor, we remind you of your obligations under the 
IETF IPR rules which encourages you to notify the IETF if you are aware 
of IPR of others on an IETF contribution, or to refrain from 
participating in any contribution or discussion related to your 
undisclosed IPR. For more information, please see 
https://www.ietf.org/standards/ipr/


Thank you,
Lou and Kent

PS Please include all listed in the headers of this message in your 
response.


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Fwd: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08

[Lou Berger]

Forwarding - this didn't make it into the archive...



 Forwarded Message 
Subject:RE: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08
Date:   Tue, 17 Jan 2023 01:13:43 +
From:   Qin Wu 
To: 	Jason Sterne (Nokia) , Lou Berger 
, Benoit Claise , Wubo 
(lana) , e...@juniper.net , 
lind...@cisco.com , 
j.shoenwael...@jacobs-university.de 
, mjethanand...@gmail.com 
, wangzitao , 
peran...@cisco.com , rwil...@cisco.com 
, res...@yahoo.com , 
balazs.leng...@ericsson.com , 
jcla...@cisco.com 
CC: 	NetMod WG Chairs , NETMOD Group 





No, I'm not aware of any IPR that applies to this draft.

Qin
-邮件原件-
发件人: Jason Sterne (Nokia) [mailto:jason.ste...@nokia.com] 发送时间: 
2023年1月17日 6:55
收件人: Lou Berger ; Benoit Claise 
; Wubo (lana) ; 
e...@juniper.net; lind...@cisco.com; j.shoenwael...@jacobs-university.de; 
mjethanand...@gmail.com; wangzitao ; 
peran...@cisco.com; Qin Wu ; rwil...@cisco.com; 
res...@yahoo.com; balazs.leng...@ericsson.com; jcla...@cisco.com
抄送: NetMod WG Chairs ; NETMOD Group 


主题: RE: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08

Hello WG and Chairs,
No, I'm not aware of any IPR that applies to this draft.
Jason


-Original Message-
From: Lou Berger 
Sent: Monday, January 16, 2023 5:53 PM
To: benoit.cla...@huawei.com; lana.w...@huawei.com; e...@juniper.net; 
lind...@cisco.com; j.shoenwael...@jacobs-university.de;
mjethanand...@gmail.com; wangzi...@huawei.com; peran...@cisco.com; 
bill...@huawei.com; rwil...@cisco.com; res...@yahoo.com; 
balazs.leng...@ericsson.com; jcla...@cisco.com; Jason Sterne (Nokia) 

Cc: NetMod WG Chairs ; NETMOD Group 


Subject: Regarding IPR on draft-ietf-netmod-yang-module-versioning-08


Authors, Contributors, WG,

In preparation for 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 compliance with IETF IPR rules 
(see RFCs 3669, 5378 and 8179 for more details)?


If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think 
appropriate. If you are listed as a document author or contributor 
please answer the above by responding to this email regardless of 
whether or not you are aware of any relevant IPR. This document will 
not advance to the next stage until a response has been received from 
each author.


NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not 
listed as an author or contributor, we remind you of your obligations 
under the IETF IPR rules which encourages you to notify the IETF if 
you are aware of IPR of others on an IETF contribution, or to refrain 
from participating in any contribution or discussion related to your 
undisclosed IPR. For more information, please see 
https://www.ietf.org/standards/ipr/


Thank you,
Lou and Kent

PS Please include all listed in the headers of this message in your 
response.


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regarding IPR on draft-ietf-netmod-yang-module-versioning-08

[Lou Berger]

Authors, Contributors, WG,

In preparation for 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 compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see
https://www.ietf.org/standards/ipr/

Thank you,
Lou and Kent

PS Please include all listed in the headers of this message in your
response.


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] WG adoption call: draft-dbb-netmod-acl-03

[Lou Berger]

Hi,

This poll is closed.  Authors please republish the draft with a 'file 
name' of draft-ietf-netmod-acl-00 and only this and the date changed. 
Please then work to address adoption comments in rev -01.


Thank you,
Lou and Kent


On 12/19/2022 6:00 PM, Lou Berger wrote:

Hello,

This email begins a 3-week adoption poll for:
https://datatracker.ietf.org/doc/draft-dbb-netmod-acl/

Please voice your support or technical objections to adoption on the
list by the end of the day (any time zone) January 9.

This is an extended call due to the holiday/New Year.

Thank you,
Lou (as Co-chair)



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] WG adoption call: draft-dbb-netmod-acl-03

[Lou Berger]

Hello,

This email begins a 3-week adoption poll for: 
https://datatracker.ietf.org/doc/draft-dbb-netmod-acl/


Please voice your support or technical objections to adoption on the
list by the end of the day (any time zone) January 9.

This is an extended call due to the holiday/New Year.

Thank you,
Lou (as Co-chair)

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Regarding IPR on draft-dbb-netmod-acl-03

[Lou Berger]

On 12/12/2022 1:28 AM, mohamed.boucad...@orange.com wrote:

Hi Kent, all,

Samier has already replied. Please see attached.

Cheers,
Med

Forwarding to list -- attachment was stripped from archive...

 Forwarded Message 
Subject: RE: Regarding IPR on draft-dbb-netmod-acl-03
Date: Wed, 7 Dec 2022 08:23:22 +
From: Samier Barguil Giraldo (Nokia) 
To: NetMod WG Chairs 
CC: NETMOD Group , Oscar González de Dios 
, BOUCADAIR Mohamed INNOV/NET 



Dear NETMOD WG chairs, all,

No, I'm not aware of any IPR that applies to this draft.

Regards,

Samier

-Original Message-
From: Oscar González de Dios 
Sent: Tuesday, December 6, 2022 7:16 PM
To: mohamed.boucad...@orange.com; Lou Berger ; Samier 
Barguil Giraldo (Nokia) 
Cc: NetMod WG Chairs ; NETMOD Group 


Subject: RE: Regarding IPR on draft-dbb-netmod-acl-03

Dear NETMOD WG chairs, all,

No, I'm not aware of any IPR that applies to this draft.

Our co-author Samier has changed affiliation. I add his new email in the 
loop so he can answer to the IPR poll.


Best Regards,

Oscar

-Mensaje original-
De: mohamed.boucad...@orange.com  Enviado 
el: martes, 6 de diciembre de 2022 7:41
Para: Lou Berger ; Oscar González de Dios 
; SAMIER BARGUIL GIRALDO 

CC: NetMod WG Chairs ; NETMOD Group 


Asunto: RE: Regarding IPR on draft-dbb-netmod-acl-03

Hi Lou, all,

No, I'm not aware of any IPR that applies to this draft.

Cheers,
Med

-Message d'origine-  > De : Lou Berger  > Envoyé : lundi 5 décembre 2022 
23:51 > À : OSCAR GONZALEZ DE DIOS 
; > 
samier.barguilgiraldo@telefonica.com; BOUCADAIR Mohamed INNOV/NET > 
 Cc : NetMod WG Chairs > 
; NETMOD Group  Objet : > 
Regarding IPR on draft-dbb-netmod-acl-03 > > Authors, Contributors, WG, 
> > In 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 
disclosed in compliance with IETF IPR rules > (see RFCs 3669, 5378 and 
8179 for more details)? > > If yes to the above, please state either: > 
> "Yes, the IPR has been disclosed in compliance with IETF IPR rules" > 
or > "No, the IPR has not been disclosed" > > If you answer no, please 
provide any additional details you think > appropriate. If you are 
listed as a document author or contributor > please answer the above by 
responding to this email regardless of > whether or not you are aware of 
any relevant IPR. This document will > not advance to the next stage 
until a response has been received from > each author. > > NOTE: THIS 
APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES. > > If you are 
on the WG email list or attend WG meetings but are not > listed as an 
author or contributor, we remind you of your obligations > under the 
IETF IPR rules which encourages you to notify the IETF if > you are 
aware of IPR of others on an IETF contribution, or to refrain > from 
participating in any contribution or discussion related to your > 
undisclosed IPR. For more information, please see > 
https://www.ietf.org/standards/ipr/ > > Thank you, > Lou and Kent > > PS 
Please include all listed in the headers of this message in your > 
response. >
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] The NETMOD WG has placed draft-dbb-netmod-acl in state "Candidate for WG Adoption"

[Lou Berger]

No, a formal adoption call is forthcoming. We just started the process with the 
ior call, updated the data tracker and it sent the mail.  Stay tuned...

Lou



On December 6, 2022 6:57:53 PM Mahesh Jethanandani  
wrote:

Is this in-lieu of a call for adoption, or did I somehow miss the call for 
adoption? I do see a separate IPR call.

Either ways, I do support the work, whether as a separate draft or as a bis of 
the original work. Would have preferred the latter, if not for anything else 
but to see how a YANG model can be updated in IETF.

Cheers.

On Dec 5, 2022, at 2:41 PM, IETF Secretariat 
mailto:ietf-secretariat-re...@ietf.org>> wrote:


The NETMOD WG has placed draft-dbb-netmod-acl in state
Candidate for WG Adoption (entered by Lou Berger)

The document is available at
https://datatracker.ietf.org/doc/draft-dbb-netmod-acl/


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod


Mahesh Jethanandani
mjethanand...@gmail.com<mailto:mjethanand...@gmail.com>






___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regarding IPR on draft-dbb-netmod-acl-03

[Lou Berger]

Authors, Contributors, WG,

In 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 disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see
https://www.ietf.org/standards/ipr/

Thank you,
Lou and Kent

PS Please include all listed in the headers of this message in your
response.


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] IETF 115 Slot Requests

[Lou Berger]

WG,

The *draft* agenda for IETF115 has been posted -
https://datatracker.ietf.org/meeting/115/agenda

The NetMod session information is scheduled to be held:

   Tuesday, November 8, 2022
   09:30-11:30 Tuesday Session I
   Richmond 4
   https://datatracker.ietf.org/meeting/115/sessions/netmod.ics

This will be a (new) normal in-person with remote participation meeting.

Please send slot requests to netmod-cha...@ietf.org before the end of 
the day Monday October 24 (any TZ, but earlier is appreciated).  Please 
include draft names(s), presenter, desired slot length.  Also, please 
let us know if you think the topic would be better covered in a Virtual 
Interim to be held at a future date.


Thank you!

Lou (Kent and Joel)

Important dates:

IETF 115
2022-11-05, London, GB
DateWeekday Description
2022-10-12  Wednesday   Cut-off date for requests to reschedule
Working Group or BOF meetings UTC 23:59
2022-10-14  Friday  Final agenda to be published
2022-10-24  Monday  Internet Draft submission cut-off (for all
drafts, including -00) by UTC 23:59 Upload
using the ID Submission Tool.
2022-10-24  Monday  Standard rate registration and payment cut-off
at UTC 23:59.
2022-10-26  Wednesday   Draft Working Group agendas due by UTC
23:59 Upload using the Meeting Materials
Management Tool.
2022-10-31  Monday  Registration cancellation cut-off at UTC 23:59
2022-10-31  Monday  Revised Working Group agendas due by UTC 23:59
Upload using the Meeting Materials Management
Tool.
2022-12-02  Friday  Proceedings submission cutoff date by UTC 23:59
Upload using the Meeting Materials Management
Tool.
2022-12-26  Monday  Proceedings submission corrections cutoff date
by UTC 23:59

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] What's the plan with draft-ietf-netmod-node-tags

[Lou Berger]

Adrian,

Thanks for this -- as far as I can tell, Jurgen's comments were not 
addressed in the on-list discussion in August.  Do think that they 
were?  We were at least expecting some document update based on the 
discussion.


Authors/Contributors,

    Where do you think we stand in resolving the on-list discussion?

Thanks,

Lou (and Kent)

On 10/10/2022 4:29 AM, Adrian Farrel wrote:

Hi,

Discussion of this document seemed to fizzle out in August, and the last
email seems to be Qin saying "I'm happy to make no change if no change is
needed."

Where does that leave us with regards to the WG last call comments and the
discussion at IETF-114?

Thanks,
Adrian



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Please send you slides

[Lou Berger]

Presenters, please check that your slides are properly uploaded. If not 
- please send/upload ASAP.


Thank you,

Lou

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] IETF 114 Slot Requests

[Lou Berger]

WG,

The *draft* agenda for IETF114 has been posted -
https://datatracker.ietf.org/meeting/114/agenda

The NetMod session information is:

      Wednesday, July 27, 2022
  15:00-17:00 Wednesday Session III
  Independence A/B
  iCalendar: 
https://datatracker.ietf.org/meeting/114/sessions/netmod.ics


This will be an in-person/hybrid meeting.

Please send slot requests to netmod-cha...@ietf.org before the end of 
the day Monday July 11 (any TZ, but earlier is appreciated).  Please 
include draft names(s), presenter, desired slot length.  Also, please 
let us know if you think the topic would be better covered in a Virtual 
Interim to be held at a future date.


Thank you!

Lou (Kent and Joel)

Important dates:

IETF 114
2022-07-23, Philadelphia, US
DateWeekday Description
2022-06-24  Friday  Preliminary Agenda published for comment
2022-06-29  Wednesday   Cut-off date for requests to reschedule
Working Group or BOF meetings UTC 23:59
2022-07-01  Friday  Final agenda to be published
2022-07-11  Monday  Internet Draft submission cut-off (for all
drafts, including -00) by UTC 23:59 Upload using
the ID Submission Tool.
2022-07-11  Monday  Standard rate registration and payment cut-off
at UTC 23:59.
2022-07-13  Wednesday   Draft Working Group agendas due by UTC
23:59 Upload using the Meeting Materials
Management Tool.
2022-07-18  Monday  Registration cancellation cut-off at UTC 23:59
2022-07-18  Monday  Revised Working Group agendas due by UTC 23:59
Upload using the Meeting Materials Management
Tool.
2022-08-19  Friday  Proceedings submission cutoff date by UTC 23:59
Upload using the Meeting Materials Management
Tool.
2022-09-12  Monday Proceedings submission corrections cutoff date by
UTC 23:59



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Tree diagram comment lines

[Lou Berger]

Yes. See https://datatracker.ietf.org/doc/html/rfc8340#section-2.5

Lou


--
On April 11, 2022 6:52:27 AM tom petch  wrote:

Can a YANG tree diagram contain comment lines?

draft-ietf-teas-yang-te has a tree diagram of 40 pages and since the IETF has 
abolished the page number, then any reference into it could be a challenge.  
For a YANG module, this can be ameliorated by inserting comment lines every 
page or two.

Can this be done with tree diagrams?

Tom Petch
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] WG Last Call: draft-ietf-netmod-yang-semver-06

[Lou Berger]

Hi,

I'd like to formally close this (and the other) LC -- by saying the same 
thing for both.


There were some good comments made during the LC that should be 
addressed before publication.  Authors, as I'm sure you are doing so 
already, please work through all public and private comments received; 
preferably with on-list discussion.  Once you publish a version that 
addresses all received comments as well as the on-list discussions, 
please summarize the changes to the WG.  Also please state that the 
document is ready for publication. The need for a second last call will 
be based on the specific changes.


Thank you!

Lou (Co-Chair & doc Shepherd)
On 2/21/2022 12:20 PM, Lou Berger wrote:

All,

This starts working group last call on
https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-semver/

The working group last call ends on March 7 th.
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 publication", are welcome!
This is useful and important, even from authors.

Please note that once WG Last call is complete, this document will be
held and submitted as a set with the other versioning documents (once
they are ready) for publication request to the IESG.

Thank you,
Lou (Co-Chair & doc Shepherd)




___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] WG Last Call: draft-ietf-netmod-yang-module-versioning-05

[Lou Berger]

Hi,

I'd like to formally close this (and the other) LC -- by saying the same 
thing for both.


There were some good comments made during the LC that should be 
addressed before publication.  Authors, as I'm sure you are doing so 
already, please work through all public and private comments received; 
preferably with on-list discussion.  Once you publish a version that 
addresses all received comments as well as the on-list discussions, 
please summarize the changes to the WG.  Also please state that the 
document is ready for publication. The need for a second last call will 
be based on the specific changes.


Thank you!

Lou (Co-Chair & doc Shepherd)

On 2/21/2022 12:20 PM, Lou Berger wrote:


All,

This starts working group last call on
https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-module-versioning/

The working group last call ends on March 7 th.
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 publication", are welcome!
This is useful and important, even from authors.

Please note that once WG Last call is complete, this document will be
held and submitted as a set with the other versioning documents (once
they are ready) for publication request to the IESG.

Thank you,
Lou (Co-Chair & doc Shepherd)






___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Draft IETF 113 Agenda Posted

[Lou Berger]

NETMOD WG.

A draft agenda is now available.

Please let us know if we missed a request.

Presenters:

Please provide your slides to the chairs not later than Sunday March 20th.

Authors of WG documents:

If you are not on the agenda , please send a update on status and
plans for the document no later than Monday March 21.

Thank you,

Lou and Kent (and Joel)


Agenda for the NETMOD 113 WG Session
---
https://datatracker.ietf.org/meeting/113/materials/agenda-113-netmod


Session:

   Tuesday, March 22, 2022
   Session II (10:00-12:00 +1 CET, 09:00-11:00 UTC)


WG Chairs:

   Lou Berger(lberger at labs dot net)
   Kent Watsen   (kent plus ietf at watsen dot net)
   Joel Jaeggli  (joelja at bogus dot com)


Available During Session:

   ICS: https://datatracker.ietf.org/meeting/113/sessions/netmod.ics
   MeetEcho: https://meetings.conf.meetecho.com/ietf113/?group=netmod
   Audio Only: https://mp3.conf.meetecho.com/ietf113/netmod/1.m3u
   Jabber:xmpp:net...@jabber.ietf.org?join


Available During and After Session:

   Notes: https://notes.ietf.org/notes-ietf-113-netmod
   Slides: https://datatracker.ietf.org/meeting/113/session/netmod
   Drafts (TGZ): 
https://datatracker.ietf.org/meeting/113/agenda/netmod-drafts.tgz
   Drafts (PDF): 
https://datatracker.ietf.org/meeting/113/agenda/netmod-drafts.pdf



Available After Session:

   Recording: http://www.meetecho.com/ietf113/recordings#NETMOD
   Jabber Logs: https://www.ietf.org/jabber/logs/netmod


Introduction

   Chairs (10 minutes)
   Session Intro & WG Status


Chartered items:

  Title: YANG Versioning Update (45 min)

https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-module-versioning-05
  https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-semver-06
  https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-packages-03
  Discussion Leader: TBD

  Title: Self Describing Data Object Tags (10 min)
  https://datatracker.ietf.org/doc/html/draft-ietf-netmod-node-tags-06
  Presenter: Qin Wu


Non-Chartered items:

   Title: System-defined configuration (15 min)
   https://datatracker.ietf.org/doc/html/draft-ma-netmod-with-system-02
   Presenter: Qiufang Ma

   Title: Immutable Metadata Annotation (15 min)

https://datatracker.ietf.org/doc/html/draft-ma-netmod-immutable-flag-00
   Presenter: Qiufang Ma

   Title: Updated Common YANG Data Types for Traffic Engineering (10 min)
   https://datatracker.ietf.org/doc/html/draft-busi-teas-te-types-update-01
   Presenter: Italo Busi

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] IETF 113 Slot Requests

[Lou Berger]

WG,

The *draft* agenda for IETF111 has been posted - 
https://datatracker.ietf.org/meeting/113/agenda


Tuesday, March 22, Tuesday, March 22, 2022 09:00-11:00 UTC

iCalendar: https://datatracker.ietf.org/meeting/113/sessions/netmod.ics

This will be a hybrid meeting.  Our plan to cover updates, open issues, 
and new topics.


Please send slot requests to netmod-cha...@ietf.org before the end of 
the day Sunday, March 6 (any TZ).  Please include draft names(s), 
presenter, desired slot length.  Also, please let us know if you think 
the topic would be better covered in a Virtual Interim to be held at a 
future date.


Please keep in mind that priority for agenda time is given to WG drafts 
and other drafts/topics discussed on the mailing list.


Finally, if you plan to be in person and are willing to help manage the 
in person queue please let us know.


Thank you!

Lou, (Kent and Joel)

Important dates:

IETF 113: 2022-03-19, Vienna, AT

2022-02-23 (Wednesday): Cut-off date for requests to reschedule Working 
Group or BOF meetings UTC 23:59.

2022-02-25 (Friday): Final agenda to be published.
2022-03-07 (Monday): Internet Draft submission cut-off (for all drafts, 
including -00) by UTC 23:59. Upload using the ID Submission Tool.
2022-03-07 (Monday): Standard rate registration and payment cut-off at 
UTC 23:59..
2022-03-09 (Wednesday): Draft Working Group agendas due by UTC 23:59. 
Upload using the Meeting Materials Management Tool.

2022-03-14 (Monday): Registration cancellation cut-off at UTC 23:59.
2022-03-14 (Monday): Revised Working Group agendas due by UTC 23:59. 
Upload using the Meeting Materials Management Tool.
2022-04-15 (Friday): Proceedings submission cutoff date by UTC 23:59. 
Upload using the Meeting Materials Management Tool.
2022-05-09 (Monday): Proceedings submission corrections cutoff date by 
UTC 23:59.




___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] WG Last Call: draft-ietf-netmod-yang-module-versioning-05

[Lou Berger]

All,

This starts working group last call on
https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-module-versioning/

The working group last call ends on March 7 th.
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 publication", are welcome!
This is useful and important, even from authors.

Please note that once WG Last call is complete, this document will be 
held and submitted as a set with the other versioning documents (once 
they are ready) for publication request to the IESG.


Thank you,
Lou (Co-Chair & doc Shepherd)




___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] WG Last Call: draft-ietf-netmod-yang-semver-06

[Lou Berger]

All,

This starts working group last call on
https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-semver/

The working group last call ends on March 7 th.
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 publication", are welcome!
This is useful and important, even from authors.

Please note that once WG Last call is complete, this document will be 
held and submitted as a set with the other versioning documents (once 
they are ready) for publication request to the IESG.


Thank you,
Lou (Co-Chair & doc Shepherd)


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regarding IPR on Regarding IPR on draft-ietf-netmod-yang-semver-06

[Lou Berger]

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 compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
Lou (Co-Chair)

PS Please include all listed in the headers of this message in your
response.


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regarding IPR on draft-ietf-netmod-yang-module-versioning-05

[Lou Berger]

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 compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
Lou (Co-Chair)

PS Please include all listed in the headers of this message in your
response.


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Draft IETF112 Agenda Available

[Lou Berger]

All,

A draft agenda for our virtual 112 meeting has been posted.

Please take a look and let us know if any changes are needed.

https://datatracker.ietf.org/meeting/112/materials/agenda-112-netmod

Presenters:
Please provide your slides to the chairs no later than the Tuesday
before our meeting.

Authors of WG documents:
If you are not on the agenda, please send a update on status and
plans for the document no later than Friday November 5.

Thank you!
Lou (Kent and Joel)

Some session information:

Thursday, November 11 --   UTC: 14:30-15:30 (Session II)

Session material:
https://datatracker.ietf.org/meeting/112/session/netmod
ICS: https://datatracker.ietf.org/meeting/112/sessions/netmod.ics
MeetEcho: https://meetings.conf.meetecho.com/ietf112/?group=netmod
Jabber: xmpp:net...@jabber.ietf.org?join
CodiMD:https://codimd.ietf.org/notes-ietf-112-netmod

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] NULL value for uint16

[Lou Berger]

Tom,

okay, you made me look...

The full text is

 leaf received-metric {
   type uint16;
   description
 "The metric with which this route was advertised by the
  neighbor, or maximum value (infinity) to indicate the
  route was recently retracted and is temporarily
  unreachable. This metric will be NULL (no value) if the
  route was not received from a neighbor but instead was
  injected through means external to the Babel routing
  protocol. At least one of calculated-metric or
  received-metric MUST be non-NULL.";

and it references an RFC that says:

  This is a 16-bit unsigned integer;
  if the data model uses zero (0) to represent NULL values for
  unsigned integers, the data model MAY use a different data type
  that allows differentiation between zero (0) and NULL.


So, in context I read it as saying NULL = 0

While I think the phrasing *is* problematic if the definition of NULL 
was expected to be yang, the reference points to a relevant definition 
of NULL.  So, in this context, I'm not sure I see a substantive issue 
that *needs* to be fixed.  I do think this is something for the yang Drs 
to keep an eye out for  and perhaps avoid possibly confusing language in 
the future.


Lou (as contributor)

On 9/10/2021 12:06 PM, tom petch wrote:


From: Jürgen Schönwälder 
Sent: 10 September 2021 13:14

I guess the description should be worded as

   "This leaf does not exist if ..."

instead of talking about NULL, a concept that does not exist in the
YANG language and the protocols.

One subtle point with the "does not exist" approach is that a client
cannot reliably distinguish between 'a leaf does not exist' and
'access to a leaf was denied by an authorization policy'. In practice,
though, most authorization policies tend to be rather coarse grained.



Juergen, Lada

Thank you for the prompt responses.  This is an I-D that has been to the IESG 
although the announcement has yet to appear, which makes me coy about saying 
which it is:-)  My inclination is to let sleeping dogs lie and see what comes 
out of the RFC Editor (probably the same as went in: but if you think it 
significant enough, I would flag it to the WG Chair:-(

Tom Petch

/js

On Fri, Sep 10, 2021 at 11:56:22AM +, tom petch wrote:

Does NULL have any meaning for a leaf of type uint16?

Looking at a leaf of type uint16 the description says that
'This metric will be NULL (no value) ..'

Some languages differentiate  a 'never been set' state from e.g set to zero or 
some other value but for me, YANG does not have that concept.  Rather the leaf 
does not exist which  will be reflected by the protocol accessing the leaf.

I see no NULL at least in this context in RFC7950.

Tom petch
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

--
Juergen Schoenwaelder   Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103 

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] IETF 111 Slot Requests

[Lou Berger]

WG,

The *draft* agenda for IETF111 has been posted - 
https://datatracker.ietf.org/meeting/111/agenda


    TUESDAY, July 27, 2021 -- 1430-1530  Session II (UTC)

iCalendar: https://datatracker.ietf.org/meeting/111/sessions/nemod.ics

This will be fully remote meeting.  Our plan to cover updates, open 
issues, and new topics.


Please send slot requests to netmod-cha...@ietf.org before the end of 
the day Sunday, July 11 (any TZ).  Please include draft names(s), 
presenter, desired slot length.  Also, please let us know if you think 
the topic would be better covered in a Virtual Interim to be held at a 
future date.
Please keep in mind that priority for agenda time is given to WG drafts 
and other drafts/topics discussed on the mailing list.


Thank you !

Lou, (Kent and Joel)

Important dates:
IETF 111: 2021-07-24, Online, US
2021-06-30 (Wednesday): Cut-off date for requests to reschedule Working 
Group or BOF meetings UTC 23:59.

2021-07-02 (Friday): Final agenda to be published.
2021-07-12 (Monday): Standard rate registration and payment cut-off at 
UTC 23:59..
2021-07-12 (Monday): Internet Draft submission cut-off (for all drafts, 
including -00) by UTC 23:59. Upload using the ID Submission Tool.
2021-07-14 (Wednesday): Draft Working Group agendas due by UTC 23:59. 
Upload using the Meeting Materials Management Tool.
2021-07-19 (Monday): Revised Working Group agendas due by UTC 23:59. 
Upload using the Meeting Materials Management Tool.

2021-07-19 (Monday): Registration cancellation cut-off at UTC 23:59.



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Draft IETF 110 Agenda Available

[Lou Berger]

All,

A draft agenda for our virtual 110 meeting has been posted.

Please take a look and let us know if any changes are needed.

https://datatracker.ietf.org/meeting/110/materials/agenda-110-netmod

Presenters:
Please provide your slides to the chairs no later than the Tuesday
before our meeting.

Authors of WG documents:
If you are not on the agenda , please send a update on status and
plans for the document no later than Thursday March 11.

Thank you!
Lou (Kent and Joel)

Some session information:

Friday March 12 --   UTC: 16:00-18:00 (Session III)

   Session material: 
https://datatracker.ietf.org/meeting/110/session/netmod

   ICS: https://datatracker.ietf.org/meeting/110/sessions/netmod.ics
   MeetEcho: https://meetings.conf.meetecho.com/ietf110/?group=netmod
   Jabber: xmpp:net...@jabber.ietf.org?join
   CodiMD:    https://codimd.ietf.org/notes-ietf-110-netmod











___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] IETF 110 Slot Requests

[Lou Berger]

WG,

The *final* agenda for IETF110 has been posted - 
https://datatracker.ietf.org/meeting/110/agenda


    Friday, 12 March 2021, Session III 16:00-18:00 (UTC)

iCalendar: https://datatracker.ietf.org/meeting/110/sessions/nemod.ics

This will be fully remote meeting.  Our plan to cover updates, open 
issues, and covering new topics in the first half of the meeting, and to 
use the remaining time to discuss open issues on the Versioning drafts.


Please send slot requests to netmod-cha...@ietf.org before the end of 
the day Monday, February 22 (any TZ).  Please include draft names(s), 
presenter, desired slot length.  Also, please let us know if you think 
the topic would be better covered in a Virtual Interim to be held at a 
future date.
Please keep in mind that priority for agenda time is given to WG drafts 
and other drafts/topics discussed on the mailing list.


Thank you !

Lou, Kent and Joel

Important dates:
IETF 110: 2021-03-06, Online, CZ
2021-02-12 (Friday): Final agenda to be published.
2021-02-22 (Monday): Standard rate registration and payment cut-off at 
UTC 23:59..
2021-02-22 (Monday): Internet Draft submission cut-off (for all drafts, 
including -00) by UTC 23:59. Upload using the ID Submission Tool.
2021-02-24 (Wednesday): Draft Working Group agendas due by UTC 23:59. 
Upload using the Meeting Materials Management Tool.

2021-03-01 (Monday): Registration cancellation cut-off at UTC 23:59.
2021-03-01 (Monday): Revised Working Group agendas due by UTC 23:59. 
Upload using the Meeting Materials Management Tool.
2021-04-02 (Friday): Proceedings submission cutoff date by UTC 23:59. 
Upload using the Meeting Materials Management Tool.
2021-04-26 (Monday): Proceedings submission corrections cutoff date by 
UTC 23:59.


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Reminder: NETMOD Versioning Interim - Feb 20221

[Lou Berger]

Fyi here is the link to the meeting materials:

https://datatracker.ietf.org/meeting/interim-2021-netmod-01/session/netmod



On January 30, 2021 12:10:21 PM Kent Watsen  wrote:

NETMOD is hosting a virtual interim this coming Monday (in ~45 hours).

ICS file attached to this message.

NETMOD Agenda for Interim (virtual)

DateFebruary 1, 2021
Start Time  14:30 UTC
Duration90 minutes

Time Zone Converter:
 
https://www.timeanddate.com/worldclock/converter.html?iso=20210201T143000=1440=37=438=33=248=224=179
Slides:
 
https://datatracker.ietf.org/meeting/interim-2021-netmod-01/session/netmodNotes
Notes & BlueSheet:
https://codimd.ietf.org/notes-ietf-interim-2021-netmod-01-netmod
WebEx:
https://ietf.webex.com/ietf/j.php?MTID=m8ee8976e972cc17b725f3ce1900b0cd0
Jabber:
xmpp:net...@jabber.ietf.org?join

Agenda:

1   Topic   Intro & Administrivia
Presenter:  Chairs

2 Topic Module Versioning:
Presenter: Authors
Follow on to
https://datatracker.ietf.org/meeting/interim-2020-netmod-03/session/netmod
Virtual Bluesheet



Begin forwarded message:

From: NETMOD Working Group mailto:messen...@webex.com>>
Subject: Webex meeting changed: NetMod YANG Versioning Interim - Feb 20221
Date: January 15, 2021 at 11:07:12 AM EST
To: netmod-cha...@ietf.org
Resent-From: mailto:alias-boun...@ietf.org>>
Resent-To: joe...@bogus.com, 
kent+i...@watsen.net, 
lber...@labn.net
Reply-To: netmod-cha...@ietf.org



NETMOD Working Group changed the Webex meeting information.



When it's time, join the Webex meeting here.



Monday, February 1, 2021
9:30 am  |  (UTC-05:00) Eastern Time (US & Canada)  |  1 hr 30 mins

Join 
meeting

More ways to join:
Join from the meeting link
https://ietf.webex.com/ietf/j.php?MTID=m8ee8976e972cc17b725f3ce1900b0cd0

Join by meeting number
Meeting number (access code): 178 198 8377
Meeting password: Versioning

Tap to join from a mobile device (attendees only)
+1-650-479-3208,,1781988377## 
Call-in toll number (US/Canada)

Join by phone
1-650-479-3208 Call-in toll number (US/Canada)
Global call-in 
numbers

Join from a video system or application
Dial 1781988...@ietf.webex.com
You can also dial 173.243.2.68 and enter your meeting number.

Join using Microsoft Lync or Microsoft Skype for Business
Dial 1781988377.i...@lync.webex.com


Need help? Go to https://help.webex.com


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Adoption poll for draft-wwx-netmod-event-yang-10

[Lou Berger]

Hi,

The response to this poll is sufficient for it to be adopted.  We just 
need the 3 missing IPR statements and, assuming no surprises, the 
document can be republished as a WG document.


Authors,

Please prepare a version of the draft with only the file name changed to 
draft-ietf-netmod-eca-policy-00.  The -01 version should address issues 
/ comments raised during adoption.  Note that publication of the -00 
version is gated by the completion of the IPR poll.


Thank you!

Lou (for co-chairs)

On 12/7/2020 5:27 PM, Lou Berger wrote:

This email begins a 2-week adoption poll for:

https://tools.ietf.org/html/draft-wwx-netmod-event-yang-10

Please voice your support or technical objections on list before the end
of December 21, any time zone.

Thank you!

Netmod Chairs

PS Note the IPR poll is running concurrently as the private response all
indicated that no IPR exists.  The draft will not be formally adopted
until both the IPR and WG polls are complete.




___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Regarding IPR on draft-wwx-netmod-event-yang-10

[Lou Berger]

Hi Qin,

It's sub-optimal, but sufficient IMO.  Please note you didn't respond 
for yourself!


we're still missing responses from:

Qin Wu
Benoit Claise
Andy Bierman

Thanks,

Lou

On 12/7/2020 8:46 PM, Qin Wu wrote:


Hi, Lou:

Does forwarding confirmation from the authors to the list count?

I have done this accidentally. If not, I will leave this to my coauthors.

-Qin

*发件人:*Lou Berger [mailto:lber...@labn.net]
*发送时间:*2020年12月8日6:20
*收件人:*Qin Wu ; Igor Bryskin ; 
Henk Birkholz ; Xufeng Liu 
; Benoit Claise 
*抄送:*NetMod WG Chairs ; NetMod WG 


*主题:*Fwd: Regarding IPR on draft-wwx-netmod-event-yang-10

Authors,

    My apologies -- I failed to cc the WG on this.  Can you please 
re-reply so that your response make it into the WG archive.


Thank you!

Lou


 Forwarded Message 

*Subject: *



Regarding IPR on draft-wwx-netmod-event-yang-10

*Date: *



Mon, 23 Nov 2020 18:08:59 -0500

*From: *



Lou Berger  <mailto:lber...@labn.net>

*To: *



Qin Wu  <mailto:bill...@huawei.com>, Igor Bryskin 
 <mailto:i_brys...@yahoo.com>, Henk Birkholz 
 
<mailto:henk.birkh...@sit.fraunhofer.de>, Xufeng Liu 
 <mailto:xufeng.liu.i...@gmail.com>, Benoit 
Claise  <mailto:bcla...@cisco.com>


*CC: *



NetMod WG Chairs  <mailto:netmod-cha...@ietf.org>



Authors,

Per the 109 session, it is the chairs intent to do another adoption 
call on this draft. In preparation for that, we’ve determined both 
that the draft has changed significantly and that there is a new 
author, and therefore feel it necessary to issue another IPR call, as 
follows:



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 disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate.

We note that all DT members are listed as contributors. If you
contributed to the document please respond. Alternatively, please feel
free to state that you didn't materially contribute to the draft and
would like your name removed from the contribution section (and moved to
acknowledgments after WG adoption).

If you are listed as a document author or contributor please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty 
<http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty>.


Thank you,
NETMOD WG Chairs

PS Please include all listed in the headers of this message in your
response.



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Reminder: NETMOD interim on versioning tomorrow (Monday, Dec 14)

[Lou Berger]

Just a reminder that we have an upcoming interim.  Please join in via 
webex and codimd:


Date             December 14, 2020
Start Time    14:30 UTC
Duration    up to 90 minutes

Time Zone Converter:
https://www.timeanddate.com/worldclock/converter.html?iso=20201214T143000=1440=37=438=33=248=224=179
Materials:
https://datatracker.ietf.org/meeting/interim-2020-netmod-03/session/netmod
Notes & BlueSheet:
https://codimd.ietf.org/notes-ietf-interim-2020-netmod-03-netmod
WebEx:
https://ietf.webex.com/ietf/j.php?MTID=mc1669d1bed230c82a9d9a3d1510ad891
Jabber:
    xmpp:net...@jabber.ietf.org?join

Agenda:

1    Topic    Intro & Administrivia
Presenter:    Chairs

2    Topic    Module Versioning: Imports
Presenter:    Authors

3    Topic    Module Versioning: Whitespace
Presenter:    Authors

For Reference:

4    Slides    YANG Versioning Update

Draft 
https://tools.ietf.org/html/draft-ietf-netmod-yang-module-versioning-01


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Adoption poll for draft-wwx-netmod-event-yang-10

[Lou Berger]

I should have mentioned that this is the 2nd adoption call on this 
document.  for full context on discussion on this draft, see 
https://mailarchive.ietf.org/arch/browse/netmod/?q=draft-wwx-netmod-event-yang


On 12/7/2020 5:27 PM, Lou Berger wrote:

This email begins a 2-week adoption poll for:

https://tools.ietf.org/html/draft-wwx-netmod-event-yang-10

Please voice your support or technical objections on list before the end
of December 21, any time zone.

Thank you!

Netmod Chairs

PS Note the IPR poll is running concurrently as the private response all
indicated that no IPR exists.  The draft will not be formally adopted
until both the IPR and WG polls are complete.




___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Adoption poll for draft-wwx-netmod-event-yang-10

[Lou Berger]

This email begins a 2-week adoption poll for:

https://tools.ietf.org/html/draft-wwx-netmod-event-yang-10

Please voice your support or technical objections on list before the end 
of December 21, any time zone.


Thank you!

Netmod Chairs

PS Note the IPR poll is running concurrently as the private response all 
indicated that no IPR exists.  The draft will not be formally adopted 
until both the IPR and WG polls are complete.



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Fwd: Regarding IPR on draft-wwx-netmod-event-yang-10

[Lou Berger]

Authors,

    My apologies -- I failed to cc the WG on this.  Can you please 
re-reply so that your response make it into the WG archive.


Thank you!

Lou


 Forwarded Message 
Subject:Regarding IPR on draft-wwx-netmod-event-yang-10
Date:   Mon, 23 Nov 2020 18:08:59 -0500
From:   Lou Berger 
To: 	Qin Wu , Igor Bryskin , 
Henk Birkholz , Xufeng Liu 
, Benoit Claise 

CC: NetMod WG Chairs 



Authors,

Per the 109 session, it is the chairs intent to do another adoption call 
on this draft. In preparation for that, we’ve determined both that the 
draft has changed significantly and that there is a new author, and 
therefore feel it necessary to issue another IPR call, as follows:



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 disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate.

We note that all DT members are listed as contributors. If you
contributed to the document please respond. Alternatively, please feel
free to state that you didn't materially contribute to the draft and
would like your name removed from the contribution section (and moved to
acknowledgments after WG adoption).

If you are listed as a document author or contributor please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
NETMOD WG Chairs

PS Please include all listed in the headers of this message in your
response.

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] IETF 109 session info

[Lou Berger]

Hi,

Here are the usual (hopefully) useful session links:

Meetecho: 
https://meetings.conf.meetecho.com/ietf109/?group=netmod==1


Materials: https://datatracker.ietf.org/meeting/109/session/netmod

Note taking:    https://codimd.ietf.org/notes-ietf-109-netmod?both

Audio stream:    http://mp3.conf.meetecho.com/ietf109/netmod/1.m3u

Jabber:         http://jabber.ietf.org/logs/netmod or 
xmpp:net...@jabber.ietf.org?join


If you are presenting, please join a few minutes early for an audio 
check.  We should be there 10 minutes before the session.


See you soon!
Lou (Kent and Joel)


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Adoption poll for draft-tao-netmod-yang-node-tags

[Lou Berger]

Qin,

Thank you for your reply.I think you have two points below (a) tags to 
define metric type and (b) object-specific tags


For me, I believe I agree with Juergen's comments, i.e.,  that metric 
type definition is not metadata and belongs in the module definition.


On the other topic (b) object-specific tags is an interesting idea and 
may provide general utility.  (as contributor) once separated from the 
metrics discussion, this seems like an idea worth discussing in the WG 
to see if there is interest in this added capability.


Lou



On August 30, 2020 5:01:28 AM Qin Wu  wrote:


Thanks Lou for valuable comments, please see reply inline below.

*发件人:*Lou Berger [mailto:lber...@labn.net]
*发送时间:*2020年8月30日2:40
*收件人:*Kent Watsen ; netmod@ietf.org; 
draft-tao-netmod-yang-node-t...@ietf.org

*主题:*Re: [netmod] Adoption poll for draft-tao-netmod-yang-node-tags

Hi,

A couple of comments:

- As a co-author or YANG Module Tags, I'm thrilled to see it being 
used/augmented by this document, but I'm not clear on how the metric 
and operation type tags are to be used.  To me these seem to be best 
defined by the modules themselves, e.g., does a value represent an 
average /sum/min/max value or the scale of the value, and not as tag 
meta data.


[Qin]:Just to clarify, defining metric and operation type by modules 
themselves may cause revising all the existing published modules we 
expect to tag, or creating the same number of new modules (augment 
from the existing published modules) as the number of targeted 
existing modules, which is not scalable and desirable. So we abandon 
this option in our implementation design.


The data object tags like metric and operation type tag don't 
introduce any new data nodes into existing modules and can tag any 
performance metric related data object within published modules, 
standard modules, native modules without module name change. The data 
object tag can not be used to tag any one of targeted modules 
(ietf-geo-location defined in draft-ietf-netmod-geo-location or 
ietf-ip in RFC8344) which doesn't include performance metric related 
data node.


Regarding operation type tag, take ietf-interfaces in RFC8343 as an 
example, ietf-interfaces include interface statistics data object 
which can be seen as performance metric related data objects,


   +--ro statistics

  +--ro discontinuity-time yang:date-and-time

  +--ro in-octets? yang:counter64

  +--ro in-unicast-pkts? yang:counter64

  +--ro in-broadcast-pkts? yang:counter64

  +--ro in-multicast-pkts? yang:counter64

  +--ro in-discards? yang:counter32

  +--ro in-errors? yang:counter32

  +--ro in-unknown-protos? yang:counter32

  +--ro out-octets? yang:counter64

  +--ro out-unicast-pkts? yang:counter64

  +--ro out-broadcast-pkts? yang:counter64

  +--ro out-multicast-pkts? yang:counter64

  +--ro out-discards? yang:counter32

  +--ro out-errors? yang:counter32

however these statistics doesn't tell you whether in-errors is current 
value or average value or total value, so does count related data 
objects defined in ietf-dhcpv6-server of draft-ietf-dhc-dhcpv6-yang


    +--ro solicit-count?   uint32

    +--ro advertise-count? uint32

    +--ro request-count?   uint32

    +--ro confirm-count?   uint32

    +--ro renew-count? uint32

    +--ro rebind-count?    uint32

    +--ro reply-count? uint32

    +--rw release-count?   uint32

    +--ro decline-count?   uint32

    +--ro reconfigure-count?   uint32

    +--ro information-request-count?   uint32

The operation type tag is introduced to help the network device who is 
responsible for collecting these statistics data with specific 
operation type, tell the collectors the statistic related data object 
reporting current value or average value.


For the scale of the value, talking with Benoit earlier, we think 
metric scale may be overlapping with the range statement, the idea is 
to provide consistent reporting and representation for some of 
statistics data we want to tag. But if this adds complexity, we are 
happy to take it out, so does metric precision.


Similarly, the type of vpn supported by a tunnel also seems like 
module data and not tag meta data, as this is a per tunnel instance value.


[Qin] See above, data object tag is **not used to replace module 
data**, instead, it is used to label these module data as our 
interested subscribed objects. The label value or tag value is fixed 
upon it is defined.


Secondly, the precondition to use vpn service tag is the vpn service 
has already been

Re: [netmod] Adoption poll for draft-tao-netmod-yang-node-tags

[Lou Berger]

Hi,

A couple of comments:

- As a co-author or YANG Module Tags, I'm thrilled to see it being 
used/augmented by this document, but I'm not clear on how the metric and 
operation type tags are to be used.  To me these seem to be best defined 
by the modules themselves, e.g., does a value represent an average 
/sum/min/max value or the scale of the value, and not as tag meta 
data.   Similarly, the type of vpn supported by a tunnel also seems like 
module data and not tag meta data, as this is a per tunnel instance value.


While the work was previously presented to the WG, I know you didn't 
have the time we all hoped for to discuss this at the last session, so I 
(personally, not as chair) would like to ask you to explain this on the 
list prior to adoption.  I'm hoping I'm just missing something, but from 
the discussion with Juergen an Andy I suspect not.


- Since this work is derived from work that I contributed to, I'd be 
interested in hearing what new mechanism(s) is/are covered by the IPR 
disclosure prior to supporting WG adoption.  I'm not asking in order to 
debate this, as that is something for other venues, I'm merely asking 
that you state for the record what new mechanism is covered.


Thank you

Lou

(as WG contributor and co-author of draft-ietf-netmod-module-tags)


On 8/17/2020 6:05 PM, Kent Watsen wrote:

This email begins a 2-week adoption poll for:

https://tools.ietf.org/html/draft-tao-netmod-yang-node-tags-05

Please voice your support or objections on list before August 31.

Notes:
   1)  -03 was presented during the 108 session, hence the I-D has 
been updated twice since then.

   2) Please be aware that IPR has been filed for this I-D:
https://datatracker.ietf.org/ipr/search/?submit=draft=draft-tao-netmod-yang-node-tags.

Netmod Chairs



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Webex meeting changed: NETMOD YANG Version Discussions

[Lou Berger]

Sorry about the flurry of invites.  The right time is, weekly starting

https://www.timeanddate.com/worldclock/converter.html?iso=20200901T13=1440

Lou


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Session links...

[Lou Berger]

Hi,

Here are some (hopefully) useful links for today's sessions:

Joint note taking: https://codimd.ietf.org/notes-ietf-108-netmod?both

Session material: https://datatracker.ietf.org/meeting/108/session/netmod

Join session: https://meetings.conf.meetecho.com/ietf108/?group=netmod

See you soon,
Lou

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Preliminary agenda

[Lou Berger]

just a reminder -- see you tomorrow, July 30th!

https://www.timeanddate.com/worldclock/converter.html?iso=20200730T141000=1440

Lou (and Kent (and Joel ;-))

On 7/28/2020 11:09 AM, Kent Watsen wrote:

NETMOD WG.

The agenda has been updated (see below). The Etherpad link has been replaced 
with the CodiMD link for the session.

Please note that CodiMD MAY be opened in another browser window or tab, in 
addition to the MeetEcho window.

Kent (and Lou (and Joel))




Agenda for the NETMOD 108 WG Session
-
https://datatracker.ietf.org/meeting/108/materials/agenda-108-netmod


Session:
Thursday July 28th
UTC: 14:10-15:50


WG Chairs:
Kent Watsen (kent plus ietf at watsen dot net)
Lou Berger (lberger at labs dot net)
Joel Jaeggli (joelja at bogus dot com)


Available During Session:
ICS:https://datatracker.ietf.org/meeting/108/sessions/netmod.ics
MeetEcho:   https://meetings.conf.meetecho.com/ietf108/?group=netmod
Jabber: xmpp:net...@jabber.ietf.org?join


Available During / After Session:
CodiMD:https://codimd.ietf.org/notes-ietf-108-netmod
Slides (TGZ):  
https://datatracker.ietf.org/meeting/108/agenda/netmod-drafts.tgz
Slides (PDF):  
https://datatracker.ietf.org/meeting/108/agenda/netmod-drafts.pdf


Available After Session:
Recording: https://ietf108.conf.meetecho.com/index.php/Recordings#NETMOD
Jabber Logs:   https://www.ietf.org/jabber/logs/netmod


Introduction

Chairs (10 minutes)
Session Intro & WG Status


Chartered items:

Update on: (5 min)
  - Sub-interface VLAN YANG Data Models
  - Common Interface Extension YANG Data Models
https://tools.ietf.org/html/draft-ietf-netmod-sub-intf-vlan-model-07
https://tools.ietf.org/html/draft-ietf-netmod-intf-ext-yang-09
Rob Wilton

General Update on the YANG Versioning Solution (5 min)
Reshad Rahman

Updated YANG Module Revision Handling (20 min)
https://tools.ietf.org/html/draft-ietf-netmod-yang-module-versioning-01
Reshad Rahman

YANG Semantic Versioning (15 min)
https://tools.ietf.org/html/draft-ietf-netmod-yang-semver-01
Joe Clarke

Common YANG Data Types (15 min)
https://tools.ietf.org/html/draft-ietf-netmod-rfc6991-bis-04
Juergen Schoenwaelder

Non-Chartered items:

Telemetry Data Self Explanation Tags (10 min)
https://tools.ietf.org/html/draft-tao-netmod-yang-node-tags-03
Qin Wu



Remaining 25 min.


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regarding IPR on draft-tao-netmod-yang-node-tags-01

[Lou Berger]

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 disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate.

We note that all DT members are listed as contributors.  If you
contributed to the document please respond.  Alternatively, please feel
free to state that you didn't materially contribute to the draft and
would like your name removed from the contribution section (and moved to
acknowledgments after WG adoption).

If you are listed as a document author or contributor please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
NetMod WG Chairs

PS Please include all listed in the headers of this message in your
response.



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Fwd: Nomcom 2020-2021 Second Call For Volunteers

[Lou Berger]

--
--- Forwarded message ---
From: NomCom Chair 2020 nomcom-chair-2...@ietf.org
Date: June 10, 2020 2:57:10 PM
Subject: Nomcom 2020-2021 Second Call For Volunteers
To: IETF Announcement List ietf-annou...@ietf.org
CC: i...@ietf.org

This is the second sending of the call for volunteers for the 2020-2021 NomCom.

I wanted to mention a few updates from the previous email (sent 2 weeks ago):
- I've fixed the URL at the bottom of the email to point to 
https://datatracker.ietf.org/nomcom/2020/ instead of /2019/. This was a 
test to see if anyone was paying attention. Apparently, some people were. ;)
- The IETF 108 registration form includes a checkbox that will let you 
volunteer. You can use this instead of emailing me, when you register for 
IETF 108.

- I currently have 39 volunteers. Last year had 149. I need more volunteers!
-
The IETF NomCom appoints people to fill the open slots on the LLC, IETF 
Trust, the IAB, and the IESG.


Ten voting members for the NomCom are selected in a verifiably random way 
from a pool of volunteers. The more volunteers, the better chance we have 
of choosing a random yet representative cross section of the IETF population.


The details of the operation of the NomCom can be found in BCP 10 (RFC 
8713). RFC 3797 details the selection algorithm.


Special for this year (and only this year), we also have RFC 8788 (one-off 
update to RFC 8713 / BCP 10) to tell us who is eligible to volunteer:


 Members of the IETF community must have attended at least three of
 the last five in-person IETF meetings in order to volunteer.

 The five meetings are the five most recent in-person meetings that
 ended prior to the date on which the solicitation for NomCom
 volunteers was submitted for distribution to the IETF community.
 Because no IETF 107 in-person meeting was held, for the 2020-2021
 Nominating Committee those five meetings are IETFs
   102 [Montreal, Canada; July 2018],
   103 [Bangkok, Thailand; November 2018],
   104 [Prague, Czech Republic; March 2019],
   105 [Montreal, Canada; July 2019], and
   106 [Singapore; November 2019].

Keep in mind that eligibility is based on in-person attendance at the five 
listed meetings. You can check your eligibility at: 
https://www.ietf.org/registration/nomcom.py.


If you qualify, please volunteer. Before you decide to volunteer, please 
remember that anyone appointed to this NomCom will not be considered as a 
candidate for any of the positions that the 2020 - 2021 NomCom is 
responsible for filling.


People commonly volunteer by ticking the box on IETF registration forms. 
The IETF 106 form did not ask whether people were willing to volunteer. 
IETF 107 did ask, but all those registrations were canceled. I have asked 
the Secretariat if it is possible to get the list if volunteers from 
canceled IETF 107 registrations. If that list is available, I will contact 
all who are verified as eligible. But given the uncertainty of this 
process, I would encourage people to volunteer directly (see the bottom of 
this email for instructions). Thank you for volunteering!


The list of people and posts whose terms end with the March 2021 IETF 
meeting, and thus the positions for which this NomCom is responsible, are


IETF Trust:
   Joel Halpern

LLC:
   Maja Andjelkovic

IAB:
   Jari Arkko
   Jeff Tantsura
   Mark Nottingham
   Stephen Farrell
   Wes Hardaker
   Zhenbin Li

IESG:
   Alissa Cooper, IETF Chair/GEN AD
   Alvaro Retana, RTG AD
   Barry Leiba, ART AD
   Deborah Brungard, RTG AD
   Éric Vyncke, INT AD
   Magnus Westerlund, TSV AD
   Roman Danyliw, SEC AD
   Warren Kumari, OPS AD

All appointments are for 2 years. The Routing area has 3 ADs and the 
General area has 1; all other areas have 2 ADs. Thus, all areas (that have 
more than one AD) have at least one continuing AD.


The primary activity for this NomCom will begin in July 2020 and should be 
completed in January 2021.  The NomCom will have regularly scheduled 
conference calls to ensure progress. There will be activities to collect 
requirements from the community, review candidate questionnaires, review 
feedback from community members about candidates, and talk to candidates.


While being a NomCom member does require some time commitment it is also a 
very rewarding experience.


As a member of the NomCom it is very important that you be willing and able 
to attend either videoconference or in-person meetings (which may not 
happen) during 14-20 November (IETF 109 - Bangkok) to conduct interviews. 
Videoconference attendance will be supported whether or not there are 
in-person meetings. Orientation and setting of the NomCom schedule will be 
done by videoconference during the week 20-24 July (exact time and date to 
be determined after NomCom membership is finalized on July 12), the week 
prior to IETF 108.  Being at IETF 110 (Prague) is 

[netmod] Fwd: Webex meeting invitation: draft-wwx-netmod-event-yang

[Lou Berger]

Hi,

The authors/contributors have a requested an informal meeting to discuss 
draft-wwx-netmod-event-yang. The WebEx details follow


Lou


--
--- Forwarded message ---
From: NETMOD Working Group messen...@webex.com
Date: June 3, 2020 11:06:40 PM
Subject: Webex meeting invitation: draft-wwx-netmod-event-yang
To: netmod-cha...@ietf.org


Hi, NETMOD Working Group,

NETMOD Working Group invites you to join this Webex meeting.


draft-wwx-netmod-event-yang
Thursday, June 4, 2020
10:00 am  |  (UTC-04:00) Eastern Time (US & Canada)  |  1 hr
Meeting number (access code): 161 402 8273
Meeting password: Eventyang



When it's time, join the meeting.
https://ietf.webex.com/ietf/j.php?MTID=m5bc1cca3bbd3c021e60553949beb1802

Add to Calendar
https://ietf.webex.com/ietf/j.php?MTID=mf1b9ffba5ea736246713678bf8b281d8




JOIN BY PHONE
1-650-479-3208 Call-in toll number (US/Canada)
Tap here to call (mobile phones only, hosts not supported): 
tel:%2B1-650-479-3208,,*01*1614028273%23%23*01*


Global call-in numbers
https://ietf.webex.com/ietf/globalcallin.php?MTID=m07dd892eaf46480c7ae6450c6ff93650


JOIN FROM A VIDEO SYSTEM OR APPLICATION
Dial sip:1614028...@ietf.webex.com
You can also dial 173.243.2.68 and enter your meeting number.


Join using Microsoft Lync or Microsoft Skype for Business
Dial sip:1614028273.i...@lync.webex.com


Can't join the meeting?
https://collaborationhelp.cisco.com/article/WBX29055


IMPORTANT NOTICE: Please note that this Webex service allows audio and 
other information sent during the session to be recorded, which may be 
discoverable in a legal matter. By joining this session, you automatically 
consent to such recordings. If you do not consent to being recorded, 
discuss your concerns with the host or do not join the session.
BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 10.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/New_York
TZURL:http://tzurl.org/zoneinfo-outlook/America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20200604T030604Z
ATTENDEE;CN="NETMOD Working Group";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:netmod-cha...@ietf.org
ORGANIZER;CN="NETMOD Working Group":MAILTO:netmod-cha...@ietf.org
DTSTART;TZID=America/New_York:20200604T10
DTEND;TZID=America/New_York:20200604T11
LOCATION:https://ietf.webex.com/ietf/j.php?MTID=m5bc1cca3bbd3c021e60553949beb1802
TRANSP:OPAQUE
SEQUENCE:1591239964
UID:e6d93fe1-a1da-4484-bc4d-d1d2b0d27e9d
DESCRIPTION:\n\n\n\nJOIN WEBEX MEETING\nhttps://ietf.webex.com/ietf/j.php?MTID=m5bc1cca3bbd3c021e60553949beb1802\nMeeting number (access code): 161 402 8273\n\n\nMeeting password: Eventyang\n\n\n\nJOIN BY PHONE\n1-650-479-3208 Call-in toll number (US/Canada)\nTap here to call (mobile phones only, hosts not supported): tel:%2B1-650-479-3208,,*01*1614028273%23%23*01*\n\nGlobal call-in numbers\nhttps://ietf.webex.com/ietf/globalcallin.php?MTID=m07dd892eaf46480c7ae6450c6ff93650\n\n\nJOIN FROM A VIDEO SYSTEM OR APPLICATION\nDial sip:1614028...@ietf.webex.com\nYou can also dial 173.243.2.68 and enter your meeting number.\n\n\nJoin using Microsoft Lync or Microsoft Skype for Business\nDial sip:1614028273.i...@lync.webex.com\n\n\n\nCan't join the meeting?\nhttps://collaborationhelp.cisco.com/article/WBX29055\n\n\nIMPORTANT NOTICE: Please note that this Webex service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session.\n
X-ALT-DESC;FMTTYPE=text/html:\n* {\npadding: 0;margin: 0;}\ntable {\n	border-collapse: separate; width =100%;	border: 0;	border-spacing: 0;}\n\ntr {\n	line-height: 18px;}\n\na, td {\n	font-size: 14px;	font-family: Arial;	color: #333;	word-wrap: break-word;	word-break: normal;	padding: 0;}\n\n.title {\n	font-size: 28px;}\n\n.image {\n	width: auto;	max-width: auto;}\n\n.footer {\n	width: 604px;}\n\n.main {\n\n}@media screen and (max-device-width: 800px) {\n	.title {\n		font-size: 22px !important;	}\n	.image {\n		width: auto !important;		max-width: 100% !important;	}\n	.footer {\n		width: 100% !important;		max-width: 604px !important\n	}\n	.main {\n		width: 100% !important;		max-width: 604px !important\n	}\n}\n\n\n\n	\n	\n		\n			\n\n\n\n\n\n			\n\n	\n		When it's time, join the Webex meeting here.\n	\n\n\n\n	\n		Meeting number (access code): 161 402 8273\n	\n\n			\n			\n			Meeting password:Eventyang\n\n\n	\n			\n\n	\n		\n			

[netmod] Fwd: Reminder: Survey on planning for possible online IETF meetings

[Lou Berger]

in case you missed it...



 Forwarded Message 
Subject:Reminder: Survey on planning for possible online IETF meetings
Date:   Mon, 04 May 2020 00:03:35 -0700
From:   IETF Executive Director 
Reply-To:   ietf108plann...@ietf.org
To: IETF Announcement List 



This is a reminder that we need the IETF community to help us plan for 
the possibility that one or more upcoming IETF meetings in 2020 and 
possibly 2021 may not be able to go ahead in person. You can help us 
with this by filling out the following survey:

https://www.surveymonkey.com/r/5328FFJ

So far we have 114 responses and we would ideally like 500 or more.

The survey contains the following pages and will take 15-20 minutes to 
complete:


1. Welcome
2. Online IETF 107 and the subsequent virtual interims
3. Replacing a cancelled in-person meeting
4. Online meeting format and timezone
5. Replicating humming
6. Replicating the hallway environment
7. Fees
8. Thanks and anything else

We run the survey in anonymous mode which means that we only see data 
that you explicitly provide.


Thank you in advance for your help.

--
Alissa Cooper, IETF Chair
Jay Daley, IETF Executive Director
Colin Perkins, IRTF Chair

___
IETF-Announce mailing list
ietf-annou...@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] virtual hum: draft-tao-netmod-yang-node-tags-01

[Lou Berger]

Hi,

    At our interim, we mentioned that we were going to do a virtual hum 
on draft-tao-netmod-yang-node-tags-01 - we will be conducting this hum 
via etherpad.   (Yes, this is a total experiment!)


To express your support or disinterest, please visit

https://etherpad.ietf.org:9009/p/notes-ietf-107-netmod-hums

and add you opinion via a single response to each three questions.  
Logins are not required, but we reserve the right to check IPs.


We plan to announce the results later this month.

Thank you,

Kent, Lou (and Joel)


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Fwd:  WG Last Call of CORECONF drafts: draft-ietf-core-yang-cbor-12, -sid-11, -comi-09, -yang-library-01

[Lou Berger]

Just a reminder that reviews are being solicited on these documents - 
particularly if you care anout encoding and transport...



 Forwarded Message 
Subject: 	[netmod]  WG Last Call of CORECONF drafts: 
draft-ietf-core-yang-cbor-12, -sid-11, -comi-09, -yang-library-01

Date:   Mon, 9 Mar 2020 14:04:32 +0100
From:   Carsten Bormann 
Reply-To:   c...@ietf.org WG 
To: core 
CC: netmod@ietf.org



It took us a long time to get the four CORECONF drafts in sync, but now 
we are ready for WGLC.


This starts a working group last call for
— draft-ietf-core-yang-cbor-12
— draft-ietf-core-sid-11
— draft-ietf-core-comi-09
— draft-ietf-core-yang-library-01

ending on

24:00 UTC on Tuesday, March 31, 2020.

(This includes some extra time for the IETF week and for cross-WG
coordination.)

This WGLC is copied to the netmod WG mailing list; please do have a look 
at these drafts as they are slated to become a part of the greater

YANG/NETCONF/RESTCONF family. We intend the discussion to be on the
CoRE mailing list, but if you find a fundamental issue with YANG or 
RESTCONF, feel free to discuss that on netmod instead.


Please start a new email thread for each major issue that will need
discussion and make sure the subject line includes the draft name and
some sort of name for the issue. (Minor issues such as typos can also
be sent to the authors.)

If you read the draft and think it looks fine, please send a one line 
email to the list or to the chairs letting us know that so we can get a 
feel of how broad the review has been.


(To reviewers and authors:) If you are aware of any patent claims that
might apply to systems that implement these drafts, please review BCP 78
and BCP 79 and make any appropriate IPR declaration before the last-call
ends. If you are not sure whether you need to make a declaration or not, 
please talk to the chairs and we will help.


Grüße, Carsten

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] netmod - New Interim Meeting Request

[Lou Berger]

Hi Rob,

    The intent was to deconflict with LSR WG (meeting right after us) 
and thought starting 4 hours later was pushing it too late for Asia. 
Joel, is on PT agreed - although I'm sure he'd prefer later.


WG,

If the time is problematic for you and you expect to present/actively 
participate please drop the chairs a note.


Thanks!

Lou

On 3/26/2020 4:21 PM, Rob Wilton (rwilton) wrote:

Hi Lou,

Some folks have previously complained about other meetings starting so early:

11 am UTC = 4 am San Jose = 7 pm Beijing

Just to double check that you are happy with a 4 am start for any West Coast 
based folks, perhaps there are not many of them involved in Netmod.

Thanks,
Rob



-Original Message-
From: Lou Berger 
Sent: 26 March 2020 19:06
To: Rob Wilton (rwilton) 
Cc: netmod-cha...@ietf.org; netmod@ietf.org
Subject: Re: netmod - New Interim Meeting Request

delete the one that does not map to 1100 UTC...

On 3/26/2020 12:06 PM, Rob Wilton (rwilton) wrote:

There has been a suggestion to list all the meetings in UTC, so I've

changed this request to 12:00 UTC.

Okay?

I've noticed two requests for the same time, presumably the second one

can just be deleted?

Thanks,
Rob



-Original Message-
From: IETF Meeting Session Request Tool 
Sent: 26 March 2020 15:51
To: session-requ...@ietf.org
Cc: lber...@labn.net; netmod-cha...@ietf.org; netmod@ietf.org; Rob
Wilton
(rwilton) 
Subject: netmod - New Interim Meeting Request


A new interim meeting request has just been submitted by Lou Berger.

This request requires approval by the Area Director of the Operations
and Management Area

The meeting can be approved here:
https://datatracker.ietf.org/meeting/interim/request/interim-2020-net
mod-
01



-
Working Group Name: Network Modeling
Area Name: Operations and Management Area Session Requester: Lou
Berger

Meeting Type: Virtual Meeting

Session 1:

Date: 2020-04-02
Start Time: 08:00 America/New_York
Duration: 02:00
Remote Participation Information: Remote participation information
will be obtained at the time of approval Agenda Note:

-



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] netmod - New Interim Meeting Request

[Lou Berger]

delete the one that does not map to 1100 UTC...

On 3/26/2020 12:06 PM, Rob Wilton (rwilton) wrote:

There has been a suggestion to list all the meetings in UTC, so I've changed 
this request to 12:00 UTC.

Okay?

I've noticed two requests for the same time, presumably the second one can just 
be deleted?

Thanks,
Rob



-Original Message-
From: IETF Meeting Session Request Tool 
Sent: 26 March 2020 15:51
To: session-requ...@ietf.org
Cc: lber...@labn.net; netmod-cha...@ietf.org; netmod@ietf.org; Rob Wilton
(rwilton) 
Subject: netmod - New Interim Meeting Request


A new interim meeting request has just been submitted by Lou Berger.

This request requires approval by the Area Director of the Operations and
Management Area

The meeting can be approved here:
https://datatracker.ietf.org/meeting/interim/request/interim-2020-netmod-
01



-
Working Group Name: Network Modeling
Area Name: Operations and Management Area Session Requester: Lou Berger

Meeting Type: Virtual Meeting

Session 1:

Date: 2020-04-02
Start Time: 08:00 America/New_York
Duration: 02:00
Remote Participation Information: Remote participation information will be
obtained at the time of approval Agenda Note:

-



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] I-D Action: draft-ietf-netmod-dsdl-00.txt

[Lou Berger]

Just an FYI - in trying to move this document out of the WG approval 
list to Dead WG document, this version got published.  I have moved it 
now to Dead WG Document state.  There may have been a better way to do 
this datatracker, but I clearly missed it.  My apologies if this causes 
any confusion.


Lou

(NetMod Co-Chair)

On 3/19/2020 9:37 AM, internet-dra...@ietf.org wrote:

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Network Modeling WG of the IETF.

 Title   : Representing Netconf Data Models using Document 
Schema Definition Languages (DSDL)
 Authors : Rohan Mahy
   Sharon Chisholm
   Ladislav Lhotka
Filename: draft-ietf-netmod-dsdl-00.txt
Pages   : 72
Date: 2008-07-07

Abstract:
This document describes a concrete approach for representing Netconf
and other IETF data models using the RelaxNG schema language and the
Schematron validation language, which are both part of ISO's Document
Schema Definition Languages (DSDL) standard.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-netmod-dsdl/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-netmod-dsdl-00
https://datatracker.ietf.org/doc/html/draft-ietf-netmod-dsdl-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Adoption of versioning design team docs

[Lou Berger]

All,

The adoption call ended yesterday.  While there is clearly work to do to 
reach consensus on these documents, they are all adopted as the starting 
point for the solutions that the WG will develop on these topics.  
Normal working group processing of these documents will continue on 
these documents.  This includes revisiting intended status of each 
document before submission for publication to the IESG.  We thank the 
design team for their hard work and important contributions!


Authors,

    Please repos each document, with only the file name and publication 
date changed.  The file names should all be in the form 
draft-ietf-netmod-.


Thank you,

Lou (and Kent and Joel)

On 3/2/2020 5:29 PM, Lou Berger wrote:

Hi,
We'd like to start a two week adoption call for the set of documents described 
below by Rob.  To be specific, this includes
1) draft-verdt-netmod-yang-solutions-03
2) draft-verdt-netmod-yang-module-versioning-01
3) draft-verdt-netmod-yang-semver-01
4) draft-rwilton-netmod-yang-packages-03
5) draft-wilton-netmod-yang-ver-selection-02
6) draft-verdt-netmod-yang-schema-comparison-00

The adoption call ends in two weeks, on March 16.

Please voice your support or objections on list.  While we prefer to adopt as a 
set, objections on specific documents are acceptable.

Netmod Chairs

On 2/29/2020 2:21 AM, Rob Wilton (rwilton) wrote:

Netmod chairs,

The version selection draft draft-wilton-netmod-yang-ver-selection-02 is now 
posted.  With that, the YANG versioning design team would like to please 
request you make an WG adoption call for these documents.

The updated full list is:

1) draft-verdt-netmod-yang-solutions-03
   - Solution overview, updated since 106 to cover updates to version selection 
and schema comparison drafts.

2) draft-verdt-netmod-yang-module-versioning-01
   - Base module versioning solution, unchanged from the version presented at 
106.

3) draft-verdt-netmod-yang-semver-01
   - YANG Semantic version numbers, unchanged from the version presented at 106.

4) draft-rwilton-netmod-yang-packages-03
   - YANG packages draft, updated since 106
   
5) draft-wilton-netmod-yang-ver-selection-02

   - Version selection, updated since 106, as per notes below

6) draft-verdt-netmod-yang-schema-comparison-00
   - Schema comparison tooling, unchanged from the version presented at 106.

The main changes to the version selection draft are:
   - We have tried to simplify the model, but at the same time give servers 
more flexibility about how they implement version selection and what it can be 
used for.  E.g. if the server wants to allow a client to choose between 
different schema versions, but require that all clients use the same schema 
version, that is now possible
   - The draft explicitly disallows schema-selection happening mid-session
   - The solution allows the server to require clients to configure schema-sets 
before they are used
   - The solution provides more information about which schema-sets are 
compatible with each other

Regards,
Rob




___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Adoption of versioning design team docs

[Lou Berger]

Hi,
We'd like to start a two week adoption call for the set of documents described 
below by Rob.  To be specific, this includes
1) draft-verdt-netmod-yang-solutions-03
2) draft-verdt-netmod-yang-module-versioning-01
3) draft-verdt-netmod-yang-semver-01
4) draft-rwilton-netmod-yang-packages-03
5) draft-wilton-netmod-yang-ver-selection-02
6) draft-verdt-netmod-yang-schema-comparison-00

The adoption call ends in two weeks, on March 16.

Please voice your support or objections on list.  While we prefer to adopt as a 
set, objections on specific documents are acceptable.

Netmod Chairs

On 2/29/2020 2:21 AM, Rob Wilton (rwilton) wrote:


Netmod chairs,

The version selection draft draft-wilton-netmod-yang-ver-selection-02 is now 
posted.  With that, the YANG versioning design team would like to please 
request you make an WG adoption call for these documents.

The updated full list is:

1) draft-verdt-netmod-yang-solutions-03
   - Solution overview, updated since 106 to cover updates to version selection 
and schema comparison drafts.

2) draft-verdt-netmod-yang-module-versioning-01
   - Base module versioning solution, unchanged from the version presented at 
106.

3) draft-verdt-netmod-yang-semver-01
   - YANG Semantic version numbers, unchanged from the version presented at 106.

4) draft-rwilton-netmod-yang-packages-03
   - YANG packages draft, updated since 106
   
5) draft-wilton-netmod-yang-ver-selection-02

   - Version selection, updated since 106, as per notes below

6) draft-verdt-netmod-yang-schema-comparison-00
   - Schema comparison tooling, unchanged from the version presented at 106.

The main changes to the version selection draft are:
   - We have tried to simplify the model, but at the same time give servers 
more flexibility about how they implement version selection and what it can be 
used for.  E.g. if the server wants to allow a client to choose between 
different schema versions, but require that all clients use the same schema 
version, that is now possible
   - The draft explicitly disallows schema-selection happening mid-session
   - The solution allows the server to require clients to configure schema-sets 
before they are used
   - The solution provides more information about which schema-sets are 
compatible with each other

Regards,
Rob


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regarding IPR on draft-verdt-netmod-yang-module-versioning-01

[Lou Berger]

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 disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate.

We note that all DT members are listed as contributors.  If you 
contributed to the document please respond.  Alternatively, please feel 
free to state that you didn't materially contribute to the draft and 
would like your name removed from the contribution section (and moved to 
acknowledgments after WG adoption).


If you are listed as a document author or contributor please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
NetMod WG Chairs

PS Please include all listed in the headers of this message in your
response.



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regarding IPR on draft-rwilton-netmod-yang-packages-03

[Lou Berger]

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 disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate.

We note that all DT members are listed as contributors.  If you 
contributed to the document please respond.  Alternatively, please feel 
free to state that you didn't materially contribute to the draft and 
would like your name removed from the contribution section (and moved to 
acknowledgments after WG adoption).


If you are listed as a document author or contributor please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
NetMod WG Chairs

PS Please include all listed in the headers of this message in your
response.



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regarding IPR on draft-verdt-netmod-yang-semver-01

[Lou Berger]

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 disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate.

We note that all DT members are listed as contributors.  If you 
contributed to the document please respond.  Alternatively, please feel 
free to state that you didn't materially contribute to the draft and 
would like your name removed from the contribution section (and moved to 
acknowledgments after WG adoption).


If you are listed as a document author or contributor please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
NetMod WG Chairs

PS Please include all listed in the headers of this message in your
response.



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regarding IPR on draft-verdt-netmod-yang-schema-comparison-00

[Lou Berger]

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 disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate.

We note that all DT members are listed as contributors.  If you 
contributed to the document please respond.  Alternatively, please feel 
free to state that you didn't materially contribute to the draft and 
would like your name removed from the contribution section (and moved to 
acknowledgments after WG adoption).


If you are listed as a document author or contributor please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
NetMod WG Chairs

PS Please include all listed in the headers of this message in your
response.



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regarding IPR on draft-wilton-netmod-yang-ver-selection-02

[Lou Berger]

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 disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate.

We note that all DT members are listed as contributors.  If you 
contributed to the document please respond.  Alternatively, please feel 
free to state that you didn't materially contribute to the draft and 
would like your name removed from the contribution section (and moved to 
acknowledgments after WG adoption).


If you are listed as a document author or contributor please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
NetMod WG Chairs

PS Please include all listed in the headers of this message in your
response.



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Regarding IPR on draft-verdt-netmod-yang-solutions-03

[Lou Berger]

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 disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate.

We note that all DT members are listed as contributors.  If you 
contributed to the document please respond.  Alternatively, please feel 
free to state that you didn't materially contribute to the draft and 
would like your name removed from the contribution section (and moved to 
acknowledgments after WG adoption).


If you are listed as a document author or contributor please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author.

NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
NetMod WG Chairs

PS Please include all listed in the headers of this message in your
response.



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Version selection draft posted

[Lou Berger]

Excellent wort all -- stay tuned for the adoption process!

On 2/29/2020 2:21 AM, Rob Wilton (rwilton) wrote:

Netmod chairs,

The version selection draft draft-wilton-netmod-yang-ver-selection-02 is now 
posted.  With that, the YANG versioning design team would like to please 
request you make an WG adoption call for these documents.

The updated full list is:

1) draft-verdt-netmod-yang-solutions-03
  - Solution overview, updated since 106 to cover updates to version selection 
and schema comparison drafts.

2) draft-verdt-netmod-yang-module-versioning-01
  - Base module versioning solution, unchanged from the version presented at 
106.

3) draft-verdt-netmod-yang-semver-01
  - YANG Semantic version numbers, unchanged from the version presented at 106.

4) draft-rwilton-netmod-yang-packages-03
  - YANG packages draft, updated since 106
  
5) draft-wilton-netmod-yang-ver-selection-02

  - Version selection, updated since 106, as per notes below

6) draft-verdt-netmod-yang-schema-comparison-00
  - Schema comparison tooling, unchanged from the version presented at 106.

The main changes to the version selection draft are:
  - We have tried to simplify the model, but at the same time give servers more 
flexibility about how they implement version selection and what it can be used 
for.  E.g. if the server wants to allow a client to choose between different 
schema versions, but require that all clients use the same schema version, that 
is now possible
  - The draft explicitly disallows schema-selection happening mid-session
  - The solution allows the server to require clients to configure schema-sets 
before they are used
  - The solution provides more information about which schema-sets are 
compatible with each other

Regards,
Rob



-Original Message-
From: netmod  On Behalf Of Rob Wilton (rwilton)
Sent: 19 February 2020 17:03
To: netmod@ietf.org
Subject: Re: [netmod] FW: New Version Notification for draft-rwilton-
netmod-yang-packages-03.txt

Just as a reminder of what the full set of versioning documents are that
we will ask the chairs to consider for WG adoption (in case you wish to
start reviewing some of the drafts early), are listed them below, and I
have indicated which ones have been (or will be) updated since 106.

1) draft-verdt-netmod-yang-solutions-03
  - Solution overview, updated since 106 to cover updates to version
selection and schema comparison drafts.

2) draft-verdt-netmod-yang-module-versioning-01
  - Base module versioning solution, unchanged from the version presented
at 106.

3) draft-verdt-netmod-yang-semver-01
  - YANG Semantic version numbers, unchanged from the version presented at
106.

4) draft-rwilton-netmod-yang-packages-03
  - YANG packages draft, updated since 106, as per notes below.

5) draft-verdt-netmod-yang-module-versioning-02 (TBD)
  - Version selection, will post updated version soon, current aim is for
the end of Feb.

6) draft-verdt-netmod-yang-schema-comparison-00
  - Schema comparison tooling, unchanged from the version presented at 106.

Thanks,
Rob



-Original Message-
From: Lou Berger 
Sent: 19 February 2020 16:37
To: Rob Wilton (rwilton) ; netmod@ietf.org
Subject: Re: [netmod] FW: New Version Notification for draft-rwilton-
netmod-yang-packages-03.txt

Thanks Rob/Team!

All,

      We're planning to run the adoption poll on the versioning
document set  once the next update of the selection draft is published
-- so please feel free to get started reading/commenting on this

document now.

Lou

On 2/19/2020 11:31 AM, Rob Wilton (rwilton) wrote:

FYI, I've posted an updated version of the YANG packages draft.
This is

the version that we plan to request a WG adoption call on, once we
have an updated version of the version selection draft posted
(hopefully ready soon).

To highlight the main changes:
   - Added a section to describe how YANG packages relate to
datastore

schema, along with guidance on how to structure package definitions.

   - Unified the package definition on the server vs in YANG instance

data documents.  In particular, the on-server definition no longer
reuses the module-sets from YANG library.  This also simplifies the
explanation of how these definitions relate since the same common

grouping is reused.

   - Move packages into its own top level container, rather than
being

under YANG library.

   - Changed the binding between datastore schema in YANG library and

packages.  Before there was a 1:1 binding from datastore schema to
package definition.  It has been changed to a 1:N binding, i.e. a
datastore scheme is represented by a union of compatible packages.
This aligns with how the relationship is defined in the version

selection draft.

Thanks,
Rob


-Original Message-
From: internet-dra...@ietf.org 
Sent: 19 February 2020 16:15
To: Jason Sterne ; Reshad Rahman (rrahman)
; Rob Wilton (rwilton) ; Joe
Clarke (jclarke) ; Wu Bo ;
Bo Wu 
Subject: New Version Notification for
draft-rwilton-netmod-yang

Re: [netmod] FW: New Version Notification for draft-rwilton-netmod-yang-packages-03.txt

[Lou Berger]

Thanks Rob/Team!

All,

    We're planning to run the adoption poll on the versioning document 
set  once the next update of the selection draft is published -- so 
please feel free to get started reading/commenting on this document now.


Lou

On 2/19/2020 11:31 AM, Rob Wilton (rwilton) wrote:

FYI, I've posted an updated version of the YANG packages draft.  This is the 
version that we plan to request a WG adoption call on, once we have an updated 
version of the version selection draft posted (hopefully ready soon).

To highlight the main changes:
  - Added a section to describe how YANG packages relate to datastore schema, 
along with guidance on how to structure package definitions.
  - Unified the package definition on the server vs in YANG instance data 
documents.  In particular, the on-server definition no longer reuses the 
module-sets from YANG library.  This also simplifies the explanation of how 
these definitions relate since the same common grouping is reused.
  - Move packages into its own top level container, rather than being under 
YANG library.
  - Changed the binding between datastore schema in YANG library and packages.  
Before there was a 1:1 binding from datastore schema to package definition.  It 
has been changed to a 1:N binding, i.e. a datastore scheme is represented by a 
union of compatible packages.  This aligns with how the relationship is defined 
in the version selection draft.

Thanks,
Rob


-Original Message-
From: internet-dra...@ietf.org 
Sent: 19 February 2020 16:15
To: Jason Sterne ; Reshad Rahman (rrahman) ; Rob Wilton 
(rwilton) ; Joe Clarke (jclarke) ; Wu Bo 
; Bo Wu 
Subject: New Version Notification for draft-rwilton-netmod-yang-packages-03.txt


A new version of I-D, draft-rwilton-netmod-yang-packages-03.txt
has been successfully submitted by Robert Wilton and posted to the IETF 
repository.

Name:   draft-rwilton-netmod-yang-packages
Revision:   03
Title:  YANG Packages
Document date:  2020-02-19
Group:  Individual Submission
Pages:  56
URL:
https://www.ietf.org/internet-drafts/draft-rwilton-netmod-yang-packages-03.txt
Status: 
https://datatracker.ietf.org/doc/draft-rwilton-netmod-yang-packages/
Htmlized:   
https://tools.ietf.org/html/draft-rwilton-netmod-yang-packages-03
Htmlized:   
https://datatracker.ietf.org/doc/html/draft-rwilton-netmod-yang-packages
Diff:   
https://www.ietf.org/rfcdiff?url2=draft-rwilton-netmod-yang-packages-03

Abstract:
This document defines YANG packages, a versioned organizational
structure holding a set of related YANG modules, that collectively
define a YANG schema.  It describes how packages: are represented on
a server, can be defined in offline YANG instance data documents, and
can be used to define the schema associated with YANG instance data
documents.

   



Please note that it may take a couple of minutes from the time of submission 
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Question draft-wwx-netmod-event-yang

[Lou Berger]

Qin,

    if you want to  be agnostic of protocol, the document will need to 
be updated from its current netconf specific form.


Thanks,

Lou

On 11/19/2019 2:45 AM, Qin Wu wrote:
Talking with our coauthors, we believe should not limit usage of this 
model only to netconf. Other protocols could be applied. Let us know 
if any update is needed.



吴钦 Qin
Mobile：+86-13914734360 (Mobile Number)
Email：bill...@huawei.com 



*发件人： *Lou Bergermailto:lber...@labn.net>>
*收件人： 
*draft-wwx-netmod-event-yang>;NETMOD 
Groupmailto:netmod@ietf.org>>

*主题： *[netmod] Question draft-wwx-netmod-event-yang
*时间： *2019-11-19 16:23:41

Hi,

 Authors, is there a reason tat the body of the text is only focused
on netconf?  Why would you limit this work to any specific protocol?

Thanks,

Lou

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod


___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Question draft-wwx-netmod-event-yang

[Lou Berger]

Hi,

    Authors, is there a reason tat the body of the text is only focused 
on netconf?  Why would you limit this work to any specific protocol?


Thanks,

Lou

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] today's session info

[Lou Berger]

FYI

Tuesday, November 19, 2019 (+08)
Session 1    "10:00-12:00    Tuesday Morning session I"
Session 2    "15:20-16:50    Tuesday Afternoon session II"
Slides: https://datatracker.ietf.org/meeting/106/session/netmod
Etherpad: https://etherpad.ietf.org/p/notes-ietf-106-netmod
Meetecho: http://www.meetecho.com/ietf106/netmod/
Jabber:    xmpp:net...@jabber.ietf.org?join

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] Draft IETF 106 Agenda available

[Lou Berger]

All,

   A draft agenda for our 106 meeting in Singapore has been posted.
   Please take a look and let us know if any changes are needed.

https://datatracker.ietf.org/doc/agenda-106-netmod


Presenters:

   Please provide your slides to the chairs no later than the Friday
   before our meeting.

   If you requested "remote" presentation, your request has been
   submitted to the MeetEcho team.

Authors of WG documents
    If you are not on the agenda , please send a update on status and 
plans for the document no later than Wednesday Nov 13.


Lou (Kent and Joel)

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] I-D Action: draft-wwx-netmod-event-yang-04.txt

[Lou Berger]

Qin,
Thanks for the update.

To answer your question as well as respond to the related thread, as
chair, I generally think it best to adopt once there is consensus in the
WG on a direction to take with respect to the topic covered by a draft.
 That is not to say that a fully formed or documented solution is
required at adoption but that if there are several different approaches
available, that the adopted work reflects the direction that the WG will
pursue.

In this case, the current rev is certainly a step in that direction, but
the WG still as two different basic approaches available to it in this
draft and draft-bryskin-netconf-automation-yang.  I personally always
prefer it when individual draft authors can find common ground and come
to the WG with a single (unified) proposal rather than ask the working
group to choose one over the other.  I'm not sure who among the authors
will be in Singapore, but perhaps the authors can take the opportunity
to meet to discuss the possibly of such a unified proposal as well
report back to the working group on their progress/status.  Time
permitting, we should at least hear a summary of each approach so that
if a unified approach is not proposed that the WG is better informed on
the proposals.

Cheers,
Lou

On 11/1/19 11:02 PM, Qin Wu wrote:
> v-04 is posted to address chairs' comments, 
> https://datatracker.ietf.org/doc/html/draft-wwx-netmod-event-yang-04
> the main changes include:
>o  Add text in introduction section to clarify the usage examples of
>   ECA policy
>o  Update objective section to align with use cases.
>o  Clarify the relationship between target and policy variable.
>o  Change variation trigger condition back into threshold trigger
>   condition and clarify the usage of three trigger conditions.
>o  Remove Event MIB related section.
>o  Add new coauthors and contributors.
> Chairs, what is the next step?
> 
> -Qin (on behalf of authors)
> 
> -邮件原件-
> 发件人: I-D-Announce [mailto:i-d-announce-boun...@ietf.org] 代表 
> internet-dra...@ietf.org
> 发送时间: 2019年11月2日 10:57
> 收件人: i-d-annou...@ietf.org
> 主题: I-D Action: draft-wwx-netmod-event-yang-04.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> 
> 
> Title   : A YANG Data model for ECA Policy Management
> Authors : Michael Wang
>   Qin Wu
>   Chongfeng Xie
>   Igor Bryskin
>   Xufeng Liu
>   Alexander Clemm
>   Henk Birkholz
>   Tianran Zhou
>   Filename: draft-wwx-netmod-event-yang-04.txt
>   Pages   : 32
>   Date: 2019-11-01
> 
> Abstract:
>RFC8328 defines a policy-based management framework that allow
>definition of a data model to be used to represent high-level,
>possibly network-wide policies.  Policy discussed in RFC8328 are
>classified into imperative policy and declarative policy, ECA policy
>is an typical example of imperative policy.  This document defines an
>YANG data model for the ECA policy management.  The ECA policy YANG
>provides the ability for the network management function (within a
>controller, an orchestrator, or a network element) to control the
>configuration and monitor state change on the network element and
>take simple and instant action when a trigger condition on the system
>state is met.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-wwx-netmod-event-yang/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-wwx-netmod-event-yang-04
> https://datatracker.ietf.org/doc/html/draft-wwx-netmod-event-yang-04
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-wwx-netmod-event-yang-04
> 
> 
> Please note that it may take a couple of minutes from the time of submission 
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> ___
> I-D-Announce mailing list
> i-d-annou...@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or 
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod