IETF Logo Mail Archive

Re: [OAUTH-WG] draft-ietf-oauth-token-binding-01

Brian Campbell <bcampbell@pingidentity.com> Tue, 21 February 2017 20:48 UTC

Return-Path: <bcampbell@pingidentity.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 49BC01294E2 for <oauth@ietfa.amsl.com>; Tue, 21 Feb 2017 12:48:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pingidentity.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 835q1yjV9Kgl for <oauth@ietfa.amsl.com>; Tue, 21 Feb 2017 12:48:49 -0800 (PST)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (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 EA59A12944C for <oauth@ietf.org>; Tue, 21 Feb 2017 12:48:45 -0800 (PST)
Received: by mail-yw0-x22f.google.com with SMTP id p77so3106206ywg.1 for <oauth@ietf.org>; Tue, 21 Feb 2017 12:48:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=utVXTSTWErdGUMuq1eGmwKvSJO86dOpBW3c2fUTw0uE=; b=H+0jBBQ2iTP8fKm3P3U+CVmPNltQmGUo8HC5Bz0cihney7lF3LnqJpdsZOFGBWkGBh 68hASiQDw7CxbKiM5OmULSCe5eJSq5qMkIzV470ohjotups4F/8X7kyzgbFqb7A3nczW GrLlzu2sZ8lWYRTbn5MEH1tNZFQjMSPKuvNJ0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=utVXTSTWErdGUMuq1eGmwKvSJO86dOpBW3c2fUTw0uE=; b=b5yzu4s2A2qZAyji8fDB8oQ+q3Bwmjdmwv6/Z91mc1PeBYiYVuLjDkMOI5fE/AgQc3 hV701wfFmA/bJNtBlMlUL77gmxbc6JS2KtuNsuAb49qt6pjJjPM+ZkUVDB4aOoIJ3k/U 0iaFHWG8eUuGfn+RpaQkjbEJJaJjKYdh/FYolLwB/C7AJyOD1/bsIOpaQ464Ck6/g2ny o3NeJHqI/Vz4W0bhZohx52SlZRJyjCKv3m+54AGbwJBsLOf9nqJcY/jcWMihTth5ppX1 u4hSAvLE/sl7ewG96J+A5Eqch3/XhIOuiU66FvQjqFtult2MnN/ZBBvVdt51RM8+AOTL SeJA==
X-Gm-Message-State: AMke39lWqlZK5foqTu7IsvfTBYfHAPCokQdspbIEV9TPzcj/SP5KRT/bocoHU0Kyc6GO1XJp7CojszXlm8Kto3uB
X-Received: by 10.129.49.73 with SMTP id x70mr4206116ywx.171.1487710125109; Tue, 21 Feb 2017 12:48:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.126.131 with HTTP; Tue, 21 Feb 2017 12:48:14 -0800 (PST)
In-Reply-To: <01f901d28c1d$a56fbf30$f04f3d90$@nri.co.jp>
References: <01f901d28c1d$a56fbf30$f04f3d90$@nri.co.jp>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Tue, 21 Feb 2017 13:48:14 -0700
Message-ID: <CA+k3eCQNouPsf1ZdydsM51vkaxBKyKM617YPC5=U3DdBXLHVkw@mail.gmail.com>
To: Nat Sakimura <n-sakimura@nri.co.jp>
Content-Type: multipart/alternative; boundary="001a1140704089b69305491081be"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/1AnbEagZB9HRoWAaD-6RzZXtjbA>
Cc: oauth <oauth@ietf.org>
Subject: Re: [OAUTH-WG] draft-ietf-oauth-token-binding-01
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 21 Feb 2017 20:48:50 -0000

Adding some examples would probably be helpful, yes. Thanks. Some will
maybe be more possible/sensible than others (like I don't know what exactly
to show in an example of binding a refresh token) but I'll endeavor to add
some useful examples in a future revision.


On Tue, Feb 21, 2017 at 1:36 AM, Nat Sakimura <n-sakimura@nri.co.jp> wrote:

> Hi OAuthers:
>
>
>
> I was reading draft-ietf-oauth-token-binding-01 this afternoon and
> thought that examples for each subsection of 2 and 3 would be helpful.
>
>
>
> Is it possible/sensible to add them?
>
>
>
> Best,
>
>
>
> Nat
>
> --
>
> PLEASE READ :This e-mail is confidential and intended for the
>
> named recipient only. If you are not an intended recipient,
>
> please notify the sender  and delete this e-mail.
>
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>

v2.23.0 | Report a Bug | By Email