MVPN/EVPN Tunnel Aggregation with Common Labels
draft-ietf-bess-mvpn-evpn-aggregation-label-08
Revision differences
Document history
| Date | Rev. | By | Action |
|---|---|---|---|
|
2022-03-23
|
08 | Amy Vezza | Changed action holders to Andrew Alston |
|
2022-03-23
|
08 | Amy Vezza | Shepherding AD changed to Andrew Alston |
|
2022-03-01
|
08 | Martin Vigoureux | IESG state changed to Publication Requested from AD Evaluation::AD Followup |
|
2022-01-20
|
08 | Zhaohui Zhang | New version available: draft-ietf-bess-mvpn-evpn-aggregation-label-08.txt |
|
2022-01-20
|
08 | (System) | New version accepted (logged-in submitter: Zhaohui Zhang) |
|
2022-01-20
|
08 | Zhaohui Zhang | Uploaded new revision |
|
2021-12-16
|
07 | (System) | Changed action holders to Martin Vigoureux (IESG state changed) |
|
2021-12-16
|
07 | (System) | Sub state has been changed to AD Followup from Revised ID Needed |
|
2021-12-16
|
07 | Zhaohui Zhang | New version available: draft-ietf-bess-mvpn-evpn-aggregation-label-07.txt |
|
2021-12-16
|
07 | (System) | New version accepted (logged-in submitter: Zhaohui Zhang) |
|
2021-12-16
|
07 | Zhaohui Zhang | Uploaded new revision |
|
2021-11-03
|
06 | (System) | Changed action holders to IJsbrand Wijnands, Martin Vigoureux, Zhaohui Zhang, Zhenbin Li, Wen Lin, Eric Rosen (IESG state changed) |
|
2021-11-03
|
06 | Martin Vigoureux | IESG state changed to AD Evaluation::Revised I-D Needed from Publication Requested |
|
2021-04-19
|
06 | Stephane Litkowski | As required by RFC 4858, this is the current template for the Document Shepherd Write-Up. Changes are expected over time. This version is dated … As required by RFC 4858, this is the current template for the Document Shepherd Write-Up. Changes are expected over time. This version is dated 1 November 2019. (1) What type of RFC is being requested (BCP, Proposed Standard, Internet Standard, Informational, Experimental, or Historic)? Why is this the proper type of RFC? Is this type of RFC indicated in the title page header? Standard track (2) The IESG approval announcement includes a Document Announcement Write-Up. Please provide such a Document Announcement Write-Up. Recent examples can be found in the "Action" announcements for approved documents. The approval announcement contains the following sections: Technical Summary: The document provides a solution to reduce the number of upstream allocated labels to be managed by egress PEs by allowing to use provisioned labels. Working Group Summary: No controversy on this draft Document Quality: There's already implementation of the specification. Personnel: Stephane Litkowski is the shepherd Martin Vigoureux is the responsible AD (3) Briefly describe the review of this document that was performed by the Document Shepherd. If this version of the document is not ready for publication, please explain why the document is being forwarded to the IESG. The shepherd provided editorial comments that have been addressed. Nits and references have been checked and updated. (4) Does the document Shepherd have any concerns about the depth or breadth of the reviews that have been performed? No (5) Do portions of the document need review from a particular or from broader perspective, e.g., security, operational complexity, AAA, DNS, DHCP, XML, or internationalization? If so, describe the review that took place. n/a (6) Describe any specific concerns or issues that the Document Shepherd has with this document that the Responsible Area Director and/or the IESG should be aware of? For example, perhaps he or she is uncomfortable with certain parts of the document, or has concerns whether there really is a need for it. In any event, if the WG has discussed those issues and has indicated that it still wishes to advance the document, detail those concerns here. no concern (7) Has each author confirmed that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why? Yes (8) Has an IPR disclosure been filed that references this document? If so, summarize any WG discussion and conclusion regarding the IPR disclosures. There s one IPR (9) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? There is a good consensus on the document (10) Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarise 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 (11) Identify any ID nits the Document Shepherd has found in this document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist). Boilerplate checks are not enough; this check needs to be thorough. No nits (12) Describe how the document meets any required formal review criteria, such as the MIB Doctor, YANG Doctor, media type, and URI type reviews. n/a (13) Have all references within this document been identified as either normative or informative? Yes (14) Are there normative references to documents that are not ready for advancement or are otherwise in an unclear state? If such normative references exist, what is the plan for their completion? no (15) Are there downward normative references references (see RFC 3967)? If so, list these downward references to support the Area Director in the Last Call procedure. no (16) Will publication of this document change the status of any existing RFCs? Are those RFCs listed on the title page header, listed in the abstract, and discussed in the introduction? If the RFCs are not listed in the Abstract and Introduction, explain why, and point to the part of the document where the relationship of this document to the other RFCs is discussed. If this information is not in the document, explain why the WG considers it unnecessary. No, but the document updates few RFCs (17) 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 protocol extensions that the document makes are associated with the appropriate reservations in IANA registries. Confirm that any referenced IANA registries have been clearly identified. Confirm that newly created IANA registries include a detailed specification of the initial contents for the registry, that allocations procedures for future registrations are defined, and a reasonable name for the new registry has been suggested (see RFC 8126). The IANA consideration is written properly (18) List any new IANA registries that require Expert Review for future allocations. Provide any public guidance that the IESG would find useful in selecting the IANA Experts for these new registries. N/a (19) Describe reviews and automated checks performed by the Document Shepherd to validate sections of the document written in a formal language, such as XML code, BNF rules, MIB definitions, YANG modules, etc. n/a (20) If the document contains a YANG module, has the module been checked with any of the recommended validation tools (https://trac.ietf.org/trac/ops/wiki/yang-review-tools) 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 RFC8342? n/a |
|
2021-04-19
|
06 | Stephane Litkowski | Responsible AD changed to Martin Vigoureux |
|
2021-04-19
|
06 | Stephane Litkowski | IETF WG state changed to Submitted to IESG for Publication from WG Consensus: Waiting for Write-Up |
|
2021-04-19
|
06 | Stephane Litkowski | IESG state changed to Publication Requested from I-D Exists |
|
2021-04-19
|
06 | Stephane Litkowski | IESG process started in state Publication Requested |
|
2021-04-19
|
06 | Stephane Litkowski | Notification list changed to slitkows.ietf@gmail.com because the document shepherd was set |
|
2021-04-19
|
06 | Stephane Litkowski | Document shepherd changed to Stephane Litkowski |
|
2021-04-19
|
06 | Stephane Litkowski | Changed consensus to Yes from Unknown |
|
2021-04-19
|
06 | Stephane Litkowski | Intended Status changed to Proposed Standard from None |
|
2021-04-19
|
06 | Stephane Litkowski | This document now replaces draft-zzhang-bess-mvpn-evpn-aggregation-label instead of None |
|
2021-04-19
|
06 | Stephane Litkowski | As required by RFC 4858, this is the current template for the Document Shepherd Write-Up. Changes are expected over time. This version is dated … As required by RFC 4858, this is the current template for the Document Shepherd Write-Up. Changes are expected over time. This version is dated 1 November 2019. (1) What type of RFC is being requested (BCP, Proposed Standard, Internet Standard, Informational, Experimental, or Historic)? Why is this the proper type of RFC? Is this type of RFC indicated in the title page header? Standard track (2) The IESG approval announcement includes a Document Announcement Write-Up. Please provide such a Document Announcement Write-Up. Recent examples can be found in the "Action" announcements for approved documents. The approval announcement contains the following sections: Technical Summary: The document provides a solution to reduce the number of upstream allocated labels to be managed by egress PEs by allowing to use provisioned labels. Working Group Summary: No controversy on this draft Document Quality: There's already implementation of the specification. Personnel: Stephane Litkowski is the shepherd Martin Vigoureux is the responsible AD (3) Briefly describe the review of this document that was performed by the Document Shepherd. If this version of the document is not ready for publication, please explain why the document is being forwarded to the IESG. The shepherd provided editorial comments that have been addressed. Nits and references have been checked and updated. (4) Does the document Shepherd have any concerns about the depth or breadth of the reviews that have been performed? No (5) Do portions of the document need review from a particular or from broader perspective, e.g., security, operational complexity, AAA, DNS, DHCP, XML, or internationalization? If so, describe the review that took place. n/a (6) Describe any specific concerns or issues that the Document Shepherd has with this document that the Responsible Area Director and/or the IESG should be aware of? For example, perhaps he or she is uncomfortable with certain parts of the document, or has concerns whether there really is a need for it. In any event, if the WG has discussed those issues and has indicated that it still wishes to advance the document, detail those concerns here. no concern (7) Has each author confirmed that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why? Yes (8) Has an IPR disclosure been filed that references this document? If so, summarize any WG discussion and conclusion regarding the IPR disclosures. There s one IPR (9) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? There is a good consensus on the document (10) Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarise 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 (11) Identify any ID nits the Document Shepherd has found in this document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist). Boilerplate checks are not enough; this check needs to be thorough. No nits (12) Describe how the document meets any required formal review criteria, such as the MIB Doctor, YANG Doctor, media type, and URI type reviews. n/a (13) Have all references within this document been identified as either normative or informative? Yes (14) Are there normative references to documents that are not ready for advancement or are otherwise in an unclear state? If such normative references exist, what is the plan for their completion? no (15) Are there downward normative references references (see RFC 3967)? If so, list these downward references to support the Area Director in the Last Call procedure. no (16) Will publication of this document change the status of any existing RFCs? Are those RFCs listed on the title page header, listed in the abstract, and discussed in the introduction? If the RFCs are not listed in the Abstract and Introduction, explain why, and point to the part of the document where the relationship of this document to the other RFCs is discussed. If this information is not in the document, explain why the WG considers it unnecessary. No, but the document updates few RFCs (17) 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 protocol extensions that the document makes are associated with the appropriate reservations in IANA registries. Confirm that any referenced IANA registries have been clearly identified. Confirm that newly created IANA registries include a detailed specification of the initial contents for the registry, that allocations procedures for future registrations are defined, and a reasonable name for the new registry has been suggested (see RFC 8126). The IANA consideration is written properly (18) List any new IANA registries that require Expert Review for future allocations. Provide any public guidance that the IESG would find useful in selecting the IANA Experts for these new registries. N/a (19) Describe reviews and automated checks performed by the Document Shepherd to validate sections of the document written in a formal language, such as XML code, BNF rules, MIB definitions, YANG modules, etc. n/a (20) If the document contains a YANG module, has the module been checked with any of the recommended validation tools (https://trac.ietf.org/trac/ops/wiki/yang-review-tools) 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 RFC8342? n/a |
|
2021-04-19
|
06 | Zhaohui Zhang | New version available: draft-ietf-bess-mvpn-evpn-aggregation-label-06.txt |
|
2021-04-19
|
06 | (System) | New version accepted (logged-in submitter: Zhaohui Zhang) |
|
2021-04-19
|
06 | Zhaohui Zhang | Uploaded new revision |
|
2021-01-18
|
05 | Stephane Litkowski | IETF WG state changed to WG Consensus: Waiting for Write-Up from In WG Last Call |
|
2021-01-11
|
05 | Zhaohui Zhang | New version available: draft-ietf-bess-mvpn-evpn-aggregation-label-05.txt |
|
2021-01-11
|
05 | (System) | New version approved |
|
2021-01-11
|
05 | (System) | Request for posting confirmation emailed to previous authors: Eric Rosen <erosen@juniper.net>, IJsbrand Wijnands <ice@cisco.com>, Wen Lin <wlin@juniper.net>, Zhaohui Zhang … Request for posting confirmation emailed to previous authors: Eric Rosen <erosen@juniper.net>, IJsbrand Wijnands <ice@cisco.com>, Wen Lin <wlin@juniper.net>, Zhaohui Zhang <zzhang@juniper.net>, Zhenbin Li <lizhenbin@huawei.com>, bess-chairs@ietf.org |
|
2021-01-11
|
05 | Zhaohui Zhang | Uploaded new revision |
|
2021-01-04
|
Jenny Bui | Posted related IPR disclosure Huawei Technologies Co.,Ltd's Statement about IPR related to draft-ietf-bess-mvpn-evpn-aggregation-label | |
|
2020-12-11
|
04 | Stephane Litkowski | IETF WG state changed to In WG Last Call from WG Document |
|
2020-11-15
|
04 | Zhaohui Zhang | New version available: draft-ietf-bess-mvpn-evpn-aggregation-label-04.txt |
|
2020-11-15
|
04 | (System) | New version accepted (logged-in submitter: Zhaohui Zhang) |
|
2020-11-15
|
04 | Zhaohui Zhang | Uploaded new revision |
|
2020-04-26
|
03 | (System) | Document has expired |
|
2019-10-24
|
03 | Zhaohui Zhang | New version available: draft-ietf-bess-mvpn-evpn-aggregation-label-03.txt |
|
2019-10-24
|
03 | (System) | New version approved |
|
2019-10-24
|
03 | (System) | Request for posting confirmation emailed to previous authors: Zhaohui Zhang <zzhang@juniper.net>, Zhenbin Li <lizhenbin@huawei.com>, IJsbrand Wijnands <ice@cisco.com>, Eric Rosen … Request for posting confirmation emailed to previous authors: Zhaohui Zhang <zzhang@juniper.net>, Zhenbin Li <lizhenbin@huawei.com>, IJsbrand Wijnands <ice@cisco.com>, Eric Rosen <erosen@juniper.net>, Wen Lin <wlin@juniper.net> |
|
2019-10-24
|
03 | Zhaohui Zhang | Uploaded new revision |
|
2019-06-21
|
02 | (System) | Document has expired |
|
2018-12-18
|
02 | Zhaohui Zhang | New version available: draft-ietf-bess-mvpn-evpn-aggregation-label-02.txt |
|
2018-12-18
|
02 | (System) | New version approved |
|
2018-12-18
|
02 | (System) | Request for posting confirmation emailed to previous authors: Zhaohui Zhang <zzhang@juniper.net>, Zhenbin Li <lizhenbin@huawei.com>, IJsbrand Wijnands <ice@cisco.com>, Eric Rosen … Request for posting confirmation emailed to previous authors: Zhaohui Zhang <zzhang@juniper.net>, Zhenbin Li <lizhenbin@huawei.com>, IJsbrand Wijnands <ice@cisco.com>, Eric Rosen <erosen@juniper.net>, Wen Lin <wlin@juniper.net> |
|
2018-12-18
|
02 | Zhaohui Zhang | Uploaded new revision |
|
2018-12-07
|
01 | Zhaohui Zhang | New version available: draft-ietf-bess-mvpn-evpn-aggregation-label-01.txt |
|
2018-12-07
|
01 | (System) | New version approved |
|
2018-12-07
|
01 | (System) | Request for posting confirmation emailed to previous authors: Zhaohui Zhang <zzhang@juniper.net>, Zhenbin Li <lizhenbin@huawei.com>, IJsbrand Wijnands <ice@cisco.com>, Eric Rosen … Request for posting confirmation emailed to previous authors: Zhaohui Zhang <zzhang@juniper.net>, Zhenbin Li <lizhenbin@huawei.com>, IJsbrand Wijnands <ice@cisco.com>, Eric Rosen <erosen@juniper.net>, Wen Lin <wlin@juniper.net> |
|
2018-12-07
|
01 | Zhaohui Zhang | Uploaded new revision |
|
2018-11-26
|
00 | Zhaohui Zhang | New version available: draft-ietf-bess-mvpn-evpn-aggregation-label-00.txt |
|
2018-11-26
|
00 | (System) | New version approved |
|
2018-11-26
|
00 | Zhaohui Zhang | Request for posting confirmation emailed to submitter and authors: Zhaohui Zhang <zzhang@juniper.net>, Zhenbin Li <lizhenbin@huawei.com>, IJsbrand Wijnands <ice@cisco.com>, Eric … Request for posting confirmation emailed to submitter and authors: Zhaohui Zhang <zzhang@juniper.net>, Zhenbin Li <lizhenbin@huawei.com>, IJsbrand Wijnands <ice@cisco.com>, Eric Rosen <erosen@juniper.net>, Wen Lin <wlin@juniper.net> |
|
2018-11-26
|
00 | Zhaohui Zhang | Uploaded new revision |