[OAUTH-WG] Fwd: draft-ietf-oauth-jwt-bearer draft errors
Brian Campbell <bcampbell@pingidentity.com> Wed, 12 November 2014 17:06 UTC
Return-Path: <bcampbell@pingidentity.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B8F81A8AEA for <oauth@ietfa.amsl.com>; Wed, 12 Nov 2014 09:06:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.578
X-Spam-Level:
X-Spam-Status: No, score=-3.578 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 gslZsdUNF63M for <oauth@ietfa.amsl.com>; Wed, 12 Nov 2014 09:06:27 -0800 (PST)
Received: from na3sys009aog108.obsmtp.com (na3sys009aog108.obsmtp.com [74.125.149.199]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90F171A1B17 for <oauth@ietf.org>; Wed, 12 Nov 2014 09:06:27 -0800 (PST)
Received: from mail-ig0-f173.google.com ([209.85.213.173]) (using TLSv1) by na3sys009aob108.postini.com ([74.125.148.12]) with SMTP ID DSNKVGOTk3UE0mX0zuby6V5aeLIpaPkB/z5w@postini.com; Wed, 12 Nov 2014 09:06:27 PST
Received: by mail-ig0-f173.google.com with SMTP id r10so3352943igi.0 for <oauth@ietf.org>; Wed, 12 Nov 2014 09:06:26 -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:from:date :message-id:subject:to:content-type; bh=lvniXLQ9menbeIK7hGNkqCjjiQUGz30mLE4C+E2P3PE=; b=jYf4ZtTCVcp/IsCGMNemlOMS+eiLsmpbSL+WMYVwk4Ghb0z1DJJNuSIukp1sDZ8r9h SKHRihIi+oezI/wIHx8GTUBD71LJbUzQxqfHa9wScVPw/yFr7Dn0F6tdifghXMjlVSC9 NrJkCy/G7M2608lpfnA8cbd0Wuc7VATDxXx800VG5nZZJPnJCr+g9w3e8IiPmQEUQIdb cRQWJYOukxp1Meqf980wF54GpfhLcR9Vkmxtvysr0bj7HcazP1l+wZQ2L+xa5I0bVLD1 DmrUHy+r57w/8u9Nvvy0zFm9rEeYJGOj27/tVAn4TUChPbFNBYFeZu4MJMzbUmeTr5si cv6g==
X-Gm-Message-State: ALoCoQlSFDxScVX4pspHvdA3hJWtnrs48iXXq/EBqI4B+HG867ILYc7+Ana2RdQGwDat9lcsshlH1GQ5iYo060LdIRrCSP6gKOalBiuJ5grWZKbJ8tMDiWBqWCU9gPLJkzM3cMz51+0b
X-Received: by 10.43.99.3 with SMTP id cq3mr14277621icc.49.1415811986921; Wed, 12 Nov 2014 09:06:26 -0800 (PST)
X-Received: by 10.43.99.3 with SMTP id cq3mr14276718icc.49.1415811978688; Wed, 12 Nov 2014 09:06:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.28.15 with HTTP; Wed, 12 Nov 2014 09:05:48 -0800 (PST)
In-Reply-To: <CAAX2Qa2JQoZPzM0AtQy3VpE9EjaTbi1qBRqcb6d6dF2TZsOieA@mail.gmail.com>
References: <CABhm=xCHO7OCEPFk26hgVVtUWvUo99Q-T1ZWwKCk2nMwfK5eTw@mail.gmail.com> <CAAX2Qa2JQoZPzM0AtQy3VpE9EjaTbi1qBRqcb6d6dF2TZsOieA@mail.gmail.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Wed, 12 Nov 2014 10:05:48 -0700
Message-ID: <CA+k3eCStAvyM9niT3hoNgAq5CWH-jJb+7uUSk0grYmXt1wmBaA@mail.gmail.com>
To: oauth <oauth@ietf.org>, "oauth-chairs@tools.ietf.org" <oauth-chairs@tools.ietf.org>, Benjamin Trofatter <trofatter@google.com>
Content-Type: multipart/alternative; boundary="bcaec5171a870f10a00507ac6a48"
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/FTN6riSNKM1bGS_pK2xgYQSauHA
Subject: [OAUTH-WG] Fwd: draft-ietf-oauth-jwt-bearer draft errors
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 12 Nov 2014 17:06:34 -0000
Forwarding this to the WG. There is a word missing in the sentence noted below as well as in the similar sentence in the SAML draft. However, I believe it should be "to the client" rather than "about the client". What is the most appropriate way to handle a minor fix like this at this stage? A note to the RFC editor? Or should I push new drafts? https://tools.ietf.org/html/draft-ietf-oauth-jwt-bearer-11#section-7 https://tools.ietf.org/html/draft-ietf-oauth-saml2-bearer-22#section-7 ---------- Forwarded message ---------- From: Benjamin Trofatter <trofatter@google.com> Date: Sat, Nov 8, 2014 at 8:11 PM Subject: draft-ietf-oauth-jwt-bearer draft errors To: mbj@microsoft.com, brian.d.campbell@gmail.com, cmortimore@salesforce.com Hi, I was reading your draft and noticed a couple of typos. In 7 Privacy paragraph 1, the last sentence reads: "In cases where it is desirable to prevent disclosure of certain information the client, the JWT should be be encrypted to the authorization server." I'm guessing this ought to say something like: "In cases where it is desirable to prevent disclosure of certain information about the client, the JWT should be encrypted to the authorization server." Hope this helps, Ben *_______________________________________________* Ben Trofatter // Software Engineer // trofatter@g oogle.com // (650) 279-0512
- [OAUTH-WG] Fwd: draft-ietf-oauth-jwt-bearer draft… Brian Campbell
- Re: [OAUTH-WG] Fwd: draft-ietf-oauth-jwt-bearer d… Kathleen Moriarty
- Re: [OAUTH-WG] Fwd: draft-ietf-oauth-jwt-bearer d… Brian Campbell