BGP Signaled IPsec Tunnel Configuration
draft-hujun-idr-bgp-ipsec-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-05
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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                                                                J. Hu
Internet-Draft                                                     Nokia
Intended status: Standards Track                           March 4, 2019
Expires: September 5, 2019

                BGP Signaled IPsec Tunnel Configuration
                      draft-hujun-idr-bgp-ipsec-00

Abstract

   This document defines a method of using BGP to signal IPsec tunnel
   configuration along with NLRI, it uses and extends tunnel
   encapsulation attribute as specified in [I-D.ietf-idr-tunnel-encaps]
   for IPsec tunnel.

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 https://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 September 5, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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.

Hu                      Expires September 5, 2019               [Page 1]
Internet-Draft             BGP signaled IPsec                 March 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Tunnel Encapsulation Attribute for IPsec  . . . . . . . . . .   3
     2.1.  Local and Remote Prefix sub-TLV . . . . . . . . . . . . .   4
     2.2.  Public Routing Instance sub-TLV . . . . . . . . . . . . .   4
   3.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Semantics and Usage of IPsec Tunnel Encapsulation attribute .   8
     4.1.  Nested Tunnel . . . . . . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   IPsec is the standard for IP layer traffic protection, however in a
   big network where mesh connections are needed, configuring large
   number of IPsec tunnels is error prone and not scalable.  So instead
   of pre-provision IPsec tunnels on each router, this document defines
   a method to allow router to advertise the IPsec tunnel configurations
   it requires to reach a given NLRI via BGP.  This document does not
   intend to be one solution for all cases, the main use case is to
   simplify IPsec tunnel provision in networks under single
   administrative domain; it uses standard based components (IPsec/
   IKEv2[RFC7296] and BGP) with limited changes.  There is no change to
   IPsec/IKEv2, and only limited changes to BGP.

   IPsec tunnel configurations typically include following parts:

   o  tunnel endpoint address (local and remote)

   o  public routing instance, routing instance where IPsec packet is
      forwarded in

   o  private routing instance, routing instance where payload packet is
      forwarded in

   o  tunnel authentication method and credentials

   o  IKE SA and CHILD SA transform (a.k.a crypto algorithms)

   o  CHILD SA traffic selector

   o  other: like lifetime, DPD timer, use of PFS ..etc

Hu                      Expires September 5, 2019               [Page 2]
Internet-Draft             BGP signaled IPsec                 March 2019

   In order to minimize amount configurations signal via BGP, only
   following configurations are explicit advertised:

   o  local tunnel endpoint address: BGP tunnel encapsulation attribute

   o  public routing instance: sub-TLV in tunnel encapsulation attribute
Show full document text