<?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-05">
   <front>
      <title>Preference for IPv6 ULAs over IPv4 addresses in RFC6724</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="December" day="22" year="2023" />
      <abstract>
	 <t>   When [RFC6724] was published it defined an address selection
   algorithm along with a default policy table, and noted a number of
   examples where that policy table might benefit from adjustment for
   specific scenarios.  It also noted that it is important for
   implementations to provide a way to change the default policies as
   more experience is gained.  This update draws on several years of
   operational experience to refine RFC 6724 further, with particular
   emphasis on preference for the use of ULA addresses over IPv4
   addresses and the addition of mandatory support for Rule 5.5.  The
   update also demotes the preference for 6to4 addresses.  The changes
   to default behavior improve supportability of common use cases,
   including automatic / unmanaged scenarios.  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-05" />
   
</reference>
