Deprecation of BGP Path Attribute Values 30, 31, 129, 241, 242, and 243
draft-ietf-idr-deprecate-30-31-129-02
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2017-02-14
|
02 | (System) | RFC Editor state changed to AUTH48-DONE from AUTH48 |
2017-02-13
|
02 | (System) | RFC Editor state changed to AUTH48 from EDIT |
2017-01-11
|
02 | (System) | IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor |
2017-01-11
|
02 | (System) | IANA Action state changed to Waiting on RFC Editor from Waiting on Authors |
2017-01-11
|
02 | (System) | IANA Action state changed to Waiting on Authors |
2017-01-10
|
02 | Gunter Van de Velde | Request for Telechat review by OPSDIR Completed: Ready. Reviewer: Mehmet Ersue. |
2017-01-09
|
02 | (System) | RFC Editor state changed to EDIT |
2017-01-09
|
02 | (System) | IESG state changed to RFC Ed Queue from Approved-announcement sent |
2017-01-09
|
02 | (System) | Announcement was received by RFC Editor |
2017-01-09
|
02 | Amy Vezza | IESG state changed to Approved-announcement sent from Approved-announcement to be sent |
2017-01-09
|
02 | Amy Vezza | IESG has approved the document |
2017-01-09
|
02 | Amy Vezza | Closed "Approve" ballot |
2017-01-09
|
02 | Amy Vezza | Ballot approval text was generated |
2017-01-05
|
02 | Jean Mahoney | Request for Telechat review by GENART Completed: Ready. Reviewer: Meral Shirazipour. |
2017-01-05
|
02 | Cindy Morgan | IESG state changed to Approved-announcement to be sent from IESG Evaluation |
2017-01-05
|
02 | Jari Arkko | [Ballot Position Update] New position, No Objection, has been recorded for Jari Arkko |
2017-01-04
|
02 | Amanda Baber | IANA Review state changed to IANA OK - Actions Needed from Version Changed - Review Needed |
2017-01-04
|
02 | Ben Campbell | [Ballot Position Update] New position, No Objection, has been recorded for Ben Campbell |
2017-01-04
|
02 | Kathleen Moriarty | [Ballot Position Update] New position, No Objection, has been recorded for Kathleen Moriarty |
2017-01-04
|
02 | Stephen Farrell | [Ballot Position Update] New position, No Objection, has been recorded for Stephen Farrell |
2017-01-04
|
02 | Spencer Dawkins | [Ballot Position Update] New position, Yes, has been recorded for Spencer Dawkins |
2017-01-03
|
02 | Suresh Krishnan | [Ballot Position Update] New position, No Objection, has been recorded for Suresh Krishnan |
2017-01-03
|
02 | Terry Manderson | [Ballot Position Update] New position, Yes, has been recorded for Terry Manderson |
2017-01-03
|
02 | Alia Atlas | [Ballot Position Update] New position, Yes, has been recorded for Alia Atlas |
2017-01-03
|
02 | Deborah Brungard | [Ballot Position Update] New position, No Objection, has been recorded for Deborah Brungard |
2017-01-03
|
02 | Alissa Cooper | [Ballot Position Update] New position, No Objection, has been recorded for Alissa Cooper |
2017-01-03
|
02 | Benoît Claise | [Ballot Position Update] New position, No Objection, has been recorded for Benoit Claise |
2017-01-02
|
02 | Mirja Kühlewind | [Ballot Position Update] New position, No Objection, has been recorded for Mirja Kühlewind |
2017-01-01
|
02 | Joel Jaeggli | [Ballot comment] Stop them before they kill again. Imho, while we're not doing it here, we should probably provide advice to implementers or even revisit … [Ballot comment] Stop them before they kill again. Imho, while we're not doing it here, we should probably provide advice to implementers or even revisit how we allocate them on how to do this safely in the future cause squatting on code points is definite minefield here. |
2017-01-01
|
02 | Joel Jaeggli | [Ballot Position Update] New position, Yes, has been recorded for Joel Jaeggli |
2016-12-31
|
02 | Jean Mahoney | Request for Telechat review by GENART is assigned to Meral Shirazipour |
2016-12-31
|
02 | Jean Mahoney | Request for Telechat review by GENART is assigned to Meral Shirazipour |
2016-12-29
|
02 | (System) | IANA Review state changed to Version Changed - Review Needed from IANA OK - Actions Needed |
2016-12-29
|
02 | Job Snijders | New version available: draft-ietf-idr-deprecate-30-31-129-02.txt |
2016-12-29
|
02 | (System) | New version approved |
2016-12-29
|
02 | (System) | Request for posting confirmation emailed to previous authors: "Job Snijders" |
2016-12-29
|
02 | Job Snijders | Uploaded new revision |
2016-12-27
|
01 | Meral Shirazipour | Request for Last Call review by GENART Completed: Ready with Nits. Reviewer: Meral Shirazipour. |
2016-12-23
|
01 | Alexey Melnikov | [Ballot Position Update] New position, No Objection, has been recorded for Alexey Melnikov |
2016-12-22
|
01 | Tero Kivinen | Request for Last Call review by SECDIR Completed: Ready. Reviewer: Radia Perlman. |
2016-12-21
|
01 | (System) | IANA Review state changed to IANA OK - Actions Needed from Version Changed - Review Needed |
2016-12-17
|
01 | (System) | IANA Review state changed to Version Changed - Review Needed from IANA OK - Actions Needed |
2016-12-17
|
01 | Job Snijders | New version available: draft-ietf-idr-deprecate-30-31-129-01.txt |
2016-12-17
|
01 | (System) | New version approved |
2016-12-17
|
01 | (System) | Request for posting confirmation emailed to previous authors: "Job Snijders" |
2016-12-17
|
01 | Job Snijders | Uploaded new revision |
2016-12-16
|
00 | Alvaro Retana | IESG state changed to IESG Evaluation from Waiting for Writeup |
2016-12-16
|
00 | Alvaro Retana | Ballot has been issued |
2016-12-16
|
00 | Alvaro Retana | [Ballot Position Update] New position, Yes, has been recorded for Alvaro Retana |
2016-12-16
|
00 | Alvaro Retana | Created "Approve" ballot |
2016-12-16
|
00 | Alvaro Retana | Ballot writeup was changed |
2016-12-16
|
00 | (System) | IANA Review state changed to IANA OK - Actions Needed from IANA - Review Needed |
2016-12-16
|
00 | Sabrina Tanamal | (Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs: The IANA Services Operator has completed its review of draft-ietf-idr-deprecate-30-31-129-00.txt. If any part of this review is inaccurate, please let … (Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs: The IANA Services Operator has completed its review of draft-ietf-idr-deprecate-30-31-129-00.txt. If any part of this review is inaccurate, please let us know. The IANA Services Operator understands that, upon approval of this document, there is a single action which we must complete. In the BGP Path Attributes subregistry of the Border Gateway Protocol (BGP) Parameters registry located at: https://www.iana.org/assignments/bgp-parameters/ the following registrations will be marked deprecated: 30, 31, 129, 241, 242 and 243. The IANA Services Operator understands that this is the only action required to be completed upon approval of this document. Note: The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed. Thank you, Sabrina Tanamal IANA Services Specialist PTI |
2016-12-16
|
00 | (System) | IESG state changed to Waiting for Writeup from In Last Call |
2016-12-08
|
00 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Radia Perlman |
2016-12-08
|
00 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Radia Perlman |
2016-12-05
|
00 | Jean Mahoney | Request for Last Call review by GENART is assigned to Meral Shirazipour |
2016-12-05
|
00 | Jean Mahoney | Request for Last Call review by GENART is assigned to Meral Shirazipour |
2016-12-02
|
00 | Alvaro Retana | Telechat date has been changed to 2017-01-05 from 2016-12-15 |
2016-12-02
|
00 | Gunter Van de Velde | Request for Telechat review by OPSDIR is assigned to Mehmet Ersue |
2016-12-02
|
00 | Gunter Van de Velde | Request for Telechat review by OPSDIR is assigned to Mehmet Ersue |
2016-12-02
|
00 | Amy Vezza | IANA Review state changed to IANA - Review Needed |
2016-12-02
|
00 | Amy Vezza | The following Last Call announcement was sent out: From: The IESG To: "IETF-Announce" CC: idr@ietf.org, idr-chairs@ietf.org, draft-ietf-idr-deprecate-30-31-129@ietf.org, jgs@juniper.net, aretana@cisco.com, shares@ndzh.com … The following Last Call announcement was sent out: From: The IESG To: "IETF-Announce" CC: idr@ietf.org, idr-chairs@ietf.org, draft-ietf-idr-deprecate-30-31-129@ietf.org, jgs@juniper.net, aretana@cisco.com, shares@ndzh.com, "John Scudder" Reply-To: ietf@ietf.org Sender: Subject: Last Call: (Deprecation of BGP Path Attribute values 30, 31, 129, 241, 242, and 234) to Proposed Standard The IESG has received a request from the Inter-Domain Routing WG (idr) to consider the following document: - 'Deprecation of BGP Path Attribute values 30, 31, 129, 241, 242, and 234' 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 2016-12-16. 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 requests IANA to mark BGP path attribute values 30, 31, 129, 241, 242, and 243 as "deprecated". The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-30-31-129/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-30-31-129/ballot/ No IPR declarations have been submitted directly on this I-D. |
2016-12-02
|
00 | Amy Vezza | IESG state changed to In Last Call from Last Call Requested |
2016-12-02
|
00 | Amy Vezza | Last call announcement was changed |
2016-12-01
|
00 | Alvaro Retana | Placed on agenda for telechat - 2016-12-15 |
2016-12-01
|
00 | Alvaro Retana | Last call was requested |
2016-12-01
|
00 | Alvaro Retana | Ballot approval text was generated |
2016-12-01
|
00 | Alvaro Retana | Ballot writeup was generated |
2016-12-01
|
00 | Alvaro Retana | IESG state changed to Last Call Requested from AD Evaluation |
2016-12-01
|
00 | Alvaro Retana | Last call announcement was generated |
2016-12-01
|
00 | Alvaro Retana | IESG state changed to AD Evaluation from Publication Requested |
2016-12-01
|
00 | Alvaro Retana | Notification list changed to "John Scudder" <jgs@juniper.net>, shares@ndzh.com, aretana@cisco.com from "John Scudder" <jgs@juniper.net>, shares@ndzh.com; |
2016-12-01
|
00 | John Scudder | 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? Proposed Standard. This is necessary to make changes to the related IANA registries which have standards action policy. (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 requests IANA to mark BGP path attribute values 30, 31, 129, 241, 242, and 243 as "deprecated". These values were found to be in use in the Internet, despite not having been allocated by IANA. Working Group Summary This document arises because as part of the development of the large communities specification, values 30 and 31 were discovered to be "squatted" on by fielded implementations. Subsequently, two other implementations were found to be "squatting" on the other values. There was some debate in the working group as to whether it was better to deprecate the code points or to somehow "punish" the offending implementers. One of the arguments in favor of deprecation was that pragmatically speaking, no implementer would reasonably want to use one of the tainted code points and if forced to do so, no operator would be excited to deploy the resulting feature. The deprecation process was identified as the appropriate one to allow IANA to flag them as unfit for use. There was good working group consensus for this position. There was also a concern raised by Tom Petch that "deprecated" is not a well-defined term in the IETF lexicon and that different working group members might understand it to mean different things. This concern was addressed by explicitly adopting the definition of "deprecated" used in draft-leiba-cotton-iana-5226bis. Thus there is no ambiguity as to what the working group agreed to. Finally it's worth noting that as part of the working group discussion it was pointed out that it's possible for a "deprecated" value to later be assigned. This might become relevant if one of the implementations that is currently "squatting" on one of those values later is brought up to snuff to meet the requirements for proper allocation. As a possibly-interesting point of trivia, all debate about this draft took place before and during the working group adoption call, there was no discussion during the working group last call, which was announced as a "silence gives assent" call immediately following the conclusion of the adoption call. (There was opportunity for WG members to object to the "silence gives assent" rules, nobody did.) 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 is a trivial process document. It has received good WG attention including review by people associated with all parties "squatting" on the affected path attribute values. Personnel Who is the Document Shepherd? Who is the Responsible Area Director? Document Shepherd: John Scudder Responsible Area Director: Alvaro Retana (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. I've carefully read each version of the document as it was prepared, and monitored the mailing list discussion. The document is ready for publication. (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. No. (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: https://www.ietf.org/mail-archive/web/idr/current/msg17196.html (8) Has an IPR disclosure been filed that references this document? If so, summarize any WG discussion and conclusion regarding the IPR disclosures. N/A (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? Strong and active consensus was shown, see also the working group summary above. (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 https://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist). Boilerplate checks are not enough; this check needs to be thorough. IDnits throws a "outdated reference" complaint for draft-ietf-idr-large-community; this will be corrected as a matter of course when the document reaches RFC editor phase and is not worth revising the document for now, especially because draft-ietf-idr-large-community is in IESG review and further revisions are likely before this document is complete. (12) Describe how the document meets any required formal review criteria, such as the MIB 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. Although the values being deprecated are of course being used in implementations of various (draft, not RFC) specifications, none of the values are documented in those specifications, so this document does not update them. (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). This document is essentially nothing but an IANA Considerations section, as such the Document Shepherd's review was comprehensive and exhaustive. (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. N/A |
2016-12-01
|
00 | John Scudder | Responsible AD changed to Alvaro Retana |
2016-12-01
|
00 | John Scudder | IETF WG state changed to Submitted to IESG for Publication from WG Consensus: Waiting for Write-Up |
2016-12-01
|
00 | John Scudder | IESG state changed to Publication Requested |
2016-12-01
|
00 | John Scudder | IESG process started in state Publication Requested |
2016-12-01
|
00 | John Scudder | IETF WG state changed to WG Consensus: Waiting for Write-Up from In WG Last Call |
2016-12-01
|
00 | Susan Hares | Notification list changed to "John Scudder" <jgs@juniper.net>, shares@ndzh.com; from "John Scudder" <jgs@juniper.net> |
2016-11-30
|
00 | John Scudder | Changed consensus to Yes from Unknown |
2016-11-30
|
00 | John Scudder | Intended Status changed to Proposed Standard from None |
2016-11-30
|
00 | John Scudder | Changed document writeup |
2016-11-22
|
00 | John Scudder | Notification list changed to "John Scudder" <jgs@juniper.net> |
2016-11-22
|
00 | John Scudder | Document shepherd changed to John Scudder |
2016-11-16
|
00 | John Scudder | IETF WG state changed to In WG Last Call from WG Document |
2016-11-14
|
00 | John Scudder | This document now replaces draft-snijders-idr-deprecate-30-31-129 instead of None |
2016-11-14
|
00 | Job Snijders | New version available: draft-ietf-idr-deprecate-30-31-129-00.txt |
2016-11-14
|
00 | (System) | WG -00 approved |
2016-11-14
|
00 | Job Snijders | Set submitter to "Job Snijders ", replaces to (none) and sent approval email to group chairs: idr-chairs@ietf.org |
2016-11-14
|
00 | Job Snijders | Uploaded new revision |