RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 2633, "S/MIME Version 3 Message Specification", June 1999

Note: This RFC has been obsoleted by RFC 3851

Source of RFC: smime (sec)

Errata ID: 405

Status: Verified
Type: Technical

Reported By: Joni Yrjana
Date Reported: 2003-03-12

Section 3.5 says:

   This may be useful in an environment were automatic signature
   verification is desired, as no private key material is required to
   verify a signature.

It should say:

   This may be useful in an environment where automatic signature
   verification is desired, as no private key material is required to
   verify a signature.

Status: Reported (1)

RFC 2633, "S/MIME Version 3 Message Specification", June 1999

Note: This RFC has been obsoleted by RFC 3851

Source of RFC: smime (sec)

Errata ID: 5019

Status: Reported
Type: Technical

Reported By: Josh Soref
Date Reported: 2017-05-14

Section 5 says:

id-aa-encrypKeyPref OBJECT IDENTIFIER ::= {id-aa 11}

It should say:

id-aa-encrypKeyPref [sic] OBJECT IDENTIFIER ::= {id-aa 11}

Notes:

encryp isn't a word, it's a typo. Unfortunately, like http's (rfc1945) referer [sic] before it, this is now part of the API.

This error should be highlighted (as rfc2068 does for referer [sic]) so that people are aware that the natural spelling doesn't apply.

If it's possible for a revised RFC to be published suggesting the correct spelling w/ a way for clients/servers to handle the old spelling, that would be nice, but based on precedent, that seems unlikely.

Report New Errata



Search RFCs
Advanced Search
×