Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add SETTINGS_ prefix to parameter name. #469

Merged
merged 1 commit into from Jan 12, 2018
Merged

Add SETTINGS_ prefix to parameter name. #469

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
16 changes: 8 additions & 8 deletions draft-ietf-httpbis-h2-websockets.md
View file
Open in desktop
Expand Up @@ -78,27 +78,27 @@ In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as
described in BCP 14, {{!RFC2119}}.

# The ENABLE_CONNECT_PROTOCOL SETTINGS Parameter
# The SETTINGS_ENABLE_CONNECT_PROTOCOL SETTINGS Parameter

This document adds a new SETTINGS Parameter to those defined by
{{!RFC7540}}, Section 6.5.2.

The new parameter is ENABLE_CONNECT_PROTOCOL (type = 0x8). The value
The new parameter name is SETTINGS_ENABLE_CONNECT_PROTOCOL. The value
of the parameter MUST be 0 or 1.

Upon receipt of ENABLE_CONNECT_PROTOCOL with a value of 1 a client MAY
Upon receipt of SETTINGS_ENABLE_CONNECT_PROTOCOL with a value of 1 a client MAY
use the Extended CONNECT definition of this document when creating new
streams. Receipt of this parameter by a server does not have any
impact.

A sender MUST NOT send a ENABLE_CONNECT_PROTOCOL parameter with the
A sender MUST NOT send a SETTINGS_ENABLE_CONNECT_PROTOCOL parameter with the
value of 0 after previously sending a value of 1.

The use of a SETTINGS Parameter to opt-in to an otherwise incompatible
protocol change is a use of "Extending HTTP/2" defined by Section 5.5
of {{!RFC7540}}. If a client were to use the provisions of the extended
CONNECT method defined in this document without first receiving a
ENABLE_CONNECT_PROTOCOL parameter with the value of 1 it would be a
SETTINGS_ENABLE_CONNECT_PROTOCOL parameter with the value of 1 it would be a
protocol violation.

# The Extended CONNECT Method
Expand Down Expand Up @@ -169,7 +169,7 @@ this point is OPEN as defined by {{!RFC6455}}, Section 4.1.
[[ From Client ]] [[ From Server ]]

SETTINGS
ENABLE_CONNECT_PROTOCOL = 1
SETTINGS_ENABLE_CONNECT_PROTOCOL = 1

HEADERS + END_HEADERS
:method = CONNECT
Expand Down Expand Up @@ -230,10 +230,10 @@ specification addresses that concern in two ways:

# IANA Considerations

This document establishes a entry for the HTTP/2 Settings Registry
This document establishes an entry for the HTTP/2 Settings Registry
that was established by Section 11.3 of {{!RFC7540}}.

Name: ENABLE_CONNECT_PROTOCOL
Name: SETTINGS_ENABLE_CONNECT_PROTOCOL

Code: 0x8

Expand Down