Using IS-IS with Role-Based Access Control
draft-baker-ipv6-isis-dst-flowlabel-routing-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Baker | ||
| Last updated | 2013-08-21 (Latest revision 2013-02-17) | ||
| RFC stream | (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 the changes necessary for IS-IS to route classes of IPv6 traffic that are defined by an IPv6 Flow Label and a destination prefix. This implies not routing "to a destination", but "traffic matching a classification tuple". The obvious application is data center inter-tenant routing using a form of role-based access control. If the sender doesn't know the value to insert in the flow label (the receiver's tenant ID), he in effect has no route to that destination.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)