datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

IPv6 Extensions for Route Target Distribution
draft-ietf-idr-bgp-ipv6-rt-constrain-03

Active Internet-Draft (idr WG)
Document Stream: IETF
Last updated: 2012-12-18
Intended RFC status: (None)
Other versions: plain text, pdf, html

IETF State: WG Document (idr)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                           K. Patel
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                               R. Raszuk
Expires: June 21, 2013                                      NTT MCL Inc.
                                                             M. Djernaes
                                                        Juniper Networks
                                                                 J. Dong
                                                                 M. Chen
                                                     Huawei Technologies
                                                       December 18, 2012

             IPv6 Extensions for Route Target Distribution
                draft-ietf-idr-bgp-ipv6-rt-constrain-03

Abstract

   The current route target distribution specification described in
   RFC4684 defines Route Target NLRIs of maximum length of 12 bytes.
   The IPv6 specific Route Target extended community is defined in
   [RFC5701] as length of 20 bytes.  Since the current specification
   only supports prefixes of maximum length of 12 bytes, the lack of an
   IPv6 specific Route Target reachability information may be a problem
   when an operator wants to use this application in a pure IPv6
   environment.  This document defines an extension that allows BGP to
   exchange longer length IPv6 Route Target prefixes.

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 http://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."

Patel, et al.             Expires June 21, 2013                 [Page 1]
Internet-Draft     IPv6 Extensions for RT Distribution     December 2012

   This Internet-Draft will expire on June 21, 2013.

Copyright Notice

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

Patel, et al.             Expires June 21, 2013                 [Page 2]
Internet-Draft     IPv6 Extensions for RT Distribution     December 2012

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 4
   2.  BGP IPv6 Constrained Route Target Capability  . . . . . . . . . 4
   3.  IPv6 Constrained Route Target NLRI Advertisements . . . . . . . 4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 5
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 6

Patel, et al.             Expires June 21, 2013                 [Page 3]
Internet-Draft     IPv6 Extensions for RT Distribution     December 2012

1.  Introduction

   The current constrained route distribution specification defined in
   [RFC4684] supports prefixes with a maximum length of 12 bytes.  The
   prefix length needs to be extended to support the IPv6 specific Route
   Target extended community defined in [RFC5701] which is 20 bytes in