[Webpush] Mirja Kühlewind's No Objection on draft-ietf-webpush-protocol-11: (with COMMENT)

["Mirja Kuehlewind" <[e-mail]>]

Mirja Kühlewind has entered the following ballot position for
draft-ietf-webpush-protocol-11: No Objection

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:
----------------------------------------------------------------------

Maybe stupid questions:

1) Would it be possible for a user agent to use the same push service
with multiple application servers? Or is this the case where a
subscription set should be used? What happens in this case? Also, is
there a possibility for different user agents to use the same push
service if they would need to receive the same message from the same
server...? Just thinking...

2) section 8.4 says:
"To address this case, the W3C Push API [API] has adopted Voluntary
   Application Server Identification [I-D.ietf-webpush-vapid], which
   allows a user agent to restrict a subscription to a specific
   application server. "
How does the user agent signal to the push service which application
servers should be accepted? Did I miss that?

Nit?:
- In the Figure at the beginning of section 2 (which doesn't have a
caption btw.) I guess you should use "application server" instead of
"application" otherwise the previous definition is confusing...

Also here in section 8 (s/application/application server):
"This includes any communications
   between user agent and push service, plus communications between the
   application and the push service. "