Change:
This is an editorial PR based on comments made by Chris Wood during his shepherd review of the document.

Discussion:
different from the one used to receive it, as the request encoding differs by version (see below). <del> otherwise, the recipient will act as an IP proxy.  It extracts the optional "target" and "ipproto" variables from the URI it has reconstructed from the request headers, decodes their percent- encoding, and establishes an IP tunnel. </del> <ins> otherwise, the recipient will act as an IP proxy.  The IP proxy can choose to reject the IP proxying request.  Otherwise, it extracts the optional "target" and "ipproto" variables from the URI it has reconstructed from the request headers, decodes their percent-encoding, and establishes an IP tunnel. </ins> IP proxies MUST validate whether the decoded "target" and "ipproto" variables meet the requirements in scope.  If they do not, the IP proxy MUST treat the request as malformed; see H2 and H3.  If the "target" variable is a DNS name, the IP proxy MUST perform DNS <del> resolution before replying to the HTTP request.  If errors occur during this process, the IP proxy MUST reject the request and SHOULD send details using an appropriate Proxy-Status header field PROXY- STATUS.  For example, if DNS resolution returns an error, the proxy can use the "dns_error" Proxy Error Type from PROXY-STATUS. </del> <ins> resolution (to query the corresponding IPv4 and/or IPv6 addresses via A and/or AAAA records) before replying to the HTTP request.  If errors occur during this process, the IP proxy MUST reject the request and SHOULD send details using an appropriate Proxy-Status header field PROXY-STATUS.  For example, if DNS resolution returns an error, the proxy can use the "dns_error" Proxy Error Type from PROXY- STATUS. </ins> The lifetime of the IP forwarding tunnel is tied to the IP proxying request stream.  The IP proxy MUST maintain all IP address and route

8.2. <ins> The following example shows how to connect a branch office network to a corporate network such that all machines on those networks can communicate.  In this example, the IP proxying client is attached to the branch office network 192.0.2.0/24, and the IP proxy is attached to the corporate network 203.0.113.0/24.  There are legacy clients on the branch office network that only allow maintenance request from machines on their subnet, so the IP Proxy is provisioned with an IP address from that subnet. In this case, the client does not specify any scope in its request. The IP proxy assigns the client an IPv4 address (203.0.113.100) and a split-tunnel route to the corporate network (203.0.113.0/24).  The client assigns the IP proxy an IPv4 address (192.0.2.200) and a split-tunnel route to the branch office network (192.0.2.0/24).  This allows hosts on both networks to communicate with each other, and allows the IP proxy to perform maintenance on legacy hosts in the branch office. 8.3. </ins> The following example shows an IP flow forwarding setup, where a client requests to establish a forwarding tunnel to target.example.com using SCTP (IP protocol 132), and receives a

(2001:db8:3456::b), scoped to SCTP.  The client can send and receive SCTP IP packets to the remote host. <del> 8.3. </del> <ins> 8.4. </ins> The following example shows a setup where a client is proxying UDP packets through an IP proxy in order to control connection