Drop requirement that "reasonable assurances" need to be based on a s…

…tandards-track RFC (#148)
httpwg · Mar 1, 2016 · 6b1cc19 · 6b1cc19
1 parent 63ee756
commit 6b1cc19
Showing 1 changed file with 1 addition and 2 deletions.
diff --git a/draft-ietf-httpbis-alt-svc.xml b/draft-ietf-httpbis-alt-svc.xml
@@ -273,8 +273,7 @@ uri-host      = &lt;uri-host, see <xref target="RFC7230" x:rel="#uri"/>&gt;
 </t>
 <t>
    For the purposes of this document, "reasonable assurances" can be established through use of a
-   TLS-based protocol with the certificate checks defined in <xref target="RFC2818"/>. Other means
-   of establishing them &MUST; be documented in an RFC that updates this specification. Clients
+   TLS-based protocol with the certificate checks defined in <xref target="RFC2818"/>. Clients
    &MAY; impose additional criteria for establishing reasonable assurances.
 </t>
 <t>