Plasma Service Trust Processing
draft-schaad-plasma-service-05
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Jim Schaad | ||
| Last updated | 2014-08-18 (Latest revision 2014-02-14) | ||
| Replaces | draft-schaad-eps-trust | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-schaad-plasma-service-05.txt
Abstract
RFC TBD describes a new model and set of requirements to implement a labeling system on Cryptographic Message Syntax (CMS) objects where the entity in charge of doing the label enforcement is under the control of a central authority rather than the recipient of the object. This document describes a protocol to be used by senders and recipients of CMS objects to communicate with a centralized label enforcement server. The document outlines how a client will get the set of labels or policies that it can use for sending messages, composes a secure CMS object with a label on it and gets the necessary keys to decrypt a CMS object from the server. This document is designed to be used with RFC TBD2 which describes the extensions used in CMS objects to hold the label information.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)