From 6b1cc1995538fde23241ed4d89725f4e9a62b3ec Mon Sep 17 00:00:00 2001
From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 1 Mar 2016 12:05:46 +0100
Subject: [PATCH] Drop requirement that "reasonable assurances" need to be
 based on a standards-track RFC (#148)

---
 draft-ietf-httpbis-alt-svc.xml | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/draft-ietf-httpbis-alt-svc.xml b/draft-ietf-httpbis-alt-svc.xml
index 3f7d42780..d707d0f52 100755
--- 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>