[OAUTH-WG] Fwd: Last Call: <draft-ietf-kitten-sasl-oauth-22.txt> (A set of SASL Mechanisms for OAuth) to Proposed Standard

Benjamin Kaduk <kaduk@MIT.EDU> Thu, 30 April 2015 18:37 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id A9A621ACDE0 for <oauth@ietfa.amsl.com>; Thu, 30 Apr 2015 11:37:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7puA7uS0aqH5 for <oauth@ietfa.amsl.com>; Thu, 30 Apr 2015 11:37:41 -0700 (PDT)
Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD6471ACDCC for <oauth@ietf.org>; Thu, 30 Apr 2015 11:37:40 -0700 (PDT)
X-AuditID: 1209190f-f79d16d000000d3d-8e-5542767383fc
Received: from mailhub-auth-4.mit.edu ( []) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 68.A8.03389.37672455; Thu, 30 Apr 2015 14:37:39 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu []) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id t3UIbcmG028165 for <oauth@ietf.org>; Thu, 30 Apr 2015 14:37:39 -0400
Received: from multics.mit.edu (system-low-sipb.mit.edu []) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id t3UIbafw010272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <oauth@ietf.org>; Thu, 30 Apr 2015 14:37:38 -0400
Received: (from kaduk@localhost) by multics.mit.edu ( id t3UIbZKw027665; Thu, 30 Apr 2015 14:37:35 -0400 (EDT)
Date: Thu, 30 Apr 2015 14:37:35 -0400
From: Benjamin Kaduk <kaduk@MIT.EDU>
To: oauth@ietf.org
Message-ID: <alpine.GSO.1.10.1504301434550.22210@multics.mit.edu>
User-Agent: Alpine 1.10 (GSO 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPIsWRmVeSWpSXmKPExsUixG6nrltc5hRq8GyzlsXJt6/YHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVMe9YRsEs0YptS2ewNzAuF+xi5OSQEDCRmLR9LiOELSZx4d56 ti5GLg4hgcVMEmu3zGaGcI4xSmxYfw7Kuc4k8WjqURYIp4FRYsukRhaQfhYBbYkpX18xg9hs AioSM99sZAOxRQSEJJ7v7GMCsYUFqiT+z57KCmLzCjhKXNv8BWy3qICOxOr9U1gg4oISJ2c+ AbOZBbQklk/fxjKBkW8WktQsJKkFjEyrGGVTcqt0cxMzc4pTk3WLkxPz8lKLdE30cjNL9FJT SjcxgsKJU5J/B+O3g0qHGAU4GJV4eD+0O4YKsSaWFVfmHmKU5GBSEuVtynUKFeJLyk+pzEgs zogvKs1JLT7EKMHBrCTCq5YJlONNSaysSi3Kh0lJc7AoifNu+sEXIiSQnliSmp2aWpBaBJOV 4eBQkuB9VQLUKFiUmp5akZaZU4KQZuLgBBnOAzRctxRkeHFBYm5xZjpE/hSjopQ4bxBIQgAk kVGaB9cLi/dXjOJArwjzTgWp4gGmCrjuV0CDmYAGn7/lADK4JBEhJdXAmJNhcGnN/Qldy/Zc 79dpTD7hpf30otRFNcUXbcqc4qr2L3N8fDf2b2Db+LffPfWmk870+59aSzkfZKzdsPlxcfFV 55cvtlvFSXN28VsZHDysMqVE623CmoykVf5tTlESy08JTnP48EvrvSGj/URBzwWFRXxbtYwm zJ34au4qtidNaukGr3auUWIpzkg01GIuKk4EADIZvzTSAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/i7VYbSAmRb88x-C2KlZ6otuLj8M>
Subject: [OAUTH-WG] Fwd: Last Call: <draft-ietf-kitten-sasl-oauth-22.txt> (A set of SASL Mechanisms for OAuth) to Proposed Standard
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: Thu, 30 Apr 2015 18:37:42 -0000

Hi all,

I just wanted to call attention to this IETF Last Call; there were some
changes since the -18 which is the last one that we sent to this list.


---------- Forwarded message ----------
Date: Thu, 30 Apr 2015 14:31:47 -0400
From: The IESG <iesg-secretary@ietf.org>
Reply-To: ietf@ietf.org
To: IETF-Announce <ietf-announce@ietf.org>
Cc: kitten@ietf.org
Subject: [kitten] Last Call: <draft-ietf-kitten-sasl-oauth-22.txt> (A set of
    SASL Mechanisms for OAuth) to Proposed Standard

The IESG has received a request from the Common Authentication Technology
Next Generation WG (kitten) to consider the following document:
- 'A set of SASL Mechanisms for OAuth'
  <draft-ietf-kitten-sasl-oauth-22.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-05-14. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   OAuth enables a third-party application to obtain limited access to a
   protected resource, either on behalf of a resource owner by
   orchestrating an approval interaction, or by allowing the third-party
   application to obtain access on its own behalf.

   This document defines how an application client uses credentials
   obtained via OAuth over the Simple Authentication and Security Layer
   (SASL) to access a protected resource at a resource serve.  Thereby,
   it enables schemes defined within the OAuth framework for non-HTTP-
   based application protocols.

   Clients typically store the user's long-term credential.  This does,
   however, lead to significant security vulnerabilities, for example,
   when such a credential leaks.  A significant benefit of OAuth for
   usage in those clients is that the password is replaced by a shared
   secret with higher entropy, i.e., the token.  Tokens typically
   provide limited access rights and can be managed and revoked
   separately from the user's long-term password.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.

This defines a way to use the obsolete OAUTH1.0a mechanism
as well an OAUTH2 mechanism. That is deliberate and reasonable.

Kitten mailing list