<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1"><font face="Helvetica, Arial, sans-serif">The
Carterfone era RJ11 interface to the telephone handset is another
example; the internals of the PSTN have changed radically without
altering the customer experience in any meaningful way. I've always
thought it interesting that TCP was designed at the same time that the
FCC was enacting the Carterfone rules. <br>
<br>
To me, IP is more an interface specification than a protocol, FWIW; its
enduring property is the format it imposes on messages crossing a
particular system boundary.<br>
<br>
RB </font></font><br>
<br>
On 6/2/2010 10:40 AM, Dave Crocker wrote:
<blockquote cite="mid:4C06979C.9080603@gmail.com" type="cite"><br>
<br>
On 6/2/2010 7:25 AM, Tony Finch wrote:
<br>
<blockquote type="cite">On Tue, 1 Jun 2010, Noel Chiappa wrote:
<br>
<blockquote type="cite">For example, you could, today, build a
network that was POTS user interface,
<br>
but independently routed packets inside.
<br>
</blockquote>
</blockquote>
...
<br>
<blockquote type="cite">That's what the BT 21CN project is about:
replacing the core of the
<br>
telephone network with VOIP. The edges remain POTS for most
subscribers.
<br>
</blockquote>
<br>
<br>
This model of retaining interface behaviors while replacing the
internals is remarkably well-established.
<br>
<br>
Netbios and Ethernet are salient examples for this grup.
<br>
<br>
d/
<br>
<br>
<br>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Richard Bennett
Research Fellow
Information Technology and Innovation Foundation
Washington, DC</pre>
</body>
</html>