Algorithm Agility Procedure for RPKI.
draft-ietf-sidr-algorithm-agility-10

The information below is for an old version of the document
Document Type Active Internet-Draft (sidr WG)
Last updated 2013-01-10 (latest revision 2013-01-07)
Replaces draft-rgaglian-sidr-algorithm-agility
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Alexey Melnikov
Shepherd write-up Show (last changed 2012-11-07)
IESG IESG state IESG Evaluation
Consensus Boilerplate Unknown
Telechat date
Needs a YES. Needs 9 more YES or NO OBJECTION positions to pass.
Responsible AD Stewart Bryant
IESG note Alexey Melnikov (alexey.melnikov@isode.com) is the Document Shepherd.
Send notices to sidr-chairs@tools.ietf.org, draft-ietf-sidr-algorithm-agility@tools.ietf.org
Network Working Group                                        R. Gagliano
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                                 S. Kent
Expires: July 11, 2013                                  BBN Technologies
                                                               S. Turner
                                                              IECA, Inc.
                                                         January 7, 2013

                 Algorithm Agility Procedure for RPKI.
                  draft-ietf-sidr-algorithm-agility-10

Abstract

   This document specifies the process that Certification Authorities
   (CAs) and Relying Parties (RPs) participating in the Resource Public
   Key Infrastructure (RPKI) will need to follow to transition to a new
   (and probably cryptographically stronger) algorithm set.  The process
   is expected to be completed in a time scale of several years.
   Consequently, no emergency transition is specified.  The transition
   procedure defined in this document supports only a top-down migration
   (parent migrates before children).

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 July 11, 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
   (http://trustee.ietf.org/license-info) in effect on the date of

Gagliano, et al.          Expires July 11, 2013                 [Page 1]
Internet-Draft           RPKI Algorithm Agility             January 2013

   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.  Requirements notation  . . . . . . . . . . . . . . . . . . . .  3
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  6
   4.  Key Rollover steps for algorithm migration . . . . . . . . . .  8
     4.1.  Milestones definition  . . . . . . . . . . . . . . . . . .  8
     4.2.  Process overview . . . . . . . . . . . . . . . . . . . . .  8
     4.3.  Phase 0  . . . . . . . . . . . . . . . . . . . . . . . . . 10
       4.3.1.  Milestone 1  . . . . . . . . . . . . . . . . . . . . . 11
     4.4.  Phase 1  . . . . . . . . . . . . . . . . . . . . . . . . . 12
     4.5.  Phase 2  . . . . . . . . . . . . . . . . . . . . . . . . . 13
     4.6.  Phase 3  . . . . . . . . . . . . . . . . . . . . . . . . . 14
     4.7.  Phase 4  . . . . . . . . . . . . . . . . . . . . . . . . . 15
     4.8.  Return to Phase 0  . . . . . . . . . . . . . . . . . . . . 16
   5.  Multi Algorithm support in the RPKI provisioning protocol  . . 17
   6.  Validation of multiple instance of signed products . . . . . . 18
   7.  Revocation . . . . . . . . . . . . . . . . . . . . . . . . . . 19
   8.  Key rollover . . . . . . . . . . . . . . . . . . . . . . . . . 20
   9.  Repository structure . . . . . . . . . . . . . . . . . . . . . 21
   10. Deprecating an Algorithm Suite . . . . . . . . . . . . . . . . 22
   11. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 24
   12. Security Considerations  . . . . . . . . . . . . . . . . . . . 25
   13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 26
   14. Normative References . . . . . . . . . . . . . . . . . . . . . 27
   Appendix A.  Change Log  . . . . . . . . . . . . . . . . . . . . . 28
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31

Gagliano, et al.          Expires July 11, 2013                 [Page 2]
Internet-Draft           RPKI Algorithm Agility             January 2013

1.  Requirements notation

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