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

A framework for RPs to use IKEv2 KMP
draft-chunduri-karp-using-ikev2-with-tcp-ao-06

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-02-04
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

Working Group                                                U. Chunduri
Internet-Draft                                                   A. Tian
Intended status: Informational                             Ericsson Inc.
Expires: August 9, 2014                                         J. Touch
                                                                 USC/ISI
                                                        February 5, 2014

                  A framework for RPs to use IKEv2 KMP
             draft-chunduri-karp-using-ikev2-with-tcp-ao-06

Abstract

   This document describes a mechanism to enable using IKEv2 with TCP-
   AO, which may also be of more general use to other pairwise Routing
   Protocols.

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 August 9, 2014.

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
   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.

Chunduri, et al.         Expires August 9, 2014                 [Page 1]
Internet-Draft    A framework for RPs to use IKEv2 KMP     February 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Acronyms  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Motivation and Overview . . . . . . . . . . . . . . . . . . .   4
     2.1.  Manual Keying with the Gatekeeper . . . . . . . . . . . .   6
   3.  The Gatekeeper  . . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  TCP-based RP interface to the Gatekeeper  . . . . . . . .   8
       3.1.1.  TCP-AO interface to Gatekeeper  . . . . . . . . . . .   9
     3.2.  Other pairwise RPs interface to the Gatekeeper  . . . . .   9
     3.3.  KMP interaction with the Gatekeeper . . . . . . . . . . .  10
       3.3.1.  Interaction with KARP Crypto Key Table  . . . . . . .  11
       3.3.2.  Interface to the PAD  . . . . . . . . . . . . . . . .  12
     3.4.  Impact of Policy changes  . . . . . . . . . . . . . . . .  13
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   7.  Appendix A  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     7.1.  BGP Multi Session and transport level differentiation . .  13
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   This document analyzes the pairwise Routing Protocol (RP)
   requirements needed to integrate the IKEv2[RFC5996] KMP and provides
   a framework to achieve this.

   The KARP design guide [RFC6518] suggests various requirements and
   options for obtaining keys to protect the routing protocols and
   recommends using a Key Management Protocol (KMP) to automate key
   establishment, as well as rekeying to continuously protect the
   routing protocols.  However, there are few gaps which need to be
   addressed for serene integration of IKEv2 KMP and any pairwise
   routing protocol either securing messages by RP itself or through a
   security protocol like TCP-AO [RFC5925].  For example, there are
   differences in both established protocols like IKEv2 and TCP-AO on
   how the Security Associations (SAs) to be maintained or there is a
   need for common framework in general on how the pairwise RPs can

[include full document text]