Re: [Gen-art] Gen-ART review of draft-ietf-tsvwg-sctp-strrst-12

Michael Tuexen <tuexen@fh-muenster.de> Fri, 02 December 2011 21:25 UTC

Return-Path: <tuexen@fh-muenster.de>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32A8B11E8110 for <gen-art@ietfa.amsl.com>; Fri, 2 Dec 2011 13:25:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.243
X-Spam-Level:
X-Spam-Status: No, score=-2.243 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FFqS-OVaeN+z for <gen-art@ietfa.amsl.com>; Fri, 2 Dec 2011 13:25:43 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 44CDA11E80D0 for <gen-art@ietf.org>; Fri, 2 Dec 2011 13:25:42 -0800 (PST)
Received: from [192.168.1.200] (p508F9B37.dip.t-dialin.net [80.143.155.55]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 036BE1C0C0BCE; Fri, 2 Dec 2011 22:25:39 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset="iso-8859-1"
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <4ED936E9.9040402@bell-labs.com>
Date: Fri, 02 Dec 2011 22:25:38 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <D03638C3-51E3-455D-B3D5-25586F92A15A@fh-muenster.de>
References: <4ED66709.50304@bell-labs.com> <22C7D48E-485B-4333-B29A-DB16BCCD3626@fh-muenster.de> <4ED69BB9.4030001@bell-labs.com> <4369045C-3B5C-4310-BF67-D141A34498BB@fh-muenster.de> <4ED936E9.9040402@bell-labs.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: gorry@erg.abdn.ac.uk, Wesley Eddy <wes@mti-systems.com>, draft-ietf-tsvwg-sctp-strrst@tools.ietf.org, "James M. Polk" <jmpolk@cisco.com>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-tsvwg-sctp-strrst-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2011 21:25:44 -0000

On Dec 2, 2011, at 9:36 PM, Vijay K. Gurbani wrote:

> On 12/02/2011 02:11 AM, Michael Tuexen wrote:
>> What about:
>> 
>> <t>One important thing to remember about SCTP streams is that they
>> are uni-directional. The endpoint for which a stream is an outgoing
>> stream is called the outgoing side, the endpoint for which the
>> stream is an incoming stream is called the incoming side.
> 
> Michael: I would reword the above as "The endpoint that originates
> the SCTP connection (resulting the the associated stream) is the
> outgoing side and the recipient of that SCTP connection becomes the
> incoming side."
Hi Vijay,

the above is incorrect... It is not important which side establishes
the SCTP association. No matter how it was established, a uni-directional
stream is outgoing for one side, incoming for the other.
After the association has been established, you have n uni-directional
streams from A to B, and m uni-directional streams from B to A.

For the n streams, A is the outgoing side, B the incoming. For the m
streams, B is the outgoing side, A is the incoming side. No matter
if A is client, B is server, vice versa, or both were acting as peers.

Best regards
Michael
> 
> The rest of what you write below is fine.
> 
>> The procedures outlined in this section are designed so that the
>> incoming side will always reset their stream sequence number first
>> before the outgoing side which means the re-configuration request
>> must always originate from the outgoing side. These two issues have
>> important ramifications upon how an SCTP endpoint might request that
>> its incoming streams be reset. In effect it must ask the peer to
>> start an outgoing reset procedure and once that request is
>> acknowledged let the peer actually control the reset operation.</t>
> 
> Whether or not to include issue of glare, I will leave up to you.
> 
> Thanks,
> 
> - vijay
> -- 
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web:   http://ect.bell-labs.com/who/vkg/
>