Default External BGP (EBGP) Route Propagation Behavior without Policies
draft-ietf-grow-bgp-reject-08
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2017-07-01
|
08 | (System) | RFC Editor state changed to AUTH48-DONE from AUTH48 |
2017-06-30
|
08 | (System) | RFC Editor state changed to AUTH48 from EDIT |
2017-06-12
|
08 | (System) | IANA Action state changed to No IC from In Progress |
2017-06-12
|
08 | (System) | IANA Action state changed to In Progress |
2017-06-12
|
08 | (System) | RFC Editor state changed to EDIT |
2017-06-12
|
08 | (System) | IESG state changed to RFC Ed Queue from Approved-announcement sent |
2017-06-12
|
08 | (System) | Announcement was received by RFC Editor |
2017-06-12
|
08 | Amy Vezza | IESG state changed to Approved-announcement sent from Approved-announcement to be sent |
2017-06-12
|
08 | Amy Vezza | IESG has approved the document |
2017-06-12
|
08 | Amy Vezza | Closed "Approve" ballot |
2017-06-12
|
08 | Amy Vezza | Ballot approval text was generated |
2017-06-12
|
08 | Amy Vezza | Ballot writeup was changed |
2017-06-08
|
08 | Cindy Morgan | IESG state changed to Approved-announcement to be sent from IESG Evaluation |
2017-06-08
|
08 | Takeshi Takahashi | Request for Telechat review by SECDIR Completed: Ready. Reviewer: Takeshi Takahashi. |
2017-06-08
|
08 | Benoît Claise | [Ballot comment] The Appendix A is typically what the OPS directorate would look for. |
2017-06-08
|
08 | Benoît Claise | [Ballot Position Update] New position, No Objection, has been recorded for Benoit Claise |
2017-06-07
|
08 | Terry Manderson | [Ballot Position Update] New position, No Objection, has been recorded for Terry Manderson |
2017-06-07
|
08 | Deborah Brungard | [Ballot Position Update] New position, No Objection, has been recorded for Deborah Brungard |
2017-06-06
|
08 | Amanda Baber | IANA Review state changed to IANA OK - No Actions Needed from Version Changed - Review Needed |
2017-06-06
|
08 | Suresh Krishnan | [Ballot Position Update] New position, No Objection, has been recorded for Suresh Krishnan |
2017-06-06
|
08 | Alia Atlas | [Ballot Position Update] New position, Yes, has been recorded for Alia Atlas |
2017-06-06
|
08 | Alvaro Retana | [Ballot Position Update] New position, Yes, has been recorded for Alvaro Retana |
2017-06-06
|
08 | Eric Rescorla | [Ballot comment] I am having a little trouble reading Appendix A. If I understand correctly, the idea is: - In version N, you have a … [Ballot comment] I am having a little trouble reading Appendix A. If I understand correctly, the idea is: - In version N, you have a behavior X - In version N+1, you introduce a setting S with default value S=X - In version N+2 you change the default to S=!X However, the text says that "installations upgraded from release N+1 will adhere to the previous insecure behavior" Do you need to say that in N+1, you save the value S=X so that in N+1, it continues to apply? |
2017-06-06
|
08 | Eric Rescorla | [Ballot Position Update] New position, No Objection, has been recorded for Eric Rescorla |
2017-06-06
|
08 | Alissa Cooper | [Ballot Position Update] New position, Yes, has been recorded for Alissa Cooper |
2017-06-06
|
08 | Spencer Dawkins | [Ballot comment] I echo Adam's appreciation for Appendix A. |
2017-06-06
|
08 | Spencer Dawkins | [Ballot Position Update] New position, No Objection, has been recorded for Spencer Dawkins |
2017-06-05
|
08 | Kathleen Moriarty | [Ballot Position Update] New position, No Objection, has been recorded for Kathleen Moriarty |
2017-06-05
|
08 | Adam Roach | [Ballot comment] Thank you for Appendix A; I think it is very helpful. Dale Worley's name appears twice in the Acknowledgements section. |
2017-06-05
|
08 | Adam Roach | [Ballot Position Update] New position, Yes, has been recorded for Adam Roach |
2017-06-03
|
08 | Alexey Melnikov | [Ballot Position Update] Position for Alexey Melnikov has been changed to Yes from No Objection |
2017-06-03
|
08 | Alexey Melnikov | [Ballot Position Update] New position, No Objection, has been recorded for Alexey Melnikov |
2017-06-02
|
08 | Ben Campbell | [Ballot Position Update] New position, Yes, has been recorded for Ben Campbell |
2017-06-01
|
08 | Dale Worley | Request for Telechat review by GENART Completed: Ready. Reviewer: Dale Worley. Sent review to list. |
2017-05-30
|
08 | Jean Mahoney | Request for Telechat review by GENART is assigned to Dale Worley |
2017-05-30
|
08 | Jean Mahoney | Request for Telechat review by GENART is assigned to Dale Worley |
2017-05-26
|
08 | (System) | IANA Review state changed to Version Changed - Review Needed from IANA OK - No Actions Needed |
2017-05-26
|
08 | Job Snijders | New version available: draft-ietf-grow-bgp-reject-08.txt |
2017-05-26
|
08 | (System) | New version approved |
2017-05-26
|
08 | (System) | Request for posting confirmation emailed to previous authors: Job Snijders , Greg Hankins , Jared Mauch |
2017-05-26
|
08 | Job Snijders | Uploaded new revision |
2017-05-24
|
07 | Mirja Kühlewind | [Ballot Position Update] New position, No Objection, has been recorded for Mirja Kühlewind |
2017-05-19
|
07 | Dale Worley | Request for Telechat review by GENART Completed: Ready with Nits. Reviewer: Dale Worley. Sent review to list. |
2017-05-11
|
07 | Jean Mahoney | Request for Telechat review by GENART is assigned to Dale Worley |
2017-05-11
|
07 | Jean Mahoney | Request for Telechat review by GENART is assigned to Dale Worley |
2017-05-11
|
07 | Tero Kivinen | Request for Telechat review by SECDIR is assigned to Takeshi Takahashi |
2017-05-11
|
07 | Tero Kivinen | Request for Telechat review by SECDIR is assigned to Takeshi Takahashi |
2017-05-09
|
07 | (System) | IANA Review state changed to IANA OK - No Actions Needed from Version Changed - Review Needed |
2017-05-09
|
07 | Warren Kumari | Placed on agenda for telechat - 2017-06-08 |
2017-05-09
|
07 | Warren Kumari | IESG state changed to IESG Evaluation from Waiting for AD Go-Ahead |
2017-05-09
|
07 | Warren Kumari | Ballot has been issued |
2017-05-09
|
07 | Warren Kumari | [Ballot Position Update] New position, Yes, has been recorded for Warren Kumari |
2017-05-09
|
07 | Warren Kumari | Created "Approve" ballot |
2017-05-09
|
07 | Warren Kumari | Ballot writeup was changed |
2017-05-08
|
07 | Job Snijders | New version available: draft-ietf-grow-bgp-reject-07.txt |
2017-05-08
|
07 | (System) | New version approved |
2017-05-08
|
07 | (System) | Request for posting confirmation emailed to previous authors: Job Snijders , Greg Hankins , Jared Mauch |
2017-05-08
|
07 | Job Snijders | Uploaded new revision |
2017-05-02
|
06 | (System) | IESG state changed to Waiting for AD Go-Ahead from In Last Call |
2017-05-01
|
06 | (System) | IANA Review state changed to Version Changed - Review Needed from IANA OK - No Actions Needed |
2017-05-01
|
06 | Job Snijders | New version available: draft-ietf-grow-bgp-reject-06.txt |
2017-05-01
|
06 | (System) | New version approved |
2017-05-01
|
06 | (System) | Request for posting confirmation emailed to previous authors: Job Snijders , Greg Hankins , Jared Mauch |
2017-05-01
|
06 | Job Snijders | Uploaded new revision |
2017-04-21
|
05 | (System) | IANA Review state changed to IANA OK - No Actions Needed from Version Changed - Review Needed |
2017-04-21
|
05 | Sabrina Tanamal | (Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs: The IANA Services Operator has reviewed draft-ietf-grow-bgp-reject-05.txt, which is currently in Last Call, and has the following comments: We … (Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs: The IANA Services Operator has reviewed draft-ietf-grow-bgp-reject-05.txt, which is currently in Last Call, and has the following comments: We understand that this document doesn't require any registry actions. While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object. If this assessment is not accurate, please respond as soon as possible. Thank you, Sabrina Tanamal IANA Services Specialist PTI |
2017-04-20
|
05 | Alvaro Retana | Notification list changed to Christopher Morrow <christopher.morrow@gmail.com>, aretana@cisco.com from Christopher Morrow <christopher.morrow@gmail.com> |
2017-04-20
|
05 | Tero Kivinen | Request for Last Call review by SECDIR Completed: Ready. Reviewer: Takeshi Takahashi. |
2017-04-19
|
05 | Carlos Martínez | Request for Last Call review by OPSDIR Completed: Ready. Reviewer: Carlos Martinez. |
2017-04-18
|
05 | Cindy Morgan | The following Last Call announcement was sent out: From: The IESG To: IETF-Announce CC: draft-ietf-grow-bgp-reject@ietf.org, grow-chairs@ietf.org, grow@ietf.org, Christopher Morrow , christopher.morrow@gmail.com, … The following Last Call announcement was sent out: From: The IESG To: IETF-Announce CC: draft-ietf-grow-bgp-reject@ietf.org, grow-chairs@ietf.org, grow@ietf.org, Christopher Morrow , christopher.morrow@gmail.com, warren@kumari.net Reply-To: ietf@ietf.org Sender: Subject: Last Call: (Default EBGP Route Propagation Behavior Without Policies) to Proposed Standard The IESG has received a request from the Global Routing Operations WG (grow) to consider the following document: - 'Default EBGP Route Propagation Behavior Without Policies' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2017-05-02. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document defines the default behavior of a BGP speaker when there is no import or export policy associated with an External BGP session. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-reject/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-reject/ballot/ This IETF LC, which originally concluded on 2017-04-18, is being extended to allow for additional input to be provided. Ops AD (for GROW) and Routing AD (for IDR) wish to ensure that cross WG discussions have had a chance to occur. No IPR declarations have been submitted directly on this I-D. |
2017-04-18
|
05 | Cindy Morgan | IESG state changed to In Last Call from Last Call Requested |
2017-04-18
|
05 | Cindy Morgan | Last call was requested |
2017-04-18
|
05 | Cindy Morgan | IESG state changed to Last Call Requested from Waiting for Writeup |
2017-04-18
|
05 | Cindy Morgan | Last call announcement was changed |
2017-04-18
|
05 | Cindy Morgan | Last call announcement was generated |
2017-04-18
|
05 | Warren Kumari | Ballot writeup was changed |
2017-04-18
|
05 | Warren Kumari | 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 24 February 2012. (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? Standards 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 "This document defines the default behavior of a BGP speaker when there is no import or export policy associated with an External BGP session." Working Group Summary Was there anything in WG process that is worth noting? For example, was there controversy about particular points or were there decisions where the consensus was particularly rough? Nothing of note. Document Quality Are there existing implementations of the protocol? Have a significant number of vendors indicated their plan to implement the specification? Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? If there was a MIB Doctor, Media Type or other expert review, what was its course (briefly)? In the case of a Media Type review, on what date was the request posted? This document describes a change in default (or a standardization of a default) behavior, no changes in protocols expected. Basically this says that implementations MUST consider a deny-all policy if nothing is explicitly configured / act as though the peer is not fully configured until policy is applied. Personnel Who is the Document Shepherd? Who is the Responsible Area Director? Shepherd: christopher.morrow@gmail.com (me) RAD: warren@kumari.net (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. Shepherd read and reviewed the document along it's life cycle. It's ready for publication at this time. (4) Does the document Shepherd have any concerns about the depth or breadth of the reviews that have been performed? no concern (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. no external review required. (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 concerns (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. no claims filed. (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? quite solid consensus. (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 threats (11) Identify any ID nits the Document Shepherd has found in this document. (See https://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist). Boilerplate checks are not enough; this check needs to be thorough. There are no nits identified. (12) Describe how the document meets any required formal review criteria, such as the MIB Doctor, media type, and URI type reviews. no external/expert review is required. (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 (edited by Warren) (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 changes (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 5226). No IANA actions are expected from this draft. (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. none (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, etc. no reviews required. |
2017-04-18
|
05 | (System) | IESG state changed to Waiting for Writeup from In Last Call |
2017-04-14
|
05 | Alvaro Retana | This document now replaces draft-mauch-bgp-reject instead of None |
2017-04-12
|
05 | (System) | IANA Review state changed to Version Changed - Review Needed from IANA OK - No Actions Needed |
2017-04-12
|
05 | Job Snijders | New version available: draft-ietf-grow-bgp-reject-05.txt |
2017-04-12
|
05 | (System) | New version approved |
2017-04-12
|
05 | (System) | Request for posting confirmation emailed to previous authors: Job Snijders , Greg Hankins , Jared Mauch |
2017-04-12
|
05 | Job Snijders | Uploaded new revision |
2017-04-10
|
04 | Min Ye | Request for Last Call review by RTGDIR Completed: Ready. Reviewer: Russ White. |
2017-04-10
|
04 | Dale Worley | Request for Last Call review by GENART Completed: Ready with Nits. Reviewer: Dale Worley. Sent review to list. |
2017-04-09
|
04 | Min Ye | Request for Last Call review by RTGDIR is assigned to Russ White |
2017-04-09
|
04 | Min Ye | Request for Last Call review by RTGDIR is assigned to Russ White |
2017-04-07
|
04 | Alvaro Retana | Requested Last Call review by RTGDIR |
2017-04-06
|
04 | Jean Mahoney | Request for Last Call review by GENART is assigned to Dale Worley |
2017-04-06
|
04 | Jean Mahoney | Request for Last Call review by GENART is assigned to Dale Worley |
2017-04-06
|
04 | (System) | IANA Review state changed to IANA OK - No Actions Needed from IANA - Review Needed |
2017-04-06
|
04 | Sabrina Tanamal | (Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs: The IANA Services Operator has reviewed draft-ietf-grow-bgp-reject-04.txt, which is currently in Last Call, and has the following comments: We … (Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs: The IANA Services Operator has reviewed draft-ietf-grow-bgp-reject-04.txt, which is currently in Last Call, and has the following comments: We understand that this document doesn't require any registry actions. While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object. If this assessment is not accurate, please respond as soon as possible. Thank you, Sabrina Tanamal IANA Services Specialist PTI |
2017-04-06
|
04 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Takeshi Takahashi |
2017-04-06
|
04 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Takeshi Takahashi |
2017-04-05
|
04 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Carlos Martinez |
2017-04-05
|
04 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Carlos Martinez |
2017-04-04
|
04 | Amy Vezza | IANA Review state changed to IANA - Review Needed |
2017-04-04
|
04 | Amy Vezza | The following Last Call announcement was sent out: From: The IESG To: IETF-Announce CC: draft-ietf-grow-bgp-reject@ietf.org, grow-chairs@ietf.org, grow@ietf.org, Christopher Morrow , christopher.morrow@gmail.com, … The following Last Call announcement was sent out: From: The IESG To: IETF-Announce CC: draft-ietf-grow-bgp-reject@ietf.org, grow-chairs@ietf.org, grow@ietf.org, Christopher Morrow , christopher.morrow@gmail.com, warren@kumari.net Reply-To: ietf@ietf.org Sender: Subject: Last Call: (Default EBGP Route Propagation Behavior Without Policies) to Proposed Standard The IESG has received a request from the Global Routing Operations WG (grow) to consider the following document: - 'Default EBGP Route Propagation Behavior Without Policies' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2017-04-18. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document defines the default behavior of a BGP speaker when there is no import or export policy associated with an External BGP session. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-reject/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-reject/ballot/ No IPR declarations have been submitted directly on this I-D. |
2017-04-04
|
04 | Amy Vezza | IESG state changed to In Last Call from Last Call Requested |
2017-04-04
|
04 | Warren Kumari | 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 24 February 2012. (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? Standards 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 "This document defines the default behavior of a BGP speaker when there is no import or export policy associated with an External BGP session." Working Group Summary Was there anything in WG process that is worth noting? For example, was there controversy about particular points or were there decisions where the consensus was particularly rough? Nothing of note. Document Quality Are there existing implementations of the protocol? Have a significant number of vendors indicated their plan to implement the specification? Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? If there was a MIB Doctor, Media Type or other expert review, what was its course (briefly)? In the case of a Media Type review, on what date was the request posted? This document describes a change in default (or a standardization of a default) behavior, no changes in protocols expected. Personnel Who is the Document Shepherd? Who is the Responsible Area Director? Shepherd: christopher.morrow@gmail.com (me) RAD: warren@kumari.net (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. Shepherd read and reviewed the document along it's life cycle. It's ready for publication at this time. (4) Does the document Shepherd have any concerns about the depth or breadth of the reviews that have been performed? no concern (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. no external review required. (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 concerns (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. no claims filed. (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? quite solid consensus. (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 threats (11) Identify any ID nits the Document Shepherd has found in this document. (See https://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist). Boilerplate checks are not enough; this check needs to be thorough. There are no nits identified. (12) Describe how the document meets any required formal review criteria, such as the MIB Doctor, media type, and URI type reviews. no external/expert review is required. (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 (edited by Warren) (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 changes (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 5226). No IANA actions are expected from this draft. (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. none (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, etc. no reviews required. |
2017-04-04
|
04 | Warren Kumari | Last call was requested |
2017-04-04
|
04 | Warren Kumari | Ballot approval text was generated |
2017-04-04
|
04 | Warren Kumari | Ballot writeup was generated |
2017-04-04
|
04 | Warren Kumari | IESG state changed to Last Call Requested from AD Evaluation |
2017-04-04
|
04 | Warren Kumari | Last call announcement was generated |
2017-04-04
|
04 | Warren Kumari | Last call announcement was generated |
2017-03-29
|
04 | Cindy Morgan | Shepherding AD changed to Warren Kumari |
2017-03-27
|
04 | Job Snijders | New version available: draft-ietf-grow-bgp-reject-04.txt |
2017-03-27
|
04 | (System) | New version approved |
2017-03-27
|
04 | (System) | Request for posting confirmation emailed to previous authors: grow-chairs@ietf.org, Job Snijders , Greg Hankins , Jared Mauch |
2017-03-27
|
04 | Job Snijders | Uploaded new revision |
2017-03-25
|
03 | Joel Jaeggli | IESG state changed to AD Evaluation from Publication Requested |
2017-03-23
|
03 | Chris Morrow | 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 24 February 2012. (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? Standards 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 "This document defines the default behavior of a BGP speaker when there is no import or export policy associated with an External BGP session." Working Group Summary Was there anything in WG process that is worth noting? For example, was there controversy about particular points or were there decisions where the consensus was particularly rough? Nothing of note. Document Quality Are there existing implementations of the protocol? Have a significant number of vendors indicated their plan to implement the specification? Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? If there was a MIB Doctor, Media Type or other expert review, what was its course (briefly)? In the case of a Media Type review, on what date was the request posted? This document describes a change in default (or a standardization of a default) behavior, no changes in protocols expected. Personnel Who is the Document Shepherd? Who is the Responsible Area Director? Shepherd: christopher.morrow@gmail.com (me) RAD: warren@kumari.net (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. Shepherd read and reviewed the document along it's life cycle. It's ready for publication at this time. (4) Does the document Shepherd have any concerns about the depth or breadth of the reviews that have been performed? no concern (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. no external review required. (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 concerns (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. no claims filed. (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? quite solid consensus. (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 threats (11) Identify any ID nits the Document Shepherd has found in this document. (See https://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist). Boilerplate checks are not enough; this check needs to be thorough. There are no nits identified. (12) Describe how the document meets any required formal review criteria, such as the MIB Doctor, media type, and URI type reviews. no external/expert review is required. (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? yes (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 changes (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 5226). No IANA actions are expected from this draft. (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. none (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, etc. no reviews required. |
2017-03-23
|
03 | Chris Morrow | Responsible AD changed to Joel Jaeggli |
2017-03-23
|
03 | Chris Morrow | IETF WG state changed to Submitted to IESG for Publication from WG Document |
2017-03-23
|
03 | Chris Morrow | IESG state changed to Publication Requested |
2017-03-23
|
03 | Chris Morrow | IESG process started in state Publication Requested |
2017-03-23
|
03 | Chris Morrow | Changed document writeup |
2017-03-23
|
03 | Chris Morrow | Notification list changed to Christopher Morrow <christopher.morrow@gmail.com> |
2017-03-23
|
03 | Chris Morrow | Document shepherd changed to Christopher Morrow |
2017-03-23
|
03 | Chris Morrow | Changed consensus to Yes from Unknown |
2017-03-23
|
03 | Chris Morrow | Intended Status changed to Proposed Standard from None |
2017-02-21
|
03 | Job Snijders | New version available: draft-ietf-grow-bgp-reject-03.txt |
2017-02-21
|
03 | (System) | New version approved |
2017-02-21
|
03 | (System) | Request for posting confirmation emailed to previous authors: Job Snijders , Greg Hankins , Jared Mauch |
2017-02-21
|
03 | Job Snijders | Uploaded new revision |
2016-10-31
|
02 | Job Snijders | New version available: draft-ietf-grow-bgp-reject-02.txt |
2016-10-31
|
02 | (System) | New version approved |
2016-10-31
|
01 | (System) | Request for posting confirmation emailed to previous authors: grow-chairs@ietf.org, "Jared Mauch" , "Job Snijders" |
2016-10-31
|
01 | Job Snijders | Uploaded new revision |
2016-05-10
|
01 | Jared Mauch | New version available: draft-ietf-grow-bgp-reject-01.txt |
2015-12-28
|
00 | Jared Mauch | New version available: draft-ietf-grow-bgp-reject-00.txt |