Eric An example or commentary explaining going from a JSON message to signing would be useful.
I read over the document twice and I cannot figure out how it all fits together. -- Dick On 2011-03-09, at 2:10 PM, Peter Saint-Andre wrote: > FYI. > > -------- Original Message -------- > Subject: I-D Action:draft-rescorla-jsms-00.txt > Date: Mon, 07 Mar 2011 15:30:03 -0800 > From: [email protected] > Reply-To: [email protected] > To: [email protected] > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > Title : JavaScript Message Security Format > Author(s) : E. Rescorla, J. Hildebrand > Filename : draft-rescorla-jsms-00.txt > Pages : 24 > Date : 2011-03-07 > > Many applications require the ability to send cryptographically > secured messages. While the IETF has defined a number of formats for > such messages (e.g. CMS) those formats use encodings which are not > congenial for Web applications. This document describes a new > cryptographic message format which is based on JavaScript Object > Notation (JSON) and thus is easy for Web applications to generate and > parse. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-rescorla-jsms-00.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > > <draft-rescorla-jsms-00.txt><Attached Message > Part.txt>_______________________________________________ > woes mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/woes _______________________________________________ woes mailing list [email protected] https://www.ietf.org/mailman/listinfo/woes
