RE: Key Ownership and SOP exception

Ryan,
During the ‘asia call’ yesterday, it was discussed that CORS would be a technology to analyse to identify how it could relate to the certificate issued by  scenario.  I have asked Mountie to update the wiki, according to that plan in order to keep track of that, and I think that informing the group of this update is a good practice.
The result of ‘CORS/SOP exception’ analysis will be the next milestones for discussing certificate. We also agreed that this would happen after the Last Call of our current deliverables.
Regards,
Virginie


From: Ryan Sleevi [mailto:sleevi@google.com]
Sent: mardi 11 février 2014 01:04
To: mountie.lee@gmail.com
Cc: Web Cryptography Working Group
Subject: Re: Key Ownership and SOP exception


Mountie,

It does not seem like any changes have been made as were requested.

I believe it has been sufficiently explained that "SOP Exceptions" and CORS are either nob-starters or entirely unrelated technologies.

My understanding was that there would be no further discussion on your proposals until the requested issues were addressed.

Best regards,
Ryan
On Feb 10, 2014 3:57 PM, "Mountie Lee" <mountie@paygate.net<mailto:mountie@paygate.net>> wrote:
Hi.
I have added my comments on WIKI.

see https://www.w3.org/2012/webcrypto/wiki/Deliverable_web_certificate_API



--
Mountie Lee

PayGate
CTO, CISSP
Tel : +82 2 2140 2700<tel:%2B82%202%202140%202700>
E-Mail : mountie@paygate.net<mailto:mountie@paygate.net>

=======================================

PayGate Inc.

THE STANDARD FOR ONLINE PAYMENT

for Korea, Japan, China, and the World



________________________________
This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus