Re: [OAUTH-WG] Alexey Melnikov's Discuss on draft-ietf-oauth-amr-values-05: (with DISCUSS and COMMENT)

Alexey Melnikov <aamelnikov@fastmail.fm> Fri, 03 February 2017 10:16 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 A4F8B129B8A; Fri, 3 Feb 2017 02:16:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level:
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=GbWDdp5G; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=IZ8PONW+
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 VWD3lU4ulQzi; Fri, 3 Feb 2017 02:16:13 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E146D127078; Fri, 3 Feb 2017 02:16:12 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 5788D20BB0; Fri, 3 Feb 2017 05:16:12 -0500 (EST)
Received: from web5 ([10.202.2.215]) by compute7.internal (MEProxy); Fri, 03 Feb 2017 05:16:12 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=q0lT6+H+GCSmWsY209ZxQk4Qs+ c=; b=GbWDdp5GhE3GK0/Q7kjFb9zAKsuECnFvb6CPku6EsjXDM6nTMTCuhJJbBE mu1oZKxinAjO9CQqbijpkshB9UrFIaul/1BIuElmXBKvQn5l/j9R09lmGV54xzTH bAy2gZFjKEwNy/n+939OCMqqhgv8M6MF0Hypw+loVUfaNlp/Y=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=smtpout; bh=q0 lT6+H+GCSmWsY209ZxQk4Qs+c=; b=IZ8PONW+vEnhVmDDTKuV+FI3sC/nLlM/mU cwQgHk72WRJmfcVXyUs/MdEKpLmH7NsDyUib+BWDiHvFqkm5lZPn8yAc6gu7uEYm zRaIxhrSxceC5j2RIFnIOIr0a6N3q0qNtvCiLmCDbYcNho+DL8u4Z/JAJ12On12t LBCaPlMqs=
X-ME-Sender: <xms:bFiUWGUATuJImfnuno9kbA_3jX3tNIqYEb6mrhnASppg08CXXwZCKw>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 2E3DA6ABFB; Fri, 3 Feb 2017 05:16:12 -0500 (EST)
Message-Id: <1486116972.569299.869047696.03427CD3@webmail.messagingengine.com>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: Mike Jones <Michael.Jones@microsoft.com>, The IESG <iesg@ietf.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-e9b51b02
Date: Fri, 03 Feb 2017 10:16:12 +0000
References: <148602274618.28299.16863291767893795433.idtracker@ietfa.amsl.com> <BN3PR03MB2355DFDFA5F06F9479A2FE66F54C0@BN3PR03MB2355.namprd03.prod.outlook.com> <1486048021.331167.868093568.44D5380B@webmail.messagingengine.com> <BN3PR03MB235525F67155805900076665F54C0@BN3PR03MB2355.namprd03.prod.outlook.com>
In-Reply-To: <BN3PR03MB235525F67155805900076665F54C0@BN3PR03MB2355.namprd03.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/-S57y5Ld3DA_4kgUt71AqUsT3vQ>
Cc: oauth-chairs@ietf.org, draft-ietf-oauth-amr-values@ietf.org, oauth@ietf.org
Subject: Re: [OAUTH-WG] Alexey Melnikov's Discuss on draft-ietf-oauth-amr-values-05: (with DISCUSS and COMMENT)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Feb 2017 10:16:15 -0000

On Thu, Feb 2, 2017, at 06:05 PM, Mike Jones wrote:
> I was planning to stay with the characters specified in 6.1 (a)
> https://tools.ietf.org/html/draft-ietf-oauth-amr-values-05#section-6.1:
> 
>    a.  require that Authentication Method Reference values being
>        registered use only printable ASCII characters excluding double
>        quote ('"') and backslash ('\') (the Unicode characters with code
>        points U+0021, U+0023 through U+005B, and U+005D through U+007E),
> 
> That excludes space.  That's the set taken from RFC 7638, Section 6
> https://tools.ietf.org/html/rfc7638#section-6, which is a very related
> usage.
> 
> Space is excluded because sometimes in OAuth messages, values are
> represented as space-separated strings.

I am sorry I misread this earlier: you already exclude space, so the
text as specified is fine.

> 				-- Mike
> 
> -----Original Message-----
> From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm] 
> Sent: Thursday, February 2, 2017 7:07 AM
> To: Mike Jones <Michael.Jones@microsoft.com>;; The IESG <iesg@ietf.org>;
> Cc: draft-ietf-oauth-amr-values@ietf.org; Hannes Tschofenig
> <Hannes.Tschofenig@gmx.net>;; oauth-chairs@ietf.org; oauth@ietf.org
> Subject: Re: Alexey Melnikov's Discuss on draft-ietf-oauth-amr-values-05:
> (with DISCUSS and COMMENT)
> 
> Hi Mike,
> 
> On Thu, Feb 2, 2017, at 03:05 PM, Mike Jones wrote:
> > I'd be OK limiting the protocol elements to using ASCII characters, if 
> > that would be the IESG's preference.
> 
> I think that would be much simpler for everybody.
> 
> I still want to confirm that spaces are allowed in names. Can you
> confirm?
> 
> > 
> > -----Original Message-----
> > From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
> > Sent: Thursday, February 2, 2017 12:06 AM
> > To: The IESG <iesg@ietf.org>;
> > Cc: draft-ietf-oauth-amr-values@ietf.org; Hannes Tschofenig 
> > <Hannes.Tschofenig@gmx.net>;; oauth-chairs@ietf.org; 
> > Hannes.Tschofenig@gmx.net; oauth@ietf.org
> > Subject: Alexey Melnikov's Discuss on draft-ietf-oauth-amr-values-05:
> > (with DISCUSS and COMMENT)
> > 
> > Alexey Melnikov has entered the following ballot position for
> > draft-ietf-oauth-amr-values-05: Discuss
> > 
> > When responding, please keep the subject line intact and reply to all 
> > email addresses included in the To and CC lines. (Feel free to cut 
> > this introductory paragraph, however.)
> > 
> > 
> > Please refer to 
> > https://www.ietf.org/iesg/statement/discuss-criteria.html
> > for more information about IESG DISCUSS and COMMENT positions.
> > 
> > 
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-oauth-amr-values/
> > 
> > 
> > 
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> > 
> > This is a fine document and I support its publication. However I have 
> > a small set of issues that I would like to discuss first.
> > 
> > Are non ASCII names needed? (This is a protocol element, not a human 
> > readable string, so non ASCII is not needed). Are ASCII spaces allowed 
> > in names? More generally: what do you call printable character?
> > 
> > 
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> > 
> > In Section 6.1: suggestion to first describe IANA registration policy, 
> > then describe restrictions on registered names. Otherwise the current 
> > text doesn't flow well.
> > 
> > I am also agreeing with Stephen's DISCUSS.
> > 
> >