[Tsvwg] Future of TCP and SCTP

"Uri Elzur" <uri@broadcom.com> Wed, 20 March 2002 22:24 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17413 for <tsvwg-archive@odin.ietf.org>; Wed, 20 Mar 2002 17:24:43 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id RAA18706 for tsvwg-archive@odin.ietf.org; Wed, 20 Mar 2002 17:24:45 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA15732; Wed, 20 Mar 2002 16:47:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA15700 for <tsvwg@optimus.ietf.org>; Wed, 20 Mar 2002 16:47:32 -0500 (EST)
Received: from mms1.broadcom.com (mms1.broadcom.com [63.70.210.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA16037 for <tsvwg@ietf.org>; Wed, 20 Mar 2002 16:47:28 -0500 (EST)
Received: from 63.70.210.1 by mms1.broadcom.com with ESMTP (Broadcom MMS-1 SMTP Relay (MMS v4.7)); Wed, 20 Mar 2002 13:47:08 -0800
X-Server-Uuid: 1e1caf3a-b686-11d4-a6a3-00508bfc9ae5
Received: from nt-irva-0701.broadcom.com (nt-irva-0701 [10.5.10.97]) by mon-irva-11.broadcom.com (8.9.1/8.9.1) with ESMTP id NAA20229 for <tsvwg@ietf.org>; Wed, 20 Mar 2002 13:47:29 -0800 (PST)
Received: by nt-irva-0701.broadcom.com with Internet Mail Service ( 5.5.2653.19) id <TTX8AFZJ>; Wed, 20 Mar 2002 13:47:30 -0800
Message-ID: <BFF68BEA7C79B949AF6EA9B7BEF7066D058CC9@nt-irva-0740.brcm.ad.broadcom.com>
From: Uri Elzur <uri@broadcom.com>
To: tsvwg@ietf.org
Subject: [Tsvwg] Future of TCP and SCTP
Date: Wed, 20 Mar 2002 13:47:28 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-WSS-ID: 1087DCD6246191-01-01
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1D058.D4B648E0"
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
X-BeenThere: tsvwg@ietf.org

1) In the ROI BOF yesterday, a statement has been made that "SCTP is a main
stream Transport protocol" and that RDMA/DDP mapping to SCTP, will encourage
application use of SCTP in the future. 
 
SCTP is not immune from IP packet drops and out-of-order reception, hence,
like TCP a high speed flow-through NIC would either buffer out-of-order
packets (expensive and not scalable at 10 Gbps and beyond) or place data
out-of-order but indicate to ULP in order. (side comment: it seems to be a
discussion on RDMA list, whether SCTP even provides the hints to the
Receiver to enable placement of out-of-order data or buffering is required
in any case)
 
2) TCP = Protocol of the past ??? TSVWG agrees there is value in framing TCP
as evident by admittance of draft-ietf-tsvwg-tcp-ulp-frame-00. However, a
single bit in the TCP header or a TCP option, that could have been used to
make it simple, are "reserved for future use"
 
What is the future direction for TCP? Isn't SCTP the future?
 
Sorry if I missed something
 
thx
 
Uri