%% You should probably cite draft-baker-ipv6-ospf-dst-flowlabel-routing-03 instead of this revision. @techreport{baker-ipv6-ospf-dst-flowlabel-routing-02, number = {draft-baker-ipv6-ospf-dst-flowlabel-routing-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-baker-ipv6-ospf-dst-flowlabel-routing/02/}, author = {Fred Baker}, title = {{Using OSPFv3 with Role-Based Access Control}}, pagetotal = 10, year = 2013, month = may, day = 2, abstract = {This note describes the changes necessary for OSPFv3 to route classes of IPv6 traffic that are defined by an IPv6 Flow Label and a destination prefix. This implies not simply routing "to a destination", but "traffic going to that destination AND using a specified flow label". It may be combined with other qualifying attributes, such as "traffic going to that destination AND using a specified flow label AND from a specified source prefix". 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), it in effect has no route to that destination, thus providing an access list that is as changeable and scalable as routing.}, }