Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt
"t.petch" <ietfc@btconnect.com> Mon, 06 September 2010 18:14 UTC
Return-Path: <ietfc@btconnect.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 027133A6959 for <tsvwg@core3.amsl.com>; Mon, 6 Sep 2010 11:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.266
X-Spam-Level:
X-Spam-Status: No, score=-2.266 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C1IWXOXbDS+j for <tsvwg@core3.amsl.com>; Mon, 6 Sep 2010 11:14:25 -0700 (PDT)
Received: from c2beaomr05.btconnect.com (c2beaomr05.btconnect.com [213.123.26.183]) by core3.amsl.com (Postfix) with ESMTP id 45E1C3A696D for <tsvwg@ietf.org>; Mon, 6 Sep 2010 11:14:20 -0700 (PDT)
Received: from pc6 (host81-153-11-67.range81-153.btcentralplus.com [81.153.11.67]) by c2beaomr05.btconnect.com with SMTP id FKH92142; Mon, 6 Sep 2010 19:14:23 +0100 (BST)
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=0001.0A0B0302.4C852F7F.018A, actions=tag
Message-ID: <005201cb4de6$40c41440$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: gorry@erg.abdn.ac.uk, Benoit Claise <bclaise@cisco.com>
References: <20100823124502.7BD433A6A2E@core3.amsl.com><4C77BCD1.9010706@cisco.com> <4C7E8A4F.5080807@erg.abdn.ac.uk>
Subject: Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt
Date: Mon, 06 Sep 2010 19:08:53 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Junkmail-Status: score=10/50, host=c2beaomr05.btconnect.com
X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A0B0208.4C852F90.0101, ss=1, fgs=0, ip=0.0.0.0, so=2009-07-20 21:54:04, dmn=5.7.1/2009-08-27, mode=single engine
X-Junkmail-IWF: false
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Sep 2010 18:14:28 -0000
----- Original Message ----- From: "Gorry Fairhurst" <gorry@erg.abdn.ac.uk> To: "Benoit Claise" <bclaise@cisco.com> Cc: <tsvwg@ietf.org> Sent: Wednesday, September 01, 2010 7:15 PM > My understanding is that we need reviewers (or reviews). > > A quick read seems to suggest the current draft may benefit from some > editorial work before starting a WGLC ... I'm happy to offer comments to > help this, but that doesn't remove the need for other people to step up > as reviewers. I see what you mean. The challenge is how to communicate what is potentially a large number of minor edits without expending large amounts of man power. Thus I could provide text in the usual form of /old/new/ in which case the Introduction would be "Many applications that /desire to// use SCTP /want/have requested/ the ability to "reset" a stream. The intention of resetting a stream is to /set/start/ the numbering sequence of the stream back /to/at/ 'zero' with a corresponding notification to the upper layer that this /has/act as/ been performed. The applications that /want/have requested/ this feature /want to/normally desire it so that they can/ "re-use" streams for different purposes but still utilize the stream sequence number /so that the application can/for the application to/ track the message flows. Thus, without this feature, a new use /of/on/ an old stream would result in message numbers /greater/larger/ than expected /unless there is/without/ a protocol mechanism to "/reset/start/ the streams back /to/at/ zero". This document / also includes/s presents also a/ method/s// for resetting the transport sequence numbers, adding additional streams and resetting all stream sequence numbers. Would that do the job? Tom Petch > > Offers please to WG Chairs and/or authors! > > Gorry > > > > Dear all, > > > > I see in the minutes: > > > > Four IDs approaching WGLC: > > - SCTP Stream Reconfiguration > > - IANA procedures for ports and services > > - SCTP Sockets > > - SCTP Flag Chunks > > > > Are we still waiting for something before starting the WGLC on this draft? > > > > Regards, Benoit. > >> A New Internet-Draft is available from the on-line Internet-Drafts directories. > >> This draft is a work item of the Transport Area Working Group Working Group of the IETF. > >> > >> > >> Title : Stream Control Transmission Protocol (SCTP) Stream Reconfiguration > >> Author(s) : R. Stewart, et al. > >> Filename : draft-ietf-tsvwg-sctp-strrst-05.txt > >> Pages : 30 > >> Date : 2010-08-23 > >> > >> Many applications that desire to use SCTP have requested the ability > >> to "reset" a stream. The intention of resetting a stream is to start > >> the numbering sequence of the stream back at 'zero' with a > >> corresponding notification to the upper layer that this act as been > >> performed. The applications that have requested this feature > >> normally desire it so that they can "re-use" streams for different > >> purposes but still utilize the stream sequence number for the > >> application to track the message flows. Thus, without this feature, > >> a new use on an old stream would result in message numbers larger > >> than expected without a protocol mechanism to "start the streams back > >> at zero". This documents presents also a method for resetting the > >> transport sequence numbers, adding additional streams and resetting > >> all stream sequence numbers. > >> > >> A URL for this Internet-Draft is: > >> http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctp-strrst-05.txt > >> > >> Internet-Drafts are also available by anonymous FTP at: > >> ftp://ftp.ietf.org/internet-drafts/ > >> > >> Below is the data which will enable a MIME compliant mail reader > >> implementation to automatically retrieve the ASCII version of the > >> Internet-Draft. > > >
- I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt Internet-Drafts
- Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt t.petch
- Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt Benoit Claise
- Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt Gorry Fairhurst
- Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt t.petch
- Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt Michael Tüxen
- Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt Brian F. G. Bidulock
- Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt t.petch
- RFC4960 IANA actions t.petch
- Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt Michael Tüxen
- Re: RFC4960 IANA actions Randy Stewart
- Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt t.petch
- Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt Chris Benson
- Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt Randy Stewart
- Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt t.petch
- Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt Randy Stewart