Internet Engineering Task Force V. Breitmoser
Internet-Draft
Updates: 4880 (if approved) May 5, 2015
Intended status: Standards Track
Expires: November 6, 2015
URI Attributes for OpenPGP
draft-vb-openpgp-uri-attribute-01
Abstract
This specification extends OpenPGP with the URI Attribute as a new
type of User Attribute.
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 November 6, 2015.
Copyright Notice
Copyright (c) 2015 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
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.
Breitmoser Expires November 6, 2015 [Page 1]
Internet-Draft URI Attributes for OpenPGP May 2015
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Conventions Used in This Document . . . . . . . . . . . . 2
2. URI User Attribute subpacket . . . . . . . . . . . . . . . . 2
3. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 3
6. Normative References . . . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
The OpenPGP specification [RFC4880] allows primary keys to associate
themselves with identities in the form of User ID and User Attribute
packets. The only defined type of User Attribute is JPEG. This
document introduces the URI subpacket as an additional type of User
Attribute subpacket.
1.1. Scope
Similar to RFC 4880, the scope of this document is limited to a
technical description of the format, and does not include specifics
on how URI Attributes may be used by implementations.
1.2. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. Any
implementation that adheres to the format and methods specified in
this document is called a compliant application. Compliant
applications are a subset of the broader set of OpenPGP applications
described in [RFC4880]. Any [RFC2119] keyword within this document
applies to compliant applications only.
2. URI User Attribute subpacket
The URI subpacket is added as an additional User Attribute subpacket
with type id [TBD] to expand Section 5.12 of the OpenPGP
specification [RFC4880], "User Attribute Packet (Tag 17)". The body
of this subpacket consists of a single UTF-8 encoded URI string. A
URI Attribute is a User Attribute packet with a single URI subpacket.
The purpose of this packet type is to provide a mechanism for
associating the key with an identity encoded in a URI. The
Breitmoser Expires November 6, 2015 [Page 2]
Internet-Draft URI Attributes for OpenPGP May 2015
particular semantics of a URI depend on its scheme, there are no
restrictions on the URIs which may appear in URI Attributes.
An implementation SHOULD NOT issue certificates for URI Attributes
with unknown URI schemes. It MAY treat such packets as opaque, or
display their contents in a generic way.
3. Compatibility
An implementation SHOULD NOT use a URI Attribute to fulfill the
minimum requirement of one User ID packet in a transferable key.
This is to ensure that at least one non-opaque type of user id is
part of every key.
4. IANA Considerations
IANA is requested to assign a number to the URI User Attribute
subpacket, updating the User Attribute Type namespace established in
[RFC4880]. See Section 2.
+------+---------------------+-----------+
| ID | User Attribute Type | Reference |
+------+---------------------+-----------+
| TBD1 | URI | This doc |
+------+---------------------+-----------+
[Notes to RFC-Editor: Please remove the table above on publication.
There are no non-standardized types used in current implementations
known to the author. As of now 2 is the next free number.]
5. Security Considerations
The security considerations of the URI Attribute are the same as for
other identity packets, leaving the considerations from [RFC4880]
unchanged.
6. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4880] Callas, J., Donnerhacke, L., Finney, H., Shaw, D., and R.
Thayer, "OpenPGP Message Format", RFC 4880, November 2007.
Breitmoser Expires November 6, 2015 [Page 3]
Internet-Draft URI Attributes for OpenPGP May 2015
Author's Address
Vincent Breitmoser
Braunschweig
DE
Email: v.breitmoser@my.amazin.horse
Breitmoser Expires November 6, 2015 [Page 4]