This version has had a substantial rewrite on section 2.  The new version
makes it more clear what protocols are used where and gives some of the
reasoning behind the selection of the protocol.

Comments and suggestions are gladly welcomed.

Jim


> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf
> Of [email protected]
> Sent: Monday, July 09, 2012 10:14 AM
> To: [email protected]
> Cc: [email protected]
> Subject: [abfab] I-D Action: draft-ietf-abfab-arch-03.txt
> 
> 
> 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) Architecture
>       Author(s)       : Josh Howlett
>                           Sam Hartman
>                           Hannes Tschofenig
>                           Eliot Lear
>                           Jim Schaad
>       Filename        : draft-ietf-abfab-arch-03.txt
>       Pages           : 44
>       Date            : 2012-07-09
> 
> Abstract:
>    Over the last decade a substantial amount of work has occurred in the
>    space of federated access management.  Most of this effort has
>    focused on two use-cases: network and web-based access.  However, the
>    solutions to these use-cases that have been proposed and deployed
>    tend to have few common building blocks in common.
> 
>    This memo describes an architecture that makes use of extensions to
>    the commonly used security mechanisms for both federated and non-
>    federated access management, including the Remote Authentication Dial
>    In User Service (RADIUS) and the Diameter protocol, the Generic
>    Security Service (GSS), the GS2 family, the Extensible Authentication
>    Protocol (EAP) and the Security Assertion Markup Language (SAML).
>    The architecture addresses the problem of federated access management
>    to primarily non-web-based services, in a manner that will scale to
>    large numbers of identity providers, relying parties, and
>    federations.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-abfab-arch
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-abfab-arch-03
> 
> A diff from previous version is available at:
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-abfab-arch-03
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> abfab mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/abfab

_______________________________________________
abfab mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/abfab

Reply via email to