Jon Choukroun

@timcappalli is correct, our proposal intends to support long-lived keys. As for the storage mechanism, our thinking has been that the API should be agnostic on where the key material...

Thanks for the feedback @twiss and @estark37. - The `getRemoteKey` method would be required to get the `CryptoKey` handle. This means the calling web app will know quickly whether it...

To clarify, the intent of this proposal is to support long-lived key use, across multiple browsers and user devices. For example, I can create an encryption key pair on my...

@estark37 I think you're right. We've been thinking of these keys as origin-bound, in the sense that when a web app calls `getRemoteKey()` the browser would pass along the web...

@RByers that's an interesting use case I'm not familiar with. You're correct, the intent of this proposal covers use cases where keys should be syncable across devices. For example, I...

We agree that ”remote“ may not be the correct term for these keys. However, it seems that it should be observable from the browser’s perspective that the key material exists...

That's correct @othermaciej , by "in the client" we mean in webpage code. We agree the explainer can be clearer on why the existing `CryptoKey` properties don't cover our use...