draft-ietf-httpbis-proxy-status-08.txt   draft-ietf-httpbis-proxy-status-latest.txt 
HTTP Working Group M. Nottingham HTTP Working Group M. Nottingham
Internet-Draft Fastly Internet-Draft Fastly
Intended status: Standards Track P. Sikora Intended status: Standards Track P. Sikora
Expires: April 16, 2022 Google Expires: July 18, 2022 Google
October 13, 2021 January 14, 2022
The Proxy-Status HTTP Response Header Field The Proxy-Status HTTP Response Header Field
draft-ietf-httpbis-proxy-status-08 draft-ietf-httpbis-proxy-status-latest
Abstract Abstract
This document defines the Proxy-Status HTTP field to convey the This document defines the Proxy-Status HTTP field to convey the
details of intermediary response handling, including generated details of intermediary response handling, including generated
errors. errors.
Note to Readers Discussion Venues
_RFC EDITOR: please remove this section before publication_ This note is to be removed before publishing as an RFC.
Discussion of this draft takes place on the HTTP working group Discussion of this document takes place on the HTTP Working Group
mailing list (ietf-http-wg@w3.org), which is archived at mailing list (ietf-http-wg@w3.org), which is archived at
https://lists.w3.org/Archives/Public/ietf-http-wg/ [1]. <https://lists.w3.org/Archives/Public/ietf-http-wg/>.
Working Group information can be found at https://httpwg.org/ [2];
source code and issues list for this draft can be found at
https://github.com/httpwg/http-extensions/labels/proxy-status [3].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 16, 2022. This Internet-Draft will expire on July 18, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 7, line 28 skipping to change at page 7, line 14
2.1.3. next-protocol 2.1.3. next-protocol
The "next-protocol" parameter's value indicates the ALPN protocol The "next-protocol" parameter's value indicates the ALPN protocol
identifier [RFC7301] of the protocol used by the intermediary to identifier [RFC7301] of the protocol used by the intermediary to
connect to the next hop when obtaining this response. connect to the next hop when obtaining this response.
The value MUST be either an sf-token or sf-binary, representing a TLS The value MUST be either an sf-token or sf-binary, representing a TLS
Application-Layer Protocol Negotiation (ALPN) Protocol ID (see Application-Layer Protocol Negotiation (ALPN) Protocol ID (see
https://www.iana.org/assignments/tls-extensiontype-values/tls- https://www.iana.org/assignments/tls-extensiontype-values/tls-
extensiontype-values.xhtml#alpn-protocol-ids [4]). If the protocol extensiontype-values.xhtml#alpn-protocol-ids [1]). If the protocol
identifier is able to be expressed as an sf-token using ASCII identifier is able to be expressed as an sf-token using ASCII
encoding, that form MUST be used. encoding, that form MUST be used.
For example: For example:
Proxy-Status: "proxy.example.org"; next-protocol=h2 Proxy-Status: "proxy.example.org"; next-protocol=h2
Note that the APLN identifier is being used here to identify the Note that the APLN identifier is being used here to identify the
protocol in use; it may or may not have been actually used in the protocol in use; it may or may not have been actually used in the
protocol negotiation. protocol negotiation.
skipping to change at page 8, line 50 skipping to change at page 8, line 39
Registration requests should use the following template: Registration requests should use the following template:
o Name: [a name for the Proxy-Status Parameter that matches key] o Name: [a name for the Proxy-Status Parameter that matches key]
o Description: [a description of the parameter semantics and value] o Description: [a description of the parameter semantics and value]
o Reference: [to a specification defining this parameter; optional] o Reference: [to a specification defining this parameter; optional]
See the registry at https://iana.org/assignments/http-proxy-status See the registry at https://iana.org/assignments/http-proxy-status
[5] for details on where to send registration requests. [2] for details on where to send registration requests.
2.3. Proxy Error Types 2.3. Proxy Error Types
This section lists the Proxy Error Types defined by this document. This section lists the Proxy Error Types defined by this document.
See Section 2.4 for information about defining new Proxy Error Types. See Section 2.4 for information about defining new Proxy Error Types.
Note that implementations might not produce all Proxy Error Types. Note that implementations might not produce all Proxy Error Types.
The set of types below is designed to map to existing states in The set of types below is designed to map to existing states in
implementations, and so may not be applicable to some. implementations, and so may not be applicable to some.
skipping to change at page 22, line 9 skipping to change at page 21, line 31
If the Proxy Error Type might occur in responses that are not If the Proxy Error Type might occur in responses that are not
generated by the intermediary -- for example, when an error is generated by the intermediary -- for example, when an error is
detected as the response is streamed from a forward connection, detected as the response is streamed from a forward connection,
causing a Proxy-Status trailer field to be appended -- the 'Response causing a Proxy-Status trailer field to be appended -- the 'Response
only generated by intermediaries' should be 'false'. If the Proxy only generated by intermediaries' should be 'false'. If the Proxy
Error Type only occurs in responses that are generated by the Error Type only occurs in responses that are generated by the
intermediary, it should be 'true'. intermediary, it should be 'true'.
See the registry at https://iana.org/assignments/http-proxy-status See the registry at https://iana.org/assignments/http-proxy-status
[6] for details on where to send registration requests. [3] for details on where to send registration requests.
3. IANA Considerations 3. IANA Considerations
Upon publication, please create the HTTP Proxy-Status Parameters Upon publication, please create the HTTP Proxy-Status Parameters
registry and the HTTP Proxy Error Types registry at registry and the HTTP Proxy Error Types registry at
https://iana.org/assignments/http-proxy-status [7] and populate them https://iana.org/assignments/http-proxy-status [4] and populate them
with the types defined in Section 2.1 and Section 2.3 respectively; with the types defined in Section 2.1 and Section 2.3 respectively;
see Section 2.2 and Section 2.4 for its associated procedures. see Section 2.2 and Section 2.4 for its associated procedures.
Additionally, please register the following entry in the Hypertext Additionally, please register the following entry in the Hypertext
Transfer Protocol (HTTP) Field Name Registry: Transfer Protocol (HTTP) Field Name Registry:
o Field name: Proxy-Status o Field name: Proxy-Status
o Status: permanent o Status: permanent
skipping to change at page 24, line 19 skipping to change at page 23, line 37
DOI 10.17487/RFC5234, January 2008, DOI 10.17487/RFC5234, January 2008,
<https://www.rfc-editor.org/info/rfc5234>. <https://www.rfc-editor.org/info/rfc5234>.
[RFC8586] Ludin, S., Nottingham, M., and N. Sullivan, "Loop [RFC8586] Ludin, S., Nottingham, M., and N. Sullivan, "Loop
Detection in Content Delivery Networks (CDNs)", RFC 8586, Detection in Content Delivery Networks (CDNs)", RFC 8586,
DOI 10.17487/RFC8586, April 2019, DOI 10.17487/RFC8586, April 2019,
<https://www.rfc-editor.org/info/rfc8586>. <https://www.rfc-editor.org/info/rfc8586>.
5.3. URIs 5.3. URIs
[1] https://lists.w3.org/Archives/Public/ietf-http-wg/ [1] https://www.iana.org/assignments/tls-extensiontype-values/tls-
[2] https://httpwg.org/
[3] https://github.com/httpwg/http-extensions/labels/proxy-status
[4] https://www.iana.org/assignments/tls-extensiontype-values/tls-
extensiontype-values.xhtml#alpn-protocol-ids extensiontype-values.xhtml#alpn-protocol-ids
[5] https://iana.org/assignments/http-proxy-status [2] https://iana.org/assignments/http-proxy-status
[6] https://iana.org/assignments/http-proxy-status [3] https://iana.org/assignments/http-proxy-status
[7] https://iana.org/assignments/http-proxy-status [4] https://iana.org/assignments/http-proxy-status
Authors' Addresses Authors' Addresses
Mark Nottingham Mark Nottingham
Fastly Fastly
Prahran Prahran
Australia Australia
Email: mnot@mnot.net Email: mnot@mnot.net
URI: https://www.mnot.net/ URI: https://www.mnot.net/
Piotr Sikora Piotr Sikora
Google Google
 End of changes. 17 change blocks. 
28 lines changed or deleted 17 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/