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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-05-24
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)
Operational Security                                     G. Van de Velde
Internet-Draft                                                  K. Patel
Updates: 792, 4443 (if approved)                           Cisco Systems
Intended status: Standards Track                            May 24, 2012
Expires: November 25, 2012

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

Abstract

   The BGP Remote-Next-Hop optional transitive attribute, provides an
   additional level of recursive route-lookup.  The BGP Remote-Next-Hop
   attribute can be used, both on the public Internet infrastructure and
   within public or private Autonomous Systems (AS).  The usage of BGP
   Remote-Next-Hop operates as ships-in-the-night and does not require
   any capability exchange for any BGP Session.  BGP Remote-Next-Hop is
   providing the distribution of one or more Location Identifiers
   assigned to a particular BGP prefix or an NLRI.  To secure the BGP
   prefix or NLRI entry BGP security mechanisms, either RPKI or other
   BGP mechanisms can be utilized.

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 November 25, 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

Van de Velde & Patel    Expires November 25, 2012               [Page 1]
Internet-Draft             BGP Remote-Next-Hop                  May 2012

   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  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . . . 3
     1.2.  Option Format: BGP Remote-Next-Hop  . . . . . . . . . . . . 3
       1.2.1.  BGP Option Type . . . . . . . . . . . . . . . . . . . . 3
       1.2.2.  Option Format . . . . . . . . . . . . . . . . . . . . . 4
       1.2.3.  Remote-Next-Hop Attribute Format  . . . . . . . . . . . 4
     1.3.  Usage Guidelines  . . . . . . . . . . . . . . . . . . . . . 5
       1.3.1.  Networks that do NOT support BGP Next-Hop-Attribute . . 5
       1.3.2.  Multi-homing for IPv6 . . . . . . . . . . . . . . . . . 5
       1.3.3.  Mapping Technology to compliment LISP . . . . . . . . . 6
       1.3.4.  Network Overlay Infrastructure  . . . . . . . . . . . . 6
       1.3.5.  Reduction of the Routing Forwarding Information
               Base  . . . . . . . . . . . . . . . . . . . . . . . . . 6
   2.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
   3.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
     3.1.  Privacy Considerations  . . . . . . . . . . . . . . . . . . 7
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 7
   5.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 7
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 8

Van de Velde & Patel    Expires November 25, 2012               [Page 2]
Internet-Draft             BGP Remote-Next-Hop                  May 2012

1.  Introduction

   Each IP address (v4 or v6) represents a location and an identity.
   This is captured and developed by Locator Identity Split Protocol
   (LISP) and additionally documented by rfc6227 (Design Goals for
   Scalable Internet Routing) to scale the Internet.

   The optional transitive BGP Remote-Next-Hop attribute provides a
   mapping to complement and support mapping technologies (i.e.  LISP)
   by using using BGP to distribute either a single or a set of locators
   attached to each entry in the BGP table.  Based upon this locater
Show full document text