discovery-api/Overview.src.html
changeset 440 fcbaadc4fd54
parent 438 d66ca00fe7d9
child 441 b4b2569b4e9b
     1.1 --- a/discovery-api/Overview.src.html	Thu Aug 08 14:41:34 2013 -0400
     1.2 +++ b/discovery-api/Overview.src.html	Mon Aug 12 16:20:17 2013 +1000
     1.3 @@ -217,7 +217,8 @@
     1.4  </pre>
     1.5        </div>
     1.6        <p>
     1.7 -        For more detailed examples see the <a href="#examples">Examples</a> section.
     1.8 +        For more detailed examples, including examples of communicating with obtained networked services, see the
     1.9 +        <a href="#examples">Examples</a> section.
    1.10        </p>
    1.11      </section>
    1.12      <section id='conformance'>
    1.13 @@ -329,6 +330,67 @@
    1.14      </section>
    1.15      <section>
    1.16        <h2>
    1.17 +        Security and privacy considerations
    1.18 +      </h2>
    1.19 +      <p>
    1.20 +        The API defined in this specification can be used to find and connect to devices and services within a user's
    1.21 +        current network. This discloses information related to a user's network: devices available on their network and
    1.22 +        the publicly-accessible services ("networked services") currently running and available on those devices. The
    1.23 +        distribution of this information could potentially compromise the user's privacy. A conforming implementation
    1.24 +        of this specification MUST provide a mechanism that protects the user's privacy. This mechanism MUST ensure
    1.25 +        that no networked service information is retrievable without the user's express permission.
    1.26 +      </p>
    1.27 +      <section>
    1.28 +        <h3>
    1.29 +          Privacy considerations for API implementations
    1.30 +        </h3>
    1.31 +        <p>
    1.32 +          A <a>user agent</a> MUST NOT provide networked service information to web sites without the express
    1.33 +          permission of the user. A user agent MUST acquire permission through a user interface, unless they have
    1.34 +          prearranged trust relationships with users, as described below. The user interface MUST include the document
    1.35 +          base URL. Those permissions that are acquired through the user interface and that are preserved beyond the
    1.36 +          current browsing session (i.e. beyond the time when the browsing context is navigated to another URL) MUST be
    1.37 +          revocable and a user agent MUST respect revoked permissions.
    1.38 +        </p>
    1.39 +        <p>
    1.40 +          Obtaining the user's express permission to access one API method does not imply the user has granted
    1.41 +          permission for the same web site to access any other methods that may be provided by this API, or to access
    1.42 +          the same method with a different set of arguments, as part of the same permission context. If a user has
    1.43 +          expressed permission for an implementation to, e.g. find a set of existing networked services, the
    1.44 +          implementation MUST seek the user's express permission if and when any subsequent functions are called on
    1.45 +          this API.
    1.46 +        </p>
    1.47 +        <p>
    1.48 +          A user agent MAY have prearranged trust relationships that do not require such user interfaces. For example,
    1.49 +          while a web browser will present a user interface when a web site performs a networked service lookup, a
    1.50 +          different runtime may have a prearranged, delegated security relationship with the user and, as such, a
    1.51 +          suitable alternative security and privacy mechanism with which to authorise the retrieval of networked
    1.52 +          service information.
    1.53 +        </p>
    1.54 +      </section>
    1.55 +      <section class="informative">
    1.56 +        <h3>
    1.57 +          Additional API implementation considerations
    1.58 +        </h3>
    1.59 +        <p>
    1.60 +          Further to the requirements listed in the previous section, implementors of the Network Service Discovery API
    1.61 +          are also advised to consider the following aspects that can negatively affect the privacy of their users: in
    1.62 +          certain cases, users can inadvertently grant permission to the user agent to disclose networked services to
    1.63 +          Web sites. In other cases, the content hosted at a certain URL changes in such a way that previously granted
    1.64 +          networked service permissions no longer apply as far as the user is concerned. Or the users might simply
    1.65 +          change their minds.
    1.66 +        </p>
    1.67 +        <p>
    1.68 +          Predicting or preventing these situations is inherently difficult. Mitigation and in-depth defensive measures
    1.69 +          are an implementation responsibility and not prescribed by this specification. However, in designing these
    1.70 +          measures, implementers are advised to enable user awareness of networked service sharing, and to provide easy
    1.71 +          access to interfaces that enable revocation of permissions that web applications have for accessing networked
    1.72 +          services via this API.
    1.73 +        </p>
    1.74 +      </section>
    1.75 +    </section>
    1.76 +    <section>
    1.77 +      <h2>
    1.78          Requesting networked services
    1.79        </h2>
    1.80        <pre class="widl">
    1.81 @@ -1029,7 +1091,7 @@
    1.82        <p>
    1.83          The <dfn>list of available service records</dfn> is a single dynamic internal lookup table within user agents
    1.84          that is used to track all the services that have been discovered and are available in the current network at
    1.85 -        the current time. At any point during the running of either of the two <a>service discovery mechanisms</a> then
    1.86 +        the current time. At any point during the running of any of the <a>service discovery mechanisms</a> then
    1.87          existing entries within this table can be updated, entries can be added and entries can be removed as the
    1.88          status of networked services changes according to the rules defined in this specification.
    1.89        </p>