40 likes | 158 Vues
This document discusses the recent updates and refinements made to usability and user interface (UI) considerations for ABFAB identity selectors. It clarifies misconceptions between identity selector mechanisms and GSS-API mechanisms while emphasizing that effective HCI/UX design is essential and not superseded by this document. Key updates include language tidying, addressing potential UI issues, and new requirements regarding identity storage. Ongoing work includes enhancements to error handling and security/privacy sections, ensuring that the document is clear and usable for developers and implementers.
E N D
draft-ietf-abfab-usability-ui-considerations Rhys Smith IETF 90, Toronto
Status • Now wg doc -01 • Various updates since -00 • Nearly there, I think.
Changes • Tidying up language throughout • Finished most of TODOs • Added language that tries to explain that this document is not a substitute for good HCI/UX design. • Changed terminology slightly to avoid confusion between an identity selector "mechanism" and a GSS-API mechanism. • Added caveat about potential for the UI to show the identity currently in use for a particular service. • Added a requirement that the identity selector must not store the same NAI for multiple identities. • Stopped talking about "provisioning" after saying that I wouldn’t talk about "provisioning".
What’s Left? • Errors section (have volunteer) • Security/Privacy sections