RFC 3114: Implementing Company Classification Policy with the S/MIME Security Label
In plain English — editorial summary, not part of the RFC
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 memo provides information for the Internet community.
Document record
- Document ID
- RFC3114
- Published
- May 2002
- Authors
- W. Nicolls
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1767MIME Encapsulation of EDI ObjectsCurrent
March 1995
- RFC 3126Electronic Signature Formats for long term electronic signaturesObsoleted
September 2001
- RFC 3185Reuse of CMS Content Encryption KeysCurrent
October 2001
- RFC 2785Methods for Avoiding the "Small-Subgroup" Attacks on the Diffie-Hellman Key Agreement Method for S/MIMECurrent
March 2000
- RFC 2633S/MIME Version 3 Message SpecificationObsoleted
June 1999
- RFC 2632S/MIME Version 3 Certificate HandlingObsoleted
June 1999
- RFC 2479Independent Data Unit Protection Generic Security Service Application Program Interface (IDUP-GSS-API)Current
December 1998
- RFC 2078Generic Security Service Application Program Interface, Version 2Obsoleted
January 1997
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?