Re: [OAUTH-WG] AD Review of draft-ietf-oauth-introspection-07
Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Mon, 20 April 2015 13:03 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 52D021AC42B for <oauth@ietfa.amsl.com>; Mon, 20 Apr 2015 06:03:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 8ckwFyhhmX1M for <oauth@ietfa.amsl.com>; Mon, 20 Apr 2015 06:03:54 -0700 (PDT)
Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) (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 B87C11AC407 for <oauth@ietf.org>; Mon, 20 Apr 2015 06:03:53 -0700 (PDT)
Received: by lagv1 with SMTP id v1so126170573lag.3 for <oauth@ietf.org>; Mon, 20 Apr 2015 06:03:52 -0700 (PDT)
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=pNnfnkgvckh83SmQWHKsw8MrSAURdLXqFWJTQhosxf0=; b=PfrlBgzH/D4zbiVjboesE2Lv9zidJMMw5sqN2Ig4KWWMKBQX6ferWLd9fXHo/Y25oE HUF6Lt2fRZ9yckkxWYbfe2lJejQdNkoU7jQVM+rv7oIb5wViMm+dejra1r70lvpiL67F gZBqe3o+nMfvIlBNETbYVE/qeUrzVPFEB8I6+nN7tmjF3HIiX9Os/3u6BVUCqS3rjzql R/tb/DPR1RPl/BeCtEST5oEGqXOZHZt0rChg3IJV8FRBAmmuw0EdGjbJYL/7B6wDlrOg ZMXjPSdMezTrGwFJTDHEGIyVk8Ikm416NcMoqunzx/ht61Pda7/q7fGih3HensmyAQi8 NLGA==
MIME-Version: 1.0
X-Received: by 10.152.27.194 with SMTP id v2mr15276510lag.75.1429535032218; Mon, 20 Apr 2015 06:03:52 -0700 (PDT)
Received: by 10.112.11.199 with HTTP; Mon, 20 Apr 2015 06:03:52 -0700 (PDT)
In-Reply-To: <5534F011.8030200@mit.edu>
References: <CAHbuEH6=036uX5O_kaRJ5zTZneEqDXkF8UUuPxT6UosMfjZYaw@mail.gmail.com> <5534F011.8030200@mit.edu>
Date: Mon, 20 Apr 2015 09:03:52 -0400
Message-ID: <CAHbuEH41dYMhOcBsBeZwDLruGd=pOkUVZ2cJRGh0wu1vOna5Jw@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: Justin Richer <jricher@mit.edu>
Content-Type: multipart/alternative; boundary="089e0158c2acca1a420514278f12"
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/r5KlF_cv8E26C-0HHRnLEvzWNXw>
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] AD Review of draft-ietf-oauth-introspection-07
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: Mon, 20 Apr 2015 13:03:56 -0000
Hi Justin, On Mon, Apr 20, 2015 at 8:24 AM, Justin Richer <jricher@mit.edu> wrote: > Kathleen, > > Thanks for the update. How would we best handle this situation, since it's > really referring to additional information that's outside the scope of the > interoperable core? Since we're not specifying what the data is, we're not > really in a position to say what the concerns are in a concrete manner. I'm > thinking a sentence or two like this in the privacy considerations section: > > If the protected resource sends additional information about the client's > request to the authorization server using an extension of this > specification, such as the client's IP address or other information, such > information could have have additional privacy considerations. > > I think that looks good and you may want to say it is out-of scope for this draft so no one asks why you didn't go deeper. Let me know once it is ready and I'll kick off last call. Thanks. Kathleen > > > -- Justin > > > On 4/19/2015 7:01 PM, Kathleen Moriarty wrote: > > Hello, > > Thank you for your work on draft-ietf-oauth-introspection-07. The > security considerations appear to be addressed well and I was glad to see > how a response is handled when the response code is false, to not reveal > information as to why. > > The privacy considerations look good, but I do have another question > that should be addressed in the draft in regard to privacy. > > Section 2.1 says an IP address (or something else) might be used to > provide context of the query, the authorization server could have other > information about the client. It would be good to mention privacy related > considerations for the client in this case in addition to what gets > returned in the Introspection Response (already covered). > > Thank you. > > > -- > > Best regards, > Kathleen > > > _______________________________________________ > OAuth mailing listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth > > > -- Best regards, Kathleen
- [OAUTH-WG] AD Review of draft-ietf-oauth-introspe… Kathleen Moriarty
- Re: [OAUTH-WG] AD Review of draft-ietf-oauth-intr… Justin Richer
- Re: [OAUTH-WG] AD Review of draft-ietf-oauth-intr… Kathleen Moriarty