[Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usctp-01.txt
Qiaobing Xie <xieqb@cig.mot.com> Mon, 26 February 2001 18:56 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 NAA21422 for <tsvwg-archive@odin.ietf.org>; Mon, 26 Feb 2001 13:56:06 -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 NAA00055; Mon, 26 Feb 2001 13:21:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA00024 for <tsvwg@ns.ietf.org>; Mon, 26 Feb 2001 13:21:21 -0500 (EST)
Received: from motgate4.mot.com (motgate4.mot.com [144.189.100.102]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA19909 for <tsvwg@ietf.org>; Mon, 26 Feb 2001 13:21:18 -0500 (EST)
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate4.mot.com (motgate4 2.1) with ESMTP id LAA10658 for <tsvwg@ietf.org>; Mon, 26 Feb 2001 11:21:15 -0700 (MST)]
Received: [from relay1.cig.mot.com (relay1.cig.mot.com [136.182.15.23]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id LAA02898 for <tsvwg@ietf.org>; Mon, 26 Feb 2001 11:21:14 -0700 (MST)]
Received: from agevole.cig.mot.com (agevole [136.182.3.251]) by relay1.cig.mot.com (8.8.8+Sun/SCERG-RELAY-1.11b) with ESMTP id MAA16062; Mon, 26 Feb 2001 12:21:12 -0600 (CST)
Received: from cig.mot.com (d42-506b.cig.mot.com [160.15.80.107]) by agevole.cig.mot.com (8.7.5 Motorola CIG/ITS v1.1 (Solaris 2.5)) with ESMTP id MAA19818; Mon, 26 Feb 2001 12:21:12 -0600 (CST)
Message-Id: <200102261821.MAA19818@agevole.cig.mot.com>
Date: Mon, 26 Feb 2001 12:24:26 -0600
From: Qiaobing Xie <xieqb@cig.mot.com>
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jon Berger <JRB@dataconnection.com>
CC: Qiaobing Xie <Qiaobing_Xie-QXIE1@email.mot.com>, "SIGTRAN LIST (E-mail)" <SIGTRAN@STANDARDS.NORTELNETWORKS.COM>, tsvwg@ietf.org
References: <37701240971DD31193970000F6CCB9F7024E96DF@duke.datcon.co.uk>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usctp-01.txt
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
Content-Transfer-Encoding: 7bit
Jon, See my comments below... -Qiaobing Jon Berger wrote: > > Qiaobing, > > A few more comments on this latest draft. > > 1) Section 3.2.2 > The description of the B and E bits indicates that fragmentation is not > allowed in the P-DATA chunk, but the text in section 5 explicitly states > that fragmentation is allowed. I think you need to update this section with > the text from the RFC. Yeah, this is a little messy in the document. P-DATA can be either reliable or unreliable depends on which steam it is sent to. Fragmentation is only prohibited on *unreliable P-DATA* (ie., when it is sent to an unreliable stream) but not prohibited if it is sent to a reliable stream. I will clean this up in the next revision (we are in fact proposing two different extensions in this one draft). > > 2) Section 3.2.2 > One thing that isn't explicitly mentioned (although is implied) is when to > calculate the checksum on padding bytes. Maybe the addition of the > following sentence at the end of the Checksum Coverage section would help? > "Padding at the end of the P-DATA chunk MUST NOT be considered when > calculating the Adler-32 checksum." Ok. will be added. > > 3) Section 4.2 > The second paragraph states that unreliable data must not be fragmented but > transmitted in one go no matter what the size. Section 6.9 of the RFC says > that, if fragmentation is supported, messages larger than the MTU must > either be fragmented or not sent at all. I'm not aware of the reasoning for > this requirement in the RFC but I think we should be consistent. I don't see any inconsistency here. Section 6.9 of RFC2960 is talking about reliable messages, while Section 4.2 of this document deals with __unreliable__ messages. > > Jon > > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: 20 February 2001 15:29 > To: IETF-Announce > Cc: sigtran@marvin.corpeast.baynetworks.com > Subject: I-D ACTION:draft-ietf-sigtran-usctp-01.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Signaling Transport Working Group of the > IETF. > > Title : SCTP Unreliable Data Mode Extension > Author(s) : Q. Xie, R. Stewart, C. Sharp, I. Rytina > Filename : draft-ietf-sigtran-usctp-01.txt > Pages : 14 > Date : 19-Feb-01 > > This document describes an extension to the Stream Control > Transmission Protocol (SCTP) [RFC2960] to provide unreliable data > transfer services. The benefits of this extension includes unified > congestion control over reliable and unreliable data streams, single > association for multi-content data services, link level > fault tolerance for unreliable data transfer, unreliable data stream > multiplexing, etc. > > The unreliable data transfer service will also support partial payload > checksum in order to facilitate bit-error tolerance media > applications. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-sigtran-usctp-01.txt > > Internet-Drafts are also available by anonymous FTP. Login with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-sigtran-usctp-01.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-sigtran-usctp-01.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. _______________________________________________ tsvwg mailing list tsvwg@ietf.org http://www1.ietf.org/mailman/listinfo/tsvwg
- [Tsvwg] RE: I-D ACTION:draft-ietf-sigtran-usctp-0… Jon Berger
- [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usctp-0… Qiaobing Xie
- RE: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… Jon Berger
- Re: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… Randall R. Stewart
- RE: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… john.loughney
- RE: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… KaCheong.Leung
- Re: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… Randall R. Stewart
- Re: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… Qiaobing Xie
- Re: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… Randall R. Stewart
- Re: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… Ian Rytina
- RE: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… john.loughney
- Re: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… Qiaobing Xie
- Re: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… Qiaobing Xie
- Re: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… Randall R. Stewart
- Re: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… Randall R. Stewart
- Re: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… Qiaobing Xie
- Re: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… Randall R. Stewart
- Re: [Tsvwg] Re: I-D ACTION:draft-ietf-sigtran-usc… Qiaobing Xie