FYI, I have updated the use cases document.
Begin forwarded message: > From: [email protected] > Subject: New Version Notification for draft-barnes-jose-use-cases-01.txt > Date: October 22, 2012 12:01:35 PM EDT > To: [email protected] > > > A new version of I-D, draft-barnes-jose-use-cases-01.txt > has been successfully submitted by Richard Barnes and posted to the > IETF repository. > > Filename: draft-barnes-jose-use-cases > Revision: 01 > Title: Use Cases and Requirements for JSON Object Signing and > Encryption (JOSE) > Creation date: 2012-10-22 > WG ID: Individual Submission > Number of pages: 17 > URL: > http://www.ietf.org/internet-drafts/draft-barnes-jose-use-cases-01.txt > Status: http://datatracker.ietf.org/doc/draft-barnes-jose-use-cases > Htmlized: http://tools.ietf.org/html/draft-barnes-jose-use-cases-01 > Diff: > http://www.ietf.org/rfcdiff?url2=draft-barnes-jose-use-cases-01 > > 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. > > > > > The IETF Secretariat > _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
