<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Am 25.04.2013 14:52, schrieb John Day:<br>
</div>
<blockquote cite="mid:a06240852cd9ed3117ebb@%5B10.0.1.3%5D"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=us-ascii">
<title>Re: [e2e] Port numbers in the network
layer?</title>
<div>The question is why is a protocol-id field required in some
protocols and not others.</div>
<div><br>
</div>
<div>If it is to identify the protocol in the layer above, then
how
many thousand SCTP instances can I identify on top of a single
IP
instance. If it identifies the protocol, then that should be
possible. Obviously it isn't what it is intended for.<br>
</div>
</blockquote>
<br>
So, what is, concisely, the problem and your proposed solution?<br>
<br>
Up to know, each individual TCP connection is uniquely identified by
an address quadruple (node 1, port 1, node 2, port2). <br>
<br>
Why doesn't this work?<br>
<br>
And which solution works better?<br>
<br>
<br>
</body>
</html>