Re-subscription needs clarification

[matthiaswilder]

Currently the spec suggests that re-subscription is supported by including the hub.channel.endpoint parameter in a subscription request. However, it makes no mention of re-subscription in the Subscription Denial/Confirmation sections. In those sections the language is written as if the subscriber will always need to connect to a websocket before receiving a confirmation/denial, but in re-subscription the subscriber has presumably already connected.

The obvious solution to me here is that the confirmation/denial is sent automatically, since the connection is already open. But I have had at least one person suggest that this implies another behavior where the subscriber reconnects to the websocket on every re-subscription.

I think that language calling out permutations of the subscription for re-subscription should probably be more explicit and less inferred.