Concise Identities
draft-birkholz-core-coid-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-02
Stream (None)
Intended RFC status (None)
Formats plain text 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)
CoRE Working Group                                           H. Birkholz
Internet-Draft                                            Fraunhofer SIT
Intended status: Informational                                C. Bormann
Expires: January 2, 2019                         Universitaet Bremen TZI
                                                             M. Pritikin
                                                                   Cisco
                                                            R. Moskowitz
                                                                  Huawei
                                                           July 01, 2018

                           Concise Identities
                      draft-birkholz-core-coid-00

Abstract

   There is an increased demand of trustworthy claim sets -- a set of
   system entity characteristics tied to an entity via signatures -- in
   order to provide information.  Claim sets represented via CBOR Web
   Tokens (CWT) can compose a variety of evidence suitable for
   constrained-node networks and to support secure device automation.
   This document focuses on sets of identifiers and attributes that are
   tied to a system entity and are typically used to compose identities
   appropriate for Constrained RESTful Environment (CoRE) authentication
   needs.

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 https://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 January 2, 2019.

Copyright Notice

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

Birkholz, et al.         Expires January 2, 2019                [Page 1]
Internet-Draft                    CoID                         July 2018

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://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.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Claims in a Concise Identity  . . . . . . . . . . . . . . . .   4
     2.1.  iss: CWT issuer . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  sub: CWT subject  . . . . . . . . . . . . . . . . . . . .   5
     2.3.  aud: CWT audience . . . . . . . . . . . . . . . . . . . .   5
     2.4.  exp: CWT expiration time  . . . . . . . . . . . . . . . .   5
     2.5.  nbf: CWT start of validity  . . . . . . . . . . . . . . .   5
     2.6.  iat: CWT time of issue  . . . . . . . . . . . . . . . . .   5
     2.7.  cti: CWT ID . . . . . . . . . . . . . . . . . . . . . . .   5
     2.8.  cnf: CWT proof-of-possession key claim  . . . . . . . . .   5
   3.  Signature Envelope  . . . . . . . . . . . . . . . . . . . . .   5
   4.  Processing Rules  . . . . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Appendix A.  Examples of claims taken from IEEE 802.1AR
                identifiers  . . . . . . . . . . . . . . . . . . . .   7
     A.1.  7.2.1 version . . . . . . . . . . . . . . . . . . . . . .   8
     A.2.  7.2.2 serialNumber  . . . . . . . . . . . . . . . . . . .   8
     A.3.  7.2.3 signature . . . . . . . . . . . . . . . . . . . . .   8
     A.4.  7.2.4 issuer Name . . . . . . . . . . . . . . . . . . . .   8
     A.5.  7.2.5 authoritykeyidentifier  . . . . . . . . . . . . . .   8
     A.6.  7.2.7.1 notBefore . . . . . . . . . . . . . . . . . . . .   8
     A.7.  7.2.7.2 notAfter  . . . . . . . . . . . . . . . . . . . .   8
     A.8.  7.2.8 subject . . . . . . . . . . . . . . . . . . . . . .   9
     A.9.  7.2.10 subjectPublicKeyInfo . . . . . . . . . . . . . . .   9
Show full document text