A YANG Model for Network and VPN Service Performance Monitoring
draft-ietf-opsawg-yang-vpn-service-pm-08
Revision differences
Document history
| Date | Rev. | By | Action |
|---|---|---|---|
|
2022-05-11
|
08 | Adrian Farrel | Document shepherd write-up for draft-ietf-opsawg-yang-vpn-service-pm > ## Document History > > 1. Does the working group (WG) consensus represent the strong concurrence of a > … Document shepherd write-up for draft-ietf-opsawg-yang-vpn-service-pm > ## 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? The document has 5 co-authors, 4 contributors, and 7 reviewers acknowledged in the document. WG last call (which can be found in the archive at https://mailarchive.ietf.org/arch/msg/opsawg/0UjzdhIAmLr_x0V6cqhgBUmGPic/) attracted three detailed reviews and some additional comments (https://mailarchive.ietf.org/arch/msg/opsawg/giJgyVBYg-7cDYNKNQR1HQUp1VM/) The work was also presented at several OPSAWG meetings. There was no objection to publication, so this represents relatively broad consensus for publication. > 2. Was there controversy about particular points, or were there decisions where > the consensus was particularly rough? None observed. > 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. There has been debate about various points, but these seem to have been resolved through discussion and modification of the document. > 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)? No implementations have been publicly reported. However, the document shepherd is aware of plans to include this function in two separate implementations. > ### Additional Reviews > > 5. Does this document need review from other IETF working groups or external > organizations? Have those reviews occurred? None needed. It might have been useful to share this with IPPM and BESS. The shepherd notified those two working groups to watch out for IETF last call, and this resulted in an immediate additional review that has been addressed in a new revision of the document. A review by the Routing Directorate has been requested twice, but no review has been received. The ADs might reinvent the pm-dir to get some extra views on this document. > 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 received YANG Doctor review from Radek Krejci at the time of WG last call. It found nits that have been fixed. https://datatracker.ietf.org/doc/review-ietf-opsawg-yang-vpn-service-pm-07-yangdoctors-lc-krejci-2022-04-27/ An additional review of -05 (updated after WG last call) was performed by Ladislav Lhotka. It found nits that have been fixed. https://datatracker.ietf.org/doc/review-ietf-opsawg-yang-vpn-service-pm-05-yangdoctors-early-lhotka-2022-04-08/ > 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? The Datatracker reports YANG validation passes with no errors and no warnings. > Does the YANG module comply with the Network Management Datastore > Architecture (NMDA) as specified in [RFC 8342][5]? The document makes no claims about conformance to NMDA, however to the best of my knowledge, the model complies with the NMDA. > 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. As above: - YANG Doctor reviews - Datatracker automated checks > ### Document Shepherd Checks The document shepherd reviewed this document at adoption, during its progress through the working group (-01), during WG last call (-03), and in their role as document shepherd (-05). In each case, the authors made updates and addressed all of the comments. > 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 > 10. Several IETF Areas have assembled [lists of common issues that their > reviewers encounter][6]. Do any such issues remain that would merit specific > attention from subsequent reviews? It would be easier to answer this question if a pointer was provided to those lists. No reviews or reviewers have pointed to any open issues that need attention. The shepherd has some experience with getting documents up to the right level, and considers this one good enough. > 11. What type of RFC publication is being requested on the IETF stream (Best > Current Practice, Proposed Standard, Internet Standard, Informational, > Experimental, or Historic)? Why is this the proper type of RFC? Do all > Datatracker state attributes correctly reflect this intent? This document is the product of the OPSAWG and is presented for publication on the Standards Track as a Draft Standard. This is appropriate for a YANG model that will be implemented and must interoperate. The status is properly indicated on the title page and in the Datatracker. > 12. Has the interested community confirmed that any and all appropriate IPR > disclosures required by [BCP 78][7] and [BCP 79][8] have been filed? If not, > explain why. If yes, summarize any discussion and conclusion regarding the > intellectual property rights (IPR) disclosures, including links to relevant > emails. The WG chairs requested an IPR response from all authors in a private email at the time of WG last call. Responses from three of the authors can be seen on the OPSAWG mailing list at https://mailarchive.ietf.org/arch/msg/opsawg/a4E8SNuIzZtMrWtsJwCvCEiCO50/ Other responses are at https://mailarchive.ietf.org/arch/msg/opsawg/vKW7Hpr2sSZNB3kLYWDR-aPKKoo/ No IPR has been disclosed, and all respondents declared no IP needed to be disclosed. > 13. Has each Author or Contributor confirmed their willingness to be listed as > such? Well, no. But they have been listed there for a long time, and their silence may be assumed to be consent. Note also that the IPR poll has made all authors and contributors aware of their status on the document. > If the number of Authors/Editors on the front page is greater than 5, > please provide a justification. It isn't. > 14. Identify any remaining I-D nits in this document. (See [the idnits tool][9] > and the checkbox items found in Guidelines to Authors of Internet-Drafts). > Simply running the idnits tool is not enough; please review the entire > guidelines document. id-nits is clean. Manual check of guidance for YANG-based documents reveals no issues. > 15. Should any informative references be normative or vice-versa? The distribution seems to be right. Some fixes were made as a result of various reviews. > 16. List any normative references that are not freely available to anyone. None > 17. Are there any normative downward references (see [RFC 3967][10], > [BCP 97][11])? If so, list them. No normative downrefs > 18. Are there normative references to documents that are not ready for > advancement or are otherwise in an unclear state? None > 19. Will publication of this document change the status of any existing RFCs? No > 20. Describe the document shepherd's review of the IANA considerations section, > especially with regard to its consistency with the body of the document. The document shepherd made themself a cup of tea with a slice of lemon and sat down in their office. They then read the document including the IANA considerations section, and thought about it carefully, comparing it with recently published RFCs and the needs of the rest of the document. > Confirm that all aspects of the document requiring IANA assignments are > associated with the appropriate reservations in IANA registries. Confirmed > Confirm that any referenced IANA registries have been clearly identified. Confirmed > Confirm that each newly created IANA registry specifies its initial contents, > allocations procedures, and a reasonable name (see [RFC 8126][12]). Confirmed > 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. No new registries |
|
2022-05-11
|
08 | Joe Clarke | Changed consensus to Yes from Unknown |
|
2022-05-11
|
08 | Joe Clarke | Intended Status changed to Proposed Standard from None |
|
2022-05-11
|
08 | Luc André Burdet | Request for Early review by RTGDIR is assigned to Dhruv Dhody |
|
2022-05-11
|
08 | Luc André Burdet | Request for Early review by RTGDIR is assigned to Dhruv Dhody |
|
2022-05-11
|
08 | Luc André Burdet | Assignment of request for Early review by RTGDIR to Himanshu Shah was rejected |
|
2022-05-11
|
08 | Adrian Farrel | Chairs to set the Intended Status in the Datatracker |
|
2022-05-06
|
08 | Adrian Farrel | Awaiting IPR confirmations from: 'ron.even.tlv@gmail.com' <ron.even.tlv@gmail.com>; Chairs to set the Intended Status in the Datatracker |
|
2022-05-05
|
08 | Adrian Farrel | Awaiting IPR confirmations from: 'ron.even.tlv@gmail.com' <ron.even.tlv@gmail.com>; 'liuc131@chinaunicom.cn' <liuc131@chinaunicom.cn>; 'xuhl6@chinatelecom.cn' <xuhl.bri@chinatelecom.cn>; 'oscar.gonzalezdedios@telefonica.com' <oscar.gonzalezdedios@telefonica.com>; Chairs … Awaiting IPR confirmations from: 'ron.even.tlv@gmail.com' <ron.even.tlv@gmail.com>; 'liuc131@chinaunicom.cn' <liuc131@chinaunicom.cn>; 'xuhl6@chinatelecom.cn' <xuhl.bri@chinatelecom.cn>; 'oscar.gonzalezdedios@telefonica.com' <oscar.gonzalezdedios@telefonica.com>; Chairs to set the Intended Status in the Datatracker |
|
2022-05-05
|
08 | Bo Wu | New version available: draft-ietf-opsawg-yang-vpn-service-pm-08.txt |
|
2022-05-05
|
08 | Bo Wu | New version accepted (logged-in submitter: Bo Wu) |
|
2022-05-05
|
08 | Bo Wu | Uploaded new revision |
|
2022-05-05
|
07 | Adrian Farrel | Awaiting IPR confirmations from: 'ron.even.tlv@gmail.com' <ron.even.tlv@gmail.com>; 'liuc131@chinaunicom.cn' <liuc131@chinaunicom.cn>; 'xuhl.bri@chinatelecom.cn' <xuhl.bri@chinatelecom.cn>; <<<<<<<<<<< Bouncing <<<<<<<<<<<<<<<<<<<<<<< 'oscar.gonzalezdedios@telefonica.com' < … Awaiting IPR confirmations from: 'ron.even.tlv@gmail.com' <ron.even.tlv@gmail.com>; 'liuc131@chinaunicom.cn' <liuc131@chinaunicom.cn>; 'xuhl.bri@chinatelecom.cn' <xuhl.bri@chinatelecom.cn>; <<<<<<<<<<< Bouncing <<<<<<<<<<<<<<<<<<<<<<< 'oscar.gonzalezdedios@telefonica.com' <oscar.gonzalezdedios@telefonica.com>; 'bin_wen@comcast.com' <bin_wen@comcast.com> Awaiting update to draft for incorrect Security Considerations text. Chairs to set the Intended Status in the Datatracker |
|
2022-04-29
|
07 | Adrian Farrel | Awaiting IPR confirmations from: 'wangzitao@huawei.com' <wangzitao@huawei.com>; 'ron.even.tlv@gmail.com' <ron.even.tlv@gmail.com>; 'liuc131@chinaunicom.cn' <liuc131@chinaunicom.cn>; 'xuhl.bri@chinatelecom.cn' <xuhl.bri@chinatelecom.cn>; <<<<<<<<<<< … Awaiting IPR confirmations from: 'wangzitao@huawei.com' <wangzitao@huawei.com>; 'ron.even.tlv@gmail.com' <ron.even.tlv@gmail.com>; 'liuc131@chinaunicom.cn' <liuc131@chinaunicom.cn>; 'xuhl.bri@chinatelecom.cn' <xuhl.bri@chinatelecom.cn>; <<<<<<<<<<< Bouncing <<<<<<<<<<<<<<<<<<<<<<< 'oscar.gonzalezdedios@telefonica.com' <oscar.gonzalezdedios@telefonica.com>; 'bin_wen@comcast.com' <bin_wen@comcast.com> Awaiting update to draft for incorrect Security Considerations text. Chairs to set the Intended Status in the Datatracker |
|
2022-04-29
|
07 | Adrian Farrel | Awaiting IPR confirmations from: 'wangzitao@huawei.com' <wangzitao@huawei.com>; 'ron.even.tlv@gmail.com' <ron.even.tlv@gmail.com>; 'liuc131@chinaunicom.cn' <liuc131@chinaunicom.cn>; 'xuhl.bri@chinatelecom.cn' <xuhl.bri@chinatelecom.cn>; <<<<<<<<<<< … Awaiting IPR confirmations from: 'wangzitao@huawei.com' <wangzitao@huawei.com>; 'ron.even.tlv@gmail.com' <ron.even.tlv@gmail.com>; 'liuc131@chinaunicom.cn' <liuc131@chinaunicom.cn>; 'xuhl.bri@chinatelecom.cn' <xuhl.bri@chinatelecom.cn>; <<<<<<<<<<< Bouncing <<<<<<<<<<<<<<<<<<<<<<< 'oscar.gonzalezdedios@telefonica.com' <oscar.gonzalezdedios@telefonica.com>; 'bin_wen@comcast.com' <bin_wen@comcast.com> Awaiting update to draft for incorrect Security Considerations text. |
|
2022-04-27
|
07 | Radek Krejčí | Request for Last Call review by YANGDOCTORS Completed: Ready with Nits. Reviewer: Radek Krejčí. Sent review to list. |
|
2022-04-26
|
07 | Luc André Burdet | Request for Early review by RTGDIR is assigned to Himanshu Shah |
|
2022-04-26
|
07 | Luc André Burdet | Request for Early review by RTGDIR is assigned to Himanshu Shah |
|
2022-04-26
|
07 | Luc André Burdet | Assignment of request for Early review by RTGDIR to Emmanuel Baccelli was marked no-response |
|
2022-04-25
|
07 | Bo Wu | New version available: draft-ietf-opsawg-yang-vpn-service-pm-07.txt |
|
2022-04-25
|
07 | Bo Wu | New version accepted (logged-in submitter: Bo Wu) |
|
2022-04-25
|
07 | Bo Wu | Uploaded new revision |
|
2022-04-14
|
06 | Joe Clarke | Tag Revised I-D Needed - Issue raised by WG cleared. |
|
2022-04-14
|
06 | Joe Clarke | Notification list changed to adrian@olddog.co.uk because the document shepherd was set |
|
2022-04-14
|
06 | Joe Clarke | Document shepherd changed to Adrian Farrel |
|
2022-04-14
|
06 | Bo Wu | New version available: draft-ietf-opsawg-yang-vpn-service-pm-06.txt |
|
2022-04-14
|
06 | (System) | New version accepted (logged-in submitter: Bo Wu) |
|
2022-04-14
|
06 | Bo Wu | Uploaded new revision |
|
2022-04-12
|
05 | Luc André Burdet | Request for Early review by RTGDIR is assigned to Emmanuel Baccelli |
|
2022-04-12
|
05 | Luc André Burdet | Request for Early review by RTGDIR is assigned to Emmanuel Baccelli |
|
2022-04-12
|
05 | Luc André Burdet | Assignment of request for Early review by RTGDIR to Stig Venaas was withdrawn |
|
2022-04-11
|
05 | Luc André Burdet | Request for Last Call review by RTGDIR is assigned to Lou Berger |
|
2022-04-11
|
05 | Luc André Burdet | Request for Last Call review by RTGDIR is assigned to Lou Berger |
|
2022-04-08
|
05 | Ladislav Lhotka | Request for Early review by YANGDOCTORS Completed: Ready with Nits. Reviewer: Ladislav Lhotka. Sent review to list. |
|
2022-04-08
|
05 | Bo Wu | New version available: draft-ietf-opsawg-yang-vpn-service-pm-05.txt |
|
2022-04-08
|
05 | (System) | New version accepted (logged-in submitter: Bo Wu) |
|
2022-04-08
|
05 | Bo Wu | Uploaded new revision |
|
2022-04-07
|
04 | Mehmet Ersue | Request for Last Call review by YANGDOCTORS is assigned to Radek Krejčí |
|
2022-04-07
|
04 | Mehmet Ersue | Request for Last Call review by YANGDOCTORS is assigned to Radek Krejčí |
|
2022-04-07
|
04 | Mehmet Ersue | Assignment of request for Last Call review by YANGDOCTORS to Acee Lindem was rejected |
|
2022-04-07
|
04 | Mehmet Ersue | Request for Last Call review by YANGDOCTORS is assigned to Acee Lindem |
|
2022-04-07
|
04 | Mehmet Ersue | Request for Last Call review by YANGDOCTORS is assigned to Acee Lindem |
|
2022-04-06
|
04 | Joe Clarke | IETF WG state changed to WG Consensus: Waiting for Write-Up from In WG Last Call |
|
2022-04-06
|
04 | Joe Clarke | Requested Last Call review by RTGDIR |
|
2022-04-06
|
04 | Joe Clarke | Requested Last Call review by YANGDOCTORS |
|
2022-03-31
|
04 | Gunter Van de Velde | Closed request for Early review by OPSDIR with state 'Overtaken by Events' |
|
2022-03-21
|
04 | Bo Wu | New version available: draft-ietf-opsawg-yang-vpn-service-pm-04.txt |
|
2022-03-21
|
04 | (System) | New version approved |
|
2022-03-21
|
04 | (System) | Request for posting confirmation emailed to previous authors: Bin Wen <bin_wen@comcast.com>, Bo Wu <lana.wubo@huawei.com>, Mohamed Boucadair <mohamed.boucadair@orange.com>, Oscar de … Request for posting confirmation emailed to previous authors: Bin Wen <bin_wen@comcast.com>, Bo Wu <lana.wubo@huawei.com>, Mohamed Boucadair <mohamed.boucadair@orange.com>, Oscar de Dios <oscar.gonzalezdedios@telefonica.com>, Qin WU <bill.wu@huawei.com> |
|
2022-03-21
|
04 | Bo Wu | Uploaded new revision |
|
2022-03-09
|
03 | Gunter Van de Velde | Request for Early review by OPSDIR is assigned to Zitao Wang |
|
2022-03-09
|
03 | Gunter Van de Velde | Request for Early review by OPSDIR is assigned to Zitao Wang |
|
2022-03-03
|
03 | Luc André Burdet | Request for Early review by RTGDIR is assigned to Stig Venaas |
|
2022-03-03
|
03 | Luc André Burdet | Request for Early review by RTGDIR is assigned to Stig Venaas |
|
2022-03-01
|
03 | Mehmet Ersue | Request for Early review by YANGDOCTORS is assigned to Ladislav Lhotka |
|
2022-03-01
|
03 | Mehmet Ersue | Request for Early review by YANGDOCTORS is assigned to Ladislav Lhotka |
|
2022-02-28
|
03 | Joe Clarke | Tag Revised I-D Needed - Issue raised by WG set. |
|
2022-02-28
|
03 | Joe Clarke | IETF WG state changed to In WG Last Call from WG Document |
|
2022-02-28
|
03 | Joe Clarke | Requested Early review by YANGDOCTORS |
|
2022-02-28
|
03 | Joe Clarke | Requested Early review by RTGDIR |
|
2022-02-28
|
03 | Joe Clarke | Requested Early review by OPSDIR |
|
2022-01-29
|
03 | Bo Wu | New version available: draft-ietf-opsawg-yang-vpn-service-pm-03.txt |
|
2022-01-29
|
03 | (System) | New version approved |
|
2022-01-29
|
03 | (System) | Request for posting confirmation emailed to previous authors: Bin Wen <bin_wen@comcast.com>, Bo Wu <lana.wubo@huawei.com>, Mohamed Boucadair <mohamed.boucadair@orange.com>, Oscar de … Request for posting confirmation emailed to previous authors: Bin Wen <bin_wen@comcast.com>, Bo Wu <lana.wubo@huawei.com>, Mohamed Boucadair <mohamed.boucadair@orange.com>, Oscar de Dios <oscar.gonzalezdedios@telefonica.com>, Qin WU <bill.wu@huawei.com> |
|
2022-01-29
|
03 | Bo Wu | Uploaded new revision |
|
2022-01-19
|
02 | Bo Wu | New version available: draft-ietf-opsawg-yang-vpn-service-pm-02.txt |
|
2022-01-19
|
02 | (System) | New version approved |
|
2022-01-19
|
02 | (System) | Request for posting confirmation emailed to previous authors: Bin Wen <bin_wen@comcast.com>, Bo Wu <lana.wubo@huawei.com>, Chang Liu <liuc131@chinaunicom.cn>, Honglei Xu … Request for posting confirmation emailed to previous authors: Bin Wen <bin_wen@comcast.com>, Bo Wu <lana.wubo@huawei.com>, Chang Liu <liuc131@chinaunicom.cn>, Honglei Xu <xuhl.bri@chinatelecom.cn>, Mohamed Boucadair <mohamed.boucadair@orange.com>, Oscar de Dios <oscar.gonzalezdedios@telefonica.com>, Qin WU <bill.wu@huawei.com>, opsawg-chairs@ietf.org |
|
2022-01-19
|
02 | Bo Wu | Uploaded new revision |
|
2022-01-07
|
01 | (System) | Document has expired |
|
2021-08-04
|
01 | Joe Clarke | Added to session: IETF-111: opsawg Fri-1600 |
|
2021-07-06
|
01 | Bo Wu | New version available: draft-ietf-opsawg-yang-vpn-service-pm-01.txt |
|
2021-07-06
|
01 | (System) | New version approved |
|
2021-07-06
|
01 | (System) | Request for posting confirmation emailed to previous authors: Bin Wen <bin_wen@comcast.com>, Bo Wu <lana.wubo@huawei.com>, Chang Liu <liuc131@chinaunicom.cn>, Honglei Xu … Request for posting confirmation emailed to previous authors: Bin Wen <bin_wen@comcast.com>, Bo Wu <lana.wubo@huawei.com>, Chang Liu <liuc131@chinaunicom.cn>, Honglei Xu <xuhl.bri@chinatelecom.cn>, Mohamed Boucadair <mohamed.boucadair@orange.com>, Oscar de Dios <oscar.gonzalezdedios@telefonica.com>, Qin WU <bill.wu@huawei.com> |
|
2021-07-06
|
01 | Bo Wu | Uploaded new revision |
|
2021-02-18
|
00 | Joe Clarke | This document now replaces draft-www-opsawg-yang-vpn-service-pm instead of None |
|
2021-02-18
|
00 | Bo Wu | New version available: draft-ietf-opsawg-yang-vpn-service-pm-00.txt |
|
2021-02-18
|
00 | (System) | WG -00 approved |
|
2021-02-17
|
00 | Bo Wu | Set submitter to "Bo Wu <lana.wubo@huawei.com>", replaces to draft-www-opsawg-yang-vpn-service-pm and sent approval email to group chairs: opsawg-chairs@ietf.org |
|
2021-02-17
|
00 | Bo Wu | Uploaded new revision |