<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-6man-pio-pflag" target="https://datatracker.ietf.org/doc/html/draft-ietf-6man-pio-pflag-12">
   <front>
      <title>Signaling DHCPv6 Prefix per Client Availability to Hosts</title>
      <author initials="L." surname="Colitti" fullname="Lorenzo Colitti">
         <organization>Google</organization>
      </author>
      <author initials="J." surname="Linkova" fullname="Jen Linkova">
         <organization>Google</organization>
      </author>
      <author initials="X." surname="Ma" fullname="Xiao Ma">
         <organization>Google</organization>
      </author>
      <author initials="D. E." surname="Lamparter" fullname="David &#x27;equinox&#x27; Lamparter">
         <organization>NetDEF, Inc.</organization>
      </author>
      <date month="October" day="8" year="2024" />
      <abstract>
	 <t>   This document defines a &quot;P&quot; flag in the Prefix Information Option
   (PIO) of IPv6 Router Advertisements (RAs).  The flag is used to
   indicate that the network prefers that clients use the RFC9663
   deployment model instead of using individual adresses in the on-link
   prefix assigned using Stateless Address Autoconfiguration (SLAAC) or
   DHCPv6 address assignment.

   This document updates RFC4862 to indicate that the Autonomous flag in
   a PIO needs to be ignored if the PIO has the P flag set.  It also
   updates RFC4861 to specify that the P flag indicates DHCPv6 Prefix
   Delegation support for clients.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-6man-pio-pflag-12" />
   
</reference>
