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.

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

TSV-ART review from Magnus Westerlund #131

Merged
merged 6 commits into from Oct 5, 2016
Merged

TSV-ART review from Magnus Westerlund #131

merged 6 commits into from Oct 5, 2016

Conversation

brianraymor
Copy link

This draft attempts to address all of the issues identified during TSV-ART review with the exception of Dealing with overload situations where further guidance has been requested from early implementers of webpush.

</t>
</list>

Where HTTP/2 server push is required, the more verbose frame format
Copy link
Contributor

Choose a reason for hiding this comment

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

Some IETF curmudgeons will get their panties in a twist over "required", since "REQUIRED" is an RFC 2119 keyword. I tend to avoid it to avoid the pedants.

Copy link
Author

Choose a reason for hiding this comment

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

Sound advice. Updated.

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

<t>
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"/>).
delivery receipt, the push service MUST return a failure response (s<xref target="acknowledge_message"/>).
Copy link

Choose a reason for hiding this comment

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

Is that "s" in the parenthesis spurious?

Copy link
Author

Choose a reason for hiding this comment

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

Doh. Yes. I was editing out a see and managed to miss the s. Thanks.

@brianraymor brianraymor merged commit 8cc624a into webpush-wg:master Oct 5, 2016
@brianraymor brianraymor deleted the magnus_review branch October 5, 2016 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants