Secure Object Delivery Protocol (SODP)
draft-turner-sodp-02

Document Type Expired Internet-Draft (individual)
Last updated 2012-07-13 (latest revision 2012-01-10)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-turner-sodp-02.txt

Abstract

This document describes the Secure Object Delivery Protocol (SODP). SODP enables clients to obtain secured packages from a Secure Object Management System (SOMS). Packages supported by a SOMS server include but are not limited to: firmware packages [RFC4108], trust anchor (TA) packages [RFC5934], symmetric key packages [RFC6031], asymmetric key packages [RFC5958], encrypted key packages [RFC6031], public key certificate enrollment packages [RFC5272], public key certificates [RFC5280], and Certificate Revocation Lists (CRLs) [RFC5280]. Client access is ideally direct and web-based, but access via agents acting on behalf of clients is supported.

Authors

Sean Turner (turners@ieca.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)