Re: [OAUTH-WG] Fwd: draft-ietf-oauth-jwt-bearer draft errors

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Wed, 12 November 2014 19:09 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.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 8D2BC1A1AA7 for <oauth@ietfa.amsl.com>; Wed, 12 Nov 2014 11:09:38 -0800 (PST)
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, 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 MdkfOkr3GZj4 for <oauth@ietfa.amsl.com>; Wed, 12 Nov 2014 11:09:31 -0800 (PST)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71BD21ACF17 for <oauth@ietf.org>; Wed, 12 Nov 2014 11:08:17 -0800 (PST)
Received: by mail-la0-f45.google.com with SMTP id pn19so11922694lab.32 for <oauth@ietf.org>; Wed, 12 Nov 2014 11:08:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=L2K/I4x1XZqIUhRrI6OGTezKYqJLGm6brbzN8fRjgy4=; b=Otl/voN30nYs9mnrvpr9HfzXdfbiTC9ZRmxDMyGosm51TQH2ATVEQRfzcg88zUEj3H rGR8F7lNgPGiojzSItWdDwbpFcr84Ib+drTXMI31klEXMLrwQcg0KYp1Vrx3jNIRke0r x9NP5MgAgtofkblT7xPsGI31a7/PvSL32bN84goBSxs8tPNdFLhF4p+9HS4KVKxbiRNU HGyVrAIYx+hkZBq+8PLVnE4928l52k1DMOWNMDldwNXEuwpwcCGz5HCfSn0sBIlqGnnu RoNISrx8cYMKjbVwzzec0MZ99MDDVyoFhoNQBdeu64SBh3FWFl8CMXSrisUWyRDuMyDR Dzgw==
MIME-Version: 1.0
X-Received: by 10.152.115.131 with SMTP id jo3mr43827719lab.20.1415819295829; Wed, 12 Nov 2014 11:08:15 -0800 (PST)
Received: by 10.112.49.52 with HTTP; Wed, 12 Nov 2014 11:08:15 -0800 (PST)
In-Reply-To: <CA+k3eCStAvyM9niT3hoNgAq5CWH-jJb+7uUSk0grYmXt1wmBaA@mail.gmail.com>
References: <CABhm=xCHO7OCEPFk26hgVVtUWvUo99Q-T1ZWwKCk2nMwfK5eTw@mail.gmail.com> <CAAX2Qa2JQoZPzM0AtQy3VpE9EjaTbi1qBRqcb6d6dF2TZsOieA@mail.gmail.com> <CA+k3eCStAvyM9niT3hoNgAq5CWH-jJb+7uUSk0grYmXt1wmBaA@mail.gmail.com>
Date: Wed, 12 Nov 2014 14:08:15 -0500
Message-ID: <CAHbuEH4hxB-a08n6YYobzZ=b1mkBqNe-WRBkoytbrXbdW7-TDg@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: Brian Campbell <bcampbell@pingidentity.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/T8BBIHLPcaGKdQTCx_wX45a_kgc
Cc: Benjamin Trofatter <trofatter@google.com>, "oauth-chairs@tools.ietf.org" <oauth-chairs@tools.ietf.org>, oauth <oauth@ietf.org>
Subject: Re: [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 19:09:38 -0000

Hi Brian,

If you could make a quick update, that would be easier to prevent it
from getting lost.  The shepherd and I will recheck the draft and then
I'll move it forward.

Thanks for all of your work on this!
Kathleen

On Wed, Nov 12, 2014 at 12:05 PM, Brian Campbell
<bcampbell@pingidentity.com> wrote:
> 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@google.com       //      (650) 279-0512
>
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>



-- 

Best regards,
Kathleen