[OAUTH-WG] Fwd: New Version Notification for draft-ietf-oauth-jwt-bcp-02.txt

Yaron Sheffer <yaronf.ietf@gmail.com> Wed, 02 May 2018 08:36 UTC

Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B1321270A0 for <oauth@ietfa.amsl.com>; Wed, 2 May 2018 01:36:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 GiG1jyBUxMjh for <oauth@ietfa.amsl.com>; Wed, 2 May 2018 01:36:04 -0700 (PDT)
Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B16F1242F5 for <oauth@ietf.org>; Wed, 2 May 2018 01:36:04 -0700 (PDT)
Received: by mail-wr0-x22c.google.com with SMTP id g21-v6so13044844wrb.8 for <oauth@ietf.org>; Wed, 02 May 2018 01:36:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=M9P4egI/WOll4CuuR5/1UJ6XtroyTWJ3x43U9vT36ps=; b=Q8ZEsOeyBQmrTJL1UhxOIkas3f9jggnRhv3gJVXOHty6Fl2XvEvHvxJc5mpgIstx06 DON2D/bUBHm5sQ4EGNIdV85ZvsEG0g52180DT/XiUzBD0Ry37iHB3s4whsxl4L3CbV0K tSHlGJODMkcKUmejGv30S8P3+JSodVxKBp0gFvTRUxENtddycAH+z3rIkdPi4UFzneBR i0ED3PnS7DlVigmWNucNayfKZd7GbAAlrQadnNbmBo6EB8POgSaZ8Y/0UhX03C/LklkW tZ1+o1VxYohzrTvwhJDlP3iLqa021b7a6fYRwg/JfTcOA9eS8NRWXp34kfVa66gJQkof 6PlQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=M9P4egI/WOll4CuuR5/1UJ6XtroyTWJ3x43U9vT36ps=; b=RlvpZgfksZDrEU6fKpH1EjtwPWGEpFVjZ4o6vC8JoQUj468mOCR4winye9OfzzRUUT MKw22JJqo7N/jyWGNejMZfiHHMuljLV1jsqJ66xL0cM8y1iwg/htPEJYBIVnTU/sDWXH Ya6sXgMYJVXcObeNxmf12jWmysQ9dKaYHMG62/qQUNNo7fF6RspujONxtZx16q/pL8Dl hUqLFrn3uDWhAjSs0mqEtEUbayoEXwu4Kd4dUYWalHRKxsIJzfKzAWtqr0boNJ9rkIjT H5ooo2ZZtD8tfRtOBEdWiK/6EyAJXVBZQ9+G9ccfptTY7yYhnuJMQIMHyiQmicqFLwB2 ukuQ==
X-Gm-Message-State: ALQs6tBx4tkWnwIeU+ejBikmYE4q9dewd2DcnBPGsfePvf3xmn+mL/jp AHgGPmzaEJgr8g/ZgzbDse6pJPV9
X-Google-Smtp-Source: AB8JxZpqdfWM9Zq1C54CPxgzab0CNMi3qGvzG8QyXINNh+7epqUb0V3KaMycZzPqLV1gki0kruQ2DQ==
X-Received: by 2002:adf:d245:: with SMTP id o5-v6mr13576031wri.134.1525250162395; Wed, 02 May 2018 01:36:02 -0700 (PDT)
Received: from [172.21.2.7] (bzq-164-168-31-230.red.bezeqint.net. [31.168.164.230]) by smtp.gmail.com with ESMTPSA id m134sm13912927wmg.4.2018.05.02.01.36.01 for <oauth@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 02 May 2018 01:36:01 -0700 (PDT)
References: <152524957750.10707.16363318021232931449.idtracker@ietfa.amsl.com>
To: oauth@ietf.org
From: Yaron Sheffer <yaronf.ietf@gmail.com>
X-Forwarded-Message-Id: <152524957750.10707.16363318021232931449.idtracker@ietfa.amsl.com>
Message-ID: <53552a40-c1df-0a97-fce0-4a39c5e32182@gmail.com>
Date: Wed, 02 May 2018 11:36:00 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <152524957750.10707.16363318021232931449.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/SQU3XjdfoWtgBFCB4VbGZZD3AmY>
Subject: [OAUTH-WG] Fwd: New Version Notification for draft-ietf-oauth-jwt-bcp-02.txt
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 08:36:08 -0000

This new version should address all WGLC comments. Please let us know if 
there's anything missing.

Thanks,
	Yaron


-------- Forwarded Message --------
Subject: New Version Notification for draft-ietf-oauth-jwt-bcp-02.txt
Date: Wed, 02 May 2018 01:26:17 -0700
From: internet-drafts@ietf.org
To: Michael B. Jones <mbj@microsoft.com>, Yaron Sheffer 
<yaronf.ietf@gmail.com>, Dick Hardt <dick@amazon.com>, Michael Jones 
<mbj@microsoft.com>


A new version of I-D, draft-ietf-oauth-jwt-bcp-02.txt
has been successfully submitted by Yaron Sheffer and posted to the
IETF repository.

Name:		draft-ietf-oauth-jwt-bcp
Revision:	02
Title:		JSON Web Token Best Current Practices
Document date:	2018-05-02
Group:		oauth
Pages:		13
URL: 
https://www.ietf.org/internet-drafts/draft-ietf-oauth-jwt-bcp-02.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-oauth-jwt-bcp/
Htmlized:       https://tools.ietf.org/html/draft-ietf-oauth-jwt-bcp-02
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-ietf-oauth-jwt-bcp
Diff: 
https://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-jwt-bcp-02

Abstract:
    JSON Web Tokens, also known as JWTs, are URL-safe JSON-based security
    tokens that contain a set of claims that can be signed and/or
    encrypted.  JWTs are being widely used and deployed as a simple
    security token format in numerous protocols and applications, both in
    the area of digital identity, and in other application areas.  The
    goal of this Best Current Practices document is to provide actionable
    guidance leading to secure implementation and deployment of JWTs.

 


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.

The IETF Secretariat