Re: [abfab] I-D Action: draft-ietf-abfab-usability-ui-considerations-02.txt

[Rhys Smith <[e-mail]>]

Hi all,

I've updated the UI draft, finally. I think it’s now complete. Have written the security considerations section and the error handling section (the last two that needed doing), and tidied up some other bits and pieces.

Would still welcome all feedback and some more comprehensive suggested text for both of those (security considerations & error handling), but if none is forthcoming then in the interests of getting this done and dusted I think it’s good to go. No more TODOs left in the document at least :-)

https://tools.ietf.org/html/draft-ietf-abfab-usability-ui-considerations-02

Best,
Rhys.
--
Dr Rhys Smith
Chief Technical Architect, Trust & Identity
Jisc

T: [phone]
M: [phone]
Skype: rhys-smith
GPG: 0x4638C985
Lumen House, Library Avenue, Harwell Oxford, Didcot, OX11 0SG

jisc.ac.uk

Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.




> On 6 Jul 2015, at 17:04, [e-mail] wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Application Bridging for Federated Access Beyond web Working Group of the IETF.
> 
>        Title           : Application Bridging for Federated Access Beyond web (ABFAB) Usability and User Interface Considerations
>        Author          : Rhys Smith
> 	Filename        : draft-ietf-abfab-usability-ui-considerations-02.txt
> 	Pages           : 21
> 	Date            : 2015-07-06
> 
> Abstract:
>   The real world use of ABFAB-based technologies requires that any
>   identity that is to be used for authentication has to be configured
>   on the ABFAB-enabled client device.  Achieving this requires software
>   on that device (either built into the operating system or a
>   standalone utility) that will interact with the user, managing their
>   identity information and identity-to-service mappings.  All designers
>   of software to fulfil this role will face the same set of challenges.
>   This document aims to document these challenges with the aim of
>   producing well-thought out UIs with some degree of consistency
>   between implementations.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-abfab-usability-ui-considerations/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-abfab-usability-ui-considerations-02
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-abfab-usability-ui-considerations-02
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> abfab mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/abfab
>