<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.barnes-jose-use-cases" target="https://datatracker.ietf.org/doc/html/draft-barnes-jose-use-cases-02">
   <front>
      <title>Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)</title>
      <author initials="R." surname="Barnes" fullname="Richard Barnes">
         <organization>BBN Technologies</organization>
      </author>
      <date month="February" day="25" year="2013" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-barnes-jose-use-cases-02" />
   
</reference>
