Re: [push-api] Add and Encryption Key array to the PushRegistration interface (#89)

> @@ -639,6 +645,17 @@
>          <code>registrationId</code> and <code>endpoint</code> is expected to be unique and specific
>          to a particular <a>webapp</a> instance running on a specific device.
>        </p>
> +      <p>
> +        When getting the <code><dfn id=
> +        "widl-PushRegistration-encryptionKeys">encryptionKeys</dfn></code> attribute, the <a>user
> +        agent</a> MAY return one or more encryption keys.
> +      </p>
> +      <p class="note">
> +        In order to encrypt a message the web developer would use
> +        <a href="http://www.w3.org/TR/WebCryptoAPI/#dfn-KeyAlgorithm"> Key.algorithm </a> to detect what encryption algorithm
> +        (and any necessary parameters) each key is for, then export the key (to upload to their server) in the KeyFormat
> +        of their choice using crypto.subtle.exportKey(KeyFormat, Key).

While exportKey is needed, we need to avoid it on the private portion of this pair.  The private portion MUST NOT be `extractable`.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/pull/89/files#r20900041