IETF Logo Mail Archive

Re: [OAUTH-WG] Indicating sites where a token is valid

Brian Eaton <beaton@google.com> Fri, 14 May 2010 15:45 UTC

Return-Path: <beaton@google.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE74C3A69D2 for <oauth@core3.amsl.com>; Fri, 14 May 2010 08:45:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.408
X-Spam-Level:
X-Spam-Status: No, score=-100.408 tagged_above=-999 required=5 tests=[AWL=-0.845, BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EjjpK6DfAyzN for <oauth@core3.amsl.com>; Fri, 14 May 2010 08:45:50 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 9BA133A68DF for <oauth@ietf.org>; Fri, 14 May 2010 08:45:49 -0700 (PDT)
Received: from kpbe14.cbf.corp.google.com (kpbe14.cbf.corp.google.com [172.25.105.78]) by smtp-out.google.com with ESMTP id o4EFjZUA017397 for <oauth@ietf.org>; Fri, 14 May 2010 08:45:35 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1273851936; bh=lzEO9RZkzajBmDbmwMOM+c+Dvhk=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=w9xOHcu68vdP+vC18LChSYnXUAJZYbYdHKAgM0/rvq/VFEQ8E+a9mMfdPgxudeka2 /run375V2ZT6DwbFT9vdQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=WeyuCdCytV/HqzN9Mwh+HleK7ngft3aZeGE8iBHIm594jFgeN4JUnfOQEg+Ks7X7y yJAUfPZu/rrJeqEbbwzgQ==
Received: from pvg4 (pvg4.prod.google.com [10.241.210.132]) by kpbe14.cbf.corp.google.com with ESMTP id o4EFjXFW009685 for <oauth@ietf.org>; Fri, 14 May 2010 08:45:34 -0700
Received: by pvg4 with SMTP id 4so174813pvg.10 for <oauth@ietf.org>; Fri, 14 May 2010 08:45:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.210.21 with SMTP id i21mr888326wfg.16.1273851930491; Fri, 14 May 2010 08:45:30 -0700 (PDT)
Received: by 10.143.136.7 with HTTP; Fri, 14 May 2010 08:45:30 -0700 (PDT)
In-Reply-To: <AANLkTil7gTRNmqTAwsvFEdMLmlgeakpy8o1wyPTcTbLF@mail.gmail.com>
References: <255B9BB34FB7D647A506DC292726F6E11263073D6D@WSMSG3153V.srv.dir.telstra.com> <g2xfd6741651005071106if93ba794q7e9739669eb22fc2@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343B3AB46E1F@P3PW5EX1MB01.EX1.SECURESERVER.NET> <D24C564ACEAD16459EF2526E1D7D605D0C8D22ED62@IMCMBX3.MITRE.ORG> <AANLkTilkUA9i-WZPv8PqPsxiJf5_1SuiCb_GOTdcwtPX@mail.gmail.com> <AANLkTilNNyKvpbzCYfc__AvY1rJKqXE7KN8VL-m_CF-L@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E112633D9594@WSMSG3153V.srv.dir.telstra.com> <AANLkTim0PNhUJAi1ZuDjB8feKh2Sb_OMoNz7AlDTYO6P@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E112634655A4@WSMSG3153V.srv.dir.telstra.com> <AANLkTil7gTRNmqTAwsvFEdMLmlgeakpy8o1wyPTcTbLF@mail.gmail.com>
Date: Fri, 14 May 2010 08:45:30 -0700
Message-ID: <AANLkTinPiCBvtnTW_m3bSUhB_OOK4ZD6JFjquECDMCi6@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Indicating sites where a token is valid
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 14 May 2010 15:45:51 -0000

On Thu, May 13, 2010 at 9:00 AM, Evan Gilbert <uidude@google.com> wrote:
>> Consider a generic search spider tool that you point at
>> http://calendar.serviceprovider.com/calendar/get. It can do its job with no
>> knowledge about what "calendar.get" means -- but it still needs to know (as
>> it spiders along) when it is safe to expose the token.
>
> How does the generic search spider know to call to
> http://calendar.serviceprovider.com/calendar/get in the first place?

I'm a bit confused by this example.

James, can you explain what you mean by "generic search spider tool"?

v2.23.0 | Report a Bug | By Email