RFC 6376, "DomainKeys Identified Mail (DKIM) Signatures", September 2011

Note: This RFC has been updated by RFC 8301, RFC 8463, RFC 8553, RFC 8616

Errata ID: 3017
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Vernon Tang
Date Reported: 2011-11-05
Held for Document Update by: Barry Leiba
Date Held: 2019-04-30

Section 3.6.1 says:

   k= Key type (plain-text; OPTIONAL, default is "rsa").  Signers and
      Verifiers MUST support the "rsa" key type.  The "rsa" key type
      indicates that an ASN.1 DER-encoded [ITU-X660-1997] RSAPublicKey
      (see [RFC3447], Sections 3.1 and A.1.1) is being used in the "p="
      tag.  (Note: the "p=" tag further encodes the value using the
      base64 algorithm.)  Unrecognized key types MUST be ignored.

It should say:

   k= Key type (plain-text; OPTIONAL, default is "rsa").  Signers and
      Verifiers MUST support the "rsa" key type.  The "rsa" key type
      indicates that an ASN.1 DER-encoded [ITU-X660-1997] RSAPublicKey
      (see [RFC3447], Sections 3.1 and A.1.1), which MAY be contained in
      a SubjectPublicKeyInfo (see [RFC5280], Section A.1), is being used
      in the "p=" tag.  (Note: the "p=" tag further encodes the value
      using the base64 algorithm.)  Unrecognized key types MUST be
      ignored.

Notes:

The procedure in Appendix C results in a public key in SubjectPublicKeyInfo format. Accordingly, most current implementations will accept such keys. Furthermore, it is trivial to distinguish whether a key is encapsulated in a SubjectPublicKeyInfo.

Report New Errata