Re: [jose] I-D Action: draft-ietf-jose-use-cases-06.txt

Richard Barnes <rlb@ipv.sx> Fri, 27 December 2013 19:23 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7F8E1AE281 for <jose@ietfa.amsl.com>; Fri, 27 Dec 2013 11:23:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x2CDJqUngxEK for <jose@ietfa.amsl.com>; Fri, 27 Dec 2013 11:23:16 -0800 (PST)
Received: from mail-ob0-f171.google.com (mail-ob0-f171.google.com [209.85.214.171]) by ietfa.amsl.com (Postfix) with ESMTP id 55F801ADFC9 for <jose@ietf.org>; Fri, 27 Dec 2013 11:23:16 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id wp18so9775147obc.30 for <jose@ietf.org>; Fri, 27 Dec 2013 11:23:11 -0800 (PST)
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=TgXmykLZWFkKf1IGFKRP7B9moBcX9EXXeaBmVH1uayk=; b=RwdqtpPVP2l8W06vI8f37CrAHlfhukz6clHeOnAxX17Cm7Utz9HOrgABkazC2JuoQp Ih35Q+DXKG68rqqlKHPDwWUMa+5tk9mpS+9bVde1qpbRW5iETNd9EJKpT/4qWba78s/E 1j8zKtKAsnFC0AgUihoceFKSMOiMXehPm+CynNGwU9lAKXttT78rtRB7XqYqdtNDlwbR EPw+tOClYn4c2oDFpPihatYCJEDNhEjOBsWT9/LO3mfAQtV/O92Xfb56P6Jc9OKSXb4s s+2JbzhBACYZOWGnAGfNiQAfN9T3FQdDqEI2MCkCTJHwhgEB897+pSyKvVLfL3dpaN+D eFAA==
X-Gm-Message-State: ALoCoQmcntedEbj2Qu4qJN9qonrsF80uHDeesMM8MJj5uo3ZurQlbXoMqU4OYO5d6xjjoEew2G33
MIME-Version: 1.0
X-Received: by 10.182.250.163 with SMTP id zd3mr35689153obc.20.1388172190362; Fri, 27 Dec 2013 11:23:10 -0800 (PST)
Received: by 10.60.54.65 with HTTP; Fri, 27 Dec 2013 11:23:10 -0800 (PST)
In-Reply-To: <20131227192151.425.70057.idtracker@ietfa.amsl.com>
References: <20131227192151.425.70057.idtracker@ietfa.amsl.com>
Date: Fri, 27 Dec 2013 14:23:10 -0500
Message-ID: <CAL02cgSNmKuB-heAE1xvSHHwgGiT7e4z8z2vNPmPUrh=wfKK2Q@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "jose@ietf.org" <jose@ietf.org>
Content-Type: multipart/alternative; boundary="089e01634ec24b3e4a04ee890677"
Subject: Re: [jose] I-D Action: draft-ietf-jose-use-cases-06.txt
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/jose/>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Dec 2013 19:23:19 -0000

This is a very minor update to address some wording changes suggested by
the IESG.
--Richard


On Fri, Dec 27, 2013 at 2:21 PM, <internet-drafts@ietf.org> 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          : Richard Barnes
>         Filename        : draft-ietf-jose-use-cases-06.txt
>         Pages           : 26
>         Date            : 2013-12-27
>
> Abstract:
>    Many Internet applications have a need for object-based security
>    mechanisms in addition to security mechanisms at the network layer or
>    transport layer.  For many years, the Cryptographic Message Syntax
>    (CMS) has provided a binary secure object format based on ASN.1.
>    Over time, binary object encodings such as ASN.1 have become less
>    common than 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-06
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-jose-use-cases-06
>
>
> 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
>