--- a/Overview-UseCases.xml Wed Dec 19 09:40:17 2012 -0500
+++ b/Overview-UseCases.xml Fri Dec 21 13:32:14 2012 -0500
@@ -16,7 +16,7 @@
<meta http-equiv='Content-Type' content='text/html; charset=UTF-8'/>
<title>Web Cryptography API Use Cases</title>
- <meta name='revision' content='$Id: Overview-FA.xml,v 1.164 2012/12/17 12:23:12 arangana Exp $'/>
+ <meta name='revision' content='$Id: Overview-FA.xml,v 1.164 2013/01/02 12:23:12 arangana Exp $'/>
<link rel='stylesheet' href='FileAPI.css' type='text/css'/>
<script src='section-links.js' type='application/ecmascript'/>
@@ -32,7 +32,9 @@
<options xmlns='http://mcc.id.au/ns/local'>
<versions>
- <cvs href=' http://dvcs.w3.org/hg/webcrypto-usecases'/>
+ <cvs href='http://dvcs.w3.org/hg/webcrypto-usecases/raw-file/tip/Overview.html'/>
+ <this href="http://www.w3.org/TR/2013/WD-webcrypto-usecases-20130201"/>
+ <previous href="http://dvcs.w3.org/hg/webcrypto-usecases/raw-file/tip/Overview.html"/>
</versions>
<editors>
<person homepage='http://arunranga.com/' email='arun@mozilla.com'>
@@ -40,7 +42,7 @@
<affiliation>Mozilla Corporation</affiliation>
</person>
</editors>
- <maturity>ED</maturity>
+ <maturity>FPWD</maturity>
</options>
</head>
@@ -132,7 +134,7 @@
</li>
<li><p><dfn id="NAMEDKEY">NAMEDKEY</dfn> which allows an application in JavaScript to discover a <dfn id="pre-prov">pre-provisioned</dfn> key within the scope of the application's origin, which exists at the time of the application's first invocation, and has not been derived, generated or imported by the application using any of the features listed above; such keys may have been provisioned by a device manufacturer, for example, and the JavaSript application can access them for initial authorization and authentication at time of first invocation. </p>
- <div class="note"><p>This feature is developed in the <a href="#KeyDiscover">Key Discovery API</a>.</p></div>
+ <div class="note"><p>This feature is developed in the <a href="#KeyDiscovery">Key Discovery API</a>.</p></div>
</li>
</ul>
</div>
@@ -259,7 +261,7 @@
<p>Ryan has just bought a new TV and wishes to watch video content from the service provider. He connects the TV to the Internet, and navigates to the video provider's website. The video provider's site establishes a secure communication channel between the video provider's page on the TV and the video provider's servers, proving to the servers that Ryan's TV is indeed one of those that meets the security requirements by use of the cryptographic key and identifier pre-provisioned on the TV. The video provider's page on the TV likewise verifies that it is talking to a genuine server, preventing the hijacking of Ryan's video watching by a malicious third party. To ensure the highest security, the pre-provisoned key is used minimally in this process to deliver session keys. <p>[<a href="#namedkey">NAMEDKEY</a> | <a href="#verify">VERIFY</a> | <a href="#unwrap">UNWRAP</a> | <a href="#mac">MAC</a> | <a href="#encrypt-sym">ENCRYPT-SYM</a> | <a href="#decrypt-sym">DECRYPT-SYM</a> | <a href="#sign">SIGN</a>]</p></p>
<div class="example">
-<p>The Key Discovery API describes the provides a mechanism for an application in JavaScript to detect the presence of a pre-provisioned key using the name of a disclosed identifier. </p>
+<p>The <a href="#KeyDiscovery">Key Discovery API</a> describes the provides a mechanism for an application in JavaScript to detect the presence of a pre-provisioned key using the name of a disclosed identifier. </p>
<div class="ednote"><p>While <code>KeyOperation</code> is asynchronous and event driven, the key retrieval mechanism is synchronous; this might change in subsequent drafts.</p></div>
<x:codeblock language="es">
var keys = window.getKeysByName("VetFlxL33t_Device.p1a.b11");
@@ -461,19 +463,19 @@
<dt id='OTR'>OTR</dt>
<dd><cite><a href="http://www.cypherpunks.ca/otr/Protocol-v3-4.0.0.html">Off-the-Record Messaging Protocol version 3</a></cite>, cypherpunks.ca</dd>
<dt id='hcard'>hCard</dt>
- <dd><cite><a href="http://microformats.org/wiki/hcard">hCard</a></cite>, T. Celik, B. Suda, microformats.org</dd>
+ <dd><cite><a href="http://microformats.org/wiki/hcard">hCard</a></cite>, T. Celik, B. Suda. microformats.org</dd>
<dt id='keyexamples'>Microformats Key Examples</dt>
- <dd><cite><a href="http://microformats.org/wiki/key-examples">Key Examples</a></cite>, T. Celik, microformats.org</dd>
+ <dd><cite><a href="http://microformats.org/wiki/key-examples">Key Examples</a></cite>, T. Celik. microformats.org</dd>
<dt id="JWK">JSON Web Key</dt>
- <dd><cite><a href="https://datatracker.ietf.org/doc/draft-ietf-jose-json-web-key/">JSON Web Key (JWK) draft-ietf-jose-json-web-key-07</a></cite>, M. Jones, IETF</dd>
+ <dd><cite><a href="https://datatracker.ietf.org/doc/draft-ietf-jose-json-web-key/">JSON Web Key (JWK) draft-ietf-jose-json-web-key-07</a></cite>, M. Jones. IETF</dd>
<dt id="GoogleContacts">Google Contacts API</dt>
<dd><cite><a href="https://developers.google.com/google-apps/contacts/v3/">Google Contacts API v. 3.0</a></cite>, Google</dd>
<dt id="MozillaContacts">Mozilla Contacts API</dt>
<dd><cite><a href="https://wiki.mozilla.org/WebAPI/ContactsAPI">Mozilla Proposed Contacts API</a></cite>, Mozilla</dd>
<dt id="DAPContacts">Pick Contacts Intent</dt>
- <dd><cite><a href="http://www.w3.org/TR/contacts-api/">Pick Contacts Intent</a></cite>, R. Tibbett, R. Berjon, W3C</dd>
+ <dd><cite><a href="http://www.w3.org/TR/contacts-api/">Pick Contacts Intent</a></cite>R. Tibbett, R. Berjon. W3C</dd>
<dt id="HTML">HTML</dt>
- <dd><cite><a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/network.html">HTML Living Standard</a></cite>I. Hickson, WHATWG</dd>
+ <dd><cite><a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/network.html">HTML Living Standard</a></cite>, I. Hickson. WHATWG</dd>
</dl>
--- a/Overview.html Wed Dec 19 09:40:17 2012 -0500
+++ b/Overview.html Fri Dec 21 13:32:14 2012 -0500
@@ -1,18 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!--
- Overview.html
- Web IDL
-
- Note: This file is generated from Overview.xml. Run "make" to regenerate it.
- -->
-
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Web Cryptography API Use Cases</title>
- <meta name="revision" content="$Id: Overview-FA.xml,v 1.164 2012/12/17 12:23:12 arangana Exp $" />
+ <meta name="revision" content="$Id: Overview-FA.xml,v 1.164 2013/01/02 12:23:12 arangana Exp $" />
<link rel="stylesheet" href="FileAPI.css" type="text/css" />
<script src="section-links.js" type="application/ecmascript"></script>
@@ -27,10 +20,10 @@
<![endif]-->
- <link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-ED" type="text/css" /></head>
+ <link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD" type="text/css" /></head>
<body>
- <div class="head"><div><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" width="72" height="48" alt="W3C" /></a></div><h1>Web Cryptography API Use Cases</h1><h2>W3C Editor’s Draft <em>17 December 2012</em></h2><dl><dt>Latest Editor’s Draft:</dt><dd><a href=" http://dvcs.w3.org/hg/webcrypto-usecases"> http://dvcs.w3.org/hg/webcrypto-usecases</a></dd><dt>Latest Published Version:</dt><dt>Editor:</dt><dd><a href="http://arunranga.com/">Arun Ranganathan</a>, Mozilla Corporation <arun@mozilla.com></dd><dt>Participate:</dt><dd></dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.org/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr />
+ <div class="head"><div><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" width="72" height="48" alt="W3C" /></a></div><h1>Web Cryptography API Use Cases</h1><h2>W3C Working Draft <em>02 January 2013</em></h2><dl><dt>This Version:</dt><dd><a href="http://www.w3.org/TR/2013/WD-webcrypto-usecases-20130201">http://www.w3.org/TR/2013/WD-webcrypto-usecases-20130201</a></dd><dt>Latest Published Version:</dt><dt>Previous Version(s):</dt><dd><a href="http://dvcs.w3.org/hg/webcrypto-usecases/raw-file/tip/Overview.html">http://dvcs.w3.org/hg/webcrypto-usecases/raw-file/tip/Overview.html</a></dd><dt>Editor:</dt><dd><a href="http://arunranga.com/">Arun Ranganathan</a>, Mozilla Corporation <arun@mozilla.com></dd><dt>Participate:</dt><dd></dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © -201 <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.org/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr />
<div class="section">
<h2>Abstract</h2>
@@ -39,7 +32,7 @@
</p>
- <div class="ednote"><div class="ednoteHeader">Editorial note</div><p>This is revision $Id: Overview-FA.xml,v 1.164 2012/12/17 12:23:12 arangana Exp $.</p><p>There are 4 further editorial notes in the document.</p></div>
+
</div>
<div class="section">
@@ -51,8 +44,8 @@
report can be found in the <a href="http://www.w3.org/TR/">W3C technical
reports index</a> at http://www.w3.org/TR/.
</em></p><p>
- This document is the 17 December 2012 <b>Editor’s Draft</b> of the
- <cite>Web Cryptography API Use Cases</cite> specification.
+ This document is the 02 January 2013 <b>First Public Working Draft</b> of the
+ <cite>Web Cryptography API Use Cases</cite> document.
Please send comments about this document to
<a href="mailto:public-webcrypto@w3.org">public-webcrypto@w3.org</a>
@@ -91,7 +84,7 @@
<a href="https://dvcs.w3.org/hg/webcrypto-usecases">W3C public Mercurial Repository</a>.
</p>
<p>
- Publication as an Editor’s Draft does not imply endorsement by the
+ Publication as a Working Draft does not imply endorsement by the
W3C Membership. This is a draft document and may be updated, replaced
or obsoleted by other documents at any time. It is inappropriate to cite
this document as other than work in progress.
@@ -148,7 +141,7 @@
</li>
<li><p><dfn id="NAMEDKEY">NAMEDKEY</dfn> which allows an application in JavaScript to discover a <dfn id="pre-prov">pre-provisioned</dfn> key within the scope of the application's origin, which exists at the time of the application's first invocation, and has not been derived, generated or imported by the application using any of the features listed above; such keys may have been provisioned by a device manufacturer, for example, and the JavaSript application can access them for initial authorization and authentication at time of first invocation. </p>
- <div class="note"><div class="noteHeader">Note</div><p>This feature is developed in the <a href="#KeyDiscover">Key Discovery API</a>.</p></div>
+ <div class="note"><div class="noteHeader">Note</div><p>This feature is developed in the <a href="#KeyDiscovery">Key Discovery API</a>.</p></div>
</li>
</ul>
</div>
@@ -275,7 +268,7 @@
<p>Ryan has just bought a new TV and wishes to watch video content from the service provider. He connects the TV to the Internet, and navigates to the video provider's website. The video provider's site establishes a secure communication channel between the video provider's page on the TV and the video provider's servers, proving to the servers that Ryan's TV is indeed one of those that meets the security requirements by use of the cryptographic key and identifier pre-provisioned on the TV. The video provider's page on the TV likewise verifies that it is talking to a genuine server, preventing the hijacking of Ryan's video watching by a malicious third party. To ensure the highest security, the pre-provisoned key is used minimally in this process to deliver session keys. <p>[<a href="#namedkey">NAMEDKEY</a> | <a href="#verify">VERIFY</a> | <a href="#unwrap">UNWRAP</a> | <a href="#mac">MAC</a> | <a href="#encrypt-sym">ENCRYPT-SYM</a> | <a href="#decrypt-sym">DECRYPT-SYM</a> | <a href="#sign">SIGN</a>]</p></p>
<div class="example"><div class="exampleHeader">Example</div>
-<p>The Key Discovery API describes the provides a mechanism for an application in JavaScript to detect the presence of a pre-provisioned key using the name of a disclosed identifier. </p>
+<p>The <a href="#KeyDiscovery">Key Discovery API</a> describes the provides a mechanism for an application in JavaScript to detect the presence of a pre-provisioned key using the name of a disclosed identifier. </p>
<div class="ednote"><div class="ednoteHeader">Editorial note</div><p>While <code>KeyOperation</code> is asynchronous and event driven, the key retrieval mechanism is synchronous; this might change in subsequent drafts.</p></div>
<div class="block"><div class="blockTitleDiv"><span class="blockTitle">ECMAScript</span></div><div class="blockContent"><pre class="code"><code class="es-code">
var keys = window.getKeysByName("VetFlxL33t_Device.p1a.b11");
@@ -477,19 +470,19 @@
<dt id="OTR">OTR</dt>
<dd><cite><a href="http://www.cypherpunks.ca/otr/Protocol-v3-4.0.0.html">Off-the-Record Messaging Protocol version 3</a></cite>, cypherpunks.ca</dd>
<dt id="hcard">hCard</dt>
- <dd><cite><a href="http://microformats.org/wiki/hcard">hCard</a></cite>, T. Celik, B. Suda, microformats.org</dd>
+ <dd><cite><a href="http://microformats.org/wiki/hcard">hCard</a></cite>, T. Celik, B. Suda. microformats.org</dd>
<dt id="keyexamples">Microformats Key Examples</dt>
- <dd><cite><a href="http://microformats.org/wiki/key-examples">Key Examples</a></cite>, T. Celik, microformats.org</dd>
+ <dd><cite><a href="http://microformats.org/wiki/key-examples">Key Examples</a></cite>, T. Celik. microformats.org</dd>
<dt id="JWK">JSON Web Key</dt>
- <dd><cite><a href="https://datatracker.ietf.org/doc/draft-ietf-jose-json-web-key/">JSON Web Key (JWK) draft-ietf-jose-json-web-key-07</a></cite>, M. Jones, IETF</dd>
+ <dd><cite><a href="https://datatracker.ietf.org/doc/draft-ietf-jose-json-web-key/">JSON Web Key (JWK) draft-ietf-jose-json-web-key-07</a></cite>, M. Jones. IETF</dd>
<dt id="GoogleContacts">Google Contacts API</dt>
<dd><cite><a href="https://developers.google.com/google-apps/contacts/v3/">Google Contacts API v. 3.0</a></cite>, Google</dd>
<dt id="MozillaContacts">Mozilla Contacts API</dt>
<dd><cite><a href="https://wiki.mozilla.org/WebAPI/ContactsAPI">Mozilla Proposed Contacts API</a></cite>, Mozilla</dd>
<dt id="DAPContacts">Pick Contacts Intent</dt>
- <dd><cite><a href="http://www.w3.org/TR/contacts-api/">Pick Contacts Intent</a></cite>, R. Tibbett, R. Berjon, W3C</dd>
+ <dd><cite><a href="http://www.w3.org/TR/contacts-api/">Pick Contacts Intent</a></cite>R. Tibbett, R. Berjon. W3C</dd>
<dt id="HTML">HTML</dt>
- <dd><cite><a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/network.html">HTML Living Standard</a></cite>I. Hickson, WHATWG</dd>
+ <dd><cite><a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/network.html">HTML Living Standard</a></cite>, I. Hickson. WHATWG</dd>
</dl>