datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Negotiation for Keying Pairwise Routing Protocols in IKEv2
draft-mahesh-karp-rkmp-05

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-11-15
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

Network Working Group                                    M. Jethanandani
Internet-Draft                                         Ciena Corporation
Intended status: Standards Track                                 B. Weis
Expires: May 20, 2014                                           K. Patel
                                                           Cisco Systems
                                                                D. Zhang
                                                                  Huawei
                                                              S. Hartman
                                                       Painless Security
                                                             U. Chunduri
                                                                 A. Tian
                                                           Ericsson Inc.
                                                                J. Touch
                                                                 USC/ISI
                                                       November 16, 2013

       Negotiation for Keying Pairwise Routing Protocols in IKEv2
                       draft-mahesh-karp-rkmp-05

Abstract

   This document describes a mechanism to secure the routing protocols
   which use unicast to transport their signaling messages.  Most of
   such routing protocols are TCP-based (e.g., BGP and LDP), and the TCP
   Authentication Option (TCP-AO) is primarily employed for securing the
   signaling messages of these routing protocols.  There are also two
   exceptions: BFD which is over UDP or MPLS, and RSVP-TE which is over
   IP (but employs an integrated approach to protecting the signaling
   messages instead of using IPsec).  The proposed mechanism secures
   pairwise TCP-based Routing Protocol (RP) associations, BFD
   associations and RSVP-TE associations using the IKEv2 Key Management
   Protocol (KMP) integrated with TCP-AO, BFD, and RSVP-TE respectively.
   Included are extensions to IKEv2 and its Security Associations to
   enable its key negotiation to support TCP-AO, BFD, and RSVP-TE.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

Jethanandani, et al.      Expires May 20, 2014                  [Page 1]
Internet-Draft                TCP-AO-IKEv2                 November 2013

   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 May 20, 2014.

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminologies . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Acronyms and Abbreviations  . . . . . . . . . . . . . . .   4
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Types of Keys . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Protocol Exchanges  . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  IKE_SA_INIT . . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  IKE_AUTH  . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  CREATE_CHILD_SA . . . . . . . . . . . . . . . . . . . . .   7
     3.4.  INFORMATIONAL . . . . . . . . . . . . . . . . . . . . . .   8
   4.  Operation Details . . . . . . . . . . . . . . . . . . . . . .   8

[include full document text]