Draft: draft-ietf-webpush-protocol

Commentary: reviewed the document , these are the easy changes .
Paragraph (version A):
Requesting the delivery of events is particularly important for the
W3C Push API.  The subscription, management and monitoring functions
are currently fulfilled by proprietary protocols; these are adequate,
but do not offer any of the advantages that standardization affords.
Paragraph (version B):
A standardized method of event delivery is particularly important for
the W3C Push API, where application servers might need to use
multiple push services.  The subscription, management and monitoring
functions are currently fulfilled by proprietary protocols; these are
adequate, but do not offer any of the advantages that standardization
affords.
Paragraph (version A):
The component of an application that runs on a server and requests
the delivery of a push message.
Paragraph (version B):
The component of an application that usually runs on a server and
requests the delivery of a push message.
Paragraph (version A):
Collecting multiple push message subscriptions into a subscription
set can represent a significant efficiency improvement for a push
service.  The push service MAY provide a URI for a subscription set
resource in a link relation of type "urn:ietf:params:push:set".
Paragraph (version B):
Collecting multiple push message subscriptions into a subscription
set can represent a significant efficiency improvement for push
services and user agents.  The push service MAY provide a URI for a
subscription set resource in a link relation of type
"urn:ietf:params:push:set".
Paragraph (version A):
An application server requests the delivery of a push message by
sending a HTTP POST request to a push resource distributed to the
application server by a user agent.  The push message is included in
the body of the request.
Paragraph (version B):
An application server requests the delivery of a push message by
sending a HTTP POST request to a push resource distributed to the
application server by a user agent.  The ciphertext of the push
message is included in the body of the request.
Paragraph (version A):
Only push messages that have been assigned a topic can be updated.  A
push message with a topic replaces any outstanding push message with
an identical topic.
Paragraph (version B):
Only push messages that have been assigned a topic can be replaced.
A push message with a topic replaces any outstanding push message
with an identical topic.
Paragraph (version A):
A push message update request creates a new push message resource and
simultaneously deletes any existing message resource that has a
matching topic.  In effect, the information that is stored for the
push message is updated, but a new resource is created to avoid
problems with in flight acknowledgments for the old message.  The
push service MAY suppress acknowledgement receipts for the replaced
message.
Paragraph (version B):
A push message replacement request creates a new push message
resource and simultaneously deletes any existing message resource
that has a matching topic.  In effect, the information that is stored
for the push message is replaced, but a new resource is created to
avoid problems with in flight acknowledgments for the old message.
The push service MAY suppress delivery receipts for the replaced
message.