BGP Remote-Next-Hop
draft-vandevelde-idr-remote-next-hop-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-10-15
Replaced by draft-ietf-idr-tunnel-encaps
Stream (None)
Intended RFC status (None)
Formats 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)
IDR                                                      G. Van de Velde
Internet-Draft                                                  K. Patel
Intended status: Standards Track                           Cisco Systems
Expires: April 02, 2013                                        R. Raszuk
                                                            NTT MCL Inc.
                                                                 R. Bush
                                               Internet Initiative Japan
                                                            October 2012

                          BGP Remote-Next-Hop
                draft-vandevelde-idr-remote-next-hop-02

Abstract

   The BGP Remote-Next-Hop is a new optional transitive attribute
   intended to facilitate automatic tunneling across an AS on a per
   address family basis.  The attribute carries one or more tunnel end-
   points for a NLRI.  Additionally, tunnel encapsulation information is
   communicated to successfully setup these tunnels.

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

   This Internet-Draft will expire on April 02, 2013.

Van de Velde, et al.     Expires April 02, 2013                 [Page 1]
Internet-Draft                                              October 2012

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.

   This document may not be modified, and derivative works of it may not
   be created, and it may not be published except as an Internet-Draft.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Requirements Language  . . . . . . . . . . . . . . . . . . . .  2
   3.  Tunnel Encapsulation attribute versus BGP Remote-Next-Hop
       attribute  . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   4.   BGP Remote-Next-Hop attribute TLV Format  . . . . . . . . . .  3
   5.  Use Case scenarios . . . . . . . . . . . . . . . . . . . . . .  4
     5.1.  Multi-homing for IPv6  . . . . . . . . . . . . . . . . . .  4
     5.2.  Dynamic Network Overlay Infrastructure . . . . . . . . . .  5
     5.3.  The Tunnel end-point is NOT the originating BGP speaker  .  5
     5.4.  Networks that do not support BGP Remote-Next-Hop attribute  5
     5.5.  Networks that do NOT support BGP Remote-Next-Hop attribute  5
   6.  BGP Remote-Next-Hop Community  . . . . . . . . . . . . . . . .  5
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  5
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . .  6
     8.1.  Protecting the validity of the BGP Remote-Next-Hop attribut 6
   9.  Privacy Considerations . . . . . . . . . . . . . . . . . . . .  6
   10. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     11.1.  Normative References  . . . . . . . . . . . . . . . . . .  6
     11.2.  Informative References  . . . . . . . . . . . . . . . . .  7
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  7

1.  Introduction

   [RFC5512] defines an attribute attached to an NLRI to signal tunnel
   end-point encapsulation information between two BGP speakers.  It
   assumes that the exchanged tunnel endpoint is the NLRI.

   This document defines a new BGP transitive attribute known as a
   Remote-Next-Hop BGP attribute for Intra-AS and Inter-AS usage which
   removes that assumption.

   The tunnel endpoint information and the tunnel encapsulation
   information is carried within a Remote-Next-Hop BGP attribute.  This
   attribute is tagged on an any BGP NLRI. This way the Address Family
   (AF) of the NLRI exchanged is decoupled from the tunnel SAFI address-
Show full document text