• Aucun résultat trouvé

Status of This Memo This is an Internet Standards Track document

N/A
N/A
Protected

Academic year: 2022

Partager "Status of This Memo This is an Internet Standards Track document"

Copied!
3
0
0

Texte intégral

(1)

Internet Engineering Task Force (IETF) J. Scudder Request for Comments: 6938 Juniper Networks Category: Standards Track May 2013 ISSN: 2070-1721

Deprecation of BGP Path Attributes: DPA, ADVERTISER, and RCID_PATH / CLUSTER_ID

Abstract

This document requests IANA to deprecate the following BGP path attributes: DPA, ADVERTISER, and RCID_PATH / CLUSTER_ID, associated with an abandoned Internet-Draft and a Historic RFC.

Status of This Memo

This is an Internet Standards Track document.

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at

http://www.rfc-editor.org/info/rfc6938.

Copyright Notice

Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust’s Legal Provisions Relating to IETF Documents

(http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents

carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Scudder Standards Track [Page 1]

(2)

RFC 6938 Deprecation of DPA et al. May 2013

1. Introduction

As of this writing, the BGP Path Attributes registry maintained by IANA contains entries for DPA, ADVERTISER, and RCID_PATH /

CLUSTER_ID. The first of these is associated with [BGPDPA], an

Internet-Draft that was abandoned in 1996. The latter are associated with [RFC1863], an RFC that was reclassified as Historic by [RFC4223]

in 2005. Neither specification is currently in use, nor have they ever been.

Note that the deprecated CLUSTER_ID is distinct from CLUSTER_LIST [RFC4456]. CLUSTER_LIST is not being deprecated.

2. IANA Considerations

Per this document, IANA has marked the BGP Path Attributes registry entries for DPA (Value 11), ADVERTISER (Value 12), and RCID_PATH / CLUSTER_ID (Value 13) as "deprecated".

3. Security Considerations

There are no meaningful security consequences arising from this registry update.

4. Informative References

[BGPDPA] Chen, E. and T. Bates, "Destination Preference Attribute for BGP", Work in Progress, March 1996.

[RFC1863] Haskin, D., "A BGP/IDRP Route Server alternative to a full mesh routing", RFC 1863, October 1995.

[RFC4223] Savola, P., "Reclassification of RFC 1863 to Historic", RFC 4223, October 2005.

[RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)", RFC 4456, April 2006.

Scudder Standards Track [Page 2]

(3)

RFC 6938 Deprecation of DPA et al. May 2013

Author’s Address John Scudder Juniper Networks 1194 N. Mathilda Ave.

Sunnyvale, CA 94089 USA

EMail: jgs@juniper.net

Scudder Standards Track [Page 3]

Références

Documents relatifs

For historical reasons, NAT devices are not typically capable of handling datagrams and flows for applications that use the Datagram Congestion Control Protocol (DCCP)

This document describes the operations that can be applied to user input in order to get it into a form that is acceptable by the Internationalized Domain Names in

It is therefore necessary, indeed urgent, to specify a method of transmitting IPv6 datagrams [RFC2460] over the RFC 1149 medium, rather than obliging those service providers

They can do this, for example, by invoking an API provided by a host firewall included with the operating system, or by providing metadata to the operating system for use

This document outlines a possible, but not recommended, method to mitigate the effect of collisions in the DNS namespace by providing a means for end users to disambiguate

syntax variant, called Pandoc [Pandoc], and a bit of XML [RFC2629] as a source format for documents that are Internet-Drafts (I-Ds) or RFCs.. The goal of this technique is to

The adjustment is always towards larger (i.e., slower) interval values when the initial interval proposed by the peer is not supported.. This document is not adding

On the other hand, when the protocol is ICMP, a NAT session is created only for query/response-type ICMP messages such as ICMP echo, Timestamp, and