<?xml version="1.0" encoding="utf-8"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude"
     version="3"
     ipr="trust200902"
     docName="draft-spiriyath-dhc-ai-gateway-uri-00"
     category="std"
     submissionType="IETF"
     xml:lang="en">
  <front>
    <title abbrev="DHCP AI Gateway URI">
      DHCP and DHCPv6 Options for an AI Gateway URI
    </title>
    <seriesInfo name="Internet-Draft"
                value="draft-spiriyath-dhc-ai-gateway-uri-00"/>
    <author initials="S." surname="Piriyath" fullname="Shibu Piriyath">
      <organization>Nile Global, Inc.</organization>
      <address>
        <email>shibupiriyath@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="12"/>
    <area>Internet</area>
    <workgroup>Dynamic Host Configuration</workgroup>
    <keyword>DHCP</keyword>
    <keyword>DHCPv6</keyword>
    <keyword>AI gateway</keyword>
    <keyword>forward proxy</keyword>
    <abstract>
      <t>
        This document specifies a DHCPv4 option and a DHCPv6 option that
        carry the HTTPS URI of an AI gateway descriptor. The descriptor
        is a Provisioning Domain Additional Information document. It
        identifies a forward proxy and the destinations for which that
        proxy is to be used. The DHCP options do not carry proxy
        credentials, model identifiers, or a Proxy Auto-Configuration
        script.
      </t>
    </abstract>
    <note removeInRFC="true">
      <name>Discussion Venues</name>
      <t>
        This is an individual submission. It has not been adopted by
        the Dynamic Host Configuration (DHC) Working Group. Discussion
        of this document is directed to the author.
      </t>
    </note>
  </front>
  <middle>
    <section>
      <name>Introduction</name>
      <t>
        Clients on an enterprise network increasingly reach model
        providers through an organizational AI gateway operated as a
        forward proxy. The gateway is not the general HTTP proxy for
        the network. It is used only for a set of AI provider
        destinations. Those destinations, and the gateway's address,
        change more often than endpoint configuration can be updated
        by hand.
      </t>
      <t>
        Existing mechanisms do not provide this advertisement:
      </t>
      <ul>
        <li>
          <t>
            The Web Proxy Auto-Discovery Protocol (WPAD)
            <xref target="RFC3040"/> distributes the URL of a
            JavaScript Proxy Auto-Configuration (PAC) file. Common
            DHCPv4 implementations carry that URL in option code 252,
            a site-specific code in the range 224-254
            <xref target="RFC3942"/> that is not a standards-track
            option. There is no corresponding DHCPv6 option. WPAD
            names a general web proxy, and support outside Windows
            HTTP stacks is inconsistent.
          </t>
        </li>
        <li>
          <t>
            <xref target="I-D.ietf-intarea-proxy-config"/> defines
            Provisioning Domain (PvD) keys that describe proxy URI
            templates and the destinations those proxies serve. A
            network can advertise a PvD identifier in a Router
            Advertisement <xref target="RFC8801"/>; the client then
            fetches the document over HTTPS. The document does not
            define a DHCP option. It also requires that a client not automatically
            send traffic to a network-advertised proxy unless local
            policy allows that proxy.
          </t>
        </li>
        <li>
          <t>
            <xref target="I-D.su-ai-gateway-discovery"/> defines
            DNS-Based Service Discovery for an AI gateway that is an
            HTTP API router on the local link. That advertisement
            carries a host, a port, and a mount path. It profiles
            link-local multicast DNS, although DNS-SD can also be
            served by unicast DNS or a discovery proxy
            <xref target="RFC8766"/>. It does not name a forward
            proxy.
          </t>
        </li>
        <li>
          <t>
            <xref target="I-D.yang-dhc-dhcp-extension"/> defines a
            DHCP option for a campus device that hosts a model used
            by network operations. The option carries model size and
            price. It is not a client forward-proxy advertisement.
          </t>
        </li>
      </ul>
      <t>
        This document follows the pattern of
        <xref target="RFC8910"/>. DHCP carries a URI. The client
        retrieves the operational data over HTTPS. The operational
        data is the PvD Additional Information document of
        <xref target="I-D.ietf-intarea-proxy-config"/>, with one
        additional proxy key, "purpose", whose value "ai-gateway"
        distinguishes this proxy from a general web proxy.
      </t>
    </section>
    <section>
      <name>Requirements Language</name>
      <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 anchor="terminology">
      <name>Terminology</name>
      <t>
        AI gateway:
        A forward proxy that a client uses for traffic to AI provider
        destinations named by the gateway descriptor. This document
        does not use the term for an API router discovered by
        <xref target="I-D.su-ai-gateway-discovery"/>.
      </t>
      <t>
        Gateway descriptor:
        A PvD Additional Information document
        <xref target="RFC8801"/> retrieved from the URI carried by
        the option defined in this document.
      </t>
      <t>
        Client:
        A DHCP or DHCPv6 client that requests the option, or the
        application that consumes the resulting descriptor. This
        document does not require every host DHCP stack to interpret
        the option. Applications MAY retrieve the option value
        through the host configuration API.
      </t>
    </section>
    <section>
      <name>Option Format</name>
      <t>
        Both options carry the same URI. The URI is encoded as
        UTF-8 <xref target="RFC3629"/> with no terminating NUL.
      </t>
      <section>
        <name>DHCPv4 Option</name>
        <t>
          The DHCPv4 option code is OPTION_AI_GATEWAY_URI (TBD1).
          Its format is:
        </t>
        <figure>
          <artwork type="ascii-art"><![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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     Code      |     Len       |                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |
|                   URI (UTF-8, no NUL)                         |
|                            ...                                |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
          ]]></artwork>
        </figure>
        <dl>
          <dt>Code</dt>
          <dd>OPTION_AI_GATEWAY_URI (TBD1), one octet.</dd>
          <dt>Len</dt>
          <dd>Length of the URI in octets, one octet.</dd>
          <dt>URI</dt>
          <dd>
            The gateway descriptor URI. If the URI exceeds the
            length that fits in one option, the option is
            concatenated as specified in <xref target="RFC3396"/>.
          </dd>
        </dl>
      </section>
      <section>
        <name>DHCPv6 Option</name>
        <t>
          The DHCPv6 option code is OPTION_AI_GATEWAY_URI (TBD2).
          Its format is:
        </t>
        <figure>
          <artwork type="ascii-art"><![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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_AI_GATEWAY_URI (TBD2)  |          option-len           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                     URI (UTF-8, no NUL)                       |
|                              ...                              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
          ]]></artwork>
        </figure>
        <dl>
          <dt>option-code</dt>
          <dd>OPTION_AI_GATEWAY_URI (TBD2), 16 bits.</dd>
          <dt>option-len</dt>
          <dd>Length of the URI in octets, 16 bits.</dd>
          <dt>URI</dt>
          <dd>The gateway descriptor URI.</dd>
        </dl>
      </section>
      <section anchor="uri-constraints">
        <name>URI Constraints</name>
        <t>
          The URI MUST use the "https" scheme. A client MUST discard
          a value that is empty, that is not a valid URI, or whose
          scheme is not "https".
        </t>
        <t>
          The URI MUST NOT contain userinfo (a username or
          password). A client MUST discard a URI that contains
          userinfo.
        </t>
        <t>
          A typical value is:
        </t>
        <figure>
          <artwork type="ascii-art"><![CDATA[
https://ai-gw.example.com/.well-known/pvd
          ]]></artwork>
        </figure>
        <t>
          The path "/.well-known/pvd" is the well-known PvD URI
          defined in <xref target="RFC8801"/> and the location from
          which <xref target="I-D.ietf-intarea-proxy-config"/>
          retrieves proxy PvD information. A deployment MAY use
          another HTTPS path on the gateway host; the host matching
          rule in <xref target="client"/> still applies. This
          document does not register a new well-known URI.
        </t>
        <t>
          Each DHCPv4 option occurrence carries one URI. If the URI
          exceeds the length that fits in one occurrence, the server
          splits it as specified in <xref target="RFC3396"/>. A
          DHCPv4 client concatenates those occurrences into a
          single URI <xref target="RFC3396"/> and MUST NOT treat
          them as a list of URIs. DHCPv4 therefore carries at most
          one URI.
        </t>
        <t>
          A DHCPv6 server MAY send more than one instance of
          OPTION_AI_GATEWAY_URI. The order of instances is the
          server's preference order, highest preference first. A
          DHCPv6 client tries the URIs in that order and stops at
          the first descriptor it accepts.
        </t>
      </section>
    </section>
    <section>
      <name>Server Behavior</name>
      <t>
        A DHCPv4 server includes OPTION_AI_GATEWAY_URI only in a
        response to a client whose Parameter Request List
        <xref target="RFC2132"/> contains TBD1, and only when the
        server is configured with at least one URI for that client
        or link. Otherwise the server MUST NOT include the option.
        The server includes a single URI. If that URI does not fit
        in one occurrence, the server splits it as specified in
        <xref target="RFC3396"/>.
      </t>
      <t>
        A DHCPv6 server includes OPTION_AI_GATEWAY_URI only in a
        response to a client whose Option Request option
        <xref target="RFC9915"/> contains TBD2, and only when the
        server is configured with at least one URI. Otherwise the
        server MUST NOT include the option. The option MAY appear
        in Advertise and Reply messages, including a Reply to
        Information-request. If the server is configured with more
        than one URI, it MAY include one instance per URI, in
        preference order as specified in
        <xref target="uri-constraints"/>.
      </t>
      <t>
        The option value is configuration. This document does not
        define a new DHCP message type. Servers SHOULD allow the
        URI list to vary by link or by client class, so that a
        gateway appropriate to one segment is not advertised on
        another.
      </t>
    </section>
    <section anchor="client">
      <name>Client Behavior</name>
      <t>
        A client that wants the advertisement includes TBD1 in its
        DHCPv4 Parameter Request List, or TBD2 in its DHCPv6 Option
        Request option. A client that did not request the option
        MUST ignore it if a server sends it.
      </t>
      <t>
        On receiving one or more accepted URIs, the client fetches
        the descriptor with HTTP GET over TLS. The request SHOULD
        include:
      </t>
      <figure>
        <artwork type="ascii-art"><![CDATA[
Accept: application/pvd+json
        ]]></artwork>
      </figure>
      <t>
        The client MUST authenticate the TLS server and MUST verify
        that the certificate matches the hostname of the URI
        <xref target="RFC9110"/> <xref target="RFC9525"/>. A client
        MUST NOT follow a redirect to a URI whose scheme is not
        "https" or whose host is not acceptable under local policy.
      </t>
      <t>
        The client MUST discard a descriptor unless the host of the
        option URI, the descriptor "identifier" (without the
        trailing dot), and the hostname of each "ai-gateway"
        proxy entry are identical. For "https-connect" and
        "http-connect", that hostname is the host in the
        "host:port" value, not including the port. For a URI
        template, it is the host of the URI. This is the hostname,
        PvD identifier, and certificate match required by
        <xref target="I-D.ietf-intarea-proxy-config"/>.
      </t>
      <t>
        The client uses a proxy from the descriptor only when all
        of the following are true:
      </t>
      <ol>
        <li>
          <t>
            The proxy dictionary contains "purpose" with the value
            "ai-gateway".
          </t>
        </li>
        <li>
          <t>
            A "proxy-match" rule
            <xref target="I-D.ietf-intarea-proxy-config"/> selects
            that proxy for the destination.
          </t>
        </li>
        <li>
          <t>
            Local policy or an explicit user action allows the use
            of that proxy hostname. Receipt of the DHCP option is
            not by itself permission to send traffic or credentials
            to the proxy. This is the same constraint
            <xref target="I-D.ietf-intarea-proxy-config"/> places on
            proxies learned from a network PvD.
          </t>
        </li>
      </ol>
      <t>
        The client MUST NOT install the advertised proxy as the
        system HTTP or HTTPS proxy. Destinations that no
        "proxy-match" rule maps to an "ai-gateway" proxy are
        contacted directly, or through whatever proxy local policy
        already configured.
      </t>
      <t>
        If every URI fails validation or retrieval, the client
        continues without an AI gateway. Failure to discover a
        gateway is not treated as a requirement to block the
        connection.
      </t>
      <t>
        The client SHOULD refresh the descriptor when the DHCP
        lease is renewed and when the descriptor "expires" time
        <xref target="RFC8801"/> is reached. It MUST apply the
        randomized backoff required by <xref target="RFC8801"/>
        when refreshing because of expiry.
      </t>
    </section>
    <section>
      <name>Gateway Descriptor</name>
      <t>
        The descriptor is a PvD Additional Information object
        <xref target="RFC8801"/> containing the "proxies" and
        "proxy-match" keys defined by
        <xref target="I-D.ietf-intarea-proxy-config"/>.
      </t>
      <t>
        This document defines one additional key, "purpose", used
        inside a proxy dictionary. The key's value is a string.
        The value "ai-gateway" means the proxy is an AI forward
        proxy as defined in <xref target="terminology"/>. Other
        values are reserved for future registration.
      </t>
      <t>
        An example descriptor is:
      </t>
      <figure>
        <artwork type="ascii-art"><![CDATA[
{
  "identifier": "ai-gw.example.com.",
  "expires": "2027-05-15T00:00:00Z",
  "prefixes": [],
  "proxies": [
    {
      "protocol": "https-connect",
      "proxy": "ai-gw.example.com:443",
      "identifier": "ai-gw",
      "purpose": "ai-gateway",
      "mandatory": [ "purpose" ]
    }
  ],
  "proxy-match": [
    {
      "domains": [ "api.openai.com", "*.anthropic.com" ],
      "proxies": [ "ai-gw" ]
    },
    {
      "proxies": []
    }
  ]
}
        ]]></artwork>
      </figure>
      <t>
        In this example the client uses ai-gw.example.com, port
        443, with HTTP CONNECT over TLS, and only for the named
        domains. The final rule selects no proxy, so every other
        destination is contacted directly.
      </t>
      <t>
        A descriptor MUST list "purpose" in the "mandatory" array
        <xref target="I-D.ietf-intarea-proxy-config"/> of every
        proxy dictionary that carries it. A client that implements
        <xref target="I-D.ietf-intarea-proxy-config"/> but not this
        document then ignores the dictionary instead of using the
        AI gateway as an ordinary proxy.
      </t>
      <t>
        The descriptor MUST NOT contain client credentials, API
        keys, or model pricing. Model catalogs are retrieved, if
        at all, from the gateway after the client has been
        authorized to use it.
      </t>
    </section>
    <section anchor="sec-security">
      <name>Security Considerations</name>
      <t>
        DHCP and DHCPv6 are unauthenticated unless a deployment
        adds its own protection. An attacker who can answer DHCP
        on the link can supply a URI. This option therefore does
        not authorize use of the named host. Authorization is the
        combination of a validated HTTPS certificate and local
        policy that allows that hostname, as required in
        <xref target="client"/>.
      </t>
      <t>
        Operators SHOULD prevent rogue DHCP servers on access
        networks. That is a property of the access network. This
        document does not require DHCP authentication
        <xref target="RFC3118"/>, which is not widely deployed.
      </t>
      <t>
        The option carries a name, not a raw address, so that the
        TLS certificate can be checked against a stable name. A
        client MUST NOT accept an "https" URI whose authority is
        an IP address unless local policy explicitly allows that
        address and the certificate matches it.
      </t>
      <t>
        A malicious descriptor can list destinations that the
        client did not intend to proxy. Clients MUST only narrow
        or select among destinations that local policy already
        permits to be sent to that proxy. A descriptor MUST NOT
        cause the client to proxy traffic that local policy sends
        direct or to a different proxy. This is the narrowing rule
        in <xref target="I-D.ietf-intarea-proxy-config"/>.
      </t>
      <t>
        Because the gateway sees the destinations it proxies,
        local policy should allow an AI gateway only for the
        provider names the organization intends to inspect.
        Advertising the gateway through DHCP does not expand that
        set.
      </t>
      <t>
        The option is requested explicitly. Servers do not attach
        it to every lease. This limits exposure to clients that
        implement the option, and it avoids changing the behavior
        of hosts that only implement WPAD.
      </t>
    </section>
    <section anchor="sec-iana">
      <name>IANA Considerations</name>
      <section>
        <name>DHCPv4 Option</name>
        <t>
          IANA is requested to assign a new option code from the
          "BOOTP Vendor Extensions and DHCP Options" registry
          (https://www.iana.org/assignments/bootp-dhcp-parameters)
          as follows:
        </t>
        <table>
          <thead>
            <tr>
              <th>Tag</th>
              <th>Name</th>
              <th>Data Length</th>
              <th>Meaning</th>
              <th>Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>TBD1</td>
              <td>OPTION_AI_GATEWAY_URI</td>
              <td>N</td>
              <td>HTTPS URI of an AI gateway descriptor</td>
              <td>This document</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section>
        <name>DHCPv6 Option</name>
        <t>
          IANA is requested to assign a new option code from the
          "Option Codes" registry under "Dynamic Host Configuration
          Protocol for IPv6 (DHCPv6)"
          (https://www.iana.org/assignments/dhcpv6-parameters)
          as follows:
        </t>
        <table>
          <thead>
            <tr>
              <th>Value</th>
              <th>Description</th>
              <th>Client ORO</th>
              <th>Singleton</th>
              <th>Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>TBD2</td>
              <td>OPTION_AI_GATEWAY_URI</td>
              <td>Yes</td>
              <td>No</td>
              <td>This document</td>
            </tr>
          </tbody>
        </table>
        <t>
          The option is not a singleton: more than one instance
          MAY appear, in preference order.
        </t>
      </section>
      <section>
        <name>PvD Proxy Key</name>
        <t>
          IANA is requested to register the following key in the
          "Proxy Information PvD Keys" registry established by
          <xref target="I-D.ietf-intarea-proxy-config"/>:
        </t>
        <table>
          <thead>
            <tr>
              <th>JSON Key</th>
              <th>Optional/Required</th>
              <th>Description</th>
              <th>Type</th>
              <th>Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>purpose</td>
              <td>optional</td>
              <td>
                Role of this proxy. The value "ai-gateway"
                identifies an AI forward proxy.
              </td>
              <td>String</td>
              <td>This document</td>
            </tr>
          </tbody>
        </table>
        <t>
          IANA is requested to create a registry titled "AI Gateway
          Proxy Purpose Values" on the "Provisioning Domains (PvDs)"
          registry page established by <xref target="RFC8801"/>.
          The initial contents are:
        </t>
        <table>
          <thead>
            <tr>
              <th>Value</th>
              <th>Description</th>
              <th>Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>ai-gateway</td>
              <td>
                Forward proxy used only for AI provider
                destinations selected by proxy-match.
              </td>
              <td>This document</td>
            </tr>
          </tbody>
        </table>
        <t>
          New values are allocated by Expert Review
          <xref target="RFC8126"/>. The expert reviews the
          specification for a clear meaning that does not overlap
          an existing value. Values containing an underscore are
          reserved for vendor use, consistent with
          <xref target="I-D.ietf-intarea-proxy-config"/>.
        </t>
      </section>
    </section>
  </middle>
  <back>
    <references>
      <name>Normative References</name>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2132.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3396.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3629.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9915.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8801.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9110.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9525.xml"/>
      <reference anchor="I-D.ietf-intarea-proxy-config">
        <front>
          <title>Communicating Proxy Configurations in Provisioning Domains</title>
          <author initials="T." surname="Pauly" fullname="Tommy Pauly">
            <organization>Apple Inc.</organization>
          </author>
          <author initials="D." surname="Damjanovic" fullname="Dragana Damjanovic">
            <organization>Microsoft</organization>
          </author>
          <author initials="Y." surname="Rosomakho" fullname="Yaroslav Rosomakho">
            <organization>Zscaler</organization>
          </author>
          <date year="2026" month="May" day="19"/>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-ietf-intarea-proxy-config-14"/>
        <seriesInfo name="Work in Progress" value=""/>
        <refcontent>RFC Editor queue.</refcontent>
      </reference>
    </references>
    <references>
      <name>Informative References</name>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3040.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3118.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3942.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8766.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8910.xml"/>
      <reference anchor="I-D.su-ai-gateway-discovery">
        <front>
          <title>DNS-Based Service Discovery for AI Gateways</title>
          <author initials="C." surname="Su" fullname="C. Su">
            <organization>Router-for-Me</organization>
          </author>
          <date year="2026" month="October" day="28"/>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-su-ai-gateway-discovery-01"/>
        <seriesInfo name="Work in Progress" value=""/>
      </reference>
      <reference anchor="I-D.yang-dhc-dhcp-extension">
        <front>
          <title>DHCP New Option Extension based on LLM Capability</title>
          <author initials="Y." surname="Yang" fullname="Yuanyuan Yang">
            <organization>Huawei</organization>
          </author>
          <author initials="Q." surname="Wu" fullname="Qin Wu">
            <organization>Huawei</organization>
          </author>
          <date year="2026" month="July" day="6"/>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-yang-dhc-dhcp-extension-00"/>
        <seriesInfo name="Work in Progress" value=""/>
      </reference>
    </references>
    <section numbered="false">
      <name>Acknowledgements</name>
      <t>
        The option shape follows the captive-portal URI option in
        RFC 8910. The descriptor reuses the proxy and destination
        keys defined by draft-ietf-intarea-proxy-config.
      </t>
    </section>
  </back>
</rfc>
