Dismiss
There will be a system update on Friday, May 5th, 6 PM ET. You may experience a brief service interruption.
Browse Prior Art Database

Deprecation of BGP Path Attribute Values 30, 31, 129, 241, 242, and 243 (RFC8093)

IP.com Disclosure Number: IPCOM000249339D
Original Publication Date: 2017-Feb-01
Included in the Prior Art Database: 2017-Feb-17
Document File: 6 page(s) / 6K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Snijders: AUTHOR

Abstract

It has been discovered that certain BGP Path Attribute values have been used in BGP implementations that have been deployed in the wild while not being assigned by IANA for such usage. Unregistered usage of BGP Path Attribute values can lead to deployment problems for new technologies.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 49% of the total text.

Internet Engineering Task Force (IETF)                       J. Snijders Request for Comments: 8093                                           NTT Category: Standards Track                                  February 2017 ISSN: 2070-1721

                    Deprecation of BGP Path Attribute                  Values 30, 31, 129, 241, 242, and 243

Abstract

   This document requests IANA to mark BGP path attribute values 30, 31,    129, 241, 242, and 243 as "Deprecated".

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

   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/rfc8093.

Copyright Notice

   Copyright (c) 2017 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.

Snijders                     Standards Track                    [Page 1]
 RFC 8093       Deprecation of Squatted BGP Path Attributes February 2017

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2    2.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   2    3.  Security Considerations . . . . . . . . . . . . . . . . . . .   2    4.  Informative References  . . . . . . . . . . . . . . . . . . .   3    Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   3    Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3

1.  Introduction

   It has been discovered that certain BGP Path Attribute values have    been used in BGP implementations that have been deployed in the wild    while not being assigned by IANA for such usage.  Unregistered usage    of BGP Path Attribute values can lead to deployment problems for new    technologies.

   The use of these unregistere...