< draft-ietf-lamps-5480-ku-clarifications-01.txt   draft-ietf-lamps-5480-ku-clarifications-02.txt >
LAMPS T. Ito LAMPS T. Ito
Internet-Draft SECOM CO., LTD. Internet-Draft SECOM CO., LTD.
Updates: 5480 (if approved) S. Turner Updates: 5480 (if approved) S. Turner
Intended status: Standards Track sn3rd Intended status: Standards Track sn3rd
Expires: August 25, 2020 February 25, 2020 Expires: August 28, 2020 February 28, 2020
Clarifications for Elliptic Curve Cryptogtaphy Subject Public Key Clarifications for Elliptic Curve Cryptogtaphy Subject Public Key
Information Information
draft-ietf-lamps-5480-ku-clarifications-01 draft-ietf-lamps-5480-ku-clarifications-02
Abstract Abstract
This document updates RFC 5480 to specify semantics for the This document updates RFC 5480 to specify semantics for the
keyEncipherment and dataEncipherment key usage bits when used in keyEncipherment and dataEncipherment key usage bits when used in
certificates that support Elliptic Curve Cryptography. certificates that support Elliptic Curve Cryptography.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 26, 2020. This Internet-Draft will expire on August 28, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 25 skipping to change at page 2, line 25
1. Introduction 1. Introduction
[RFC5480] specifies the syntax and semantics for the Subject Public [RFC5480] specifies the syntax and semantics for the Subject Public
Key Information field in certificates that support Elliptic Curve Key Information field in certificates that support Elliptic Curve
Cryptography. As part of these semantics, it defines what Cryptography. As part of these semantics, it defines what
combinations are permissible for the values of the key usage combinations are permissible for the values of the key usage
extensions [RFC5280]. [RFC5480] specifies 7 of the 9 values; it extensions [RFC5280]. [RFC5480] specifies 7 of the 9 values; it
makes no mention of keyEncipherment and dataEncipherment key usage makes no mention of keyEncipherment and dataEncipherment key usage
bits. This document corrects this omission, by updating Section 3 of bits. This document corrects this omission, by updating Section 3 of
[RFC5480] to make it clear that neither keyEncipherment nor the [RFC5480] to make it clear that neither keyEncipherment nor the
dataEncipherment key usage bits are set for key agreement algorithms. dataEncipherment key usage bits are set for key agreement algorithms
defined therein. The additions are to be made to the end of
Section 3.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. Updates to Section 3 3. Updates to Section 3
If the keyUsage extension is present in a certificate that indicates If the keyUsage extension is present in a certificate that indicates
in SubjectPublicKeyInfo, then following values MUST NOT be present: id-ecPublicKey in SubjectPublicKeyInfo, then following values MUST
NOT be present:
keyEncipherment; and keyEncipherment; and
dataEncipherment. dataEncipherment.
If the keyUsage extension is present in a certificate that indicates If the keyUsage extension is present in a certificate that indicates
id-ecDH or id-ecMQV in SubjectPublicKeyInfo, then the following id-ecDH or id-ecMQV in SubjectPublicKeyInfo, then the following
values also MUST NOT be present: values also MUST NOT be present:
keyEncipherment; and keyEncipherment; and
dataEncipherment. dataEncipherment.
 End of changes. 5 change blocks. 
5 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/