Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate Handling
RFC 3850
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2015-10-14 |
07 | (System) | Notify list changed from turners@ieca.com, blake@sendmail.com to turners@ieca.com |
2012-08-22 |
07 | (System) | post-migration administrative database adjustment to the No Objection position for Scott Hollenbeck |
2009-05-27 |
(System) | Posted related IPR disclosure: Certicom's Statement about IPR related to draft-ietf-tls-rfc4347-bis, draft-rescorla-tls-suiteb, draft-ietf-tls-extractor, draft-green-secsh-ecc, draft-ietf-avt-dtls-srtp, draft-igoe-secsh-suiteb, draft-ietf-smime-3851bis, draft-ietf-smime-3850bis, dra... | |
2009-05-18 |
(System) | Posted related IPR disclosure: Certicom's Statement about IPR related to draft-ietf-smime-3278bis, draft-ietf-smime-sha2, draft-ietf-smime-multisig, draft-ietf-smime-3850bis, draft-ietf-smime-3851bis, draft-igoe-secsh-suiteb, draft-ietf-avt-dtls-srtp, draft-green-secsh-ecc, draft-ie... | |
2008-10-30 |
(System) | Posted related IPR disclosure: Certicom's Statement about IPR related to RFC 4346, RFC 5246, RFC 5289, RFC 4492, RFC 2409, RFC 4306, RFC 4754, RFC … Posted related IPR disclosure: Certicom's Statement about IPR related to RFC 4346, RFC 5246, RFC 5289, RFC 4492, RFC 2409, RFC 4306, RFC 4754, RFC 4753, RFC 4869, RFC 4253, RFC 2633, RFC 3278, RFC 4347, RFC 4366, RFC 4109, RFC 4252, RFC 3850, RFC 3851, RFC 5008, draft-ietf-tls-rfc43... |
|
2004-07-23 |
07 | Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
2004-07-23 |
07 | Amy Vezza | [Note]: 'RFC 3850' added by Amy Vezza |
2004-07-21 |
07 | (System) | RFC published |
2004-06-15 |
07 | Amy Vezza | State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza |
2004-06-14 |
07 | Amy Vezza | IESG state changed to Approved-announcement sent |
2004-06-14 |
07 | Amy Vezza | IESG has approved the document |
2004-06-14 |
07 | Amy Vezza | Closed "Approve" ballot |
2004-06-11 |
07 | (System) | Removed from agenda for telechat - 2004-06-10 |
2004-06-10 |
07 | Amy Vezza | State Changes to Approved-announcement to be sent from IESG Evaluation by Amy Vezza |
2004-06-10 |
07 | Amy Vezza | [Ballot Position Update] New position, No Objection, has been recorded for Harald Alvestrand by Amy Vezza |
2004-06-10 |
07 | Thomas Narten | [Ballot Position Update] New position, No Objection, has been recorded for Thomas Narten by Thomas Narten |
2004-06-10 |
07 | Margaret Cullen | [Ballot Position Update] New position, No Objection, has been recorded for Margaret Wasserman by Margaret Wasserman |
2004-06-10 |
07 | Allison Mankin | [Ballot Position Update] New position, No Objection, has been recorded for Allison Mankin by Allison Mankin |
2004-06-10 |
07 | David Kessens | [Ballot Position Update] New position, No Objection, has been recorded for David Kessens by David Kessens |
2004-06-10 |
07 | Bert Wijnen | [Ballot comment] No IPR section. I assume RFC-Editor will add it. |
2004-06-10 |
07 | Bert Wijnen | [Ballot Position Update] Position for Bert Wijnen has been changed to No Objection from Undefined by Bert Wijnen |
2004-06-10 |
07 | Bert Wijnen | [Ballot comment] No IPR section |
2004-06-10 |
07 | Bert Wijnen | [Ballot Position Update] New position, Undefined, has been recorded for Bert Wijnen by Bert Wijnen |
2004-06-10 |
07 | Scott Hollenbeck | [Ballot Position Update] Position for Scott Hollenbeck has been changed to No Objection from Discuss by Scott Hollenbeck |
2004-06-10 |
07 | Jon Peterson | [Ballot comment] In Section 3 (2nd paragraph), I'm a little confused by the text that says receiving implementations MUST "recognize and accept" certificates that contain … [Ballot comment] In Section 3 (2nd paragraph), I'm a little confused by the text that says receiving implementations MUST "recognize and accept" certificates that contain no email address. What asssurance are such certificates providing in the mail context? How are they processed? Given the importance placed on matching the subjectAltName with the From header field of an email in later paragraphs, I found the lack of procedures for this case a little odd. |
2004-06-10 |
07 | Jon Peterson | [Ballot Position Update] New position, No Objection, has been recorded for Jon Peterson by Jon Peterson |
2004-06-10 |
07 | Bill Fenner | [Ballot Position Update] New position, No Objection, has been recorded for Bill Fenner by Bill Fenner |
2004-06-09 |
07 | Steven Bellovin | [Ballot comment] - |
2004-06-09 |
07 | Alex Zinin | [Ballot Position Update] New position, No Objection, has been recorded for Alex Zinin by Alex Zinin |
2004-06-08 |
07 | Ted Hardie | [Ballot Position Update] New position, No Objection, has been recorded for Ted Hardie by Ted Hardie |
2004-06-08 |
07 | Steven Bellovin | [Ballot Position Update] Position for Steve Bellovin has been changed to No Objection from Undefined by Steve Bellovin |
2004-06-08 |
07 | Steven Bellovin | [Ballot comment] Does Section 3, which among other things talks about comparing email addresses, raise any internationalization issues? |
2004-06-08 |
07 | Steven Bellovin | [Ballot Position Update] New position, Undefined, has been recorded for Steve Bellovin by Steve Bellovin |
2004-06-08 |
07 | Scott Hollenbeck | [Ballot discuss] This document uses ASN.1 data structures (such as SEQUENCE in section 3, CHOICE in section 4.4.3) to describe MUSTs, but it doesn't include … [Ballot discuss] This document uses ASN.1 data structures (such as SEQUENCE in section 3, CHOICE in section 4.4.3) to describe MUSTs, but it doesn't include a normative reference to ITU-T X.208. |
2004-06-08 |
07 | Scott Hollenbeck | [Ballot comment] "BER" and "DER" are included in the list of definitions in section 1.1, but they're not used anywhere in the document that I … [Ballot comment] "BER" and "DER" are included in the list of definitions in section 1.1, but they're not used anywhere in the document that I could find. They should probably be removed. |
2004-06-08 |
07 | Scott Hollenbeck | [Ballot discuss] This document uses ASN.1 data structures (such as SEQUENCE in section 3, CHOICE in section 4.4.3) to describe MUSTs, but it doesn't include … [Ballot discuss] This document uses ASN.1 data structures (such as SEQUENCE in section 3, CHOICE in section 4.4.3) to describe MUSTs, but it doesn't include a normative references to ITU-T X.208. |
2004-06-08 |
07 | Scott Hollenbeck | [Ballot Position Update] New position, Discuss, has been recorded for Scott Hollenbeck by Scott Hollenbeck |
2004-06-08 |
07 | Russ Housley | [Ballot Position Update] New position, Yes, has been recorded for Russ Housley |
2004-06-08 |
07 | Russ Housley | Ballot has been issued by Russ Housley |
2004-06-08 |
07 | Russ Housley | Created "Approve" ballot |
2004-06-04 |
07 | Russ Housley | Placed on agenda for telechat - 2004-06-10 by Russ Housley |
2004-06-04 |
07 | Russ Housley | State Changes to IESG Evaluation from Waiting for AD Go-Ahead by Russ Housley |
2004-06-04 |
07 | (System) | New version available: draft-ietf-smime-rfc2632bis-07.txt |
2004-06-02 |
07 | (System) | State has been changed to Waiting for AD Go-Ahead from In Last Call by system |
2004-05-21 |
07 | Michelle Cotton | IANA Last Call Comments: We understand there to be no IANA Actions. |
2004-05-19 |
07 | Amy Vezza | Last call sent |
2004-05-19 |
07 | Amy Vezza | State Changes to In Last Call from Last Call Requested by Amy Vezza |
2004-05-19 |
07 | Russ Housley | Last Call was requested by Russ Housley |
2004-05-19 |
07 | Russ Housley | State Changes to Last Call Requested from Publication Requested by Russ Housley |
2004-05-19 |
07 | (System) | Ballot writeup text was added |
2004-05-19 |
07 | (System) | Last call text was added |
2004-05-19 |
07 | (System) | Ballot approval text was added |
2004-05-19 |
07 | Russ Housley | Draft Added by Russ Housley |
2004-05-10 |
06 | (System) | New version available: draft-ietf-smime-rfc2632bis-06.txt |
2004-02-16 |
05 | (System) | New version available: draft-ietf-smime-rfc2632bis-05.txt |
2003-10-27 |
04 | (System) | New version available: draft-ietf-smime-rfc2632bis-04.txt |
2003-02-20 |
03 | (System) | New version available: draft-ietf-smime-rfc2632bis-03.txt |
2002-11-04 |
02 | (System) | New version available: draft-ietf-smime-rfc2632bis-02.txt |
2002-07-03 |
01 | (System) | New version available: draft-ietf-smime-rfc2632bis-01.txt |
2002-02-11 |
00 | (System) | New version available: draft-ietf-smime-rfc2632bis-00.txt |