BGP Extended Community for Identifying the Target Node
draft-dong-idr-node-target-ext-comm-02

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            J. Dong
Internet-Draft                                                 S. Zhuang
Intended status: Standards Track                     Huawei Technologies
Expires: September 10, 2020                              G. Van de Velde
                                                                   Nokia
                                                           March 9, 2020

         BGP Extended Community for Identifying the Target Node
                 draft-dong-idr-node-target-ext-comm-02

Abstract

   BGP [RFC4271] has been used to distribute different types of routing
   and policy information in the network.  In some cases, the
   information distributed may be only intended for one or several
   particular receiving BGP nodes in the network.  However, BGP does not
   have a general mechanism of designating the receiving node of the
   routing information.  This document defines a new type of BGP
   Extended Community called "Node Target".  The mechanism of using the
   Node Target Extended Community to steer BGP route distribution to
   particular BGP nodes is specified.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 September 10, 2020.

Dong, et al.           Expires September 10, 2020               [Page 1]
Internet-Draft     BGP Node Target Extended Community         March 2020

Copyright Notice

   Copyright (c) 2020 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
   (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.  Node Target Extended Communities  . . . . . . . . . . . . . .   3
     2.1.  IPv4 Node Target Extended Community . . . . . . . . . . .   3
     2.2.  IPv6 Node Target Extended Community . . . . . . . . . . .   4
   3.  Procedures  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   BGP [RFC4271] has been used to distribute different types of routing
   and policy information in the network.  In some cases, the
   information distributed may be only intended for one or several
   particular receiving BGP nodes in the network.  A typical use case is
   the distribution of BGP FlowSpec [RFC5575] [I-D.ietf-idr-rfc5575bis]
   policies to some particular BGP nodes.  Such a targeting mechanism
   would be useful that it can save the amount of TCAM.

   However, BGP does not have a general mechanism of designating the
   receiving nodes of the information to be distributed.  Route Target
   (RT) as defined in [RFC4364] is used for the distribution of VPN
   routes into the target VPN Routing and Forwarding tables (VRFs) on a
   set of PE nodes.  Although it is possible to use RTs to control the
   distribution of non VPN-specific information to particular receiving
   nodes, such mechanism is not applicable when the information to be
   distributed is VPN-specific and relies on RTs to match the target

Dong, et al.           Expires September 10, 2020               [Page 2]
Show full document text