ietf-smime
[Top] [All Lists]

{Blocked Content} RFC 4262 on X.509 Certificate Extension for Secure/Multipurpose Internet Mail Extensions (S/MIME) Capabilities

2005-12-16 18:28:21
Warning: This message has had one or more attachments removed
Warning: (not named).
Warning: Please read the "mallorn-Attachment-Warning.txt" attachment(s) for 
more information.


A new Request for Comments is now available in online RFC libraries.


        RFC 4262

        Title:      X.509 Certificate Extension for
                    Secure/Multipurpose Internet Mail Extensions
                    (S/MIME) Capabilities
        Author(s):  S. Santesson
        Status:     Standards Track
        Date:       December 2005
        Mailbox:    stefans(_at_)microsoft(_dot_)com
        Pages:      5
        Characters: 9801
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-smime-certcapa-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4262.txt


This document defines a certificate extension for inclusion of
Secure/Multipurpose Internet Mail Extensions (S/MIME)
Capabilities in X.509 public key certificates, as defined by RFC
3280.  This certificate extension provides an optional method to
indicate the cryptographic capabilities of an entity as a complement
to the S/MIME Capabilities signed attribute in S/MIME messages
according to RFC 3851.

This document is a product of the S/MIME Mail Security Working Group
of the IETF.  

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST(_at_)IETF(_dot_)ORG(_dot_)  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST(_at_)RFC-EDITOR(_dot_)ORG(_dot_)

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info(_at_)RFC-EDITOR(_dot_)ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info(_at_)RFC-EDITOR(_dot_)ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to 
RFC-Manager(_at_)RFC-EDITOR(_dot_)ORG(_dot_)  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR(_at_)RFC-EDITOR(_dot_)ORG(_dot_)  Please consult RFC 2223, 
Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
This is a message from the MailScanner E-Mail Virus Protection Service
----------------------------------------------------------------------
The original e-mail attachment "not named"
was believed to be infected by a virus and has been replaced by this warning
message.

If you wish to receive a copy of the *infected* attachment, please
e-mail helpdesk and include the whole of this message
in your request. Alternatively, you can call them, with
the contents of this message to hand when you call.

At Fri Dec 16 19:28:26 2005 the virus scanner said:
   External message bodies cannot be scanned and are removed

Note to Help Desk: Look on the mallorn MailScanner in 
/mnt/Logs/MailScanner/quarantine/20051216 (message jBH1SLh30392).
-- 
Postmaster
MailScanner thanks transtec Computers for their support
This is a message from the MailScanner E-Mail Virus Protection Service
----------------------------------------------------------------------
The original e-mail attachment "not named"
was believed to be infected by a virus and has been replaced by this warning
message.

If you wish to receive a copy of the *infected* attachment, please
e-mail helpdesk and include the whole of this message
in your request. Alternatively, you can call them, with
the contents of this message to hand when you call.

At Fri Dec 16 19:28:26 2005 the virus scanner said:
   External message bodies cannot be scanned and are removed

Note to Help Desk: Look on the mallorn MailScanner in 
/mnt/Logs/MailScanner/quarantine/20051216 (message jBH1SLh30392).
-- 
Postmaster
MailScanner thanks transtec Computers for their support
<Prev in Thread] Current Thread [Next in Thread>
  • {Blocked Content} RFC 4262 on X.509 Certificate Extension for Secure/Multipurpose Internet Mail Extensions (S/MIME) Capabilities, rfc-editor <=