datatracker.ietf.org
Sign In
Version 4.45, 2013-05-14
Report a bug

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

Active Internet-Draft (None)
Document Stream: No stream defined
Last updated: 2013-02-25
Intended RFC status: (None)
Other versions: plain text, pdf, html

Document shepherd:(None)
Shepherd writeup

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 29, 2013                                        J. Touch
                                                                 USC/ISI
                                                       February 25, 2013

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

Abstract

   This document describes a mechanism to secure pairwise Routing
   Protocol associations using the IKEv2 Key Management Protocol (KMP).
   Most of the pairwise Routing Protocols (RPs) are TCP-based but the
   framework described here is applicable to other pairwise RPs, which
   not necessarily use the TCP at transport layer.  A Gatekeeper
   mechanism is introduced to allow all pairwise RPs to coordinate with
   IKEv2 Protocol to pass the policy, get the keying material and to
   maintain the security associations.  The Gatekeeper also allows
   pairwise RPs which use TCP-AO to coordinate with IKEv2 without
   fundamental modification to either.

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 29, 2013.

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

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

   (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.  Requirements Language  . . . . . . . . . . . . . . . . . .  4
     1.2.  Acronyms . . . . . . . . . . . . . . . . . . . . . . . . .  4
   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 . . . . . . . . 10
       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

Chunduri, et al.         Expires August 29, 2013                [Page 2]
Internet-Draft    A framework for RPs to use IKEv2 KMP     February 2013

1.  Introduction

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

   The KARP design guide [RFC6518] suggests various requirements and