Automated Cryptographic Validation Protocol
draft-fussell-acvp-spec-00

Document Type Active Internet-Draft (individual)
Last updated 2019-02-21
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Internet Engineering Task Force                          B. Fussell, Ed.
Internet-Draft                                             Cisco Systems
Intended status: Informational                          A. Vassilev, Ed.
Expires: August 25, 2019                                        H. Booth
                          National Institute of Standards and Technology
                                                       February 21, 2019

              Automated Cryptographic Validation Protocol
                       draft-fussell-acvp-spec-00

Abstract

   The ACV Protocol provides a method for communication between a
   cryptographic module that is embedded inside of a device or otherwise
   running on a platform accessible via computer network, and an
   external testing system, using standard network communication
   interfaces and protocols.  This communication protocol can also be
   used to validate the correctness of the algorithm implementations in
   the cryptographic module with a validation authority.

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 25, 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
   (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

Fussell, et al.          Expires August 25, 2019                [Page 1]
Internet-Draft                ACV Protocol                 February 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Audience  . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Goals . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Server/Client Architecture(realtime)  . . . . . . . . . .   6
     4.2.  Server/Client Architecture(not realtime)  . . . . . . . .   7
     4.3.  Server/Proxy Architecture . . . . . . . . . . . . . . . .   7
     4.4.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  ACV Protocol  . . . . . . . . . . . . . . . . . . . . . . . .   9
     5.1.  HTTP URI Hierarchy  . . . . . . . . . . . . . . . . . . .  10
     5.2.  HTTP URI Resources  . . . . . . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
     6.1.  Authentication  . . . . . . . . . . . . . . . . . . . . .  13
   7.  Encoding  . . . . . . . . . . . . . . . . . . . . . . . . . .  14
   8.  Submission Size Considerations  . . . . . . . . . . . . . . .  14
   9.  Versioning  . . . . . . . . . . . . . . . . . . . . . . . . .  14
   10. Messaging and Workflow  . . . . . . . . . . . . . . . . . . .  14
     10.1.  Product Registration/Capabilities Exchange . . . . . . .  14
     10.2.  Test Exchange  . . . . . . . . . . . . . . . . . . . . .  14
     10.3.  JSON Web Token (JWT) . . . . . . . . . . . . . . . . . .  15
       10.3.1.  Authorization flows with JWT . . . . . . . . . . . .  15
       10.3.2.  JWT Expiration/Renewal . . . . . . . . . . . . . . .  16
     10.4.  Message Flow . . . . . . . . . . . . . . . . . . . . . .  17
     10.5.  Vendor Resources . . . . . . . . . . . . . . . . . . . .  18
       10.5.1.  Vendor Listing . . . . . . . . . . . . . . . . . . .  19
       10.5.2.  Create a New Vendor  . . . . . . . . . . . . . . . .  20
       10.5.3.  Vendor Information . . . . . . . . . . . . . . . . .  21
       10.5.4.  Update an existing Vendor  . . . . . . . . . . . . .  22
       10.5.5.  Remove a Vendor  . . . . . . . . . . . . . . . . . .  23
     10.6.  Modules  . . . . . . . . . . . . . . . . . . . . . . . .  23
       10.6.1.  List Modules . . . . . . . . . . . . . . . . . . . .  24
Show full document text