<html>
<body>
<font size=3>At 12:50 PM 10/21/2005, Fab Tillier wrote:<br>
<blockquote type=cite class=cite cite="">> From: James Lentini
[<a href="mailto:jlentini@netapp.com" eudora="autourl">
mailto:jlentini@netapp.com</a>]<br>
> Sent: Friday, October 21, 2005 12:38 PM<br>
> <br>
> On Fri, 21 Oct 2005, Sean Hefty wrote:<br>
> <br>
> > > sean> version(8) | reserved(8) | src port (16)<br>
> > <x-tab> </x-tab>version(1) | reserved(1)
| src port (2)<br>
> > > sean> src ip (16)<br>
> > > sean> dst ip (16)<br>
> > > sean> user private data
(56)<x-tab> </x-tab><x-tab>
</x-tab>/* for version 1
*/<br>
> > ><br>
> > > Are the numbers in parens in bytes or bits? It looks like
a mixture to me.<br>
> ><br>
> > Uhm.. they were a mix. Changed above to bytes.<br>
> <br>
> Ok. I assume that your 1 byte of version information is broken into
2<br>
> 4-bit pieces, one for the protocol version and one for the IP
version.<br><br>
Doesn't leading-zero-padding the IPv4 addresses to be 16 bytes eliminates
the<br>
need for an IP version field?</blockquote><br>
Not really. The same logic was used in the SDP port mapper for
iWARP where there was still an IP version provided so that the space
remained constant while the end node would know how to parse the
message.<br><br>
Mike</font></body>
</html>