[w3c/push-api] Some things about the PushEncryptionKeys p256dh and auth are not clear enough (#212)

In the working draft 15 is written: 

> Keys named p256dh and auth must be supported.

Does that mean that those keys must exist and contain a value, is it enough that they exist and contain null or does that mean (in context of what comes before that sentence) that if getKey() is supported, only then you must be able to get auth and p256dh?

Secondly, what is not clear to me is, whether it is possible that auth and p256dh can change after the subscription:
Case 1: If the values were null, is it possible that a value gets added without a new subscription - For example: a browser wasn't able to generate these values and was now updated to a version which can
Case 2: A browser had values, is it possible that these get deleted or changed without a new subscription?
So basically the question is can I assume that in any case the subscription settings stay exactly the same until the endpoint is invalidated?

In the editor draft from 18 August 2016 is written: 

> Once set, options for a push subscription cannot change.

But that is in a part which focuses on the  PushSubscriptionOptions userVisibleOnly and applicationServerKey. And if that also contains p256 and auth, then the question is again: does "set" mean filled with a value or does null qualify too, that the "value" cannot be changed?

Thanks

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/212