From 074d3ac8b46188737d4e4671191d71a62e3609d2 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Fri, 22 Sep 2017 11:07:29 +1000 Subject: [PATCH 1/3] Punctuate! --- draft-ietf-httpbis-origin-frame.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/draft-ietf-httpbis-origin-frame.md b/draft-ietf-httpbis-origin-frame.md index a48644150..330ba1436 100644 --- a/draft-ietf-httpbis-origin-frame.md +++ b/draft-ietf-httpbis-origin-frame.md @@ -156,7 +156,7 @@ The contents of that ORIGIN frame (and subsequent ones) allows the server to inc origins to the Origin Set, as described in {{process}}. The Origin Set is also affected by the 421 (Misdirected Request) response status code, defined in -{{!RFC7540}} Section 9.1.2. Upon receipt of a response with this status code, implementing clients +{{!RFC7540}}, Section 9.1.2. Upon receipt of a response with this status code, implementing clients MUST create the ASCII serialisation of the corresponding request's origin (as per {{!RFC6454}}, Section 6.2) and remove it from the connection's Origin Set, if present. @@ -182,7 +182,7 @@ Note: {{!RFC7540}}, Section 10.1 uses both DNS and the presented TLS certificate to establish the origin server(s) that a connection is authoritative for, just as HTTP/1.1 does in {{?RFC7230}}. -Furthermore, {{!RFC7540}} Section 9.1.1 explicitly allows a connection to be used for more than one +Furthermore, {{!RFC7540}}, Section 9.1.1 explicitly allows a connection to be used for more than one origin server, if it is authoritative. This affects what requests can be sent on the connection, both in HEADERS frame by the client and as PUSH_PROMISE frames from the server ({{!RFC7540}}, Section 8.2.2). @@ -196,10 +196,10 @@ Note that for a connection to be considered authoritative for a given origin, th required to obtain a certificate that passes suitable checks; see {{!RFC7540}} Section 9.1.1 for more information. This includes verifying that the host matches a `dNSName` value from the certificate `subjectAltName` field (using the rules defined in {{!RFC2818}}; see also -{{!RFC5280}} Section 4.2.1.6). +{{!RFC5280}}, Section 4.2.1.6). Additionally, clients MAY avoid consulting DNS to establish the connection's authority for new -requests; however, those that do so face new risks, as explained in {{sc}} +requests; however, those that do so face new risks, as explained in {{sc}}. Because ORIGIN can change the set of origins a connection is used for over time, it is possible that a client might have more than one viable connection to an origin open at any time. When this From be1afb74aeee4f366134cacbb6b3537ea28dd2a9 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Fri, 22 Sep 2017 11:08:07 +1000 Subject: [PATCH 2/3] Punctuate() --- draft-ietf-httpbis-origin-frame.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-httpbis-origin-frame.md b/draft-ietf-httpbis-origin-frame.md index 330ba1436..4b77f3168 100644 --- a/draft-ietf-httpbis-origin-frame.md +++ b/draft-ietf-httpbis-origin-frame.md @@ -163,7 +163,7 @@ Section 6.2) and remove it from the connection's Origin Set, if present. Note: : When sending an ORIGIN frame to a connection that is initialised as an Alternative Service - {{?RFC7838}}, the initial origin set {{set}} will contain an origin with the appropriate + {{?RFC7838}}, the initial origin set ({{set}}) will contain an origin with the appropriate scheme and hostname (since Alternative Services specifies that the origin's hostname be sent in SNI). However, it is possible that the port will be different than that of the intended origin, since the initial origin set is calculated using the actual port in use, which can be From 787b8b8c4ca201d2f1e86c7c4ec5b5d621cd6111 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Fri, 22 Sep 2017 11:08:47 +1000 Subject: [PATCH 3/3] NOT --- draft-ietf-httpbis-origin-frame.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-httpbis-origin-frame.md b/draft-ietf-httpbis-origin-frame.md index 4b77f3168..b8f43a563 100644 --- a/draft-ietf-httpbis-origin-frame.md +++ b/draft-ietf-httpbis-origin-frame.md @@ -203,7 +203,7 @@ requests; however, those that do so face new risks, as explained in {{sc}}. Because ORIGIN can change the set of origins a connection is used for over time, it is possible that a client might have more than one viable connection to an origin open at any time. When this -occurs, clients SHOULD not emit new requests on any connection whose Origin Set is a proper subset +occurs, clients SHOULD NOT emit new requests on any connection whose Origin Set is a proper subset of another connection's Origin Set, and SHOULD close it once all outstanding requests are satisfied. The Origin Set is unaffected by any alternative services {{?RFC7838}} advertisements made by the