datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)
draft-barnes-jose-use-cases-02

Replaced Internet-Draft (None)
Document Stream: No stream defined
Last updated: 2013-02-25
Replaced by: draft-ietf-jose-use-cases
Intended RFC status: (None)
Other versions: (expired, archived): plain text, xml, pdf, html
Document shepherd:(None)
Shepherd writeup
IESG State: Replaced
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-barnes-jose-use-cases.

Abstract:
Many Internet applications have a need for object-based security mechanisms in addition to security mechanisms at the network layer or transport layer. In the past, the Cryptographic Message Syntax has provided a binary secure object format based on ASN.1. Over time, the use of binary object encodings such as ASN.1 has been overtaken by text-based encodings, for example JavaScript Object Notation. This document defines a set of use cases and requirements for a secure object format encoded using JavaScript Object Notation, drawn from a variety of application security mechanisms currently in development.

Authors:
Richard Barnes <rlb@ipv.sx>

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