A YANG Data Model for Virtual Network (VN) Operations
draft-ietf-teas-actn-vn-yang-24
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2024-04-11
|
24 | Vishnu Beeram | # Document Shepherd Write-Up for Group Documents *This version is dated 4 July 2022.* Thank you for your service as a document shepherd. Among the … # Document Shepherd Write-Up for Group Documents *This version is dated 4 July 2022.* Thank you for your service as a document shepherd. Among the responsibilities is answering the questions in this write-up to give helpful context to Last Call and Internet Engineering Steering Group ([IESG][1]) reviewers, and your diligence in completing it is appreciated. The full role of the shepherd is further described in [RFC 4858][2]. You will need the cooperation of the authors and editors to complete these checks. Note that some numbered items contain multiple related questions; please be sure to answer all of them. ## Document History 1. Does the working group (WG) consensus represent the strong concurrence of a few individuals, with others being silent, or did it reach broad agreement? “Strong concurrence of a few individuals, with others being silent" is a reasonable characterization. 2. Was there controversy about particular points, or were there decisions where the consensus was particularly rough? There was no controversy. There were no decisions where the consensus was particularly rough. 3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarize the areas of conflict in separate email messages to the responsible Area Director. (It should be in a separate email because this questionnaire is publicly available.) No one has threatened an appeal. No one has indicated extreme discontent. 4. For protocol documents, are there existing implementations of the contents of the document? Have a significant number of potential implementers indicated plans to implement? Are any existing implementations reported somewhere, either in the document itself (as [RFC 7942][3] recommends) or elsewhere (where)? This document provides a YANG data model for Virtual Network (VN) operations. The document does not include any implementation report. This document is driven by multiple vendors/operators and is expected to be implemented in some form. ## Additional Reviews 5. Do the contents of this document closely interact with technologies in other IETF working groups or external organizations, and would it therefore benefit from their review? Have those reviews occurred? If yes, describe which reviews took place. The data model provided in this document can work together with service models discussed in other WGs (OPSAWG, CCAMP). However, there isn't enough in-depth detail or dependency on any of these models to warrant a review from these other WGs. 6. Describe how the document meets any required formal expert review criteria, such as the MIB Doctor, YANG Doctor, media type, and URI type reviews. The document has been reviewed by a YANG Doctor. Please refer to https://datatracker.ietf.org/doc/review-ietf-teas-actn-vn-yang-10-yangdoctors-early-bierman-2020-12-20/ The document has also been reviewed by the Routing Directorate. Please refer to https://datatracker.ietf.org/doc/review-ietf-teas-actn-vn-yang-22-rtgdir-early-dukes-2024-01-23/ 7. If the document contains a YANG module, has the final version of the module been checked with any of the [recommended validation tools][4] for syntax and formatting validation? If there are any resulting errors or warnings, what is the justification for not fixing them at this time? Does the YANG module comply with the Network Management Datastore Architecture (NMDA) as specified in [RFC 8342][5]? Yes, the current version of the YANG module has been checked with recommended validation tools. Please refer to the YANG validation results on datatracker: https://datatracker.ietf.org/doc/draft-ietf-teas-actn-vn-yang/ There are currently 0 errors and 2 warnings listed against the YANG module. The 2 yanglint warnings are specific to an imported module (ietf-te-types) and are not pertinent to this document. The YANG module complies with the Network Management Datastore Architecture (NMDA) as specified in [RFC 8342] 8. Describe reviews and automated checks performed to validate sections of the final version of the document written in a formal language, such as XML code, BNF rules, MIB definitions, CBOR's CDDL, etc. The YANG code in the document has been validated using prescribed YANG review Tools. The document has been reviewed by a YANG Doctor. ## Document Shepherd Checks 9. Based on the shepherd's review of the document, is it their opinion that this document is needed, clearly written, complete, correctly designed, and ready to be handed off to the responsible Area Director? Yes, it is the shepherd's opinion that the document is needed, reasonably well written, complete and ready to be handed off to the responsible Area Director. 10. Several IETF Areas have assembled [lists of common issues that their reviewers encounter][6]. For which areas have such issues been identified and addressed? For which does this still need to happen in subsequent Reviews? It is the shepherd's opinion that the document sufficiently addresses all the issues specified in [6]. 11. What type of RFC publication is being requested on the IETF stream ([Best Current Practice][12], [Proposed Standard, Internet Standard][13], [Informational, Experimental or Historic][14])? Why is this the proper type of RFC? Do all Datatracker state attributes correctly reflect this intent? The type of publication being requested is "Standards Track". This is appropriate for a document that provides a YANG data model for Virtual Network Operations. All Datatracker state attributes correctly reflect this intent. 12. Have reasonable efforts been made to remind all authors of the intellectual property rights (IPR) disclosure obligations described in [BCP 79][7]? To the best of your knowledge, have all required disclosures been filed? If not, explain why. If yes, summarize any relevant discussion, including links to publicly-available messages when applicable. The TEAS WG conducts an IPR poll before an individual draft becomes a WG document and before a WG document goes to last call. The WG process requires IPR compliance statement from all authors and contributors listed in the document. This process was duly applied to the document. There is an IPR disclosure associated with this document: https://datatracker.ietf.org/ipr/4215/ Pre-WGLC IPR Poll: Please refer to entries dated 2023-07-04 and 2023-07-10 at https://datatracker.ietf.org/doc/draft-ietf-teas-actn-vn-yang/history/ Pre-WG-Adoption IPR Poll: Please refer to entry dated 2018-05-10 at https://datatracker.ietf.org/doc/draft-lee-teas-actn-vn-yang/history/ 13. Has each author, editor, and contributor shown their willingness to be listed as such? If the total number of authors and editors on the front page is greater than five, please provide a justification. The authors/editors and contributors have had sufficient opportunities to express unwillingness to be listed as such. There are 5 authors listed on the front page and 7 other contributors listed later in the document. 14. Document any remaining I-D nits in this document. Simply running the [idnits tool][8] is not enough; please review the ["Content Guidelines" on authors.ietf.org][15]. (Also note that the current idnits tool generates some incorrect warnings; a rewrite is underway.) There are no I-D nits that are yet to be resolved. 15. Should any informative references be normative or vice-versa? See the [IESG Statement on Normative and Informative References][16]. All listed informative and normative references are appropriate. 16. List any normative references that are not freely available to anyone. Did the community have sufficient access to review any such normative references? All listed normative references are freely available. 17. Are there any normative downward references (see [RFC 3967][9] and [BCP 97][10]) that are not already listed in the [DOWNREF registry][17]? If so, list them. There are no normative downward references. All listed normative references are published RFCs. 18. Are there normative references to documents that are not ready to be submitted to the IESG for publication or are otherwise in an unclear state? If so, what is the plan for their completion? All listed normative references are published RFCs. 19. Will publication of this document change the status of any existing RFCs? If so, does the Datatracker metadata correctly reflect this and are those RFCs listed on the title page, in the abstract, and discussed in the introduction? If not, explain why and point to the part of the document where the relationship of this document to these other RFCs is discussed. The publication of this document will not change the status of any existing RFCs. 20. Describe the document shepherd's review of the IANA considerations section, especially with regard to its consistency with the body of the document. Confirm that all aspects of the document requiring IANA assignments are associated with the appropriate reservations in IANA registries. Confirm that any referenced IANA registries have been clearly identified. Confirm that each newly created IANA registry specifies its initial contents, allocations procedures, and a reasonable name (see [RFC 8126][11]). The allocation requests made to the IANA in this document are appropriate and the referenced IANA registries are clearly identified. There are no new IANA registries proposed in this document. 21. List any new IANA registries that require Designated Expert Review for future allocations. Are the instructions to the Designated Expert clear? Please include suggestions of designated experts, if appropriate. There are no new IANA registries proposed in this document. [1]: https://www.ietf.org/about/groups/iesg/ [2]: https://www.rfc-editor.org/rfc/rfc4858.html [3]: https://www.rfc-editor.org/rfc/rfc7942.html [4]: https://wiki.ietf.org/group/ops/yang-review-tools [5]: https://www.rfc-editor.org/rfc/rfc8342.html [6]: https://wiki.ietf.org/group/iesg/ExpertTopics [7]: https://www.rfc-editor.org/info/bcp79 [8]: https://www.ietf.org/tools/idnits/ [9]: https://www.rfc-editor.org/rfc/rfc3967.html [10]: https://www.rfc-editor.org/info/bcp97 [11]: https://www.rfc-editor.org/rfc/rfc8126.html [12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5 [13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1 [14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2 [15]: https://authors.ietf.org/en/content-guidelines-overview [16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/ [17]: https://datatracker.ietf.org/doc/downref/ |
2024-04-11
|
24 | Vishnu Beeram | IETF WG state changed to Submitted to IESG for Publication from WG Consensus: Waiting for Write-Up |
2024-04-11
|
24 | Vishnu Beeram | IESG state changed to Publication Requested from I-D Exists |
2024-04-11
|
24 | (System) | Changed action holders to John Scudder (IESG state changed) |
2024-04-11
|
24 | Vishnu Beeram | Responsible AD changed to John Scudder |
2024-04-11
|
24 | Vishnu Beeram | Document is now in IESG state Publication Requested |
2024-04-11
|
24 | Vishnu Beeram | Changed consensus to Yes from Unknown |
2024-04-11
|
24 | Vishnu Beeram | Includes Yang Data Model |
2024-04-11
|
24 | Vishnu Beeram | Intended Status changed to Proposed Standard from None |
2024-04-11
|
24 | Vishnu Beeram | Tag Awaiting Expert Review/Resolution of Issues Raised cleared. |
2024-03-16
|
24 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-24.txt |
2024-03-16
|
24 | Dhruv Dhody | New version accepted (logged-in submitter: Dhruv Dhody) |
2024-03-16
|
24 | Dhruv Dhody | Uploaded new revision |
2024-03-13
|
23 | Vishnu Beeram | # Document Shepherd Write-Up for Group Documents *This version is dated 4 July 2022.* Thank you for your service as a document shepherd. Among the … # Document Shepherd Write-Up for Group Documents *This version is dated 4 July 2022.* Thank you for your service as a document shepherd. Among the responsibilities is answering the questions in this write-up to give helpful context to Last Call and Internet Engineering Steering Group ([IESG][1]) reviewers, and your diligence in completing it is appreciated. The full role of the shepherd is further described in [RFC 4858][2]. You will need the cooperation of the authors and editors to complete these checks. Note that some numbered items contain multiple related questions; please be sure to answer all of them. ## Document History 1. Does the working group (WG) consensus represent the strong concurrence of a few individuals, with others being silent, or did it reach broad agreement? “Strong concurrence of a few individuals, with others being silent" is a reasonable characterization. 2. Was there controversy about particular points, or were there decisions where the consensus was particularly rough? There was no controversy. There were no decisions where the consensus was particularly rough. 3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarize the areas of conflict in separate email messages to the responsible Area Director. (It should be in a separate email because this questionnaire is publicly available.) No one has threatened an appeal. No one has indicated extreme discontent. 4. For protocol documents, are there existing implementations of the contents of the document? Have a significant number of potential implementers indicated plans to implement? Are any existing implementations reported somewhere, either in the document itself (as [RFC 7942][3] recommends) or elsewhere (where)? This document provides a YANG data model for Virtual Network (VN) operations. The document does not include any implementation report. This document is driven by multiple vendors/operators and is expected to be implemented in some form. ## Additional Reviews 5. Do the contents of this document closely interact with technologies in other IETF working groups or external organizations, and would it therefore benefit from their review? Have those reviews occurred? If yes, describe which reviews took place. The data model provided in this document can work together with service models discussed in other WGs (OPSAWG, CCAMP). However, there isn't enough in-depth detail or dependency on any of these models to warrant a review from these other WGs. 6. Describe how the document meets any required formal expert review criteria, such as the MIB Doctor, YANG Doctor, media type, and URI type reviews. The document has been reviewed by a YANG Doctor. Please refer to https://datatracker.ietf.org/doc/review-ietf-teas-actn-vn-yang-10-yangdoctors-early-bierman-2020-12-20/ The document has also been reviewed by the Routing Directorate. Please refer to https://datatracker.ietf.org/doc/review-ietf-teas-actn-vn-yang-22-rtgdir-early-dukes-2024-01-23/ 7. If the document contains a YANG module, has the final version of the module been checked with any of the [recommended validation tools][4] for syntax and formatting validation? If there are any resulting errors or warnings, what is the justification for not fixing them at this time? Does the YANG module comply with the Network Management Datastore Architecture (NMDA) as specified in [RFC 8342][5]? Yes, the current version of the YANG module has been checked with recommended validation tools. Please refer to the YANG validation results on datatracker: https://datatracker.ietf.org/doc/draft-ietf-teas-actn-vn-yang/ There are currently 0 errors and 2 warnings listed against the YANG module. The 2 yanglint warnings are specific to an imported module (ietf-te-types) and are not pertinent to this document. The YANG module complies with the Network Management Datastore Architecture (NMDA) as specified in [RFC 8342] 8. Describe reviews and automated checks performed to validate sections of the final version of the document written in a formal language, such as XML code, BNF rules, MIB definitions, CBOR's CDDL, etc. The YANG code in the document has been validated using prescribed YANG review Tools. The document has been reviewed by a YANG Doctor. ## Document Shepherd Checks 9. Based on the shepherd's review of the document, is it their opinion that this document is needed, clearly written, complete, correctly designed, and ready to be handed off to the responsible Area Director? Yes, it is the shepherd's opinion that the document is needed, reasonably well written, complete and ready to be handed off to the responsible Area Director. 10. Several IETF Areas have assembled [lists of common issues that their reviewers encounter][6]. For which areas have such issues been identified and addressed? For which does this still need to happen in subsequent Reviews? It is the shepherd's opinion that the document sufficiently addresses all the issues specified in [6]. 11. What type of RFC publication is being requested on the IETF stream ([Best Current Practice][12], [Proposed Standard, Internet Standard][13], [Informational, Experimental or Historic][14])? Why is this the proper type of RFC? Do all Datatracker state attributes correctly reflect this intent? The type of publication being requested is "Standards Track". This is appropriate for a document that provides a YANG data model for Virtual Network Operations. All Datatracker state attributes correctly reflect this intent. 12. Have reasonable efforts been made to remind all authors of the intellectual property rights (IPR) disclosure obligations described in [BCP 79][7]? To the best of your knowledge, have all required disclosures been filed? If not, explain why. If yes, summarize any relevant discussion, including links to publicly-available messages when applicable. The TEAS WG conducts an IPR poll before an individual draft becomes a WG document and before a WG document goes to last call. The WG process requires IPR compliance statement from all authors and contributors listed in the document. This process was duly applied to the document. There is an IPR disclosure associated with this document: https://datatracker.ietf.org/ipr/4215/ Pre-WGLC IPR Poll: Please refer to entries dated 2023-07-04 and 2023-07-10 at https://datatracker.ietf.org/doc/draft-ietf-teas-actn-vn-yang/history/ Pre-WG-Adoption IPR Poll: Please refer to entry dated 2018-05-10 at https://datatracker.ietf.org/doc/draft-lee-teas-actn-vn-yang/history/ 13. Has each author, editor, and contributor shown their willingness to be listed as such? If the total number of authors and editors on the front page is greater than five, please provide a justification. The authors/editors and contributors have had sufficient opportunities to express unwillingness to be listed as such. There are 5 authors listed on the front page and 7 other contributors listed later in the document. 14. Document any remaining I-D nits in this document. Simply running the [idnits tool][8] is not enough; please review the ["Content Guidelines" on authors.ietf.org][15]. (Also note that the current idnits tool generates some incorrect warnings; a rewrite is underway.) There are no I-D nits that are yet to be resolved. 15. Should any informative references be normative or vice-versa? See the [IESG Statement on Normative and Informative References][16]. All listed informative and normative references are appropriate. 16. List any normative references that are not freely available to anyone. Did the community have sufficient access to review any such normative references? All listed normative references are freely available. 17. Are there any normative downward references (see [RFC 3967][9] and [BCP 97][10]) that are not already listed in the [DOWNREF registry][17]? If so, list them. There are no normative downward references. All listed normative references are published RFCs. 18. Are there normative references to documents that are not ready to be submitted to the IESG for publication or are otherwise in an unclear state? If so, what is the plan for their completion? All listed normative references are published RFCs. 19. Will publication of this document change the status of any existing RFCs? If so, does the Datatracker metadata correctly reflect this and are those RFCs listed on the title page, in the abstract, and discussed in the introduction? If not, explain why and point to the part of the document where the relationship of this document to these other RFCs is discussed. The publication of this document will not change the status of any existing RFCs. 20. Describe the document shepherd's review of the IANA considerations section, especially with regard to its consistency with the body of the document. Confirm that all aspects of the document requiring IANA assignments are associated with the appropriate reservations in IANA registries. Confirm that any referenced IANA registries have been clearly identified. Confirm that each newly created IANA registry specifies its initial contents, allocations procedures, and a reasonable name (see [RFC 8126][11]). The allocation requests made to the IANA in this document are appropriate and the referenced IANA registries are clearly identified. There are no new IANA registries proposed in this document. 21. List any new IANA registries that require Designated Expert Review for future allocations. Are the instructions to the Designated Expert clear? Please include suggestions of designated experts, if appropriate. There are no new IANA registries proposed in this document. [1]: https://www.ietf.org/about/groups/iesg/ [2]: https://www.rfc-editor.org/rfc/rfc4858.html [3]: https://www.rfc-editor.org/rfc/rfc7942.html [4]: https://wiki.ietf.org/group/ops/yang-review-tools [5]: https://www.rfc-editor.org/rfc/rfc8342.html [6]: https://wiki.ietf.org/group/iesg/ExpertTopics [7]: https://www.rfc-editor.org/info/bcp79 [8]: https://www.ietf.org/tools/idnits/ [9]: https://www.rfc-editor.org/rfc/rfc3967.html [10]: https://www.rfc-editor.org/info/bcp97 [11]: https://www.rfc-editor.org/rfc/rfc8126.html [12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5 [13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1 [14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2 [15]: https://authors.ietf.org/en/content-guidelines-overview [16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/ [17]: https://datatracker.ietf.org/doc/downref/ |
2024-01-30
|
23 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-23.txt |
2024-01-30
|
23 | Dhruv Dhody | New version accepted (logged-in submitter: Dhruv Dhody) |
2024-01-30
|
23 | Dhruv Dhody | Uploaded new revision |
2024-01-23
|
22 | Darren Dukes | Request for Early review by RTGDIR Completed: Has Nits. Reviewer: Darren Dukes. Sent review to list. |
2024-01-08
|
22 | Daniam Henriques | Request for Early review by RTGDIR is assigned to Darren Dukes |
2024-01-08
|
22 | Daniam Henriques | Assignment of request for Early review by RTGDIR to Ines Robles was withdrawn |
2024-01-02
|
22 | Daniam Henriques | Request for Early review by RTGDIR is assigned to Ines Robles |
2024-01-02
|
22 | Vishnu Beeram | Tag Awaiting Expert Review/Resolution of Issues Raised set. Tag Revised I-D Needed - Issue raised by WGLC cleared. |
2024-01-02
|
22 | Vishnu Beeram | Requested Early review by RTGDIR |
2023-12-22
|
22 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-22.txt |
2023-12-22
|
22 | Dhruv Dhody | New version accepted (logged-in submitter: Dhruv Dhody) |
2023-12-22
|
22 | Dhruv Dhody | Uploaded new revision |
2023-12-06
|
21 | Vishnu Beeram | Tag Revised I-D Needed - Issue raised by WGLC set. |
2023-12-06
|
21 | Vishnu Beeram | IETF WG state changed to WG Consensus: Waiting for Write-Up from Waiting for WG Chair Go-Ahead |
2023-11-03
|
21 | Lou Berger | see https://mailarchive.ietf.org/arch/msg/teas/dQAQLpjPDlo5GZ8QDVBJA7bf0SU/ |
2023-11-03
|
21 | Lou Berger | IETF WG state changed to Waiting for WG Chair Go-Ahead from WG Document |
2023-10-22
|
21 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-21.txt |
2023-10-22
|
21 | Dhruv Dhody | New version accepted (logged-in submitter: Dhruv Dhody) |
2023-10-22
|
21 | Dhruv Dhody | Uploaded new revision |
2023-10-14
|
20 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-20.txt |
2023-10-14
|
20 | Dhruv Dhody | New version accepted (logged-in submitter: Dhruv Dhody) |
2023-10-14
|
20 | Dhruv Dhody | Uploaded new revision |
2023-09-12
|
19 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-19.txt |
2023-09-12
|
19 | Dhruv Dhody | New version accepted (logged-in submitter: Dhruv Dhody) |
2023-09-12
|
19 | Dhruv Dhody | Uploaded new revision |
2023-07-10
|
18 | Vishnu Beeram | Pre WGLC IPR Poll (Part 3): byyun@etri.re.kr https://mailarchive.ietf.org/arch/msg/teas/I313THqvKofzZdIJ20Dy43zDhOk/ Note: All required responses received. |
2023-07-10
|
18 | Vishnu Beeram | Pre WGLC IPR Poll (Part 2): Igor Bryskin https://mailarchive.ietf.org/arch/msg/teas/ARfvvc5jC7u3BsvWDcBNsBqoeFE/ "Belotti, Sergio (Nokia - IT)" https://mailarchive.ietf.org/arch/msg/teas/tFbzO9FM0lJ7yXxCOfCt5TfJNOo/ ta-miyasaka@kddi.com https://mailarchive.ietf.org/arch/msg/teas/mluSNb_ZzKXY0fwHh0Y3lyifFcM/ Missing Response: byyun@etri.re.kr |
2023-07-04
|
18 | Vishnu Beeram | Pre WGLC IPR Poll: https://mailarchive.ietf.org/arch/msg/teas/8Ow7krt9phKP5BcjoGEcy7DU_fQ/ Responses: younglee.tx@gmail.com https://mailarchive.ietf.org/arch/msg/teas/crkPYMZVAGxftKnn0TIQPIIOmV0/ Dhruv Dhody https://mailarchive.ietf.org/arch/msg/teas/-rTWPvBvPgmNS9gkX9J3vNBR98Q/ daniele.ietf@gmail.com https://mailarchive.ietf.org/arch/msg/teas/J9qr59t0X2pUHRF6RXKpMuUMCgU/ Qin Wu https://mailarchive.ietf.org/arch/msg/teas/vPn_bj1Uu-d4TuBhCpgM9Uraw_o/ peter.park@kt.com https://mailarchive.ietf.org/arch/msg/teas/qPO2fi8kjlgxAeGBGKSnRKMxnvE/ "Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)" https://mailarchive.ietf.org/arch/msg/teas/KE0-S0zzK2nGDIm7249mJTTuDmQ/ … Pre WGLC IPR Poll: https://mailarchive.ietf.org/arch/msg/teas/8Ow7krt9phKP5BcjoGEcy7DU_fQ/ Responses: younglee.tx@gmail.com https://mailarchive.ietf.org/arch/msg/teas/crkPYMZVAGxftKnn0TIQPIIOmV0/ Dhruv Dhody https://mailarchive.ietf.org/arch/msg/teas/-rTWPvBvPgmNS9gkX9J3vNBR98Q/ daniele.ietf@gmail.com https://mailarchive.ietf.org/arch/msg/teas/J9qr59t0X2pUHRF6RXKpMuUMCgU/ Qin Wu https://mailarchive.ietf.org/arch/msg/teas/vPn_bj1Uu-d4TuBhCpgM9Uraw_o/ peter.park@kt.com https://mailarchive.ietf.org/arch/msg/teas/qPO2fi8kjlgxAeGBGKSnRKMxnvE/ "Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)" https://mailarchive.ietf.org/arch/msg/teas/KE0-S0zzK2nGDIm7249mJTTuDmQ/ "Zhangxian (Xian)" https://mailarchive.ietf.org/arch/msg/teas/Jz4tbCwyWNYNRpl-0Erqth8ZQrY/ "Ogaki, Kenichi" https://mailarchive.ietf.org/arch/msg/teas/JvA7v75S4fkQfPxxyuWVqb8zezM/ Missing Responses: Igor Bryskin byyun@etri.re.kr "Belotti, Sergio (Nokia - IT)" ta-miyasaka@kddi.com |
2023-04-02
|
18 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-18.txt |
2023-04-02
|
18 | Dhruv Dhody | New version accepted (logged-in submitter: Dhruv Dhody) |
2023-04-02
|
18 | Dhruv Dhody | Uploaded new revision |
2023-03-10
|
17 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-17.txt |
2023-03-10
|
17 | Dhruv Dhody | New version accepted (logged-in submitter: Dhruv Dhody) |
2023-03-10
|
17 | Dhruv Dhody | Uploaded new revision |
2022-11-07
|
16 | Lou Berger | IETF 115 - Ready for WG LC |
2022-11-07
|
16 | Lou Berger | Notification list changed to vbeeram@juniper.net because the document shepherd was set |
2022-11-07
|
16 | Lou Berger | Document shepherd changed to Vishnu Pavan Beeram |
2022-10-24
|
16 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-16.txt |
2022-10-24
|
16 | Dhruv Dhody | New version accepted (logged-in submitter: Dhruv Dhody) |
2022-10-24
|
16 | Dhruv Dhody | Uploaded new revision |
2022-07-11
|
15 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-15.txt |
2022-07-11
|
15 | Dhruv Dhody | New version accepted (logged-in submitter: Dhruv Dhody) |
2022-07-11
|
15 | Dhruv Dhody | Uploaded new revision |
2022-03-07
|
14 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-14.txt |
2022-03-07
|
14 | (System) | New version accepted (logged-in submitter: Dhruv Dhody) |
2022-03-07
|
14 | Dhruv Dhody | Uploaded new revision |
2021-11-09
|
13 | Vishnu Beeram | Removed from session: IETF-112: teas Tue-1600 |
2021-11-09
|
13 | Vishnu Beeram | Added to session: IETF-112: teas Tue-1430 |
2021-11-09
|
13 | Vishnu Beeram | Added to session: IETF-112: teas Tue-1600 |
2021-10-23
|
13 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-13.txt |
2021-10-23
|
13 | (System) | New version accepted (logged-in submitter: Dhruv Dhody) |
2021-10-23
|
13 | Dhruv Dhody | Uploaded new revision |
2021-08-25
|
12 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-12.txt |
2021-08-25
|
12 | (System) | New version accepted (logged-in submitter: Dhruv Dhody) |
2021-08-25
|
12 | Dhruv Dhody | Uploaded new revision |
2021-08-23
|
11 | (System) | Document has expired |
2021-03-07
|
11 | Lou Berger | Added to session: IETF-110: teas Tue-1700 |
2021-02-19
|
11 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-11.txt |
2021-02-19
|
11 | (System) | New version approved |
2021-02-19
|
11 | (System) | Request for posting confirmation emailed to previous authors: Bin-Yeong Yoon , Daniele Ceccarelli , Dhruv Dhody , Igor Bryskin , Young Lee |
2021-02-19
|
11 | Dhruv Dhody | Uploaded new revision |
2020-12-20
|
10 | Andy Bierman | Request for Early review by YANGDOCTORS Completed: Ready with Issues. Reviewer: Andy Bierman. Sent review to list. |
2020-11-13
|
10 | Mehmet Ersue | Request for Early review by YANGDOCTORS is assigned to Andy Bierman |
2020-11-13
|
10 | Mehmet Ersue | Request for Early review by YANGDOCTORS is assigned to Andy Bierman |
2020-11-13
|
10 | Vishnu Beeram | Requested Early review by YANGDOCTORS |
2020-11-13
|
10 | Lou Berger | Added to session: IETF-109: teas Mon-1600 |
2020-11-02
|
10 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-10.txt |
2020-11-02
|
10 | (System) | New version accepted (logged-in submitter: Dhruv Dhody) |
2020-11-02
|
10 | Dhruv Dhody | Uploaded new revision |
2020-07-13
|
09 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-09.txt |
2020-07-13
|
09 | (System) | New version approved |
2020-07-13
|
09 | (System) | Request for posting confirmation emailed to previous authors: Bin-Yeong Yoon , Igor Bryskin , Dhruv Dhody , Daniele Ceccarelli , Young Lee |
2020-07-13
|
09 | Dhruv Dhody | Uploaded new revision |
2020-07-02
|
Jasmine Magallanes | Posted related IPR disclosure Huawei Technologies Co.,Ltd's Statement about IPR related to draft-ietf-teas-actn-vn-yang | |
2020-07-02
|
Jasmine Magallanes | Posted related IPR disclosure Huawei Technologies Co.,Ltd's Statement about IPR related to draft-ietf-teas-actn-vn-yang | |
2020-03-08
|
08 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-08.txt |
2020-03-08
|
08 | (System) | New version approved |
2020-03-08
|
08 | (System) | Request for posting confirmation emailed to previous authors: Dhruv Dhody , Young Lee , Daniele Ceccarelli , Bin-Yeong Yoon , Igor Bryskin |
2020-03-08
|
08 | Dhruv Dhody | Uploaded new revision |
2019-10-31
|
07 | Dhruv Dhody | New version available: draft-ietf-teas-actn-vn-yang-07.txt |
2019-10-31
|
07 | (System) | New version accepted (logged-in submitter: Dhruv Dhody) |
2019-10-31
|
07 | Dhruv Dhody | Uploaded new revision |
2019-07-05
|
06 | Young Lee | New version available: draft-ietf-teas-actn-vn-yang-06.txt |
2019-07-05
|
06 | (System) | New version approved |
2019-07-05
|
06 | (System) | Request for posting confirmation emailed to previous authors: Young Lee , Igor Bryskin , Dhruv Dhody , Bin-Yeong Yoon , Daniele Ceccarelli |
2019-07-05
|
06 | Young Lee | Uploaded new revision |
2019-06-14
|
05 | Young Lee | New version available: draft-ietf-teas-actn-vn-yang-05.txt |
2019-06-14
|
05 | (System) | New version approved |
2019-06-14
|
05 | (System) | Request for posting confirmation emailed to previous authors: Daniele Ceccarelli , Bin-Yeong Yoon , Peter Park , Dhruv Dhody , teas-chairs@ietf.org, Igor Bryskin , … Request for posting confirmation emailed to previous authors: Daniele Ceccarelli , Bin-Yeong Yoon , Peter Park , Dhruv Dhody , teas-chairs@ietf.org, Igor Bryskin , Young Lee , Qin Wu |
2019-06-14
|
05 | Young Lee | Uploaded new revision |
2019-02-04
|
04 | Young Lee | New version available: draft-ietf-teas-actn-vn-yang-04.txt |
2019-02-04
|
04 | (System) | New version approved |
2019-02-04
|
04 | (System) | Request for posting confirmation emailed to previous authors: Daniele Ceccarelli , Bin-Yeong Yoon , Peter Park , Dhruv Dhody , Igor Bryskin , Young Lee … Request for posting confirmation emailed to previous authors: Daniele Ceccarelli , Bin-Yeong Yoon , Peter Park , Dhruv Dhody , Igor Bryskin , Young Lee , Qin Wu |
2019-02-04
|
04 | Young Lee | Uploaded new revision |
2018-12-30
|
03 | Young Lee | New version available: draft-ietf-teas-actn-vn-yang-03.txt |
2018-12-30
|
03 | (System) | New version approved |
2018-12-30
|
03 | (System) | Request for posting confirmation emailed to previous authors: Daniele Ceccarelli , Bin-Yeong Yoon , Peter Park , Dhruv Dhody , Igor Bryskin , Young Lee … Request for posting confirmation emailed to previous authors: Daniele Ceccarelli , Bin-Yeong Yoon , Peter Park , Dhruv Dhody , Igor Bryskin , Young Lee , Qin Wu |
2018-12-30
|
03 | Young Lee | Uploaded new revision |
2018-09-20
|
02 | Young Lee | New version available: draft-ietf-teas-actn-vn-yang-02.txt |
2018-09-20
|
02 | (System) | New version approved |
2018-09-20
|
02 | (System) | Request for posting confirmation emailed to previous authors: Daniele Ceccarelli , Bin-Yeong Yoon , Peter Park , Dhruv Dhody , Igor Bryskin , Young Lee … Request for posting confirmation emailed to previous authors: Daniele Ceccarelli , Bin-Yeong Yoon , Peter Park , Dhruv Dhody , Igor Bryskin , Young Lee , Qin Wu |
2018-09-20
|
02 | Young Lee | Uploaded new revision |
2018-07-24
|
01 | Vishnu Beeram | This document now replaces draft-lee-teas-actn-vn-yang instead of None |
2018-06-21
|
01 | Young Lee | New version available: draft-ietf-teas-actn-vn-yang-01.txt |
2018-06-21
|
01 | (System) | New version approved |
2018-06-21
|
01 | (System) | Request for posting confirmation emailed to previous authors: Daniele Ceccarelli , Bin-Yeong Yoon , Dhruv Dhody , teas-chairs@ietf.org, Igor Bryskin , Young Lee |
2018-06-21
|
01 | Young Lee | Uploaded new revision |
2018-05-31
|
00 | Young Lee | New version available: draft-ietf-teas-actn-vn-yang-00.txt |
2018-05-31
|
00 | (System) | WG -00 approved |
2018-05-29
|
00 | Young Lee | Set submitter to "Young Lee ", replaces to (none) and sent approval email to group chairs: teas-chairs@ietf.org |
2018-05-29
|
00 | Young Lee | Uploaded new revision |