datatracker.ietf.org
Sign in
Version 5.6.4.p1, 2014-10-20
Report a bug

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

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-10-08
Intended RFC status: Unknown
Other versions: plain text, xml, 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: April 11, 2015                                    Cisco Systems
                                                               R. Raszuk
                                                            NTT MCL Inc.
                                                                 R. Bush
                                               Internet Initiative Japan
                                                         October 8, 2014

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

Abstract

   The BGP Remote-Next-Hop attribute is an optional transitive attribute
   intended to facilitate automatic tunnelling across an AS for an NLRI
   in a given address family.  The attribute carries one or more tunnel
   end-points and associated tunnel encapsulation information for a
   NLRI.

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 11, 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 April 11, 2015                 [Page 1]
Internet-Draft                                              October 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Remote-Next-Hop Attribute . . . . . . . . . . . . . . . . . .   3
     3.1.  Tunnel Encapsulation attribute versus BGP Remote-Next-Hop
           attribute . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.   BGP Remote-Next-Hop attribute TLV Format . . . . . . . . . .   4
   5.  Encapsulation sub-TLVs for virtual network overlays . . . . .   5
     5.1.  Encapsulation sub-TLV for VXLAN . . . . . . . . . . . . .   6
     5.2.  Encapsulation sub-TLV for NVGRE . . . . . . . . . . . . .   7
     5.3.  Encapsulation sub-TLV for GTP . . . . . . . . . . . . . .   8
     5.4.  Encapsulation for MPLS-in-GRE . . . . . . . . . . . . . .   8
   6.  Remote-Next-Hop Bestpath Considerations . . . . . . . . . . .   9
   7.  Securing Remote-Next-Hop  . . . . . . . . . . . . . . . . . .   9
     7.1.  Restrictions on Announcing of Remote-Next-Hop Attribute .  10
     7.2.  Restrictions on Originating of Remote-Next-Hop Attribute   10
   8.  Multiple tunnel endpoint addresses  . . . . . . . . . . . . .  11
   9.  Attribute error handling  . . . . . . . . . . . . . . . . . .  11
   10. BGP speakers that do not support BGP Remote-Next-Hop
       attribute . . . . . . . . . . . . . . . . . . . . . . . . . .  11
   11. Use Case scenarios  . . . . . . . . . . . . . . . . . . . . .  11
     11.1.  Stateless user-plane architecture for virtualized EPC
            (vEPC) . . . . . . . . . . . . . . . . . . . . . . . . .  12
     11.2.  Stateless User-plane Architecture for virtual Packet
            Edge . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     11.3.  Dynamic Network Overlay Infrastructure . . . . . . . . .  12
     11.4.  Simple VPN solution using Multi-point Security
            Association  . . . . . . . . . . . . . . . . . . . . . .  12
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   13. Security Considerations . . . . . . . . . . . . . . . . . . .  13
   14. Privacy Considerations  . . . . . . . . . . . . . . . . . . .  14
   15. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14

[include full document text]