[Webpush] Alexey Melnikov's Yes on draft-ietf-webpush-protocol-12: (with COMMENT)

["Alexey Melnikov" <[e-mail]>]

Alexey Melnikov has entered the following ballot position for
draft-ietf-webpush-protocol-12: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-webpush-protocol/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for addressing my DISCUSS points.

I haven't checked whether you addressed all of my earlier comments:

1) <This comment was replied to. Withdrawn.>

2) In 4.1:

Can 429 be used when no subscription set is specified? (If yes, this
should be mentioned in section 4).

3) <Addressed>

4) In general case it is not possible to achieve message reliability
because a push server is allowed to expire messages after they were
accepted for delivery due to overload. (Similarly for forced subscription
expiration.) I don't think the document makes this clear in Section 7.4.

5) <This comment was replied to. Withdrawn.>