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

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/