datatracker.ietf.org
Sign in
Version 5.6.2.p2, 2014-07-24
Report a bug

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

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-06-30
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

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

IDR                                                      G. Van de Velde
Internet-Draft                                                  K. Patel
Intended status: Standards Track                                  D. Rao
Expires: January 1, 2015                                   Cisco Systems
                                                               R. Raszuk
                                                            NTT MCL Inc.
                                                                 R. Bush
                                               Internet Initiative Japan
                                                           June 30, 2014

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

Abstract

   The BGP Remote-Next-Hop is an 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 January 1, 2015.

Copyright Notice

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

Van de Velde, et al.     Expires January 1, 2015                [Page 1]
Internet-Draft                                                 June 2014

   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.  Tunnel Encapsulation attribute versus BGP Remote-Next-Hop
       attribute . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.   BGP Remote-Next-Hop attribute TLV Format . . . . . . . . . .   4
     4.1.  Encapsulation sub-TLVs for virtual network overlays . . .   5
       4.1.1.  Encapsulation sub-TLV for VXLAN . . . . . . . . . . .   6
       4.1.2.  Encapsulation sub-TLV for NVGRE . . . . . . . . . . .   7
       4.1.3.  Encapsulation sub-TLV for GTP . . . . . . . . . . . .   8
   5.  Use Case scenarios  . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Stateless user-plane architecture for virtualized EPC
           (vEPC)  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  Stateless User-plane Architecture for virtual Packet Edge   9
     5.3.  Multi-homing for IPv6 . . . . . . . . . . . . . . . . . .   9
     5.4.  Dynamic Network Overlay Infrastructure  . . . . . . . . .  10
     5.5.  The Tunnel end-point is NOT the originating BGP speaker .  10
     5.6.  Networks that do not support BGP Remote-Next-Hop
           attribute . . . . . . . . . . . . . . . . . . . . . . . .  10
     5.7.  Networks that do support BGP Remote-Next-Hop attribute  .  10
   6.  BGP Remote-Next-Hop Community . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
     8.1.  Protecting the validity of the BGP Remote-Next-Hop
           attribute . . . . . . . . . . . . . . . . . . . . . . . .  11
   9.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  11
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   11. Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .  11
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     12.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

[include full document text]