RE: TCP limitations (was Re: ISCSI: Urgent Flag requirement violates TCP.)

["Douglas Otis" <dotis@sanlight.net>]

Jim,

Dropped the urgent pointer method and retain the VI TCP segment alignment
with now a required CRC-32.  Segment alignment is not TCP just as is exact
repeated segments upon retry.  I can't see use of a CRC to discover
alignment.

Doug


> > csapuntz@cisco.com wrote:
> >
> > > Given that shim protocol requires no changes to the TCP in the sender,
> > > it is currently my favorite way of doing RDMA.
> > >
> > > -Costa
> >
> > Please see Jeff's message on 10/26.  If you don't have framing, when you
> lose
> > a segment, you need to buffer generic TCP segments on the NIC before you
> can
> > "RDMA" them somewhere, because you don't know where the "RDMA"
> information
> is
> > in the "byte stream".
> >
> > -Matt
> >
>
> http://www.ietf.org/internet-drafts/draft-williams-rdmatcp-00.txt
>
> is an example of a shim layer that provides a mechanism
> to recover framing upon loss of TCP segments.
>
>