| Internet-Draft | DHCP AI Gateway URI | November 2026 |
| Piriyath | Expires 16 May 2027 | [Page] |
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.¶
This note is to be removed before publishing as an RFC.¶
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.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 16 May 2027.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
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.¶
Existing mechanisms do not provide this advertisement:¶
The Web Proxy Auto-Discovery Protocol (WPAD) [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 [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.¶
[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 [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.¶
[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 [RFC8766]. It does not name a forward proxy.¶
[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.¶
This document follows the pattern of [RFC8910]. DHCP carries a URI. The client retrieves the operational data over HTTPS. The operational data is the PvD Additional Information document of [I-D.ietf-intarea-proxy-config], with one additional proxy key, "purpose", whose value "ai-gateway" distinguishes this proxy from a general web proxy.¶
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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
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 [I-D.su-ai-gateway-discovery].¶
Gateway descriptor: A PvD Additional Information document [RFC8801] retrieved from the URI carried by the option defined in this document.¶
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.¶
Both options carry the same URI. The URI is encoded as UTF-8 [RFC3629] with no terminating NUL.¶
The DHCPv4 option code is OPTION_AI_GATEWAY_URI (TBD1). Its format is:¶
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) | | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The DHCPv6 option code is OPTION_AI_GATEWAY_URI (TBD2). Its format is:¶
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) | | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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".¶
The URI MUST NOT contain userinfo (a username or password). A client MUST discard a URI that contains userinfo.¶
A typical value is:¶
https://ai-gw.example.com/.well-known/pvd
The path "/.well-known/pvd" is the well-known PvD URI defined in [RFC8801] and the location from which [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 Section 6 still applies. This document does not register a new well-known URI.¶
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 [RFC3396]. A DHCPv4 client concatenates those occurrences into a single URI [RFC3396] and MUST NOT treat them as a list of URIs. DHCPv4 therefore carries at most one URI.¶
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.¶
A DHCPv4 server includes OPTION_AI_GATEWAY_URI only in a response to a client whose Parameter Request List [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 [RFC3396].¶
A DHCPv6 server includes OPTION_AI_GATEWAY_URI only in a response to a client whose Option Request option [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 Section 4.3.¶
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.¶
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.¶
On receiving one or more accepted URIs, the client fetches the descriptor with HTTP GET over TLS. The request SHOULD include:¶
Accept: application/pvd+json
The client MUST authenticate the TLS server and MUST verify that the certificate matches the hostname of the URI [RFC9110] [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.¶
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 [I-D.ietf-intarea-proxy-config].¶
The client uses a proxy from the descriptor only when all of the following are true:¶
The proxy dictionary contains "purpose" with the value "ai-gateway".¶
A "proxy-match" rule [I-D.ietf-intarea-proxy-config] selects that proxy for the destination.¶
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 [I-D.ietf-intarea-proxy-config] places on proxies learned from a network PvD.¶
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.¶
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.¶
The client SHOULD refresh the descriptor when the DHCP lease is renewed and when the descriptor "expires" time [RFC8801] is reached. It MUST apply the randomized backoff required by [RFC8801] when refreshing because of expiry.¶
The descriptor is a PvD Additional Information object [RFC8801] containing the "proxies" and "proxy-match" keys defined by [I-D.ietf-intarea-proxy-config].¶
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 Section 3. Other values are reserved for future registration.¶
An example descriptor is:¶
{
"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": []
}
]
}
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.¶
A descriptor MUST list "purpose" in the "mandatory" array [I-D.ietf-intarea-proxy-config] of every proxy dictionary that carries it. A client that implements [I-D.ietf-intarea-proxy-config] but not this document then ignores the dictionary instead of using the AI gateway as an ordinary proxy.¶
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.¶
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 Section 6.¶
Operators SHOULD prevent rogue DHCP servers on access networks. That is a property of the access network. This document does not require DHCP authentication [RFC3118], which is not widely deployed.¶
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.¶
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 [I-D.ietf-intarea-proxy-config].¶
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.¶
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.¶
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:¶
| Tag | Name | Data Length | Meaning | Reference |
|---|---|---|---|---|
| TBD1 | OPTION_AI_GATEWAY_URI | N | HTTPS URI of an AI gateway descriptor | This document |
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:¶
| Value | Description | Client ORO | Singleton | Reference |
|---|---|---|---|---|
| TBD2 | OPTION_AI_GATEWAY_URI | Yes | No | This document |
The option is not a singleton: more than one instance MAY appear, in preference order.¶
IANA is requested to register the following key in the "Proxy Information PvD Keys" registry established by [I-D.ietf-intarea-proxy-config]:¶
| JSON Key | Optional/Required | Description | Type | Reference |
|---|---|---|---|---|
| purpose | optional | Role of this proxy. The value "ai-gateway" identifies an AI forward proxy. | String | This document |
IANA is requested to create a registry titled "AI Gateway Proxy Purpose Values" on the "Provisioning Domains (PvDs)" registry page established by [RFC8801]. The initial contents are:¶
| Value | Description | Reference |
|---|---|---|
| ai-gateway | Forward proxy used only for AI provider destinations selected by proxy-match. | This document |
New values are allocated by Expert Review [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 [I-D.ietf-intarea-proxy-config].¶
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.¶