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

Mike Jones <Michael.Jones@microsoft.com> Thu, 02 February 2017 15:05 UTC

Return-Path: <Michael.Jones@microsoft.com>
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 39400129459; Thu, 2 Feb 2017 07:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.158
X-Spam-Level:
X-Spam-Status: No, score=-3.158 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.156, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 mv0hmJ57b9yz; Thu, 2 Feb 2017 07:05:21 -0800 (PST)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0103.outbound.protection.outlook.com [104.47.38.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71238129453; Thu, 2 Feb 2017 07:05:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=rII94THAAKSsKMoWMs6M6ZphmjYdgC57pe5qK/6wLAY=; b=o3o0TEOoN4TU4zXkgwWYssMnEqSGRT4PZVugxEOopF1q77a53GDb5ebePI6/+3nAaxrlYg9O7JGZupsPbh3329DmLYHBRpd2RYlzToC7sx3x8wGB3S5mJNZtwRoqDG6IL38yGmT1rkclsUwziueFGK4DnlxFpJgbW9vE7cVCiFg=
Received: from BN3PR03MB2355.namprd03.prod.outlook.com (10.166.74.150) by BN3PR03MB2354.namprd03.prod.outlook.com (10.166.74.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.12; Thu, 2 Feb 2017 15:05:17 +0000
Received: from BN3PR03MB2355.namprd03.prod.outlook.com ([10.166.74.150]) by BN3PR03MB2355.namprd03.prod.outlook.com ([10.166.74.150]) with mapi id 15.01.0874.021; Thu, 2 Feb 2017 15:05:17 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>, The IESG <iesg@ietf.org>
Thread-Topic: Alexey Melnikov's Discuss on draft-ietf-oauth-amr-values-05: (with DISCUSS and COMMENT)
Thread-Index: AQHSfSstZ8gA/avhoUyAuPTivWAUwqFV0P+Q
Date: Thu, 2 Feb 2017 15:05:17 +0000
Message-ID: <BN3PR03MB2355DFDFA5F06F9479A2FE66F54C0@BN3PR03MB2355.namprd03.prod.outlook.com>
References: <148602274618.28299.16863291767893795433.idtracker@ietfa.amsl.com>
In-Reply-To: <148602274618.28299.16863291767893795433.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michael.Jones@microsoft.com;
x-originating-ip: [50.47.95.25]
x-ms-office365-filtering-correlation-id: 705c65c8-b62c-49dd-c1fe-08d44b7ce65c
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:BN3PR03MB2354;
x-microsoft-exchange-diagnostics: 1; BN3PR03MB2354; 7:gAXsN2/S/VqoHtl3hXU/Dq2wnkFBVWEnJV4gucduxXXs7G0Cx+ubRhZbmkEJcTO6q/JkN0j/I2fOatecI/dpHBjm/bOATpV+75OzNMbUyZyr6kWRYicTPosR9A1vau9I74vw25ljeAVy6kHB68gRVLIaDnMZUR4CPYxV0F4OOGpV7c1Bhzk5py2Oe7ZDS5pcAxj8ioYj2VGK6xM3paopyMk1tHVGAS4tzfrWUMkxpwcwFT7vhjMpdG6Y/5VU59QOAKAfUD3TiOWH+mtj1qNWKPXDsRREGskeZxN+D50Gn0JB7q8gvq7n4/7tN9VPDyW41i1ZWzbiqg7Gu972Uu01XoCeiXibE7P36Cu8oR3Hn1LQFxI0csBoWLjBDRsjhBhWmgogX/nL+5VWd44OlZ35rHtU6IAmkpEWC10pqwJBxvhNqJzGKfBU0tKDKTUhlfU9uoaHE2J52ks9wu2k/zE6G6CgOiTPtj+CJvYg+bPyu6gMnp35a/gHxpU1swTGJUvP2NHQVU34J+EXClWpLLWyfFR5uRkgDqw/kgzciV+r5AEWsGeMfFreB5yznuhYTGWl
x-microsoft-antispam-prvs: <BN3PR03MB2354A14F141CF82FAEC65E49F54C0@BN3PR03MB2354.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(131327999870524)(248736688235697);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(61426038)(61427038)(6041248)(20161123564025)(20161123558025)(20161123555025)(20161123562025)(20161123560025)(6072148); SRVR:BN3PR03MB2354; BCL:0; PCL:0; RULEID:; SRVR:BN3PR03MB2354;
x-forefront-prvs: 02065A9E77
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39840400002)(39860400002)(39450400003)(39410400002)(39850400002)(377454003)(189002)(199003)(13464003)(6116002)(53936002)(5001770100001)(97736004)(10090500001)(3846002)(3280700002)(8990500004)(4326007)(2906002)(5005710100001)(106116001)(10290500002)(230783001)(102836003)(7736002)(106356001)(305945005)(105586002)(5660300001)(2950100002)(7696004)(6306002)(3660700001)(77096006)(25786008)(76176999)(189998001)(6436002)(8666007)(6506006)(229853002)(74316002)(55016002)(38730400001)(99286003)(9686003)(54906002)(54356999)(8676002)(122556002)(86362001)(68736007)(81156014)(101416001)(81166006)(86612001)(8936002)(33656002)(66066001)(92566002)(2900100001)(50986999); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR03MB2354; H:BN3PR03MB2355.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Feb 2017 15:05:17.6367 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR03MB2354
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/QX4RdFZ8UbC4Ex8u5Ngnl3XkMMc>
Cc: "oauth-chairs@ietf.org" <oauth-chairs@ietf.org>, "draft-ietf-oauth-amr-values@ietf.org" <draft-ietf-oauth-amr-values@ietf.org>, "oauth@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: Thu, 02 Feb 2017 15:05:23 -0000

I'd be OK limiting the protocol elements to using ASCII characters, if that would be the IESG's preference.

-----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.