<?xml version="1.0" encoding="US-ASCII"?>
<!-- edited with XMLSPY v5 rel. 3 U (http://www.xmlspy.com)
     by Daniel M Kohn (private) -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
]>
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-ma-6man-ra-dns64-flag-00" ipr="trust200902">
  <front>
    <title abbrev="DNS64 flag for DNS RA Option">Updates to DNS64
    Functionality Advertisement for DNS RA Option</title>

    <author fullname="Chenhao Ma" initials="C" surname="Ma">
      <organization>China Telecom</organization>

      <address>
        <postal>
          <street>Beiqijia Town, Changping District</street>

          <city>Beijing</city>

          <code>102209</code>

          <country>China</country>
        </postal>

        <email>machh@chinatelecom.cn</email>
      </address>
    </author>

    <author fullname="Chongfeng Xie" initials="C" surname="Xie">
      <organization>China Telecom</organization>

      <address>
        <postal>
          <street>Beiqijia Town, Changping District</street>

          <city>Beijing</city>

          <code>102209</code>

          <country>China</country>
        </postal>

        <email>xiechf@cernet.edu.cn</email>
      </address>
    </author>

    <date day="29" month="August" year="2025"/>

    <area>Internet Area</area>

    <workgroup>IPv6 Maintenance</workgroup>

    <keyword>IPv6-only DNS64</keyword>

    <abstract>
      <t>This document defines a new flag in the DNS RA Option to advertise
      the DNS64 functionality. This extension enables automatic configuration
      of DNS64 resolution, improving deployability in IPv6 transition
      scenarios.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>DNS Extensions for Network Address Translation from IPv6 clients to
      IPv4 servers (DNS64)<xref target="RFC6147"/> is a widely deployed
      mechanism for IPv6-only networks requiring access to IPv4-only services.
      <xref target="I-D.ma-v6ops-5g-ipv6only"/>introduce the reasons for using
      RA to deliver DNS64 address configuration. This document defines a new
      flag in the DNS RA option<xref target="RFC8106"/> to communicate DNS64
      server address to hosts.</t>

      <section title="Requirements Language">
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
        "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
        "OPTIONAL" in this document are to be interpreted as described in BCP
        14<xref target="RFC2119"/> <xref target="RFC8174"/> when, and only
        when, they appear in all capitals, as shown here.</t>
      </section>
    </section>

    <section title="DNS64 Flag">
      <t>Based on <xref target="RFC8106"/>, this specification introduces a
      'T' flag bit allocated in the leftmost bit of the Reserved field to
      signal the presence of DNS64 server addresses in the option payload.
      Figure 1 shows the format of the DNS64 option.</t>

      <figure align="left">
        <artwork name=""><![CDATA[0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     Type      |    Length     |T|         Reserved            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                        Lifetime                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
|            DNS64 Server Address(es) (128-bit IPv6)            |
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 Figure 1:DNS64 RA Option format                                              ]]></artwork>
      </figure>

      <t>Fields:<list style="symbols">
          <t>Type: 8-bit identifier: 25</t>

          <t>Length: 8-bit unsigned integer. </t>

          <t>Flag T: 1-bit integer. set to indicate DNS64 server addresses are
          in the option payload.</t>

          <t>Lifetime: 32-bit unsigned integer. </t>

          <t>DNS64 Server Address(es): One or more 128-bit IPv6 addresses of
          the DNS64. </t>
        </list></t>
    </section>

    <section title="Security Considerations">
      <t>This memo does not introduce any new security problems.
      Considerations are described in Section 7 in <xref
      target="RFC8106"/></t>
    </section>

    <section title="IANA Considerations">
      <t>This document requests allocation for the Flag T.</t>
    </section>

    <section title="Acknowledgements">
      <t>The comments and suggestions of the following are gratefully
      acknowledged:</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc include='reference.RFC.2119'?>

      <?rfc include='reference.RFC.6147'?>

      <?rfc include='reference.RFC.8106'?>

      <?rfc include='reference.RFC.8174'?>

      <?rfc include='reference.RFC.4861'?>
    </references>

    <references title="Informative References">
      <?rfc include='reference.I-D.ma-v6ops-5g-ipv6only'?>
    </references>
  </back>
</rfc>
