make some minor edits based on comments by Stephen Ma (networking).

git-svn-id: http://svn.whatwg.org/webapps@237 340c8d12-0b0e-0410-8428-c7bf67bfef74

index

@@ -20388,7 +20388,8 @@ document.getElementById('stock').addEventListener('stock change',
    <li>the target host is not a valid host name, or
 
    <li>the <var title="">port</var> argument is neither equal to 80, nor
-    equal to 443, nor greater than 1024 and less than 65537,
+    equal to 443, nor greater than or equal to 1024 and less than or equal to
+    65535,
   </ul>
 
   <p>...then the UA must raise a <a href="#security3">security exception</a>.</p>
@@ -20492,12 +20493,15 @@ document.getElementById('stock').addEventListener('stock change',
   <h5 id=broadcasting><span class=secno>8.2.5.1. </span>Broadcasting over
    TCP/IP</h5>
 
+  <p class=big-issue>Should we drop this altogether? Letting people fill the
+   local network with garbage seems unwise.
+
   <p class=big-issue>We need to register a UDP port for this. For now this
    spec refers to port 18080/udp.
 
   <p class=note>Since this feature requires that the user agent listen to a
-   particular port, typically only one user agent per IP address can use this
-   feature at any one time.
+   particular port, some platforms might prevent more than one user agent per
+   IP address from using this feature at any one time.
 
   <p>On TCP/IP networks, broadcast connections transmit data using UDP over
    port 18080.
@@ -20549,7 +20553,7 @@ document.getElementById('stock').addEventListener('stock change',
 
   <p>Otherwise, for each <code><a href="#connection0">Connection</a></code>
    object that was created by the <code title=dom-LocalBroadcastConnection><a
-   href="#localbroadcastconnection">LocalBroascastConnection()</a></code>
+   href="#localbroadcastconnection">LocalBroadcastConnection()</a></code>
    constructor and whose <code title=dom-Connection-network><a
    href="#network">network</a></code> attribute exactly matches <var
    title="">d</var>, a <code title=event-connection-read><a
@@ -20642,12 +20646,15 @@ document.getElementById('stock').addEventListener('stock change',
   <h5 id=peer-to-peer0><span class=secno>8.2.6.1. </span>Peer-to-peer
    connections over TCP/IP</h5>
 
+  <p class=big-issue>Should we replace this section with something that uses
+   Rendez-vous/zeroconf or equivalent?
+
   <p class=big-issue>We need to register ports for this. For now this spec
    refers to port 18080/udp and 18080/tcp.
 
   <p class=note>Since this feature requires that the user agent listen to a
-   particular port, typically only one user agent per IP address can use this
-   feature at any one time.
+   particular port, some platforms might prevent more than one user agent per
+   IP address from using this feature at any one time.
 
   <p>When using TCP/IP, broadcasting peer discovery messages must be done by
    creating UDP packets every few seconds containing as their data the value
@@ -20667,8 +20674,8 @@ document.getElementById('stock').addEventListener('stock change',
    peer-to-peer connection, and it should therefore be offered to the user.
 
   <p>Incoming connection requests must be listened for on TCP port 18080. If
-   an incoming connection is received, the UA acts as a <em>server</em>, as
-   described in the section entitled <a href="#servers1">servers accepting
+   an incoming connection is received, the UA must act as a <em>server</em>,
+   as described in the section entitled <a href="#servers1">servers accepting
    connections over TCP</a>.
 
   <p>If no incoming connection requests are accepted and the user instead
@@ -27135,10 +27142,10 @@ interface <dfn id=timeouthandler>TimeoutHandler</dfn> {
    Iannarelli, Mihai &#x015E;ucan<!-- from ROBO Design -->, Mike Shaver,
    Mikko Rantalainen, Neil Deakin, Olav Junker Kj&aelig;r, Rimantas
    Liubertas, Robert O'Callahan, Roman Ivanov, S. Mike Dierken, Shadow2531,
-   Shaun Inman, Simon Pieters, Steven Garrity, Stewart Brodie, Stuart
-   Parmenter, Tantek &Ccedil;elik, Thomas O'Connor, Tim Altman, Vladimir
-   Vuki&#x0107;evi&#x0107;, and everyone on the WHATWG mailing list for their
-   useful and substantial comments.
+   Shaun Inman, Simon Pieters, Stephen Ma, Steven Garrity, Stewart Brodie,
+   Stuart Parmenter, Tantek &Ccedil;elik, Thomas O'Connor, Tim Altman,
+   Vladimir Vuki&#x0107;evi&#x0107;, and everyone on the WHATWG mailing list
+   for their useful and substantial comments.
 
   <p>Special thanks to Richard Williamson for creating the first
    implementation of <code><a href="#canvas">canvas</a></code> in Safari,

source

@@ -18886,7 +18886,8 @@ document.getElementById('stock').addEventListener('stock change',
   <ul>
    <li>the target host is not a valid host name, or</li>
    <li>the <var title="">port</var> argument is neither equal to 80,
-   nor equal to 443, nor greater than 1024 and less than 65537,</li>
+   nor equal to 443, nor greater than or equal to 1024 and less than
+   or equal to 65535,</li>
   </ul>
   <p>...then the UA must raise a <span>security exception</span>.</p>
   <!-- XXX we should have our own port for this too, e.g. 980 -->
@@ -18991,12 +18992,16 @@ document.getElementById('stock').addEventListener('stock change',
 
   <h5>Broadcasting over TCP/IP</h5>
 
+  <p class="big-issue">Should we drop this altogether? Letting people
+  fill the local network with garbage seems unwise.</p>
+
   <p class="big-issue">We need to register a UDP port for this. For
   now this spec refers to port 18080/udp.</p>
 
   <p class="note">Since this feature requires that the user agent
-  listen to a particular port, typically only one user agent per IP
-  address can use this feature at any one time.</p>
+  listen to a particular port, some platforms might prevent more than
+  one user agent per IP address from using this feature at any one
+  time.</p>
 
   <p>On TCP/IP networks, broadcast connections transmit data using UDP
   over port 18080.</p>
@@ -19051,7 +19056,7 @@ document.getElementById('stock').addEventListener('stock change',
 
   <p>Otherwise, for each <code>Connection</code> object that was
   created by the <code
-  title="dom-LocalBroadcastConnection">LocalBroascastConnection()</code>
+  title="dom-LocalBroadcastConnection">LocalBroadcastConnection()</code>
   constructor and whose <code
   title="dom-Connection-network">network</code> attribute exactly
   matches <var title="">d</var>, a <code
@@ -19146,12 +19151,16 @@ document.getElementById('stock').addEventListener('stock change',
 
   <h5>Peer-to-peer connections over TCP/IP</h5>
 
+  <p class="big-issue">Should we replace this section with something
+  that uses Rendez-vous/zeroconf or equivalent?</p>
+
   <p class="big-issue">We need to register ports for this. For now
   this spec refers to port 18080/udp and 18080/tcp.</p>
 
   <p class="note">Since this feature requires that the user agent
-  listen to a particular port, typically only one user agent per IP
-  address can use this feature at any one time.</p>
+  listen to a particular port, some platforms might prevent more than
+  one user agent per IP address from using this feature at any one
+  time.</p>
 
   <p>When using TCP/IP, broadcasting peer discovery messages must be
   done by creating UDP packets every few seconds containing as their
@@ -19173,7 +19182,7 @@ document.getElementById('stock').addEventListener('stock change',
   therefore be offered to the user.</p>
 
   <p>Incoming connection requests must be listened for on TCP port
-  18080. If an incoming connection is received, the UA acts as a
+  18080. If an incoming connection is received, the UA must act as a
   <em>server</em>, as described in the section entitled <span>servers
   accepting connections over TCP</span>.</p>
 
@@ -24757,10 +24766,10 @@ interface <dfn>TimeoutHandler</dfn> {
   'Ratt' Iannarelli, Mihai &#x015E;ucan<!-- from ROBO Design -->, Mike
   Shaver, Mikko Rantalainen, Neil Deakin, Olav Junker Kj&aelig;r,
   Rimantas Liubertas, Robert O'Callahan, Roman Ivanov, S. Mike
-  Dierken, Shadow2531, Shaun Inman, Simon Pieters, Steven Garrity,
-  Stewart Brodie, Stuart Parmenter, Tantek &Ccedil;elik, Thomas
-  O'Connor, Tim Altman, Vladimir Vuki&#x0107;evi&#x0107;, and everyone
-  on the WHATWG mailing list for their useful and substantial
+  Dierken, Shadow2531, Shaun Inman, Simon Pieters, Stephen Ma, Steven
+  Garrity, Stewart Brodie, Stuart Parmenter, Tantek &Ccedil;elik,
+  Thomas O'Connor, Tim Altman, Vladimir Vuki&#x0107;evi&#x0107;, and
+  everyone on the WHATWG mailing list for their useful and substantial
   comments.</p>
 
   <p>Special thanks to Richard Williamson for creating the first