Re: [kitten] Ben Campbell's No Objection on draft-ietf-kitten-sasl-oauth-22: (with COMMENT)

Bill Mills <wmills_92105@yahoo.com> Thu, 28 May 2015 18:23 UTC

Return-Path: <wmills_92105@yahoo.com>
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 E54641A006D for <kitten@ietfa.amsl.com>; Thu, 28 May 2015 11:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.175
X-Spam-Level:
X-Spam-Status: No, score=-1.175 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO_END_DIGIT=0.25, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 ZR3_yIaZgVnF for <kitten@ietfa.amsl.com>; Thu, 28 May 2015 11:23:21 -0700 (PDT)
Received: from nm44-vm9.bullet.mail.gq1.yahoo.com (nm44-vm9.bullet.mail.gq1.yahoo.com [67.195.87.214]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D72851A011B for <kitten@ietf.org>; Thu, 28 May 2015 11:23:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1432837398; bh=BFNQhKv8+I8xcQfdm5Ip8hA4Lh+cuCA95shdVTY0yLA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=khBIGzUwRKeuy/mv0Kow0pPX7BTIDDieEJHfZD7ru0B9HBBx++hgNpOM2T+DvaRoCgQPefT2HbLAJA7nqMalRzrGJwCAa4cD7WePdCiyleCmLCXf1ejXsW3oZ53r9nd5MiikFSYL/s8y63/F4gHuDub4vfs95F/oFkMEMPiFUGkCYpBWcT7zC7FzP73wKyEbCcs08Pwg1bPLCwdmPa3MtrLhzjp6hfaRqnzm0scCJrCaYGSE2X0sxBc1RHhNTXN4uYjk1VAx2NCjj7BFykqHLC9mPkkgJ8rqS1eLT3ZT4rD/RcJ3q4wit7i27MAm+BDvasG7tBcaiI7dqxy+JxuxZQ==
Received: from [127.0.0.1] by nm44.bullet.mail.gq1.yahoo.com with NNFMP; 28 May 2015 18:23:18 -0000
Received: from [98.137.12.191] by nm44.bullet.mail.gq1.yahoo.com with NNFMP; 28 May 2015 18:20:27 -0000
Received: from [66.196.81.173] by tm12.bullet.mail.gq1.yahoo.com with NNFMP; 28 May 2015 18:20:27 -0000
Received: from [98.139.212.240] by tm19.bullet.mail.bf1.yahoo.com with NNFMP; 28 May 2015 18:20:27 -0000
Received: from [127.0.0.1] by omp1049.mail.bf1.yahoo.com with NNFMP; 28 May 2015 18:20:27 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 461654.79261.bm@omp1049.mail.bf1.yahoo.com
X-YMail-OSG: VpggOq8VM1mHQ4nksq1Ev56RmKE5f._gnNhlyQWTMmHug5zlDndwCCpbCO.lniS xX8b_R.nyS6m96FzcxXwj.HvljjiILz.kJbYeY5S4JmEZdJH_mFLnidR1wPb5XyjicL2zYuzj_Gp FI_0J9QjhL0RAKQJLcEdsCTSEh_pC165.hns7rxi4NJG4RNXExpAZkCz4cVpF9hugzO1e8ikToew eeSs4mMT9O7LYtAdPycHm8qj.EA7azNPIedgy_POmEPWxJQ3bKnEHziHf4THe7SPccNrCxTKn.iK mlfnqPTt3fbRx479UNFkdaHJyWDxzRcVGpnur0Nf88k_fW5a6.nE8jRNGAULKh6_OUYj395ep5K4 0vjzqwRVuGr28lpl1M.xAZfv4meTR65W6VfQjghrWpzI0JHchR0vG5ZXyGM2GFNopOzGCLzrgpYC lh7xebB.E7LC6qiB8RdyB1TURw6kjz91RkNzlXfCV9QRvbegod67e1yavAUfd8cePfTwTcPkSeO_ OtzKOSrqKmUI1OWdN
Received: by 66.196.80.120; Thu, 28 May 2015 18:20:27 +0000
Date: Thu, 28 May 2015 18:17:37 +0000 (UTC)
From: Bill Mills <wmills_92105@yahoo.com>
To: Benjamin Kaduk <kaduk@MIT.EDU>, Ben Campbell <ben@nostrum.com>
Message-ID: <1076402811.687497.1432837057605.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <alpine.GSO.1.10.1505272351080.22210@multics.mit.edu>
References: <alpine.GSO.1.10.1505272351080.22210@multics.mit.edu>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_687496_66331018.1432837057601"
Archived-At: <http://mailarchive.ietf.org/arch/msg/kitten/DbTq_6CQ5ciHYeN_p1l48jblTm8>
Cc: "kitten-chairs@ietf.org" <kitten-chairs@ietf.org>, "draft-ietf-kitten-sasl-oauth.shepherd@ietf.org" <draft-ietf-kitten-sasl-oauth.shepherd@ietf.org>, "kitten@ietf.org" <kitten@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-kitten-sasl-oauth@ietf.org" <draft-ietf-kitten-sasl-oauth@ietf.org>, "draft-ietf-kitten-sasl-oauth.ad@ietf.org" <draft-ietf-kitten-sasl-oauth.ad@ietf.org>
Subject: Re: [kitten] Ben Campbell's No Objection on draft-ietf-kitten-sasl-oauth-22: (with COMMENT)
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Bill Mills <wmills_92105@yahoo.com>
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: Thu, 28 May 2015 18:23:23 -0000

 Responses inline below tagged with [[WMILLS]]


     On Wednesday, May 27, 2015 8:56 PM, Benjamin Kaduk <kaduk@MIT.EDU> wrote:
   

 Hi Ben,

On Wed, 27 May 2015, Ben Campbell wrote:

> Hi, thanks for the response. A few comments below. I removed sections that do
> not seem to need further discussion.
>
> On 27 May 2015, at 17:49, Bill Mills wrote:
>
> [...]
>
> > >  > -- 3: "Such a new SASL OAuth mechanism can be added by simply>  
> > >  registering the new name(s)"> > Register them where?
> > s/by simply registering the new name(s)/by registering the new name(s) with
> > IANA/
> > change made in my working copy.
>
> Sorry, I guess I was asking for which registry at IANA.

The SASL Mechanisms registry; the only one affected by this document.
[[WMILLS]] changed wording to "registering the new name(s) with IANA in the SASL Mechanisms registry"

> > >  > -- 3.2, 2nd paragraph : "... known to the application."> > Known to the
> > > "resource server"?
> > this is server config and in protocol data that the app could have, so I'd
> > rather leave this as "application" but if there's strong desire for
> > "resource server" I'll make the change.
>
> Do I understand correctly that we are talking about matching things like host
> and port sent by the client to things the server "knows" through other
> channels?  It seems like "application" could mean application at the client as
> well as the server, or even the combination of both. Maybe "application
> server"? (Or maybe I've missed the intent?)

Things like host and port that could be extracted from the OS or http
stack or similar, yes.  I don't particularly care for "resource server"
here, but "application server" seems unobjectionable.

[[wmills]] WFM "application server" it is.

> > >  > Editorial Stuff:> > -- 3.1, "Port":> > I assume that means the
> > > destination port to which the client connected?> (similar to Host?)> > --
> > > 3.1.1 "Post": default value is "". > > Does "" represent an empty string?
> > Yes, does this need to be spelled out?
>
> "Need" might be too strong a word, but I think a description like "empty"
> would be more clear than '""'.

[[WMILLS]] changed those to "the default value is the empty string ("")."

I agree that it's probably worth doing "destination port to which the
client connected".  I have no strong feelings regarding the way in which
the empty string is described.
[[WMILLS]] WFM now "Contains the destination port that the client connected to, represented as a  decimal positive integer string without leading zeros."

> > >  > -- 3.2, first sentence"> > s/" ... according the specification..." /
> > > "... according to the specification..."
>
> [...]

Indeed.

-Ben