RE: new iSCSI draft - 02.txt

["David Peterson" <dap@cisco.com>]

I believe there was agreement to remove the Urgent-Pointer framing mechanism
but don't recall any agreement to replace it with an in-stream marker. For a
software implementation it would be hard to support this type of framing
mechanism. I believe a TCP option indicating the message boundry or a
fixed-length PDU at a granularity to minimize overhead are much better
solutions and are workable for both software and hardware implementations. I
have not seen an agenda but I would hope this issue would be discussed at
the upcoming meeting in Orlando.
Dave

-----Original Message-----
From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu]On Behalf Of
julian_satran@il.ibm.com
Sent: Saturday, December 30, 2000 11:11 AM
To: ips@ece.cmu.edu
Subject: new iSCSI draft - 02.txt






Dear colleagues,

I've just submitted to the Internet-Drafts repository and to our list
archive (at CMU) a new
version of the draft.

Changes (from 2b!):

   framing by Urgent-Pointer replaced by framing through in-stream marker
   editorials and typos (not completed yet)
   simpler digests
   digest recovery and some clarifications on iSCSI specific errors (more
   to come)


I will have version 03 with many more editorial changes before the
intermediate meeting.

You can see the draft at:

http://www.haifa.il.ibm.com/satran/draft-ietf-ips-iSCSI-02.txt

Regards,
Julo