idnits 2.17.00 (12 Aug 2021) /tmp/idnits21330/draft-ietf-idr-deprecate-dpa-etal-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 10, 2012) is 3442 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 1863 (Obsoleted by RFC 4223) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Scudder 3 Internet-Draft Juniper Networks 4 Intended status: Informational December 10, 2012 5 Expires: June 13, 2013 7 Deprecation of BGP Path Attributes DPA, ADVERTISER and RCID_PATH / 8 CLUSTER_ID 9 draft-ietf-idr-deprecate-dpa-etal-00 11 Abstract 13 This document requests IANA to deprecate the BGP path attributes DPA, 14 ADVERTISER, and RCID_PATH / CLUSTER_ID, associated with an abandoned 15 Internet Draft and a Historic RFC, respectively. 17 Status of this Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on June 13, 2013. 34 Copyright Notice 36 Copyright (c) 2012 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 1. Introduction 51 As of this writing the BGP Path Attributes registry maintained by 52 IANA contains entries for DPA, ADVERTISER, and RCID_PATH / 53 CLUSTER_ID. The first of these is associated with 54 [draft-ietf-idr-bgp-dpa-05], an Internet Draft that was abandoned in 55 1996. The latter are associated with [RFC1863], an RFC that was 56 reclassified as Historic by [RFC4223] in 2005. Neither of these 57 specifications is in use now, nor ever was. 59 Note that the deprecated CLUSTER_ID is distinct from CLUSTER_LIST 60 [RFC4456]. CLUSTER_LIST is not being deprecated. 62 2. IANA Considerations 64 This document requests IANA to mark the BGP Path Attributes registry 65 entries for DPA (Value 11), ADVERTISER (Value 12), and RCID_PATH / 66 CLUSTER_ID (Value 13) as "Deprecated". 68 3. Security Considerations 70 There are no meaningful security consequences arising from this 71 registry update. 73 4. Informative References 75 [RFC1863] Haskin, D., "A BGP/IDRP Route Server alternative to a full 76 mesh routing", RFC 1863, October 1995. 78 [RFC4223] Savola, P., "Reclassification of RFC 1863 to Historic", 79 RFC 4223, October 2005. 81 [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route 82 Reflection: An Alternative to Full Mesh Internal BGP 83 (IBGP)", RFC 4456, April 2006. 85 [draft-ietf-idr-bgp-dpa-05] 86 Chen, E. and T. Bates, "Destination Preference Attribute 87 for BGP", 1996. 89 Author's Address 91 John Scudder 92 Juniper Networks 93 1194 N. Mathilda Ave 94 Sunnyvale, CA 94089 95 USA 97 Email: jgs@juniper.net