Re: [kitten] AD review of draft-ietf-kitten-sasl-oauth-21

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 29 April 2015 21:05 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E63651A1BE3 for <kitten@ietfa.amsl.com>; Wed, 29 Apr 2015 14:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 Q4wBpU-3c40w for <kitten@ietfa.amsl.com>; Wed, 29 Apr 2015 14:05:30 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C84ED1A1BBD for <kitten@ietf.org>; Wed, 29 Apr 2015 14:05:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E6362BE3E; Wed, 29 Apr 2015 22:05:26 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U_2AXO1bunvK; Wed, 29 Apr 2015 22:05:25 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.18.22]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id CA9D1BDCA; Wed, 29 Apr 2015 22:05:25 +0100 (IST)
Message-ID: <55414795.3030606@cs.tcd.ie>
Date: Wed, 29 Apr 2015 22:05:25 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Benjamin Kaduk <kaduk@MIT.EDU>
References: <553F9DDB.4050401@cs.tcd.ie> <699427215.7347807.1430236125356.JavaMail.yahoo@mail.yahoo.com> <553FB99F.5070609@cs.tcd.ie> <alpine.GSO.1.10.1504291525130.22210@multics.mit.edu>
In-Reply-To: <alpine.GSO.1.10.1504291525130.22210@multics.mit.edu>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/kitten/xz0QkJ5clndBMLsFXA6MzHXGaQM>
Cc: "kitten@ietf.org" <kitten@ietf.org>
Subject: Re: [kitten] AD review of draft-ietf-kitten-sasl-oauth-21
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Apr 2015 21:05:31 -0000


On 29/04/15 20:43, Benjamin Kaduk wrote:
> The server fully validates the client response before generating a server
> response; this will necessarily include the validation steps listed in the
> specification for the OAuth Access Token Type used.  However, additional
> validation steps may be needed, depending on the particular application
> protocol making use of SASL.  In particular, values included as kvpairs in
> the client response (such as host and port) which correspond to values
> known to the application by some other mechanism (such as an application
> protocol data unit or pre-configured values) MUST be validated to match
> between the initial client response and the the other source(s) of such
> information.  As a concrete example, when SASL is used over TLS, the
> hostname can be available via the Server Name Indication TLS extension;
> this hostname must be validated to match the value sent in the 'host'

Yep, that'd work I think.

S.