[Tsvwg] Drafts for SCTP extensions

Lyndon Ong <long@pointreyesnet.com> Mon, 12 February 2001 23:58 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 SMTP id SAA24091 for <tsvwg-archive@odin.ietf.org>; Mon, 12 Feb 2001 18:58:22 -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 SAA27420; Mon, 12 Feb 2001 18:53:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA27389 for <tsvwg@ns.ietf.org>; Mon, 12 Feb 2001 18:53:53 -0500 (EST)
Received: from 2KSRVR.POINTR.NET (97-34.pointreyesnet.com [209.133.97.34] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA24053 for <tsvwg@ietf.org>; Mon, 12 Feb 2001 18:52:47 -0500 (EST)
Received: by 2KSRVR.POINTR.NET with Internet Mail Service (5.5.2650.21) id <D58HCZBT>; Mon, 12 Feb 2001 15:49:09 -0800
Message-ID: <BF66AE0D91F53D46BF08718AB976D26E1D5AED@2KSRVR.POINTR.NET>
From: Lyndon Ong <long@pointreyesnet.com>
To: "'tsvwg@ietf.org'" <tsvwg@ietf.org>
Cc: "'sigtran@standards.nortelnetworks.com'" <sigtran@standards.nortelnetworks.com>
Date: Mon, 12 Feb 2001 15:48:58 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [Tsvwg] Drafts for SCTP extensions
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

Folks,

I would like to bring to your attention a set of drafts for extensions to
SCTP (Stream Control Transmission Protocol) that will be discussed at the
TSV WG session in Minneapolis.  These drafts are:

draft-ietf-sigtran-usctp-00.txt
draft-ietf-sigtran-relreq-sctp-00.txt
draft-ietf-sigtran-srwnd-sctp-00.txt
draft-ietf-sigtran-addip-sctp-00.txt

The first document proposes the addition of an unreliable transfer mode to
SCTP, which allows SCTP to do flow and congestion control across both
reliable and unreliable streams.  

The second document proposes a generic mechanism for transmitting a control
"chunk" reliably across an existing SCTP association.  This generic
mechanism is then applied in the third and fourth proposals.

The third document proposes an enhancement to SCTP to allow
receiver-window-based flow control on a per-stream basis, utilizing the
reliable control chunk mechanism.

The fourth document proposes an enhancement to SCTP to allow addresses to be
added and deleted from the address list for an endpoint of an active SCTP
association, again utilizing the reliable control chunk mechanism.

Please be aware of these as input to the TSV WG session for general
discussion.

Thanks,

L. Ong
Chair, Sigtran WG  

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
http://www1.ietf.org/mailman/listinfo/tsvwg