Skip to content

Latest commit

 

History

History
188 lines (141 loc) · 5.06 KB

draft-ietf-lamps-im-keyusage.md

File metadata and controls

188 lines (141 loc) · 5.06 KB
Raw

title: "X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIs" abbrev: "extendedKeyUsage for IM URIs" category: std

docname: draft-ietf-lamps-im-keyusage-latest submissiontype: IETF # also: "independent", "editorial", "IAB", or "IRTF" number: date: consensus: true v: 3 area: SEC workgroup: LAMPS WG keyword:

author:

fullname: Rohan Mahy
organization: Rohan Mahy Consulting Services
email: [email protected]

normative: ITU.X690.2021: title: > Information Technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER) author: org: International Telecommunications Union date: 2021 seriesinfo: ITU-T: Recommendation X.690

ITU.X680.2021: title: > Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation author: org: International Telecommunications Union date: 2021 seriesinfo: ITU-T: Recommendation X.680

informative:

--- abstract

RFC 5280 specifies several extended key purpose identifiers (KeyPurposeIds) for X.509 certificates. This document defines Instant Messaging (IM) identity KeyPurposeId for inclusion in the Extended Key Usage (EKU) extension of X.509 v3 public key certificates

--- middle

Introduction

Instant Messaging (IM) systems using the Messaging Layer Security (MLS) {{?RFC9420}} protocol can incorporate per-client identity certificate credentials. A subjectAltName in these certificates can be an IM URI {{?RFC3860}} or XMPP URI {{?RFC6121}}, for example.

Organizations may be unwilling to issue certificates for Instant Message client using a general KeyPurposeId such as id-kp-serverAuth or id-kp-clientAuth, because of the risk that such certificates could be abused in a cross-protocol attack.

An explanation of MLS credentials as they apply to Instant Messaging is described in {{?I-D.barnes-mimi-identity-arch}}. These credentials are expected to be heavily used in the More Instant Messaging Interoperability (MIMI) Working Group.

Conventions and Definitions

{::boilerplate bcp14-tagged}

The IM URI Extended Key Usage

This specification defines the KeyPurposeId id-kp-imUri, which may be included in certificates used to prove the identity of an Instant Messaging client. This EKU extension MAY, at the option of the certificate issuer, be either critical or non-critical.

id-kp  OBJECT IDENTIFIER  ::= {
  iso(1) identified-organization(3) dod(6) internet(1)
  security(5) mechanisms(5) pkix(7) kp(3) }

id-kp-imUri OBJECT IDENTIFIER ::= { id-kp TBD1 }

Security Considerations

The Security Considerations of {{!RFC5280}} are applicable to this document. This extended key purpose does not introduce new security risks but instead reduces existing security risks by providing means to identify if the certificate is generated to sign IM identity credentials. Issuers SHOULD NOT set the id-kp-imUri extended key purpose and an id-kp-clientAuth or id-kp-serverAuth extended key purpose, as that would defeat the improved specificity offered by having an id-kp-imUri extended key purpose.

IANA Considerations

IANA is requested to register the following OIDs in the "SMI Security for PKIX Extended Key Purpose" registry (1.3.6.1.5.5.7.3). These OIDs are defined in Section 4.

Decimal Description References
TBD1 id-kp-imUri This-RFC

IANA is also requested to register the following ASN.1 {{ITU.X690.2021}} module OID in the "SMI Security for PKIX Module Identifier" registry (1.3.6.1.5.5.7.0). This OID is defined in {{asn1-module}}.

Decimal Description References
TBD2 id-mod-im-eku This-RFC

--- back

ASN.1 Module {#asn1-module}

The following module adheres to ASN.1 specifications {{ITU.X680.2021}} and {{ITU.X690.2021}}.

<CODE BEGINS>

IM-EKU
  { iso(1) identified-organization(3) dod(6) internet(1)
  security(5) mechanisms(5) pkix(7) id-mod(0)
  id-mod-im-eku (TBD2) }

DEFINITIONS IMPLICIT TAGS ::=
BEGIN

-- OID Arc

id-kp OBJECT IDENTIFIER ::=
  { iso(1) identified-organization(3) dod(6) internet(1)
    security(5) mechanisms(5) pkix(7) kp(3) }

-- Extended Key Usage Values

id-kp-imUri OBJECT IDENTIFIER ::= { id-kp TBD1 }

END


<CODE ENDS>

Change log

RFC Editor, please remove this section on publication.

  • made Proposed Standard
  • added a MAY statement in Section 3
  • corrected typo in registration of the ASN.1 module (Thanks Sean!)
  • updated author affiliation
  • added ASN.1 module
  • specified that eku is optionally critical

Acknowledgments

{:numbered="false"}

Thanks to Sean Turner and Russ Housley for reviews, suggestions, corrections, and encouragement.