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:[email protected]] > Sent: Thursday, February 2, 2017 12:06 AM > To: The IESG <[email protected]> > Cc: [email protected]; Hannes Tschofenig > <[email protected]>; [email protected]; > [email protected]; [email protected] > 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. > > _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
