[jose] I-D Action: draft-ietf-jose-jws-signing-input-options-05.txt
internet-drafts@ietf.org Thu, 19 November 2015 04:55 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: jose@ietf.org
Delivered-To: jose@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 50DA11A878C; Wed, 18 Nov 2015 20:55:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.10.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151119045530.2703.41693.idtracker@ietfa.amsl.com>
Date: Wed, 18 Nov 2015 20:55:30 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/mjIelLvg9ks6moDxXE2vQNCOWwQ>
Cc: jose@ietf.org
Subject: [jose] I-D Action: draft-ietf-jose-jws-signing-input-options-05.txt
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Nov 2015 04:55:30 -0000
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 : JWS Unencoded Payload Option Author : Michael B. Jones Filename : draft-ietf-jose-jws-signing-input-options-05.txt Pages : 12 Date : 2015-11-18 Abstract: JSON Web Signature (JWS) represents the payload of a JWS as a base64url encoded value and uses this value in the JWS Signature computation. While this enables arbitrary payloads to be integrity protected, some have described use cases in which the base64url encoding is unnecessary and/or an impediment to adoption, especially when the payload is large and/or detached. This specification defines a means of accommodating these use cases by defining an option to change the JWS Signing Input computation to not base64url- encode the payload. This option is intended to broaden the set of use cases for which the use of JWS is a good fit. This specification updates RFC 7519 by prohibiting the use of this option in JSON Web Tokens (JWTs). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jose-jws-signing-input-options/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-jose-jws-signing-input-options-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-jose-jws-signing-input-options-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] I-D Action: draft-ietf-jose-jws-signing-in… internet-drafts