Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: email@example.com, The IESG <firstname.lastname@example.org>, Marc Blanchet <Marc.Blanchet@viagenie.ca>, email@example.com, Marc.Blanchet@viagenie.ca, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Protocol Action: 'Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords' to Proposed Standard (draft-ietf-precis-7613bis-11.txt) The IESG has approved the following document: - 'Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords' (draft-ietf-precis-7613bis-11.txt) as Proposed Standard This document is the product of the Preparation and Comparison of Internationalized Strings Working Group. The IESG contact persons are Adam Roach, Alexey Melnikov and Ben Campbell. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-precis-7613bis/
Technical Summary This document is part of a set of revised RFCs (7564, 7613, 7700), based on implementation experience. 7564 is the base Precis protocol, 7613 and 7700 are profiles for specific use (username/passwords and nicknames respectively). This revised document, the Precis profile for username and passwords, essentially clarifies the original specification and make it synchronized with the revised base spec, specially regarding case mapping. Working Group Summary Multiple versions of the revised spec was discussed over more than a year in the working group mailing list. As a clarification of the original profile specification, there was no real contention on the document. A discussion happened on a desirable property of being idempotent, but the discussion went that this is a desirable property, not an absolute requirment. Document Quality RFC 7613 is referenced by a number of protocols heavily implemented and deployed protocols. It is reasonable to expect the same for this document. Personnel The document shepherd is Marc Blanchet. The responsible AD is Ben Campbell.