<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-6man-rfc6724-update" target="https://datatracker.ietf.org/doc/html/draft-ietf-6man-rfc6724-update-15">
   <front>
      <title>Prioritizing known-local IPv6 ULAs through address selection policy</title>
      <author initials="N." surname="Buraglio" fullname="Nick Buraglio">
         <organization>Energy Sciences Network</organization>
      </author>
      <author initials="T." surname="Chown" fullname="Tim Chown">
         <organization>Jisc</organization>
      </author>
      <author initials="J." surname="Duncan" fullname="Jeremy Duncan">
         <organization>Tachyon Dynamics</organization>
      </author>
      <date month="November" day="6" year="2024" />
      <abstract>
	 <t>   This document draws on several years of operational experience to
   update RFC 6724, defining the concept of &quot;known-local&quot; ULA prefixes
   that enable ULA-to-ULA communications within fd00::/8 to become
   preferred over both IPv4-IPv4 and GUA-to-GUA for local use.  The
   document defines the means by which nodes can both identify and
   insert such prefixes into their address selection policy table.  It
   also clarifies the mandatory, unconditional requirement for support
   for Rule 5.5 and demotes the preference for 6to4 addresses.  These
   changes to default behavior improve supportability of common use
   cases, including automatic / unmanaged scenarios, and makes
   preference for IPv6 over IPv4 consistent in local site networks for
   both ULA and GUA prefixes.  It is recognized that some less common
   deployment scenarios may require explicit configuration or custom
   changes to achieve desired operational parameters.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-6man-rfc6724-update-15" />
   
</reference>
