Deprecation of BGP Path Attributes: DPA, ADVERTISER, and RCID_PATH / CLUSTER_ID
draft-ietf-idr-deprecate-dpa-etal-00

We have received this 2nd Last Call for draft-ietf-idr-deprecate-dpa-etal-00
and have the following comments:

We noticed that the document still has the Intended Status as
"Informational" located at the top area of the document.

We understand that, upon approval of this document, there is a single action which needs to be completed.

In the BGP Path Attributes subregistry of the Border Gateway Protocol (BGP) Parameters registry located at:

http://www.iana.org/assignments/bgp-parameters

the following BGP Path Attributes will be marked as "Deprecated"
as per this document:

DPA (Value 11)
[Chen, E., Bates, T., "Destination Preference Attribute for BGP", Work in progress, March 1996.][this document]

ADVERTISER (Value 12)
[RFC1863][RFC4223][this document]

RCID_PATH / CLUSTER_ID (Value 13)
[RFC1863][RFC4223][this document]

IANA understands that this is the only action required to be completed upon approval of this document.

Please report any inaccuracies and respond to any questions as soon as possible.

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.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC:
Reply-To: ietf@ietf.org
Subject: Last Call:  (Deprecation of BGP Path Attributes DPA, ADVERTISER and RCID_PATH / CLUSTER_ID) 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 Attributes DPA, ADVERTISER and RCID_PATH /
  CLUSTER_ID'
  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 2013-03-07. 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 deprecate the BGP path attributes DPA,
  ADVERTISER, and RCID_PATH / CLUSTER_ID, associated with an abandoned
  Internet Draft and a Historic RFC, respectively.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-dpa-etal/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-dpa-etal/ballot/


No IPR declarations have been submitted directly on this I-D.

This document was previously Last Called as Informational. However it
deprecates codepoints that were created by Standards Track documents.
It is therefore being re Last Called as a Proposed Standard. The
text change to PS is provided via an RFC Editor Note in the tracker.

[Ballot discuss]
I agree with Adrian, but I think in these cases, we are simply cleaning up earlier process fails.

DPA looks to have been an Early Allocation. Our rules for Early Allocation (RFC 4020) says that entries should expire after 1 year should simply be marked as deprecated. We failed to make that happen. Doing so now is just cleaning up something we ought to have done semi-automatically.

ADVERTISER, and RCID_PATH / CLUSTER_ID look to have been Standards Action additions by RFC 1863. So a Standards Action should be needed to deprecate them. But there *was* a Standards Action: Moving 1863 to Historic. The failure there was that 4223 had no IANA actions, and the move to Historic was not minuted as a Standards Action.

Barry's right: This should have simply been a Management Item. No need for the draft or a new RFC. Can we skip the document and just do the action? Why waste an RFC number? Minute the action and be done with it.

[Ballot comment]
I am very supportive of this action, but completely confused by process.

AFAICS, the registry is "Standards Action process or the Early IANA Allocation process". From where I stand, that means that action to change the registry must be in a Standards Track RFC or (for new allocations) in an I-D that is intended for Standards Track publication.

This would be a minor pain in this case since the I-D was last called as Informational. However, we have lived a number of years with these stray values in the registry, so I doubt a couple more weeks will kill anyone. I'll leave it to the responsible AD to work out what needs to be done.

[Ballot comment]
No action required here, other than, perhaps, further generic discussion within the IESG:

We should absolutely do this.

I would have preferred to do it by last-calling the action and then handling it as a management item by the IESG.  The significant expense of publishing an RFC for it seems excessive.

IANA has reviewed draft-ietf-idr-deprecate-dpa-etal-00 and has the following comments:

IANA understands that, upon approval of this document, there is a single action which needs to be completed.

In the BGP Path Attributes subregistry of the Border Gateway Protocol (BGP) Parameters registry located at:

http://www.iana.org/assignments/bgp-parameters

the following BGP Path Attributes will be marked as "Deprecated"
as per this document:

DPA (Value 11)
[Chen, E., Bates, T., "Destination Preference Attribute for BGP", Work in progress, March 1996.][this document]

ADVERTISER (Value 12)
[RFC1863][RFC4223][this document]

RCID_PATH / CLUSTER_ID (Value 13)
[RFC1863][RFC4223][this document]

IANA 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.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC:
Reply-To: ietf@ietf.org
Subject: Last Call:  (Deprecation of BGP Path Attributes DPA, ADVERTISER and RCID_PATH / CLUSTER_ID) to Informational RFC


The IESG has received a request from the Inter-Domain Routing WG (idr) to
consider the following document:
- 'Deprecation of BGP Path Attributes DPA, ADVERTISER and RCID_PATH /
  CLUSTER_ID'
  as Informational RFC

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 2013-01-24. 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 deprecate the BGP path attributes DPA,
  ADVERTISER, and RCID_PATH / CLUSTER_ID, associated with an abandoned
  Internet Draft and a Historic RFC, respectively.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-dpa-etal/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-dpa-etal/ballot/


No IPR declarations have been submitted directly on this I-D.

Doc Shepherd write-up submitted.  We have scheduled teleconference for review with  AD( Stewart Bryant)  for 1/3/12 at 10:00am. If AD agrees, this this will go forward to the 1/10/13 IESG teleconference.