%% You should probably cite draft-baker-ipv6-ospf-dst-src-routing-03 instead of this revision. @techreport{baker-ipv6-ospf-dst-src-routing-01, number = {draft-baker-ipv6-ospf-dst-src-routing-01}, 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-src-routing/01/}, author = {Fred Baker}, title = {{IPv6 Source/Destination Routing using OSPFv3}}, 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 source prefix and a destination prefix. This implies not simply routing "to a destination", but "traffic going to that destination AND coming from a specified source". 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 egress routing, as required for a multihomed entity with a provider-allocated prefix from each of several upstream networks. Traffic within the network could be source/destination routed as well, or could be routed from "any prefix", ::/0. If traffic is routed from the relevant PA prefixes but in fact has a source address that is in none of them, the traffic in effect has no route.}, }