BIER Penultimate Hop Popping
draft-ietf-bier-php-11
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2024-02-06
|
11 | Zhaohui Zhang | New version available: draft-ietf-bier-php-11.txt |
2024-02-06
|
11 | Zhaohui Zhang | New version accepted (logged-in submitter: Zhaohui Zhang) |
2024-02-06
|
11 | Zhaohui Zhang | Uploaded new revision |
2023-09-10
|
10 | (System) | Document has expired |
2023-03-09
|
10 | Xiao Min | # 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? There is a broad agreement to adopt and progress this work in the working group. 2. Was there controversy about particular points, or were there decisions where the consensus was particularly rough? None. 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.) None. 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)? There is no report for existing or planned implementation yet, due to slow deployment of base BIER functionality itself. The situation is changing as more vendor implementations for BIER are coming. As this extension will further promote the BIER deployment, it is expected that vendors will start planning to support it. ## 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. BIER PHP described in this document follows similar principles and examples of MPLS PHP, several MPLS experts have carefully reviewed this document and suggested some improvements. 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. No formal review is required other than the review required to perform the IANA actions (i.e., new IGP/BGP sub-TLV/sub-sub-TLV assignments). 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]? N/A. 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. N/A. ## 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, the document is ready. I've performed my shepherd's review, and made several technical/editorial comments, which have been addressed by the author. 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? No issues identified. 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? This document requests publication as a Proposed Standard RFC. That is indicated on the header page. The intended status is justified given that the document specifies new IGP/BGP sub-TLV/sub-sub-TLV with a set of normative behavior to ensure interoperability. 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. IPR has been disclosed for its predecessor draft-zzhang-bier-php. https://datatracker.ietf.org/ipr/3234/ There is only one author, whose organization disclosed the IPR. 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. I think so. There is only one author. 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.) None to report for -10. 15. Should any informative references be normative or vice-versa? See the [IESG Statement on Normative and Informative References][16]. No. 16. List any normative references that are not freely available to anyone. Did the community have sufficient access to review any such normative references? None. 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. No. 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? No. 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. 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. 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]). No issues on IANA considerations section identified. 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. None. [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://trac.ietf.org/trac/ops/wiki/yang-review-tools [5]: https://www.rfc-editor.org/rfc/rfc8342.html [6]: https://trac.ietf.org/trac/iesg/wiki/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/ |
2023-03-09
|
10 | Jenny Bui | This document now replaces draft-zzhang-bier-php instead of None |
2023-03-09
|
10 | Zhaohui Zhang | New version available: draft-ietf-bier-php-10.txt |
2023-03-09
|
10 | Zhaohui Zhang | New version accepted (logged-in submitter: Zhaohui Zhang) |
2023-03-09
|
10 | Zhaohui Zhang | Uploaded new revision |
2023-03-06
|
09 | Tony Przygienda | IETF WG state changed to WG Consensus: Waiting for Write-Up from In WG Last Call |
2023-03-06
|
09 | Tony Przygienda | Tag Doc Shepherd Follow-up Underway set. |
2023-02-15
|
09 | Zhaohui Zhang | New version available: draft-ietf-bier-php-09.txt |
2023-02-15
|
09 | Zhaohui Zhang | New version accepted (logged-in submitter: Zhaohui Zhang) |
2023-02-15
|
09 | Zhaohui Zhang | Uploaded new revision |
2023-01-05
|
08 | Zhaohui Zhang | New version available: draft-ietf-bier-php-08.txt |
2023-01-05
|
08 | Zhaohui Zhang | New version accepted (logged-in submitter: Zhaohui Zhang) |
2023-01-05
|
08 | Zhaohui Zhang | Uploaded new revision |
2022-11-24
|
07 | Tony Przygienda | Notification list changed to xiao.min2@zte.com.cn because the document shepherd was set |
2022-11-24
|
07 | Tony Przygienda | Document shepherd changed to Xiao Min |
2022-06-10
|
07 | (System) | Document has expired |
2021-12-07
|
07 | Zhaohui Zhang | New version available: draft-ietf-bier-php-07.txt |
2021-12-07
|
07 | (System) | New version accepted (logged-in submitter: Zhaohui Zhang) |
2021-12-07
|
07 | Zhaohui Zhang | Uploaded new revision |
2021-03-08
|
06 | (System) | Document has expired |
2020-08-24
|
06 | Zhaohui Zhang | New version available: draft-ietf-bier-php-06.txt |
2020-08-24
|
06 | (System) | New version accepted (logged-in submitter: Zhaohui Zhang) |
2020-08-24
|
06 | Zhaohui Zhang | Uploaded new revision |
2020-07-29
|
05 | Zhaohui Zhang | New version available: draft-ietf-bier-php-05.txt |
2020-07-29
|
05 | (System) | New version accepted (logged-in submitter: Zhaohui Zhang) |
2020-07-29
|
05 | Zhaohui Zhang | Uploaded new revision |
2020-05-03
|
04 | (System) | Document has expired |
2019-10-31
|
04 | Zhaohui Zhang | New version available: draft-ietf-bier-php-04.txt |
2019-10-31
|
04 | (System) | New version approved |
2019-10-31
|
04 | (System) | Request for posting confirmation emailed to previous authors: Zhaohui Zhang |
2019-10-31
|
04 | Zhaohui Zhang | Uploaded new revision |
2019-10-03
|
03 | Zhaohui Zhang | New version available: draft-ietf-bier-php-03.txt |
2019-10-03
|
03 | (System) | New version approved |
2019-10-03
|
03 | (System) | Request for posting confirmation emailed to previous authors: Zhaohui Zhang |
2019-10-03
|
03 | Zhaohui Zhang | Uploaded new revision |
2019-07-30
|
02 | Greg Shepherd | IETF WG state changed to In WG Last Call from WG Document |
2019-05-29
|
02 | Zhaohui Zhang | New version available: draft-ietf-bier-php-02.txt |
2019-05-29
|
02 | (System) | New version approved |
2019-05-29
|
02 | (System) | Request for posting confirmation emailed to previous authors: Zhaohui Zhang |
2019-05-29
|
02 | Zhaohui Zhang | Uploaded new revision |
2018-11-28
|
01 | Zhaohui Zhang | New version available: draft-ietf-bier-php-01.txt |
2018-11-28
|
01 | (System) | New version approved |
2018-11-28
|
01 | (System) | Request for posting confirmation emailed to previous authors: Zhaohui Zhang |
2018-11-28
|
01 | Zhaohui Zhang | Uploaded new revision |
2018-11-17
|
00 | Zhaohui Zhang | New version available: draft-ietf-bier-php-00.txt |
2018-11-17
|
00 | (System) | WG -00 approved |
2018-11-16
|
00 | Zhaohui Zhang | Set submitter to "Zhaohui Zhang ", replaces to (none) and sent approval email to group chairs: bier-chairs@ietf.org |
2018-11-16
|
00 | Zhaohui Zhang | Uploaded new revision |