Federated Identity for IPv6 Role-base Access Control
draft-baker-openstack-rbac-federated-identity-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Baker | ||
| Last updated | 2015-04-20 (Latest revision 2014-10-17) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This note describes an IPv6 option intended to carry a Federated Identity for use in Role-Based Access Control. Rather than identify a person, it identifies a group of systems that the sender is a member of. Role-Based Access Control permits specified sets of systems to communicate with other specified sets of systems, with the intention of scalability.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)