<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-rtgwg-dst-src-routing-revive" target="https://datatracker.ietf.org/doc/html/draft-ietf-rtgwg-dst-src-routing-revive-04">
   <front>
      <title>Destination/Source Routing</title>
      <author initials="D. E." surname="Lamparter" fullname="David &#x27;equinox&#x27; Lamparter">
         <organization>NetDEF, Inc.</organization>
      </author>
      <author initials="A." surname="Smirnov" fullname="Anton Smirnov">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="J." surname="Linkova" fullname="Jen Linkova">
         <organization>Google</organization>
      </author>
      <author initials="S." surname="Yang" fullname="Shu Yang">
         <organization>Shenzhen University</organization>
      </author>
      <author initials="M." surname="Xu" fullname="Mingwei Xu">
         <organization>Tsinghua University</organization>
      </author>
      <date month="September" day="14" year="2025" />
      <abstract>
	 <t>   This note specifies using packets&#x27; source addresses in route lookups
   as additional qualifier to be used in hop-by-hop routing decisions.
   This applies to IPv6 [RFC8200] in general with specific
   considerations for routing protocol left for separate documents.
   There is nothing precluding similar operation in IPv4, but this is
   not in scope of this document.

   Note that destination/source routing, source/destination routing,
   SADR, source-specific routing, source-sensitive routing, S/D routing
   and D/S routing are all used synonymously.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-rtgwg-dst-src-routing-revive-04" />
   
</reference>
