Return-Path: X-Original-To: jose@ietfa.amsl.com Delivered-To: jose@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11EB821F9951 for ; Thu, 5 Sep 2013 08:53:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.804 X-Spam-Level: X-Spam-Status: No, score=-2.804 tagged_above=-999 required=5 tests=[AWL=0.172, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rTu23QMpis6k for ; Thu, 5 Sep 2013 08:53:09 -0700 (PDT) Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by ietfa.amsl.com (Postfix) with ESMTP id EABDA21F93B9 for ; Thu, 5 Sep 2013 08:53:06 -0700 (PDT) Received: by mail-oa0-f48.google.com with SMTP id o17so2387970oag.7 for ; Thu, 05 Sep 2013 08:53:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=yq4DGsqn0DqBfO5xjj/wY7zutZAXz6Sp7udH473nzj8=; b=juOxnYP1lcY6ZldSBRpx9gJk6GkRjP3vaOVSu6UEqXmFRvTyH+PCfZi3jNyHcVkjja Mkls5eGerAhh81Ba8zrwDPVcU7ewyGNQpA2uR/1ITm+OKAO3F4gxaUgJ+yG0FA/PnJBX C8oyg+4+r7gc2vFvH5Ai0dcQVeBgw/Mt0EAz+bbp3v89SpqG6EtJMx/WKfvBof4Q6Ggk gBruir6BdwnyHnroPje1bhuokC1fYAjipqQeXMZYSnlrl5wtHsmwHeqRB7pFmlWb14Tl 8fr34CPqvLkXbJGijqgJEWRkoi06XBRZ0webyfIg9VqiwrfNAgKgpDuDv0hc6+JwZJTy OdPA== X-Gm-Message-State: ALoCoQlEVvt9kLz4wMTCI3LK8DXrOH1YkzHpwVMM5WGcM/m1gV6f4j0L5y1VKB/a2LY4oDEBuXFf MIME-Version: 1.0 X-Received: by 10.182.199.74 with SMTP id ji10mr6921507obc.69.1378396385192; Thu, 05 Sep 2013 08:53:05 -0700 (PDT) Received: by 10.60.31.74 with HTTP; Thu, 5 Sep 2013 08:53:05 -0700 (PDT) In-Reply-To: <20130905154742.11450.63345.idtracker@ietfa.amsl.com> References: <20130905154742.11450.63345.idtracker@ietfa.amsl.com> Date: Thu, 5 Sep 2013 11:53:05 -0400 Message-ID: From: Richard Barnes To: "jose@ietf.org" Content-Type: multipart/alternative; boundary=e89a8ff1c024e639e904e5a4ea60 Subject: Re: [jose] I-D Action: draft-ietf-jose-use-cases-05.txt X-BeenThere: jose@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Javascript Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Sep 2013 15:53:14 -0000 --e89a8ff1c024e639e904e5a4ea60 Content-Type: text/plain; charset=ISO-8859-1 This just updates the use cases to include a mention of non-protected objects, as discussed previously on the list. --Richard On Thu, Sep 5, 2013 at 11:47 AM, wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Javascript Object Signing and Encryption > Working Group of the IETF. > > Title : Use Cases and Requirements for JSON Object > Signing and Encryption (JOSE) > Author(s) : Richard Barnes > Filename : draft-ietf-jose-use-cases-05.txt > Pages : 26 > Date : 2013-09-05 > > 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 (CMS) > 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 > (JSON), drawn from a variety of application security mechanisms > currently in development. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-jose-use-cases > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-jose-use-cases-05 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-jose-use-cases-05 > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > jose mailing list > jose@ietf.org > https://www.ietf.org/mailman/listinfo/jose > --e89a8ff1c024e639e904e5a4ea60 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
This just updates the use cases to include a mention of no= n-protected objects, as discussed previously on the list.
--Richard


On Th= u, Sep 5, 2013 at 11:47 AM, <internet-drafts@ietf.org> wrote:

A New Internet-Draft is available from the on-line Internet-Drafts director= ies.
=A0This draft is a work item of the Javascript Object Signing and Encryptio= n Working Group of the IETF.

=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Use Cases and Requirements for = JSON Object Signing and Encryption (JOSE)
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Richard Barnes
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-jose-use-cases-05.txt<= br> =A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 26
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2013-09-05

Abstract:
=A0 =A0Many Internet applications have a need for object-based security
=A0 =A0mechanisms in addition to security mechanisms at the network layer o= r
=A0 =A0transport layer. =A0In the past, the Cryptographic Message Syntax (C= MS)
=A0 =A0has provided a binary secure object format based on ASN.1. =A0Over =A0 =A0time, the use of binary object encodings such as ASN.1 has been
=A0 =A0overtaken by text-based encodings, for example JavaScript Object
=A0 =A0Notation. =A0This document defines a set of use cases and requiremen= ts
=A0 =A0for a secure object format encoded using JavaScript Object Notation<= br> =A0 =A0(JSON), drawn from a variety of application security mechanisms
=A0 =A0currently in development.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-jose-use-cases

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-jose-use-cases-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-jose-use-c= ases-05


Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp= .ietf.org/internet-drafts/

_______________________________________________
jose mailing list
jose@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/jose

--e89a8ff1c024e639e904e5a4ea60--