--- 1/draft-ietf-httpbis-origin-frame-05.txt	2018-01-13 14:13:10.222454508 -0800
+++ 2/draft-ietf-httpbis-origin-frame-06.txt	2018-01-13 14:13:10.246455080 -0800
@@ -1,19 +1,19 @@
 
 HTTP                                                       M. Nottingham
 Internet-Draft
 Intended status: Standards Track                               E. Nygren
-Expires: July 15, 2018                                            Akamai
-                                                        January 11, 2018
+Expires: July 17, 2018                                            Akamai
+                                                        January 13, 2018
 
                         The ORIGIN HTTP/2 Frame
-                   draft-ietf-httpbis-origin-frame-05
+                   draft-ietf-httpbis-origin-frame-06
 
 Abstract
 
    This document specifies the ORIGIN frame for HTTP/2, to indicate what
    origins are available on a given connection.
 
 Note to Readers
 
    Discussion of this draft takes place on the HTTP working group
    mailing list (ietf-http-wg@w3.org), which is archived at
@@ -31,21 +31,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on July 15, 2018.
+   This Internet-Draft will expire on July 17, 2018.
 
 Copyright Notice
 
    Copyright (c) 2018 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -180,24 +180,27 @@
    understands ORIGIN).
 
    See Appendix A for an illustrative algorithm for processing ORIGIN
    frames.
 
 2.3.  The Origin Set
 
    The set of origins (as per [RFC6454]) that a given connection might
    be used for is known in this specification as the Origin Set.
 
-   By default, the Origin Set for a connection is uninitialised.  When
-   an ORIGIN frame is first received and successfully processed by a
-   client, the connection's Origin Set is defined to contain an initial
-   origin.  The initial origin is composed from:
+   By default, the Origin Set for a connection is uninitialised.  An
+   uninitialized Origin Set means that clients apply the coalescing
+   rules from Section 9.1.1 of [RFC7540].
+
+   When an ORIGIN frame is first received and successfully processed by
+   a client, the connection's Origin Set is defined to contain an
+   initial origin.  The initial origin is composed from:
 
    o  Scheme: "https"
 
    o  Host: the value sent in Server Name Indication (SNI, [RFC6066],
       Section 3), converted to lower case; if SNI is not present, the
       remote address of the connection (i.e., the server's IP address)
 
    o  Port: the remote port of the connection (i.e., the server's port)
 
    The contents of that ORIGIN frame (and subsequent ones) allows the