OpenPGP Extensions for Device Certificates
draft-atkins-openpgp-device-certificates-04

Document Type Active Internet-Draft (individual)
Last updated 2019-04-10
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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                                D. Atkins
Internet-Draft                                      SecureRF Corporation
Updates: 4880 (if approved)                               April 10, 2019
Intended status: Standards Track
Expires: October 12, 2019

               OpenPGP Extensions for Device Certificates
              draft-atkins-openpgp-device-certificates-04

Abstract

   The OpenPGP Message Formats defined in RFC 4880 specify packet
   formats and methods for combining those packets to form messages and
   certificates.  However RFC 4880 made an architectural decision that
   keys are owned by users and must be self-certified.  New use cases
   have emerged where that is not the case.  There is a desire to have
   certificates that are not tied to a user (e.g. device certificates)
   which may only have encryption keys so may not be self certifiable.
   Moreover, devices might be space constrained so reducing size is
   important.  This draft specifies extensions to (and updates) RFC 4880
   that loosen the definitions of certificates in order to enable
   userless certificates without self-certifications and specifies a set
   of notations to enable compact device certifications.

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 October 12, 2019.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Atkins                  Expires October 12, 2019                [Page 1]
Internet-Draft         OpenPGP Device Certificates            April 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Device Certificate Format . . . . . . . . . . . . . . . . . .   3
   3.  User ID Attribute Subpacket . . . . . . . . . . . . . . . . .   4
   4.  Device Certification Notations  . . . . . . . . . . . . . . .   4
     4.1.  The 'manu' Notation . . . . . . . . . . . . . . . . . . .   5
     4.2.  The 'make' Notation . . . . . . . . . . . . . . . . . . .   5
     4.3.  The 'model' Notation  . . . . . . . . . . . . . . . . . .   5
     4.4.  The 'prodid' Notation . . . . . . . . . . . . . . . . . .   5
     4.5.  The 'pvers' Notation  . . . . . . . . . . . . . . . . . .   5
     4.6.  The 'lot' Notation  . . . . . . . . . . . . . . . . . . .   5
     4.7.  The 'qty' Notation  . . . . . . . . . . . . . . . . . . .   5
     4.8.  The 'loc' and 'dest' Notations  . . . . . . . . . . . . .   5
     4.9.  The 'hash' Notation . . . . . . . . . . . . . . . . . . .   6
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  PGP User Attribute Types  . . . . . . . . . . . . . . . .   6
     6.2.  Signature Notation Data Subpacket Types . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   OpenPGP [RFC4880] defines a standard, compact format for, among other
   things, sharing keys and signature certificates.  Unfortunately the
   specification is user-focused, assuming that there are people sitting
   at the ends and creating and managing those keys.  New use cases have
   come up where that is not the case and the endpoint for these keys
   are devices, not users.  Yet we still want to be able to certify
   these device keys.

   Since the publication of RFC 4880, new use cases have emerged that
Show full document text