Application Bridging for Federated Access Beyond web (ABFAB) Usability and User Interface Considerations

Document Type Replaced Internet-Draft (individual)
Author Rhys Smith 
Last updated 2014-03-05 (latest revision 2013-09-25)
Replaced by draft-ietf-abfab-usability-ui-considerations
Stream (None)
Intended RFC status (None)
Expired & archived
plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-abfab-usability-ui-considerations
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The use of ABFAB-based technologies requires that each user's device is configured with the user's identities that they wish to use in ABFAB transactions. This will require something on that device, either built into the operating system or a standalone utility, that will manage the user's identities and identity to service mappings. Anyone designing that "something" 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.


Rhys Smith (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)