Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TSV-ART review from Magnus Westerlund #131

Merged
merged 6 commits into from
Oct 5, 2016
Merged

TSV-ART review from Magnus Westerlund #131

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
890ca7b
Section 3
Oct 4, 2016
6ac5dea
Section 5.2
Oct 4, 2016
23353fa
Section 7.2
Oct 4, 2016
91ca701
Unclarities which requests that require HTTP/2
Oct 4, 2016
c9db4f7
Avoid the use of required (Martin)
Oct 5, 2016
332f3fd
editorial
Oct 5, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
51 changes: 45 additions & 6 deletions draft-ietf-webpush-protocol.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -184,8 +184,37 @@
<t>
Examples in this document use the <xref target="RFC7230">HTTP/1.1
message format</xref>. Many of the exchanges can be completed using
HTTP/1.1. Where HTTP/2 is necessary, the more verbose frame format
from <xref target="RFC7540"/> is used.
HTTP/1.1:

<list style="symbols">
<t>
<xref target="message_subscription">Subscribing for Push Messages</xref>
</t>
<t>
<xref target="send">Requesting Push Message Delivery</xref>
</t>
<t>
<xref target="replace">Replacing Push Messages</xref>
</t>
<t>
<xref target="acknowledge_message">Acknowledging Push Messages</xref>
</t>
</list>

When an example depends on HTTP/2 server push, the more verbose frame format
from <xref target="RFC7540"/> is used:

<list style="symbols">
<t>
<xref target="monitor-subscription">Receiving Push Messages for a Subscription</xref>
</t>
<t>
<xref target="monitor-set">Receiving Push Messages for a Subscription Set</xref>
</t>
<t>
<xref target="receive_receipt">Receiving Push Message Receipts</xref>
</t>
</list>
</t>
<t>
Examples do not include specific methods for push message encryption
Expand Down Expand Up @@ -310,6 +339,7 @@
</section>
<section title="Connecting to the Push Service">
<t>
The push service MUST use HTTP over TLS [RFC2818] following the recommendations in [RFC7525].
The push service shares the same default port number (443/TCP) with HTTPS, but MAY
also advertise the IANA allocated TCP System Port 1001 using HTTP alternative services
<xref target="RFC7838"/>.
Expand Down Expand Up @@ -556,6 +586,13 @@ Location: https://push.example.net/message/qDIYHNcfAIPP_5ITvURr-d6BGt
in seconds that suggests how long a push message is retained by the push service.
</t>
<figure>
<preamble>
The TTL rule specifies a non-negative integer, representing time in seconds.
A recipient parsing and converting a TTL value to binary form SHOULD use an
arithmetic type of at least 31 bits of non-negative integer range. If a recipient
receives a TTL value greater than the greatest integer it can represent, or if any
of its subsequent calculations overflows, it MUST consider the value to be 2147483648 (2^31).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I couldn't find where you cribbed this text from. It looks fine.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RFC7234 – delta seconds

</preamble>
<artwork type="abnf"><![CDATA[
TTL = 1*DIGIT
]]></artwork>
Expand Down Expand Up @@ -1067,11 +1104,13 @@ HEADERS [stream 82] +END_STREAM
in response to requests that include an entity body that is too large.
Push services MUST NOT return a 413 status code in responses to an entity
body that is 4096 bytes or less in size.
</t>
</t>
<t>
To limit the number of stored push messages, the push service MAY either
expire messages prior to their advertised Time-To-Live or reduce their
advertised Time-To-Live.
To limit the number of stored push messages, the push service MAY respond with a shorter
Time-To-Live than proposed by the application server in its request for push message delivery
(<xref target="ttl"/>). Once a message has been accepted, the push service MAY later expire
the message prior to its advertised Time-To-Live. If the application server requested a
delivery receipt, the push service MUST return a failure response (<xref target="acknowledge_message"/>).
</t>
</section>

Expand Down