Re: [jose] I-D Action: draft-ietf-jose-use-cases-04.txt
Richard Barnes <rlb@ipv.sx> Thu, 15 August 2013 14:49 UTC
Return-Path: <rlb@ipv.sx>
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 8E3F721E8145 for <jose@ietfa.amsl.com>; Thu, 15 Aug 2013 07:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.676
X-Spam-Level:
X-Spam-Status: No, score=-2.676 tagged_above=-999 required=5 tests=[AWL=0.300, 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 o+sV4csKElsX for <jose@ietfa.amsl.com>; Thu, 15 Aug 2013 07:49:02 -0700 (PDT)
Received: from mail-oa0-f50.google.com (mail-oa0-f50.google.com [209.85.219.50]) by ietfa.amsl.com (Postfix) with ESMTP id 3B90421E8158 for <jose@ietf.org>; Thu, 15 Aug 2013 07:48:23 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id i4so866571oah.37 for <jose@ietf.org>; Thu, 15 Aug 2013 07:48:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=k/+grR6Vac4OUBe1thrqG2r2CUaoGPuX9HhzGSozM6E=; b=dfmWiTXJAZq666DJtXRiOLBZUXATdJGiCeCxxqR4sTv8Nhtq+i1ozDwdksUjYtv+6R ln416Ilnlfzc1RQZFMXDXtE9l0av2ZBcj8bTQu8eyaaWlcPWPz6BLt60mjGre6E3d4VH 4RsdiPzHXoooRnplAnxVBvJHpYgJ7Q25xznQAXD82mCKCZ2mkwunQG99UIidczzX/CWj c1i4fKposSFO++9eEqx0MAfLpLKVUqogM+slyPc70o/FjM/s5w021hM4GcZMjqX4lLLH KLs3vt5OIQZoTgWRW3UVc1touxYtAPtnA5raeljPyNZN2QKOq10WJT2/T5+yv6DZg+MF +CLQ==
X-Gm-Message-State: ALoCoQk9GHzqPi2v++Jls8FqN+/RiDsCC9/FE7AHJz8rHEqXZ2seQhfUn9eFfR+uuFqh/SOl7Bv+
MIME-Version: 1.0
X-Received: by 10.182.148.8 with SMTP id to8mr26349910obb.17.1376578102741; Thu, 15 Aug 2013 07:48:22 -0700 (PDT)
Received: by 10.60.31.74 with HTTP; Thu, 15 Aug 2013 07:48:22 -0700 (PDT)
X-Originating-IP: [192.1.51.54]
In-Reply-To: <20130815134214.24601.92567.idtracker@ietfa.amsl.com>
References: <20130815134214.24601.92567.idtracker@ietfa.amsl.com>
Date: Thu, 15 Aug 2013 10:48:22 -0400
Message-ID: <CAL02cgQGDzYkjx=0HPrQxqMPJVA1ApbhsfJS3MrkR0KGAQ0pGw@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "jose@ietf.org" <jose@ietf.org>
Content-Type: multipart/alternative; boundary="089e0139fc76d1decd04e3fd90ce"
Subject: Re: [jose] I-D Action: draft-ietf-jose-use-cases-04.txt
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 15 Aug 2013 14:49:08 -0000
This version makes a couple of minor updates in response to late comments -- Updates the XMPP use case to more closely match the current E2E spec -- Notes that applications should pick a serialization -- Adds back some functional requirements that were accidentally deleted On Thu, Aug 15, 2013 at 9:42 AM, <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(s) : Richard Barnes > Filename : draft-ietf-jose-use-cases-04.txt > Pages : 25 > Date : 2013-08-15 > > 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-04 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-jose-use-cases-04 > > > 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 >
- [jose] I-D Action: draft-ietf-jose-use-cases-04.t… internet-drafts
- Re: [jose] I-D Action: draft-ietf-jose-use-cases-… Richard Barnes
- Re: [jose] I-D Action: draft-ietf-jose-use-cases-… Anders Rundgren