Implementing Company Classification Policy with the S/MIME Security Label
draft-ietf-smime-seclabel-04
The information below is for an old version of the document that is already published as an RFC.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 3114.
|
|
---|---|---|---|
Author | Weston Nicolls | ||
Last updated | 2013-03-02 (Latest revision 2001-05-08) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Informational | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | (None) | |
Document shepherd | (None) | ||
IESG | IESG state | Became RFC 3114 (Informational) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Steven M. Bellovin | ||
Send notices to | <turners@ieca.com>, <blake@brutesquadlabs.com> |
draft-ietf-smime-seclabel-04
A new Request for Comments is now available in online RFC libraries. RFC 3114 Title: Implementing Company Classification Policy with the S/MIME Security Label Author(s): W. Nicolls Status: Informational Date: May 2002 Mailbox: wnicolls@forsythesolutions.com Pages: 14 Characters: 27764 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-smime-seclabel-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3114.txt This document discusses how company security policy for data classification can be mapped to the S/MIME security label. Actual policies from three companies provide worked examples. This document is a product of the S/MIME Mail Security Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.