Deprecation of AS_SET and AS_CONFED_SET in BGP
draft-ietf-idr-deprecate-as-set-confed-set-02

Document Type Active Internet-Draft (idr WG)
Last updated 2019-11-03
Replaces draft-kumari-deprecate-as-set-confed-set
Stream IETF
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          W. Kumari
Internet-Draft                                              Google, Inc.
Obsoletes: 6472 (if approved)                                  K. Sriram
Updates: 4271 5065 (if approved)                             L. Hannachi
Intended status: Standards Track                                USA NIST
Expires: May 6, 2020                                    November 3, 2019

             Deprecation of AS_SET and AS_CONFED_SET in BGP
             draft-ietf-idr-deprecate-as-set-confed-set-02

Abstract

   BCP 172 (i.e., RFC 6472) recommends not using AS_SET and
   AS_CONFED_SET in the Border Gateway Protocol.  This document advances
   this recommendation to a standards requirement in BGP; it proscribes
   the use of the AS_SET and AS_CONFED_SET types of path segments in the
   AS_PATH.  This is done to simplify the design and implementation of
   BGP and to make the semantics of the originator of a route clearer.
   This will also simplify the design, implementation, and deployment of
   various BGP security mechanisms.  This document (if approved) updates
   RFC 4271 and RFC 5065 by eliminating AS_SET and AS_CONFED_SET types,
   and obsoletes RFC 6472.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 6, 2020.

Copyright Notice

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

Kumari, et al.             Expires May 6, 2020                  [Page 1]
Internet-Draft    AS_SET, AS_CONFED_SET use deprecation    November 2019

   (https://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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Recommendations . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Updates to Existing RFCs  . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   BCP 172 [RFC6472] makes a recommendation for not using AS_SET (see
   [RFC4271]) and AS_CONFED_SET (see [RFC5065]) in the Border Gateway
   Protocol (BGP).  This document advances the BCP recommendation to a
   standards requirement in BGP; it proscribes the use of the AS_SET and
   AS_CONFED_SET types of path segments in the AS_PATH.

   The AS_SET path segment in the AS_PATH attribute (Sections 4.3 and
   5.1.2 of [RFC4271]) is created by a router that is performing route
   aggregation and contains an unordered set of Autonomous Systems
   (ASes) that the update has traversed.  The AS_CONFED_SET path segment
   (see [RFC5065]) in the AS_PATH attribute is created by a router that
   is performing route aggregation and contains an unordered set of
   Member AS Numbers in the local confederation that the update has
   traversed.  It is very similar to AS_SETs but is used within a
   confederation.

   By performing aggregation, a router is combining multiple existing
   routes into a single new route.  The aggregation together with the
   use of AS_SET blurs the semantics of origin AS for the prefix being
   announced.  Therefore, the aggregation with AS_SET (or AS_CONFED_SET)
   can cause operational issues, such as not being able to authenticate
Show full document text