Return-Path: <torsten@lodderstedt.net>
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 C070021F86A8 for <oauth@ietfa.amsl.com>;
 Sun,  3 Feb 2013 05:04:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.2
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 tagged_above=-999 required=5 tests=[AWL=1.048,
 BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uUtiOnge45TP for
 <oauth@ietfa.amsl.com>; Sun,  3 Feb 2013 05:04:53 -0800 (PST)
Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de
 [80.67.18.15]) by ietfa.amsl.com (Postfix) with ESMTP id EC03D21F86B8 for
 <oauth@ietf.org>; Sun,  3 Feb 2013 05:04:52 -0800 (PST)
Received: from [79.253.33.56] (helo=[192.168.71.36]) by
 smtprelay03.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68)
 (envelope-from <torsten@lodderstedt.net>) id 1U1zFY-0004UH-0A;
 Sun, 03 Feb 2013 14:04:48 +0100
Message-ID: <510E606E.2040409@lodderstedt.net>
Date: Sun, 03 Feb 2013 14:04:46 +0100
From: Torsten Lodderstedt <torsten@lodderstedt.net>
User-Agent: Mozilla/5.0 (Windows NT 6.2;
 rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Donald F Coffin <donald.coffin@reminetworks.com>
References: <006401cdfe5f$2555f170$7001d450$@reminetworks.com>
 <51085B43.3080103@aol.com> <00c901cdfe80$e7d0eb30$b772c190$@reminetworks.com>
 <9DFD603A-1170-41D8-A22F-8654D55546B3@lodderstedt.net>
 <00a301ce0205$b6b1ca00$24155e00$@reminetworks.com>
In-Reply-To: <00a301ce0205$b6b1ca00$24155e00$@reminetworks.com>
Content-Type: multipart/alternative;
 boundary="------------060604060908010306040000"
X-Df-Sender: dG9yc3RlbkBsb2RkZXJzdGVkdC1vbmxpbmUuZGU=
Cc: 'John Adkins' <jva2@pge.com>, 'Marty Burns' <marty@hypertek.us>,
 'Scott Crowder' <scott.crowder@qadoenergy.com>,
 'Dave Robin' <drobin@automatedlogic.com>,
 'John Teeter' <john.teeter@peoplepowerco.com>, pmadsen@pingidentity.com,
 'Edward Denson' <ewd7@pge.com>, oauth@ietf.org,
 'Ray Perlner' <ray.perlner@nist.gov>, 'Anne Hendry' <ahendry2@gmail.com>,
 'Lynne Rodoni' <mrodoni@semprautilities.com>,
 'Uday Verma' <uday.verma@ilinknet.com>
Subject: Re: [OAUTH-WG] draft-ietf-oauth-revocation-04
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 03 Feb 2013 13:04:53 -0000

This is a multi-part message in MIME format.
--------------060604060908010306040000
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Donald,

Am 03.02.2013 12:57, schrieb Donald F Coffin:
> Perhaps the section on the *Server’s Revocation Policy* should address 
> a few of the reasons why a client may want or need to revoke a token.  
> The current description provides no consideration for the relationship 
> between tokens and scope, although there clearly is a relationship.

I will extend the description text in the next revision.

regards,
Torsten.

--------------060604060908010306040000
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hi Donald,<br>
    <br>
    <div class="moz-cite-prefix">Am 03.02.2013 12:57, schrieb Donald F
      Coffin:<br>
    </div>
    <blockquote
      cite="mid:00a301ce0205$b6b1ca00$24155e00$@reminetworks.com"
      type="cite"><span
style="font-size:12.0pt;font-family:&quot;Cambria&quot;,&quot;serif&quot;;color:#0070C0">Perhaps
        the section on the <b>Server’s Revocation Policy</b> should
        address a few of the reasons why a client may want or need to
        revoke a token.  The current description provides no
        consideration for the relationship between tokens and scope,
        although there clearly is a relationship.</span></blockquote>
    <br>
    I will extend the description text in the next revision.<br>
    <br>
    regards,<br>
    Torsten.<br>
  </body>
</html>

--------------060604060908010306040000--
