
From gorry@erg.abdn.ac.uk  Tue Mar  1 10:35:48 2011
Return-Path: <gorry@erg.abdn.ac.uk>
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 7F99E3A6A3B for <tsvwg@core3.amsl.com>; Tue,  1 Mar 2011 10:35:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102
X-Spam-Level: 
X-Spam-Status: No, score=-102 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 V+g+flOuVJFC for <tsvwg@core3.amsl.com>; Tue,  1 Mar 2011 10:35:47 -0800 (PST)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id 436F43A6A10 for <tsvwg@ietf.org>; Tue,  1 Mar 2011 10:35:46 -0800 (PST)
Received: from gorry-mac.erg.abdn.ac.uk ([IPv6:2001:630:241:207:21f:5bff:fe38:7354]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id p21IafaM020947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 1 Mar 2011 18:36:41 GMT
Message-ID: <4D6D3CB9.4080108@erg.abdn.ac.uk>
Date: Tue, 01 Mar 2011 18:36:41 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
Subject: Updated TSVWG: session conflict list
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
Cc: tsvwg WG <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
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: Tue, 01 Mar 2011 18:35:48 -0000

David, we've trimmed the list as follows:

Level 1: iccrg, 6man ecrit geopriv sipcore tcpm conex ledbat mptcp
  mmusic mboned dccp

Level 2: multimob v6ops behave dispatch tmrg pim storm alto
atoca pcn ccamp

Please avoid all other TSV area sessions, including tsvarea.

Note for the next meeting the following will also change:

DISPATCH will move up to a level 1
DCCP will move down to a level 2,
SIPCORE will move down to a level 2

- Do you want to get some of this captured in the meetings tool, so it 
doesn't get lost?

Gorry

From jmpolk@cisco.com  Tue Mar  1 11:00:37 2011
Return-Path: <jmpolk@cisco.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 011F13A6A74 for <tsvwg@core3.amsl.com>; Tue,  1 Mar 2011 11:00:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 uYJIOhxfzRyS for <tsvwg@core3.amsl.com>; Tue,  1 Mar 2011 11:00:36 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 478C83A6A79 for <tsvwg@ietf.org>; Tue,  1 Mar 2011 11:00:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=369; q=dns/txt; s=iport; t=1299006100; x=1300215700; h=message-id:date:to:from:subject:mime-version; bh=yRWqioVA1f6T1NtMwY5S2CW09nSlDlHN8uJgFJy1dA8=; b=LyEqbQZumCSSMsP0zNo5b+8f24krlNPObMB6Esj7d1KXEQqNoxyfC+7b RSCp4EbMKv0viHLdaUN0R2SPmRrjuTC1yeGExE3L/xPbgbEKCgezQ/fcb 01SXd2JsnWm++Tvs8lRc3YEkRxR632w7npJqqTcrJO4CMkQd8kGtRMYqi 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEALTRbE2rRN+K/2dsb2JhbACmT3SgT5wbhWEEhRI
X-IronPort-AV: E=Sophos;i="4.62,248,1297036800"; d="scan'208";a="411516883"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-1.cisco.com with ESMTP; 01 Mar 2011 19:01:39 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p21J1dLK016838 for <tsvwg@ietf.org>; Tue, 1 Mar 2011 19:01:39 GMT
Message-Id: <201103011901.p21J1dLK016838@sj-core-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 01 Mar 2011 13:01:37 -0600
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: WGLC ends for draft-ietf-tsvwg-sctpsocket-26
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Tue, 01 Mar 2011 19:00:37 -0000

WG

There has been sufficient, albeit late, reviews and comments for the 
chairs to consider the WGLC for draft-ietf-tsvwg-sctpsocket-26 done.

Authors - please incorporate those comments made during into a -27 
version and post this version, which the chairs will forward to the 
ADs for their consideration for RFC publication.

James & Gorry
TSVWG chairs


From ietfdbh@comcast.net  Tue Mar  1 11:50:57 2011
Return-Path: <ietfdbh@comcast.net>
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 858103A6A79 for <tsvwg@core3.amsl.com>; Tue,  1 Mar 2011 11:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.272
X-Spam-Level: 
X-Spam-Status: No, score=-102.272 tagged_above=-999 required=5 tests=[AWL=-0.273, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
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 FkljI5Bok6Xn for <tsvwg@core3.amsl.com>; Tue,  1 Mar 2011 11:50:56 -0800 (PST)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by core3.amsl.com (Postfix) with ESMTP id 931F23A6A44 for <tsvwg@ietf.org>; Tue,  1 Mar 2011 11:50:56 -0800 (PST)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta03.westchester.pa.mail.comcast.net with comcast id DvqG1g0031vXlb853vs1K4; Tue, 01 Mar 2011 19:52:01 +0000
Received: from davidPC ([67.189.235.106]) by omta17.westchester.pa.mail.comcast.net with comcast id Dvrz1g00K2JQnJT3dvrzuq; Tue, 01 Mar 2011 19:52:00 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <gorry@erg.abdn.ac.uk>
References: <4D6D3CB9.4080108@erg.abdn.ac.uk>
In-Reply-To: <4D6D3CB9.4080108@erg.abdn.ac.uk>
Subject: RE: Updated TSVWG: session conflict list
Date: Tue, 1 Mar 2011 14:51:56 -0500
Message-ID: <587E0D7704BC40BB99A10718FBB93E84@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7600.16543
Thread-Index: AcvYP6ANbGIs23V6SPe8Uhxitk75MAACmROQ
Cc: 'tsvwg WG' <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: Tue, 01 Mar 2011 19:50:57 -0000

If you can enter it there, that would be helpful.
Let me know if that is a problem.

dbh 

> -----Original Message-----
> From: Gorry Fairhurst [mailto:gorry@erg.abdn.ac.uk] 
> Sent: Tuesday, March 01, 2011 1:37 PM
> To: David Harrington
> Cc: tsvwg WG
> Subject: Updated TSVWG: session conflict list
> 
> 
> David, we've trimmed the list as follows:
> 
> Level 1: iccrg, 6man ecrit geopriv sipcore tcpm conex ledbat mptcp
>   mmusic mboned dccp
> 
> Level 2: multimob v6ops behave dispatch tmrg pim storm alto
> atoca pcn ccamp
> 
> Please avoid all other TSV area sessions, including tsvarea.
> 
> Note for the next meeting the following will also change:
> 
> DISPATCH will move up to a level 1
> DCCP will move down to a level 2,
> SIPCORE will move down to a level 2
> 
> - Do you want to get some of this captured in the meetings 
> tool, so it 
> doesn't get lost?
> 
> Gorry
> 


From Michael.Tuexen@lurchi.franken.de  Tue Mar  1 12:06:29 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 EF2A33A6A8C for <tsvwg@core3.amsl.com>; Tue,  1 Mar 2011 12:06:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.256
X-Spam-Level: 
X-Spam-Status: No, score=-2.256 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 Mso7ystgyUAt for <tsvwg@core3.amsl.com>; Tue,  1 Mar 2011 12:06:29 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id 082043A6A16 for <tsvwg@ietf.org>; Tue,  1 Mar 2011 12:06:28 -0800 (PST)
Received: from [192.168.1.113] (p508FC90C.dip.t-dialin.net [80.143.201.12]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id AB1561C0C0BCC; Tue,  1 Mar 2011 21:07:30 +0100 (CET)
Subject: Re: WGLC ends for draft-ietf-tsvwg-sctpsocket-26
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <201103011901.p21J1dLK016838@sj-core-4.cisco.com>
Date: Tue, 1 Mar 2011 21:07:29 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <43B28C18-692C-4942-BBFF-B150ACC9C8AE@lurchi.franken.de>
References: <201103011901.p21J1dLK016838@sj-core-4.cisco.com>
To: James M. Polk <jmpolk@cisco.com>
X-Mailer: Apple Mail (2.1082)
Cc: tsvwg <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: Tue, 01 Mar 2011 20:06:30 -0000

On Mar 1, 2011, at 8:01 PM, James M. Polk wrote:

> WG
>=20
> There has been sufficient, albeit late, reviews and comments for the =
chairs to consider the WGLC for draft-ietf-tsvwg-sctpsocket-26 done.
>=20
> Authors - please incorporate those comments made during into a -27 =
version and post this version, which the chairs will forward to the ADs =
for their consideration for RFC publication.
Hi James,

Done.

Best regards
Michael
>=20
> James & Gorry
> TSVWG chairs
>=20
>=20


From Internet-Drafts@ietf.org  Tue Mar  1 12:15:02 2011
Return-Path: <Internet-Drafts@ietf.org>
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 1E36E3A6A8C; Tue,  1 Mar 2011 12:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 OFwhmCYlXfXI; Tue,  1 Mar 2011 12:15:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 725563A6A16; Tue,  1 Mar 2011 12:15:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-tsvwg-sctpsocket-27.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110301201501.32416.42444.idtracker@localhost>
Date: Tue, 01 Mar 2011 12:15:01 -0800
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: Tue, 01 Mar 2011 20:15:02 -0000

--NextPart

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           : Sockets API Extensions for Stream Control Transmission Protocol (SCTP)
	Author(s)       : R. Stewart, et al.
	Filename        : draft-ietf-tsvwg-sctpsocket-27.txt
	Pages           : 111
	Date            : 2011-03-01

This document describes a mapping of the Stream Control Transmission
Protocol (SCTP) into a sockets API.  The benefits of this mapping
include compatibility for TCP applications, access to new SCTP
features and a consolidated error and event notification scheme.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctpsocket-27.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.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-tsvwg-sctpsocket-27.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-01120539.I-D@ietf.org>


--NextPart--

From magnus.westerlund@ericsson.com  Tue Mar  1 23:49:05 2011
Return-Path: <magnus.westerlund@ericsson.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 F12DA3A6ABB for <tsvwg@core3.amsl.com>; Tue,  1 Mar 2011 23:49:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.114
X-Spam-Level: 
X-Spam-Status: No, score=-106.114 tagged_above=-999 required=5 tests=[AWL=-0.115, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 NO6E2ludNMqE for <tsvwg@core3.amsl.com>; Tue,  1 Mar 2011 23:49:05 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id D86543A68B3 for <tsvwg@ietf.org>; Tue,  1 Mar 2011 23:49:04 -0800 (PST)
X-AuditID: c1b4fb39-b7c6dae0000023f2-98-4d6df6b05b2e
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id E6.FE.09202.0B6FD6D4; Wed,  2 Mar 2011 08:50:08 +0100 (CET)
Received: from [147.214.183.8] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.2.234.1; Wed, 2 Mar 2011 08:50:07 +0100
Message-ID: <4D6DF6B0.6060701@ericsson.com>
Date: Wed, 2 Mar 2011 08:50:08 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>
Subject: Re: Updated TSVWG: session conflict list
References: <4D6D3CB9.4080108@erg.abdn.ac.uk>
In-Reply-To: <4D6D3CB9.4080108@erg.abdn.ac.uk>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: tsvwg WG <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: Wed, 02 Mar 2011 07:49:06 -0000

Hi,

I think AVTCore belongs on Level 2 currently due to the ECN for RTP work
ongoing in that WG that seem relevant for TSVWG.

Cheers

Magnus

Gorry Fairhurst skrev 2011-03-01 19:36:
> 
> David, we've trimmed the list as follows:
> 
> Level 1: iccrg, 6man ecrit geopriv sipcore tcpm conex ledbat mptcp
>   mmusic mboned dccp
> 
> Level 2: multimob v6ops behave dispatch tmrg pim storm alto
> atoca pcn ccamp
> 
> Please avoid all other TSV area sessions, including tsvarea.
> 
> Note for the next meeting the following will also change:
> 
> DISPATCH will move up to a level 1
> DCCP will move down to a level 2,
> SIPCORE will move down to a level 2
> 
> - Do you want to get some of this captured in the meetings tool, so it 
> doesn't get lost?
> 
> Gorry
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From fluffy@cisco.com  Wed Mar  2 13:31:49 2011
Return-Path: <fluffy@cisco.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 E9C8D3A6850 for <tsvwg@core3.amsl.com>; Wed,  2 Mar 2011 13:31:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.547
X-Spam-Level: 
X-Spam-Status: No, score=-110.547 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100, WEIRD_PORT=0.001]
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 n7E2SEZm-l1P for <tsvwg@core3.amsl.com>; Wed,  2 Mar 2011 13:31:49 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id F23063A6816 for <tsvwg@ietf.org>; Wed,  2 Mar 2011 13:31:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=1355; q=dns/txt; s=iport; t=1299101576; x=1300311176; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=BeihX0V5UAWry86VoxspvDApmLO5BdSRpawk+cguLKA=; b=b8wgdd6DO5AfIpeq9/LgWTsFKTE21lzybr5rvJHbAibSZXVbqW2Tpur5 7w7gHGDzhwABgNyA1VFUU+O68a7p9TFyERZvkOxL69YpK7RHd9KFr6vHt 5zBl6rO/hcXnFlwZ/VLT7xpU7pSDll+o3ubN0xA2q0St5CZtTLdF/0hDP 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAB5Gbk2rRN+K/2dsb2JhbACmcHSidJwChWEEhReHD4NA
X-IronPort-AV: E=Sophos;i="4.62,255,1297036800"; d="scan'208";a="411783458"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-1.cisco.com with ESMTP; 02 Mar 2011 21:32:55 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p22LWsee015021; Wed, 2 Mar 2011 21:32:54 GMT
Subject: Re: [dccp] WGLC for draft-ietf-dccp-udpencap
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <0F4E2D93-F132-4FE8-AF69-8313A0B0BD69@iki.fi>
Date: Wed, 2 Mar 2011 14:35:26 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <640EB785-03DD-41BA-ABB5-C490556C63FB@cisco.com>
References: <9610_1298631433_ZZ0LH600GE26F708.00_9847_1298631427_4D678B03_9847_2510_1_51F3C3D7-3CA1-4A4E-AAF3-A526F253B497@iki.fi> <0F4E2D93-F132-4FE8-AF69-8313A0B0BD69@iki.fi>
To: Pasi Sarolahti <pasi.sarolahti@iki.fi>
X-Mailer: Apple Mail (2.1082)
Cc: tsvwg IETF list <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: Wed, 02 Mar 2011 21:31:50 -0000

I'm wondering what would be the downside of saying the UDP source / dest =
port had to match the DCCP source and dest port?  This would make it =
much easier to figure out hot to integrate this into something like ICE =
or decide what UDP and DCCP ports one uses for a URL like =
sip:example.com:5060


On Feb 28, 2011, at 2:09 AM, Pasi Sarolahti wrote:

> Hello,
>=20
> We just started DCCP WG last call on draft-ietf-dccp-udpencap that =
specifies UDP encapsulation for DCCP packets (see pointer below). The =
issue of UDP encapsulation was discussed earlier also on this list, so =
people might be interested to read the draft. Please send comments to =
the DCCP mailing list <dccp@ietf.org> by March 11.
>=20
> Thanks!
>=20
> - Pasi
>=20
>=20
> Begin forwarded message:
>=20
>> From: Pasi Sarolahti <pasi.sarolahti@iki.fi>
>> Date: February 25, 2011 12:56:46 PM GMT+02:00
>> To: 'dccp' working group <dccp@ietf.org>
>> Subject: [dccp] WGLC for draft-ietf-dccp-udpencap
>>=20
>> Hi,
>>=20
>> This mail starts a working group last call for the UDP encapsulation =
draft. The draft is available at =
http://tools.ietf.org/html/draft-ietf-dccp-udpencap-06 . Please read the =
draft and send any comments to the DCCP mailing list.
>>=20
>> The WGLC lasts for two weeks, until March 11.
>>=20
>> - Pasi
>>=20
>=20


From randall@lakerest.net  Wed Mar  2 18:56:41 2011
Return-Path: <randall@lakerest.net>
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 5FAE03A6936 for <tsvwg@core3.amsl.com>; Wed,  2 Mar 2011 18:56:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, WEIRD_PORT=0.001]
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 o4a62IwnWkbC for <tsvwg@core3.amsl.com>; Wed,  2 Mar 2011 18:56:40 -0800 (PST)
Received: from lakerest.net (lakerest.net [70.155.160.98]) by core3.amsl.com (Postfix) with ESMTP id E8F3A3A6403 for <tsvwg@ietf.org>; Wed,  2 Mar 2011 18:56:39 -0800 (PST)
Received: from [192.168.1.65] ([50.36.28.77]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p232u1h6055311 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 2 Mar 2011 21:56:07 -0500 (EST) (envelope-from randall@lakerest.net)
Subject: Re: [dccp] WGLC for draft-ietf-dccp-udpencap
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <640EB785-03DD-41BA-ABB5-C490556C63FB@cisco.com>
Date: Wed, 2 Mar 2011 21:55:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA6A8036-93FC-4E1B-A73A-026E2ABF973F@lakerest.net>
References: <9610_1298631433_ZZ0LH600GE26F708.00_9847_1298631427_4D678B03_9847_2510_1_51F3C3D7-3CA1-4A4E-AAF3-A526F253B497@iki.fi> <0F4E2D93-F132-4FE8-AF69-8313A0B0BD69@iki.fi> <640EB785-03DD-41BA-ABB5-C490556C63FB@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1082)
Cc: tsvwg IETF list <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: Thu, 03 Mar 2011 02:56:41 -0000

Cullen:

(not having read the draft.. :0)

Your idea makes me wonder... would that not also pollute the UDP port =
space? After all then
you are burning a UDP port for every DCCP (or am I mis-understanding =
you)? If not this
seems a waste..

R
On Mar 2, 2011, at 4:35 PM, Cullen Jennings wrote:

>=20
> I'm wondering what would be the downside of saying the UDP source / =
dest port had to match the DCCP source and dest port?  This would make =
it much easier to figure out hot to integrate this into something like =
ICE or decide what UDP and DCCP ports one uses for a URL like =
sip:example.com:5060
>=20
>=20
> On Feb 28, 2011, at 2:09 AM, Pasi Sarolahti wrote:
>=20
>> Hello,
>>=20
>> We just started DCCP WG last call on draft-ietf-dccp-udpencap that =
specifies UDP encapsulation for DCCP packets (see pointer below). The =
issue of UDP encapsulation was discussed earlier also on this list, so =
people might be interested to read the draft. Please send comments to =
the DCCP mailing list <dccp@ietf.org> by March 11.
>>=20
>> Thanks!
>>=20
>> - Pasi
>>=20
>>=20
>> Begin forwarded message:
>>=20
>>> From: Pasi Sarolahti <pasi.sarolahti@iki.fi>
>>> Date: February 25, 2011 12:56:46 PM GMT+02:00
>>> To: 'dccp' working group <dccp@ietf.org>
>>> Subject: [dccp] WGLC for draft-ietf-dccp-udpencap
>>>=20
>>> Hi,
>>>=20
>>> This mail starts a working group last call for the UDP encapsulation =
draft. The draft is available at =
http://tools.ietf.org/html/draft-ietf-dccp-udpencap-06 . Please read the =
draft and send any comments to the DCCP mailing list.
>>>=20
>>> The WGLC lasts for two weeks, until March 11.
>>>=20
>>> - Pasi
>>>=20
>>=20
>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From pasi.sarolahti@iki.fi  Thu Mar  3 01:47:45 2011
Return-Path: <pasi.sarolahti@iki.fi>
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 634623A69A2; Thu,  3 Mar 2011 01:47:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=-2.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100, WEIRD_PORT=0.001]
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 OJcDRtOunEKZ; Thu,  3 Mar 2011 01:47:44 -0800 (PST)
Received: from smtp.netlab.hut.fi (luuri.netlab.hut.fi [130.233.154.177]) by core3.amsl.com (Postfix) with ESMTP id 713E43A69A1; Thu,  3 Mar 2011 01:47:44 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.netlab.hut.fi (Postfix) with ESMTP id 0CCAB1E132; Thu,  3 Mar 2011 11:48:48 +0200 (EET)
X-Virus-Scanned: by amavisd-new at luuri.netlab.hut.fi
Received: from smtp.netlab.hut.fi ([127.0.0.1]) by localhost (luuri.netlab.hut.fi [127.0.0.1]) (amavisd-new, port 10024) with LMTP id rlsNctpipPOg; Thu,  3 Mar 2011 11:48:44 +0200 (EET)
Received: from pc74.netlab.hut.fi (pc74.netlab.hut.fi [130.233.154.74]) by smtp.netlab.hut.fi (Postfix) with ESMTPSA id 47E701E0C0; Thu,  3 Mar 2011 11:48:44 +0200 (EET)
Subject: Re: [dccp] WGLC for draft-ietf-dccp-udpencap
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Pasi Sarolahti <pasi.sarolahti@iki.fi>
In-Reply-To: <375_1299101583_ZZ0LHG00G4S972T0.00_640EB785-03DD-41BA-ABB5-C490556C63FB@cisco.com>
Date: Thu, 3 Mar 2011 11:48:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <20328115-B657-407F-B1D5-CF292B440855@iki.fi>
References: <9610_1298631433_ZZ0LH600GE26F708.00_9847_1298631427_4D678B03_9847_2510_1_51F3C3D7-3CA1-4A4E-AAF3-A526F253B497@iki.fi> <0F4E2D93-F132-4FE8-AF69-8313A0B0BD69@iki.fi> <375_1299101583_ZZ0LHG00G4S972T0.00_640EB785-03DD-41BA-ABB5-C490556C63FB@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1082)
Cc: 'dccp' working group <dccp@ietf.org>, tsvwg IETF list <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: Thu, 03 Mar 2011 09:47:45 -0000

Hi Cullen,

(cc:ing dccp mailing list as well)

The dccp/udp port issues were discussed in the DCCP WG some time ago. =
With the source port one problem is that a NAT could change the UDP port =
but not the inner DCCP port. There were opinions for keeping the two =
port spaces separate, to support tunneling scenarios through a =
well-known UDP port at the server end.

- Pasi


On Mar 2, 2011, at 11:35 PM, Cullen Jennings wrote:

> I'm wondering what would be the downside of saying the UDP source / =
dest port had to match the DCCP source and dest port?  This would make =
it much easier to figure out hot to integrate this into something like =
ICE or decide what UDP and DCCP ports one uses for a URL like =
sip:example.com:5060


From jmpolk@cisco.com  Sun Mar  6 18:12:21 2011
Return-Path: <jmpolk@cisco.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 ADA813A68BC for <tsvwg@core3.amsl.com>; Sun,  6 Mar 2011 18:12:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.583
X-Spam-Level: 
X-Spam-Status: No, score=-110.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 GjgsR-RIT8A3 for <tsvwg@core3.amsl.com>; Sun,  6 Mar 2011 18:12:20 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id C92413A68BA for <tsvwg@ietf.org>; Sun,  6 Mar 2011 18:12:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=523; q=dns/txt; s=iport; t=1299464013; x=1300673613; h=message-id:date:to:from:subject:mime-version; bh=mkHx2I02EEw3j/JbRVrx8dLHFbrt0bDBGJnPYx0W3W4=; b=OD+DUXTGfbnFaSYftu6Betvd4CBGgeauy0mPpgY9gy1Df936rCc2FlvU No3ZXb9gGsXGZ532mC8ZpzH5yXjxTpLj3Cdy41iBBCPskGxNPgWd9ec3d FsC9zVjENGrQV0mctcoAyOyaYDBFJFXOWsI84Flk/DygcNoaM9vDPijem o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAIPNc02rR7Hu/2dsb2JhbACmTXSjOpp9hWIEhRw
X-IronPort-AV: E=Sophos;i="4.62,274,1297036800"; d="scan'208";a="340761983"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 07 Mar 2011 02:13:33 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p272DWQR016380 for <tsvwg@ietf.org>; Mon, 7 Mar 2011 02:13:33 GMT
Message-Id: <201103070213.p272DWQR016380@sj-core-5.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 06 Mar 2011 20:13:32 -0600
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Call for Agenda items for IETF 80 (Prague)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 07 Mar 2011 02:12:21 -0000

TSVWG

We chairs are asking TSVWG for requests to present IDs during our 
session.  You need to give us your name, the ID you want to present 
material from, and the amount of time you would like to have to 
present (generally at 10 min slot per preso).

Presentations will have the following priority:

1 - TSVWG items
2 - Items positively discussed at previous meetings
3 - new work of interest to the WG

Please send your request to BOTH chairs (so each has a record of it).

James & Gorry
TSVWG Chairs


From rrs@lakerest.net  Mon Mar  7 14:33:06 2011
Return-Path: <rrs@lakerest.net>
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 759FB3A6955 for <tsvwg@core3.amsl.com>; Mon,  7 Mar 2011 14:33:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 GLbP0wRcqKBR for <tsvwg@core3.amsl.com>; Mon,  7 Mar 2011 14:33:05 -0800 (PST)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id EE0583A6809 for <tsvwg@ietf.org>; Mon,  7 Mar 2011 14:33:04 -0800 (PST)
Received: from [10.1.1.53] ([10.1.1.53]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p27MYFWP033376 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <tsvwg@ietf.org>; Mon, 7 Mar 2011 17:34:15 -0500 (EST) (envelope-from rrs@lakerest.net)
From: Randall Stewart <rrs@lakerest.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Fwd: SCTP API document.. 
Date: Mon, 7 Mar 2011 17:34:15 -0500
References: <201103072140.p27Le5QE051998@chez.mckusick.com>
To: tsvwg IETF list <tsvwg@ietf.org>
Message-Id: <8037A893-D2A9-4C5E-96A4-E57AD7D23D49@lakerest.net>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
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, 07 Mar 2011 22:33:06 -0000

All:

A bit late but Kirk did finally reply..

I answered his query about the deprecated features... I am not sure
if we can do anything about the way bindx works...

The non-mention of the replacement for the deprecated interface is probably
an easy fix.

R

Begin forwarded message:

> From: Kirk McKusick
> Date: March 7, 2011 4:40:05 PM EST
> To: Randall Stewart <rrs@lakerest.net>
> Subject: Re: SCTP API document.. 
> 
>> From: Randall Stewart <rrs@lakerest.net>
>> Subject: Re: SCTP API document.. 
>> Date: Mon, 28 Feb 2011 06:00:06 -0500
>> To: Kirk McKusick <mckusick@mckusick.com>
>> 
>> Kirk:
>> 
>> Your input would be appreciated... You might want to just
>> scan the document.. its pretty large ;-0
>> 
>> http://www.ietf.org/id/draft-ietf-tsvwg-sctpsocket-26.txt
>> 
>> The above link is the last version.. There were some minor english
>> comments just discussed on the list (Michael T prompted a few people
>> as well and one of them did a detailed review)...
>> 
>> I understand your time crunch... it would be nice if you
>> make a couple of comments though ;-)
>> 
>> R
> 
> Finally got around to looking at this document (well version 27
> actually :) It was the first time that I had dived down into the
> details of SCTP. You have done a good job of integrating it into
> the historic sockets interface. As this was my first time looking
> at SCTP I cannot be much help in finding bugs. So my comments are
> limited to things that I found confusing.
> 
> The 6.2.1. SCTP_EVENTS option is DEPRECATED. Most of the DEPRECATED
> interfaces start with a note pointing to what should be used in its
> place. This interface lacks that pointer (though the replacement
> does follow immediately).
> 
> Also, I am curious why a new standard documents already deprecated
> interfaces? Is it that existing implementations have them?
> 
> In 9.1. sctp_bindx() if one of several addresses fails the whole
> thing fails with no indication of which address caused the problem.
> This is reminicent of IBM JCL days when a single mistype in a
> 50-card deck caused the whole thing to be rejected with no
> indication of what was wrong. The only solution was to go through
> card-by-card to find the problem. That is the suggested solution 
> here. One would hope that in fifty years we could do better. In
> reading this interface my take was never to specify more than one
> address per call.
> 
> 	~Kirk
> 

------------------------------
Randall Stewart
803-317-4952 (cell)


From Michael.Tuexen@lurchi.franken.de  Tue Mar  8 01:07:28 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 EE5153A67AC for <tsvwg@core3.amsl.com>; Tue,  8 Mar 2011 01:07:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.262
X-Spam-Level: 
X-Spam-Status: No, score=-2.262 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 9ogs-t+H6F2C for <tsvwg@core3.amsl.com>; Tue,  8 Mar 2011 01:07:28 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id A48EC3A67F5 for <tsvwg@ietf.org>; Tue,  8 Mar 2011 01:07:27 -0800 (PST)
Received: from [192.168.1.198] (p508FCEF7.dip.t-dialin.net [80.143.206.247]) (Authenticated sender: micmac) by mail-n.franken.de (Postfix) with ESMTP id E9A8D1C0C0BD6; Tue,  8 Mar 2011 10:08:39 +0100 (CET)
Subject: Re: SCTP API document.. 
Mime-Version: 1.0 (Apple Message framework v1203)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <8037A893-D2A9-4C5E-96A4-E57AD7D23D49@lakerest.net>
Date: Tue, 8 Mar 2011 10:08:39 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <00B3E637-8FB5-4CB9-B046-E61C48028693@lurchi.franken.de>
References: <201103072140.p27Le5QE051998@chez.mckusick.com> <8037A893-D2A9-4C5E-96A4-E57AD7D23D49@lakerest.net>
To: Randall Stewart <rrs@lakerest.net>
X-Mailer: Apple Mail (2.1203)
Cc: tsvwg IETF list <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: Tue, 08 Mar 2011 09:07:29 -0000

On Mar 7, 2011, at 11:34 PM, Randall Stewart wrote:

> All:
> 
> A bit late but Kirk did finally reply..
> 
> I answered his query about the deprecated features... I am not sure
> if we can do anything about the way bindx works...
> 
> The non-mention of the replacement for the deprecated interface is probably
> an easy fix.
I'll add such a sentence and we can include this in the next
rev (assuming there is one based on the comments we get from the IETF LC).

Regarding the sctp_bindx() comment: We state this in the last paragraph
of the sctp_bindx() section, were we state that it might be a good idea
to use a single address only.

Best regards
Michael
> 
> R
> 
> Begin forwarded message:
> 
>> From: Kirk McKusick
>> Date: March 7, 2011 4:40:05 PM EST
>> To: Randall Stewart <rrs@lakerest.net>
>> Subject: Re: SCTP API document.. 
>> 
>>> From: Randall Stewart <rrs@lakerest.net>
>>> Subject: Re: SCTP API document.. 
>>> Date: Mon, 28 Feb 2011 06:00:06 -0500
>>> To: Kirk McKusick <mckusick@mckusick.com>
>>> 
>>> Kirk:
>>> 
>>> Your input would be appreciated... You might want to just
>>> scan the document.. its pretty large ;-0
>>> 
>>> http://www.ietf.org/id/draft-ietf-tsvwg-sctpsocket-26.txt
>>> 
>>> The above link is the last version.. There were some minor english
>>> comments just discussed on the list (Michael T prompted a few people
>>> as well and one of them did a detailed review)...
>>> 
>>> I understand your time crunch... it would be nice if you
>>> make a couple of comments though ;-)
>>> 
>>> R
>> 
>> Finally got around to looking at this document (well version 27
>> actually :) It was the first time that I had dived down into the
>> details of SCTP. You have done a good job of integrating it into
>> the historic sockets interface. As this was my first time looking
>> at SCTP I cannot be much help in finding bugs. So my comments are
>> limited to things that I found confusing.
>> 
>> The 6.2.1. SCTP_EVENTS option is DEPRECATED. Most of the DEPRECATED
>> interfaces start with a note pointing to what should be used in its
>> place. This interface lacks that pointer (though the replacement
>> does follow immediately).
>> 
>> Also, I am curious why a new standard documents already deprecated
>> interfaces? Is it that existing implementations have them?
>> 
>> In 9.1. sctp_bindx() if one of several addresses fails the whole
>> thing fails with no indication of which address caused the problem.
>> This is reminicent of IBM JCL days when a single mistype in a
>> 50-card deck caused the whole thing to be rejected with no
>> indication of what was wrong. The only solution was to go through
>> card-by-card to find the problem. That is the suggested solution 
>> here. One would hope that in fifty years we could do better. In
>> reading this interface my take was never to specify more than one
>> address per call.
>> 
>> 	~Kirk
>> 
> 
> ------------------------------
> Randall Stewart
> 803-317-4952 (cell)
> 
> 


From rrs@lakerest.net  Tue Mar  8 02:18:49 2011
Return-Path: <rrs@lakerest.net>
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 E5AAC3A67DA for <tsvwg@core3.amsl.com>; Tue,  8 Mar 2011 02:18:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 R5UVzgo2yBwV for <tsvwg@core3.amsl.com>; Tue,  8 Mar 2011 02:18:49 -0800 (PST)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 785B93A681B for <tsvwg@ietf.org>; Tue,  8 Mar 2011 02:18:48 -0800 (PST)
Received: from [10.1.1.53] ([10.1.1.53]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p28AJwZB058918 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 8 Mar 2011 05:19:59 -0500 (EST) (envelope-from rrs@lakerest.net)
Subject: Re: SCTP API document.. 
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Randall Stewart <rrs@lakerest.net>
In-Reply-To: <00B3E637-8FB5-4CB9-B046-E61C48028693@lurchi.franken.de>
Date: Tue, 8 Mar 2011 05:19:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4D7C411-B607-4F16-9B71-DC3426C6C504@lakerest.net>
References: <201103072140.p27Le5QE051998@chez.mckusick.com> <8037A893-D2A9-4C5E-96A4-E57AD7D23D49@lakerest.net> <00B3E637-8FB5-4CB9-B046-E61C48028693@lurchi.franken.de>
To: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.1082)
Cc: tsvwg IETF list <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: Tue, 08 Mar 2011 10:18:50 -0000

On Mar 8, 2011, at 4:08 AM, Michael T=FCxen wrote:

> On Mar 7, 2011, at 11:34 PM, Randall Stewart wrote:
>=20
>> All:
>>=20
>> A bit late but Kirk did finally reply..
>>=20
>> I answered his query about the deprecated features... I am not sure
>> if we can do anything about the way bindx works...
>>=20
>> The non-mention of the replacement for the deprecated interface is =
probably
>> an easy fix.
> I'll add such a sentence and we can include this in the next
> rev (assuming there is one based on the comments we get from the IETF =
LC).
>=20
> Regarding the sctp_bindx() comment: We state this in the last =
paragraph
> of the sctp_bindx() section, were we state that it might be a good =
idea
> to use a single address only.

Yeah, I know.. and I think thats Kirk's comment... basically it
would be nice if you did NOT have to do that...

But I do not see an easy alternative ;-0

R


>=20
> Best regards
> Michael
>>=20
>> R
>>=20
>> Begin forwarded message:
>>=20
>>> From: Kirk McKusick
>>> Date: March 7, 2011 4:40:05 PM EST
>>> To: Randall Stewart <rrs@lakerest.net>
>>> Subject: Re: SCTP API document..=20
>>>=20
>>>> From: Randall Stewart <rrs@lakerest.net>
>>>> Subject: Re: SCTP API document..=20
>>>> Date: Mon, 28 Feb 2011 06:00:06 -0500
>>>> To: Kirk McKusick <mckusick@mckusick.com>
>>>>=20
>>>> Kirk:
>>>>=20
>>>> Your input would be appreciated... You might want to just
>>>> scan the document.. its pretty large ;-0
>>>>=20
>>>> http://www.ietf.org/id/draft-ietf-tsvwg-sctpsocket-26.txt
>>>>=20
>>>> The above link is the last version.. There were some minor english
>>>> comments just discussed on the list (Michael T prompted a few =
people
>>>> as well and one of them did a detailed review)...
>>>>=20
>>>> I understand your time crunch... it would be nice if you
>>>> make a couple of comments though ;-)
>>>>=20
>>>> R
>>>=20
>>> Finally got around to looking at this document (well version 27
>>> actually :) It was the first time that I had dived down into the
>>> details of SCTP. You have done a good job of integrating it into
>>> the historic sockets interface. As this was my first time looking
>>> at SCTP I cannot be much help in finding bugs. So my comments are
>>> limited to things that I found confusing.
>>>=20
>>> The 6.2.1. SCTP_EVENTS option is DEPRECATED. Most of the DEPRECATED
>>> interfaces start with a note pointing to what should be used in its
>>> place. This interface lacks that pointer (though the replacement
>>> does follow immediately).
>>>=20
>>> Also, I am curious why a new standard documents already deprecated
>>> interfaces? Is it that existing implementations have them?
>>>=20
>>> In 9.1. sctp_bindx() if one of several addresses fails the whole
>>> thing fails with no indication of which address caused the problem.
>>> This is reminicent of IBM JCL days when a single mistype in a
>>> 50-card deck caused the whole thing to be rejected with no
>>> indication of what was wrong. The only solution was to go through
>>> card-by-card to find the problem. That is the suggested solution=20
>>> here. One would hope that in fifty years we could do better. In
>>> reading this interface my take was never to specify more than one
>>> address per call.
>>>=20
>>> 	~Kirk
>>>=20
>>=20
>> ------------------------------
>> Randall Stewart
>> 803-317-4952 (cell)
>>=20
>>=20
>=20

------------------------------
Randall Stewart
803-317-4952 (cell)


From Michael.Tuexen@lurchi.franken.de  Tue Mar  8 02:46:43 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 00ACD3A6834 for <tsvwg@core3.amsl.com>; Tue,  8 Mar 2011 02:46:43 -0800 (PST)
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.033,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 wPj3nt10aeKh for <tsvwg@core3.amsl.com>; Tue,  8 Mar 2011 02:46:42 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id 407153A6835 for <tsvwg@ietf.org>; Tue,  8 Mar 2011 02:46:41 -0800 (PST)
Received: from [192.168.1.198] (p508FCEF7.dip.t-dialin.net [80.143.206.247]) (Authenticated sender: micmac) by mail-n.franken.de (Postfix) with ESMTP id 358761C0C0BD6; Tue,  8 Mar 2011 11:47:55 +0100 (CET)
Subject: Re: SCTP API document.. 
Mime-Version: 1.0 (Apple Message framework v1203)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <B4D7C411-B607-4F16-9B71-DC3426C6C504@lakerest.net>
Date: Tue, 8 Mar 2011 11:47:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD5FF8A6-609A-4AE3-B109-1741A712869B@lurchi.franken.de>
References: <201103072140.p27Le5QE051998@chez.mckusick.com> <8037A893-D2A9-4C5E-96A4-E57AD7D23D49@lakerest.net> <00B3E637-8FB5-4CB9-B046-E61C48028693@lurchi.franken.de> <B4D7C411-B607-4F16-9B71-DC3426C6C504@lakerest.net>
To: Randall Stewart <rrs@lakerest.net>
X-Mailer: Apple Mail (2.1203)
Cc: tsvwg IETF list <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: Tue, 08 Mar 2011 10:46:43 -0000

On Mar 8, 2011, at 11:19 AM, Randall Stewart wrote:
>=20
> On Mar 8, 2011, at 4:08 AM, Michael T=FCxen wrote:
>=20
>> On Mar 7, 2011, at 11:34 PM, Randall Stewart wrote:
>>=20
>>> All:
>>>=20
>>> A bit late but Kirk did finally reply..
>>>=20
>>> I answered his query about the deprecated features... I am not sure
>>> if we can do anything about the way bindx works...
>>>=20
>>> The non-mention of the replacement for the deprecated interface is =
probably
>>> an easy fix.
>> I'll add such a sentence and we can include this in the next
>> rev (assuming there is one based on the comments we get from the IETF =
LC).
>>=20
>> Regarding the sctp_bindx() comment: We state this in the last =
paragraph
>> of the sctp_bindx() section, were we state that it might be a good =
idea
>> to use a single address only.
>=20
> Yeah, I know.. and I think thats Kirk's comment... basically it
> would be nice if you did NOT have to do that...
>=20
> But I do not see an easy alternative ;-0
I think for sctp_bindx() we have to keep it. But MPTCP is
another protocol providing support for multihoming.

For binding multiple addresses they refer to sctp_bindx().
But I think sctp_bindx() should be SCTP specific, and
we possibly should define a bindx(), or whatever you
would name it, call which support SCTP and MPTCP, which
only accepts one address. This is pretty much what Kacheong
suggested years ago... I still have to send comments regarding
the MPTCP API ID...

Best regards
Michael
>=20
> R
>=20
>=20
>>=20
>> Best regards
>> Michael
>>>=20
>>> R
>>>=20
>>> Begin forwarded message:
>>>=20
>>>> From: Kirk McKusick
>>>> Date: March 7, 2011 4:40:05 PM EST
>>>> To: Randall Stewart <rrs@lakerest.net>
>>>> Subject: Re: SCTP API document..=20
>>>>=20
>>>>> From: Randall Stewart <rrs@lakerest.net>
>>>>> Subject: Re: SCTP API document..=20
>>>>> Date: Mon, 28 Feb 2011 06:00:06 -0500
>>>>> To: Kirk McKusick <mckusick@mckusick.com>
>>>>>=20
>>>>> Kirk:
>>>>>=20
>>>>> Your input would be appreciated... You might want to just
>>>>> scan the document.. its pretty large ;-0
>>>>>=20
>>>>> http://www.ietf.org/id/draft-ietf-tsvwg-sctpsocket-26.txt
>>>>>=20
>>>>> The above link is the last version.. There were some minor english
>>>>> comments just discussed on the list (Michael T prompted a few =
people
>>>>> as well and one of them did a detailed review)...
>>>>>=20
>>>>> I understand your time crunch... it would be nice if you
>>>>> make a couple of comments though ;-)
>>>>>=20
>>>>> R
>>>>=20
>>>> Finally got around to looking at this document (well version 27
>>>> actually :) It was the first time that I had dived down into the
>>>> details of SCTP. You have done a good job of integrating it into
>>>> the historic sockets interface. As this was my first time looking
>>>> at SCTP I cannot be much help in finding bugs. So my comments are
>>>> limited to things that I found confusing.
>>>>=20
>>>> The 6.2.1. SCTP_EVENTS option is DEPRECATED. Most of the DEPRECATED
>>>> interfaces start with a note pointing to what should be used in its
>>>> place. This interface lacks that pointer (though the replacement
>>>> does follow immediately).
>>>>=20
>>>> Also, I am curious why a new standard documents already deprecated
>>>> interfaces? Is it that existing implementations have them?
>>>>=20
>>>> In 9.1. sctp_bindx() if one of several addresses fails the whole
>>>> thing fails with no indication of which address caused the problem.
>>>> This is reminicent of IBM JCL days when a single mistype in a
>>>> 50-card deck caused the whole thing to be rejected with no
>>>> indication of what was wrong. The only solution was to go through
>>>> card-by-card to find the problem. That is the suggested solution=20
>>>> here. One would hope that in fifty years we could do better. In
>>>> reading this interface my take was never to specify more than one
>>>> address per call.
>>>>=20
>>>> 	~Kirk
>>>>=20
>>>=20
>>> ------------------------------
>>> Randall Stewart
>>> 803-317-4952 (cell)
>>>=20
>>>=20
>>=20
>=20
> ------------------------------
> Randall Stewart
> 803-317-4952 (cell)
>=20
>=20


From rrs@lakerest.net  Tue Mar  8 04:08:49 2011
Return-Path: <rrs@lakerest.net>
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 C64473A6839 for <tsvwg@core3.amsl.com>; Tue,  8 Mar 2011 04:08:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.374
X-Spam-Level: 
X-Spam-Status: No, score=-2.374 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 JZk5eO4uzZaM for <tsvwg@core3.amsl.com>; Tue,  8 Mar 2011 04:08:49 -0800 (PST)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 70AA93A6821 for <tsvwg@ietf.org>; Tue,  8 Mar 2011 04:08:48 -0800 (PST)
Received: from [10.1.1.53] ([10.1.1.53]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p28CA1CO063103 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 8 Mar 2011 07:10:01 -0500 (EST) (envelope-from rrs@lakerest.net)
Subject: Re: SCTP API document.. 
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Randall Stewart <rrs@lakerest.net>
In-Reply-To: <AD5FF8A6-609A-4AE3-B109-1741A712869B@lurchi.franken.de>
Date: Tue, 8 Mar 2011 07:10:00 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F1D6208-C7D1-4492-99E4-4DE2AE35BBDA@lakerest.net>
References: <201103072140.p27Le5QE051998@chez.mckusick.com> <8037A893-D2A9-4C5E-96A4-E57AD7D23D49@lakerest.net> <00B3E637-8FB5-4CB9-B046-E61C48028693@lurchi.franken.de> <B4D7C411-B607-4F16-9B71-DC3426C6C504@lakerest.net> <AD5FF8A6-609A-4AE3-B109-1741A712869B@lurchi.franken.de>
To: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.1082)
Cc: tsvwg IETF list <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: Tue, 08 Mar 2011 12:08:49 -0000

On Mar 8, 2011, at 5:47 AM, Michael T=FCxen wrote:

> On Mar 8, 2011, at 11:19 AM, Randall Stewart wrote:
>>=20
>> On Mar 8, 2011, at 4:08 AM, Michael T=FCxen wrote:
>>=20
>>> On Mar 7, 2011, at 11:34 PM, Randall Stewart wrote:
>>>=20
>>>> All:
>>>>=20
>>>> A bit late but Kirk did finally reply..
>>>>=20
>>>> I answered his query about the deprecated features... I am not sure
>>>> if we can do anything about the way bindx works...
>>>>=20
>>>> The non-mention of the replacement for the deprecated interface is =
probably
>>>> an easy fix.
>>> I'll add such a sentence and we can include this in the next
>>> rev (assuming there is one based on the comments we get from the =
IETF LC).
>>>=20
>>> Regarding the sctp_bindx() comment: We state this in the last =
paragraph
>>> of the sctp_bindx() section, were we state that it might be a good =
idea
>>> to use a single address only.
>>=20
>> Yeah, I know.. and I think thats Kirk's comment... basically it
>> would be nice if you did NOT have to do that...
>>=20
>> But I do not see an easy alternative ;-0
> I think for sctp_bindx() we have to keep it. But MPTCP is
> another protocol providing support for multihoming.
>=20
> For binding multiple addresses they refer to sctp_bindx().
> But I think sctp_bindx() should be SCTP specific, and
> we possibly should define a bindx(), or whatever you
> would name it, call which support SCTP and MPTCP, which
> only accepts one address. This is pretty much what Kacheong
> suggested years ago... I still have to send comments regarding
> the MPTCP API ID...
>=20

Ahh, I did not know they had one.. I will have to look at it.

R=20

------------------------------
Randall Stewart
803-317-4952 (cell)


From fluffy@cisco.com  Tue Mar  8 12:38:23 2011
Return-Path: <fluffy@cisco.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 DE82E3A67B3; Tue,  8 Mar 2011 12:38:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.555
X-Spam-Level: 
X-Spam-Status: No, score=-110.555 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100, WEIRD_PORT=0.001]
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 WAJYWEEPOEhV; Tue,  8 Mar 2011 12:38:22 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id EDCE13A6781; Tue,  8 Mar 2011 12:38:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=1161; q=dns/txt; s=iport; t=1299616777; x=1300826377; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=FAKCsVDqHDzfgNYPxLoFX+SZTJ004aWWWCXm97gLvoU=; b=JAwQ1hPgp2f9hYWX7Tgs/J+Vx62k5blkgmFR0BFdjrnHSmJg7BOmJTdw ftYSzKKxjOtls+B3FsuraKLk/6P0iF1D0gtgP8kxZj6zF3dBfGzFLsbst uE912UQOH5R5ba9NZoWKQhVrRnnMERHWE61mUfWx6f2/wpgkqpdmZnsNN o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEADUjdk2rRN+K/2dsb2JhbACmY3SjR5wrhWMEhR2HFYNH
X-IronPort-AV: E=Sophos;i="4.62,285,1297036800"; d="scan'208";a="272739360"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 08 Mar 2011 20:39:37 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p28KdajS015182; Tue, 8 Mar 2011 20:39:36 GMT
Subject: Re: [dccp] WGLC for draft-ietf-dccp-udpencap
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <20328115-B657-407F-B1D5-CF292B440855@iki.fi>
Date: Tue, 8 Mar 2011 13:42:11 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F8C22210-CC16-43C1-9E2A-87D1367FF79C@cisco.com>
References: <9610_1298631433_ZZ0LH600GE26F708.00_9847_1298631427_4D678B03_9847_2510_1_51F3C3D7-3CA1-4A4E-AAF3-A526F253B497@iki.fi> <0F4E2D93-F132-4FE8-AF69-8313A0B0BD69@iki.fi> <375_1299101583_ZZ0LHG00G4S972T0.00_640EB785-03DD-41BA-ABB5-C490556C63FB@cisco.com> <20328115-B657-407F-B1D5-CF292B440855@iki.fi>
To: Pasi Sarolahti <pasi.sarolahti@iki.fi>
X-Mailer: Apple Mail (2.1082)
Cc: 'dccp' working group <dccp@ietf.org>, tsvwg IETF list <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: Tue, 08 Mar 2011 20:38:23 -0000

How about the destination ports need to match and we don't worry as much =
about the source ports? If we have to have specify both the udp and dccp =
destination port, I have no idea how existing applications are going to =
be able to easily use this. What would you even put in a DNS SRV record.=20=


On Mar 3, 2011, at 2:48 AM, Pasi Sarolahti wrote:

> Hi Cullen,
>=20
> (cc:ing dccp mailing list as well)
>=20
> The dccp/udp port issues were discussed in the DCCP WG some time ago. =
With the source port one problem is that a NAT could change the UDP port =
but not the inner DCCP port. There were opinions for keeping the two =
port spaces separate, to support tunneling scenarios through a =
well-known UDP port at the server end.
>=20
> - Pasi
>=20
>=20
> On Mar 2, 2011, at 11:35 PM, Cullen Jennings wrote:
>=20
>> I'm wondering what would be the downside of saying the UDP source / =
dest port had to match the DCCP source and dest port?  This would make =
it much easier to figure out hot to integrate this into something like =
ICE or decide what UDP and DCCP ports one uses for a URL like =
sip:example.com:5060
>=20


From bob.briscoe@bt.com  Wed Mar  9 05:45:56 2011
Return-Path: <bob.briscoe@bt.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 8264F3A69E5 for <tsvwg@core3.amsl.com>; Wed,  9 Mar 2011 05:45:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.337
X-Spam-Level: 
X-Spam-Status: No, score=-3.337 tagged_above=-999 required=5 tests=[AWL=0.262,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 WNZ0iHZTUnNB for <tsvwg@core3.amsl.com>; Wed,  9 Mar 2011 05:45:55 -0800 (PST)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id 6239C3A6855 for <tsvwg@ietf.org>; Wed,  9 Mar 2011 05:45:54 -0800 (PST)
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 9 Mar 2011 13:47:09 +0000
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by i2kc08-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 9 Mar 2011 13:47:09 +0000
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1299678428462; Wed, 9 Mar 2011 13:47:08 +0000
Received: from MUT.jungle.bt.co.uk ([10.215.131.97]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id p29Dl79Q025812; Wed, 9 Mar 2011 13:47:07 GMT
Message-Id: <201103091347.p29Dl79Q025812@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 09 Mar 2011 13:47:10 +0000
To: Mirja Kuehlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>
From: Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: I-D Action:draft-ietf-tsvwg-byte-pkt-congest-03.txt
In-Reply-To: <201102221938.48204.mirja.kuehlewind@ikr.uni-stuttgart.de>
References: <20101025221535.A7CE33A68B7@core3.amsl.com> <201102221938.48204.mirja.kuehlewind@ikr.uni-stuttgart.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 09 Mar 2011 13:47:09.0468 (UTC) FILETIME=[7C59D5C0:01CBDE60]
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: Wed, 09 Mar 2011 13:45:56 -0000

Mirja,

Belated thanks for this.

We will address your comments, hopefully producing a rev this week.


Bob

At 18:38 22/02/2011, Mirja Kuehlewind wrote:
>Hi,
>
>I reviewed the doc. Here are comments:
>
>-> I haven't read the previous version but I still find the doc quite hard=
 to
>read. I would prefer to have the recommendation right after the=
 introduction
>and all kind of reasoning afterwards. The whole section "1.2 Why now?"=
 might
>not be intresting for somebody how really wants a recommendation. Maybe=
 move
>it to the appendix.
>
>-> You mention this mail [pktByteEmail] at least 4 times at different=
 places.
>After a while I really got annoyed reading the same things over and over
>again... as the doc is anyway quite long, maybe there is an option to=
 shorten
>this.
>
>-> 1. Introduction
>------------------
>   - page 6, 1. paragraph:
>     "However, there are ways of addressing these issues at the transport
>     layer, rather than reverse engineering network forwarding to fix the
>     problems of one specific transport."
>     At this point in the doc it is not clear if the network is reverse
>engineering the transport or vice versa...
>
>   - page 6, 4 paragraph:
>     Reference to RFC 3465 - TCP Congestion Control with Appropriate Byte
>Counting (ABC)?
>
>   - page 6, 3. paragraph:
>     Maybe have a brief list with the arguments described in 2. Motivating
>Arguments. I would say, if somebody is reading the doc to get some
>recommendations he would like to hear some arguments right at the beginning
>but having the full discussion is not necessary. That's why I would move 2.
>Motivating Arguments after the recommendation section itself.
>
>   - 1.2. Why now:
>      Its 2. and 3. the same?
>      Would move the whole section to the appendix...
>
>-> 2. Motivating Arguments
>------
>   - 2.3. page 12, 2. paragraph
>     From my point of view does this example give the main reason why
>packet-mode drop is the right thing to do and all other points just support
>this with examples showing that either byte-mode drop is wrong or=
 packet-size
>congestion control would be the easier solution. But the example is
>complicated to read and the reason itself is never clearly stated: Network
>should provide the same behavior against all flows (in this case the same
>rate reduction) independent of their higher level characteristics!
>I would include this example in the introduction and maybe a table like=
 this
>might help (?):
>Packet Size                     1500B           60B
># of packet per 1.2 sec 100                     2500
>drop probability                25%                     1%
># of drops                      25                      25
>rate=20
>reduction                  300k                    12k
>With the first reading I was confused because the example says XX% of=
 packets
>drops. But as there is a different number of packet in the same time, this
>equals XX% of bits dropped. Maybe this table is a way to make this more
>explicit and thus easier to read (or maybe its just me....). Moreover, you
>could include a picture like this:
>
>1 Mbps ---------|       25%             |----------750 kbps
>                         |       RED             |
>1 Mbps............      |       1%              |.............990 kbps
>
>Further remarks on the example to make thing clearer:
>- The rates are not the link capacity but the=20
>transmission rates if sufficient
>link capacity is available.
>- The RED queue would just operate in a certain=20
>state with 25% and 1% drop but
>whenever RED is dropping packets the one probability will be 25 times=
 larger
>than the other.
>- This is the troughput not the goodput. Thus header overhead it not taken
>into account.
>
>-> 3. Recommendations
>-----------------
>   - 3.1. Recommendations on Queue Measurement
>     The 2. paragraph says the same than the 2. corollary. Also I don't=
 know
>why the 2. corollary says "If RED is used" because this is true for all=
 queue
>measurements. This paragraph should be the first collary and for the other
>one I would suggest to rephrase to:
>"An Admin SHOULD NOT be able to configure the way a queue measures itself,
>because wether a queue is bit-congestible or packet-congestible is a=
 property
>of the resource."
>Maybe add an example here.
>
>   - 3.2. page 14, 4. paragraph NOTE WELL
>     This is important for understanding the whole wording used. Maybe make
>this statement earlier more explicit.
>
>   - 3.3. Both corollaries basically say if=20
> modifications are needed because of
>layer-specific characteristics, those changes MUST be done in the same=
 layer
>and MUST never been done in any layer below.
>But the question left open here is: If the network is doing the wrong thing
>and I can't know what the network is doing, how can I do the right thing
>(e.g. to get equal rates)?
>
>-> 4. A Survey and Critique of Past Advice
>------------------------
>   - 4.1.: 1. paragraph: Do you have the respective reference?
>   - 4.2.3.: 1.paragraph: "... these two proposal are safer and ..." Why=
 are
>they safer?
>   - 4.2.3.: 2.paragraph: Doesn't this give a new option for attacks?
>
>-> Would move 4.2.5. to Appendix
>
>-> Even though section 4. and 5. are intresting to read, I would see this=
 doc
>as a guideline for implementers or transport designers. Some point are more
>about open research issues. Maybe there is a way to shorten these parts (or
>to move them into a second doc...). Maybe have something like implementor's
>guidelines or design principles instead. Allover the message of the doc is
>(more or less) quite simple but the long discussions on various different
>side effects makes the doc hard to read and it's hard to focus on the
>actually statement.
>
>-> I like the conclusion!
>
>Mirja
>
>
>On Tuesday 26 October 2010 00:15:32 Internet-Drafts@ietf.org wrote:
> > 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           : Byte and Packet Congestion Notification
> >       Author(s)       : B. Briscoe, J. Manner
> >       Filename        : draft-ietf-tsvwg-byte-pkt-congest-03.txt
> >       Pages           : 41
> >       Date            : 2010-10-25
> >
> > This memo concerns dropping or marking packets using active queue
> > management (AQM) such as random early detection (RED) or pre-
> > congestion notification (PCN).  We give three strong recommendations:
> > (1) packet size should be taken into account when transports read
> > congestion indications, (2) packet size should not be taken into
> > account when network equipment creates congestion signals (marking,
> > dropping), and therefore (3) the byte-mode packet drop variant of the
> > RED AQM algorithm that drops fewer small packets should not be used.
> >
> > A URL for this Internet-Draft is:
> >=
 http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-byte-pkt-congest-03.tx
> >t
> >
> > 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.
>
>
>
>--
>-------------------------------------------------------------------
>Dipl.-Ing. Mirja K=FChlewind
>Institute of Communication Networks and Computer Engineering (IKR)
>University of Stuttgart, Germany
>Pfaffenwaldring 47, D-70569 Stuttgart
>
>tel: +49(0)711/685-67973
>email: mirja.kuehlewind@ikr.uni-stuttgart.de
>web: www.ikr.uni-stuttgart.de
>-------------------------------------------------------------------

________________________________________________________________
Bob Briscoe,                                BT Innovate & Design=20


From jukka.manner@tkk.fi  Thu Mar 10 13:12:21 2011
Return-Path: <jukka.manner@tkk.fi>
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 DB7883A6922 for <tsvwg@core3.amsl.com>; Thu, 10 Mar 2011 13:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 EctpTpcJD0TY for <tsvwg@core3.amsl.com>; Thu, 10 Mar 2011 13:12:19 -0800 (PST)
Received: from smtp.netlab.hut.fi (luuri.netlab.hut.fi [130.233.154.177]) by core3.amsl.com (Postfix) with ESMTP id C17ED3A691F for <tsvwg@ietf.org>; Thu, 10 Mar 2011 13:12:18 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.netlab.hut.fi (Postfix) with ESMTP id BDE091E139; Thu, 10 Mar 2011 23:13:35 +0200 (EET)
X-Virus-Scanned: by amavisd-new at luuri.netlab.hut.fi
Received: from smtp.netlab.hut.fi ([127.0.0.1]) by localhost (luuri.netlab.hut.fi [127.0.0.1]) (amavisd-new, port 10024) with LMTP id zSAWp-PwLo9v; Thu, 10 Mar 2011 23:13:31 +0200 (EET)
Received: from [192.168.100.49] (a91-152-186-160.elisa-laajakaista.fi [91.152.186.160]) by smtp.netlab.hut.fi (Postfix) with ESMTPSA id 7692A1E120; Thu, 10 Mar 2011 23:13:31 +0200 (EET)
Message-ID: <4D793EFA.2030702@tkk.fi>
Date: Thu, 10 Mar 2011 23:13:30 +0200
From: Jukka Manner <jukka.manner@tkk.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9pre) Gecko/20100818 Lanikai/3.1.3pre
MIME-Version: 1.0
To: Mirja Kuehlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>
Subject: Re: I-D Action:draft-ietf-tsvwg-byte-pkt-congest-03.txt
References: <20101025221535.A7CE33A68B7@core3.amsl.com> <9610_1298399931_ZZ0LH100G797SQ19.00_201102221938.48204.mirja.kuehlewind@ikr.uni-stuttgart.de>
In-Reply-To: <9610_1298399931_ZZ0LH100G797SQ19.00_201102221938.48204.mirja.kuehlewind@ikr.uni-stuttgart.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 10 Mar 2011 21:12:21 -0000

Hi Mirja, thanks for the review. I'll comment on your feedback below.

cheers,
Jukka

On 02/22/2011 08:38 PM, Mirja Kuehlewind wrote:
> Hi,
>
> I reviewed the doc. Here are comments:
>
> ->  I haven't read the previous version but I still find the doc quite hard to
> read. I would prefer to have the recommendation right after the introduction
> and all kind of reasoning afterwards. The whole section "1.2 Why now?" might
> not be intresting for somebody how really wants a recommendation. Maybe move
> it to the appendix.

[JM]: I see this as important motivation. It is partly the same as in 
the introduction, so one option is to merge part of it with the main 
intro. I'd rather not put it away in the end.

>
> ->  You mention this mail [pktByteEmail] at least 4 times at different places.
> After a while I really got annoyed reading the same things over and over
> again... as the doc is anyway quite long, maybe there is an option to shorten
> this.

[JM]: Well, it is an important reference. :)

>
> ->  1. Introduction
> ------------------
>    - page 6, 1. paragraph:
>      "However, there are ways of addressing these issues at the transport
>      layer, rather than reverse engineering network forwarding to fix the
>      problems of one specific transport."
>      At this point in the doc it is not clear if the network is reverse
> engineering the transport or vice versa...

[JM]: Will rephrase.

>
>    - page 6, 4 paragraph:
>      Reference to RFC 3465 - TCP Congestion Control with Appropriate Byte
> Counting (ABC)?

[JM]: Sure, will add.

>
>    - page 6, 3. paragraph:
>      Maybe have a brief list with the arguments described in 2. Motivating
> Arguments. I would say, if somebody is reading the doc to get some
> recommendations he would like to hear some arguments right at the beginning
> but having the full discussion is not necessary. That's why I would move 2.
> Motivating Arguments after the recommendation section itself.

[JM]: Switching 2 & 3 could potentially work... I understand your point.

>
>    - 1.2. Why now:
>       Its 2. and 3. the same?
>       Would move the whole section to the appendix...

[JM]: Yes, pretty much, will remove the second one.

>
> ->  2. Motivating Arguments
> ------
>    - 2.3. page 12, 2. paragraph
>      From my point of view does this example give the main reason why
> packet-mode drop is the right thing to do and all other points just support
> this with examples showing that either byte-mode drop is wrong or packet-size
> congestion control would be the easier solution. But the example is
> complicated to read and the reason itself is never clearly stated: Network
> should provide the same behavior against all flows (in this case the same
> rate reduction) independent of their higher level characteristics!
> I would include this example in the introduction and maybe a table like this
> might help (?):
> Packet Size			1500B		60B
> # of packet per 1.2 sec	100			2500
> drop probability		25%			1%
> # of drops			25			25
> rate reduction			300k			12k			
> With the first reading I was confused because the example says XX% of packets
> drops. But as there is a different number of packet in the same time, this
> equals XX% of bits dropped. Maybe this table is a way to make this more
> explicit and thus easier to read (or maybe its just me....). Moreover, you
> could include a picture like this:
>
> 1 Mbps ---------|	25%		|----------750 kbps
> 			|	RED		|
> 1 Mbps............	|	1%		|.............990 kbps
>
> Further remarks on the example to make thing clearer:
> - The rates are not the link capacity but the transmission rates if sufficient
> link capacity is available.
> - The RED queue would just operate in a certain state with 25% and 1% drop but
> whenever RED is dropping packets the one probability will be 25 times larger
> than the other.
> - This is the troughput not the goodput. Thus header overhead it not taken
> into account.

[JM]: I'll rephrase the example to make it hopefully more clear.

>
> ->  3. Recommendations
> -----------------
>    - 3.1. Recommendations on Queue Measurement
>      The 2. paragraph says the same than the 2. corollary. Also I don't know
> why the 2. corollary says "If RED is used" because this is true for all queue
> measurements. This paragraph should be the first collary and for the other
> one I would suggest to rephrase to:
> "An Admin SHOULD NOT be able to configure the way a queue measures itself,
> because wether a queue is bit-congestible or packet-congestible is a property
> of the resource."
> Maybe add an example here.

[JM]: Rephrased the 2. collary, not sure your proposal would make the 
whole recommendation really more clear.

>
>    - 3.2. page 14, 4. paragraph NOTE WELL
>      This is important for understanding the whole wording
used. Maybe make
> this statement earlier more explicit.

[JM]: Any suggestion what/where to put?

>
>    - 3.3. Both corollaries basically say if modifications are needed because of
> layer-specific characteristics, those changes MUST be done in the same layer
> and MUST never been done in any layer below.
> But the question left open here is: If the network is doing the wrong thing
> and I can't know what the network is doing, how can I do the right thing
> (e.g. to get equal rates)?

[JM]: You can only affect how you behave, you can't really affect 
others' behavior. Just have to hope everybody behaves alike (in a good 
way). :)

>
> ->  4. A Survey and Critique of Past Advice
> ------------------------
>    - 4.1.: 1. paragraph: Do you have the respective reference?

[JM]: Will try to find something.

>    - 4.2.3.: 1.paragraph: "... these two proposal are safer and ..." Why are
> they safer?

[JM]: The point about favoring small packets within the network, which 
was deemed bad since the introduction.

>    - 4.2.3.: 2.paragraph: Doesn't this give a new option for attacks?

[JM]: DiffServ only works in practice in closely controlled 
environments, and you have to take that into account if you want to use 
DSCPs for triggering a certain response from the network.

>
> ->  Would move 4.2.5. to Appendix

[JM]: Not yet. ;)

>
> ->  Even though section 4. and 5. are intresting to read, I would see this doc
> as a guideline for implementers or transport designers. Some point are more
> about open research issues. Maybe there is a way to shorten these parts (or
> to move them into a second doc...). Maybe have something like implementor's
> guidelines or design principles instead. Allover the message of the doc is
> (more or less) quite simple but the long discussions on various different
> side effects makes the doc hard to read and it's hard to focus on the
> actually statement.

[JM]: IMO, Sections 4 & 5 are more concrete and important than the 
current appendix material, so would like to keep them within the main 
body of the doc.

>
> ->  I like the conclusion!
>
> Mirja
>
>
> On Tuesday 26 October 2010 00:15:32 Internet-Drafts@ietf.org wrote:
>> 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           : Byte and Packet Congestion Notification
>> 	Author(s)       : B. Briscoe, J. Manner
>> 	Filename        : draft-ietf-tsvwg-byte-pkt-congest-03.txt
>> 	Pages           : 41
>> 	Date            : 2010-10-25
>>
>> This memo concerns dropping or marking packets using active queue
>> management (AQM) such as random early detection (RED) or pre-
>> congestion notification (PCN).  We give three strong recommendations:
>> (1) packet size should be taken into account when transports read
>> congestion indications, (2) packet size should not be taken into
>> account when network equipment creates congestion signals (marking,
>> dropping), and therefore (3) the byte-mode packet drop variant of the
>> RED AQM algorithm that drops fewer small packets should not be used.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-byte-pkt-congest-03.tx
>> t
>>
>> 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.
>
>
>

From bob.briscoe@bt.com  Fri Mar 11 03:28:54 2011
Return-Path: <bob.briscoe@bt.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 40E6A3A68AA for <tsvwg@core3.amsl.com>; Fri, 11 Mar 2011 03:28:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.383
X-Spam-Level: 
X-Spam-Status: No, score=-3.383 tagged_above=-999 required=5 tests=[AWL=0.216,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 ICE5t7J6mksW for <tsvwg@core3.amsl.com>; Fri, 11 Mar 2011 03:28:52 -0800 (PST)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151]) by core3.amsl.com (Postfix) with ESMTP id 8C93C3A6846 for <tsvwg@ietf.org>; Fri, 11 Mar 2011 03:28:51 -0800 (PST)
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 11 Mar 2011 11:30:09 +0000
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by i2kc08-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.4675); Fri, 11 Mar 2011 11:30:05 +0000
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 129984300381; Fri, 11 Mar 2011 11:30:03 +0000
Received: from MUT.jungle.bt.co.uk ([10.73.176.21]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id p2BBU02r001761; Fri, 11 Mar 2011 11:30:01 GMT
Message-Id: <201103111130.p2BBU02r001761@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 11 Mar 2011 11:29:49 +0000
To: Mirja Kuehlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>, Jukka Manner <jukka.manner@tkk.fi>
From: Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: I-D Action:draft-ietf-tsvwg-byte-pkt-congest-03.txt
In-Reply-To: <4D793EFA.2030702@tkk.fi>
References: <20101025221535.A7CE33A68B7@core3.amsl.com> <9610_1298399931_ZZ0LH100G797SQ19.00_201102221938.48204.mirja.kuehlewind@ikr.uni-stuttgart.de> <4D793EFA.2030702@tkk.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 11 Mar 2011 11:30:05.0114 (UTC) FILETIME=[AB1481A0:01CBDFDF]
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: Fri, 11 Mar 2011 11:28:54 -0000

Mirja, Jukka,

Thanks Mirja for this review.

I've said nothing where I agree, and added responses where necessary. Inline...

At 21:13 10/03/2011, Jukka Manner wrote:
>Hi Mirja, thanks for the review. I'll comment on your feedback below.
>
>cheers,
>Jukka
>
>On 02/22/2011 08:38 PM, Mirja Kuehlewind wrote:
>>Hi,
>>
>>I reviewed the doc. Here are comments:
>>
>>->  I haven't read the previous version but I still find the doc 
>>quite hard to
>>read. I would prefer to have the recommendation right after the introduction
>>and all kind of reasoning afterwards. The whole section "1.2 Why now?" might
>>not be intresting for somebody how really wants a recommendation. Maybe move
>>it to the appendix.
>
>[JM]: I see this as important motivation. It is partly the same as 
>in the introduction, so one option is to merge part of it with the 
>main intro. I'd rather not put it away in the end.
>
>>
>>->  You mention this mail [pktByteEmail] at least 4 times at 
>>different places.
>>After a while I really got annoyed reading the same things over and over
>>again... as the doc is anyway quite long, maybe there is an option to shorten
>>this.
>
>[JM]: Well, it is an important reference. :)
>
>>
>>->  1. Introduction
>>------------------
>>    - page 6, 1. paragraph:
>>      "However, there are ways of addressing these issues at the transport
>>      layer, rather than reverse engineering network forwarding to fix the
>>      problems of one specific transport."
>>      At this point in the doc it is not clear if the network is reverse
>>engineering the transport or vice versa...
>
>[JM]: Will rephrase.
>
>>
>>    - page 6, 4 paragraph:
>>      Reference to RFC 3465 - TCP Congestion Control with Appropriate Byte
>>Counting (ABC)?
>
>[JM]: Sure, will add.

TCP ABC seems superficially relevant here, but it's not actually 
really relevant. On balance I would not add it here.

>>    - page 6, 3. paragraph:
>>      Maybe have a brief list with the arguments described in 2. Motivating
>>Arguments. I would say, if somebody is reading the doc to get some
>>recommendations he would like to hear some arguments right at the beginning
>>but having the full discussion is not necessary. That's why I would move 2.
>>Motivating Arguments after the recommendation section itself.
>
>[JM]: Switching 2 & 3 could potentially work... I understand your point.
>
>>
>>    - 1.2. Why now:
>>       Its 2. and 3. the same?
>>       Would move the whole section to the appendix...
>
>[JM]: Yes, pretty much, will remove the second one.

I'd suggest "Why now" would be best at the end of "Motivating 
Arguements", which as a whole would be better after the Recommendations.



>>->  2. Motivating Arguments
>>------
>>    - 2.3. page 12, 2. paragraph
>>      From my point of view does this example give the main reason why
>>packet-mode drop is the right thing to do and all other points just support
>>this with examples showing that either byte-mode drop is wrong or packet-size
>>congestion control would be the easier solution. But the example is
>>complicated to read and the reason itself is never clearly stated: Network
>>should provide the same behavior against all flows (in this case the same
>>rate reduction) independent of their higher level characteristics!
>>I would include this example in the introduction and maybe a table like this
>>might help (?):
>>Packet Size                     1500B           60B
>># of packet per 1.2 sec 100                     2500
>>drop probability                25%                     1%
>># of drops                      25                      25
>>rate 
>>reduction                  300k                    12k
>>With the first reading I was confused because the example says XX% of packets
>>drops. But as there is a different number of packet in the same time, this
>>equals XX% of bits dropped. Maybe this table is a way to make this more
>>explicit and thus easier to read (or maybe its just me....). Moreover, you
>>could include a picture like this:
>>
>>1 Mbps ---------|       25%             |----------750 kbps
>>                         |       RED             |
>>1 Mbps............      |       1%              |.............990 kbps
>>
>>Further remarks on the example to make thing clearer:
>>- The rates are not the link capacity but the transmission rates if 
>>sufficient
>>link capacity is available.
>>- The RED queue would just operate in a certain state with 25% and 
>>1% drop but
>>whenever RED is dropping packets the one probability will be 25 times larger
>>than the other.
>>- This is the troughput not the goodput. Thus header overhead it not taken
>>into account.
>
>[JM]: I'll rephrase the example to make it hopefully more clear.
>
>>
>>->  3. Recommendations
>>-----------------
>>    - 3.1. Recommendations on Queue Measurement
>>      The 2. paragraph says the same than the 2. corollary.

Para 2 makes a general statement, whereas corollary 2 is specific to 
the buzz-words used in RED.

>>Also I don't know
>>why the 2. corollary says "If RED is used" because this is true for all queue
>>measurements.

PCN != RED
DCTCP != RED.

>>This paragraph should be the first collary and for the other
>>one I would suggest to rephrase to:
>>"An Admin SHOULD NOT be able to configure the way a queue measures itself,
>>because wether a queue is bit-congestible or packet-congestible is a property
>>of the resource."

I think this is a better way round.

>>Maybe add an example here.
>
>[JM]: Rephrased the 2. collary, not sure your proposal would make 
>the whole recommendation really more clear.
>
>>
>>    - 3.2. page 14, 4. paragraph NOTE WELL
>>      This is important for understanding the whole wording
>used. Maybe make
>>this statement earlier more explicit.
>
>[JM]: Any suggestion what/where to put?

Tough. If we shift it to before the Corollaries, it means we have to 
say why we're saying it. I've got no problems with leaving it where it is.


>>    - 3.3. Both corollaries basically say if modifications are 
>> needed because of
>>layer-specific characteristics, those changes MUST be done in the same layer
>>and MUST never been done in any layer below.

The recommendations are stated in abstract terms, and the corllaries 
say what this means for specific popular protocols.

>>But the question left open here is: If the network is doing the wrong thing
>>and I can't know what the network is doing, how can I do the right thing
>>(e.g. to get equal rates)?
>
>[JM]: You can only affect how you behave, you can't really affect 
>others' behavior. Just have to hope everybody behaves alike (in a good way). :)

Yes. The message here is that no-one in the network layer seems to be 
doing differently from our earlier recommendation. So documenting it 
now might actually mean we have a useful standard behaviour that we 
can rely on.



>>->  4. A Survey and Critique of Past Advice
>>------------------------
>>    - 4.1.: 1. paragraph: Do you have the respective reference?
>
>[JM]: Will try to find something.

Only BytePktEmail (?!!!) and no-one contradicting it later.


>>    - 4.2.3.: 1.paragraph: "... these two proposal are safer and ..." Why are
>>they safer?
>
>[JM]: The point about favoring small packets within the network, 
>which was deemed bad since the introduction.
>
>>    - 4.2.3.: 2.paragraph: Doesn't this give a new option for attacks?
>
>[JM]: DiffServ only works in practice in closely controlled 
>environments, and you have to take that into account if you want to 
>use DSCPs for triggering a certain response from the network.
>
>>
>>->  Would move 4.2.5. to Appendix
>
>[JM]: Not yet. ;)
>
>>
>>->  Even though section 4. and 5. are intresting to read, I would 
>>see this doc
>>as a guideline for implementers or transport designers. Some point are more
>>about open research issues. Maybe there is a way to shorten these parts (or
>>to move them into a second doc...). Maybe have something like implementor's
>>guidelines or design principles instead. Allover the message of the doc is
>>(more or less) quite simple but the long discussions on various different
>>side effects makes the doc hard to read and it's hard to focus on the
>>actually statement.
>
>[JM]: IMO, Sections 4 & 5 are more concrete and important than the 
>current appendix material, so would like to keep them within the 
>main body of the doc.

Hopefully, putting the Recommendations up front (and in the 
conclusions) allows people to get the idea quickly. But the rest of 
the info needs to be in the doc for those who want/need specific 
advice for their particular scenario.


Bob



>>->  I like the conclusion!
>>
>>Mirja
>>
>>
>>On Tuesday 26 October 2010 00:15:32 Internet-Drafts@ietf.org wrote:
>>>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           : Byte and Packet Congestion Notification
>>>         Author(s)       : B. Briscoe, J. Manner
>>>         Filename        : draft-ietf-tsvwg-byte-pkt-congest-03.txt
>>>         Pages           : 41
>>>         Date            : 2010-10-25
>>>
>>>This memo concerns dropping or marking packets using active queue
>>>management (AQM) such as random early detection (RED) or pre-
>>>congestion notification (PCN).  We give three strong recommendations:
>>>(1) packet size should be taken into account when transports read
>>>congestion indications, (2) packet size should not be taken into
>>>account when network equipment creates congestion signals (marking,
>>>dropping), and therefore (3) the byte-mode packet drop variant of the
>>>RED AQM algorithm that drops fewer small packets should not be used.
>>>
>>>A URL for this Internet-Draft is:
>>>http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-byte-pkt-congest-03.tx
>>>t
>>>
>>>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.
>>
>>
>
>________________________________________________________________
>Bob Briscoe,                                BT Innovate & Design 


From wwwrun@rfc-editor.org  Sun Mar 13 11:48:32 2011
Return-Path: <wwwrun@rfc-editor.org>
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 3FC203A6B54 for <tsvwg@core3.amsl.com>; Sun, 13 Mar 2011 11:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.428
X-Spam-Level: 
X-Spam-Status: No, score=-102.428 tagged_above=-999 required=5 tests=[AWL=0.172, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 8T2mQm8276mr for <tsvwg@core3.amsl.com>; Sun, 13 Mar 2011 11:48:31 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 7D4FD3A68B3 for <tsvwg@ietf.org>; Sun, 13 Mar 2011 11:48:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 35D74E070A; Sun, 13 Mar 2011 11:49:54 -0700 (PDT)
To: michael.larsen@tieto.com, fernando@gont.com.ar, ietfdbh@comcast.net, lars.eggert@nokia.com, wes@mti-systems.com, jmpolk@cisco.com, gorry@erg.abdn.ac.uk
Subject: [Editorial Errata Reported] RFC6056 (2750)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20110313184954.35D74E070A@rfc-editor.org>
Date: Sun, 13 Mar 2011 11:49:54 -0700 (PDT)
Cc: bzeeb+ieft@zabbadoz.net, tsvwg@ietf.org, rfc-editor@rfc-editor.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: Sun, 13 Mar 2011 18:48:32 -0000

The following errata report has been submitted for RFC6056,
"Recommendations for Transport-Protocol Port Randomization".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6056&eid=2750

--------------------------------------
Type: Editorial
Reported by: Bjoern A. Zeeb <bzeeb+ieft@zabbadoz.net>

Section: 3.3

Original Text
-------------
3.3.1.  Algorithm 1: Simple Port Randomization Algorithm

-           if(check_suitable_port(port))

3.3.2.  Algorithm 2: Another Simple Port Randomization Algorithm

-           if(check_suitable_port(port))

Corrected Text
--------------
3.3.1.  Algorithm 1: Simple Port Randomization Algorithm

+           if(check_suitable_port(next_ephemeral))

3.3.2.  Algorithm 2: Another Simple Port Randomization Algorithm

+           if(check_suitable_port(next_ephemeral))

Notes
-----
For neither Algorithm 1 or 2 the pseudo code defines "port" as a valid variable.
The variable passed to check_suitable_port() should be "next_ephemeral" in these cases.
It looks like a copy and paste error. The technical meaning is still clear.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6056 (draft-ietf-tsvwg-port-randomization-09)
--------------------------------------
Title               : Recommendations for Transport-Protocol Port Randomization
Publication Date    : January 2011
Author(s)           : M. Larsen, F. Gont
Category            : BEST CURRENT PRACTICE
Source              : Transport Area Working Group
Area                : Transport
Stream              : IETF
Verifying Party     : IESG

From jmpolk@cisco.com  Sun Mar 13 13:47:31 2011
Return-Path: <jmpolk@cisco.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 DE1D93A6BA3 for <tsvwg@core3.amsl.com>; Sun, 13 Mar 2011 13:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.421
X-Spam-Level: 
X-Spam-Status: No, score=-110.421 tagged_above=-999 required=5 tests=[AWL=-0.178, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_6CONS_WORD=0.356, USER_IN_WHITELIST=-100]
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 QFl9Y1zMOpCv for <tsvwg@core3.amsl.com>; Sun, 13 Mar 2011 13:47:30 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id DE5313A6BA1 for <tsvwg@ietf.org>; Sun, 13 Mar 2011 13:47:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=1648; q=dns/txt; s=iport; t=1300049333; x=1301258933; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=/eblytwb+RjTyEHh2ig+0DklGqLr+xaHAbxyxXBS0TE=; b=lT8zqc/wqzM/bbqQACJTNu6pA4kFWTtL+tG3aR0V1EkCuHDlDcxMyvzH lF7T6QD0hxxMLCOr/6hToCq72ncY61i0+z4hz24lUTypl4blr83AAc80J DCKUfWe3a8rirNtknGeJOHHf+u77tGOFtv5pGuEC1Q/rwlg62Zb5/KNhh U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAF/KfE2tJV2Z/2dsb2JhbACmFnelPZprhWIEhSs
X-IronPort-AV: E=Sophos;i="4.62,311,1297036800"; d="scan'208";a="345525575"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by sj-iport-5.cisco.com with ESMTP; 13 Mar 2011 20:48:53 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2DKmrP1017369 for <tsvwg@ietf.org>; Sun, 13 Mar 2011 20:48:53 GMT
Message-Id: <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 13 Mar 2011 15:48:51 -0500
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
In-Reply-To: <201102080311.p183BpvU025288@sj-core-2.cisco.com>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Sun, 13 Mar 2011 20:47:32 -0000

TSVWG

The WG chairs have determined the WGLC for our SCTP Stream 
Reconfiguration ID continues (i.e., it has not concluded at the 2 
week window) due to lack of feedback to the list. No one has 
commented in a review format that they believe this ID should 
progress. No one has even sent a note merely saying this ID in its 
present form is good to go. That lack of any feedback is troubling 
and could be a sign of a lack of interest in this ID.

The WG chairs like the idea of (and within) this draft, but we need 
transport experts to tell us this, and if the ID in its present form 
is good enough to implement to without those implementations having 
errors or causing bad behavior in SCTP because of how the ID is 
written (focusing mostly on the instructions to implementers in the ID).

We chairs want folks to show or assert they have reviewed this ID and 
give feedback to the list (and not unicast to the chairs). This ID 
cannot progress without that feedback.

James & Gorry
TSVWG chairs


At 10:07 PM 2/7/2011, James M. Polk wrote:
>TSVWG
>
>I am starting the WGLC for
>
>"Stream Control Transmission Protocol (SCTP) Stream Reconfiguration"
>http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-strrst/
>
>this is a 2 week WGLC, ending February 22nd, 2011 or when the chairs 
>feel the WG has reviewed the draft and reached consensus to progress 
>towards the ADs with the goal of becoming a proposed standard (PS) RFC.
>
>The chairs require substantive feedback from the WG regarding this 
>draft before consensus can be called.
>
>I will be the document shepherd.
>
>James
>TSVWG chair


From bclaise@cisco.com  Mon Mar 14 00:01:54 2011
Return-Path: <bclaise@cisco.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 3B39B3A67FF; Mon, 14 Mar 2011 00:01:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.48
X-Spam-Level: 
X-Spam-Status: No, score=-2.48 tagged_above=-999 required=5 tests=[AWL=-0.237,  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 7uUVNFqaCP1W; Mon, 14 Mar 2011 00:01:53 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 0EC0A3A6B07; Mon, 14 Mar 2011 00:01:52 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2E73Fq5025014; Mon, 14 Mar 2011 08:03:15 +0100 (CET)
Received: from [10.55.43.52] (ams-bclaise-8713.cisco.com [10.55.43.52]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2E73Epn006181; Mon, 14 Mar 2011 08:03:14 +0100 (CET)
Message-ID: <4D7DBDB2.7010102@cisco.com>
Date: Mon, 14 Mar 2011 08:03:14 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>
In-Reply-To: <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ipfix@ietf.org" <ipfix@ietf.org>, Gerhard Muenz <muenz@net.in.tum.de>, tsvwg <tsvwg@ietf.org>, Andrew Johnson <andrjohn@cisco.com>, Paul Aitken <paitken@cisco.com>
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, 14 Mar 2011 07:01:54 -0000

Hi James,

> TSVWG
>
> The WG chairs have determined the WGLC for our SCTP Stream 
> Reconfiguration ID continues (i.e., it has not concluded at the 2 week 
> window) due to lack of feedback to the list. No one has commented in a 
> review format that they believe this ID should progress. No one has 
> even sent a note merely saying this ID in its present form is good to 
> go. That lack of any feedback is troubling and could be a sign of a 
> lack of interest in this ID.
I'm not a transport expert so I can't comment on the technical part.
However, there is a clear interest: the functionality in the draft is 
required. "The IPFIX export per SCTP stream", 
https://datatracker.ietf.org/doc/draft-ietf-ipfix-export-per-sctp-stream/ has 
been sitting for 8 months in the RFC editor queue, waiting for this draft.

Regards, Benoit.
>
> The WG chairs like the idea of (and within) this draft, but we need 
> transport experts to tell us this, and if the ID in its present form 
> is good enough to implement to without those implementations having 
> errors or causing bad behavior in SCTP because of how the ID is 
> written (focusing mostly on the instructions to implementers in the ID).
>
> We chairs want folks to show or assert they have reviewed this ID and 
> give feedback to the list (and not unicast to the chairs). This ID 
> cannot progress without that feedback.
>
> James & Gorry
> TSVWG chairs
>
>
> At 10:07 PM 2/7/2011, James M. Polk wrote:
>> TSVWG
>>
>> I am starting the WGLC for
>>
>> "Stream Control Transmission Protocol (SCTP) Stream Reconfiguration"
>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-strrst/
>>
>> this is a 2 week WGLC, ending February 22nd, 2011 or when the chairs 
>> feel the WG has reviewed the draft and reached consensus to progress 
>> towards the ADs with the goal of becoming a proposed standard (PS) RFC.
>>
>> The chairs require substantive feedback from the WG regarding this 
>> draft before consensus can be called.
>>
>> I will be the document shepherd.
>>
>> James
>> TSVWG chair


From ka-cheong.poon@oracle.com  Mon Mar 14 03:08:53 2011
Return-Path: <ka-cheong.poon@oracle.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 2E36F3A6914 for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 03:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.255
X-Spam-Level: 
X-Spam-Status: No, score=-2.255 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_STOCK2=3.988, RCVD_IN_DNSWL_MED=-4, 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 z5UCqftmwm10 for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 03:08:52 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 6BB323A6B2E for <tsvwg@ietf.org>; Mon, 14 Mar 2011 03:08:49 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2EAAAlo005383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Mon, 14 Mar 2011 10:10:11 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2EAA9xY030029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Mon, 14 Mar 2011 10:10:10 GMT
Received: from abhmt017.oracle.com (abhmt017.oracle.com [141.146.116.26]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2EAA9e6028366 for <tsvwg@ietf.org>; Mon, 14 Mar 2011 05:10:09 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 14 Mar 2011 03:10:08 -0700
Message-ID: <4D7DE97D.6010609@oracle.com>
Date: Mon, 14 Mar 2011 18:10:05 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>
In-Reply-To: <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt358.oracle.com [141.146.40.158]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090202.4D7DE982.00F0,ss=1,fgs=0
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, 14 Mar 2011 10:08:53 -0000

On 03/14/11 04:48 AM, James M. Polk wrote:

> We chairs want folks to show or assert they have reviewed this ID and
> give feedback to the list (and not unicast to the chairs). This ID
> cannot progress without that feedback.


I have several comments.

In the Introduction, the reasons to have a SCTP protocol level
mechanism (stream sequence number reset) to solve the app issue
are quite sketchy.  For example, one can envision that an app can
just remember the stream sequence number before it intends to
re-use a stream such that it can differentiate new and old messages.
Or there can be a shim layer below the app and above socket layer
to do this translation.  Or there can be a socket level option to
do the translation.  And all these can be combined with the app
layer protocol.  I think the draft should include more details on
why a SCTP protocol level mechanism is needed.  An example of real
use case which cannot be accomplished without a SCTP level mechanism
should probably be provided.

More importantly, the draft contains a mechanism to reset
transmission sequence number but there is no rationale given on why
this is necessary.  TSN should normally be opaque to applications
and should be used solely by SCTP for protocol handling.  It is
hard to see why a reset of TSN is needed to make an app work.  I
think there should be a very strong reason why such an SCTP protocol
mechanism is needed.  But the draft gives no reason.

I suggest that the new chunk be called "Stream Re-configuration"
since the chunk is also about adding new streams.  But even this
name does not cover the case of resetting TSN, which is at the
association level.  Is it correct to include a parameter which
affects the association level TSN in this chunk?  This also goes
back to the question about the reasons of having TSN reset.

The diagram in 3.1 is not correct.  It shows that the parameter
is only 4 bytes long.

In 4.1, the use of "Stream Reset Response Sequence Number" is
confusing.  The draft says

     When this Outgoing SSN Reset Request Parameter is sent in response
     to an Incoming SSN Reset Request Parameter this parameter is also
     an implicit response to the incoming request.

So a request is sent in response to another a request?  A response
to a request is understandable, and the response is either request
accepted or not.  But a request is sent responding to a request is
confusing.  It is like sending an SCTP_ABORT in response to an
SCTP_ABORT.

I suppose the rationale, as described in section 5, is that the
originator of resetting should be the outgoing side.  But this
raises the question of why then there is an Incoming SSN Reset
Request.  This just makes the mechanism unnecessarily more
complicated.  Given that the app layer protocol must first agree
on the reset operation, it is unclear why there is a need to have
the Incoming SSN Reset Request.  And if there is really such a
reason, then why does the same reason not applicable to the SSN/TSN
resetting and adding more streams?  So should there also be an
Incoming SSN/TSN Reset Request and Incoming Adding Streams Request?

I suppose there is only the need to have Outgoing SSN Reset Request.
The app layer protocol should handle which side does the initiation.
A consequence of not having Incoming request is that then there is
no need to have an optional second parameter in the chunk.  This
also eliminates race of Incoming/Outgoing requests cross over.
Given this simplicity, I think the draft should provide a reason
that the Incoming request is absolutely necessary.

In first sentence of 4.3, does "all streams" mean "all outgoing
streams" or "all incoming streams?"

If a reset timer is running, no other request can be sent out.  So
there can only be one outstanding unacknowledged request.  I suggest
that this is mentioned explicitly in 5.1.1.

In 6.2, I think it is incorrect to change sctp_event_subscribe
and use SCTP_EVENTS option because they are deprecated.  It should
only mention the SCTP_EVENT option.

In all the new events, there are "denied" and "failed" events.  It
is not clear what "failed" means.  The peer does not respond to
a request and the association times out?  I suggest that it should
be made clearer.

In 6.3.1, IMHO, it is unusual to enable a feature by "removing the
deny flag."  It is usually done by setting the enable flag.  This
means that by default, calling getsockopt(SCTP_ENABLE_STREAM_RESET)
returns a 0 assoc_value.  To enable one feature, call setsockopt()
with that feature's flag on.



-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Mon Mar 14 03:11:28 2011
Return-Path: <ka-cheong.poon@oracle.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 286463A6C6F; Mon, 14 Mar 2011 03:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.249
X-Spam-Level: 
X-Spam-Status: No, score=-4.249 tagged_above=-999 required=5 tests=[AWL=1.994,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 jCGhJZf4vEvU; Mon, 14 Mar 2011 03:11:24 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id E71B83A6C08; Mon, 14 Mar 2011 03:11:20 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2EACfVb013786 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 14 Mar 2011 10:12:43 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2EACeg7001989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Mar 2011 10:12:40 GMT
Received: from abhmt019.oracle.com (abhmt019.oracle.com [141.146.116.28]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2EACd4O030562; Mon, 14 Mar 2011 05:12:39 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 14 Mar 2011 03:12:38 -0700
Message-ID: <4D7DEA12.4000907@oracle.com>
Date: Mon, 14 Mar 2011 18:12:34 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DBDB2.7010102@cisco.com>
In-Reply-To: <4D7DBDB2.7010102@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt358.oracle.com [141.146.40.158]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090206.4D7DEA19.0201,ss=1,fgs=0
Cc: Paul Aitken <paitken@cisco.com>, "ipfix@ietf.org" <ipfix@ietf.org>, Gerhard Muenz <muenz@net.in.tum.de>, "James M. Polk" <jmpolk@cisco.com>, Andrew Johnson <andrjohn@cisco.com>, tsvwg <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, 14 Mar 2011 10:11:29 -0000

On 03/14/11 03:03 PM, Benoit Claise wrote:

> I'm not a transport expert so I can't comment on the technical part.
> However, there is a clear interest: the functionality in the draft is
> required. "The IPFIX export per SCTP stream",
> https://datatracker.ietf.org/doc/draft-ietf-ipfix-export-per-sctp-stream/ has
> been sitting for 8 months in the RFC editor queue, waiting for this draft.


I think only the new stream addition part is needed by IPFIX, right?
Is there any IETF protocol which requires the use of SCTP SSN/TSN
reset?


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From Michael.Tuexen@lurchi.franken.de  Mon Mar 14 04:07:11 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 7BE393A6C7A; Mon, 14 Mar 2011 04:07:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 GBnpv8rMV6nq; Mon, 14 Mar 2011 04:07:10 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id B67183A6C7D; Mon, 14 Mar 2011 04:07:09 -0700 (PDT)
Received: from [192.168.1.113] (p5481DBED.dip.t-dialin.net [84.129.219.237]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id C42841C0C0BD8; Mon, 14 Mar 2011 12:08:30 +0100 (CET)
Subject: Re: SCTP Path Max Retransmission Query
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=windows-1252
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <AANLkTimva9OxsLM3bbcBktUvxxMChekqbxPx0-vEim2S@mail.gmail.com>
Date: Mon, 14 Mar 2011 12:08:30 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <98139DBB-B98C-4381-84B4-14966A2F271E@lurchi.franken.de>
References: <AANLkTik1vsK8biL_ohqAVhHXRw99seF34LzSKaAFwi1B@mail.gmail.com> <117BBC30-5365-44AB-8CB9-5E8F3F1AAE47@lurchi.franken.de> <AANLkTimva9OxsLM3bbcBktUvxxMChekqbxPx0-vEim2S@mail.gmail.com>
To: Will Yu <will.v.yu@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: will.yu@ericsson.com, tsvwg@ietf.org, ietf@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, 14 Mar 2011 11:07:11 -0000

On Mar 14, 2011, at 3:36 AM, Will Yu wrote:

> Hello dear Michael,
>=20
> Thank you for your reply. There is an additional query about your =
reply:
> In our realization, the remote address is regarded as unreachable =
until the Heartbeat Message from TWO different local address(IP1 and =
IP2) exceed PMR. It means that IP1 sent 4(PMR value) Heartbeat and IP2 =
sent 4(PMR value) Heartbeat as well. In your describing, is this method =
not accord with RFC?
The RFC only talks about an error counter per remote address, not an =
error counter per local/remote address pair.

However, you should be able to handle a network setup, where no cross =
routing is possible,
so there is only connectivity between IP1 <-> IP3 and IP2 <-> IP4. This =
is a setup which
is often used in SIGTRAN setups.

Best regards
Michael
>=20
> Thanks again.
>=20
> Brs,
> Will Yu
>=20
> 2011/3/12 Michael T=FCxen <Michael.Tuexen@lurchi.franken.de>
>=20
> On Mar 11, 2011, at 7:44 AM, Will Yu wrote:
>=20
> > Hello,
> >
> > I have a query on SCTP standard (RFC 4960). In section 8.2 Path =
Failure Detection, it describes the action which end points should take =
in detecting path unavailable.
> >
> >    When its peer endpoint is multi-homed, an endpoint should keep an
> >    error counter for each of the destination transport addresses of =
the
> >    peer endpoint.
> >    Each time the T3-rtx timer expires on any address, or when a
> >    HEARTBEAT sent to an idle address is not acknowledged within an =
RTO,
> >    the error counter of that destination address will be =
incremented.
> >    When the value in the error counter exceeds the protocol =
parameter
> >    =92Path.Max.Retrans=92 of that destination address, the endpoint =
should
> >    mark the destination transport address as inactive, and a
> >    notification SHOULD be sent to the upper layer.
> >
> > In my case, I connected two end points through four IP address. EP1 =
owns IP1 and IP2, EP2 owns IP3 and IP4. And IP1 is the primary address =
for EP1, while IP3 is the primary address for EP2. There is no other =
packet in this association except with Heartbeat and Heartbeat_ACK.
> >
> >                 IP1--------------------IP3
> >     End                   \ /                   End
> >    Point1                 *                   Point2
> >                              / \
> >                 IP2--------------------IP4
> >
> > When IP4 is unavailable, the heartbeat messages from IP1 and IP2 =
with the destination IP4 cannot received acknowledgement. In this case, =
PMR in each EP is set to 4. I observed that EP1 used IP1 and IP2 as =
source address to send the heartbeat messages to IP4 respectively. When =
the heartbeat message from source address IP2 exceed 4 times, it marked =
the path(IP2-IP4) is unreachable. And then IP1 exceed, it would mark the =
destination IP4 is unavailable. In my opinion, this result is
> There is no state for the path IP2-IP4, only for the remote address =
IP4.
> > reasonable with the recognition of IP2-IP4 is a path and IP1-IP4 is =
another path for the association. Consequently, the PMR parameter is for =
determining which PATH could regard as unavailable.
> SCTP supervises remote addresses. So EP1 is supervising IP3 and IP4. =
So there is one  error counter for IP3
> and one for IP4. There is also only a state per remote IP address. So =
after the error counter for IP4
> exceeds PMR, the IP address IP4 should be marked as unreachable.
> > But in the section 8.2 Path Failure Detection, the increasing =
counter action is based on different destination transport address, not =
on the different source-destination address pair. I think it make me =
confused that counter will impact the result in my case with the =
assumption RFC regard the destination address failure as the critical =
element for Path Failure Detection.
> >
> > Would you kindly help me clarify the behaviors in Path Failure =
Detection, or figure out if I have any misunderstanding in this case?
> As said above, SCTP supervises remote addresses, not paths.
>=20
> Best regards
> Michael
>=20
> PS: It might be better to send SCTP related questions to =
tsvwg@ietf.org
> >
> > Brs,
> > Will Yu
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
>=20
>=20


From Michael.Tuexen@lurchi.franken.de  Mon Mar 14 07:11:24 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 D25F83A6910 for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 07:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.023
X-Spam-Level: *
X-Spam-Status: No, score=1.023 tagged_above=-999 required=5 tests=[AWL=-3.322,  BAYES_00=-2.599, FRT_STOCK2=3.988, MANGLED_TOOL=2.3, MIME_8BIT_HEADER=0.3, 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 swG0hI5y2Nus for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 07:11:23 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id C4B9D3A696A for <tsvwg@ietf.org>; Mon, 14 Mar 2011 07:11:21 -0700 (PDT)
Received: from [192.168.1.113] (p5481DBED.dip.t-dialin.net [84.129.219.237]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id EDD2F1C0C0BD8; Mon, 14 Mar 2011 15:12:42 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4D7DE97D.6010609@oracle.com>
Date: Mon, 14 Mar 2011 15:12:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
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, 14 Mar 2011 14:11:25 -0000

Hi Kacheong,

thank you very much for you comments.
I'll try to address them inline.

Best regards
Michael

On Mar 14, 2011, at 11:10 AM, Kacheong Poon wrote:

> On 03/14/11 04:48 AM, James M. Polk wrote:
>=20
>> We chairs want folks to show or assert they have reviewed this ID and
>> give feedback to the list (and not unicast to the chairs). This ID
>> cannot progress without that feedback.
>=20
>=20
> I have several comments.
>=20
> In the Introduction, the reasons to have a SCTP protocol level
> mechanism (stream sequence number reset) to solve the app issue
> are quite sketchy.  For example, one can envision that an app can
> just remember the stream sequence number before it intends to
> re-use a stream such that it can differentiate new and old messages.
> Or there can be a shim layer below the app and above socket layer
> to do this translation.  Or there can be a socket level option to
> do the translation.  And all these can be combined with the app
> layer protocol.  I think the draft should include more details on
> why a SCTP protocol level mechanism is needed.  An example of real
> use case which cannot be accomplished without a SCTP level mechanism
> should probably be provided.
It is hard to provide such an example since you can implement almost
everything at every layer. The point is, where an appropriate
location is for implementing a particular functionality.

You could, for example, implement all your sequencing in the application
and use only one SCTP stream, sending every message unordered. But
it this the best function split?
>=20
> More importantly, the draft contains a mechanism to reset
> transmission sequence number but there is no rationale given on why
> this is necessary.  TSN should normally be opaque to applications
> and should be used solely by SCTP for protocol handling.  It is
> hard to see why a reset of TSN is needed to make an app work.  I
> think there should be a very strong reason why such an SCTP protocol
> mechanism is needed.  But the draft gives no reason.
The point here is that we are exposing the TSN to the application.

You are right, one can design application protocols running on
top of SCTP, and the receiver side does not pay attention to
SSN, SID or TSN. The sender just chooses the SID to enforce the
appropriate sequencing and everything works.
This is what I told people when they were thinking about
using SCTP. However, I had to learn, that they take the SSN into
account. So resetting them makes sense.
Some application writers want streams to be some dynamic channel
they can reset easily.
TSNs are similar to SSNs, they are exposed to the user. So they
might want the be controlled by the user.
> I suggest that the new chunk be called "Stream Re-configuration"
> since the chunk is also about adding new streams.  But even this
> name does not cover the case of resetting TSN, which is at the
> association level.  Is it correct to include a parameter which
> affects the association level TSN in this chunk?  This also goes
> back to the question about the reasons of having TSN reset.
I agree the naming could be improved.
What about:
* Re-configuration Chunk
* Reset Chunk
Both covers TSN/SSN. Maybe the first name covers better the addition
of streams.
>=20
> The diagram in 3.1 is not correct.  It shows that the parameter
> is only 4 bytes long.
Right. I'll change that to
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type =3D 0x82   |  Chunk Flags  |      Chunk Length             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\                                                               \
/                   Stream Reset Parameter                      /
\                                                               \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\                                                               \
/                    Stream Reset Parameter (optional)          /
\                                                               \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

OK?
>=20
> In 4.1, the use of "Stream Reset Response Sequence Number" is
> confusing.  The draft says
>=20
>    When this Outgoing SSN Reset Request Parameter is sent in response
>    to an Incoming SSN Reset Request Parameter this parameter is also
>    an implicit response to the incoming request.
>=20
> So a request is sent in response to another a request?  A response
> to a request is understandable, and the response is either request
> accepted or not.  But a request is sent responding to a request is
> confusing.  It is like sending an SCTP_ABORT in response to an
> SCTP_ABORT.
The "Incoming SSN Reset Request" requests an "Outgoing SSN Reset =
Request"
to be sent. To simplify things, the sending of the "Outgoing SSN Reset =
Request"
is an implicit acknowledgement.
>=20
> I suppose the rationale, as described in section 5, is that the
> originator of resetting should be the outgoing side.  But this
> raises the question of why then there is an Incoming SSN Reset
> Request.  This just makes the mechanism unnecessarily more
> complicated.  Given that the app layer protocol must first agree
> on the reset operation, it is unclear why there is a need to have
> the Incoming SSN Reset Request.  And if there is really such a
> reason, then why does the same reason not applicable to the SSN/TSN
> resetting and adding more streams?  So should there also be an
> Incoming SSN/TSN Reset Request and Incoming Adding Streams Request?
The SSN/TSN Reset is a reset in both directions.

However, you are right, an Add Incoming Streams Request Parameter
is missing. I think we should add this. It is conceptually missing.
Randy, Peter: What do you think?
>=20
> I suppose there is only the need to have Outgoing SSN Reset Request.
> The app layer protocol should handle which side does the initiation.
> A consequence of not having Incoming request is that then there is
> no need to have an optional second parameter in the chunk.  This
> also eliminates race of Incoming/Outgoing requests cross over.
> Given this simplicity, I think the draft should provide a reason
> that the Incoming request is absolutely necessary.
The reasoning for me is to provide a "complete" solution. I do not
want to provide this part of functionality right now and figure out
in a couple of month that I'm missing another one. I prefer to
extend it once, not multiple times.
>=20
> In first sentence of 4.3, does "all streams" mean "all outgoing
> streams" or "all incoming streams?"
It means "all incoming and all outgoing streams".
I added that as a clarification.
>=20
> If a reset timer is running, no other request can be sent out.  So
> there can only be one outstanding unacknowledged request.  I suggest
> that this is mentioned explicitly in 5.1.1.
OK. Done. I added:
<t>At any given time there MUST NOT be more than one request be
in flight. So if the 'Stream Reset Timer' is running and the
the STREAM RESET chunk contains at least one request parameter
the chunk MUST be buffered.</t>
>=20
> In 6.2, I think it is incorrect to change sctp_event_subscribe
> and use SCTP_EVENTS option because they are deprecated.  It should
> only mention the SCTP_EVENT option.
Well, there are implementations out which support this extension
but not the new way of subscribing to events.

I added text to make clear which method is deprecated.

However, I can also live with just removing the text describing
the deprecated way.
Randy? Peter?
>=20
> In all the new events, there are "denied" and "failed" events.  It
> is not clear what "failed" means.  The peer does not respond to
> a request and the association times out?  I suggest that it should
> be made clearer.
Have a look at table 3. The peer can indicate that there was an
error or that it denied the request.
>=20
> In 6.3.1, IMHO, it is unusual to enable a feature by "removing the
> deny flag."  It is usually done by setting the enable flag.  This
> means that by default, calling getsockopt(SCTP_ENABLE_STREAM_RESET)
> returns a 0 assoc_value.  To enable one feature, call setsockopt()
> with that feature's flag on.
We made deny the default to avoid any problems if an application
can not handle discontinuities in received SSN/TSN and runs now
on a kernel supporting this extension. If an application wants
to use this feature, it must enable it explicitly.
>=20
>=20
>=20
> --=20
>=20
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
>=20


From randall@lakerest.net  Mon Mar 14 09:05:31 2011
Return-Path: <randall@lakerest.net>
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 8FD6A3A6D0D for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 09:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.345
X-Spam-Level: ****
X-Spam-Status: No, score=4.345 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_STOCK2=3.988, MANGLED_TOOL=2.3, MIME_8BIT_HEADER=0.3, 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 eQ3n0o2ZzUoL for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 09:05:30 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 18E263A69DD for <tsvwg@ietf.org>; Mon, 14 Mar 2011 09:05:28 -0700 (PDT)
Received: from [32.177.10.31] ([32.177.10.31]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2EG6fe5082444 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 14 Mar 2011 12:06:46 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de>
Date: Mon, 14 Mar 2011 12:06:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <51679D6F-1789-46BE-B1E5-22AE064B27E2@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de>
To: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.1082)
Cc: Kacheong Poon <ka-cheong.poon@oracle.com>, 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, 14 Mar 2011 16:05:31 -0000

In-line..

On Mar 14, 2011, at 10:12 AM, Michael T=FCxen wrote:

> Hi Kacheong,
>=20
> thank you very much for you comments.
> I'll try to address them inline.
>=20
> Best regards
> Michael
>=20
> On Mar 14, 2011, at 11:10 AM, Kacheong Poon wrote:
>=20
>> On 03/14/11 04:48 AM, James M. Polk wrote:
>>=20
>>> We chairs want folks to show or assert they have reviewed this ID =
and
>>> give feedback to the list (and not unicast to the chairs). This ID
>>> cannot progress without that feedback.
>>=20
>>=20
>> I have several comments.
>>=20
>> In the Introduction, the reasons to have a SCTP protocol level
>> mechanism (stream sequence number reset) to solve the app issue
>> are quite sketchy.  For example, one can envision that an app can
>> just remember the stream sequence number before it intends to
>> re-use a stream such that it can differentiate new and old messages.
>> Or there can be a shim layer below the app and above socket layer
>> to do this translation.  Or there can be a socket level option to
>> do the translation.  And all these can be combined with the app
>> layer protocol.  I think the draft should include more details on
>> why a SCTP protocol level mechanism is needed.  An example of real
>> use case which cannot be accomplished without a SCTP level mechanism
>> should probably be provided.
> It is hard to provide such an example since you can implement almost
> everything at every layer. The point is, where an appropriate
> location is for implementing a particular functionality.
>=20
> You could, for example, implement all your sequencing in the =
application
> and use only one SCTP stream, sending every message unordered. But
> it this the best function split?
>>=20
>> More importantly, the draft contains a mechanism to reset
>> transmission sequence number but there is no rationale given on why
>> this is necessary.  TSN should normally be opaque to applications
>> and should be used solely by SCTP for protocol handling.  It is
>> hard to see why a reset of TSN is needed to make an app work.  I
>> think there should be a very strong reason why such an SCTP protocol
>> mechanism is needed.  But the draft gives no reason.
> The point here is that we are exposing the TSN to the application.
>=20
> You are right, one can design application protocols running on
> top of SCTP, and the receiver side does not pay attention to
> SSN, SID or TSN. The sender just chooses the SID to enforce the
> appropriate sequencing and everything works.
> This is what I told people when they were thinking about
> using SCTP. However, I had to learn, that they take the SSN into
> account. So resetting them makes sense.
> Some application writers want streams to be some dynamic channel
> they can reset easily.
> TSNs are similar to SSNs, they are exposed to the user. So they
> might want the be controlled by the user.
>> I suggest that the new chunk be called "Stream Re-configuration"
>> since the chunk is also about adding new streams.  But even this
>> name does not cover the case of resetting TSN, which is at the
>> association level.  Is it correct to include a parameter which
>> affects the association level TSN in this chunk?  This also goes
>> back to the question about the reasons of having TSN reset.
> I agree the naming could be improved.
> What about:
> * Re-configuration Chunk
> * Reset Chunk
> Both covers TSN/SSN. Maybe the first name covers better the addition
> of streams.
>>=20
>> The diagram in 3.1 is not correct.  It shows that the parameter
>> is only 4 bytes long.
> Right. I'll change that to
> 0                   1                   2                   3
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | Type =3D 0x82   |  Chunk Flags  |      Chunk Length             |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> \                                                               \
> /                   Stream Reset Parameter                      /
> \                                                               \
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> \                                                               \
> /                    Stream Reset Parameter (optional)          /
> \                                                               \
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>=20
> OK?
>>=20
>> In 4.1, the use of "Stream Reset Response Sequence Number" is
>> confusing.  The draft says
>>=20
>>   When this Outgoing SSN Reset Request Parameter is sent in response
>>   to an Incoming SSN Reset Request Parameter this parameter is also
>>   an implicit response to the incoming request.
>>=20
>> So a request is sent in response to another a request?  A response
>> to a request is understandable, and the response is either request
>> accepted or not.  But a request is sent responding to a request is
>> confusing.  It is like sending an SCTP_ABORT in response to an
>> SCTP_ABORT.
> The "Incoming SSN Reset Request" requests an "Outgoing SSN Reset =
Request"
> to be sent. To simplify things, the sending of the "Outgoing SSN Reset =
Request"
> is an implicit acknowledgement.
>>=20
>> I suppose the rationale, as described in section 5, is that the
>> originator of resetting should be the outgoing side.  But this
>> raises the question of why then there is an Incoming SSN Reset
>> Request.  This just makes the mechanism unnecessarily more
>> complicated.  Given that the app layer protocol must first agree
>> on the reset operation, it is unclear why there is a need to have
>> the Incoming SSN Reset Request.  And if there is really such a
>> reason, then why does the same reason not applicable to the SSN/TSN
>> resetting and adding more streams?  So should there also be an
>> Incoming SSN/TSN Reset Request and Incoming Adding Streams Request?
> The SSN/TSN Reset is a reset in both directions.
>=20
> However, you are right, an Add Incoming Streams Request Parameter
> is missing. I think we should add this. It is conceptually missing.
> Randy, Peter: What do you think?


I am fine with adding that... ;-)

>>=20
>> I suppose there is only the need to have Outgoing SSN Reset Request.
>> The app layer protocol should handle which side does the initiation.
>> A consequence of not having Incoming request is that then there is
>> no need to have an optional second parameter in the chunk.  This
>> also eliminates race of Incoming/Outgoing requests cross over.
>> Given this simplicity, I think the draft should provide a reason
>> that the Incoming request is absolutely necessary.
> The reasoning for me is to provide a "complete" solution. I do not
> want to provide this part of functionality right now and figure out
> in a couple of month that I'm missing another one. I prefer to
> extend it once, not multiple times.
>>=20
>> In first sentence of 4.3, does "all streams" mean "all outgoing
>> streams" or "all incoming streams?"
> It means "all incoming and all outgoing streams".
> I added that as a clarification.
>>=20
>> If a reset timer is running, no other request can be sent out.  So
>> there can only be one outstanding unacknowledged request.  I suggest
>> that this is mentioned explicitly in 5.1.1.
> OK. Done. I added:
> <t>At any given time there MUST NOT be more than one request be
> in flight. So if the 'Stream Reset Timer' is running and the
> the STREAM RESET chunk contains at least one request parameter
> the chunk MUST be buffered.</t>
>>=20
>> In 6.2, I think it is incorrect to change sctp_event_subscribe
>> and use SCTP_EVENTS option because they are deprecated.  It should
>> only mention the SCTP_EVENT option.
> Well, there are implementations out which support this extension
> but not the new way of subscribing to events.
>=20
> I added text to make clear which method is deprecated.
>=20
> However, I can also live with just removing the text describing
> the deprecated way.
> Randy? Peter?


I don't mind either way.. we can just strike the text... we could
even add the new functionality that is in the LC socket-api... That
would probably be better..


R
>>=20
>> In all the new events, there are "denied" and "failed" events.  It
>> is not clear what "failed" means.  The peer does not respond to
>> a request and the association times out?  I suggest that it should
>> be made clearer.
> Have a look at table 3. The peer can indicate that there was an
> error or that it denied the request.
>>=20
>> In 6.3.1, IMHO, it is unusual to enable a feature by "removing the
>> deny flag."  It is usually done by setting the enable flag.  This
>> means that by default, calling getsockopt(SCTP_ENABLE_STREAM_RESET)
>> returns a 0 assoc_value.  To enable one feature, call setsockopt()
>> with that feature's flag on.
> We made deny the default to avoid any problems if an application
> can not handle discontinuities in received SSN/TSN and runs now
> on a kernel supporting this extension. If an application wants
> to use this feature, it must enable it explicitly.

>>=20
>>=20
>>=20
>> --=20
>>=20
>> 					K. Poon.
>> 					ka-cheong.poon@oracle.com
>>=20
>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From Michael.Tuexen@lurchi.franken.de  Mon Mar 14 12:26:51 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 301FB3A6E93 for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 12:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.862
X-Spam-Level: *
X-Spam-Status: No, score=1.862 tagged_above=-999 required=5 tests=[AWL=-2.833,  BAYES_00=-2.599, FRT_STOCK2=3.988, HELO_EQ_DE=0.35, MANGLED_TOOL=2.3,  MIME_8BIT_HEADER=0.3, 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 o3nL+cRtzD3x for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 12:26:50 -0700 (PDT)
Received: from mail-n.franken.de (mail-n.franken.de [193.175.24.27]) by core3.amsl.com (Postfix) with ESMTP id 736063A6E9C for <tsvwg@ietf.org>; Mon, 14 Mar 2011 12:26:49 -0700 (PDT)
Received: from [192.168.1.113] (p5481DBED.dip.t-dialin.net [84.129.219.237]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id B94D61C0B461C; Mon, 14 Mar 2011 20:27:41 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <51679D6F-1789-46BE-B1E5-22AE064B27E2@lakerest.net>
Date: Mon, 14 Mar 2011 20:27:41 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B899D4B-6CF7-4A2C-8C12-748A73576579@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <51679D6F-1789-46BE-B1E5-22AE064B27E2@lakerest.net>
To: Randy Stewart <randall@lakerest.net>
X-Mailer: Apple Mail (2.1082)
Cc: Kacheong Poon <ka-cheong.poon@oracle.com>, 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, 14 Mar 2011 19:26:51 -0000

On Mar 14, 2011, at 5:06 PM, Randy Stewart wrote:

> In-line..
>=20
> On Mar 14, 2011, at 10:12 AM, Michael T=FCxen wrote:
>=20
>> Hi Kacheong,
>>=20
>> thank you very much for you comments.
>> I'll try to address them inline.
>>=20
>> Best regards
>> Michael
>>=20
>> On Mar 14, 2011, at 11:10 AM, Kacheong Poon wrote:
>>=20
>>> On 03/14/11 04:48 AM, James M. Polk wrote:
>>>=20
>>>> We chairs want folks to show or assert they have reviewed this ID =
and
>>>> give feedback to the list (and not unicast to the chairs). This ID
>>>> cannot progress without that feedback.
>>>=20
>>>=20
>>> I have several comments.
>>>=20
>>> In the Introduction, the reasons to have a SCTP protocol level
>>> mechanism (stream sequence number reset) to solve the app issue
>>> are quite sketchy.  For example, one can envision that an app can
>>> just remember the stream sequence number before it intends to
>>> re-use a stream such that it can differentiate new and old messages.
>>> Or there can be a shim layer below the app and above socket layer
>>> to do this translation.  Or there can be a socket level option to
>>> do the translation.  And all these can be combined with the app
>>> layer protocol.  I think the draft should include more details on
>>> why a SCTP protocol level mechanism is needed.  An example of real
>>> use case which cannot be accomplished without a SCTP level mechanism
>>> should probably be provided.
>> It is hard to provide such an example since you can implement almost
>> everything at every layer. The point is, where an appropriate
>> location is for implementing a particular functionality.
>>=20
>> You could, for example, implement all your sequencing in the =
application
>> and use only one SCTP stream, sending every message unordered. But
>> it this the best function split?
>>>=20
>>> More importantly, the draft contains a mechanism to reset
>>> transmission sequence number but there is no rationale given on why
>>> this is necessary.  TSN should normally be opaque to applications
>>> and should be used solely by SCTP for protocol handling.  It is
>>> hard to see why a reset of TSN is needed to make an app work.  I
>>> think there should be a very strong reason why such an SCTP protocol
>>> mechanism is needed.  But the draft gives no reason.
>> The point here is that we are exposing the TSN to the application.
>>=20
>> You are right, one can design application protocols running on
>> top of SCTP, and the receiver side does not pay attention to
>> SSN, SID or TSN. The sender just chooses the SID to enforce the
>> appropriate sequencing and everything works.
>> This is what I told people when they were thinking about
>> using SCTP. However, I had to learn, that they take the SSN into
>> account. So resetting them makes sense.
>> Some application writers want streams to be some dynamic channel
>> they can reset easily.
>> TSNs are similar to SSNs, they are exposed to the user. So they
>> might want the be controlled by the user.
>>> I suggest that the new chunk be called "Stream Re-configuration"
>>> since the chunk is also about adding new streams.  But even this
>>> name does not cover the case of resetting TSN, which is at the
>>> association level.  Is it correct to include a parameter which
>>> affects the association level TSN in this chunk?  This also goes
>>> back to the question about the reasons of having TSN reset.
>> I agree the naming could be improved.
>> What about:
>> * Re-configuration Chunk
>> * Reset Chunk
>> Both covers TSN/SSN. Maybe the first name covers better the addition
>> of streams.
>>>=20
>>> The diagram in 3.1 is not correct.  It shows that the parameter
>>> is only 4 bytes long.
>> Right. I'll change that to
>> 0                   1                   2                   3
>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> | Type =3D 0x82   |  Chunk Flags  |      Chunk Length             |
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> \                                                               \
>> /                   Stream Reset Parameter                      /
>> \                                                               \
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> \                                                               \
>> /                    Stream Reset Parameter (optional)          /
>> \                                                               \
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>=20
>> OK?
>>>=20
>>> In 4.1, the use of "Stream Reset Response Sequence Number" is
>>> confusing.  The draft says
>>>=20
>>>  When this Outgoing SSN Reset Request Parameter is sent in response
>>>  to an Incoming SSN Reset Request Parameter this parameter is also
>>>  an implicit response to the incoming request.
>>>=20
>>> So a request is sent in response to another a request?  A response
>>> to a request is understandable, and the response is either request
>>> accepted or not.  But a request is sent responding to a request is
>>> confusing.  It is like sending an SCTP_ABORT in response to an
>>> SCTP_ABORT.
>> The "Incoming SSN Reset Request" requests an "Outgoing SSN Reset =
Request"
>> to be sent. To simplify things, the sending of the "Outgoing SSN =
Reset Request"
>> is an implicit acknowledgement.
>>>=20
>>> I suppose the rationale, as described in section 5, is that the
>>> originator of resetting should be the outgoing side.  But this
>>> raises the question of why then there is an Incoming SSN Reset
>>> Request.  This just makes the mechanism unnecessarily more
>>> complicated.  Given that the app layer protocol must first agree
>>> on the reset operation, it is unclear why there is a need to have
>>> the Incoming SSN Reset Request.  And if there is really such a
>>> reason, then why does the same reason not applicable to the SSN/TSN
>>> resetting and adding more streams?  So should there also be an
>>> Incoming SSN/TSN Reset Request and Incoming Adding Streams Request?
>> The SSN/TSN Reset is a reset in both directions.
>>=20
>> However, you are right, an Add Incoming Streams Request Parameter
>> is missing. I think we should add this. It is conceptually missing.
>> Randy, Peter: What do you think?
>=20
>=20
> I am fine with adding that... ;-)
>=20
>>>=20
>>> I suppose there is only the need to have Outgoing SSN Reset Request.
>>> The app layer protocol should handle which side does the initiation.
>>> A consequence of not having Incoming request is that then there is
>>> no need to have an optional second parameter in the chunk.  This
>>> also eliminates race of Incoming/Outgoing requests cross over.
>>> Given this simplicity, I think the draft should provide a reason
>>> that the Incoming request is absolutely necessary.
>> The reasoning for me is to provide a "complete" solution. I do not
>> want to provide this part of functionality right now and figure out
>> in a couple of month that I'm missing another one. I prefer to
>> extend it once, not multiple times.
>>>=20
>>> In first sentence of 4.3, does "all streams" mean "all outgoing
>>> streams" or "all incoming streams?"
>> It means "all incoming and all outgoing streams".
>> I added that as a clarification.
>>>=20
>>> If a reset timer is running, no other request can be sent out.  So
>>> there can only be one outstanding unacknowledged request.  I suggest
>>> that this is mentioned explicitly in 5.1.1.
>> OK. Done. I added:
>> <t>At any given time there MUST NOT be more than one request be
>> in flight. So if the 'Stream Reset Timer' is running and the
>> the STREAM RESET chunk contains at least one request parameter
>> the chunk MUST be buffered.</t>
>>>=20
>>> In 6.2, I think it is incorrect to change sctp_event_subscribe
>>> and use SCTP_EVENTS option because they are deprecated.  It should
>>> only mention the SCTP_EVENT option.
>> Well, there are implementations out which support this extension
>> but not the new way of subscribing to events.
>>=20
>> I added text to make clear which method is deprecated.
>>=20
>> However, I can also live with just removing the text describing
>> the deprecated way.
>> Randy? Peter?
>=20
>=20
> I don't mind either way.. we can just strike the text... we could
> even add the new functionality that is in the LC socket-api... That
> would probably be better..
Hmm. I prefer keeping the socket API ID as it is, because:
* it passed the WG LC.
* protocol extensions might need to extend the socket API anyway.

So, I would prefer to strike the text referring to the deprecated API.

Best regards
Michael
>=20
>=20
> R
>>>=20
>>> In all the new events, there are "denied" and "failed" events.  It
>>> is not clear what "failed" means.  The peer does not respond to
>>> a request and the association times out?  I suggest that it should
>>> be made clearer.
>> Have a look at table 3. The peer can indicate that there was an
>> error or that it denied the request.
>>>=20
>>> In 6.3.1, IMHO, it is unusual to enable a feature by "removing the
>>> deny flag."  It is usually done by setting the enable flag.  This
>>> means that by default, calling getsockopt(SCTP_ENABLE_STREAM_RESET)
>>> returns a 0 assoc_value.  To enable one feature, call setsockopt()
>>> with that feature's flag on.
>> We made deny the default to avoid any problems if an application
>> can not handle discontinuities in received SSN/TSN and runs now
>> on a kernel supporting this extension. If an application wants
>> to use this feature, it must enable it explicitly.
>=20
>>>=20
>>>=20
>>>=20
>>> --=20
>>>=20
>>> 					K. Poon.
>>> 					ka-cheong.poon@oracle.com
>>>=20
>>=20
>>=20
>=20
> -----
> Randall Stewart
> randall@lakerest.net
>=20
>=20
>=20
>=20
>=20


From Internet-Drafts@ietf.org  Mon Mar 14 12:45:03 2011
Return-Path: <Internet-Drafts@ietf.org>
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 34BB73A6AA9; Mon, 14 Mar 2011 12:45:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 yPSEyZ6Eb9f5; Mon, 14 Mar 2011 12:45:02 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2AD23A6B65; Mon, 14 Mar 2011 12:45:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-tsvwg-byte-pkt-congest-04.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110314194501.5173.60369.idtracker@localhost>
Date: Mon, 14 Mar 2011 12:45:01 -0700
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, 14 Mar 2011 19:45:03 -0000

--NextPart

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           : Byte and Packet Congestion Notification
	Author(s)       : B. Briscoe, J. Manner
	Filename        : draft-ietf-tsvwg-byte-pkt-congest-04.txt
	Pages           : 42
	Date            : 2011-03-14

This memo concerns dropping or marking packets using active queue
management (AQM) such as random early detection (RED) or pre-
congestion notification (PCN).  We give three strong recommendations:
(1) packet size should be taken into account when transports read
congestion indications, (2) packet size should not be taken into
account when network equipment creates congestion signals (marking,
dropping), and therefore (3) the byte-mode packet drop variant of the
RED AQM algorithm that drops fewer small packets should not be used.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-byte-pkt-congest-04.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.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-tsvwg-byte-pkt-congest-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-14123441.I-D@ietf.org>


--NextPart--

From randall@lakerest.net  Mon Mar 14 13:42:59 2011
Return-Path: <randall@lakerest.net>
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 85E983A6B57 for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 13:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.345
X-Spam-Level: ****
X-Spam-Status: No, score=4.345 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_STOCK2=3.988, MANGLED_TOOL=2.3, MIME_8BIT_HEADER=0.3, 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 AGEEK2tovJuz for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 13:42:58 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 301B73A69C9 for <tsvwg@ietf.org>; Mon, 14 Mar 2011 13:42:56 -0700 (PDT)
Received: from [32.177.10.31] ([32.177.10.31]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2EKiAXP093048 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 14 Mar 2011 16:44:16 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <9B899D4B-6CF7-4A2C-8C12-748A73576579@lurchi.franken.de>
Date: Mon, 14 Mar 2011 16:44:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <41206F6C-9221-4BB6-9E2F-EBB8C9CB6913@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <51679D6F-1789-46BE-B1E5-22AE064B27E2@lakerest.net> <9B899D4B-6CF7-4A2C-8C12-748A73576579@lurchi.franken.de>
To: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.1082)
Cc: Kacheong Poon <ka-cheong.poon@oracle.com>, 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, 14 Mar 2011 20:42:59 -0000

On Mar 14, 2011, at 3:27 PM, Michael T=FCxen wrote:

> On Mar 14, 2011, at 5:06 PM, Randy Stewart wrote:
>=20
>> In-line..
>>=20
>> On Mar 14, 2011, at 10:12 AM, Michael T=FCxen wrote:
>>=20
>>> Hi Kacheong,
>>>=20
>>> thank you very much for you comments.
>>> I'll try to address them inline.
>>>=20
>>> Best regards
>>> Michael
>>>=20
>>> On Mar 14, 2011, at 11:10 AM, Kacheong Poon wrote:
>>>=20
>>>> On 03/14/11 04:48 AM, James M. Polk wrote:
>>>>=20
>>>>> We chairs want folks to show or assert they have reviewed this ID =
and
>>>>> give feedback to the list (and not unicast to the chairs). This ID
>>>>> cannot progress without that feedback.
>>>>=20
>>>>=20
>>>> I have several comments.
>>>>=20
>>>> In the Introduction, the reasons to have a SCTP protocol level
>>>> mechanism (stream sequence number reset) to solve the app issue
>>>> are quite sketchy.  For example, one can envision that an app can
>>>> just remember the stream sequence number before it intends to
>>>> re-use a stream such that it can differentiate new and old =
messages.
>>>> Or there can be a shim layer below the app and above socket layer
>>>> to do this translation.  Or there can be a socket level option to
>>>> do the translation.  And all these can be combined with the app
>>>> layer protocol.  I think the draft should include more details on
>>>> why a SCTP protocol level mechanism is needed.  An example of real
>>>> use case which cannot be accomplished without a SCTP level =
mechanism
>>>> should probably be provided.
>>> It is hard to provide such an example since you can implement almost
>>> everything at every layer. The point is, where an appropriate
>>> location is for implementing a particular functionality.
>>>=20
>>> You could, for example, implement all your sequencing in the =
application
>>> and use only one SCTP stream, sending every message unordered. But
>>> it this the best function split?
>>>>=20
>>>> More importantly, the draft contains a mechanism to reset
>>>> transmission sequence number but there is no rationale given on why
>>>> this is necessary.  TSN should normally be opaque to applications
>>>> and should be used solely by SCTP for protocol handling.  It is
>>>> hard to see why a reset of TSN is needed to make an app work.  I
>>>> think there should be a very strong reason why such an SCTP =
protocol
>>>> mechanism is needed.  But the draft gives no reason.
>>> The point here is that we are exposing the TSN to the application.
>>>=20
>>> You are right, one can design application protocols running on
>>> top of SCTP, and the receiver side does not pay attention to
>>> SSN, SID or TSN. The sender just chooses the SID to enforce the
>>> appropriate sequencing and everything works.
>>> This is what I told people when they were thinking about
>>> using SCTP. However, I had to learn, that they take the SSN into
>>> account. So resetting them makes sense.
>>> Some application writers want streams to be some dynamic channel
>>> they can reset easily.
>>> TSNs are similar to SSNs, they are exposed to the user. So they
>>> might want the be controlled by the user.
>>>> I suggest that the new chunk be called "Stream Re-configuration"
>>>> since the chunk is also about adding new streams.  But even this
>>>> name does not cover the case of resetting TSN, which is at the
>>>> association level.  Is it correct to include a parameter which
>>>> affects the association level TSN in this chunk?  This also goes
>>>> back to the question about the reasons of having TSN reset.
>>> I agree the naming could be improved.
>>> What about:
>>> * Re-configuration Chunk
>>> * Reset Chunk
>>> Both covers TSN/SSN. Maybe the first name covers better the addition
>>> of streams.
>>>>=20
>>>> The diagram in 3.1 is not correct.  It shows that the parameter
>>>> is only 4 bytes long.
>>> Right. I'll change that to
>>> 0                   1                   2                   3
>>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>> | Type =3D 0x82   |  Chunk Flags  |      Chunk Length             |
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>> \                                                               \
>>> /                   Stream Reset Parameter                      /
>>> \                                                               \
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>> \                                                               \
>>> /                    Stream Reset Parameter (optional)          /
>>> \                                                               \
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>=20
>>> OK?
>>>>=20
>>>> In 4.1, the use of "Stream Reset Response Sequence Number" is
>>>> confusing.  The draft says
>>>>=20
>>>> When this Outgoing SSN Reset Request Parameter is sent in response
>>>> to an Incoming SSN Reset Request Parameter this parameter is also
>>>> an implicit response to the incoming request.
>>>>=20
>>>> So a request is sent in response to another a request?  A response
>>>> to a request is understandable, and the response is either request
>>>> accepted or not.  But a request is sent responding to a request is
>>>> confusing.  It is like sending an SCTP_ABORT in response to an
>>>> SCTP_ABORT.
>>> The "Incoming SSN Reset Request" requests an "Outgoing SSN Reset =
Request"
>>> to be sent. To simplify things, the sending of the "Outgoing SSN =
Reset Request"
>>> is an implicit acknowledgement.
>>>>=20
>>>> I suppose the rationale, as described in section 5, is that the
>>>> originator of resetting should be the outgoing side.  But this
>>>> raises the question of why then there is an Incoming SSN Reset
>>>> Request.  This just makes the mechanism unnecessarily more
>>>> complicated.  Given that the app layer protocol must first agree
>>>> on the reset operation, it is unclear why there is a need to have
>>>> the Incoming SSN Reset Request.  And if there is really such a
>>>> reason, then why does the same reason not applicable to the SSN/TSN
>>>> resetting and adding more streams?  So should there also be an
>>>> Incoming SSN/TSN Reset Request and Incoming Adding Streams Request?
>>> The SSN/TSN Reset is a reset in both directions.
>>>=20
>>> However, you are right, an Add Incoming Streams Request Parameter
>>> is missing. I think we should add this. It is conceptually missing.
>>> Randy, Peter: What do you think?
>>=20
>>=20
>> I am fine with adding that... ;-)
>>=20
>>>>=20
>>>> I suppose there is only the need to have Outgoing SSN Reset =
Request.
>>>> The app layer protocol should handle which side does the =
initiation.
>>>> A consequence of not having Incoming request is that then there is
>>>> no need to have an optional second parameter in the chunk.  This
>>>> also eliminates race of Incoming/Outgoing requests cross over.
>>>> Given this simplicity, I think the draft should provide a reason
>>>> that the Incoming request is absolutely necessary.
>>> The reasoning for me is to provide a "complete" solution. I do not
>>> want to provide this part of functionality right now and figure out
>>> in a couple of month that I'm missing another one. I prefer to
>>> extend it once, not multiple times.
>>>>=20
>>>> In first sentence of 4.3, does "all streams" mean "all outgoing
>>>> streams" or "all incoming streams?"
>>> It means "all incoming and all outgoing streams".
>>> I added that as a clarification.
>>>>=20
>>>> If a reset timer is running, no other request can be sent out.  So
>>>> there can only be one outstanding unacknowledged request.  I =
suggest
>>>> that this is mentioned explicitly in 5.1.1.
>>> OK. Done. I added:
>>> <t>At any given time there MUST NOT be more than one request be
>>> in flight. So if the 'Stream Reset Timer' is running and the
>>> the STREAM RESET chunk contains at least one request parameter
>>> the chunk MUST be buffered.</t>
>>>>=20
>>>> In 6.2, I think it is incorrect to change sctp_event_subscribe
>>>> and use SCTP_EVENTS option because they are deprecated.  It should
>>>> only mention the SCTP_EVENT option.
>>> Well, there are implementations out which support this extension
>>> but not the new way of subscribing to events.
>>>=20
>>> I added text to make clear which method is deprecated.
>>>=20
>>> However, I can also live with just removing the text describing
>>> the deprecated way.
>>> Randy? Peter?
>>=20
>>=20
>> I don't mind either way.. we can just strike the text... we could
>> even add the new functionality that is in the LC socket-api... That
>> would probably be better..
> Hmm. I prefer keeping the socket API ID as it is, because:
> * it passed the WG LC.
> * protocol extensions might need to extend the socket API anyway.
>=20
> So, I would prefer to strike the text referring to the deprecated API.

Fine by me.. I did not mean change the socket api.. but to add
the new methods from the socket api into the stream reset draft..

But I can live with either

R

>=20
> Best regards
> Michael
>>=20
>>=20
>> R
>>>>=20
>>>> In all the new events, there are "denied" and "failed" events.  It
>>>> is not clear what "failed" means.  The peer does not respond to
>>>> a request and the association times out?  I suggest that it should
>>>> be made clearer.
>>> Have a look at table 3. The peer can indicate that there was an
>>> error or that it denied the request.
>>>>=20
>>>> In 6.3.1, IMHO, it is unusual to enable a feature by "removing the
>>>> deny flag."  It is usually done by setting the enable flag.  This
>>>> means that by default, calling getsockopt(SCTP_ENABLE_STREAM_RESET)
>>>> returns a 0 assoc_value.  To enable one feature, call setsockopt()
>>>> with that feature's flag on.
>>> We made deny the default to avoid any problems if an application
>>> can not handle discontinuities in received SSN/TSN and runs now
>>> on a kernel supporting this extension. If an application wants
>>> to use this feature, it must enable it explicitly.
>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> --=20
>>>>=20
>>>> 					K. Poon.
>>>> 					ka-cheong.poon@oracle.com
>>>>=20
>>>=20
>>>=20
>>=20
>> -----
>> Randall Stewart
>> randall@lakerest.net
>>=20
>>=20
>>=20
>>=20
>>=20
>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From Michael.Tuexen@lurchi.franken.de  Mon Mar 14 13:59:11 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 4C1403A6B57 for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 13:59:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.847
X-Spam-Level: 
X-Spam-Status: No, score=0.847 tagged_above=-999 required=5 tests=[AWL=-1.198,  BAYES_00=-2.599, FRT_STOCK2=3.988, MIME_8BIT_HEADER=0.3, 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 m0TjnyntoL2s for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 13:59:10 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id 231593A69C9 for <tsvwg@ietf.org>; Mon, 14 Mar 2011 13:59:08 -0700 (PDT)
Received: from [192.168.1.113] (p5481DBED.dip.t-dialin.net [84.129.219.237]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 3F51F1C0B4619; Mon, 14 Mar 2011 22:00:30 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <41206F6C-9221-4BB6-9E2F-EBB8C9CB6913@lakerest.net>
Date: Mon, 14 Mar 2011 22:00:29 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E945C0E8-53B8-4EF0-8D04-DBA70E5BF4C1@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <51679D6F-1789-46BE-B1E5-22AE064B27E2@lakerest.net> <9B899D4B-6CF7-4A2C-8C12-748A73576579@lurchi.franken.de> <41206F6C-9221-4BB6-9E2F-EBB8C9CB6913@lakerest.net>
To: Randy Stewart <randall@lakerest.net>
X-Mailer: Apple Mail (2.1082)
Cc: Kacheong Poon <ka-cheong.poon@oracle.com>, 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, 14 Mar 2011 20:59:11 -0000

On Mar 14, 2011, at 9:44 PM, Randy Stewart wrote:
>=20
> On Mar 14, 2011, at 3:27 PM, Michael T=FCxen wrote:
>=20
>> On Mar 14, 2011, at 5:06 PM, Randy Stewart wrote:
>>=20
>>> In-line..
>>>=20
>>> On Mar 14, 2011, at 10:12 AM, Michael T=FCxen wrote:
>>>=20
>>>> Hi Kacheong,
>>>>=20
>>>> thank you very much for you comments.
>>>> I'll try to address them inline.
>>>>=20
>>>> Best regards
>>>> Michael
>>>>=20
>>>> On Mar 14, 2011, at 11:10 AM, Kacheong Poon wrote:
>>>>=20
>>>>> On 03/14/11 04:48 AM, James M. Polk wrote:
>>>>>=20
>>>>>> We chairs want folks to show or assert they have reviewed this ID =
and
>>>>>> give feedback to the list (and not unicast to the chairs). This =
ID
>>>>>> cannot progress without that feedback.
>>>>>=20
>>>>>=20
>>>>> I have several comments.
>>>>>=20
>>>>> In the Introduction, the reasons to have a SCTP protocol level
>>>>> mechanism (stream sequence number reset) to solve the app issue
>>>>> are quite sketchy.  For example, one can envision that an app can
>>>>> just remember the stream sequence number before it intends to
>>>>> re-use a stream such that it can differentiate new and old =
messages.
>>>>> Or there can be a shim layer below the app and above socket layer
>>>>> to do this translation.  Or there can be a socket level option to
>>>>> do the translation.  And all these can be combined with the app
>>>>> layer protocol.  I think the draft should include more details on
>>>>> why a SCTP protocol level mechanism is needed.  An example of real
>>>>> use case which cannot be accomplished without a SCTP level =
mechanism
>>>>> should probably be provided.
>>>> It is hard to provide such an example since you can implement =
almost
>>>> everything at every layer. The point is, where an appropriate
>>>> location is for implementing a particular functionality.
>>>>=20
>>>> You could, for example, implement all your sequencing in the =
application
>>>> and use only one SCTP stream, sending every message unordered. But
>>>> it this the best function split?
>>>>>=20
>>>>> More importantly, the draft contains a mechanism to reset
>>>>> transmission sequence number but there is no rationale given on =
why
>>>>> this is necessary.  TSN should normally be opaque to applications
>>>>> and should be used solely by SCTP for protocol handling.  It is
>>>>> hard to see why a reset of TSN is needed to make an app work.  I
>>>>> think there should be a very strong reason why such an SCTP =
protocol
>>>>> mechanism is needed.  But the draft gives no reason.
>>>> The point here is that we are exposing the TSN to the application.
>>>>=20
>>>> You are right, one can design application protocols running on
>>>> top of SCTP, and the receiver side does not pay attention to
>>>> SSN, SID or TSN. The sender just chooses the SID to enforce the
>>>> appropriate sequencing and everything works.
>>>> This is what I told people when they were thinking about
>>>> using SCTP. However, I had to learn, that they take the SSN into
>>>> account. So resetting them makes sense.
>>>> Some application writers want streams to be some dynamic channel
>>>> they can reset easily.
>>>> TSNs are similar to SSNs, they are exposed to the user. So they
>>>> might want the be controlled by the user.
>>>>> I suggest that the new chunk be called "Stream Re-configuration"
>>>>> since the chunk is also about adding new streams.  But even this
>>>>> name does not cover the case of resetting TSN, which is at the
>>>>> association level.  Is it correct to include a parameter which
>>>>> affects the association level TSN in this chunk?  This also goes
>>>>> back to the question about the reasons of having TSN reset.
>>>> I agree the naming could be improved.
>>>> What about:
>>>> * Re-configuration Chunk
>>>> * Reset Chunk
>>>> Both covers TSN/SSN. Maybe the first name covers better the =
addition
>>>> of streams.
>>>>>=20
>>>>> The diagram in 3.1 is not correct.  It shows that the parameter
>>>>> is only 4 bytes long.
>>>> Right. I'll change that to
>>>> 0                   1                   2                   3
>>>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> | Type =3D 0x82   |  Chunk Flags  |      Chunk Length             |
>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> \                                                               \
>>>> /                   Stream Reset Parameter                      /
>>>> \                                                               \
>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> \                                                               \
>>>> /                    Stream Reset Parameter (optional)          /
>>>> \                                                               \
>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>=20
>>>> OK?
>>>>>=20
>>>>> In 4.1, the use of "Stream Reset Response Sequence Number" is
>>>>> confusing.  The draft says
>>>>>=20
>>>>> When this Outgoing SSN Reset Request Parameter is sent in response
>>>>> to an Incoming SSN Reset Request Parameter this parameter is also
>>>>> an implicit response to the incoming request.
>>>>>=20
>>>>> So a request is sent in response to another a request?  A response
>>>>> to a request is understandable, and the response is either request
>>>>> accepted or not.  But a request is sent responding to a request is
>>>>> confusing.  It is like sending an SCTP_ABORT in response to an
>>>>> SCTP_ABORT.
>>>> The "Incoming SSN Reset Request" requests an "Outgoing SSN Reset =
Request"
>>>> to be sent. To simplify things, the sending of the "Outgoing SSN =
Reset Request"
>>>> is an implicit acknowledgement.
>>>>>=20
>>>>> I suppose the rationale, as described in section 5, is that the
>>>>> originator of resetting should be the outgoing side.  But this
>>>>> raises the question of why then there is an Incoming SSN Reset
>>>>> Request.  This just makes the mechanism unnecessarily more
>>>>> complicated.  Given that the app layer protocol must first agree
>>>>> on the reset operation, it is unclear why there is a need to have
>>>>> the Incoming SSN Reset Request.  And if there is really such a
>>>>> reason, then why does the same reason not applicable to the =
SSN/TSN
>>>>> resetting and adding more streams?  So should there also be an
>>>>> Incoming SSN/TSN Reset Request and Incoming Adding Streams =
Request?
>>>> The SSN/TSN Reset is a reset in both directions.
>>>>=20
>>>> However, you are right, an Add Incoming Streams Request Parameter
>>>> is missing. I think we should add this. It is conceptually missing.
>>>> Randy, Peter: What do you think?
>>>=20
>>>=20
>>> I am fine with adding that... ;-)
>>>=20
>>>>>=20
>>>>> I suppose there is only the need to have Outgoing SSN Reset =
Request.
>>>>> The app layer protocol should handle which side does the =
initiation.
>>>>> A consequence of not having Incoming request is that then there is
>>>>> no need to have an optional second parameter in the chunk.  This
>>>>> also eliminates race of Incoming/Outgoing requests cross over.
>>>>> Given this simplicity, I think the draft should provide a reason
>>>>> that the Incoming request is absolutely necessary.
>>>> The reasoning for me is to provide a "complete" solution. I do not
>>>> want to provide this part of functionality right now and figure out
>>>> in a couple of month that I'm missing another one. I prefer to
>>>> extend it once, not multiple times.
>>>>>=20
>>>>> In first sentence of 4.3, does "all streams" mean "all outgoing
>>>>> streams" or "all incoming streams?"
>>>> It means "all incoming and all outgoing streams".
>>>> I added that as a clarification.
>>>>>=20
>>>>> If a reset timer is running, no other request can be sent out.  So
>>>>> there can only be one outstanding unacknowledged request.  I =
suggest
>>>>> that this is mentioned explicitly in 5.1.1.
>>>> OK. Done. I added:
>>>> <t>At any given time there MUST NOT be more than one request be
>>>> in flight. So if the 'Stream Reset Timer' is running and the
>>>> the STREAM RESET chunk contains at least one request parameter
>>>> the chunk MUST be buffered.</t>
>>>>>=20
>>>>> In 6.2, I think it is incorrect to change sctp_event_subscribe
>>>>> and use SCTP_EVENTS option because they are deprecated.  It should
>>>>> only mention the SCTP_EVENT option.
>>>> Well, there are implementations out which support this extension
>>>> but not the new way of subscribing to events.
>>>>=20
>>>> I added text to make clear which method is deprecated.
>>>>=20
>>>> However, I can also live with just removing the text describing
>>>> the deprecated way.
>>>> Randy? Peter?
>>>=20
>>>=20
>>> I don't mind either way.. we can just strike the text... we could
>>> even add the new functionality that is in the LC socket-api... That
>>> would probably be better..
>> Hmm. I prefer keeping the socket API ID as it is, because:
>> * it passed the WG LC.
>> * protocol extensions might need to extend the socket API anyway.
>>=20
>> So, I would prefer to strike the text referring to the deprecated =
API.
>=20
> Fine by me.. I did not mean change the socket api.. but to add
> the new methods from the socket api into the stream reset draft..
Hmm. I don't get what you are suggesting...

The socket API in the stream reset should be in tune with the new
socket API. We only have text referring to deprecated API elements.
So I was suggesting to remove this text.

So which new methods from the socket API do you want to add to
the stream reset ID?

Best regards
Michael
>=20
> But I can live with either
>=20
> R
>=20
>>=20
>> Best regards
>> Michael
>>>=20
>>>=20
>>> R
>>>>>=20
>>>>> In all the new events, there are "denied" and "failed" events.  It
>>>>> is not clear what "failed" means.  The peer does not respond to
>>>>> a request and the association times out?  I suggest that it should
>>>>> be made clearer.
>>>> Have a look at table 3. The peer can indicate that there was an
>>>> error or that it denied the request.
>>>>>=20
>>>>> In 6.3.1, IMHO, it is unusual to enable a feature by "removing the
>>>>> deny flag."  It is usually done by setting the enable flag.  This
>>>>> means that by default, calling =
getsockopt(SCTP_ENABLE_STREAM_RESET)
>>>>> returns a 0 assoc_value.  To enable one feature, call setsockopt()
>>>>> with that feature's flag on.
>>>> We made deny the default to avoid any problems if an application
>>>> can not handle discontinuities in received SSN/TSN and runs now
>>>> on a kernel supporting this extension. If an application wants
>>>> to use this feature, it must enable it explicitly.
>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> --=20
>>>>>=20
>>>>> 					K. Poon.
>>>>> 					ka-cheong.poon@oracle.com
>>>>>=20
>>>>=20
>>>>=20
>>>=20
>>> -----
>>> Randall Stewart
>>> randall@lakerest.net
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>=20
>>=20
>=20
> -----
> Randall Stewart
> randall@lakerest.net
>=20
>=20
>=20
>=20
>=20


From randall@lakerest.net  Mon Mar 14 14:35:12 2011
Return-Path: <randall@lakerest.net>
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 76F5C3A6F43 for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 14:35:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.201
X-Spam-Level: *
X-Spam-Status: No, score=1.201 tagged_above=-999 required=5 tests=[AWL=3.144,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 ePKBYl72IwsU for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 14:35:11 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id E4D193A6BBA for <tsvwg@ietf.org>; Mon, 14 Mar 2011 14:35:10 -0700 (PDT)
Received: from [32.177.10.31] ([32.177.10.31]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2ELaP6a095115 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 14 Mar 2011 17:36:32 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <E945C0E8-53B8-4EF0-8D04-DBA70E5BF4C1@lurchi.franken.de>
Date: Mon, 14 Mar 2011 17:36:17 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <F5F9727D-6ED1-4F97-B275-1A8DF768CCFD@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <51679D6F-1789-46BE-B1E5-22AE064B27E2@lakerest.net> <9B899D4B-6CF7-4A2C-8C12-748A73576579@lurchi.franken.de> <41206F6C-9221-4BB6-9E2F-EBB8C9CB6913@lakerest.net> <E945C0E8-53B8-4EF0-8D04-DBA70E5BF4C1@lurchi.franken.de>
To: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.1082)
Cc: Kacheong Poon <ka-cheong.poon@oracle.com>, 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, 14 Mar 2011 21:35:12 -0000

>>> 
>> 
>> Fine by me.. I did not mean change the socket api.. but to add
>> the new methods from the socket api into the stream reset draft..
> Hmm. I don't get what you are suggesting...
> 
> The socket API in the stream reset should be in tune with the new
> socket API. We only have text referring to deprecated API elements.
> So I was suggesting to remove this text.
> 
> So which new methods from the socket API do you want to add to
> the stream reset ID?
> 
> Best regards
> Michael


What I mean is add the individual socket options like we
have in the socket api draft..

I.e. instead of expanding the events .. add an event
explicitly for stream reset to turn on off notifications..

Is that clearer?

R

-----
Randall Stewart
randall@lakerest.net





From Michael.Tuexen@lurchi.franken.de  Mon Mar 14 14:49:30 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 8B8693A6A4B for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 14:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.997
X-Spam-Level: 
X-Spam-Status: No, score=-0.997 tagged_above=-999 required=5 tests=[AWL=0.946,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 22UsRBwydC50 for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 14:49:29 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id 6FC8B3A6F43 for <tsvwg@ietf.org>; Mon, 14 Mar 2011 14:49:29 -0700 (PDT)
Received: from [192.168.1.113] (p5481DBED.dip.t-dialin.net [84.129.219.237]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 9868D1C0C0BD8; Mon, 14 Mar 2011 22:50:52 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <F5F9727D-6ED1-4F97-B275-1A8DF768CCFD@lakerest.net>
Date: Mon, 14 Mar 2011 22:50:51 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <0DEB3D5C-DEB9-44AB-8DA9-443AC23ADA25@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <51679D6F-1789-46BE-B1E5-22AE064B27E2@lakerest.net> <9B899D4B-6CF7-4A2C-8C12-748A73576579@lurchi.franken.de> <41206F6C-9221-4BB6-9E2F-EBB8C9CB6913@lakerest.net> <E945C0E8-53B8-4EF0-8D04-DBA70E5BF4C1@lurchi.franken.de> <F5F9727D-6ED1-4F97-B275-1A8DF768CCFD@lakerest.net>
To: Randy Stewart <randall@lakerest.net>
X-Mailer: Apple Mail (2.1082)
Cc: Kacheong Poon <ka-cheong.poon@oracle.com>, 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, 14 Mar 2011 21:49:30 -0000

On Mar 14, 2011, at 10:36 PM, Randy Stewart wrote:

> 
>>>> 
>>> 
>>> Fine by me.. I did not mean change the socket api.. but to add
>>> the new methods from the socket api into the stream reset draft..
>> Hmm. I don't get what you are suggesting...
>> 
>> The socket API in the stream reset should be in tune with the new
>> socket API. We only have text referring to deprecated API elements.
>> So I was suggesting to remove this text.
>> 
>> So which new methods from the socket API do you want to add to
>> the stream reset ID?
>> 
>> Best regards
>> Michael
> 
> 
> What I mean is add the individual socket options like we
> have in the socket api draft..
> 
> I.e. instead of expanding the events .. add an event
> explicitly for stream reset to turn on off notifications..
Section 6.2 already contains the text (there is a typo SCTP_SET_EVENT
instead of SCTP_EVENT, which I just fixed in CVS), or am I missing
something. The API in the stream reset should be in-tune with the
non-deprecated API in the socket API ID.
Am I missing something?

Best regards
Michael
> 
> Is that clearer?
> 
> R
> 
> -----
> Randall Stewart
> randall@lakerest.net
> 
> 
> 
> 
> 


From randall@lakerest.net  Mon Mar 14 16:23:48 2011
Return-Path: <randall@lakerest.net>
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 F31873A6F9B for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 16:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.153
X-Spam-Level: 
X-Spam-Status: No, score=0.153 tagged_above=-999 required=5 tests=[AWL=2.096,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 7WMAaw2W2uuy for <tsvwg@core3.amsl.com>; Mon, 14 Mar 2011 16:23:47 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 69A053A6F2F for <tsvwg@ietf.org>; Mon, 14 Mar 2011 16:23:46 -0700 (PDT)
Received: from [32.177.10.31] ([32.177.10.31]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2ENP02b099356 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 14 Mar 2011 19:25:06 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <0DEB3D5C-DEB9-44AB-8DA9-443AC23ADA25@lurchi.franken.de>
Date: Mon, 14 Mar 2011 19:24:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0757B6BD-05E3-4000-BEA5-3FC28D9E390F@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <51679D6F-1789-46BE-B1E5-22AE064B27E2@lakerest.net> <9B899D4B-6CF7-4A2C-8C12-748A73576579@lurchi.franken.de> <41206F6C-9221-4BB6-9E2F-EBB8C9CB6913@lakerest.net> <E945C0E8-53B8-4EF0-8D04-DBA70E5BF4C1@lurchi.franken.de> <F5F9727D-6ED1-4F97-B275-1A8DF768CCFD@lakerest.net> <0DEB3D5C-DEB9-44AB-8DA9-443AC23ADA25@lurchi.franken.de>
To: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.1082)
Cc: Kacheong Poon <ka-cheong.poon@oracle.com>, 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, 14 Mar 2011 23:23:48 -0000

On Mar 14, 2011, at 5:50 PM, Michael T=FCxen wrote:

> On Mar 14, 2011, at 10:36 PM, Randy Stewart wrote:
>=20
>>=20
>>>>>=20
>>>>=20
>>>> Fine by me.. I did not mean change the socket api.. but to add
>>>> the new methods from the socket api into the stream reset draft..
>>> Hmm. I don't get what you are suggesting...
>>>=20
>>> The socket API in the stream reset should be in tune with the new
>>> socket API. We only have text referring to deprecated API elements.
>>> So I was suggesting to remove this text.
>>>=20
>>> So which new methods from the socket API do you want to add to
>>> the stream reset ID?
>>>=20
>>> Best regards
>>> Michael
>>=20
>>=20
>> What I mean is add the individual socket options like we
>> have in the socket api draft..
>>=20
>> I.e. instead of expanding the events .. add an event
>> explicitly for stream reset to turn on off notifications..
> Section 6.2 already contains the text (there is a typo SCTP_SET_EVENT
> instead of SCTP_EVENT, which I just fixed in CVS), or am I missing
> something. The API in the stream reset should be in-tune with the
> non-deprecated API in the socket API ID.
> Am I missing something?

Its probably me missing something.. I had thought it was not from
Kacheongs response.. if its in tune then just kill the other
text ;-)

R

>=20
> Best regards
> Michael
>>=20
>> Is that clearer?
>>=20
>> R
>>=20
>> -----
>> Randall Stewart
>> randall@lakerest.net
>>=20
>>=20
>>=20
>>=20
>>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From ka-cheong.poon@oracle.com  Tue Mar 15 03:14:23 2011
Return-Path: <ka-cheong.poon@oracle.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 263D93A6CB7 for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 03:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.952
X-Spam-Level: 
X-Spam-Status: No, score=-1.952 tagged_above=-999 required=5 tests=[AWL=-2.297, BAYES_00=-2.599, FRT_STOCK2=3.988, MANGLED_TOOL=2.3, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, 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 gH4wWl6Gvl4P for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 03:14:21 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id BC1E33A6C99 for <tsvwg@ietf.org>; Tue, 15 Mar 2011 03:14:21 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2FAFiUi011201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 15 Mar 2011 10:15:45 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2FAFhiR012983 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Mar 2011 10:15:43 GMT
Received: from abhmt004.oracle.com (abhmt004.oracle.com [141.146.116.13]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2FAFg1o013240; Tue, 15 Mar 2011 05:15:42 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 15 Mar 2011 03:15:41 -0700
Message-ID: <4D7F3C4B.7090303@oracle.com>
Date: Tue, 15 Mar 2011 18:15:39 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de>
In-Reply-To: <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Source-IP: acsmt358.oracle.com [141.146.40.158]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090209.4D7F3C50.0137,ss=1,fgs=0
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: Tue, 15 Mar 2011 10:14:23 -0000

On 03/14/11 10:12 PM, Michael Tüxen wrote:

>> In the Introduction, the reasons to have a SCTP protocol level
>> mechanism (stream sequence number reset) to solve the app issue
>> are quite sketchy.  For example, one can envision that an app can
>> just remember the stream sequence number before it intends to
>> re-use a stream such that it can differentiate new and old messages.
>> Or there can be a shim layer below the app and above socket layer
>> to do this translation.  Or there can be a socket level option to
>> do the translation.  And all these can be combined with the app
>> layer protocol.  I think the draft should include more details on
>> why a SCTP protocol level mechanism is needed.  An example of real
>> use case which cannot be accomplished without a SCTP level mechanism
>> should probably be provided.
> It is hard to provide such an example since you can implement almost
> everything at every layer. The point is, where an appropriate
> location is for implementing a particular functionality.
>
> You could, for example, implement all your sequencing in the application
> and use only one SCTP stream, sending every message unordered. But
> it this the best function split?


I think this is a dangerous design decision.  What you are
saying is that the transport protocol should provide every
conceivable services any apps may want to use.  IMHO, this is
not the right way to design protocol stack.  We should choose
to have the right service at the right level.  For example,
SCTP provides multiple streams to avoid head of line blocking.
Without it, an app needs to open multiple association to
achieve the same functionality.  So having multiple streams
in SCTP is a sound design choice.

What I am asking above is to have an example which resetting
SSN should be done in SCTP protocol level.  I think this is
a reasonable question this draft should answer.  We need to
understand the background and check different design choices.
Otherwise, how can we know that this is the right choice?
Note that I am just asking for information.  I am not
asserting that this is the wrong choice.  The problem is that
the draft does not provide enough info for me to decide :-(


>> More importantly, the draft contains a mechanism to reset
>> transmission sequence number but there is no rationale given on why
>> this is necessary.  TSN should normally be opaque to applications
>> and should be used solely by SCTP for protocol handling.  It is
>> hard to see why a reset of TSN is needed to make an app work.  I
>> think there should be a very strong reason why such an SCTP protocol
>> mechanism is needed.  But the draft gives no reason.
> The point here is that we are exposing the TSN to the application.
>
> You are right, one can design application protocols running on
> top of SCTP, and the receiver side does not pay attention to
> SSN, SID or TSN. The sender just chooses the SID to enforce the
> appropriate sequencing and everything works.
> This is what I told people when they were thinking about
> using SCTP. However, I had to learn, that they take the SSN into
> account. So resetting them makes sense.


The question I don't understand is that how difficult is for
an app to remember a number such that it can subtract from to
do the same thing as resetting SSN?


> Some application writers want streams to be some dynamic channel
> they can reset easily.
> TSNs are similar to SSNs, they are exposed to the user. So they
> might want the be controlled by the user.


I beg to differ.  TSN is very fundamental to SCTP protocol
handling.  Unless absolutely necessary, I don't think it should
be manipulated by an app.  Anyway, just my $0.02.


> I agree the naming could be improved.
> What about:
> * Re-configuration Chunk
> * Reset Chunk


Re-configuration chunk is a better choice.


> Both covers TSN/SSN. Maybe the first name covers better the addition
> of streams.
>>
>> The diagram in 3.1 is not correct.  It shows that the parameter
>> is only 4 bytes long.
> Right. I'll change that to
>   0                   1                   2                   3
>   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | Type = 0x82   |  Chunk Flags  |      Chunk Length             |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> \                                                               \
> /                   Stream Reset Parameter                      /
> \                                                               \
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> \                                                               \
> /                    Stream Reset Parameter (optional)          /
> \                                                               \
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> OK?


It is right.


>> In 4.1, the use of "Stream Reset Response Sequence Number" is
>> confusing.  The draft says
>>
>>     When this Outgoing SSN Reset Request Parameter is sent in response
>>     to an Incoming SSN Reset Request Parameter this parameter is also
>>     an implicit response to the incoming request.
>>
>> So a request is sent in response to another a request?  A response
>> to a request is understandable, and the response is either request
>> accepted or not.  But a request is sent responding to a request is
>> confusing.  It is like sending an SCTP_ABORT in response to an
>> SCTP_ABORT.
> The "Incoming SSN Reset Request" requests an "Outgoing SSN Reset Request"
> to be sent. To simplify things, the sending of the "Outgoing SSN Reset Request"
> is an implicit acknowledgement.


I understand this.  But my question is why we need such a
protocol mechanism while the app can perfectly do it.  My
point is that the app layer protocol must decide to do the
reset first.  So it can tell the other side to initiate it.
Again, this is a design decision when need more explanations.


>> I suppose the rationale, as described in section 5, is that the
>> originator of resetting should be the outgoing side.  But this
>> raises the question of why then there is an Incoming SSN Reset
>> Request.  This just makes the mechanism unnecessarily more
>> complicated.  Given that the app layer protocol must first agree
>> on the reset operation, it is unclear why there is a need to have
>> the Incoming SSN Reset Request.  And if there is really such a
>> reason, then why does the same reason not applicable to the SSN/TSN
>> resetting and adding more streams?  So should there also be an
>> Incoming SSN/TSN Reset Request and Incoming Adding Streams Request?
> The SSN/TSN Reset is a reset in both directions.
>
> However, you are right, an Add Incoming Streams Request Parameter
> is missing. I think we should add this. It is conceptually missing.
> Randy, Peter: What do you think?


My take is that there should be no "Incoming" request to
make things simple.  I always think KISS is a good design
principle.  We should have a feature in the transport
protocol level only if it is necessary.


>> I suppose there is only the need to have Outgoing SSN Reset Request.
>> The app layer protocol should handle which side does the initiation.
>> A consequence of not having Incoming request is that then there is
>> no need to have an optional second parameter in the chunk.  This
>> also eliminates race of Incoming/Outgoing requests cross over.
>> Given this simplicity, I think the draft should provide a reason
>> that the Incoming request is absolutely necessary.
> The reasoning for me is to provide a "complete" solution. I do not
> want to provide this part of functionality right now and figure out
> in a couple of month that I'm missing another one. I prefer to
> extend it once, not multiple times.


Another way to look at it is "over design."  Since we are
talking about a standard, it is wise to be very careful.
We can always add a mechanism later.  But once a mechanism is
deployed, it is difficult to "obsolete" it even though later
we think that it is actually a bad choice.


>> In all the new events, there are "denied" and "failed" events.  It
>> is not clear what "failed" means.  The peer does not respond to
>> a request and the association times out?  I suggest that it should
>> be made clearer.
> Have a look at table 3. The peer can indicate that there was an
> error or that it denied the request.


The result is that the request is not successful, right?
So it seems that there should only be one request failure
event with the appropriate error cause.  Deny is one of
the error cause.


>> In 6.3.1, IMHO, it is unusual to enable a feature by "removing the
>> deny flag."  It is usually done by setting the enable flag.  This
>> means that by default, calling getsockopt(SCTP_ENABLE_STREAM_RESET)
>> returns a 0 assoc_value.  To enable one feature, call setsockopt()
>> with that feature's flag on.
> We made deny the default to avoid any problems if an application
> can not handle discontinuities in received SSN/TSN and runs now
> on a kernel supporting this extension. If an application wants
> to use this feature, it must enable it explicitly.


I was not saying that "accept" is the default.  Calling
getsockopt(SCTP_ENABLE_STREAM_RESET) and gets back 0 means
that this mechanism is not enabled (hence the _ENABLE_
name in the option name).  0 means not feature flag is
set.  This is the default.  Calling
setsockopt(SCTP_ENABLE_STREAM_RESET) with the appropriate
flags will enable those features.  IMHO, it is not that
intuitive to have an _ENABLE_ option to deny features.
_ENABLE_ option should enable features.  Just a nit.



-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Tue Mar 15 03:30:32 2011
Return-Path: <ka-cheong.poon@oracle.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 8AF313A6D2E for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 03:30:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.33
X-Spam-Level: 
X-Spam-Status: No, score=-4.33 tagged_above=-999 required=5 tests=[AWL=1.613,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, 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 0VI-sun7awjE for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 03:30:31 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 71EDE3A6D1E for <tsvwg@ietf.org>; Tue, 15 Mar 2011 03:30:31 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2FAVsG0005651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 15 Mar 2011 10:31:55 GMT
Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2FAVrL6003266 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Mar 2011 10:31:53 GMT
Received: from abhmt018.oracle.com (abhmt018.oracle.com [141.146.116.27]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2FAVrjU013130; Tue, 15 Mar 2011 05:31:53 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 15 Mar 2011 03:31:52 -0700
Message-ID: <4D7F4016.3080904@oracle.com>
Date: Tue, 15 Mar 2011 18:31:50 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com>
In-Reply-To: <4D7F3C4B.7090303@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt356.oracle.com [141.146.40.156]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090209.4D7F401A.0029,ss=1,fgs=0
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: Tue, 15 Mar 2011 10:30:32 -0000

On 03/15/11 06:15 PM, Kacheong Poon wrote:

> What I am asking above is to have an example which resetting
> SSN should be done in SCTP protocol level. I think this is
> a reasonable question this draft should answer. We need to
> understand the background and check different design choices.
> Otherwise, how can we know that this is the right choice?
> Note that I am just asking for information. I am not
> asserting that this is the wrong choice. The problem is that
> the draft does not provide enough info for me to decide :-(


BTW, is it true that only the streams addition mechanism is
being requested by another IETF protocol, IPFIX?  Since
this draft is supposed to be on standard track, isn't it a
pre-requisite that some real apps must be using those
features before this draft becomes an RFC?  Since Michael
mentioned that there is running code using these features, I
think information should be provided to the WG about them.


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From Michael.Tuexen@lurchi.franken.de  Tue Mar 15 04:44:54 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 B8A373A6C78 for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 04:44:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.204
X-Spam-Level: 
X-Spam-Status: No, score=-1.204 tagged_above=-999 required=5 tests=[AWL=0.739,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 Ky6kQFF3r9CZ for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 04:44:54 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id 88E113A6C96 for <tsvwg@ietf.org>; Tue, 15 Mar 2011 04:44:53 -0700 (PDT)
Received: from [192.168.1.113] (p5481B2C9.dip.t-dialin.net [84.129.178.201]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 0B7021C0B4613; Tue, 15 Mar 2011 12:46:15 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4D7F4016.3080904@oracle.com>
Date: Tue, 15 Mar 2011 12:46:15 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <FBB96A7C-2493-4E08-8FFE-7ECD651FC702@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <4D7F4016.3080904@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
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: Tue, 15 Mar 2011 11:44:54 -0000

Hi Kacheong,

comments in-line.

Best regards
Michael

On Mar 15, 2011, at 11:31 AM, Kacheong Poon wrote:

> On 03/15/11 06:15 PM, Kacheong Poon wrote:
> 
>> What I am asking above is to have an example which resetting
>> SSN should be done in SCTP protocol level. I think this is
>> a reasonable question this draft should answer. We need to
>> understand the background and check different design choices.
>> Otherwise, how can we know that this is the right choice?
>> Note that I am just asking for information. I am not
>> asserting that this is the wrong choice. The problem is that
>> the draft does not provide enough info for me to decide :-(
> 
> 
> BTW, is it true that only the streams addition mechanism is
> being requested by another IETF protocol, IPFIX?  Since
I think so.
> this draft is supposed to be on standard track, isn't it a
> pre-requisite that some real apps must be using those
> features before this draft becomes an RFC?  Since Michael
As far as I know, there is even no implementation required
to be able to go for PS. You need two independent implementations
for all features to move from PS to DS. But I think even for
DS there is no requirement on other protocols actually using
this one. To go from DS to IS there is the requirement for
being widely deployed. This requires being used.
But this is only my understanding.
The WG chairs know better and may want to jump in...
> mentioned that there is running code using these features, I
> think information should be provided to the WG about them.
What I said:
* For the most part of the ID, it is implemented in FreeBSD.
  We are not using the API described in the ID, since we
  haven't moved to the new, non-deprecated API.
* I've been asked several times (can't be more specific)
  about the semantics of the SCTP streams. What developers
  want is an easy method to setup and terminate uni directional
  channels without implementing this stuff by their own.
  I'll give one example (HTTP tunneling) in the response to your
  other e-mail.

Best regards
Michael
> 
> 
> -- 
> 
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
> 


From randall@lakerest.net  Tue Mar 15 05:48:36 2011
Return-Path: <randall@lakerest.net>
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 512553A6BC3 for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 05:48:36 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rO288ke5RtAD for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 05:48:35 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id C8A303A6D41 for <tsvwg@ietf.org>; Tue, 15 Mar 2011 05:48:34 -0700 (PDT)
Received: from mobile-166-187-165-233.mycingular.net (mobile-166-187-165-233.mycingular.net [166.187.165.233] (may be forged)) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2FCnnHe029211 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 15 Mar 2011 08:49:55 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <4D7F4016.3080904@oracle.com>
Date: Tue, 15 Mar 2011 08:49:41 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <D262443F-0E7E-48BD-86D3-AD8E4B071F54@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <4D7F4016.3080904@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
Cc: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>, 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: Tue, 15 Mar 2011 12:48:36 -0000

On Mar 15, 2011, at 6:31 AM, Kacheong Poon wrote:

> On 03/15/11 06:15 PM, Kacheong Poon wrote:
> 
>> What I am asking above is to have an example which resetting
>> SSN should be done in SCTP protocol level. I think this is
>> a reasonable question this draft should answer. We need to
>> understand the background and check different design choices.
>> Otherwise, how can we know that this is the right choice?
>> Note that I am just asking for information. I am not
>> asserting that this is the wrong choice. The problem is that
>> the draft does not provide enough info for me to decide :-(
> 
> 
> BTW, is it true that only the streams addition mechanism is
> being requested by another IETF protocol, IPFIX?  Since
> this draft is supposed to be on standard track, isn't it a
> pre-requisite that some real apps must be using those
> features before this draft becomes an RFC?  Since Michael
> mentioned that there is running code using these features, I
> think information should be provided to the WG about them.

Kacheong:

I can gladly provide some code that runs it.. not all.. since some of
the stuff was proprietary code of another company.

But I do have an FTP client/server around that use
the 

Add-Stream
Stream-Reset

as a convient way to do multi-streaming FTP... when I get
a chance (I am a bit overwhelemd) at work right now I will see
if I can put these up for anyone to download.

R



> 
> 
> -- 
> 
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
> 

-----
Randall Stewart
randall@lakerest.net





From randall@lakerest.net  Tue Mar 15 05:54:38 2011
Return-Path: <randall@lakerest.net>
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 EA8793A6D84 for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 05:54:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.901
X-Spam-Level: 
X-Spam-Status: No, score=0.901 tagged_above=-999 required=5 tests=[AWL=-3.144,  BAYES_00=-2.599, FRT_STOCK2=3.988, MANGLED_TOOL=2.3, 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 SU2rFIR2QFKN for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 05:54:37 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 534723A6D7F for <tsvwg@ietf.org>; Tue, 15 Mar 2011 05:54:36 -0700 (PDT)
Received: from mobile-166-187-165-233.mycingular.net (mobile-166-187-165-233.mycingular.net [166.187.165.233] (may be forged)) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2FCtniO029473 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 15 Mar 2011 08:55:56 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <4D7F3C4B.7090303@oracle.com>
Date: Tue, 15 Mar 2011 08:55:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D891B32A-51F4-401C-A4D6-4DF5FEAF3E91@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
Cc: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>, 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: Tue, 15 Mar 2011 12:54:39 -0000

On Mar 15, 2011, at 6:15 AM, Kacheong Poon wrote:

> On 03/14/11 10:12 PM, Michael T=FCxen wrote:
>=20
>>> In the Introduction, the reasons to have a SCTP protocol level
>>> mechanism (stream sequence number reset) to solve the app issue
>>> are quite sketchy.  For example, one can envision that an app can
>>> just remember the stream sequence number before it intends to
>>> re-use a stream such that it can differentiate new and old messages.
>>> Or there can be a shim layer below the app and above socket layer
>>> to do this translation.  Or there can be a socket level option to
>>> do the translation.  And all these can be combined with the app
>>> layer protocol.  I think the draft should include more details on
>>> why a SCTP protocol level mechanism is needed.  An example of real
>>> use case which cannot be accomplished without a SCTP level mechanism
>>> should probably be provided.
>> It is hard to provide such an example since you can implement almost
>> everything at every layer. The point is, where an appropriate
>> location is for implementing a particular functionality.
>>=20
>> You could, for example, implement all your sequencing in the =
application
>> and use only one SCTP stream, sending every message unordered. But
>> it this the best function split?
>=20
>=20
> I think this is a dangerous design decision.  What you are
> saying is that the transport protocol should provide every
> conceivable services any apps may want to use.  IMHO, this is
> not the right way to design protocol stack.  We should choose
> to have the right service at the right level.  For example,
> SCTP provides multiple streams to avoid head of line blocking.
> Without it, an app needs to open multiple association to
> achieve the same functionality.  So having multiple streams
> in SCTP is a sound design choice.


Resetting a stream then lets an app re-use it sort of like
ftp uses the closing of a connection to indicate that the
file transfer is complete.... I don't see thats a poor design
choice.

>=20
> What I am asking above is to have an example which resetting
> SSN should be done in SCTP protocol level.  I think this is
> a reasonable question this draft should answer.  We need to
> understand the background and check different design choices.
> Otherwise, how can we know that this is the right choice?
> Note that I am just asking for information.  I am not
> asserting that this is the wrong choice.  The problem is that
> the draft does not provide enough info for me to decide :-(

Hmm.. sounds to me above you are saying its a wrong choice ;-0

>=20
>=20
>>> More importantly, the draft contains a mechanism to reset
>>> transmission sequence number but there is no rationale given on why
>>> this is necessary.  TSN should normally be opaque to applications
>>> and should be used solely by SCTP for protocol handling.  It is
>>> hard to see why a reset of TSN is needed to make an app work.  I
>>> think there should be a very strong reason why such an SCTP protocol
>>> mechanism is needed.  But the draft gives no reason.
>> The point here is that we are exposing the TSN to the application.
>>=20
>> You are right, one can design application protocols running on
>> top of SCTP, and the receiver side does not pay attention to
>> SSN, SID or TSN. The sender just chooses the SID to enforce the
>> appropriate sequencing and everything works.
>> This is what I told people when they were thinking about
>> using SCTP. However, I had to learn, that they take the SSN into
>> account. So resetting them makes sense.
>=20
>=20
> The question I don't understand is that how difficult is for
> an app to remember a number such that it can subtract from to
> do the same thing as resetting SSN?

So lets see .. what happens when I send more than 65,536 messages
as I re-use the stream say 10.000 times?

Or do we say no you may only send N messages where N =3D =
65k/number-of-times you wish to
use it?

>=20
>=20
>> Some application writers want streams to be some dynamic channel
>> they can reset easily.
>> TSNs are similar to SSNs, they are exposed to the user. So they
>> might want the be controlled by the user.
>=20
>=20
> I beg to differ.  TSN is very fundamental to SCTP protocol
> handling.  Unless absolutely necessary, I don't think it should
> be manipulated by an app.  Anyway, just my $0.02.
>=20
>=20
>> I agree the naming could be improved.
>> What about:
>> * Re-configuration Chunk
>> * Reset Chunk
>=20
>=20
> Re-configuration chunk is a better choice.


Sounds fine to me ;-)

>=20
>=20
>> Both covers TSN/SSN. Maybe the first name covers better the addition
>> of streams.
>>>=20
>>> The diagram in 3.1 is not correct.  It shows that the parameter
>>> is only 4 bytes long.
>> Right. I'll change that to
>>  0                   1                   2                   3
>>  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> | Type =3D 0x82   |  Chunk Flags  |      Chunk Length             |
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> \                                                               \
>> /                   Stream Reset Parameter                      /
>> \                                                               \
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> \                                                               \
>> /                    Stream Reset Parameter (optional)          /
>> \                                                               \
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>=20
>> OK?
>=20
>=20
> It is right.
>=20
>=20
>>> In 4.1, the use of "Stream Reset Response Sequence Number" is
>>> confusing.  The draft says
>>>=20
>>>    When this Outgoing SSN Reset Request Parameter is sent in =
response
>>>    to an Incoming SSN Reset Request Parameter this parameter is also
>>>    an implicit response to the incoming request.
>>>=20
>>> So a request is sent in response to another a request?  A response
>>> to a request is understandable, and the response is either request
>>> accepted or not.  But a request is sent responding to a request is
>>> confusing.  It is like sending an SCTP_ABORT in response to an
>>> SCTP_ABORT.
>> The "Incoming SSN Reset Request" requests an "Outgoing SSN Reset =
Request"
>> to be sent. To simplify things, the sending of the "Outgoing SSN =
Reset Request"
>> is an implicit acknowledgement.
>=20
>=20
> I understand this.  But my question is why we need such a
> protocol mechanism while the app can perfectly do it.  My
> point is that the app layer protocol must decide to do the
> reset first.  So it can tell the other side to initiate it.
> Again, this is a design decision when need more explanations.
>=20
>=20
>>> I suppose the rationale, as described in section 5, is that the
>>> originator of resetting should be the outgoing side.  But this
>>> raises the question of why then there is an Incoming SSN Reset
>>> Request.  This just makes the mechanism unnecessarily more
>>> complicated.  Given that the app layer protocol must first agree
>>> on the reset operation, it is unclear why there is a need to have
>>> the Incoming SSN Reset Request.  And if there is really such a
>>> reason, then why does the same reason not applicable to the SSN/TSN
>>> resetting and adding more streams?  So should there also be an
>>> Incoming SSN/TSN Reset Request and Incoming Adding Streams Request?
>> The SSN/TSN Reset is a reset in both directions.
>>=20
>> However, you are right, an Add Incoming Streams Request Parameter
>> is missing. I think we should add this. It is conceptually missing.
>> Randy, Peter: What do you think?
>=20
>=20
> My take is that there should be no "Incoming" request to
> make things simple.  I always think KISS is a good design
> principle.  We should have a feature in the transport
> protocol level only if it is necessary.
>=20
>=20
>>> I suppose there is only the need to have Outgoing SSN Reset Request.
>>> The app layer protocol should handle which side does the initiation.
>>> A consequence of not having Incoming request is that then there is
>>> no need to have an optional second parameter in the chunk.  This
>>> also eliminates race of Incoming/Outgoing requests cross over.
>>> Given this simplicity, I think the draft should provide a reason
>>> that the Incoming request is absolutely necessary.
>> The reasoning for me is to provide a "complete" solution. I do not
>> want to provide this part of functionality right now and figure out
>> in a couple of month that I'm missing another one. I prefer to
>> extend it once, not multiple times.
>=20
>=20
> Another way to look at it is "over design."  Since we are
> talking about a standard, it is wise to be very careful.
> We can always add a mechanism later.  But once a mechanism is
> deployed, it is difficult to "obsolete" it even though later
> we think that it is actually a bad choice.
>=20
>=20
>>> In all the new events, there are "denied" and "failed" events.  It
>>> is not clear what "failed" means.  The peer does not respond to
>>> a request and the association times out?  I suggest that it should
>>> be made clearer.
>> Have a look at table 3. The peer can indicate that there was an
>> error or that it denied the request.
>=20
>=20
> The result is that the request is not successful, right?
> So it seems that there should only be one request failure
> event with the appropriate error cause.  Deny is one of
> the error cause.
>=20
>=20
>>> In 6.3.1, IMHO, it is unusual to enable a feature by "removing the
>>> deny flag."  It is usually done by setting the enable flag.  This
>>> means that by default, calling getsockopt(SCTP_ENABLE_STREAM_RESET)
>>> returns a 0 assoc_value.  To enable one feature, call setsockopt()
>>> with that feature's flag on.
>> We made deny the default to avoid any problems if an application
>> can not handle discontinuities in received SSN/TSN and runs now
>> on a kernel supporting this extension. If an application wants
>> to use this feature, it must enable it explicitly.
>=20
>=20
> I was not saying that "accept" is the default.  Calling
> getsockopt(SCTP_ENABLE_STREAM_RESET) and gets back 0 means
> that this mechanism is not enabled (hence the _ENABLE_
> name in the option name).  0 means not feature flag is
> set.  This is the default.  Calling
> setsockopt(SCTP_ENABLE_STREAM_RESET) with the appropriate
> flags will enable those features.  IMHO, it is not that
> intuitive to have an _ENABLE_ option to deny features.
> _ENABLE_ option should enable features.  Just a nit.


Which I am sure Michael has already fixed (I saw a nit- commit go into
the cvs ietf repo -D)

R
>=20
>=20
>=20
> --=20
>=20
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
>=20

-----
Randall Stewart
randall@lakerest.net





From Michael.Tuexen@lurchi.franken.de  Tue Mar 15 06:13:37 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 58DF73A6D19 for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 06:13:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.802
X-Spam-Level: *
X-Spam-Status: No, score=1.802 tagged_above=-999 required=5 tests=[AWL=-2.543,  BAYES_00=-2.599, FRT_STOCK2=3.988, MANGLED_TOOL=2.3, MIME_8BIT_HEADER=0.3, 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 NhcSLljc065F for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 06:13:36 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id EEE453A6BCC for <tsvwg@ietf.org>; Tue, 15 Mar 2011 06:13:34 -0700 (PDT)
Received: from [192.168.1.113] (p5481B2C9.dip.t-dialin.net [84.129.178.201]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 962DF1C0B4613; Tue, 15 Mar 2011 14:14:58 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4D7F3C4B.7090303@oracle.com>
Date: Tue, 15 Mar 2011 14:14:57 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
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: Tue, 15 Mar 2011 13:13:37 -0000

On Mar 15, 2011, at 11:15 AM, Kacheong Poon wrote:

> On 03/14/11 10:12 PM, Michael T=FCxen wrote:
>=20
>>> In the Introduction, the reasons to have a SCTP protocol level
>>> mechanism (stream sequence number reset) to solve the app issue
>>> are quite sketchy.  For example, one can envision that an app can
>>> just remember the stream sequence number before it intends to
>>> re-use a stream such that it can differentiate new and old messages.
>>> Or there can be a shim layer below the app and above socket layer
>>> to do this translation.  Or there can be a socket level option to
>>> do the translation.  And all these can be combined with the app
>>> layer protocol.  I think the draft should include more details on
>>> why a SCTP protocol level mechanism is needed.  An example of real
>>> use case which cannot be accomplished without a SCTP level mechanism
>>> should probably be provided.
>> It is hard to provide such an example since you can implement almost
>> everything at every layer. The point is, where an appropriate
>> location is for implementing a particular functionality.
>>=20
>> You could, for example, implement all your sequencing in the =
application
>> and use only one SCTP stream, sending every message unordered. But
>> it this the best function split?
>=20
>=20
> I think this is a dangerous design decision.  What you are
> saying is that the transport protocol should provide every
> conceivable services any apps may want to use.  IMHO, this is
> not the right way to design protocol stack.  We should choose
> to have the right service at the right level.  For example,
> SCTP provides multiple streams to avoid head of line blocking.
> Without it, an app needs to open multiple association to
> achieve the same functionality.  So having multiple streams
> in SCTP is a sound design choice.
I agree, the question is where to put which functionality best.
Ten years ago I though the receiver should not pay attention
to the SID, SSN or TSN. For whatever reason, these fields
are exposed to the application writer. So they start looking
at them.
>=20
> What I am asking above is to have an example which resetting
> SSN should be done in SCTP protocol level.  I think this is
> a reasonable question this draft should answer.  We need to
> understand the background and check different design choices.
> Otherwise, how can we know that this is the right choice?
> Note that I am just asking for information.  I am not
> asserting that this is the wrong choice.  The problem is that
> the draft does not provide enough info for me to decide :-(
OK, think about an HTTP proxy which tunnels HTTP to another HTTP proxy.
You could map incoming TCP connections to one proxy to a stream of
an SCTP association between the two proxies. When the TCP terminate,
including being reseted, you want to communicate this to the other end.
One possibility is to reset the stream. In case of an reset, you
might even bring PR-SCTP into the game.
On the SCTP association, you would only see HTTP traffic.
Can you do this without Stream Reset. Sure. But you need to define
an application protocol which implemented the resetting. You need
a request, a reply, the procedures and you need to multiplex
this with the HTTP traffic. You can use the PPID for demultiplexing.
You can do it, but it is much harder for the application writer dealing
with HTTP.
>=20
>=20
>>> More importantly, the draft contains a mechanism to reset
>>> transmission sequence number but there is no rationale given on why
>>> this is necessary.  TSN should normally be opaque to applications
>>> and should be used solely by SCTP for protocol handling.  It is
>>> hard to see why a reset of TSN is needed to make an app work.  I
>>> think there should be a very strong reason why such an SCTP protocol
>>> mechanism is needed.  But the draft gives no reason.
>> The point here is that we are exposing the TSN to the application.
>>=20
>> You are right, one can design application protocols running on
>> top of SCTP, and the receiver side does not pay attention to
>> SSN, SID or TSN. The sender just chooses the SID to enforce the
>> appropriate sequencing and everything works.
>> This is what I told people when they were thinking about
>> using SCTP. However, I had to learn, that they take the SSN into
>> account. So resetting them makes sense.
>=20
>=20
> The question I don't understand is that how difficult is for
> an app to remember a number such that it can subtract from to
> do the same thing as resetting SSN?
Because it is more that doing a subtraction. You need messages
to signal the reset. You can do this at the application layer
or at the SCTP layer as indicated above. But for the application
writer it is simple if it is provided. And it is about the
management of the streams, an entity belonging to SCTP.
>=20
>=20
>> Some application writers want streams to be some dynamic channel
>> they can reset easily.
>> TSNs are similar to SSNs, they are exposed to the user. So they
>> might want the be controlled by the user.
>=20
>=20
> I beg to differ.  TSN is very fundamental to SCTP protocol
> handling.  Unless absolutely necessary, I don't think it should
> be manipulated by an app.  Anyway, just my $0.02.
>=20
>=20
>> I agree the naming could be improved.
>> What about:
>> * Re-configuration Chunk
>> * Reset Chunk
>=20
>=20
> Re-configuration chunk is a better choice.
OK, I'll change that.
>=20
>=20
>> Both covers TSN/SSN. Maybe the first name covers better the addition
>> of streams.
>>>=20
>>> The diagram in 3.1 is not correct.  It shows that the parameter
>>> is only 4 bytes long.
>> Right. I'll change that to
>>  0                   1                   2                   3
>>  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> | Type =3D 0x82   |  Chunk Flags  |      Chunk Length             |
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> \                                                               \
>> /                   Stream Reset Parameter                      /
>> \                                                               \
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> \                                                               \
>> /                    Stream Reset Parameter (optional)          /
>> \                                                               \
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>=20
>> OK?
>=20
>=20
> It is right.
>=20
>=20
>>> In 4.1, the use of "Stream Reset Response Sequence Number" is
>>> confusing.  The draft says
>>>=20
>>>    When this Outgoing SSN Reset Request Parameter is sent in =
response
>>>    to an Incoming SSN Reset Request Parameter this parameter is also
>>>    an implicit response to the incoming request.
>>>=20
>>> So a request is sent in response to another a request?  A response
>>> to a request is understandable, and the response is either request
>>> accepted or not.  But a request is sent responding to a request is
>>> confusing.  It is like sending an SCTP_ABORT in response to an
>>> SCTP_ABORT.
>> The "Incoming SSN Reset Request" requests an "Outgoing SSN Reset =
Request"
>> to be sent. To simplify things, the sending of the "Outgoing SSN =
Reset Request"
>> is an implicit acknowledgement.
>=20
>=20
> I understand this.  But my question is why we need such a
> protocol mechanism while the app can perfectly do it.  My
> point is that the app layer protocol must decide to do the
> reset first.  So it can tell the other side to initiate it.
> Again, this is a design decision when need more explanations.
>=20
>=20
>>> I suppose the rationale, as described in section 5, is that the
>>> originator of resetting should be the outgoing side.  But this
>>> raises the question of why then there is an Incoming SSN Reset
>>> Request.  This just makes the mechanism unnecessarily more
>>> complicated.  Given that the app layer protocol must first agree
>>> on the reset operation, it is unclear why there is a need to have
>>> the Incoming SSN Reset Request.  And if there is really such a
>>> reason, then why does the same reason not applicable to the SSN/TSN
>>> resetting and adding more streams?  So should there also be an
>>> Incoming SSN/TSN Reset Request and Incoming Adding Streams Request?
>> The SSN/TSN Reset is a reset in both directions.
>>=20
>> However, you are right, an Add Incoming Streams Request Parameter
>> is missing. I think we should add this. It is conceptually missing.
>> Randy, Peter: What do you think?
>=20
>=20
> My take is that there should be no "Incoming" request to
> make things simple.  I always think KISS is a good design
> principle.  We should have a feature in the transport
> protocol level only if it is necessary.
I agree, I like KISS too. But I do not like "half solutions".
>=20
>=20
>>> I suppose there is only the need to have Outgoing SSN Reset Request.
>>> The app layer protocol should handle which side does the initiation.
>>> A consequence of not having Incoming request is that then there is
>>> no need to have an optional second parameter in the chunk.  This
>>> also eliminates race of Incoming/Outgoing requests cross over.
>>> Given this simplicity, I think the draft should provide a reason
>>> that the Incoming request is absolutely necessary.
>> The reasoning for me is to provide a "complete" solution. I do not
>> want to provide this part of functionality right now and figure out
>> in a couple of month that I'm missing another one. I prefer to
>> extend it once, not multiple times.
>=20
>=20
> Another way to look at it is "over design."  Since we are
> talking about a standard, it is wise to be very careful.
> We can always add a mechanism later.  But once a mechanism is
> deployed, it is difficult to "obsolete" it even though later
> we think that it is actually a bad choice.
>=20
>=20
>>> In all the new events, there are "denied" and "failed" events.  It
>>> is not clear what "failed" means.  The peer does not respond to
>>> a request and the association times out?  I suggest that it should
>>> be made clearer.
>> Have a look at table 3. The peer can indicate that there was an
>> error or that it denied the request.
>=20
>=20
> The result is that the request is not successful, right?
> So it seems that there should only be one request failure
> event with the appropriate error cause.  Deny is one of
> the error cause.
And how do you know that it was successful? Since the information
provided in the events are different, we use different events.
>=20
>=20
>>> In 6.3.1, IMHO, it is unusual to enable a feature by "removing the
>>> deny flag."  It is usually done by setting the enable flag.  This
>>> means that by default, calling getsockopt(SCTP_ENABLE_STREAM_RESET)
>>> returns a 0 assoc_value.  To enable one feature, call setsockopt()
>>> with that feature's flag on.
>> We made deny the default to avoid any problems if an application
>> can not handle discontinuities in received SSN/TSN and runs now
>> on a kernel supporting this extension. If an application wants
>> to use this feature, it must enable it explicitly.
>=20
>=20
> I was not saying that "accept" is the default.  Calling
> getsockopt(SCTP_ENABLE_STREAM_RESET) and gets back 0 means
> that this mechanism is not enabled (hence the _ENABLE_
> name in the option name).  0 means not feature flag is
> set.  This is the default.  Calling
> setsockopt(SCTP_ENABLE_STREAM_RESET) with the appropriate
> flags will enable those features.  IMHO, it is not that
> intuitive to have an _ENABLE_ option to deny features.
> _ENABLE_ option should enable features.  Just a nit.
Now I understand what you are saying. I agree completely.
I changed the flags to SCTP_ENABLE_RESET_IN_STREAM_REQ and so on.
I guess this addresses your point.

I also removed the text regarding the deprecated SCTP_EVENTS socket
option.
>=20
>=20
>=20
> --=20
>=20
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
>=20


From randall@lakerest.net  Tue Mar 15 07:05:21 2011
Return-Path: <randall@lakerest.net>
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 1A59E3A6DA8 for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 07:05:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.623
X-Spam-Level: **
X-Spam-Status: No, score=2.623 tagged_above=-999 required=5 tests=[AWL=-1.722,  BAYES_00=-2.599, FRT_STOCK2=3.988, MANGLED_TOOL=2.3, MIME_8BIT_HEADER=0.3, 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 V2Jgru-uP61C for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 07:05:19 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id CFBED3A6D27 for <tsvwg@ietf.org>; Tue, 15 Mar 2011 07:05:17 -0700 (PDT)
Received: from mobile-166-187-175-038.mycingular.net (mobile-166-187-175-038.mycingular.net [166.187.175.38] (may be forged)) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2FE6Xni032179 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 15 Mar 2011 10:06:39 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de>
Date: Tue, 15 Mar 2011 10:06:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D67FB95D-0672-4CF2-BC0E-8A3D1749ADB5@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de>
To: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.1082)
Cc: Kacheong Poon <ka-cheong.poon@oracle.com>, 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: Tue, 15 Mar 2011 14:05:21 -0000

On Mar 15, 2011, at 9:14 AM, Michael T=FCxen wrote:

> On Mar 15, 2011, at 11:15 AM, Kacheong Poon wrote:
>=20
>> On 03/14/11 10:12 PM, Michael T=FCxen wrote:
>>=20
>>>> In the Introduction, the reasons to have a SCTP protocol level
>>>> mechanism (stream sequence number reset) to solve the app issue
>>>> are quite sketchy.  For example, one can envision that an app can
>>>> just remember the stream sequence number before it intends to
>>>> re-use a stream such that it can differentiate new and old =
messages.
>>>> Or there can be a shim layer below the app and above socket layer
>>>> to do this translation.  Or there can be a socket level option to
>>>> do the translation.  And all these can be combined with the app
>>>> layer protocol.  I think the draft should include more details on
>>>> why a SCTP protocol level mechanism is needed.  An example of real
>>>> use case which cannot be accomplished without a SCTP level =
mechanism
>>>> should probably be provided.
>>> It is hard to provide such an example since you can implement almost
>>> everything at every layer. The point is, where an appropriate
>>> location is for implementing a particular functionality.
>>>=20
>>> You could, for example, implement all your sequencing in the =
application
>>> and use only one SCTP stream, sending every message unordered. But
>>> it this the best function split?
>>=20
>>=20
>> I think this is a dangerous design decision.  What you are
>> saying is that the transport protocol should provide every
>> conceivable services any apps may want to use.  IMHO, this is
>> not the right way to design protocol stack.  We should choose
>> to have the right service at the right level.  For example,
>> SCTP provides multiple streams to avoid head of line blocking.
>> Without it, an app needs to open multiple association to
>> achieve the same functionality.  So having multiple streams
>> in SCTP is a sound design choice.
> I agree, the question is where to put which functionality best.
> Ten years ago I though the receiver should not pay attention
> to the SID, SSN or TSN. For whatever reason, these fields
> are exposed to the application writer. So they start looking
> at them.
>>=20
>> What I am asking above is to have an example which resetting
>> SSN should be done in SCTP protocol level.  I think this is
>> a reasonable question this draft should answer.  We need to
>> understand the background and check different design choices.
>> Otherwise, how can we know that this is the right choice?
>> Note that I am just asking for information.  I am not
>> asserting that this is the wrong choice.  The problem is that
>> the draft does not provide enough info for me to decide :-(
> OK, think about an HTTP proxy which tunnels HTTP to another HTTP =
proxy.
> You could map incoming TCP connections to one proxy to a stream of
> an SCTP association between the two proxies. When the TCP terminate,
> including being reseted, you want to communicate this to the other =
end.
> One possibility is to reset the stream. In case of an reset, you
> might even bring PR-SCTP into the game.
> On the SCTP association, you would only see HTTP traffic.
> Can you do this without Stream Reset. Sure. But you need to define
> an application protocol which implemented the resetting. You need
> a request, a reply, the procedures and you need to multiplex
> this with the HTTP traffic. You can use the PPID for demultiplexing.
> You can do it, but it is much harder for the application writer =
dealing
> with HTTP.


Which is precisely the same sort of thing I did with the FTP client... =
since
ftp is using the close of the connection as the EOF indication.. =
something
that is harder to do if you are trying to use multi-streaming i.e. a =
stream
for each file transfer and want an parallel transfer..

It really helps provide this nice mapping.. STREAM-RESET =3D=3D =
TCP-Connection-Ended.

:-)



>>=20
>>=20
>>>> More importantly, the draft contains a mechanism to reset
>>>> transmission sequence number but there is no rationale given on why
>>>> this is necessary.  TSN should normally be opaque to applications
>>>> and should be used solely by SCTP for protocol handling.  It is
>>>> hard to see why a reset of TSN is needed to make an app work.  I
>>>> think there should be a very strong reason why such an SCTP =
protocol
>>>> mechanism is needed.  But the draft gives no reason.
>>> The point here is that we are exposing the TSN to the application.
>>>=20
>>> You are right, one can design application protocols running on
>>> top of SCTP, and the receiver side does not pay attention to
>>> SSN, SID or TSN. The sender just chooses the SID to enforce the
>>> appropriate sequencing and everything works.
>>> This is what I told people when they were thinking about
>>> using SCTP. However, I had to learn, that they take the SSN into
>>> account. So resetting them makes sense.
>>=20
>>=20
>> The question I don't understand is that how difficult is for
>> an app to remember a number such that it can subtract from to
>> do the same thing as resetting SSN?
> Because it is more that doing a subtraction. You need messages
> to signal the reset. You can do this at the application layer
> or at the SCTP layer as indicated above. But for the application
> writer it is simple if it is provided. And it is about the
> management of the streams, an entity belonging to SCTP.


And don't forget that streams are a very narrow sequence space. Doing
a subtraction won't work if the app needs to send a fairly large number
of messages and wants to "reuse the stream" multiple times. It becomes
a LOT more information that needs to be maintained somehow...


>>=20
>>=20
>>> Some application writers want streams to be some dynamic channel
>>> they can reset easily.
>>> TSNs are similar to SSNs, they are exposed to the user. So they
>>> might want the be controlled by the user.
>>=20
>>=20
>> I beg to differ.  TSN is very fundamental to SCTP protocol
>> handling.  Unless absolutely necessary, I don't think it should
>> be manipulated by an app.  Anyway, just my $0.02.
>>=20
>>=20
>>> I agree the naming could be improved.
>>> What about:
>>> * Re-configuration Chunk
>>> * Reset Chunk
>>=20
>>=20
>> Re-configuration chunk is a better choice.
> OK, I'll change that.
>>=20
>>=20
>>> Both covers TSN/SSN. Maybe the first name covers better the addition
>>> of streams.
>>>>=20
>>>> The diagram in 3.1 is not correct.  It shows that the parameter
>>>> is only 4 bytes long.
>>> Right. I'll change that to
>>> 0                   1                   2                   3
>>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>> | Type =3D 0x82   |  Chunk Flags  |      Chunk Length             |
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>> \                                                               \
>>> /                   Stream Reset Parameter                      /
>>> \                                                               \
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>> \                                                               \
>>> /                    Stream Reset Parameter (optional)          /
>>> \                                                               \
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>=20
>>> OK?
>>=20
>>=20
>> It is right.
>>=20
>>=20
>>>> In 4.1, the use of "Stream Reset Response Sequence Number" is
>>>> confusing.  The draft says
>>>>=20
>>>>   When this Outgoing SSN Reset Request Parameter is sent in =
response
>>>>   to an Incoming SSN Reset Request Parameter this parameter is also
>>>>   an implicit response to the incoming request.
>>>>=20
>>>> So a request is sent in response to another a request?  A response
>>>> to a request is understandable, and the response is either request
>>>> accepted or not.  But a request is sent responding to a request is
>>>> confusing.  It is like sending an SCTP_ABORT in response to an
>>>> SCTP_ABORT.
>>> The "Incoming SSN Reset Request" requests an "Outgoing SSN Reset =
Request"
>>> to be sent. To simplify things, the sending of the "Outgoing SSN =
Reset Request"
>>> is an implicit acknowledgement.
>>=20
>>=20
>> I understand this.  But my question is why we need such a
>> protocol mechanism while the app can perfectly do it.  My
>> point is that the app layer protocol must decide to do the
>> reset first.  So it can tell the other side to initiate it.
>> Again, this is a design decision when need more explanations.
>>=20
>>=20
>>>> I suppose the rationale, as described in section 5, is that the
>>>> originator of resetting should be the outgoing side.  But this
>>>> raises the question of why then there is an Incoming SSN Reset
>>>> Request.  This just makes the mechanism unnecessarily more
>>>> complicated.  Given that the app layer protocol must first agree
>>>> on the reset operation, it is unclear why there is a need to have
>>>> the Incoming SSN Reset Request.  And if there is really such a
>>>> reason, then why does the same reason not applicable to the SSN/TSN
>>>> resetting and adding more streams?  So should there also be an
>>>> Incoming SSN/TSN Reset Request and Incoming Adding Streams Request?
>>> The SSN/TSN Reset is a reset in both directions.
>>>=20
>>> However, you are right, an Add Incoming Streams Request Parameter
>>> is missing. I think we should add this. It is conceptually missing.
>>> Randy, Peter: What do you think?
>>=20
>>=20
>> My take is that there should be no "Incoming" request to
>> make things simple.  I always think KISS is a good design
>> principle.  We should have a feature in the transport
>> protocol level only if it is necessary.
> I agree, I like KISS too. But I do not like "half solutions".

:-)


>>=20
>>=20
>>>> I suppose there is only the need to have Outgoing SSN Reset =
Request.
>>>> The app layer protocol should handle which side does the =
initiation.
>>>> A consequence of not having Incoming request is that then there is
>>>> no need to have an optional second parameter in the chunk.  This
>>>> also eliminates race of Incoming/Outgoing requests cross over.
>>>> Given this simplicity, I think the draft should provide a reason
>>>> that the Incoming request is absolutely necessary.
>>> The reasoning for me is to provide a "complete" solution. I do not
>>> want to provide this part of functionality right now and figure out
>>> in a couple of month that I'm missing another one. I prefer to
>>> extend it once, not multiple times.
>>=20
>>=20
>> Another way to look at it is "over design."  Since we are
>> talking about a standard, it is wise to be very careful.
>> We can always add a mechanism later.  But once a mechanism is
>> deployed, it is difficult to "obsolete" it even though later
>> we think that it is actually a bad choice.
>>=20
>>=20
>>>> In all the new events, there are "denied" and "failed" events.  It
>>>> is not clear what "failed" means.  The peer does not respond to
>>>> a request and the association times out?  I suggest that it should
>>>> be made clearer.
>>> Have a look at table 3. The peer can indicate that there was an
>>> error or that it denied the request.
>>=20
>>=20
>> The result is that the request is not successful, right?
>> So it seems that there should only be one request failure
>> event with the appropriate error cause.  Deny is one of
>> the error cause.
> And how do you know that it was successful? Since the information
> provided in the events are different, we use different events.
>>=20
>>=20
>>>> In 6.3.1, IMHO, it is unusual to enable a feature by "removing the
>>>> deny flag."  It is usually done by setting the enable flag.  This
>>>> means that by default, calling getsockopt(SCTP_ENABLE_STREAM_RESET)
>>>> returns a 0 assoc_value.  To enable one feature, call setsockopt()
>>>> with that feature's flag on.
>>> We made deny the default to avoid any problems if an application
>>> can not handle discontinuities in received SSN/TSN and runs now
>>> on a kernel supporting this extension. If an application wants
>>> to use this feature, it must enable it explicitly.
>>=20
>>=20
>> I was not saying that "accept" is the default.  Calling
>> getsockopt(SCTP_ENABLE_STREAM_RESET) and gets back 0 means
>> that this mechanism is not enabled (hence the _ENABLE_
>> name in the option name).  0 means not feature flag is
>> set.  This is the default.  Calling
>> setsockopt(SCTP_ENABLE_STREAM_RESET) with the appropriate
>> flags will enable those features.  IMHO, it is not that
>> intuitive to have an _ENABLE_ option to deny features.
>> _ENABLE_ option should enable features.  Just a nit.
> Now I understand what you are saying. I agree completely.
> I changed the flags to SCTP_ENABLE_RESET_IN_STREAM_REQ and so on.
> I guess this addresses your point.
>=20
> I also removed the text regarding the deprecated SCTP_EVENTS socket
> option.


Thanks for doing all these changes Michael ;-)

R

>>=20
>>=20
>>=20
>> --=20
>>=20
>> 					K. Poon.
>> 					ka-cheong.poon@oracle.com
>>=20
>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From Michael.Tuexen@lurchi.franken.de  Tue Mar 15 07:47:54 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 8E2EC3A6D76 for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 07:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 tagged_above=-999 required=5 tests=[AWL=0.797,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 HXE8oDXpiKAq for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 07:47:53 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id 70D0F3A6D31 for <tsvwg@ietf.org>; Tue, 15 Mar 2011 07:47:53 -0700 (PDT)
Received: from [192.168.1.113] (p5481B2C9.dip.t-dialin.net [84.129.178.201]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id C23391C0B461B; Tue, 15 Mar 2011 15:49:16 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4D7F3C4B.7090303@oracle.com>
Date: Tue, 15 Mar 2011 15:49:15 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <D8826A52-1B36-404B-8A60-FEC7DC90EDB4@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
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: Tue, 15 Mar 2011 14:47:54 -0000

Hi Kacheong,

one additional question:


>> I agree the naming could be improved.
>> What about:
>> * Re-configuration Chunk
>> * Reset Chunk
> 
> 
> Re-configuration chunk is a better choice.
> 
> 

I change "STREAM RESET chunk" to "RE-CONFIG chunk".
However, we still have the generic

Stream Reset Parameter 
Stream Reset Request Parameter
Stream Reset Response Parameter

Shouldn't these also be

Re-configuration Parameter
Re-configuration Request Parameter
Re-configuration Response Parameter

What do you think?

Best regards
Michael


From peter.lei@ieee.org  Tue Mar 15 09:29:12 2011
Return-Path: <peter.lei@ieee.org>
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 E8E663A6DA1 for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 09:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.655
X-Spam-Level: 
X-Spam-Status: No, score=-95.655 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_STOCK2=3.988, MANGLED_TOOL=2.3, MIME_8BIT_HEADER=0.3, SARE_SUB_6CONS_WORD=0.356, USER_IN_WHITELIST=-100]
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 aPaJe9Ft1D7d for <tsvwg@core3.amsl.com>; Tue, 15 Mar 2011 09:29:10 -0700 (PDT)
Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by core3.amsl.com (Postfix) with ESMTP id 6E6333A6DAF for <tsvwg@ietf.org>; Tue, 15 Mar 2011 09:29:10 -0700 (PDT)
Received: from omta06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by qmta12.emeryville.ca.mail.comcast.net with comcast id KUPe1g00716AWCUACUWb57; Tue, 15 Mar 2011 16:30:35 +0000
Received: from mbpro5.local ([98.228.214.213]) by omta06.emeryville.ca.mail.comcast.net with comcast id KUWM1g01b4cpPwJ8SUWVtd; Tue, 15 Mar 2011 16:30:34 +0000
Message-ID: <4D7F941C.9050400@ieee.org>
Date: Tue, 15 Mar 2011 11:30:20 -0500
From: Peter Lei <peter.lei@ieee.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.19) Gecko/20081209 Thunderbird/2.0.0.19 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: Randy Stewart <randall@lakerest.net>, =?ISO-8859-1?Q?Michael_T=FCxe?= =?ISO-8859-1?Q?n?= <Michael.Tuexen@lurchi.franken.de>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <51679D6F-1789-46BE-B1E5-22AE064B27E2@lakerest.net>
In-Reply-To: <51679D6F-1789-46BE-B1E5-22AE064B27E2@lakerest.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Kacheong Poon <ka-cheong.poon@oracle.com>, 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: Tue, 15 Mar 2011 16:29:12 -0000

Comments inline:

On 3/14/11 11:06 AM, Randy Stewart wrote:
> In-line..
> 
> On Mar 14, 2011, at 10:12 AM, Michael Tüxen wrote:
> 
>> Hi Kacheong,
>>
>> thank you very much for you comments.
>> I'll try to address them inline.
>>
>> Best regards
>> Michael
>>
>> On Mar 14, 2011, at 11:10 AM, Kacheong Poon wrote:
>>
>>> On 03/14/11 04:48 AM, James M. Polk wrote:
>>>
>>>> We chairs want folks to show or assert they have reviewed this ID and
>>>> give feedback to the list (and not unicast to the chairs). This ID
>>>> cannot progress without that feedback.
>>>
>>>
>>> I have several comments.
>>>
>>> In the Introduction, the reasons to have a SCTP protocol level
>>> mechanism (stream sequence number reset) to solve the app issue
>>> are quite sketchy.  For example, one can envision that an app can
>>> just remember the stream sequence number before it intends to
>>> re-use a stream such that it can differentiate new and old messages.
>>> Or there can be a shim layer below the app and above socket layer
>>> to do this translation.  Or there can be a socket level option to
>>> do the translation.  And all these can be combined with the app
>>> layer protocol.  I think the draft should include more details on
>>> why a SCTP protocol level mechanism is needed.  An example of real
>>> use case which cannot be accomplished without a SCTP level mechanism
>>> should probably be provided.
>> It is hard to provide such an example since you can implement almost
>> everything at every layer. The point is, where an appropriate
>> location is for implementing a particular functionality.
>>
>> You could, for example, implement all your sequencing in the application
>> and use only one SCTP stream, sending every message unordered. But
>> it this the best function split?
>>>
>>> More importantly, the draft contains a mechanism to reset
>>> transmission sequence number but there is no rationale given on why
>>> this is necessary.  TSN should normally be opaque to applications
>>> and should be used solely by SCTP for protocol handling.  It is
>>> hard to see why a reset of TSN is needed to make an app work.  I
>>> think there should be a very strong reason why such an SCTP protocol
>>> mechanism is needed.  But the draft gives no reason.
>> The point here is that we are exposing the TSN to the application.
>>
>> You are right, one can design application protocols running on
>> top of SCTP, and the receiver side does not pay attention to
>> SSN, SID or TSN. The sender just chooses the SID to enforce the
>> appropriate sequencing and everything works.
>> This is what I told people when they were thinking about
>> using SCTP. However, I had to learn, that they take the SSN into
>> account. So resetting them makes sense.
>> Some application writers want streams to be some dynamic channel
>> they can reset easily.
>> TSNs are similar to SSNs, they are exposed to the user. So they
>> might want the be controlled by the user.
>>> I suggest that the new chunk be called "Stream Re-configuration"
>>> since the chunk is also about adding new streams.  But even this
>>> name does not cover the case of resetting TSN, which is at the
>>> association level.  Is it correct to include a parameter which
>>> affects the association level TSN in this chunk?  This also goes
>>> back to the question about the reasons of having TSN reset.
>> I agree the naming could be improved.
>> What about:
>> * Re-configuration Chunk
>> * Reset Chunk
>> Both covers TSN/SSN. Maybe the first name covers better the addition
>> of streams.
>>>
>>> The diagram in 3.1 is not correct.  It shows that the parameter
>>> is only 4 bytes long.
>> Right. I'll change that to
>> 0                   1                   2                   3
>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> | Type = 0x82   |  Chunk Flags  |      Chunk Length             |
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> \                                                               \
>> /                   Stream Reset Parameter                      /
>> \                                                               \
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> \                                                               \
>> /                    Stream Reset Parameter (optional)          /
>> \                                                               \
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>> OK?
>>>
>>> In 4.1, the use of "Stream Reset Response Sequence Number" is
>>> confusing.  The draft says
>>>
>>>   When this Outgoing SSN Reset Request Parameter is sent in response
>>>   to an Incoming SSN Reset Request Parameter this parameter is also
>>>   an implicit response to the incoming request.
>>>
>>> So a request is sent in response to another a request?  A response
>>> to a request is understandable, and the response is either request
>>> accepted or not.  But a request is sent responding to a request is
>>> confusing.  It is like sending an SCTP_ABORT in response to an
>>> SCTP_ABORT.
>> The "Incoming SSN Reset Request" requests an "Outgoing SSN Reset Request"
>> to be sent. To simplify things, the sending of the "Outgoing SSN Reset Request"
>> is an implicit acknowledgement.
>>>
>>> I suppose the rationale, as described in section 5, is that the
>>> originator of resetting should be the outgoing side.  But this
>>> raises the question of why then there is an Incoming SSN Reset
>>> Request.  This just makes the mechanism unnecessarily more
>>> complicated.  Given that the app layer protocol must first agree
>>> on the reset operation, it is unclear why there is a need to have
>>> the Incoming SSN Reset Request.  And if there is really such a
>>> reason, then why does the same reason not applicable to the SSN/TSN
>>> resetting and adding more streams?  So should there also be an
>>> Incoming SSN/TSN Reset Request and Incoming Adding Streams Request?
>> The SSN/TSN Reset is a reset in both directions.
>>
>> However, you are right, an Add Incoming Streams Request Parameter
>> is missing. I think we should add this. It is conceptually missing.
>> Randy, Peter: What do you think?
> 
> 
> I am fine with adding that... ;-)

Yes, agree as well.

>>>
>>> I suppose there is only the need to have Outgoing SSN Reset Request.
>>> The app layer protocol should handle which side does the initiation.
>>> A consequence of not having Incoming request is that then there is
>>> no need to have an optional second parameter in the chunk.  This
>>> also eliminates race of Incoming/Outgoing requests cross over.
>>> Given this simplicity, I think the draft should provide a reason
>>> that the Incoming request is absolutely necessary.
>> The reasoning for me is to provide a "complete" solution. I do not
>> want to provide this part of functionality right now and figure out
>> in a couple of month that I'm missing another one. I prefer to
>> extend it once, not multiple times.
>>>
>>> In first sentence of 4.3, does "all streams" mean "all outgoing
>>> streams" or "all incoming streams?"
>> It means "all incoming and all outgoing streams".
>> I added that as a clarification.
>>>
>>> If a reset timer is running, no other request can be sent out.  So
>>> there can only be one outstanding unacknowledged request.  I suggest
>>> that this is mentioned explicitly in 5.1.1.
>> OK. Done. I added:
>> <t>At any given time there MUST NOT be more than one request be
>> in flight. So if the 'Stream Reset Timer' is running and the
>> the STREAM RESET chunk contains at least one request parameter
>> the chunk MUST be buffered.</t>
>>>
>>> In 6.2, I think it is incorrect to change sctp_event_subscribe
>>> and use SCTP_EVENTS option because they are deprecated.  It should
>>> only mention the SCTP_EVENT option.
>> Well, there are implementations out which support this extension
>> but not the new way of subscribing to events.
>>
>> I added text to make clear which method is deprecated.
>>
>> However, I can also live with just removing the text describing
>> the deprecated way.
>> Randy? Peter?
> 
> 
> I don't mind either way.. we can just strike the text... we could
> even add the new functionality that is in the LC socket-api... That
> would probably be better..

I would suggest we just remove the text that describes the deprecated
behavior and stick with text that is consistent with the latest sockets
API draft.

--peter


> 
> R
>>>
>>> In all the new events, there are "denied" and "failed" events.  It
>>> is not clear what "failed" means.  The peer does not respond to
>>> a request and the association times out?  I suggest that it should
>>> be made clearer.
>> Have a look at table 3. The peer can indicate that there was an
>> error or that it denied the request.
>>>
>>> In 6.3.1, IMHO, it is unusual to enable a feature by "removing the
>>> deny flag."  It is usually done by setting the enable flag.  This
>>> means that by default, calling getsockopt(SCTP_ENABLE_STREAM_RESET)
>>> returns a 0 assoc_value.  To enable one feature, call setsockopt()
>>> with that feature's flag on.
>> We made deny the default to avoid any problems if an application
>> can not handle discontinuities in received SSN/TSN and runs now
>> on a kernel supporting this extension. If an application wants
>> to use this feature, it must enable it explicitly.
> 
>>>
>>>
>>>
>>> -- 
>>>
>>> 					K. Poon.
>>> 					ka-cheong.poon@oracle.com
>>>
>>
>>
> 
> -----
> Randall Stewart
> randall@lakerest.net
> 
> 
> 
> 
> 

From ietfc@btconnect.com  Wed Mar 16 02:34:37 2011
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 18A213A68E0 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 02:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.04
X-Spam-Level: 
X-Spam-Status: No, score=-1.04 tagged_above=-999 required=5 tests=[AWL=-1.397,  BAYES_50=0.001, 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 7zVtEgFIzjPq for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 02:34:36 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr13.btconnect.com [213.123.20.131]) by core3.amsl.com (Postfix) with ESMTP id A07963A68DF for <tsvwg@ietf.org>; Wed, 16 Mar 2011 02:34:35 -0700 (PDT)
Received: from host217-44-145-106.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.106]) by c2bthomr13.btconnect.com with SMTP id CCM09008; Wed, 16 Mar 2011 09:36:00 +0000 (GMT)
Message-ID: <00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "tsvwg" <tsvwg@ietf.org>, "James M. Polk" <jmpolk@cisco.com>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Date: Wed, 16 Mar 2011 09:31:07 +0100
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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4D808480.0070, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr13.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0207.4D808480.01DB,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
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: Wed, 16 Mar 2011 09:34:37 -0000

----- Original Message -----
From: "James M. Polk" <jmpolk@cisco.com>
To: "tsvwg" <tsvwg@ietf.org>
Sent: Sunday, March 13, 2011 9:48 PM

> TSVWG
>
> The WG chairs have determined the WGLC for our SCTP Stream
> Reconfiguration ID continues (i.e., it has not concluded at the 2
> week window) due to lack of feedback to the list. No one has
> commented in a review format that they believe this ID should
> progress. No one has even sent a note merely saying this ID in its
> present form is good to go. That lack of any feedback is troubling
> and could be a sign of a lack of interest in this ID.
>
> The WG chairs like the idea of (and within) this draft, but we need
> transport experts to tell us this, and if the ID in its present form
> is good enough to implement to without those implementations having
> errors or causing bad behavior in SCTP because of how the ID is
> written (focusing mostly on the instructions to implementers in the ID).
>
> We chairs want folks to show or assert they have reviewed this ID and
> give feedback to the list (and not unicast to the chairs). This ID
> cannot progress without that feedback.

I am sitting on my hands because I did not consider the I-D ready for last call
but also, I do not have a view as to whether or not this I-D will be
implemented,
whether or not the additional function is worth standardising - I simply do not
have the contacts to make a judgement on this.

I did comment on a previous version, and the comment was not resolved so I
decided to wait
until it was before commenting further, be that at IETF LC if so it be.  I did
get
a response about not wanting to push out too many revisions but, perversely,
that is the problem, that the latest revision was pushed out too soon, before
the comments on the previous version had been adequately (IMO) resolved.
Which, in turn, brings us full circle, that insufficient interest was expressed
by the WG in that previous version to get the comments resolved; so should
this progress to RFC or no, is it worth standardising? I have no basis on which
to say.

Tom Petch

> James & Gorry
> TSVWG chairs
>
>
> At 10:07 PM 2/7/2011, James M. Polk wrote:
> >TSVWG
> >
> >I am starting the WGLC for
> >
> >"Stream Control Transmission Protocol (SCTP) Stream Reconfiguration"
> >http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-strrst/
> >
> >this is a 2 week WGLC, ending February 22nd, 2011 or when the chairs
> >feel the WG has reviewed the draft and reached consensus to progress
> >towards the ADs with the goal of becoming a proposed standard (PS) RFC.
> >
> >The chairs require substantive feedback from the WG regarding this
> >draft before consensus can be called.
> >
> >I will be the document shepherd.
> >
> >James
> >TSVWG chair
>


From ka-cheong.poon@oracle.com  Wed Mar 16 02:59:51 2011
Return-Path: <ka-cheong.poon@oracle.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 E90623A68E0 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 02:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.883
X-Spam-Level: 
X-Spam-Status: No, score=-4.883 tagged_above=-999 required=5 tests=[AWL=1.360,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 P6pCI9ioByXx for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 02:59:51 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 1DE5F3A68D8 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 02:59:51 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2GA1FUH003191 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:01:17 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2GA1EH6020455 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:01:15 GMT
Received: from abhmt020.oracle.com (abhmt020.oracle.com [141.146.116.29]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2GA1EDr011840 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 05:01:14 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 16 Mar 2011 03:01:13 -0700
Message-ID: <4D808A66.1060604@oracle.com>
Date: Wed, 16 Mar 2011 18:01:10 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de>	<4D7F3C4B.7090303@oracle.com> <4D7F4016.3080904@oracle.com> <D262443F-0E7E-48BD-86D3-AD8E4B071F54@lakerest.net>
In-Reply-To: <D262443F-0E7E-48BD-86D3-AD8E4B071F54@lakerest.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt358.oracle.com [141.146.40.158]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090206.4D808A6B.0083,ss=1,fgs=0
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: Wed, 16 Mar 2011 09:59:52 -0000

On 03/15/11 08:49 PM, Randy Stewart wrote:

> I can gladly provide some code that runs it.. not all.. since some of
> the stuff was proprietary code of another company.
>
> But I do have an FTP client/server around that use
> the
>
> Add-Stream
> Stream-Reset


Adding streams is a useful feature.  And it is requested
and used by IPFIX.  So I think it is good to be standardized.


> as a convient way to do multi-streaming FTP... when I get
> a chance (I am a bit overwhelemd) at work right now I will see
> if I can put these up for anyone to download.


Can you explain the need to reset SSN in this case?


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Wed Mar 16 03:11:39 2011
Return-Path: <ka-cheong.poon@oracle.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 1488F3A6904 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 03:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.155
X-Spam-Level: 
X-Spam-Status: No, score=-5.155 tagged_above=-999 required=5 tests=[AWL=1.088,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 8BdQcUHDfd+O for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 03:11:37 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id D7A8F3A68EE for <tsvwg@ietf.org>; Wed, 16 Mar 2011 03:11:37 -0700 (PDT)
Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2GAD24R007309 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:13:04 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2GAD1AZ003417 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:13:02 GMT
Received: from abhmt017.oracle.com (abhmt017.oracle.com [141.146.116.26]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2GAD1Ef010749 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 05:13:01 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 16 Mar 2011 03:13:01 -0700
Message-ID: <4D808D2A.9060705@oracle.com>
Date: Wed, 16 Mar 2011 18:12:58 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de>	<4D7F3C4B.7090303@oracle.com> <D891B32A-51F4-401C-A4D6-4DF5FEAF3E91@lakerest.net>
In-Reply-To: <D891B32A-51F4-401C-A4D6-4DF5FEAF3E91@lakerest.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt357.oracle.com [141.146.40.157]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090202.4D808D2E.0152,ss=1,fgs=0
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: Wed, 16 Mar 2011 10:11:39 -0000

On 03/15/11 08:55 PM, Randy Stewart wrote:

> Resetting a stream then lets an app re-use it sort of like
> ftp uses the closing of a connection to indicate that the
> file transfer is complete.... I don't see thats a poor design
> choice.


I guess the question is whether the app layer cannot do
it or the app layer cannot do it any better than in the
transport layer.  To tell the other side that a transfer
is complete in one stream does not require resetting SSN.
For example, HTTP allows sending multiple files and it
does not require resetting the TCP connection.


> So lets see .. what happens when I send more than 65,536 messages
> as I re-use the stream say 10.000 times?
>
> Or do we say no you may only send N messages where N = 65k/number-of-times you wish to
> use it?


I am not sure I understand the example above.  An app can
send as many messages in a stream.  Using the file transfer
example above, an app sends the whole file to the other
side (number of messages does not matter here).  The app
layer receives the whole file and it knows where it ends.
After this, the next file is sent using the same stream.
What is the reason that the SSN needs to be reset to 0 before
sending the next file?


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Wed Mar 16 03:41:39 2011
Return-Path: <ka-cheong.poon@oracle.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 14D773A6939 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 03:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.337
X-Spam-Level: 
X-Spam-Status: No, score=-5.337 tagged_above=-999 required=5 tests=[AWL=0.906,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 0uxfOaeflwgu for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 03:41:38 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 040333A692F for <tsvwg@ietf.org>; Wed, 16 Mar 2011 03:41:37 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2GAh2Ke026076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:43:04 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2GAh1Un025550 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:43:02 GMT
Received: from abhmt014.oracle.com (abhmt014.oracle.com [141.146.116.23]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2GAh1ed016615 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 05:43:01 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 16 Mar 2011 03:43:00 -0700
Message-ID: <4D809432.5050601@oracle.com>
Date: Wed, 16 Mar 2011 18:42:58 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de>
In-Reply-To: <0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Source-IP: acsmt358.oracle.com [141.146.40.158]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090206.4D809436.0117,ss=1,fgs=0
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: Wed, 16 Mar 2011 10:41:39 -0000

On 03/15/11 09:14 PM, Michael Tüxen wrote:

> I agree, the question is where to put which functionality best.
> Ten years ago I though the receiver should not pay attention
> to the SID, SSN or TSN. For whatever reason, these fields
> are exposed to the application writer. So they start looking
> at them.


I always think that exposing TSN and SSN is not a good
idea.  Anyway...


> OK, think about an HTTP proxy which tunnels HTTP to another HTTP proxy.
> You could map incoming TCP connections to one proxy to a stream of
> an SCTP association between the two proxies. When the TCP terminate,
> including being reseted, you want to communicate this to the other end.
> One possibility is to reset the stream. In case of an reset, you
> might even bring PR-SCTP into the game.


As you mentioned above, it is only one possibility.  It
is not the *only* possibility.  Another simple possibility
is to use unordered message as a signal in the app layer
protocol.  When one end detects that the TCP connection
is terminated, send an unordered message to the peer proxy.
After getting this unordered message (which can also include
a lot other info), the peer proxy knows that the TCP connection
being proxied is terminated.  This is not a new idea, telnet
uses TCP urgent pointer to do signaling.  My guess is that
doing this in the app layer protocol requires much less code
than implementing the SSN reset feature in the SCTP layer.


> On the SCTP association, you would only see HTTP traffic.
> Can you do this without Stream Reset. Sure. But you need to define
> an application protocol which implemented the resetting. You need
> a request, a reply, the procedures and you need to multiplex
> this with the HTTP traffic. You can use the PPID for demultiplexing.
> You can do it, but it is much harder for the application writer dealing
> with HTTP.


Right, there are many possibilities.  I think that many of
the possibilities are much simpler to implement than resetting
SSN.  The important point here is not the number of possibilities.
The important point is that it is *not necessary* to do it in
the transport layer.


> Because it is more that doing a subtraction. You need messages
> to signal the reset. You can do this at the application layer
> or at the SCTP layer as indicated above. But for the application
> writer it is simple if it is provided. And it is about the
> management of the streams, an entity belonging to SCTP.


As I mentioned earlier and you agreed above, it is a dangerous
design decision to provide any conceivable services in the
transport layer.  If you are worried about app writers, create a
library to do the simple signaling.  I still don't see the
necessity in providing this service by the transport layer.

BTW, the discussion so far is about resetting SSN.  Does it
mean that resetting TSN has no example use?


>>>> In all the new events, there are "denied" and "failed" events.  It
>>>> is not clear what "failed" means.  The peer does not respond to
>>>> a request and the association times out?  I suggest that it should
>>>> be made clearer.
>>> Have a look at table 3. The peer can indicate that there was an
>>> error or that it denied the request.
>>
>>
>> The result is that the request is not successful, right?
>> So it seems that there should only be one request failure
>> event with the appropriate error cause.  Deny is one of
>> the error cause.
> And how do you know that it was successful? Since the information
> provided in the events are different, we use different events.


As you mentioned, there can be many results in Table 3.  So
the return code, including success, indicates the result of
the request.  Instead of using a flag which only indicates
denied and failed, use a result code to indicate all the
possible results.


> Now I understand what you are saying. I agree completely.
> I changed the flags to SCTP_ENABLE_RESET_IN_STREAM_REQ and so on.
> I guess this addresses your point.
>
> I also removed the text regarding the deprecated SCTP_EVENTS socket
> option.


Thanks.


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Wed Mar 16 03:45:35 2011
Return-Path: <ka-cheong.poon@oracle.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 D97EB3A6939 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 03:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.466
X-Spam-Level: 
X-Spam-Status: No, score=-5.466 tagged_above=-999 required=5 tests=[AWL=0.777,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 l4YRIKLw47dT for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 03:45:35 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 288A73A6947 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 03:45:35 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2GAkxu6007217 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:47:00 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2GAkwlv005322 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:46:59 GMT
Received: from abhmt014.oracle.com (abhmt014.oracle.com [141.146.116.23]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2GAkwgY008560 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 05:46:58 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 16 Mar 2011 03:46:58 -0700
Message-ID: <4D80951F.90405@oracle.com>
Date: Wed, 16 Mar 2011 18:46:55 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de>	<4D7F3C4B.7090303@oracle.com>	<0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de> <D67FB95D-0672-4CF2-BC0E-8A3D1749ADB5@lakerest.net>
In-Reply-To: <D67FB95D-0672-4CF2-BC0E-8A3D1749ADB5@lakerest.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt357.oracle.com [141.146.40.157]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090201.4D809523.0055,ss=1,fgs=0
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: Wed, 16 Mar 2011 10:45:35 -0000

On 03/15/11 10:06 PM, Randy Stewart wrote:

> And don't forget that streams are a very narrow sequence space. Doing
> a subtraction won't work if the app needs to send a fairly large number
> of messages and wants to "reuse the stream" multiple times. It becomes
> a LOT more information that needs to be maintained somehow...


Isn't it true that regardless how many times a stream is
reset, only 1 number needs to be remembered?  My question
is on the necessity of a transport layer protocol mechanism
to achieve something which can be done at app layer easily.


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Wed Mar 16 03:49:02 2011
Return-Path: <ka-cheong.poon@oracle.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 499633A690B for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 03:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.563
X-Spam-Level: 
X-Spam-Status: No, score=-5.563 tagged_above=-999 required=5 tests=[AWL=0.680,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 yaG5KyLUB8yh for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 03:49:01 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 8A2ED3A68C2 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 03:49:01 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2GAoQ62015689 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:50:27 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2GAoP74019218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:50:26 GMT
Received: from abhmt003.oracle.com (abhmt003.oracle.com [141.146.116.12]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2GAoPjd022750 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 05:50:25 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 16 Mar 2011 03:50:25 -0700
Message-ID: <4D8095EE.3060706@oracle.com>
Date: Wed, 16 Mar 2011 18:50:22 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <D8826A52-1B36-404B-8A60-FEC7DC90EDB4@lurchi.franken.de>
In-Reply-To: <D8826A52-1B36-404B-8A60-FEC7DC90EDB4@lurchi.franken.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Source-IP: acsmt358.oracle.com [141.146.40.158]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090207.4D8095F2.00B4,ss=1,fgs=0
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: Wed, 16 Mar 2011 10:49:02 -0000

On 03/15/11 10:49 PM, Michael Tüxen wrote:

> I change "STREAM RESET chunk" to "RE-CONFIG chunk".
> However, we still have the generic
>
> Stream Reset Parameter
> Stream Reset Request Parameter
> Stream Reset Response Parameter
>
> Shouldn't these also be
>
> Re-configuration Parameter
> Re-configuration Request Parameter
> Re-configuration Response Parameter
>
> What do you think?


I think the original names are fine since they are
parameter names which indicate which re-configuration
is to be performed.


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Wed Mar 16 03:54:38 2011
Return-Path: <ka-cheong.poon@oracle.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 5F3393A6939 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 03:54:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.339
X-Spam-Level: 
X-Spam-Status: No, score=-5.339 tagged_above=-999 required=5 tests=[AWL=0.304,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4, 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 1S0yHkZqFfku for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 03:54:37 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 9F34D3A6936 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 03:54:37 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2GAu2HF003850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:56:03 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2GAu1gq003612 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:56:01 GMT
Received: from abhmt001.oracle.com (abhmt001.oracle.com [141.146.116.10]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2GAu02L027198 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 05:56:01 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 16 Mar 2011 03:56:00 -0700
Message-ID: <4D80973E.5040002@oracle.com>
Date: Wed, 16 Mar 2011 18:55:58 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net>
In-Reply-To: <00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt358.oracle.com [141.146.40.158]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090206.4D809742.004D,ss=1,fgs=0
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: Wed, 16 Mar 2011 10:54:38 -0000

On 03/16/11 04:31 PM, t.petch wrote:

> I am sitting on my hands because I did not consider the I-D ready for last call
> but also, I do not have a view as to whether or not this I-D will be
> implemented,
> whether or not the additional function is worth standardising - I simply do not
> have the contacts to make a judgement on this.


One question, do you think that the stream addition mechanism is
OK?  Suppose the draft is only about that mechanism, do you think
that it is worthwhile to be standardized?




-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From Michael.Tuexen@lurchi.franken.de  Wed Mar 16 05:03:03 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 081C23A6983 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 05:03:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[AWL=0.740,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 y2ePP6a27xTf for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 05:03:02 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id 3A6713A6958 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 05:03:00 -0700 (PDT)
Received: from [192.168.1.113] (p5481B388.dip.t-dialin.net [84.129.179.136]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id E8DAE1C0C0BCC; Wed, 16 Mar 2011 13:04:24 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4D8095EE.3060706@oracle.com>
Date: Wed, 16 Mar 2011 13:04:24 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <79C91FD0-57BC-428E-A075-B580B4A3C57D@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <D8826A52-1B36-404B-8A60-FEC7DC90EDB4@lurchi.franken.de> <4D8095EE.3060706@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
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: Wed, 16 Mar 2011 12:03:03 -0000

On Mar 16, 2011, at 11:50 AM, Kacheong Poon wrote:

> On 03/15/11 10:49 PM, Michael T=FCxen wrote:
>=20
>> I change "STREAM RESET chunk" to "RE-CONFIG chunk".
>> However, we still have the generic
>>=20
>> Stream Reset Parameter
>> Stream Reset Request Parameter
>> Stream Reset Response Parameter
>>=20
>> Shouldn't these also be
>>=20
>> Re-configuration Parameter
>> Re-configuration Request Parameter
>> Re-configuration Response Parameter
>>=20
>> What do you think?
>=20
>=20
> I think the original names are fine since they are
> parameter names which indicate which re-configuration
> is to be performed.
Hi Kacheong,

not sure you got the point I wanted to make. The text reads now (in =
CVS):

3.1.  RE-CONFIG Chunk

   This document adds one new chunk type to SCTP.  The chunk has the
   following format:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Type =3D 0x82   |  Chunk Flags  |      Chunk Length             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   \                                                               \
   /                    Stream Reset Parameter                     /
   \                                                               \
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   \                                                               \
   /                Stream Reset Parameter (optional)              /
   \                                                               \
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

...
   Stream Reset Parameter
      This field holds a Stream Reset Request Parameter or a Stream
      Reset Response Parameter.

   Note that each RE-CONFIG chunk holds at least one parameter and at
   most two parameters.  Only the following combinations are allowed:

   1.  Outgoing SSN Reset Request Parameter.

   2.  Incoming SSN Reset Request Parameter.

   3.  Outgoing SSN Reset Request Parameter, Incoming SSN Reset Request
       Parameter.

   4.  SSN/TSN Reset Request Parameter.

   5.  Add Outgoing Streams Request Parameter.

   6.  Stream Reset Response Parameter.

   7.  Stream Reset Response Parameter, Outgoing SSN Reset Request
       Parameter.

   8.  Stream Reset Response Parameter, Stream Reset Response Parameter.


For me it reads kind of strange that a RE-CONFIG chunk contains
one or two Stream Reset Parameters, which might be a Stream Reset =
Response Parameter
or a  Add Outgoing Streams Request Parameter, both not doing anything
regarding resetting. The other names are appropriate.

I thought that something like the following would be more appropriate:

3.1.  RE-CONFIG Chunk

   This document adds one new chunk type to SCTP.  The chunk has the
   following format:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Type =3D 0x82   |  Chunk Flags  |      Chunk Length             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   \                                                               \
   /                  Re-configuration Parameter                   /
   \                                                               \
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   \                                                               \
   /            Re-configuration Parameter (optional)              /
   \                                                               \
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

...
   Re-configuration Parameter
      This field holds a Re-configuration Request Parameter or a
      Re-configuration Response Parameter.

   Note that each RE-CONFIG chunk holds at least one parameter and at
   most two parameters.  Only the following combinations are allowed:

   1.  Outgoing SSN Reset Request Parameter.

   2.  Incoming SSN Reset Request Parameter.

   3.  Outgoing SSN Reset Request Parameter, Incoming SSN Reset Request
       Parameter.

   4.  SSN/TSN Reset Request Parameter.

   5.  Add Outgoing Streams Request Parameter.

   6.  Re-configuration Response Parameter.

   7.  Re-configuration Response Parameter, Outgoing SSN Reset Request
       Parameter.

   8.  Re-configuration Response Parameter, Re-configuration Response =
Parameter.

If you find the current wording appropriate, I'm happy to leave it...

Best regards
Michael
>=20
>=20
> --=20
>=20
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
>=20


From Michael.Tuexen@lurchi.franken.de  Wed Mar 16 05:31:51 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 E820C3A6977 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 05:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.253
X-Spam-Level: 
X-Spam-Status: No, score=-1.253 tagged_above=-999 required=5 tests=[AWL=0.690,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 UVyzMX5Ywwvy for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 05:31:47 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id B49393A68EA for <tsvwg@ietf.org>; Wed, 16 Mar 2011 05:31:38 -0700 (PDT)
Received: from [192.168.1.113] (p5481B388.dip.t-dialin.net [84.129.179.136]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 77E471C0C0BCC; Wed, 16 Mar 2011 13:33:03 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4D809432.5050601@oracle.com>
Date: Wed, 16 Mar 2011 13:32:58 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3AF1842-07FB-4F06-8501-B2EDB1309438@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de> <4D809432.5050601@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
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: Wed, 16 Mar 2011 12:31:52 -0000

On Mar 16, 2011, at 11:42 AM, Kacheong Poon wrote:

> On 03/15/11 09:14 PM, Michael T=FCxen wrote:
>=20
>> I agree, the question is where to put which functionality best.
>> Ten years ago I though the receiver should not pay attention
>> to the SID, SSN or TSN. For whatever reason, these fields
>> are exposed to the application writer. So they start looking
>> at them.
>=20
>=20
> I always think that exposing TSN and SSN is not a good
> idea.  Anyway...
>=20
>=20
>> OK, think about an HTTP proxy which tunnels HTTP to another HTTP =
proxy.
>> You could map incoming TCP connections to one proxy to a stream of
>> an SCTP association between the two proxies. When the TCP terminate,
>> including being reseted, you want to communicate this to the other =
end.
>> One possibility is to reset the stream. In case of an reset, you
>> might even bring PR-SCTP into the game.
>=20
>=20
> As you mentioned above, it is only one possibility.  It
> is not the *only* possibility.  Another simple possibility
> is to use unordered message as a signal in the app layer
> protocol.  When one end detects that the TCP connection
> is terminated, send an unordered message to the peer proxy.
> After getting this unordered message (which can also include
> a lot other info), the peer proxy knows that the TCP connection
> being proxied is terminated.  This is not a new idea, telnet
> uses TCP urgent pointer to do signaling.  My guess is that
> doing this in the app layer protocol requires much less code
> than implementing the SSN reset feature in the SCTP layer.
But the above is not sufficient. Resetting a stream does not
only reset the counter but also=20
* signals that it is requested
* acknowledges that is has been performed

So if you want to implement it at the application layer,
you need to define at least two application layer messages
and the appropriate procedures. So you need to extend the
application layer and get the procedures right.
So, yes it can be done at the application layer, but
* each application protocol must re-implement the same mechanism.
* you need to extend each application protocol.
Doing it at the transport layer, requires the mechanism
only to be implemented once and no change of the application
protocol.
>=20
>=20
>> On the SCTP association, you would only see HTTP traffic.
>> Can you do this without Stream Reset. Sure. But you need to define
>> an application protocol which implemented the resetting. You need
>> a request, a reply, the procedures and you need to multiplex
>> this with the HTTP traffic. You can use the PPID for demultiplexing.
>> You can do it, but it is much harder for the application writer =
dealing
>> with HTTP.
>=20
>=20
> Right, there are many possibilities.  I think that many of
> the possibilities are much simpler to implement than resetting
> SSN.  The important point here is not the number of possibilities.
> The important point is that it is *not necessary* to do it in
> the transport layer.
I think the question is not if it is necessary, but which layer
is the most appropriate.
As with my example from two days or so ago, it is *not necessary*
to do reordering at the transport layer. We could have also
left that feature for the application and only support unordered
delivery in the transport layer. But we didn't (which is good).

So I think the question is: What does provide a stream for
the application layer.
* Just a static channel which provides in-sequence delivery
  This might have been the original intention (from SIGTRAN),
  but this does not require exposing TSN/SSN.

I think people started looking at TSN/SSN, since we are
exposing it and, when using outside of the SIGTRAN applications,
they want to have something like
* A dynamic channel which provides in-sequence delivery.
Here dynamic means it can be added / removed / reused.

Removing is hard, so that is why we left it out. I also argued
at some time, the you do not need to add streams, just start
the association with enough streams. But app writers see it
differently.

So being able to add and reset streams seems a good compromise
for me. It can be added relatively simple to SCTP and it
provides almost all the app writers need.
>=20
>=20
>> Because it is more that doing a subtraction. You need messages
>> to signal the reset. You can do this at the application layer
>> or at the SCTP layer as indicated above. But for the application
>> writer it is simple if it is provided. And it is about the
>> management of the streams, an entity belonging to SCTP.
>=20
>=20
> As I mentioned earlier and you agreed above, it is a dangerous
> design decision to provide any conceivable services in the
> transport layer.  If you are worried about app writers, create a
> library to do the simple signaling.  I still don't see the
> necessity in providing this service by the transport layer.
As said above, you can put it at either layer. We just seem
to disagree, where the more appropriate layer is...
>=20
> BTW, the discussion so far is about resetting SSN.  Does it
> mean that resetting TSN has no example use?
>=20
>=20
>>>>> In all the new events, there are "denied" and "failed" events.  It
>>>>> is not clear what "failed" means.  The peer does not respond to
>>>>> a request and the association times out?  I suggest that it should
>>>>> be made clearer.
>>>> Have a look at table 3. The peer can indicate that there was an
>>>> error or that it denied the request.
>>>=20
>>>=20
>>> The result is that the request is not successful, right?
>>> So it seems that there should only be one request failure
>>> event with the appropriate error cause.  Deny is one of
>>> the error cause.
>> And how do you know that it was successful? Since the information
>> provided in the events are different, we use different events.
>=20
>=20
> As you mentioned, there can be many results in Table 3.  So
> the return code, including success, indicates the result of
> the request.  Instead of using a flag which only indicates
> denied and failed, use a result code to indicate all the
> possible results.
Well, I thought for the application it is only important
to know if the request was successful, denied or failed.
It also uses a field which is there anyway.

But if you prefer, we can add a field which contains the
return code, which was on the wire. Not sure if it really
helps.=20

Best regards
Michael
>=20
>=20
>> Now I understand what you are saying. I agree completely.
>> I changed the flags to SCTP_ENABLE_RESET_IN_STREAM_REQ and so on.
>> I guess this addresses your point.
>>=20
>> I also removed the text regarding the deprecated SCTP_EVENTS socket
>> option.
>=20
>=20
> Thanks.
>=20
>=20
> --=20
>=20
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
>=20


From Michael.Tuexen@lurchi.franken.de  Wed Mar 16 05:32:45 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 159533A6962 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 05:32:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.296
X-Spam-Level: 
X-Spam-Status: No, score=-1.296 tagged_above=-999 required=5 tests=[AWL=0.647,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 5f7PkCs-SVCC for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 05:32:44 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id 3B0CD3A68EA for <tsvwg@ietf.org>; Wed, 16 Mar 2011 05:32:44 -0700 (PDT)
Received: from [192.168.1.113] (p5481B388.dip.t-dialin.net [84.129.179.136]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id D528C1C0C0BCC; Wed, 16 Mar 2011 13:34:09 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4D80951F.90405@oracle.com>
Date: Wed, 16 Mar 2011 13:34:09 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <89B6B40B-8F73-43DD-A023-8CF025184FF3@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de>	<4D7F3C4B.7090303@oracle.com>	<0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de> <D67FB95D-0672-4CF2-BC0E-8A3D1749ADB5@lakerest.net> <4D80951F.90405@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
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: Wed, 16 Mar 2011 12:32:45 -0000

On Mar 16, 2011, at 11:46 AM, Kacheong Poon wrote:

> On 03/15/11 10:06 PM, Randy Stewart wrote:
> 
>> And don't forget that streams are a very narrow sequence space. Doing
>> a subtraction won't work if the app needs to send a fairly large number
>> of messages and wants to "reuse the stream" multiple times. It becomes
>> a LOT more information that needs to be maintained somehow...
> 
> 
> Isn't it true that regardless how many times a stream is
> reset, only 1 number needs to be remembered?  My question
> is on the necessity of a transport layer protocol mechanism
> to achieve something which can be done at app layer easily.
As indicated in my earlier mail, it is not only remembering
a sequence number.

Best regards
Michael
> 
> 
> -- 
> 
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
> 


From randall@lakerest.net  Wed Mar 16 07:04:18 2011
Return-Path: <randall@lakerest.net>
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 8DD393A6857 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 07:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.643
X-Spam-Level: 
X-Spam-Status: No, score=-1.643 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 O-K2g2hmUDI3 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 07:04:17 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 6ED4E3A699E for <tsvwg@ietf.org>; Wed, 16 Mar 2011 07:04:15 -0700 (PDT)
Received: from [10.193.34.52] ([12.133.183.34]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2GE5MsS085965 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 16 Mar 2011 10:05:26 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
X-Priority: 3
In-Reply-To: <00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net>
Date: Wed, 16 Mar 2011 10:05:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <29AEBA37-6157-44E9-8FD7-B44023DF6CD7@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net>
To: "t.petch" <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.1082)
Cc: "James M. Polk" <jmpolk@cisco.com>, tsvwg <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: Wed, 16 Mar 2011 14:04:18 -0000

On Mar 16, 2011, at 4:31 AM, t.petch wrote:

> ----- Original Message -----
> From: "James M. Polk" <jmpolk@cisco.com>
> To: "tsvwg" <tsvwg@ietf.org>
> Sent: Sunday, March 13, 2011 9:48 PM
>=20
>> TSVWG
>>=20
>> The WG chairs have determined the WGLC for our SCTP Stream
>> Reconfiguration ID continues (i.e., it has not concluded at the 2
>> week window) due to lack of feedback to the list. No one has
>> commented in a review format that they believe this ID should
>> progress. No one has even sent a note merely saying this ID in its
>> present form is good to go. That lack of any feedback is troubling
>> and could be a sign of a lack of interest in this ID.
>>=20
>> The WG chairs like the idea of (and within) this draft, but we need
>> transport experts to tell us this, and if the ID in its present form
>> is good enough to implement to without those implementations having
>> errors or causing bad behavior in SCTP because of how the ID is
>> written (focusing mostly on the instructions to implementers in the =
ID).
>>=20
>> We chairs want folks to show or assert they have reviewed this ID and
>> give feedback to the list (and not unicast to the chairs). This ID
>> cannot progress without that feedback.
>=20
> I am sitting on my hands because I did not consider the I-D ready for =
last call
> but also, I do not have a view as to whether or not this I-D will be
> implemented,


Can't say on other implementations but it is in FreeBSD ;-)

> whether or not the additional function is worth standardising - I =
simply do not
> have the contacts to make a judgement on this.
>=20
> I did comment on a previous version, and the comment was not resolved =
so I
> decided to wait
> until it was before commenting further, be that at IETF LC if so it =
be.  I did
> get
> a response about not wanting to push out too many revisions but, =
perversely,


Tom, I did too respond to your comment.. and the update was posted on =
the mailing
list... Did you not receive the email (sometimes my emails do not get =
through it
would appear)..  I can wander back on the mailing list archives and find =
it ... let me see:

Here it is from Feb 9th:
=
**************************************************************************=
*************
Tom:

Just to let you know I did NOT forget about this... Here is the text =
that is
waiting in the xml for the -10 revision:
***********************************************************
  When a peer endpoint requests a Incoming SSN Reset Request it is
  possible that the local endpoint has just sent an Outgoing SSN Reset
  Request on the same stream and has not yet received a response.  In
  such a case the local endpoint MUST do the following:

  1) If the stream reset overlaps the outstanding request completely
     respond to the requestor with an acknowledgment indicating that
     there was 'Nothing to do'.

  2) Otherwise process the stream reset request normally responding to
     the requestor with an acknowledgment.

  It is also possible that the Incoming request will arrive after the
  Outgoing SSN Reset Request just completed.  In such a case the local
  endpoint MUST do the following:

  1) If the stream reset overlaps the outstanding request completely
     all of the streams being requested will be already set to 0.  If
     so, the local endpoint SHOULD send back a Stream Reset Response
     with the success code "Nothing to do".

  2) Otherwise process the stream reset request normally responding to
     the requestor an acknowledgment.

  Note that in either race condition the local endpoint could
  optionally also perform the reset.  This would result in streams that
  are already at sequence 0 being reset again to 0 which would cause no
  harm to the application but will add an extra message to the network.

  Note also that in any of the race conditions listed above the
  receiver MUST NOT send more than one response.  In other words two
  responses MUST NOT be sent for the same request.

*******************************************************************

When we get any other comments after LC I will issue the updated draft =
with the above...

If you would like further changes or this does not satisfy your comments =
below
let me know.. you can even send suggested text :-)

Best wishes

R
On Jan 15, 2011, at 6:49 AM, t.petch wrote:

> I like the change to 5.2.3 but think that it needs to go further.
>=20
> -08 split out two cases,
>=20
> Incoming SSN Reset Request received but no response yet to the =
Outgoing request
> Incoming SSN Reset Request received after response to the Outgoing =
request
>=20
> assuming that the Incoming and Outgoing requests have overlapping =
stream
> numbers.
>=20
> -09 subdivides the first case into overlaps completely and overlaps =
partially
> but
> I think that the second case is also in need of subdivision in the =
same way.
>=20
> And, a point of clarification, in any of the four cases, is it =
required to send
> just
> the one response, ie you cannot send two responses in the partial =
overlap case,
> one saying no-op and the will do (or won't do!)?
>=20
>=20
> Tom Petch
>=20
=
**************************************************************************=
**************

You never replied to that so I had assumed you were happy with the =
changes.. if not
I would be more than glad to hear your suggested changes...


R


> that is the problem, that the latest revision was pushed out too soon, =
before
> the comments on the previous version had been adequately (IMO) =
resolved.
> Which, in turn, brings us full circle, that insufficient interest was =
expressed
> by the WG in that previous version to get the comments resolved; so =
should
> this progress to RFC or no, is it worth standardising? I have no basis =
on which
> to say.
>=20
> Tom Petch
>=20
>> James & Gorry
>> TSVWG chairs
>>=20
>>=20
>> At 10:07 PM 2/7/2011, James M. Polk wrote:
>>> TSVWG
>>>=20
>>> I am starting the WGLC for
>>>=20
>>> "Stream Control Transmission Protocol (SCTP) Stream Reconfiguration"
>>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-strrst/
>>>=20
>>> this is a 2 week WGLC, ending February 22nd, 2011 or when the chairs
>>> feel the WG has reviewed the draft and reached consensus to progress
>>> towards the ADs with the goal of becoming a proposed standard (PS) =
RFC.
>>>=20
>>> The chairs require substantive feedback from the WG regarding this
>>> draft before consensus can be called.
>>>=20
>>> I will be the document shepherd.
>>>=20
>>> James
>>> TSVWG chair
>>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From randall@lakerest.net  Wed Mar 16 07:06:53 2011
Return-Path: <randall@lakerest.net>
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 09B103A69A3 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 07:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.943
X-Spam-Level: 
X-Spam-Status: No, score=-1.943 tagged_above=-999 required=5 tests=[AWL=0.300,  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 6HIxuu7CtIIO for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 07:06:52 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 9FD933A69A1 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 07:06:51 -0700 (PDT)
Received: from [10.193.34.52] ([12.133.183.34]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2GE8CKs086089 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 16 Mar 2011 10:08:15 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <4D808D2A.9060705@oracle.com>
Date: Wed, 16 Mar 2011 10:07:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FFC0BCC4-9168-4E18-A718-7FF3DBACB24B@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de>	<4D7F3C4B.7090303@oracle.com> <D891B32A-51F4-401C-A4D6-4DF5FEAF3E91@lakerest.net> <4D808D2A.9060705@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
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: Wed, 16 Mar 2011 14:06:53 -0000

On Mar 16, 2011, at 6:12 AM, Kacheong Poon wrote:

> On 03/15/11 08:55 PM, Randy Stewart wrote:
>=20
>> Resetting a stream then lets an app re-use it sort of like
>> ftp uses the closing of a connection to indicate that the
>> file transfer is complete.... I don't see thats a poor design
>> choice.
>=20
>=20
> I guess the question is whether the app layer cannot do
> it or the app layer cannot do it any better than in the
> transport layer.  To tell the other side that a transfer
> is complete in one stream does not require resetting SSN.
> For example, HTTP allows sending multiple files and it
> does not require resetting the TCP connection.


So you use a whole transport connection setup has a mechanism to
tell that something is complete. This is the same thing as ftp and
I think resetting a stream is a LOT less heavy weight....

>=20
>=20
>> So lets see .. what happens when I send more than 65,536 messages
>> as I re-use the stream say 10.000 times?
>>=20
>> Or do we say no you may only send N messages where N =3D =
65k/number-of-times you wish to
>> use it?
>=20
>=20
> I am not sure I understand the example above.  An app can
> send as many messages in a stream.  Using the file transfer
> example above, an app sends the whole file to the other
> side (number of messages does not matter here).  The app
> layer receives the whole file and it knows where it ends.
> After this, the next file is sent using the same stream.
> What is the reason that the SSN needs to be reset to 0 before
> sending the next file?

I can easily know that I close the file and when the stream
reset arrives. This tells me the transfer is done the same way
in ftp you use the closing of the connection as an indication that
the transfer is complete.

R



>=20
>=20
> --=20
>=20
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
>=20

-----
Randall Stewart
randall@lakerest.net





From randall@lakerest.net  Wed Mar 16 07:12:55 2011
Return-Path: <randall@lakerest.net>
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 7BDCC3A68CC for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 07:12:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level: 
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 uk1XSEFqUipG for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 07:12:54 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id A61703A69A9 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 07:12:51 -0700 (PDT)
Received: from [10.193.34.52] ([12.133.183.34]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2GEEDVX086398 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 16 Mar 2011 10:14:15 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <F3AF1842-07FB-4F06-8501-B2EDB1309438@lurchi.franken.de>
Date: Wed, 16 Mar 2011 10:14:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5FDD193A-B09F-400B-8EC2-931BF6AECF18@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de> <4D809432.5050601@oracle.com> <F3AF1842-07FB-4F06-8501-B2EDB1309438@lurchi.franken.de>
To: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.1082)
Cc: Kacheong Poon <ka-cheong.poon@oracle.com>, 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: Wed, 16 Mar 2011 14:12:55 -0000

One comment below...

On Mar 16, 2011, at 8:32 AM, Michael T=FCxen wrote:

> On Mar 16, 2011, at 11:42 AM, Kacheong Poon wrote:
>=20
>> On 03/15/11 09:14 PM, Michael T=FCxen wrote:
>>=20
>>> I agree, the question is where to put which functionality best.
>>> Ten years ago I though the receiver should not pay attention
>>> to the SID, SSN or TSN. For whatever reason, these fields
>>> are exposed to the application writer. So they start looking
>>> at them.
>>=20
>>=20
>> I always think that exposing TSN and SSN is not a good
>> idea.  Anyway...
>>=20
>>=20
>>> OK, think about an HTTP proxy which tunnels HTTP to another HTTP =
proxy.
>>> You could map incoming TCP connections to one proxy to a stream of
>>> an SCTP association between the two proxies. When the TCP terminate,
>>> including being reseted, you want to communicate this to the other =
end.
>>> One possibility is to reset the stream. In case of an reset, you
>>> might even bring PR-SCTP into the game.
>>=20
>>=20
>> As you mentioned above, it is only one possibility.  It
>> is not the *only* possibility.  Another simple possibility
>> is to use unordered message as a signal in the app layer
>> protocol.  When one end detects that the TCP connection
>> is terminated, send an unordered message to the peer proxy.
>> After getting this unordered message (which can also include
>> a lot other info), the peer proxy knows that the TCP connection
>> being proxied is terminated.  This is not a new idea, telnet
>> uses TCP urgent pointer to do signaling.  My guess is that
>> doing this in the app layer protocol requires much less code
>> than implementing the SSN reset feature in the SCTP layer.
> But the above is not sufficient. Resetting a stream does not
> only reset the counter but also=20
> * signals that it is requested
> * acknowledges that is has been performed
>=20
> So if you want to implement it at the application layer,
> you need to define at least two application layer messages
> and the appropriate procedures. So you need to extend the
> application layer and get the procedures right.
> So, yes it can be done at the application layer, but
> * each application protocol must re-implement the same mechanism.
> * you need to extend each application protocol.
> Doing it at the transport layer, requires the mechanism
> only to be implemented once and no change of the application
> protocol.
>>=20
>>=20
>>> On the SCTP association, you would only see HTTP traffic.
>>> Can you do this without Stream Reset. Sure. But you need to define
>>> an application protocol which implemented the resetting. You need
>>> a request, a reply, the procedures and you need to multiplex
>>> this with the HTTP traffic. You can use the PPID for demultiplexing.
>>> You can do it, but it is much harder for the application writer =
dealing
>>> with HTTP.
>>=20
>>=20
>> Right, there are many possibilities.  I think that many of
>> the possibilities are much simpler to implement than resetting
>> SSN.  The important point here is not the number of possibilities.
>> The important point is that it is *not necessary* to do it in
>> the transport layer.
> I think the question is not if it is necessary, but which layer
> is the most appropriate.
> As with my example from two days or so ago, it is *not necessary*
> to do reordering at the transport layer. We could have also
> left that feature for the application and only support unordered
> delivery in the transport layer. But we didn't (which is good).
>=20
> So I think the question is: What does provide a stream for
> the application layer.
> * Just a static channel which provides in-sequence delivery
>  This might have been the original intention (from SIGTRAN),
>  but this does not require exposing TSN/SSN.
>=20
> I think people started looking at TSN/SSN, since we are
> exposing it and, when using outside of the SIGTRAN applications,
> they want to have something like
> * A dynamic channel which provides in-sequence delivery.
> Here dynamic means it can be added / removed / reused.
>=20
> Removing is hard, so that is why we left it out. I also argued
> at some time, the you do not need to add streams, just start
> the association with enough streams. But app writers see it
> differently.
>=20
> So being able to add and reset streams seems a good compromise
> for me. It can be added relatively simple to SCTP and it
> provides almost all the app writers need.


Once you add a mechanism to add-a-stream, making using it
to do these functionalities as well makes sense. You already
have to define the mechanism.. why make the app redefine a similar
mechanism....



>>=20
>>=20
>>> Because it is more that doing a subtraction. You need messages
>>> to signal the reset. You can do this at the application layer
>>> or at the SCTP layer as indicated above. But for the application
>>> writer it is simple if it is provided. And it is about the
>>> management of the streams, an entity belonging to SCTP.
>>=20
>>=20
>> As I mentioned earlier and you agreed above, it is a dangerous
>> design decision to provide any conceivable services in the
>> transport layer.  If you are worried about app writers, create a
>> library to do the simple signaling.  I still don't see the
>> necessity in providing this service by the transport layer.
> As said above, you can put it at either layer. We just seem
> to disagree, where the more appropriate layer is...


Yep... I think this is a plain layer disagreement ..

There is one other thing that can be done with this mechanism. If one
were to combine AUTH+DYNAMIC_ADDRESSES+RECONFIG.. one could pretty
easily move a transport connection from one machine to another without
having to track sequence number space to closely...

Just a thought

R

>>=20
>> BTW, the discussion so far is about resetting SSN.  Does it
>> mean that resetting TSN has no example use?
>>=20
>>=20
>>>>>> In all the new events, there are "denied" and "failed" events.  =
It
>>>>>> is not clear what "failed" means.  The peer does not respond to
>>>>>> a request and the association times out?  I suggest that it =
should
>>>>>> be made clearer.
>>>>> Have a look at table 3. The peer can indicate that there was an
>>>>> error or that it denied the request.
>>>>=20
>>>>=20
>>>> The result is that the request is not successful, right?
>>>> So it seems that there should only be one request failure
>>>> event with the appropriate error cause.  Deny is one of
>>>> the error cause.
>>> And how do you know that it was successful? Since the information
>>> provided in the events are different, we use different events.
>>=20
>>=20
>> As you mentioned, there can be many results in Table 3.  So
>> the return code, including success, indicates the result of
>> the request.  Instead of using a flag which only indicates
>> denied and failed, use a result code to indicate all the
>> possible results.
> Well, I thought for the application it is only important
> to know if the request was successful, denied or failed.
> It also uses a field which is there anyway.
>=20
> But if you prefer, we can add a field which contains the
> return code, which was on the wire. Not sure if it really
> helps.=20
>=20
> Best regards
> Michael
>>=20
>>=20
>>> Now I understand what you are saying. I agree completely.
>>> I changed the flags to SCTP_ENABLE_RESET_IN_STREAM_REQ and so on.
>>> I guess this addresses your point.
>>>=20
>>> I also removed the text regarding the deprecated SCTP_EVENTS socket
>>> option.
>>=20
>>=20
>> Thanks.
>>=20
>>=20
>> --=20
>>=20
>> 					K. Poon.
>> 					ka-cheong.poon@oracle.com
>>=20
>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From ietfc@btconnect.com  Wed Mar 16 08:43:04 2011
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 955A43A69B9 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 08:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.984
X-Spam-Level: 
X-Spam-Status: No, score=-1.984 tagged_above=-999 required=5 tests=[AWL=-0.041, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 AilgA7jX1-Qx for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 08:43:03 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr09.btconnect.com [213.123.20.127]) by core3.amsl.com (Postfix) with ESMTP id 7B86E3A6966 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 08:43:02 -0700 (PDT)
Received: from host217-44-145-106.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.106]) by c2bthomr09.btconnect.com with SMTP id CEF99615; Wed, 16 Mar 2011 15:44:23 +0000 (GMT)
Message-ID: <009501cbe3e7$f8fd6e20$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>, "Kacheong Poon" <ka-cheong.poon@oracle.com>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com><201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com><4D7DE97D.6010609@oracle.com><14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de><4D7F3C4B.7090303@oracle.com> <D8826A52-1B36-404B-8A60-FEC7DC90EDB4@lurchi.franken.de>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Date: Wed, 16 Mar 2011 15:24:46 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4D80DAC9.00EF, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020D.4D80DAD9.01DB,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, 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: Wed, 16 Mar 2011 15:43:04 -0000

----- Original Message -----
From: "Michael Tüxen" <Michael.Tuexen@lurchi.franken.de>
To: "Kacheong Poon" <ka-cheong.poon@oracle.com>
Cc: <tsvwg@ietf.org>
Sent: Tuesday, March 15, 2011 3:49 PM

> Hi Kacheong,
>
> one additional question:
>
>
> >> I agree the naming could be improved.
> >> What about:
> >> * Re-configuration Chunk
> >> * Reset Chunk
> >
> >
> > Re-configuration chunk is a better choice.
> >
> >
>
> I change "STREAM RESET chunk" to "RE-CONFIG chunk".
> However, we still have the generic
>
> Stream Reset Parameter
> Stream Reset Request Parameter
> Stream Reset Response Parameter
>
> Shouldn't these also be
>
> Re-configuration Parameter
> Re-configuration Request Parameter
> Re-configuration Response Parameter
>
> What do you think?

I think that you will spend the next five iterations of this I-D,
into AUTH48 and beyond, finding instances of Reset that
you have missed and omitted to change.

ie forget it, in toto.

Tom Petch

> Best regards
> Michael
>


From ietfc@btconnect.com  Wed Mar 16 08:43:12 2011
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 C173C3A69C6 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 08:43:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.014
X-Spam-Level: 
X-Spam-Status: No, score=0.014 tagged_above=-999 required=5 tests=[AWL=-2.031,  BAYES_00=-2.599, FRT_STOCK2=3.988, MIME_8BIT_HEADER=0.3, 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 47Sg0DJaNrnE for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 08:43:11 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr09.btconnect.com [213.123.20.127]) by core3.amsl.com (Postfix) with ESMTP id E0E153A69BB for <tsvwg@ietf.org>; Wed, 16 Mar 2011 08:43:10 -0700 (PDT)
Received: from host217-44-145-106.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.106]) by c2bthomr09.btconnect.com with SMTP id CEF99605; Wed, 16 Mar 2011 15:44:22 +0000 (GMT)
Message-ID: <009401cbe3e7$f8a1e0a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Peter Lei" <peter.lei@ieee.org>, "Randy Stewart" <randall@lakerest.net>,  =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de><51679D6F-1789-46BE-B1E5-22AE064B27E2@lakerest.net> <4D7F941C.9050400@ieee.org>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Date: Wed, 16 Mar 2011 15:21:55 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4D80DAC9.00EF, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0205.4D80DAD9.01F7,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: Kacheong Poon <ka-cheong.poon@oracle.com>, 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: Wed, 16 Mar 2011 15:43:12 -0000

----- Original Message -----
From: "Peter Lei" <peter.lei@ieee.org>
To: "Randy Stewart" <randall@lakerest.net>; "Michael Tüxen"
<Michael.Tuexen@lurchi.franken.de>
Cc: "Kacheong Poon" <ka-cheong.poon@oracle.com>; <tsvwg@ietf.org>
Sent: Tuesday, March 15, 2011 5:30 PM
> Comments inline:
>
> On 3/14/11 11:06 AM, Randy Stewart wrote:
> > In-line..
> >
> > On Mar 14, 2011, at 10:12 AM, Michael Tüxen wrote:
> >
> >> Hi Kacheong,
> >>
> >> thank you very much for you comments.
> >> I'll try to address them inline.
> >>
> >> Best regards
> >> Michael
> >>
> >> On Mar 14, 2011, at 11:10 AM, Kacheong Poon wrote:
> >>
> >>> On 03/14/11 04:48 AM, James M. Polk wrote:
> >>>
> >>>> We chairs want folks to show or assert they have reviewed this ID and
> >>>> give feedback to the list (and not unicast to the chairs). This ID
> >>>> cannot progress without that feedback.
> >>>
> >>>
> >>> I have several comments.
> >>>
> >>> In the Introduction, the reasons to have a SCTP protocol level
> >>> mechanism (stream sequence number reset) to solve the app issue
> >>> are quite sketchy.  For example, one can envision that an app can
> >>> just remember the stream sequence number before it intends to
> >>> re-use a stream such that it can differentiate new and old messages.
> >>> Or there can be a shim layer below the app and above socket layer
> >>> to do this translation.  Or there can be a socket level option to
> >>> do the translation.  And all these can be combined with the app
> >>> layer protocol.  I think the draft should include more details on
> >>> why a SCTP protocol level mechanism is needed.  An example of real
> >>> use case which cannot be accomplished without a SCTP level mechanism
> >>> should probably be provided.
> >> It is hard to provide such an example since you can implement almost
> >> everything at every layer. The point is, where an appropriate
> >> location is for implementing a particular functionality.
> >>
> >> You could, for example, implement all your sequencing in the application
> >> and use only one SCTP stream, sending every message unordered. But
> >> it this the best function split?
> >>>
> >>> More importantly, the draft contains a mechanism to reset
> >>> transmission sequence number but there is no rationale given on why
> >>> this is necessary.  TSN should normally be opaque to applications
> >>> and should be used solely by SCTP for protocol handling.  It is
> >>> hard to see why a reset of TSN is needed to make an app work.  I
> >>> think there should be a very strong reason why such an SCTP protocol
> >>> mechanism is needed.  But the draft gives no reason.
> >> The point here is that we are exposing the TSN to the application.
> >>
> >> You are right, one can design application protocols running on
> >> top of SCTP, and the receiver side does not pay attention to
> >> SSN, SID or TSN. The sender just chooses the SID to enforce the
> >> appropriate sequencing and everything works.
> >> This is what I told people when they were thinking about
> >> using SCTP. However, I had to learn, that they take the SSN into
> >> account. So resetting them makes sense.
> >> Some application writers want streams to be some dynamic channel
> >> they can reset easily.
> >> TSNs are similar to SSNs, they are exposed to the user. So they
> >> might want the be controlled by the user.
> >>> I suggest that the new chunk be called "Stream Re-configuration"
> >>> since the chunk is also about adding new streams.  But even this
> >>> name does not cover the case of resetting TSN, which is at the
> >>> association level.  Is it correct to include a parameter which
> >>> affects the association level TSN in this chunk?  This also goes
> >>> back to the question about the reasons of having TSN reset.
> >> I agree the naming could be improved.
> >> What about:
> >> * Re-configuration Chunk
> >> * Reset Chunk
> >> Both covers TSN/SSN. Maybe the first name covers better the addition
> >> of streams.
> >>>
> >>> The diagram in 3.1 is not correct.  It shows that the parameter
> >>> is only 4 bytes long.
> >> Right. I'll change that to
> >> 0                   1                   2                   3
> >> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >> | Type = 0x82   |  Chunk Flags  |      Chunk Length             |
> >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >> \                                                               \
> >> /                   Stream Reset Parameter                      /
> >> \                                                               \
> >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >> \                                                               \
> >> /                    Stream Reset Parameter (optional)          /
> >> \                                                               \
> >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>
> >> OK?
> >>>
> >>> In 4.1, the use of "Stream Reset Response Sequence Number" is
> >>> confusing.  The draft says
> >>>
> >>>   When this Outgoing SSN Reset Request Parameter is sent in response
> >>>   to an Incoming SSN Reset Request Parameter this parameter is also
> >>>   an implicit response to the incoming request.
> >>>
> >>> So a request is sent in response to another a request?  A response
> >>> to a request is understandable, and the response is either request
> >>> accepted or not.  But a request is sent responding to a request is
> >>> confusing.  It is like sending an SCTP_ABORT in response to an
> >>> SCTP_ABORT.
> >> The "Incoming SSN Reset Request" requests an "Outgoing SSN Reset Request"
> >> to be sent. To simplify things, the sending of the "Outgoing SSN Reset
Request"
> >> is an implicit acknowledgement.
> >>>
> >>> I suppose the rationale, as described in section 5, is that the
> >>> originator of resetting should be the outgoing side.  But this
> >>> raises the question of why then there is an Incoming SSN Reset
> >>> Request.  This just makes the mechanism unnecessarily more
> >>> complicated.  Given that the app layer protocol must first agree
> >>> on the reset operation, it is unclear why there is a need to have
> >>> the Incoming SSN Reset Request.  And if there is really such a
> >>> reason, then why does the same reason not applicable to the SSN/TSN
> >>> resetting and adding more streams?  So should there also be an
> >>> Incoming SSN/TSN Reset Request and Incoming Adding Streams Request?
> >> The SSN/TSN Reset is a reset in both directions.
> >>
> >> However, you are right, an Add Incoming Streams Request Parameter
> >> is missing. I think we should add this. It is conceptually missing.
> >> Randy, Peter: What do you think?
> >
> > I am fine with adding that... ;-)
>
> Yes, agree as well.

I don't think it makes sense at all.

I would imagine that a stream is something that the sender of the data wants,
to do with what it is being asked to do in application terms.  I struggle
to conceive why a receiver would want such a change unless the sender
had discussed it with the receiver at the application level - in which case,
the sender might as well do it.

Resetting SSN/TSN bears no resemblance to this.  This is a network.
It will get knotted.  Question is, how to disentangle the knots?  Tear down
the whole of SCTP and start again, perfectly functional, already in the
protocol,
no need for this I-D; except it is rather wasteful when
only a teeny-weeny part is actually knotted, one small instance of SSN.  So
it makes perfect sense to have an SSN reset and since either end could,
prima facie, be having the problem, then it would be mad not to provide
it at both ends.  Which you, most sensibly, have done.

So the scope of this I-D as it stands makes sense to me, comparing it
with all the other transport protocols (as opposed to having written
applications to use it).

Tom Petch

> >>>
> >>> I suppose there is only the need to have Outgoing SSN Reset Request.
> >>> The app layer protocol should handle which side does the initiation.
> >>> A consequence of not having Incoming request is that then there is
> >>> no need to have an optional second parameter in the chunk.  This
> >>> also eliminates race of Incoming/Outgoing requests cross over.
> >>> Given this simplicity, I think the draft should provide a reason
> >>> that the Incoming request is absolutely necessary.
> >> The reasoning for me is to provide a "complete" solution. I do not
> >> want to provide this part of functionality right now and figure out
> >> in a couple of month that I'm missing another one. I prefer to
> >> extend it once, not multiple times.
> >>>
> >>> In first sentence of 4.3, does "all streams" mean "all outgoing
> >>> streams" or "all incoming streams?"
> >> It means "all incoming and all outgoing streams".
> >> I added that as a clarification.
> >>>
> >>> If a reset timer is running, no other request can be sent out.  So
> >>> there can only be one outstanding unacknowledged request.  I suggest
> >>> that this is mentioned explicitly in 5.1.1.
> >> OK. Done. I added:
> >> <t>At any given time there MUST NOT be more than one request be
> >> in flight. So if the 'Stream Reset Timer' is running and the
> >> the STREAM RESET chunk contains at least one request parameter
> >> the chunk MUST be buffered.</t>
> >>>
> >>> In 6.2, I think it is incorrect to change sctp_event_subscribe
> >>> and use SCTP_EVENTS option because they are deprecated.  It should
> >>> only mention the SCTP_EVENT option.
> >> Well, there are implementations out which support this extension
> >> but not the new way of subscribing to events.
> >>
> >> I added text to make clear which method is deprecated.
> >>
> >> However, I can also live with just removing the text describing
> >> the deprecated way.
> >> Randy? Peter?
> >
> >
> > I don't mind either way.. we can just strike the text... we could
> > even add the new functionality that is in the LC socket-api... That
> > would probably be better..
>
> I would suggest we just remove the text that describes the deprecated
> behavior and stick with text that is consistent with the latest sockets
> API draft.
>
> --peter
>
>
> >
> > R
> >>>
> >>> In all the new events, there are "denied" and "failed" events.  It
> >>> is not clear what "failed" means.  The peer does not respond to
> >>> a request and the association times out?  I suggest that it should
> >>> be made clearer.
> >> Have a look at table 3. The peer can indicate that there was an
> >> error or that it denied the request.
> >>>
> >>> In 6.3.1, IMHO, it is unusual to enable a feature by "removing the
> >>> deny flag."  It is usually done by setting the enable flag.  This
> >>> means that by default, calling getsockopt(SCTP_ENABLE_STREAM_RESET)
> >>> returns a 0 assoc_value.  To enable one feature, call setsockopt()
> >>> with that feature's flag on.
> >> We made deny the default to avoid any problems if an application
> >> can not handle discontinuities in received SSN/TSN and runs now
> >> on a kernel supporting this extension. If an application wants
> >> to use this feature, it must enable it explicitly.
> >
> >>>
> >>>
> >>>
> >>> --
> >>>
> >>> K. Poon.
> >>> ka-cheong.poon@oracle.com
> >>>
> >>
> >>
> >
> > -----
> > Randall Stewart
> > randall@lakerest.net
> >
> >
> >
> >
> >


From Michael.Tuexen@lurchi.franken.de  Wed Mar 16 10:22:17 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 540C13A69D9 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 10:22:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.591
X-Spam-Level: 
X-Spam-Status: No, score=-1.591 tagged_above=-999 required=5 tests=[AWL=-0.598, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, 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 qfzqVEuNkQwT for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 10:22:16 -0700 (PDT)
Received: from mail-n.franken.de (mail-n.franken.de [193.175.24.27]) by core3.amsl.com (Postfix) with ESMTP id D1A853A69DE for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:22:15 -0700 (PDT)
Received: from [192.168.1.113] (p508FC806.dip.t-dialin.net [80.143.200.6]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 524C31C0B461B; Wed, 16 Mar 2011 18:23:11 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
X-Priority: 3
In-Reply-To: <009501cbe3e7$f8fd6e20$4001a8c0@gateway.2wire.net>
Date: Wed, 16 Mar 2011 18:23:10 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1CE0ABE0-E665-491A-B448-8151C87A74B9@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com><201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com><4D7DE97D.6010609@oracle.com><14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de><4D7F3C4B.7090303@oracle.com> <D8826A52-1B36-404B-8A60-FEC7DC90EDB4@lurchi.franken.de> <009501cbe3e7$f8fd6e20$4001a8c0@gateway.2wire.net>
To: t.petch <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.1082)
Cc: Kacheong Poon <ka-cheong.poon@oracle.com>, 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: Wed, 16 Mar 2011 17:22:17 -0000

On Mar 16, 2011, at 3:24 PM, t.petch wrote:

> ----- Original Message -----
> From: "Michael T=FCxen" <Michael.Tuexen@lurchi.franken.de>
> To: "Kacheong Poon" <ka-cheong.poon@oracle.com>
> Cc: <tsvwg@ietf.org>
> Sent: Tuesday, March 15, 2011 3:49 PM
>=20
>> Hi Kacheong,
>>=20
>> one additional question:
>>=20
>>=20
>>>> I agree the naming could be improved.
>>>> What about:
>>>> * Re-configuration Chunk
>>>> * Reset Chunk
>>>=20
>>>=20
>>> Re-configuration chunk is a better choice.
>>>=20
>>>=20
>>=20
>> I change "STREAM RESET chunk" to "RE-CONFIG chunk".
>> However, we still have the generic
>>=20
>> Stream Reset Parameter
>> Stream Reset Request Parameter
>> Stream Reset Response Parameter
>>=20
>> Shouldn't these also be
>>=20
>> Re-configuration Parameter
>> Re-configuration Request Parameter
>> Re-configuration Response Parameter
>>=20
>> What do you think?
>=20
> I think that you will spend the next five iterations of this I-D,
> into AUTH48 and beyond, finding instances of Reset that
> you have missed and omitted to change.
>=20
> ie forget it, in toto.
I think I can search for it. It is not that difficult to decide
which instance is what...

Let's see what Kacheong thinks...

Best regards
Michael
>=20
> Tom Petch
>=20
>> Best regards
>> Michael
>>=20
>=20
>=20


From ietfc@btconnect.com  Wed Mar 16 10:24:13 2011
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 8D7803A69E6 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 10:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.673
X-Spam-Level: 
X-Spam-Status: No, score=-1.673 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 CeMlbIWSKKxC for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 10:24:12 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr06.btconnect.com [213.123.26.184]) by core3.amsl.com (Postfix) with ESMTP id 76E973A69D9 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:24:12 -0700 (PDT)
Received: from host217-44-145-106.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.106]) by c2beaomr06.btconnect.com with SMTP id CIY53571; Wed, 16 Mar 2011 17:25:35 +0000 (GMT)
Message-ID: <01cd01cbe3f6$1ba2b8a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Kacheong Poon" <ka-cheong.poon@oracle.com>, <tsvwg@ietf.org>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com><00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net> <4D80973E.5040002@oracle.com>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Date: Wed, 16 Mar 2011 17:20:43 +0100
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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4D80F28F.0019, actions=TAG
X-Junkmail-Status: score=10/50, host=c2beaomr06.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0209.4D80F28F.0140,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
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: Wed, 16 Mar 2011 17:24:13 -0000

----- Original Message -----
From: "Kacheong Poon" <ka-cheong.poon@oracle.com>
To: <tsvwg@ietf.org>
Sent: Wednesday, March 16, 2011 11:55 AM

> On 03/16/11 04:31 PM, t.petch wrote:
>
> > I am sitting on my hands because I did not consider the I-D ready for last
call
> > but also, I do not have a view as to whether or not this I-D will be
> > implemented,
> > whether or not the additional function is worth standardising - I simply do
not
> > have the contacts to make a judgement on this.
>
> One question, do you think that the stream addition mechanism is
> OK?  Suppose the draft is only about that mechanism, do you think
> that it is worthwhile to be standardized?

I don't have a view.  Compared to other transport protocols, the I-D makes
sense, but whether it makes sense in the context within which SCTP is used,
I do not have the knowledge to make a judgement.

Tom Petch

> K. Poon.
> ka-cheong.poon@oracle.com


From carlberg@g11.org.uk  Wed Mar 16 10:54:52 2011
Return-Path: <carlberg@g11.org.uk>
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 B24593A6A25 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 10:54:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level: 
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599]
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 MkoU0iYYreUd for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 10:54:51 -0700 (PDT)
Received: from portland.eukhosting.net (portland.eukhosting.net [92.48.97.5]) by core3.amsl.com (Postfix) with ESMTP id 8F0FE3A69EF for <tsvwg@ietf.org>; Wed, 16 Mar 2011 10:54:51 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=g11.org.uk; h=Received:From:Content-Type:Content-Transfer-Encoding:Subject:Date:Message-Id:To:Mime-Version:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=UZ5Yhdq0XO0JD36uFqAjbQchiFB0+iRH40gOWnI6oRp5scrI3SiAeskiFjnvn+9+hfKxdnQFiZf/JSHJPoRPZWkZcQp1Q5zpHKRQKEIyNWqWU7KqTGXc/9IwsbxSHw1B;
Received: from c-76-111-69-4.hsd1.va.comcast.net ([76.111.69.4]:55404 helo=[192.168.0.20]) by portland.eukhosting.net with esmtpa (Exim 4.69) (envelope-from <carlberg@g11.org.uk>) id 1Pzux6-0004kq-Uf for tsvwg@ietf.org; Wed, 16 Mar 2011 17:56:09 +0000
From: ken carlberg <carlberg@g11.org.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: draft-polk-tsvwg-intserv-multiple-tspec-06
Date: Wed, 16 Mar 2011 13:56:15 -0400
Message-Id: <63F462BF-471D-43AC-83A1-49AB03EA1768@g11.org.uk>
To: tsvwg <tsvwg@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - portland.eukhosting.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - g11.org.uk
X-Source: 
X-Source-Args: 
X-Source-Dir: 
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: Wed, 16 Mar 2011 17:54:52 -0000

hello,

my understanding is that the decision is still open as to whether this =
individual draft should become a working group draft.  I'd like to =
express my interest in making that migration.  My first comments on the =
draft came way back at the IETF-stockholm meeting in '09, where I =
brought up questions about multicast.  The current draft satisfies these =
questions, and other comments I have made since then.  I think this =
effort is properly baked for acceptance as a working group draft.

But perhaps more importantly, I very much like its focus on =
optimization.  The bulk of the work we come across at the IETF either =
introduces new stuff, or augmentations to existing efforts.  Its =
refreshing to see work that focuses on optimizing something we already =
have.

my 2 cents,

-ken


From Michael.Tuexen@lurchi.franken.de  Wed Mar 16 12:48:20 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 EE3063A6A99 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 12:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.292
X-Spam-Level: 
X-Spam-Status: No, score=0.292 tagged_above=-999 required=5 tests=[AWL=-2.353,  BAYES_00=-2.599, FRT_STOCK2=3.988, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, 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 VY7vP2m+ZE9c for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 12:48:19 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id D9F7F3A6A84 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 12:48:18 -0700 (PDT)
Received: from [192.168.1.113] (p508FC806.dip.t-dialin.net [80.143.200.6]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 201D31C0C0BC4; Wed, 16 Mar 2011 20:49:44 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
X-Priority: 3
In-Reply-To: <009401cbe3e7$f8a1e0a0$4001a8c0@gateway.2wire.net>
Date: Wed, 16 Mar 2011 20:49:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <256633BD-20AF-4530-BEEA-9C15B169E721@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de><51679D6F-1789-46BE-B1E5-22AE064B27E2@lakerest.net> <4D7F941C.9050400@ieee.org> <009401cbe3e7$f8a1e0a0$4001a8c0@gateway.2wire.net>
To: t.petch <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.1082)
Cc: Peter Lei <peter.lei@ieee.org>, Kacheong Poon <ka-cheong.poon@oracle.com>, tsvwg@ietf.org, Randy Stewart <randall@lakerest.net>
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: Wed, 16 Mar 2011 19:48:21 -0000

On Mar 16, 2011, at 3:21 PM, t.petch wrote:

> ----- Original Message -----
> From: "Peter Lei" <peter.lei@ieee.org>
> To: "Randy Stewart" <randall@lakerest.net>; "Michael T=FCxen"
> <Michael.Tuexen@lurchi.franken.de>
> Cc: "Kacheong Poon" <ka-cheong.poon@oracle.com>; <tsvwg@ietf.org>
> Sent: Tuesday, March 15, 2011 5:30 PM
>> Comments inline:
>>=20
>> On 3/14/11 11:06 AM, Randy Stewart wrote:
>>> In-line..
>>>=20
>>> On Mar 14, 2011, at 10:12 AM, Michael T=FCxen wrote:
>>>=20
>>>> Hi Kacheong,
>>>>=20
>>>> thank you very much for you comments.
>>>> I'll try to address them inline.
>>>>=20
>>>> Best regards
>>>> Michael
>>>>=20
>>>> On Mar 14, 2011, at 11:10 AM, Kacheong Poon wrote:
>>>>=20
>>>>> On 03/14/11 04:48 AM, James M. Polk wrote:
>>>>>=20
>>>>>> We chairs want folks to show or assert they have reviewed this ID =
and
>>>>>> give feedback to the list (and not unicast to the chairs). This =
ID
>>>>>> cannot progress without that feedback.
>>>>>=20
>>>>>=20
>>>>> I have several comments.
>>>>>=20
>>>>> In the Introduction, the reasons to have a SCTP protocol level
>>>>> mechanism (stream sequence number reset) to solve the app issue
>>>>> are quite sketchy.  For example, one can envision that an app can
>>>>> just remember the stream sequence number before it intends to
>>>>> re-use a stream such that it can differentiate new and old =
messages.
>>>>> Or there can be a shim layer below the app and above socket layer
>>>>> to do this translation.  Or there can be a socket level option to
>>>>> do the translation.  And all these can be combined with the app
>>>>> layer protocol.  I think the draft should include more details on
>>>>> why a SCTP protocol level mechanism is needed.  An example of real
>>>>> use case which cannot be accomplished without a SCTP level =
mechanism
>>>>> should probably be provided.
>>>> It is hard to provide such an example since you can implement =
almost
>>>> everything at every layer. The point is, where an appropriate
>>>> location is for implementing a particular functionality.
>>>>=20
>>>> You could, for example, implement all your sequencing in the =
application
>>>> and use only one SCTP stream, sending every message unordered. But
>>>> it this the best function split?
>>>>>=20
>>>>> More importantly, the draft contains a mechanism to reset
>>>>> transmission sequence number but there is no rationale given on =
why
>>>>> this is necessary.  TSN should normally be opaque to applications
>>>>> and should be used solely by SCTP for protocol handling.  It is
>>>>> hard to see why a reset of TSN is needed to make an app work.  I
>>>>> think there should be a very strong reason why such an SCTP =
protocol
>>>>> mechanism is needed.  But the draft gives no reason.
>>>> The point here is that we are exposing the TSN to the application.
>>>>=20
>>>> You are right, one can design application protocols running on
>>>> top of SCTP, and the receiver side does not pay attention to
>>>> SSN, SID or TSN. The sender just chooses the SID to enforce the
>>>> appropriate sequencing and everything works.
>>>> This is what I told people when they were thinking about
>>>> using SCTP. However, I had to learn, that they take the SSN into
>>>> account. So resetting them makes sense.
>>>> Some application writers want streams to be some dynamic channel
>>>> they can reset easily.
>>>> TSNs are similar to SSNs, they are exposed to the user. So they
>>>> might want the be controlled by the user.
>>>>> I suggest that the new chunk be called "Stream Re-configuration"
>>>>> since the chunk is also about adding new streams.  But even this
>>>>> name does not cover the case of resetting TSN, which is at the
>>>>> association level.  Is it correct to include a parameter which
>>>>> affects the association level TSN in this chunk?  This also goes
>>>>> back to the question about the reasons of having TSN reset.
>>>> I agree the naming could be improved.
>>>> What about:
>>>> * Re-configuration Chunk
>>>> * Reset Chunk
>>>> Both covers TSN/SSN. Maybe the first name covers better the =
addition
>>>> of streams.
>>>>>=20
>>>>> The diagram in 3.1 is not correct.  It shows that the parameter
>>>>> is only 4 bytes long.
>>>> Right. I'll change that to
>>>> 0                   1                   2                   3
>>>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> | Type =3D 0x82   |  Chunk Flags  |      Chunk Length             |
>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> \                                                               \
>>>> /                   Stream Reset Parameter                      /
>>>> \                                                               \
>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> \                                                               \
>>>> /                    Stream Reset Parameter (optional)          /
>>>> \                                                               \
>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>=20
>>>> OK?
>>>>>=20
>>>>> In 4.1, the use of "Stream Reset Response Sequence Number" is
>>>>> confusing.  The draft says
>>>>>=20
>>>>>  When this Outgoing SSN Reset Request Parameter is sent in =
response
>>>>>  to an Incoming SSN Reset Request Parameter this parameter is also
>>>>>  an implicit response to the incoming request.
>>>>>=20
>>>>> So a request is sent in response to another a request?  A response
>>>>> to a request is understandable, and the response is either request
>>>>> accepted or not.  But a request is sent responding to a request is
>>>>> confusing.  It is like sending an SCTP_ABORT in response to an
>>>>> SCTP_ABORT.
>>>> The "Incoming SSN Reset Request" requests an "Outgoing SSN Reset =
Request"
>>>> to be sent. To simplify things, the sending of the "Outgoing SSN =
Reset
> Request"
>>>> is an implicit acknowledgement.
>>>>>=20
>>>>> I suppose the rationale, as described in section 5, is that the
>>>>> originator of resetting should be the outgoing side.  But this
>>>>> raises the question of why then there is an Incoming SSN Reset
>>>>> Request.  This just makes the mechanism unnecessarily more
>>>>> complicated.  Given that the app layer protocol must first agree
>>>>> on the reset operation, it is unclear why there is a need to have
>>>>> the Incoming SSN Reset Request.  And if there is really such a
>>>>> reason, then why does the same reason not applicable to the =
SSN/TSN
>>>>> resetting and adding more streams?  So should there also be an
>>>>> Incoming SSN/TSN Reset Request and Incoming Adding Streams =
Request?
>>>> The SSN/TSN Reset is a reset in both directions.
>>>>=20
>>>> However, you are right, an Add Incoming Streams Request Parameter
>>>> is missing. I think we should add this. It is conceptually missing.
>>>> Randy, Peter: What do you think?
>>>=20
>>> I am fine with adding that... ;-)
>>=20
>> Yes, agree as well.
>=20
> I don't think it makes sense at all.
>=20
> I would imagine that a stream is something that the sender of the data =
wants,
> to do with what it is being asked to do in application terms.  I =
struggle
> to conceive why a receiver would want such a change unless the sender
> had discussed it with the receiver at the application level - in which =
case,
> the sender might as well do it.
Well, thinking a bit about it... Some apps require bi-directional =
streams,
which normally is handled by using the unidirectional streams in both
directions with the same stream identifier as a bi-directional one.
RFC 3436, for example. Using the example of a communication between
proxies, where you might map TCP connections on SCTP streams, would
be another one.

Best regards
Michael
>=20
> Resetting SSN/TSN bears no resemblance to this.  This is a network.
> It will get knotted.  Question is, how to disentangle the knots?  Tear =
down
> the whole of SCTP and start again, perfectly functional, already in =
the
> protocol,
> no need for this I-D; except it is rather wasteful when
> only a teeny-weeny part is actually knotted, one small instance of =
SSN.  So
> it makes perfect sense to have an SSN reset and since either end =
could,
> prima facie, be having the problem, then it would be mad not to =
provide
> it at both ends.  Which you, most sensibly, have done.
>=20
> So the scope of this I-D as it stands makes sense to me, comparing it
> with all the other transport protocols (as opposed to having written
> applications to use it).
>=20
> Tom Petch
>=20
>>>>>=20
>>>>> I suppose there is only the need to have Outgoing SSN Reset =
Request.
>>>>> The app layer protocol should handle which side does the =
initiation.
>>>>> A consequence of not having Incoming request is that then there is
>>>>> no need to have an optional second parameter in the chunk.  This
>>>>> also eliminates race of Incoming/Outgoing requests cross over.
>>>>> Given this simplicity, I think the draft should provide a reason
>>>>> that the Incoming request is absolutely necessary.
>>>> The reasoning for me is to provide a "complete" solution. I do not
>>>> want to provide this part of functionality right now and figure out
>>>> in a couple of month that I'm missing another one. I prefer to
>>>> extend it once, not multiple times.
>>>>>=20
>>>>> In first sentence of 4.3, does "all streams" mean "all outgoing
>>>>> streams" or "all incoming streams?"
>>>> It means "all incoming and all outgoing streams".
>>>> I added that as a clarification.
>>>>>=20
>>>>> If a reset timer is running, no other request can be sent out.  So
>>>>> there can only be one outstanding unacknowledged request.  I =
suggest
>>>>> that this is mentioned explicitly in 5.1.1.
>>>> OK. Done. I added:
>>>> <t>At any given time there MUST NOT be more than one request be
>>>> in flight. So if the 'Stream Reset Timer' is running and the
>>>> the STREAM RESET chunk contains at least one request parameter
>>>> the chunk MUST be buffered.</t>
>>>>>=20
>>>>> In 6.2, I think it is incorrect to change sctp_event_subscribe
>>>>> and use SCTP_EVENTS option because they are deprecated.  It should
>>>>> only mention the SCTP_EVENT option.
>>>> Well, there are implementations out which support this extension
>>>> but not the new way of subscribing to events.
>>>>=20
>>>> I added text to make clear which method is deprecated.
>>>>=20
>>>> However, I can also live with just removing the text describing
>>>> the deprecated way.
>>>> Randy? Peter?
>>>=20
>>>=20
>>> I don't mind either way.. we can just strike the text... we could
>>> even add the new functionality that is in the LC socket-api... That
>>> would probably be better..
>>=20
>> I would suggest we just remove the text that describes the deprecated
>> behavior and stick with text that is consistent with the latest =
sockets
>> API draft.
>>=20
>> --peter
>>=20
>>=20
>>>=20
>>> R
>>>>>=20
>>>>> In all the new events, there are "denied" and "failed" events.  It
>>>>> is not clear what "failed" means.  The peer does not respond to
>>>>> a request and the association times out?  I suggest that it should
>>>>> be made clearer.
>>>> Have a look at table 3. The peer can indicate that there was an
>>>> error or that it denied the request.
>>>>>=20
>>>>> In 6.3.1, IMHO, it is unusual to enable a feature by "removing the
>>>>> deny flag."  It is usually done by setting the enable flag.  This
>>>>> means that by default, calling =
getsockopt(SCTP_ENABLE_STREAM_RESET)
>>>>> returns a 0 assoc_value.  To enable one feature, call setsockopt()
>>>>> with that feature's flag on.
>>>> We made deny the default to avoid any problems if an application
>>>> can not handle discontinuities in received SSN/TSN and runs now
>>>> on a kernel supporting this extension. If an application wants
>>>> to use this feature, it must enable it explicitly.
>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> --
>>>>>=20
>>>>> K. Poon.
>>>>> ka-cheong.poon@oracle.com
>>>>>=20
>>>>=20
>>>>=20
>>>=20
>>> -----
>>> Randall Stewart
>>> randall@lakerest.net
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>=20
>=20


From jmpolk@cisco.com  Wed Mar 16 13:00:39 2011
Return-Path: <jmpolk@cisco.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 2D3CF3A6A5B for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 13:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.569
X-Spam-Level: 
X-Spam-Status: No, score=-110.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 BAoB+NGAAuZW for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 13:00:38 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 49AC03A6A39 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 13:00:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=495; q=dns/txt; s=iport; t=1300305725; x=1301515325; h=message-id:date:to:from:subject:mime-version; bh=fh1ylclc78Dvd5xb57Mtjgk7ZTjatHXUAyvMyQ5RERY=; b=iZWO6C8rddoTQGbVwFeIvglXzEx8OXQQiNxw+SjkMr5Ze1tcBGxxOUJg MdpHV2AuT9XsBgyNp2/NDCRqFzGHNqR+kZKOpdTk0H2AkolpYmXpLwCIm o44/TPlFwPowGfVrCk1Qv8iRSLAVYb/sW9sBym/PPG3IOa5DMI46LBINw 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFS0gE2tJXG//2dsb2JhbACmDHeldZxWhWMEhS8
X-IronPort-AV: E=Sophos;i="4.63,195,1299456000"; d="scan'208";a="347880977"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by sj-iport-5.cisco.com with ESMTP; 16 Mar 2011 20:02:04 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by rcdn-core2-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2GK23MV013188 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 20:02:03 GMT
Message-Id: <201103162002.p2GK23MV013188@rcdn-core2-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 16 Mar 2011 15:02:02 -0500
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: DRAFT Agenda for TSVWG in Prague (IETF 80)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Wed, 16 Mar 2011 20:00:39 -0000

TSVWG

Here is the link to the *DRAFT* agenda for our meeting in Prague 
later this month.  We've asked several times for agenda requests, so 
here's your chance to see who all listened   ;-)

http://www.ietf.org/proceedings/80/agenda/tsvwg.txt

I know of a couple of editors that are not going to make the meeting, 
which is why a couple of docs aren't on the agenda this time.

Let me know if you see something that needs to be adjusted or added.

James & Gorry
(chair hats on)


From sob@harvard.edu  Wed Mar 16 15:08:23 2011
Return-Path: <sob@harvard.edu>
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 B30163A6A35 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 15:08:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.496
X-Spam-Level: 
X-Spam-Status: No, score=-102.496 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 DUdJSLYkxMei for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 15:08:23 -0700 (PDT)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id 044D53A69F8 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 15:08:23 -0700 (PDT)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id 75DF39962F7; Wed, 16 Mar 2011 18:09:48 -0400 (EDT)
To: tsvwg@ietf.org
Subject: Re: draft-polk-tsvwg-intserv-multiple-tspec-06
Message-Id: <20110316220948.75DF39962F7@newdev.eecs.harvard.edu>
Date: Wed, 16 Mar 2011 18:09:48 -0400 (EDT)
From: sob@harvard.edu (Scott O. Bradner)
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: Wed, 16 Mar 2011 22:08:23 -0000

I very much support this doc being finished up - it is very 
useful technology

if the tsvwg is able to do the work I'd support that  path 

thanks

Scott

From fred@cisco.com  Wed Mar 16 15:22:28 2011
Return-Path: <fred@cisco.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 933753A6A43 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 15:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.504
X-Spam-Level: 
X-Spam-Status: No, score=-110.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 j5Wn6IX4jsVT for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 15:22:26 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id A49F53A6974 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 15:22:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=2830; q=dns/txt; s=iport; t=1300314234; x=1301523834; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=9e4cQdOqv92jpRJyp0Ew2e1Yl+DtCB6DN2PwBRYRxnM=; b=Yubv/W7SVF5GFnI+lv/dxqFYVt8cvgL2A8OUuqWjQJLQkXTKFX795m4j CDZV0a69jSCh7lFLtjEo/TvjNYwLFS8gniL28D6Fr7CidpWNi6UaS0QrK k1s4FDUrSzrAC1UmKxC8ptpNY4RzkdyDxOvgFoOPnLwwZTzlOz6OGS0mu w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACPVgE2tJV2c/2dsb2JhbAClS3emB5xShWMEhS+HL4NN
X-IronPort-AV: E=Sophos;i="4.63,195,1299456000"; d="scan'208";a="276800188"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by sj-iport-4.cisco.com with ESMTP; 16 Mar 2011 22:23:53 +0000
Received: from stealth-10-32-244-221.cisco.com (stealth-10-32-244-221.cisco.com [10.32.244.221]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id p2GMNiCe001571;  Wed, 16 Mar 2011 22:23:52 GMT
Received: from [127.0.0.1] by stealth-10-32-244-221.cisco.com (PGP Universal service); Wed, 16 Mar 2011 15:23:53 -0700
X-PGP-Universal: processed; by stealth-10-32-244-221.cisco.com on Wed, 16 Mar 2011 15:23:53 -0700
Subject: Re: draft-polk-tsvwg-intserv-multiple-tspec-06
Mime-Version: 1.0 (Apple Message framework v1082)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <63F462BF-471D-43AC-83A1-49AB03EA1768@g11.org.uk>
Date: Wed, 16 Mar 2011 15:23:32 -0700
Message-Id: <E6D6FBF9-9918-4C54-BB37-C247F8ECD01E@cisco.com>
References: <63F462BF-471D-43AC-83A1-49AB03EA1768@g11.org.uk>
To: ken carlberg <carlberg@g11.org.uk>
X-Mailer: Apple Mail (2.1082)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: tsvwg <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: Wed, 16 Mar 2011 22:22:28 -0000

On Mar 16, 2011, at 10:56 AM, ken carlberg wrote:

> hello,
>=20
> my understanding is that the decision is still open as to whether this =
individual draft should become a working group draft.  I'd like to =
express my interest in making that migration.  My first comments on the =
draft came way back at the IETF-stockholm meeting in '09, where I =
brought up questions about multicast.  The current draft satisfies these =
questions, and other comments I have made since then.  I think this =
effort is properly baked for acceptance as a working group draft.
>=20
> But perhaps more importantly, I very much like its focus on =
optimization.  The bulk of the work we come across at the IETF either =
introduces new stuff, or augmentations to existing efforts.  Its =
refreshing to see work that focuses on optimizing something we already =
have.
>=20
> my 2 cents,
>=20
> -ken

I think a relevant note is:

On Nov 1, 2010, at 4:14 PM, Bruce Davie wrote:
> On these 2 drafts:
> On Oct 26, 2010, at 8:29 AM, Gorry Fairhurst wrote:
>=20
>> draft-polk-tsvwg-intserv-multiple-tspec
>>     RSVP directorate to be consulted.
>>     WG interest in this topic recorded at IETF-78.
>>     Charter update would be needed to progress this work.
>>     5 Reviews needed to determine energy/technical direction.
>>     Author will update -04.
>>     New revision expected.
>>=20
>> draft-lefaucheur-tsvwg-rsvp-multiple-preemption
>>     RSVP directorate to be consulted.
>>     WG needs to assess if this topic should be a work item.
>=20
> Two members of the RSVP directorate (myself and Lixia) have read these =
drafts and support their adoption by the WG. Below are some specific =
comments that I sent to the chairs, but I failed to send earlier to the =
WG. I believe at least one more directorate member has read these drafts =
but I've not received feedback one way or another about adoption from =
other directorate members.

It would be good to know whether other members of the RSVP Directorate =
have commented. If there has been a charter discussion, I have managed =
to miss it.

As to the draft itself, I think there is reason to support it, as we now =
have multi-rate codecs that can interact with it; rather than firing up, =
disturbing competing traffic to a degree that the codec data experiences =
loss and other traffic presumably does as well, and then backing off to =
a more acceptable rate (which is what rate-adaptive codecs do), it would =
be nice of the network could say "that will happen if you choose this =
rate, but if you choose this lower rate you will be better off." Having =
multiple T-Specs gives the network the option of making that choice on =
the first pas rather than taking binary decisions on multiple sequential =
decision steps.=

From sob@harvard.edu  Wed Mar 16 15:31:36 2011
Return-Path: <sob@harvard.edu>
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 CF8F73A6A69 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 15:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level: 
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 QSan-ugzLjhZ for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 15:31:36 -0700 (PDT)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id A1B513A6974 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 15:31:34 -0700 (PDT)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id AFCD4996491; Wed, 16 Mar 2011 18:33:01 -0400 (EDT)
To: tsvwg@ietf.org
Subject: Re: draft-polk-tsvwg-intserv-multiple-tspec-06
Message-Id: <20110316223301.AFCD4996491@newdev.eecs.harvard.edu>
Date: Wed, 16 Mar 2011 18:33:01 -0400 (EDT)
From: sob@harvard.edu (Scott O. Bradner)
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: Wed, 16 Mar 2011 22:31:37 -0000

Fred sed:
> It would be good to know whether other members of the RSVP Directorate
> have commented. 

I should have mentioned, I was commenting for myself and as a member of
the RSVP Directorate

Scott

From gorry@erg.abdn.ac.uk  Thu Mar 17 01:15:22 2011
Return-Path: <gorry@erg.abdn.ac.uk>
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 5799C3A6834 for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 01:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 lHipRBreaw7Q for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 01:15:20 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id 503E23A6836 for <tsvwg@ietf.org>; Thu, 17 Mar 2011 01:15:19 -0700 (PDT)
Received: from Gorry-Fairhursts-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id p2H8GdAd009030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 17 Mar 2011 08:16:40 GMT
Message-ID: <4D81C367.8090607@erg.abdn.ac.uk>
Date: Thu, 17 Mar 2011 08:16:39 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: tsvwg list <tsvwg@ietf.org>
Subject: TSVWG Status Update 17-Mar-2011
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
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: Thu, 17 Mar 2011 08:15:22 -0000

The email below gives a brief snapshot of WG status for 17th March 2011.

Please look at what needs to be done.

Do send notes of any corrections to tsvwg-chairs@tools.ietf.org.

Gorry & James
(TSVWG Chairs)

==================================================================

RFC Published:

draft-ietf-tsvwg-admitted-realtime-dscp-07 (RFC 5865)
draft-ietf-tsvwg-rsvp-proxy-approaches-09 (RFC 5945)
draft-ietf-tsvwg-rsvp-proxy-proto-11 (RFC 5946)
draft-ietf-tsvwg-rsvp-l3vpn-07 (RFC 6016)
draft-ietf-tsvwg-ecn-tunnel-10 (RFC6040)
draft-ietf-tsvwg-port-randomization (RFC 6056)
draft-ietf-tsvwg-sctp-chunk-flags (RFC 6096)
draft-ietf-tsvwg-dtls-for-sctp (RFC 6083)

---
IDs in RFC Editor Queue:

draft-ietf-tsvwg-emergency-rsvp-15 (MISREF)
Norm. ref to router alert draft (in the INT-area WG, now in WGLC)

-------------------------------------------------------------------

IDs in IESG processing:

draft-ietf-tsvwg-rsvp-security-groupkeying
       WGLC of previous version completed.
       SECDIR review comments received, and updated as version -05.
       Short WGLC to confirm new text ended August 11th 2010.
       New version (-09) 22-10-2010.
       Proto write-up sent 14/12/2010.
       Publication requested.
     James is Shepherd.
     DUE: AD to review.

draft-ietf-tsvwg-iana-ports
       New revision 25 Oct 2010.
       This will require a multi-working group LC.
       draft-ietf-tsvwg-iana-ports-08 was WGL'ed 30-10-2010
       WGLC ended Friday, 26th November 2010
          New version -09 02/12/2010.
           Discussion on list during Dec 2010.
          AD review received 21/12/2010.
       	 Proto Write-up sent 19/01/2011.
          Revised document text being agreed 17-Mar-2011.
       Gorry is Shepherd.

-------------------------------------------------------------------

WG Drafts with Chairs:

draft-ietf-tsvwg-sctpsocket
       New Rev -25, 07/01/2011.
       WGLC complete.
     James is Shepherd.
     DUE: Proto Write-up by Shepherd

draft-ietf-tsvwg-sctp-strrst
       Dependency on this for IPFIX document with RFC-Ed.
       Benoit Claise to review for IPFIX
       New revision (-08) 25 Oct 2010.
           Text on race-condition to be updated before WGLC
       New text to address this in revision 04/01/2011.
       WGLC in progress.
     James is Shepherd.
     DUE: WG Chairs to evaluate result of WGLC (17-Mar-2011)

-------------------------------------------------------------------

WG Drafts:

draft-ietf-tsvwg-byte-pkt-congest
       New editor added Jul 2010.
       New revision 25 Oct 2010.
      DUE: Comments needed before deciding if ready for WGLC.
      DUE: Reviewers need to volunteer for LC

draft-ietf-tsvwg-sctp-udp-encap
       (Replaced: draft-tuexen-sctp-udp-encap)
       Lars sent a note as AD agreeing to progress this work.
       Work to be coordinated with DCCP work on encaps.
       Adopted as a work item 21 Sept 2010 (Gorry).
           No WG -00 draft.
       DUE: New revision expected
       DUE: Editors please tell chairs of document plans (17-Mar-2011)

draft-ietf-tsvwg-natsupp-tsvwg
       (Replaced: draft-stewart-natsupp-tsvw)
       Dependency from BEHAVE WG.
       Adopted as a work item 21 Sept 2010 (Gorry).
           WG -00, 29/11/2010
            uploaded as: draft-ietf-natsupp-tsvwg
       New revision expected
       DUE: draft needs renamed to draft-ietf-tsvwg-natsupp-tsvwg

draft-ietf-tsvwg-source-quench
        (Replaced: draft-gont-tsvwg-source-quench-01.txt)
        IETF-79 suggested there was interest in this topic.
        Comments to list in 2010 from: Fred Baker, Antonio DeSimone,
           James Polk, Gorry Fairhurst, Andrew Yourtchenko, and others.
        WG agreed the draft should be a work item.
        Please comment on list.
       DUE: New revision expected
       DUE: Editors please tell chairs of document plans (17-Mar-2011)

-------------------------------------------------------------------

WG action required:

draft-polk-tsvwg-rsvp-app-id-vv-profiles
        -01 Presented in Beijing.
        -02 was submitted 14-Mar-2011
        WG needs to assess if the new draft should be a work item.
        Please comment on list.

-------------------------------------------------------------------

The following have received recent discussion at TSVWG meetings or on
the list. Inclusion in the list below does not indicate support for
these specific drafts and other contributions are also warmly welcomed.

draft-stewart-tsvwg-sctpecn-00
        Partially replaces (draft-stewart-tsvwg-sctp-nonce)
        IETF-78 suggested there was interest in this topic.
        Please comment to list.
        Revised draft to be uploaded with new name.
        WG needs to assess if the new draft should be a work item.

    draft-polk-tsvwg-intserv-multiple-tspec
        RSVP directorate to be consulted.
        WG interest in this topic recorded at IETF-78.
       Charter update would be needed to progress this work.
       5 Reviews needed to determine energy/technical direction.
       Version -05 (presented in Beijing)
       Version -06 was submitted 14-Mar-2011.
       WG needs to assess if the new draft should be a work item.

    draft-lefaucheur-tsvwg-rsvp-multiple-preemption
        RSVP directorate to be consulted.
           - Reviewers: Bruce Davie (awaiting other reviews)
        WG needs to assess if this topic should be a work item.

    draft-wing-tsvwg-happy-eyeballs-sctp
        Please comment to list.

    draft-tuexen-tsvwg-sctp-multipath
        Please comment to list.

    draft-nishida-tsvwg-sctp-failover
        Please comment to list.

     WGChair note: Above two drafts should be read together.

    draft-tuexen-tsvwg-sctp-sack-immediately
        Please comment to list.

    draft-lei-tsvwg-sctp-compr-requirements-profile
        Please comment to list.

    draft-wei-tsvwg-nested-header-compression
        Please comment to list.

-------------------------------------------------------------------

Related non-WG items:

draft-fairhurst-tsvwg-6man-udpzero
        Draft was adopted by 6man, please discuss on the 6man list.
        This will be LC'ed in TSVWG also.

draft-ietf-dccp-udpencap
        DCCP WG item linked to encaps (WGLC)

draft-narayanan-tsvwg-rsvp-resource-sharing
        Authors to take this draft to CCAMP WG.

draft-ietf-behave-sctpnat-03.txt
        BEHAVE WG item linked to SCTP encapsulation work.

------------------------------------------------------------------

Other news:

    RSVP Directorate (formed in May 2010)
      - Rules and guidelines to be formulated

    Charter to be updated to indicate procedure for adoption.

------------------------------------------------------------------






From gorry@erg.abdn.ac.uk  Thu Mar 17 01:28:56 2011
Return-Path: <gorry@erg.abdn.ac.uk>
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 E2C7C3A67B0 for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 01:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 jWbvNPItWCFR for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 01:28:49 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id 4CADD3A67FC for <tsvwg@ietf.org>; Thu, 17 Mar 2011 01:28:47 -0700 (PDT)
Received: from Gorry-Fairhursts-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id p2H8TxWq009253 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <tsvwg@ietf.org>; Thu, 17 Mar 2011 08:30:01 GMT
Message-ID: <4D81C686.1020701@erg.abdn.ac.uk>
Date: Thu, 17 Mar 2011 08:29:58 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>
Subject: Fwd: Re: draft-polk-tsvwg-intserv-multiple-tspec-06
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
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: Thu, 17 Mar 2011 08:28:57 -0000

I'm happy to discuss the future steps for this draft.

I'll also take an action to check the status and then seek help from the 
RSVP directorate, the last note I saw from rsv-dir was 09/11/2010.

I'll also try to sumarise where I see this draft has reached. I can't do 
this today though.

Gorry

-------- Original Message --------
Subject: Re: draft-polk-tsvwg-intserv-multiple-tspec-06
Date: Wed, 16 Mar 2011 15:23:32 -0700
From: Fred Baker <fred@cisco.com>
To: ken carlberg <carlberg@g11.org.uk>
CC: tsvwg <tsvwg@ietf.org>


On Mar 16, 2011, at 10:56 AM, ken carlberg wrote:

> hello,
>
> my understanding is that the decision is still open as to whether this individual draft should become a working group draft.  I'd like to express my interest in making that migration.  My first comments on the draft came way back at the IETF-stockholm meeting in '09, where I brought up questions about multicast.  The current draft satisfies these questions, and other comments I have made since then.  I think this effort is properly baked for acceptance as a working group draft.
>
> But perhaps more importantly, I very much like its focus on optimization.  The bulk of the work we come across at the IETF either introduces new stuff, or augmentations to existing efforts.  Its refreshing to see work that focuses on optimizing something we already have.
>
> my 2 cents,
>
> -ken

I think a relevant note is:

On Nov 1, 2010, at 4:14 PM, Bruce Davie wrote:
> On these 2 drafts:
> On Oct 26, 2010, at 8:29 AM, Gorry Fairhurst wrote:
>
>> draft-polk-tsvwg-intserv-multiple-tspec
>>     RSVP directorate to be consulted.
>>     WG interest in this topic recorded at IETF-78.
>>     Charter update would be needed to progress this work.
>>     5 Reviews needed to determine energy/technical direction.
>>     Author will update -04.
>>     New revision expected.
>>
>> draft-lefaucheur-tsvwg-rsvp-multiple-preemption
>>     RSVP directorate to be consulted.
>>     WG needs to assess if this topic should be a work item.
>
> Two members of the RSVP directorate (myself and Lixia) have read these drafts and support their adoption by the WG. Below are some specific comments that I sent to the chairs, but I failed to send earlier to the WG. I believe at least one more directorate member has read these drafts but I've not received feedback one way or another about adoption from other directorate members.

It would be good to know whether other members of the RSVP Directorate 
have commented. If there has been a charter discussion, I have managed 
to miss it.

As to the draft itself, I think there is reason to support it, as we now 
have multi-rate codecs that can interact with it; rather than firing up, 
disturbing competing traffic to a degree that the codec data experiences 
loss and other traffic presumably does as well, and then backing off to 
a more acceptable rate (which is what rate-adaptive codecs do), it would 
be nice of the network could say "that will happen if you choose this 
rate, but if you choose this lower rate you will be better off." Having 
multiple T-Specs gives the network the option of making that choice on 
the first pas rather than taking binary decisions on multiple sequential 
decision steps.



From ka-cheong.poon@oracle.com  Thu Mar 17 02:42:57 2011
Return-Path: <ka-cheong.poon@oracle.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 6AFA63A6806 for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 02:42:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.669
X-Spam-Level: 
X-Spam-Status: No, score=-5.669 tagged_above=-999 required=5 tests=[AWL=0.574,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 qsAQ0DV0EUHH for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 02:42:56 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 748CD3A67CC for <tsvwg@ietf.org>; Thu, 17 Mar 2011 02:42:56 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2H9iM1V022128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Thu, 17 Mar 2011 09:44:23 GMT
Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2H9iLca001585 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Thu, 17 Mar 2011 09:44:21 GMT
Received: from abhmt003.oracle.com (abhmt003.oracle.com [141.146.116.12]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2H9iLWx032046 for <tsvwg@ietf.org>; Thu, 17 Mar 2011 04:44:21 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 17 Mar 2011 02:44:21 -0700
Message-ID: <4D81D7F1.5060102@oracle.com>
Date: Thu, 17 Mar 2011 17:44:17 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <D8826A52-1B36-404B-8A60-FEC7DC90EDB4@lurchi.franken.de> <4D8095EE.3060706@oracle.com> <79C91FD0-57BC-428E-A075-B580B4A3C57D@lurchi.franken.de>
In-Reply-To: <79C91FD0-57BC-428E-A075-B580B4A3C57D@lurchi.franken.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Source-IP: acsmt356.oracle.com [141.146.40.156]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090206.4D81D7F6.0009,ss=1,fgs=0
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: Thu, 17 Mar 2011 09:42:57 -0000

On 03/16/11 08:04 PM, Michael Tüxen wrote:

> not sure you got the point I wanted to make. The text reads now (in CVS):


I missed that.


> I thought that something like the following would be more appropriate:


Agreed.


> 3.1.  RE-CONFIG Chunk
>
>     This document adds one new chunk type to SCTP.  The chunk has the
>     following format:
>
>      0                   1                   2                   3
>      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     | Type = 0x82   |  Chunk Flags  |      Chunk Length             |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     \                                                               \
>     /                  Re-configuration Parameter                   /
>     \                                                               \
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     \                                                               \
>     /            Re-configuration Parameter (optional)              /
>     \                                                               \
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> ...
>     Re-configuration Parameter
>        This field holds a Re-configuration Request Parameter or a
>        Re-configuration Response Parameter.
>
>     Note that each RE-CONFIG chunk holds at least one parameter and at
>     most two parameters.  Only the following combinations are allowed:
>
>     1.  Outgoing SSN Reset Request Parameter.
>
>     2.  Incoming SSN Reset Request Parameter.
>
>     3.  Outgoing SSN Reset Request Parameter, Incoming SSN Reset Request
>         Parameter.
>
>     4.  SSN/TSN Reset Request Parameter.
>
>     5.  Add Outgoing Streams Request Parameter.
>
>     6.  Re-configuration Response Parameter.
>
>     7.  Re-configuration Response Parameter, Outgoing SSN Reset Request
>         Parameter.
>
>     8.  Re-configuration Response Parameter, Re-configuration Response Parameter.




-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Thu Mar 17 03:29:21 2011
Return-Path: <ka-cheong.poon@oracle.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 022213A6839 for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 03:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.721
X-Spam-Level: 
X-Spam-Status: No, score=-5.721 tagged_above=-999 required=5 tests=[AWL=0.522,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 fVsaJW1euOe2 for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 03:29:19 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 92B9C3A6806 for <tsvwg@ietf.org>; Thu, 17 Mar 2011 03:29:19 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2HAUjcI009619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Thu, 17 Mar 2011 10:30:46 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2HAUiPj014146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Thu, 17 Mar 2011 10:30:44 GMT
Received: from abhmt010.oracle.com (abhmt010.oracle.com [141.146.116.19]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2HAUins014578 for <tsvwg@ietf.org>; Thu, 17 Mar 2011 05:30:44 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 17 Mar 2011 03:30:43 -0700
Message-ID: <4D81E2D1.3010201@oracle.com>
Date: Thu, 17 Mar 2011 18:30:41 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de> <4D809432.5050601@oracle.com> <F3AF1842-07FB-4F06-8501-B2EDB1309438@lurchi.franken.de>
In-Reply-To: <F3AF1842-07FB-4F06-8501-B2EDB1309438@lurchi.franken.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Source-IP: acsmt357.oracle.com [141.146.40.157]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090201.4D81E2D4.0127,ss=1,fgs=0
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: Thu, 17 Mar 2011 10:29:21 -0000

On 03/16/11 08:32 PM, Michael Tüxen wrote:

> But the above is not sufficient. Resetting a stream does not
> only reset the counter but also
> * signals that it is requested
> * acknowledges that is has been performed


The above is started by the app layer, right?  So
the app layer already needs to perform the action.  It
is not something which is initiated by the transport
layer and must be done in the transport layer.  It is
an app layer protocol.


> So if you want to implement it at the application layer,
> you need to define at least two application layer messages
> and the appropriate procedures. So you need to extend the
> application layer and get the procedures right.
> So, yes it can be done at the application layer, but
> * each application protocol must re-implement the same mechanism.
> * you need to extend each application protocol.
> Doing it at the transport layer, requires the mechanism
> only to be implemented once and no change of the application
> protocol.


Why is it more appropriate to do it at the transport
layer?  There are many examples of having such a layer
below app layer and above transport which do this sort of
things.  App writers don't need to reinvent the wheel,
nor do transport protocol designers.  I still don't see why
doing it at the transport layer is better or require less
code to implement the signaling right.

In fact, one can argue that having it in transport layer
removes the flexibility of supporting many different types
of semantics which  app layers require.  I think you won't
agree to the idea that SCTP should support all types of
signaling any apps may require, right?  This is not a
sound design choice.  This just makes SCTP bigger and
bigger.  It will be a kitchen sink of all sorts of app
layer protocol mechanism.  It seems that you are arguing
that there should be no app layer protocol and the transport
layer should provide every conceivable service any app may
require.  Do other people in this WG also think this way?


> I think the question is not if it is necessary, but which layer
> is the most appropriate.


Agreed.  Is it really hard to do that in the app layer?
As a previous TCP example, head of line blocking cannot
be avoided without opening multiple TCP connections.  And
doing so has congestion impact on the network.  It is this
sort of things which is appropriate to do at the transport
layer.


> As with my example from two days or so ago, it is *not necessary*
> to do reordering at the transport layer. We could have also
> left that feature for the application and only support unordered
> delivery in the transport layer. But we didn't (which is good).


Well, I guess it is expected that a connection oriented
reliable transport protocol at least provides in order
delivery.  If it does not handle re-ordering, it cannot be
called such a protocol.


> So I think the question is: What does provide a stream for
> the application layer.
> * Just a static channel which provides in-sequence delivery
>    This might have been the original intention (from SIGTRAN),
>    but this does not require exposing TSN/SSN.
>
> I think people started looking at TSN/SSN, since we are
> exposing it and, when using outside of the SIGTRAN applications,
> they want to have something like
> * A dynamic channel which provides in-sequence delivery.
> Here dynamic means it can be added / removed / reused.


While the meaning of adding and removing an SCTP stream is
clear, I think "reuse" needs to be defined carefully.  An
app can use a stream and then not use it for a while.  There
is nothing to prevent an app to re-use it later.


> Removing is hard, so that is why we left it out. I also argued
> at some time, the you do not need to add streams, just start
> the association with enough streams. But app writers see it
> differently.


I think there is no need to "remove" a stream.  An app can
choose not to use any stream.  This is not true if an app
wants to use more streams than it thinks it needs at the start
of an association.  There is no mechanism to do it now.


> So being able to add and reset streams seems a good compromise
> for me. It can be added relatively simple to SCTP and it
> provides almost all the app writers need.


Can you explain why resetting SSN/TSN is equivalent to
re-using a stream or the association?  BTW, there is still
no example given to the use of resetting TSN.  I think this
must be added to the draft.


> As said above, you can put it at either layer. We just seem
> to disagree, where the more appropriate layer is...


So far, I think the key point you've raised to support
doing it at the transport layer is that it can then be
used by any apps.  I think doing it in a library achieves
the same thing.  Don't you agree?


> Well, I thought for the application it is only important
> to know if the request was successful, denied or failed.
> It also uses a field which is there anyway.
>
> But if you prefer, we can add a field which contains the
> return code, which was on the wire. Not sure if it really
> helps.


No preference.  Just that it is not clear in the text what
the difference between denied and failed is since both
are failures.


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Thu Mar 17 03:37:41 2011
Return-Path: <ka-cheong.poon@oracle.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 116D83A68D8 for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 03:37:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.765
X-Spam-Level: 
X-Spam-Status: No, score=-5.765 tagged_above=-999 required=5 tests=[AWL=0.478,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 VQco-VXmARH4 for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 03:37:40 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 1FC0B3A68AA for <tsvwg@ietf.org>; Thu, 17 Mar 2011 03:37:40 -0700 (PDT)
Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2HAd6QL003249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Thu, 17 Mar 2011 10:39:07 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2HAd5LS017646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Thu, 17 Mar 2011 10:39:06 GMT
Received: from abhmt013.oracle.com (abhmt013.oracle.com [141.146.116.22]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2HAd5JN021596 for <tsvwg@ietf.org>; Thu, 17 Mar 2011 05:39:05 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 17 Mar 2011 03:39:05 -0700
Message-ID: <4D81E4C6.8090002@oracle.com>
Date: Thu, 17 Mar 2011 18:39:02 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de>	<4D7F3C4B.7090303@oracle.com> <D891B32A-51F4-401C-A4D6-4DF5FEAF3E91@lakerest.net> <4D808D2A.9060705@oracle.com> <FFC0BCC4-9168-4E18-A718-7FF3DBACB24B@lakerest.net>
In-Reply-To: <FFC0BCC4-9168-4E18-A718-7FF3DBACB24B@lakerest.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt357.oracle.com [141.146.40.157]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090207.4D81E4CA.0064,ss=1,fgs=0
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: Thu, 17 Mar 2011 10:37:41 -0000

On 03/16/11 10:07 PM, Randy Stewart wrote:
>
> On Mar 16, 2011, at 6:12 AM, Kacheong Poon wrote:
>
>> On 03/15/11 08:55 PM, Randy Stewart wrote:
>>
>>> Resetting a stream then lets an app re-use it sort of like
>>> ftp uses the closing of a connection to indicate that the
>>> file transfer is complete.... I don't see thats a poor design
>>> choice.
>>
>>
>> I guess the question is whether the app layer cannot do
>> it or the app layer cannot do it any better than in the
>> transport layer.  To tell the other side that a transfer
>> is complete in one stream does not require resetting SSN.
>> For example, HTTP allows sending multiple files and it
>> does not require resetting the TCP connection.
>
>
> So you use a whole transport connection setup has a mechanism to
> tell that something is complete. This is the same thing as ftp and
> I think resetting a stream is a LOT less heavy weight....


As an example above,  HTTP uses one TCP connection to transfer
multiple files without the need to resetting the connection.
What ftp currently does has no relation to what other app layer
protocols can do.


>>> So lets see .. what happens when I send more than 65,536 messages
>>> as I re-use the stream say 10.000 times?
>>>
>>> Or do we say no you may only send N messages where N = 65k/number-of-times you wish to
>>> use it?
>>
>>
>> I am not sure I understand the example above.  An app can
>> send as many messages in a stream.  Using the file transfer
>> example above, an app sends the whole file to the other
>> side (number of messages does not matter here).  The app
>> layer receives the whole file and it knows where it ends.
>> After this, the next file is sent using the same stream.
>> What is the reason that the SSN needs to be reset to 0 before
>> sending the next file?
>
> I can easily know that I close the file and when the stream
> reset arrives. This tells me the transfer is done the same way
> in ftp you use the closing of the connection as an indication that
> the transfer is complete.


This can also be done by the app layer protocol.  As I suggested
in another email, an unordered message can do the same thing or
other methods suggested by Michael.



-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Thu Mar 17 03:57:50 2011
Return-Path: <ka-cheong.poon@oracle.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 EBBCE3A68F2 for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 03:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.802
X-Spam-Level: 
X-Spam-Status: No, score=-5.802 tagged_above=-999 required=5 tests=[AWL=0.441,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 ExdZ0-S7uWdj for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 03:57:50 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 1792D3A68E1 for <tsvwg@ietf.org>; Thu, 17 Mar 2011 03:57:50 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2HAxGhK017358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Thu, 17 Mar 2011 10:59:17 GMT
Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2HAxFKA018918 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Thu, 17 Mar 2011 10:59:15 GMT
Received: from abhmt017.oracle.com (abhmt017.oracle.com [141.146.116.26]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2HAxFs8032238 for <tsvwg@ietf.org>; Thu, 17 Mar 2011 05:59:15 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 17 Mar 2011 03:59:14 -0700
Message-ID: <4D81E97F.70309@oracle.com>
Date: Thu, 17 Mar 2011 18:59:11 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de>	<4D7F3C4B.7090303@oracle.com>	<0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de>	<4D809432.5050601@oracle.com>	<F3AF1842-07FB-4F06-8501-B2EDB1309438@lurchi.franken.de> <5FDD193A-B09F-400B-8EC2-931BF6AECF18@lakerest.net>
In-Reply-To: <5FDD193A-B09F-400B-8EC2-931BF6AECF18@lakerest.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt356.oracle.com [141.146.40.156]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090206.4D81E984.0020,ss=1,fgs=0
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: Thu, 17 Mar 2011 10:57:51 -0000

On 03/16/11 10:14 PM, Randy Stewart wrote:

> Once you add a mechanism to add-a-stream, making using it
> to do these functionalities as well makes sense. You already
> have to define the mechanism.. why make the app redefine a similar
> mechanism....


By mechanism, are you referring to a new chunk?  Adding a
new chunk is not the same as defining the new protocol
handling of resetting SSN/TSN.  If the authors really think
that all the new mechanisms are needed and are being requested
by real use, the rationale behind the design and usage examples
must be provided in the draft.  It will be even better if
alternative design can be provided and compared with the current
choice so that this WG can see why the current choice is better.


> There is one other thing that can be done with this mechanism. If one
> were to combine AUTH+DYNAMIC_ADDRESSES+RECONFIG.. one could pretty
> easily move a transport connection from one machine to another without
> having to track sequence number space to closely...


Then please come back with another draft with the above thought
so that there is a real use of the mechanisms in this draft.
AFAIK from this WG mailing list, only stream addition has known
use.  The other mechanisms may be in use by some other protocols
but so far no concrete example has been given.  I don't think
this WG should adopt a standard with no use case.




-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From randall@lakerest.net  Thu Mar 17 05:01:17 2011
Return-Path: <randall@lakerest.net>
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 E4EA53A696E for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 05:01:17 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wEcB++Jt3gUv for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 05:01:17 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 9EC463A696D for <tsvwg@ietf.org>; Thu, 17 Mar 2011 05:01:16 -0700 (PDT)
Received: from [192.168.2.69] (pool-173-67-89-161.snfcca.dsl-w.verizon.net [173.67.89.161]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2HC2UJp036058 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 17 Mar 2011 08:02:41 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <4D81E97F.70309@oracle.com>
Date: Thu, 17 Mar 2011 08:02:24 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <88B3C8B8-6A73-4ABA-8809-96491A1F37A0@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DE97D.6010609@oracle.com>	<14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de>	<4D7F3C4B.7090303@oracle.com>	<0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de>	<4D809432.5050601@oracle.com>	<F3AF1842-07FB-4F06-8501-B2EDB1309438@lurchi.franken.de> <5FDD193A-B09F-400B-8EC2-931BF6AECF18@lakerest.net> <4D81E97F.70309@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
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: Thu, 17 Mar 2011 12:01:18 -0000

On Mar 17, 2011, at 6:59 AM, Kacheong Poon wrote:

> 
> 
> 
>> There is one other thing that can be done with this mechanism. If one
>> were to combine AUTH+DYNAMIC_ADDRESSES+RECONFIG.. one could pretty
>> easily move a transport connection from one machine to another without
>> having to track sequence number space to closely...
> 
> 
> Then please come back with another draft with the above thought
> so that there is a real use of the mechanisms in this draft.
> AFAIK from this WG mailing list, only stream addition has known
> use.  The other mechanisms may be in use by some other protocols
> but so far no concrete example has been given.  I don't think
> this WG should adopt a standard with no use case.

When I get some cycles I think I will do that. It will
take me a while though... I have some travels I will
be doing (like to Prague ;-D)

R

> 
> 
> 
> 
> -- 
> 
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
> 

-----
Randall Stewart
randall@lakerest.net





From bclaise@cisco.com  Thu Mar 17 06:42:22 2011
Return-Path: <bclaise@cisco.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 293CB3A696E; Thu, 17 Mar 2011 06:42:22 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F+Vws7M6igpK; Thu, 17 Mar 2011 06:42:19 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 69C973A68AD; Thu, 17 Mar 2011 06:42:19 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2HDIW0e009966; Thu, 17 Mar 2011 14:18:32 +0100 (CET)
Received: from [64.103.13.34] (dhcp-64-103-13-34.cisco.com [64.103.13.34]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2HDIQ8w003548; Thu, 17 Mar 2011 14:18:27 +0100 (CET)
Message-ID: <4D820A22.7050607@cisco.com>
Date: Thu, 17 Mar 2011 14:18:26 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Kacheong Poon <ka-cheong.poon@oracle.com>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<4D7DBDB2.7010102@cisco.com> <4D7DEA12.4000907@oracle.com>
In-Reply-To: <4D7DEA12.4000907@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Paul Aitken <paitken@cisco.com>, "ipfix@ietf.org" <ipfix@ietf.org>, Gerhard Muenz <muenz@net.in.tum.de>, "James M. Polk" <jmpolk@cisco.com>, Andrew Johnson <andrjohn@cisco.com>, tsvwg <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: Thu, 17 Mar 2011 13:42:22 -0000

> On 03/14/11 03:03 PM, Benoit Claise wrote:
>
>> I'm not a transport expert so I can't comment on the technical part.
>> However, there is a clear interest: the functionality in the draft is
>> required. "The IPFIX export per SCTP stream",
>> https://datatracker.ietf.org/doc/draft-ietf-ipfix-export-per-sctp-stream/ 
>> has
>> been sitting for 8 months in the RFC editor queue, waiting for this 
>> draft.
>
>
> I think only the new stream addition part is needed by IPFIX, right?
That's right.

Regards, Benoit.
> Is there any IETF protocol which requires the use of SCTP SSN/TSN
> reset?
>
>


From bdavie@cisco.com  Thu Mar 17 07:14:35 2011
Return-Path: <bdavie@cisco.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 1142B3A6998 for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 07:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 SRkQRsgbkU1h for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 07:14:33 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id CE95F3A695B for <tsvwg@ietf.org>; Thu, 17 Mar 2011 07:14:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=bdavie@cisco.com; l=3773; q=dns/txt; s=iport; t=1300371362; x=1301580962; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=XoIn3R2vabM0GggghUjDTbovFJK2ePViTMM83NA9wV0=; b=kJJU7ugvlm7iOjuwqvXs2omndJb5WMHE5iME87uOSV2orWl2YmVxrDO5 4gTdJuNDmWklu/Q/uemo+CNVyhYEnz4gRgDKWHl29uW6kouYDb4RW3xcI npqDD/0SLVzJkGrO042/8YEM2OTpUqqG/psqvyuTF8AEftusw16mdp/6c w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAH60gU2tJXHA/2dsb2JhbAClTnend5w4hWMEjF6MQQ
X-IronPort-AV: E=Sophos;i="4.63,199,1299456000"; d="scan'208";a="415391446"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by sj-iport-1.cisco.com with ESMTP; 17 Mar 2011 14:16:01 +0000
Received: from dhcp-161-44-173-105.cisco.com (dhcp-161-44-173-105.cisco.com [161.44.173.105]) by rcdn-core2-5.cisco.com (8.14.3/8.14.3) with ESMTP id p2HEG0a8021825;  Thu, 17 Mar 2011 14:16:01 GMT
Subject: Re: draft-polk-tsvwg-intserv-multiple-tspec-06
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bruce Davie <bdavie@cisco.com>
In-Reply-To: <4D81C686.1020701@erg.abdn.ac.uk>
Date: Thu, 17 Mar 2011 10:16:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4A17838-4D02-41FD-82A6-0EAD7DA07B8D@cisco.com>
References: <4D81C686.1020701@erg.abdn.ac.uk>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.1082)
Cc: tsvwg <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: Thu, 17 Mar 2011 14:14:35 -0000

On Mar 17, 2011, at 4:29 AM, Gorry Fairhurst wrote:

>=20
> I'm happy to discuss the future steps for this draft.
>=20
> I'll also take an action to check the status and then seek help from =
the RSVP directorate, the last note I saw from rsv-dir was 09/11/2010.
>=20

You'll note that Fred recently posted my note from Nov 1, 2010, and =
Scott Bradner just commented as a directorate member.

So, the 3 directorate members who have commented are in favor of =
adopting this draft.

Bruce

> I'll also try to sumarise where I see this draft has reached. I can't =
do this today though.
>=20
> Gorry
>=20
> -------- Original Message --------
> Subject: Re: draft-polk-tsvwg-intserv-multiple-tspec-06
> Date: Wed, 16 Mar 2011 15:23:32 -0700
> From: Fred Baker <fred@cisco.com>
> To: ken carlberg <carlberg@g11.org.uk>
> CC: tsvwg <tsvwg@ietf.org>
>=20
>=20
> On Mar 16, 2011, at 10:56 AM, ken carlberg wrote:
>=20
>> hello,
>>=20
>> my understanding is that the decision is still open as to whether =
this individual draft should become a working group draft.  I'd like to =
express my interest in making that migration.  My first comments on the =
draft came way back at the IETF-stockholm meeting in '09, where I =
brought up questions about multicast.  The current draft satisfies these =
questions, and other comments I have made since then.  I think this =
effort is properly baked for acceptance as a working group draft.
>>=20
>> But perhaps more importantly, I very much like its focus on =
optimization.  The bulk of the work we come across at the IETF either =
introduces new stuff, or augmentations to existing efforts.  Its =
refreshing to see work that focuses on optimizing something we already =
have.
>>=20
>> my 2 cents,
>>=20
>> -ken
>=20
> I think a relevant note is:
>=20
> On Nov 1, 2010, at 4:14 PM, Bruce Davie wrote:
>> On these 2 drafts:
>> On Oct 26, 2010, at 8:29 AM, Gorry Fairhurst wrote:
>>=20
>>> draft-polk-tsvwg-intserv-multiple-tspec
>>>    RSVP directorate to be consulted.
>>>    WG interest in this topic recorded at IETF-78.
>>>    Charter update would be needed to progress this work.
>>>    5 Reviews needed to determine energy/technical direction.
>>>    Author will update -04.
>>>    New revision expected.
>>>=20
>>> draft-lefaucheur-tsvwg-rsvp-multiple-preemption
>>>    RSVP directorate to be consulted.
>>>    WG needs to assess if this topic should be a work item.
>>=20
>> Two members of the RSVP directorate (myself and Lixia) have read =
these drafts and support their adoption by the WG. Below are some =
specific comments that I sent to the chairs, but I failed to send =
earlier to the WG. I believe at least one more directorate member has =
read these drafts but I've not received feedback one way or another =
about adoption from other directorate members.
>=20
> It would be good to know whether other members of the RSVP Directorate =
have commented. If there has been a charter discussion, I have managed =
to miss it.
>=20
> As to the draft itself, I think there is reason to support it, as we =
now have multi-rate codecs that can interact with it; rather than firing =
up, disturbing competing traffic to a degree that the codec data =
experiences loss and other traffic presumably does as well, and then =
backing off to a more acceptable rate (which is what rate-adaptive =
codecs do), it would be nice of the network could say "that will happen =
if you choose this rate, but if you choose this lower rate you will be =
better off." Having multiple T-Specs gives the network the option of =
making that choice on the first pas rather than taking binary decisions =
on multiple sequential decision steps.
>=20
>=20


From Michael.Tuexen@lurchi.franken.de  Thu Mar 17 12:51:44 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 3057A3A6A2E for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 12:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.834
X-Spam-Level: 
X-Spam-Status: No, score=-1.834 tagged_above=-999 required=5 tests=[AWL=0.110,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 0M8QhJF-z-aF for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 12:51:39 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id 6A03D3A6A1E for <tsvwg@ietf.org>; Thu, 17 Mar 2011 12:51:39 -0700 (PDT)
Received: from [192.168.1.113] (p508FC6B0.dip.t-dialin.net [80.143.198.176]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 4E22F1C0C0BD6; Thu, 17 Mar 2011 20:53:05 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4D81D7F1.5060102@oracle.com>
Date: Thu, 17 Mar 2011 20:53:04 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1BCF9911-0292-4DA3-AB75-FB9B96AE8778@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <D8826A52-1B36-404B-8A60-FEC7DC90EDB4@lurchi.franken.de> <4D8095EE.3060706@oracle.com> <79C91FD0-57BC-428E-A075-B580B4A3C57D@lurchi.franken.de> <4D81D7F1.5060102@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
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: Thu, 17 Mar 2011 19:51:44 -0000

On Mar 17, 2011, at 10:44 AM, Kacheong Poon wrote:

> On 03/16/11 08:04 PM, Michael T=FCxen wrote:
>=20
>> not sure you got the point I wanted to make. The text reads now (in =
CVS):
>=20
>=20
> I missed that.
>=20
>=20
>> I thought that something like the following would be more =
appropriate:
>=20
>=20
> Agreed.
I changed it. Also renames the timer and the sequence numbers... Should
now be consistent.

Best regards
Michael
>=20
>=20
>> 3.1.  RE-CONFIG Chunk
>>=20
>>    This document adds one new chunk type to SCTP.  The chunk has the
>>    following format:
>>=20
>>     0                   1                   2                   3
>>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    | Type =3D 0x82   |  Chunk Flags  |      Chunk Length             =
|
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    \                                                               \
>>    /                  Re-configuration Parameter                   /
>>    \                                                               \
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    \                                                               \
>>    /            Re-configuration Parameter (optional)              /
>>    \                                                               \
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>=20
>> ...
>>    Re-configuration Parameter
>>       This field holds a Re-configuration Request Parameter or a
>>       Re-configuration Response Parameter.
>>=20
>>    Note that each RE-CONFIG chunk holds at least one parameter and at
>>    most two parameters.  Only the following combinations are allowed:
>>=20
>>    1.  Outgoing SSN Reset Request Parameter.
>>=20
>>    2.  Incoming SSN Reset Request Parameter.
>>=20
>>    3.  Outgoing SSN Reset Request Parameter, Incoming SSN Reset =
Request
>>        Parameter.
>>=20
>>    4.  SSN/TSN Reset Request Parameter.
>>=20
>>    5.  Add Outgoing Streams Request Parameter.
>>=20
>>    6.  Re-configuration Response Parameter.
>>=20
>>    7.  Re-configuration Response Parameter, Outgoing SSN Reset =
Request
>>        Parameter.
>>=20
>>    8.  Re-configuration Response Parameter, Re-configuration Response =
Parameter.
>=20
>=20
>=20
>=20
> --=20
>=20
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
>=20


From Michael.Tuexen@lurchi.franken.de  Thu Mar 17 13:08:32 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 586CB3A69F5 for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 13:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.153
X-Spam-Level: 
X-Spam-Status: No, score=0.153 tagged_above=-999 required=5 tests=[AWL=-1.892,  BAYES_00=-2.599, FRT_STOCK2=3.988, MIME_8BIT_HEADER=0.3, 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 JRDDJXzVUSsg for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 13:08:31 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id 4F0663A69C7 for <tsvwg@ietf.org>; Thu, 17 Mar 2011 13:08:30 -0700 (PDT)
Received: from [192.168.1.113] (p508FC6B0.dip.t-dialin.net [80.143.198.176]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 29FCF1C0C0BD6; Thu, 17 Mar 2011 21:09:57 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4D81E2D1.3010201@oracle.com>
Date: Thu, 17 Mar 2011 21:09:56 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <41FD39DE-A3C4-4A01-BD0E-16EA0F7525D7@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de> <4D809432.5050601@oracle.com> <F3AF1842-07FB-4F06-8501-B2EDB1309438@lurchi.franken.de> <4D81E2D1.3010201@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
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: Thu, 17 Mar 2011 20:08:32 -0000

On Mar 17, 2011, at 11:30 AM, Kacheong Poon wrote:

> On 03/16/11 08:32 PM, Michael T=FCxen wrote:
>=20
>> But the above is not sufficient. Resetting a stream does not
>> only reset the counter but also
>> * signals that it is requested
>> * acknowledges that is has been performed
>=20
>=20
> The above is started by the app layer, right?  So
> the app layer already needs to perform the action.  It
> is not something which is initiated by the transport
> layer and must be done in the transport layer.  It is
> an app layer protocol.
The request is initiated by the app (a setsockopt call), but
it does not perform the request (creating a packet, sending it,
waiting for the response, parsing the response). In particular
the other side does not have to perform anything.
>=20
>=20
>> So if you want to implement it at the application layer,
>> you need to define at least two application layer messages
>> and the appropriate procedures. So you need to extend the
>> application layer and get the procedures right.
>> So, yes it can be done at the application layer, but
>> * each application protocol must re-implement the same mechanism.
>> * you need to extend each application protocol.
>> Doing it at the transport layer, requires the mechanism
>> only to be implemented once and no change of the application
>> protocol.
>=20
>=20
> Why is it more appropriate to do it at the transport
> layer?  There are many examples of having such a layer
> below app layer and above transport which do this sort of
> things.  App writers don't need to reinvent the wheel,
> nor do transport protocol designers.  I still don't see why
> doing it at the transport layer is better or require less
> code to implement the signaling right.
>=20
> In fact, one can argue that having it in transport layer
> removes the flexibility of supporting many different types
> of semantics which  app layers require.  I think you won't
> agree to the idea that SCTP should support all types of
> signaling any apps may require, right?  This is not a
> sound design choice.  This just makes SCTP bigger and
> bigger.  It will be a kitchen sink of all sorts of app
> layer protocol mechanism.  It seems that you are arguing
> that there should be no app layer protocol and the transport
> layer should provide every conceivable service any app may
> require.  Do other people in this WG also think this way?
At least I do not think so...
The service we are discussing is not an arbitrary service
an application requires, but it is tightly related to the
streams.

I think it can be described extending the service SCTP
provides from:
* a static number of non-resettable uni-directional message channels
to
* a dynamic number of resettable uni-directional message channels

I think this is not an arbitrary service...
>=20
>=20
>> I think the question is not if it is necessary, but which layer
>> is the most appropriate.
>=20
>=20
> Agreed.  Is it really hard to do that in the app layer?
> As a previous TCP example, head of line blocking cannot
> be avoided without opening multiple TCP connections.  And
> doing so has congestion impact on the network.  It is this
> sort of things which is appropriate to do at the transport
> layer.
>=20
>=20
>> As with my example from two days or so ago, it is *not necessary*
>> to do reordering at the transport layer. We could have also
>> left that feature for the application and only support unordered
>> delivery in the transport layer. But we didn't (which is good).
>=20
>=20
> Well, I guess it is expected that a connection oriented
> reliable transport protocol at least provides in order
> delivery.  If it does not handle re-ordering, it cannot be
> called such a protocol.
This is about terminology. I can imagine that it might make
sense to have a transport protocol ensures that all messages
sent are received exactly once, no matter in which sequence.

In SCTP, this is using only un-orered messages, but not using
PR-SCTP.
>=20
>=20
>> So I think the question is: What does provide a stream for
>> the application layer.
>> * Just a static channel which provides in-sequence delivery
>>   This might have been the original intention (from SIGTRAN),
>>   but this does not require exposing TSN/SSN.
>>=20
>> I think people started looking at TSN/SSN, since we are
>> exposing it and, when using outside of the SIGTRAN applications,
>> they want to have something like
>> * A dynamic channel which provides in-sequence delivery.
>> Here dynamic means it can be added / removed / reused.
>=20
>=20
> While the meaning of adding and removing an SCTP stream is
> clear, I think "reuse" needs to be defined carefully.  An
> app can use a stream and then not use it for a while.  There
> is nothing to prevent an app to re-use it later.
It is especially about the signalling of "I'm done with this stream".
>=20
>=20
>> Removing is hard, so that is why we left it out. I also argued
>> at some time, the you do not need to add streams, just start
>> the association with enough streams. But app writers see it
>> differently.
>=20
>=20
> I think there is no need to "remove" a stream.  An app can
> choose not to use any stream.  This is not true if an app
> wants to use more streams than it thinks it needs at the start
> of an association.  There is no mechanism to do it now.
I agree with you. We should not have a remove stream functionality.
>=20
>=20
>> So being able to add and reset streams seems a good compromise
>> for me. It can be added relatively simple to SCTP and it
>> provides almost all the app writers need.
>=20
>=20
> Can you explain why resetting SSN/TSN is equivalent to
> re-using a stream or the association?  BTW, there is still
> no example given to the use of resetting TSN.  I think this
> must be added to the draft.
Regarding the SSN/TSN reset, see Randys examples.
>=20
>=20
>> As said above, you can put it at either layer. We just seem
>> to disagree, where the more appropriate layer is...
>=20
>=20
> So far, I think the key point you've raised to support
> doing it at the transport layer is that it can then be
> used by any apps.  I think doing it in a library achieves
> the same thing.  Don't you agree?
Somewhat. You need to define a protocol for that. Including
negotiating for it. So in case of HTTP proxy communication,
it might be hard to do this in an interoperable way without
extending the HTTP, i.e. the application protocol. So doing
What you could do is to use HTTP/Kacheongs layer/SCTP.
But what would you send initially to figure out that you peer
talks HTTP/Kacheongs layer/SCTP and not only HTTP/SCTP?

Best regards
Michael
>=20
>=20
>> Well, I thought for the application it is only important
>> to know if the request was successful, denied or failed.
>> It also uses a field which is there anyway.
>>=20
>> But if you prefer, we can add a field which contains the
>> return code, which was on the wire. Not sure if it really
>> helps.
>=20
>=20
> No preference.  Just that it is not clear in the text what
> the difference between denied and failed is since both
> are failures.
>=20
>=20
> --=20
>=20
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
>=20


From lberger@labn.net  Thu Mar 17 15:44:59 2011
Return-Path: <lberger@labn.net>
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 DF4613A6B31 for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 15:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.093
X-Spam-Level: 
X-Spam-Status: No, score=-102.093 tagged_above=-999 required=5 tests=[AWL=0.172, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 smtVSZ07W2P3 for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 15:44:58 -0700 (PDT)
Received: from cpoproxy3-pub.bluehost.com (cpoproxy3-pub.bluehost.com [67.222.54.6]) by core3.amsl.com (Postfix) with SMTP id B2EC83A69E5 for <tsvwg@ietf.org>; Thu, 17 Mar 2011 15:44:58 -0700 (PDT)
Received: (qmail 14741 invoked by uid 0); 17 Mar 2011 22:46:26 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 17 Mar 2011 22:46:26 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=lHpBynmOMF2Je0jBpnlvoSKCOKN03rSu8z8PHZWlGNePA75+L1jk/o1vYpEYcJ5dw2wn3toWdCLaACQpllu7m8T5tIyB4ttiFdEILSG6SaQBh4NllEtdsn9+/zP2nK0M;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1Q0Lxa-000082-Df; Thu, 17 Mar 2011 16:46:26 -0600
Message-ID: <4D828F41.2010703@labn.net>
Date: Thu, 17 Mar 2011 18:46:25 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Bruce Davie <bdavie@cisco.com>,  Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Subject: Re: draft-polk-tsvwg-intserv-multiple-tspec-06
References: <4D81C686.1020701@erg.abdn.ac.uk> <A4A17838-4D02-41FD-82A6-0EAD7DA07B8D@cisco.com>
In-Reply-To: <A4A17838-4D02-41FD-82A6-0EAD7DA07B8D@cisco.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: tsvwg <tsvwg@ietf.org>, draft-polk-tsvwg-intserv-multiple-tspec@tools.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: Thu, 17 Mar 2011 22:45:00 -0000

I too think this is useful work and worth bringing into the WG.

Authors,

I have some comments/questions that can be addressed as the draft moves
forward (and don't need discussing if the draft isn't):

1) a real nit:
I suspect that the <flow descriptor list> RBNF is broken, and
[MULTI_FLOWSPEC] should be [ <MULTI_FLOWSPEC> ] .  (You might want to
add a reference to 5511 too.)

2) I could see this as a more generally applicable problem, in
particular it could apply to the non-IntServ class types supported by
RSVP (TSPEC/FLOWSPEC).  What do you think about having the MULT_xxSPEC
objects being defined solely on the RSVP level (perhaps using
subobjects) rather than as defined now which is a change to RSVP and
IntServ?

Lou

PS I'm on the rsv-dir mailing list, but not listed on the web page so
have no idea if this means this is a comment as a directorate member or not.

PPS I won't be in the Prague session as I'll be chairing a WG at the
same time, but do support this work as a WG document if the topic comes up.


On 3/17/2011 10:16 AM, Bruce Davie wrote:
> 
> On Mar 17, 2011, at 4:29 AM, Gorry Fairhurst wrote:
> 
>>
>> I'm happy to discuss the future steps for this draft.
>>
>> I'll also take an action to check the status and then seek help from the RSVP directorate, the last note I saw from rsv-dir was 09/11/2010.
>>
> 
> You'll note that Fred recently posted my note from Nov 1, 2010, and Scott Bradner just commented as a directorate member.
> 
> So, the 3 directorate members who have commented are in favor of adopting this draft.
> 
> Bruce
> 
>> I'll also try to sumarise where I see this draft has reached. I can't do this today though.
>>
>> Gorry
>>
>> -------- Original Message --------
>> Subject: Re: draft-polk-tsvwg-intserv-multiple-tspec-06
>> Date: Wed, 16 Mar 2011 15:23:32 -0700
>> From: Fred Baker <fred@cisco.com>
>> To: ken carlberg <carlberg@g11.org.uk>
>> CC: tsvwg <tsvwg@ietf.org>
>>
>>
>> On Mar 16, 2011, at 10:56 AM, ken carlberg wrote:
>>
>>> hello,
>>>
>>> my understanding is that the decision is still open as to whether this individual draft should become a working group draft.  I'd like to express my interest in making that migration.  My first comments on the draft came way back at the IETF-stockholm meeting in '09, where I brought up questions about multicast.  The current draft satisfies these questions, and other comments I have made since then.  I think this effort is properly baked for acceptance as a working group draft.
>>>
>>> But perhaps more importantly, I very much like its focus on optimization.  The bulk of the work we come across at the IETF either introduces new stuff, or augmentations to existing efforts.  Its refreshing to see work that focuses on optimizing something we already have.
>>>
>>> my 2 cents,
>>>
>>> -ken
>>
>> I think a relevant note is:
>>
>> On Nov 1, 2010, at 4:14 PM, Bruce Davie wrote:
>>> On these 2 drafts:
>>> On Oct 26, 2010, at 8:29 AM, Gorry Fairhurst wrote:
>>>
>>>> draft-polk-tsvwg-intserv-multiple-tspec
>>>>    RSVP directorate to be consulted.
>>>>    WG interest in this topic recorded at IETF-78.
>>>>    Charter update would be needed to progress this work.
>>>>    5 Reviews needed to determine energy/technical direction.
>>>>    Author will update -04.
>>>>    New revision expected.
>>>>
>>>> draft-lefaucheur-tsvwg-rsvp-multiple-preemption
>>>>    RSVP directorate to be consulted.
>>>>    WG needs to assess if this topic should be a work item.
>>>
>>> Two members of the RSVP directorate (myself and Lixia) have read these drafts and support their adoption by the WG. Below are some specific comments that I sent to the chairs, but I failed to send earlier to the WG. I believe at least one more directorate member has read these drafts but I've not received feedback one way or another about adoption from other directorate members.
>>
>> It would be good to know whether other members of the RSVP Directorate have commented. If there has been a charter discussion, I have managed to miss it.
>>
>> As to the draft itself, I think there is reason to support it, as we now have multi-rate codecs that can interact with it; rather than firing up, disturbing competing traffic to a degree that the codec data experiences loss and other traffic presumably does as well, and then backing off to a more acceptable rate (which is what rate-adaptive codecs do), it would be nice of the network could say "that will happen if you choose this rate, but if you choose this lower rate you will be better off." Having multiple T-Specs gives the network the option of making that choice on the first pas rather than taking binary decisions on multiple sequential decision steps.
>>
>>
> 
> 
> 
> 
> 

From bidulock@openss7.org  Thu Mar 17 17:59:38 2011
Return-Path: <bidulock@openss7.org>
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 4070E3A6AB1 for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 17:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.271
X-Spam-Level: 
X-Spam-Status: No, score=-2.271 tagged_above=-999 required=5 tests=[AWL=-0.028, 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 qg1jrCa52DzV for <tsvwg@core3.amsl.com>; Thu, 17 Mar 2011 17:59:36 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [206.75.119.236]) by core3.amsl.com (Postfix) with ESMTP id 7C5F43A6981 for <tsvwg@ietf.org>; Thu, 17 Mar 2011 17:59:35 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p2I114BI020840 for <tsvwg@ietf.org>; Thu, 17 Mar 2011 19:01:04 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p2I114sQ002247 for <tsvwg@ietf.org>; Thu, 17 Mar 2011 19:01:04 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id p2I113ue002246 for tsvwg@ietf.org; Thu, 17 Mar 2011 19:01:03 -0600
Date: Thu, 17 Mar 2011 19:01:03 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: tsvwg@ietf.org
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Message-ID: <20110318010103.GA1531@openss7.org>
Mail-Followup-To: tsvwg@ietf.org
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bidulock@openss7.org
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: Fri, 18 Mar 2011 00:59:38 -0000

James,

I'd like to weigh in on this draft.

I have review the draft and, in summary, I do not think that it
is sufficient to proceed and needs significant rework before
doing so.  I have the following issues with the current draft:

1) There is no ability to "close" (remove) a stream.

2) The protocol mechanisms proposed are overly complex.

3) The protocol mechanisms proposed are lacking.

(More detail on these issues at the end of this long note.)

On the plus side, just about any application that uses more than
one stream can benefit from the capability to dynamically
allocate and deallocate a stream to and from an association.
Without this capability, one must pre-allocate the maximum
number of streams at association establishment.  An application,
such as SIGTRAN, can have difficulty in predicting the maximum
number of required streams as association initialization, and
may not know the number of required streams until a number of
them are already in active use.

For example, M2UA would prefer to have one stream per interface
identifier (IID), however, the number of interface identifiers
(IIDs) supported by a given association changes over time.
Dropping the association and reopening it to reallocate the
number of available streams is far too disruptive to be usable
for M2UA: message loss and network degradation can occur from
the resulting changeovers.  Currently, M2UA multiplexes the IIDs
over the available streams, with the result that HOL blocking on
a stream affects more than one IID, which is bad, because M2UA
has no knowledge of which IIDs belong to a link-set, and one IID
may attempt to changeover to another IID in the same stream.

So, I agree with the authors that the concept is generally
useful.

As to whether it should be implemented in the transport layer
rather than the application or shim layer, there is one aspect
(when the draft is done correctly) that makes the transport
layer the appropriate place.  The SCTP stack can free the
transport layer resources associated with a stream when it is
"closed".  In particular, the current SSN and data fragmentation
state.

So, I agree with the authors that the best placement is in the
transport layer, but only if the ability to "close" a stream is
provided.

1) There is no ability to "close" (remove) a stream.

   Although, from discussions on the list, the major use of this
   capability is to be able to "open" and "close" a stream
   independent of opening and closing the association.

   The draft falls short of addressing that capability.  I only
   has some ability to add a stream and reset an SSN.

   Streams cannot be "closed" (removed).  This is a significant
   deficiency.  If 65,000 streams are "opened" (added) and then
   no longer required, the SCTP stack cannot free the unused
   resources associated with the 65,000 streams.

   Resetting the SSN can be viewed simply as "closing" and
   "opening" (or possibly "reopening") a stream.  If closing and
   opening are provided, resetting SSN is simply a natural
   consequence of reopening a stream.

2) The protocol mechanisms proposed are too complex.

   The draft proposes what I would call an "out-of-band"
   solution for stream reset.  Chunks and parameters are
   defined, a procedural state machine and timers.  There are
   difficulties with the complexity of this approach.

   A simpler approach is what I would call an "in-band"
   approach, where a chunk is treated by the stream logic in
   SCTP just as any other ordered stream DATA chunk.  One to
   close the stream would simply be transmitted after the last
   ordered DATA chunk on the stream.  To open a stream, one
   would be sent before the first ordered DATA chunk on the
   stream.  Then no extra state machine nor timers are required.

3) The protocol mechanisms proposed are lacking.

   As a ramification of choosing an "out-of-band" approach, the
   draft requires that all data for a stream be held until the
   "out-of-band" procedure completes (for resetting an SSN).
   This can cause transmit buffer blocking of the entire
   association and is unsuitable for high performance
   applications.

   With an "in-band" approach, reuse of a stream can be
   immediate (simple receipt of the in-band OPEN chunk is
   sufficient to reopen (reset) the stream for reuse.

Because of these issues, I think that progressing this draft is
premature.  I would like an opportunity to discuss an alternate
"in-band" approach.  (This note is already too long...)

--brian

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

From Michael.Tuexen@lurchi.franken.de  Fri Mar 18 01:18:37 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 39C293A67DB for <tsvwg@core3.amsl.com>; Fri, 18 Mar 2011 01:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.734
X-Spam-Level: 
X-Spam-Status: No, score=-1.734 tagged_above=-999 required=5 tests=[AWL=0.210,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 1MN72uA-aepg for <tsvwg@core3.amsl.com>; Fri, 18 Mar 2011 01:18:36 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id 236093A66B4 for <tsvwg@ietf.org>; Fri, 18 Mar 2011 01:18:34 -0700 (PDT)
Received: from [192.168.1.113] (p508FCEC7.dip.t-dialin.net [80.143.206.199]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 6D3DF1C0C0BD6; Fri, 18 Mar 2011 09:19:59 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <20110318010103.GA1531@openss7.org>
Date: Fri, 18 Mar 2011 09:19:58 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <E21487FF-A3D4-44CF-AB97-3FE04B4804CD@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <20110318010103.GA1531@openss7.org>
To: bidulock@openss7.org
X-Mailer: Apple Mail (2.1082)
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: Fri, 18 Mar 2011 08:18:37 -0000

On Mar 18, 2011, at 2:01 AM, Brian F. G. Bidulock wrote:

> James,
> 
> I'd like to weigh in on this draft.
> 
> I have review the draft and, in summary, I do not think that it
> is sufficient to proceed and needs significant rework before
> doing so.  I have the following issues with the current draft:
> 
> 1) There is no ability to "close" (remove) a stream.
> 
> 2) The protocol mechanisms proposed are overly complex.
> 
> 3) The protocol mechanisms proposed are lacking.
> 
> (More detail on these issues at the end of this long note.)
> 
> On the plus side, just about any application that uses more than
> one stream can benefit from the capability to dynamically
> allocate and deallocate a stream to and from an association.
> Without this capability, one must pre-allocate the maximum
> number of streams at association establishment.  An application,
> such as SIGTRAN, can have difficulty in predicting the maximum
> number of required streams as association initialization, and
> may not know the number of required streams until a number of
> them are already in active use.
> 
> For example, M2UA would prefer to have one stream per interface
> identifier (IID), however, the number of interface identifiers
> (IIDs) supported by a given association changes over time.
> Dropping the association and reopening it to reallocate the
> number of available streams is far too disruptive to be usable
> for M2UA: message loss and network degradation can occur from
> the resulting changeovers.  Currently, M2UA multiplexes the IIDs
> over the available streams, with the result that HOL blocking on
> a stream affects more than one IID, which is bad, because M2UA
> has no knowledge of which IIDs belong to a link-set, and one IID
> may attempt to changeover to another IID in the same stream.
> 
> So, I agree with the authors that the concept is generally
> useful.
> 
> As to whether it should be implemented in the transport layer
> rather than the application or shim layer, there is one aspect
> (when the draft is done correctly) that makes the transport
> layer the appropriate place.  The SCTP stack can free the
> transport layer resources associated with a stream when it is
> "closed".  In particular, the current SSN and data fragmentation
> state.
> 
> So, I agree with the authors that the best placement is in the
> transport layer, but only if the ability to "close" a stream is
> provided.
> 
> 1) There is no ability to "close" (remove) a stream.
> 
>   Although, from discussions on the list, the major use of this
>   capability is to be able to "open" and "close" a stream
>   independent of opening and closing the association.
> 
>   The draft falls short of addressing that capability.  I only
>   has some ability to add a stream and reset an SSN.
> 
>   Streams cannot be "closed" (removed).  This is a significant
>   deficiency.  If 65,000 streams are "opened" (added) and then
>   no longer required, the SCTP stack cannot free the unused
>   resources associated with the 65,000 streams.
> 
>   Resetting the SSN can be viewed simply as "closing" and
>   "opening" (or possibly "reopening") a stream.  If closing and
>   opening are provided, resetting SSN is simply a natural
>   consequence of reopening a stream.
Hi Brian,

removing streams is much more difficult than adding streams.
Assume that you have 10 streams, SID=0, ..., SID=9. Now you want
to "close" the stream SID=1. Then you need to renumber all streams
with SID > 1 or handle holes in the SIDs. Handling holes requires
a major change, since some implementations handle streams by using
an array... 
> 
> 2) The protocol mechanisms proposed are too complex.
> 
>   The draft proposes what I would call an "out-of-band"
>   solution for stream reset.  Chunks and parameters are
>   defined, a procedural state machine and timers.  There are
>   difficulties with the complexity of this approach.
> 
>   A simpler approach is what I would call an "in-band"
>   approach, where a chunk is treated by the stream logic in
>   SCTP just as any other ordered stream DATA chunk.  One to
>   close the stream would simply be transmitted after the last
>   ordered DATA chunk on the stream.  To open a stream, one
>   would be sent before the first ordered DATA chunk on the
>   stream.  Then no extra state machine nor timers are required.
> 
> 3) The protocol mechanisms proposed are lacking.
> 
>   As a ramification of choosing an "out-of-band" approach, the
>   draft requires that all data for a stream be held until the
>   "out-of-band" procedure completes (for resetting an SSN).
>   This can cause transmit buffer blocking of the entire
>   association and is unsuitable for high performance
>   applications.
> 
>   With an "in-band" approach, reuse of a stream can be
>   immediate (simple receipt of the in-band OPEN chunk is
>   sufficient to reopen (reset) the stream for reuse.
> 
> Because of these issues, I think that progressing this draft is
> premature.  I would like an opportunity to discuss an alternate
> "in-band" approach.  (This note is already too long...)
Hmm. An in-band approach. Something like a DATA chunk with a
specific flag set, or something else?

The problem with the in-band approach I see is that the stream
is not a uni-directional channel, where *all* messages are
in a sequence, since we have unordered delivery.

And what would you send if there is not DATA message to piggyback
the reset info?

I think you need some message independent from user data on
the wire to signal that you reset the stream.

Best regards
Michael
> 
> --brian
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 


From ietfc@btconnect.com  Fri Mar 18 11:42:15 2011
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 5EB683A6A29 for <tsvwg@core3.amsl.com>; Fri, 18 Mar 2011 11:42:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.681
X-Spam-Level: 
X-Spam-Status: No, score=-1.681 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 V3LWGUgtmKEa for <tsvwg@core3.amsl.com>; Fri, 18 Mar 2011 11:42:14 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr07.btconnect.com [213.123.20.125]) by core3.amsl.com (Postfix) with ESMTP id 9CC153A69B7 for <tsvwg@ietf.org>; Fri, 18 Mar 2011 11:42:13 -0700 (PDT)
Received: from host217-44-145-106.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.106]) by c2bthomr07.btconnect.com with SMTP id CJD65600; Fri, 18 Mar 2011 18:43:26 +0000 (GMT)
Message-ID: <024801cbe593$4f2d1960$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Randy Stewart" <randall@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net> <29AEBA37-6157-44E9-8FD7-B44023DF6CD7@lakerest.net>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Date: Fri, 18 Mar 2011 18:38:13 +0100
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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4D83A7C6.0011, actions=TAG
X-Junkmail-Status: score=10/50, host=c2bthomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020A.4D83A7D6.0186,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: "James M. Polk" <jmpolk@cisco.com>, tsvwg <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: Fri, 18 Mar 2011 18:42:15 -0000

Randy

Yes, I did get your e-mail and did understand that you would implement it
in -10 after WGLC.  My point was rather a process one, that I thought
that at least one earlier version of the I-D came out too soon, before
consensus had been reached on the list, leading to extra work and
the possibility of errors.

And I see something of the same now, that K. Poon comes up with
suggestions and you say yes good we will do that.  I think no, that that
is premature, wait for others to catch up and comment.  And if noone
comments, then I suspect that there is no consensus and that the
change should not be made.  At WGLC time, in my book, you need
a solid reason to change, not a 'good idea' from one participant.
At least give others a chance to say yea or nay.

For myself, I think that punctuation in a short label is a bad thing ie
RE-CONFIG
is always a mistake.  Some will forget it, some will misplace it.  It can
only create errors (a longer label, eg channel-binding, is a different matter).

And if the suggested change has not come up in the 10 previous iterations
of the I-D, then I suspect that the benefit of it is not great, not enough to be
worth making it at this time; with my previous suggestions, you did miss out
some, for all the power of sed, grep etc, so I suspect that some will be missed
now, which will be worse than either the old wording or new.

Tom Petch

----- Original Message -----
From: "Randy Stewart" <randall@lakerest.net>
To: "t.petch" <ietfc@btconnect.com>
Cc: "tsvwg" <tsvwg@ietf.org>; "James M. Polk" <jmpolk@cisco.com>
Sent: Wednesday, March 16, 2011 3:05 PM
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues



On Mar 16, 2011, at 4:31 AM, t.petch wrote:

> ----- Original Message -----
> From: "James M. Polk" <jmpolk@cisco.com>
> To: "tsvwg" <tsvwg@ietf.org>
> Sent: Sunday, March 13, 2011 9:48 PM
>
>> TSVWG
>>
>> The WG chairs have determined the WGLC for our SCTP Stream
>> Reconfiguration ID continues (i.e., it has not concluded at the 2
>> week window) due to lack of feedback to the list. No one has
>> commented in a review format that they believe this ID should
>> progress. No one has even sent a note merely saying this ID in its
>> present form is good to go. That lack of any feedback is troubling
>> and could be a sign of a lack of interest in this ID.
>>
>> The WG chairs like the idea of (and within) this draft, but we need
>> transport experts to tell us this, and if the ID in its present form
>> is good enough to implement to without those implementations having
>> errors or causing bad behavior in SCTP because of how the ID is
>> written (focusing mostly on the instructions to implementers in the ID).
>>
>> We chairs want folks to show or assert they have reviewed this ID and
>> give feedback to the list (and not unicast to the chairs). This ID
>> cannot progress without that feedback.
>
> I am sitting on my hands because I did not consider the I-D ready for last
call
> but also, I do not have a view as to whether or not this I-D will be
> implemented,


Can't say on other implementations but it is in FreeBSD ;-)

> whether or not the additional function is worth standardising - I simply do
not
> have the contacts to make a judgement on this.
>
> I did comment on a previous version, and the comment was not resolved so I
> decided to wait
> until it was before commenting further, be that at IETF LC if so it be.  I did
> get
> a response about not wanting to push out too many revisions but, perversely,


Tom, I did too respond to your comment.. and the update was posted on the
mailing
list... Did you not receive the email (sometimes my emails do not get through it
would appear)..  I can wander back on the mailing list archives and find it ...
let me see:

Here it is from Feb 9th:
********************************************************************************
*******
Tom:

Just to let you know I did NOT forget about this... Here is the text that is
waiting in the xml for the -10 revision:
***********************************************************
  When a peer endpoint requests a Incoming SSN Reset Request it is
  possible that the local endpoint has just sent an Outgoing SSN Reset
  Request on the same stream and has not yet received a response.  In
  such a case the local endpoint MUST do the following:

  1) If the stream reset overlaps the outstanding request completely
     respond to the requestor with an acknowledgment indicating that
     there was 'Nothing to do'.

  2) Otherwise process the stream reset request normally responding to
     the requestor with an acknowledgment.

  It is also possible that the Incoming request will arrive after the
  Outgoing SSN Reset Request just completed.  In such a case the local
  endpoint MUST do the following:

  1) If the stream reset overlaps the outstanding request completely
     all of the streams being requested will be already set to 0.  If
     so, the local endpoint SHOULD send back a Stream Reset Response
     with the success code "Nothing to do".

  2) Otherwise process the stream reset request normally responding to
     the requestor an acknowledgment.

  Note that in either race condition the local endpoint could
  optionally also perform the reset.  This would result in streams that
  are already at sequence 0 being reset again to 0 which would cause no
  harm to the application but will add an extra message to the network.

  Note also that in any of the race conditions listed above the
  receiver MUST NOT send more than one response.  In other words two
  responses MUST NOT be sent for the same request.

*******************************************************************

When we get any other comments after LC I will issue the updated draft with the
above...

If you would like further changes or this does not satisfy your comments below
let me know.. you can even send suggested text :-)

Best wishes

R
On Jan 15, 2011, at 6:49 AM, t.petch wrote:

> I like the change to 5.2.3 but think that it needs to go further.
>
> -08 split out two cases,
>
> Incoming SSN Reset Request received but no response yet to the Outgoing
request
> Incoming SSN Reset Request received after response to the Outgoing request
>
> assuming that the Incoming and Outgoing requests have overlapping stream
> numbers.
>
> -09 subdivides the first case into overlaps completely and overlaps partially
> but
> I think that the second case is also in need of subdivision in the same way.
>
> And, a point of clarification, in any of the four cases, is it required to
send
> just
> the one response, ie you cannot send two responses in the partial overlap
case,
> one saying no-op and the will do (or won't do!)?
>
>
> Tom Petch
>
********************************************************************************
********

You never replied to that so I had assumed you were happy with the changes.. if
not
I would be more than glad to hear your suggested changes...


R


> that is the problem, that the latest revision was pushed out too soon, before
> the comments on the previous version had been adequately (IMO) resolved.
> Which, in turn, brings us full circle, that insufficient interest was
expressed
> by the WG in that previous version to get the comments resolved; so should
> this progress to RFC or no, is it worth standardising? I have no basis on
which
> to say.
>
> Tom Petch
>
>> James & Gorry
>> TSVWG chairs
>>
>>
>> At 10:07 PM 2/7/2011, James M. Polk wrote:
>>> TSVWG
>>>
>>> I am starting the WGLC for
>>>
>>> "Stream Control Transmission Protocol (SCTP) Stream Reconfiguration"
>>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-strrst/
>>>
>>> this is a 2 week WGLC, ending February 22nd, 2011 or when the chairs
>>> feel the WG has reviewed the draft and reached consensus to progress
>>> towards the ADs with the goal of becoming a proposed standard (PS) RFC.
>>>
>>> The chairs require substantive feedback from the WG regarding this
>>> draft before consensus can be called.
>>>
>>> I will be the document shepherd.
>>>
>>> James
>>> TSVWG chair
>>
>

-----
Randall Stewart
randall@lakerest.net





From Michael.Tuexen@lurchi.franken.de  Fri Mar 18 12:43:38 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 0B3153A691C for <tsvwg@core3.amsl.com>; Fri, 18 Mar 2011 12:43:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.034
X-Spam-Level: 
X-Spam-Status: No, score=-1.034 tagged_above=-999 required=5 tests=[AWL=0.309,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, 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 FSkByyZXvq9H for <tsvwg@core3.amsl.com>; Fri, 18 Mar 2011 12:43:36 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id CF13E3A6842 for <tsvwg@ietf.org>; Fri, 18 Mar 2011 12:43:35 -0700 (PDT)
Received: from [192.168.1.113] (p5481C262.dip.t-dialin.net [84.129.194.98]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id EE2D01C0B461B; Fri, 18 Mar 2011 20:45:02 +0100 (CET)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
X-Priority: 3
In-Reply-To: <024801cbe593$4f2d1960$4001a8c0@gateway.2wire.net>
Date: Fri, 18 Mar 2011 20:45:01 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <646C4AFE-1AAE-419B-BB6D-8670D292F563@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net> <29AEBA37-6157-44E9-8FD7-B44023DF6CD7@lakerest.net> <024801cbe593$4f2d1960$4001a8c0@gateway.2wire.net>
To: t.petch <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.1082)
Cc: "James M. Polk" <jmpolk@cisco.com>, tsvwg <tsvwg@ietf.org>, Randy Stewart <randall@lakerest.net>
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: Fri, 18 Mar 2011 19:43:38 -0000

On Mar 18, 2011, at 6:38 PM, t.petch wrote:

> Randy
>=20
> Yes, I did get your e-mail and did understand that you would implement =
it
> in -10 after WGLC.  My point was rather a process one, that I thought
> that at least one earlier version of the I-D came out too soon, before
> consensus had been reached on the list, leading to extra work and
> the possibility of errors.
>=20
> And I see something of the same now, that K. Poon comes up with
> suggestions and you say yes good we will do that.  I think no, that =
that
> is premature, wait for others to catch up and comment.  And if noone
> comments, then I suspect that there is no consensus and that the
> change should not be made.  At WGLC time, in my book, you need
> a solid reason to change, not a 'good idea' from one participant.
> At least give others a chance to say yea or nay.
>=20
> For myself, I think that punctuation in a short label is a bad thing =
ie
> RE-CONFIG
> is always a mistake.  Some will forget it, some will misplace it.  It =
can
> only create errors (a longer label, eg channel-binding, is a different =
matter).
>=20
> And if the suggested change has not come up in the 10 previous =
iterations
> of the I-D, then I suspect that the benefit of it is not great, not =
enough to be
> worth making it at this time; with my previous suggestions, you did =
miss out
> some, for all the power of sed, grep etc, so I suspect that some will =
be missed
> now, which will be worse than either the old wording or new.
Hi Tom,

I can send you the current version, which we have in CVS and you can =
have a look.
While doing the changes I fixed some editorial errors which I missed =
earlier.

Let me know if you want a copy.

Best regards
Michael

> Tom Petch
>=20
> ----- Original Message -----
> From: "Randy Stewart" <randall@lakerest.net>
> To: "t.petch" <ietfc@btconnect.com>
> Cc: "tsvwg" <tsvwg@ietf.org>; "James M. Polk" <jmpolk@cisco.com>
> Sent: Wednesday, March 16, 2011 3:05 PM
> Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
>=20
>=20
>=20
> On Mar 16, 2011, at 4:31 AM, t.petch wrote:
>=20
>> ----- Original Message -----
>> From: "James M. Polk" <jmpolk@cisco.com>
>> To: "tsvwg" <tsvwg@ietf.org>
>> Sent: Sunday, March 13, 2011 9:48 PM
>>=20
>>> TSVWG
>>>=20
>>> The WG chairs have determined the WGLC for our SCTP Stream
>>> Reconfiguration ID continues (i.e., it has not concluded at the 2
>>> week window) due to lack of feedback to the list. No one has
>>> commented in a review format that they believe this ID should
>>> progress. No one has even sent a note merely saying this ID in its
>>> present form is good to go. That lack of any feedback is troubling
>>> and could be a sign of a lack of interest in this ID.
>>>=20
>>> The WG chairs like the idea of (and within) this draft, but we need
>>> transport experts to tell us this, and if the ID in its present form
>>> is good enough to implement to without those implementations having
>>> errors or causing bad behavior in SCTP because of how the ID is
>>> written (focusing mostly on the instructions to implementers in the =
ID).
>>>=20
>>> We chairs want folks to show or assert they have reviewed this ID =
and
>>> give feedback to the list (and not unicast to the chairs). This ID
>>> cannot progress without that feedback.
>>=20
>> I am sitting on my hands because I did not consider the I-D ready for =
last
> call
>> but also, I do not have a view as to whether or not this I-D will be
>> implemented,
>=20
>=20
> Can't say on other implementations but it is in FreeBSD ;-)
>=20
>> whether or not the additional function is worth standardising - I =
simply do
> not
>> have the contacts to make a judgement on this.
>>=20
>> I did comment on a previous version, and the comment was not resolved =
so I
>> decided to wait
>> until it was before commenting further, be that at IETF LC if so it =
be.  I did
>> get
>> a response about not wanting to push out too many revisions but, =
perversely,
>=20
>=20
> Tom, I did too respond to your comment.. and the update was posted on =
the
> mailing
> list... Did you not receive the email (sometimes my emails do not get =
through it
> would appear)..  I can wander back on the mailing list archives and =
find it ...
> let me see:
>=20
> Here it is from Feb 9th:
> =
**************************************************************************=
******
> *******
> Tom:
>=20
> Just to let you know I did NOT forget about this... Here is the text =
that is
> waiting in the xml for the -10 revision:
> ***********************************************************
>  When a peer endpoint requests a Incoming SSN Reset Request it is
>  possible that the local endpoint has just sent an Outgoing SSN Reset
>  Request on the same stream and has not yet received a response.  In
>  such a case the local endpoint MUST do the following:
>=20
>  1) If the stream reset overlaps the outstanding request completely
>     respond to the requestor with an acknowledgment indicating that
>     there was 'Nothing to do'.
>=20
>  2) Otherwise process the stream reset request normally responding to
>     the requestor with an acknowledgment.
>=20
>  It is also possible that the Incoming request will arrive after the
>  Outgoing SSN Reset Request just completed.  In such a case the local
>  endpoint MUST do the following:
>=20
>  1) If the stream reset overlaps the outstanding request completely
>     all of the streams being requested will be already set to 0.  If
>     so, the local endpoint SHOULD send back a Stream Reset Response
>     with the success code "Nothing to do".
>=20
>  2) Otherwise process the stream reset request normally responding to
>     the requestor an acknowledgment.
>=20
>  Note that in either race condition the local endpoint could
>  optionally also perform the reset.  This would result in streams that
>  are already at sequence 0 being reset again to 0 which would cause no
>  harm to the application but will add an extra message to the network.
>=20
>  Note also that in any of the race conditions listed above the
>  receiver MUST NOT send more than one response.  In other words two
>  responses MUST NOT be sent for the same request.
>=20
> *******************************************************************
>=20
> When we get any other comments after LC I will issue the updated draft =
with the
> above...
>=20
> If you would like further changes or this does not satisfy your =
comments below
> let me know.. you can even send suggested text :-)
>=20
> Best wishes
>=20
> R
> On Jan 15, 2011, at 6:49 AM, t.petch wrote:
>=20
>> I like the change to 5.2.3 but think that it needs to go further.
>>=20
>> -08 split out two cases,
>>=20
>> Incoming SSN Reset Request received but no response yet to the =
Outgoing
> request
>> Incoming SSN Reset Request received after response to the Outgoing =
request
>>=20
>> assuming that the Incoming and Outgoing requests have overlapping =
stream
>> numbers.
>>=20
>> -09 subdivides the first case into overlaps completely and overlaps =
partially
>> but
>> I think that the second case is also in need of subdivision in the =
same way.
>>=20
>> And, a point of clarification, in any of the four cases, is it =
required to
> send
>> just
>> the one response, ie you cannot send two responses in the partial =
overlap
> case,
>> one saying no-op and the will do (or won't do!)?
>>=20
>>=20
>> Tom Petch
>>=20
> =
**************************************************************************=
******
> ********
>=20
> You never replied to that so I had assumed you were happy with the =
changes.. if
> not
> I would be more than glad to hear your suggested changes...
>=20
>=20
> R
>=20
>=20
>> that is the problem, that the latest revision was pushed out too =
soon, before
>> the comments on the previous version had been adequately (IMO) =
resolved.
>> Which, in turn, brings us full circle, that insufficient interest was
> expressed
>> by the WG in that previous version to get the comments resolved; so =
should
>> this progress to RFC or no, is it worth standardising? I have no =
basis on
> which
>> to say.
>>=20
>> Tom Petch
>>=20
>>> James & Gorry
>>> TSVWG chairs
>>>=20
>>>=20
>>> At 10:07 PM 2/7/2011, James M. Polk wrote:
>>>> TSVWG
>>>>=20
>>>> I am starting the WGLC for
>>>>=20
>>>> "Stream Control Transmission Protocol (SCTP) Stream =
Reconfiguration"
>>>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-strrst/
>>>>=20
>>>> this is a 2 week WGLC, ending February 22nd, 2011 or when the =
chairs
>>>> feel the WG has reviewed the draft and reached consensus to =
progress
>>>> towards the ADs with the goal of becoming a proposed standard (PS) =
RFC.
>>>>=20
>>>> The chairs require substantive feedback from the WG regarding this
>>>> draft before consensus can be called.
>>>>=20
>>>> I will be the document shepherd.
>>>>=20
>>>> James
>>>> TSVWG chair
>>>=20
>>=20
>=20
> -----
> Randall Stewart
> randall@lakerest.net
>=20
>=20
>=20
>=20
>=20


From jmpolk@cisco.com  Fri Mar 18 14:02:36 2011
Return-Path: <jmpolk@cisco.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 765093A69B6 for <tsvwg@core3.amsl.com>; Fri, 18 Mar 2011 14:02:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.574
X-Spam-Level: 
X-Spam-Status: No, score=-110.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 je0zCcw5u4mV for <tsvwg@core3.amsl.com>; Fri, 18 Mar 2011 14:02:35 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 2E6B73A69A7 for <tsvwg@ietf.org>; Fri, 18 Mar 2011 14:02:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=5352; q=dns/txt; s=iport; t=1300482245; x=1301691845; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=NiHUVWVeGR4j1rS9bgC0Zy0r84//V/pX1stEB/I98/0=; b=CaehuTLKOinX4SjHGsHFkxbXNhIn5om0D97ezK6L8zBrewRSl3n+vhye mPqFXMccob0UWdphPQLosvnCjclkxW7ZnoZRp77NyQLHvTUaXB7DKxsPu ulz3603kp5QWfT7kw1m+YZC6BKxQ75lRiPeWCyjTQ6DsV0XE8kWkqw257 0=;
X-IronPort-AV: E=Sophos;i="4.63,207,1299456000"; d="scan'208";a="277806306"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by sj-iport-4.cisco.com with ESMTP; 18 Mar 2011 21:04:03 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2IL43hH018953;  Fri, 18 Mar 2011 21:04:03 GMT
Message-Id: <201103182104.p2IL43hH018953@rcdn-core-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 18 Mar 2011 16:04:02 -0500
To: Lou Berger <lberger@labn.net>, Bruce Davie <bdavie@cisco.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: draft-polk-tsvwg-intserv-multiple-tspec-06
In-Reply-To: <4D828F41.2010703@labn.net>
References: <4D81C686.1020701@erg.abdn.ac.uk> <A4A17838-4D02-41FD-82A6-0EAD7DA07B8D@cisco.com> <4D828F41.2010703@labn.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: tsvwg <tsvwg@ietf.org>, draft-polk-tsvwg-intserv-multiple-tspec@tools.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: Fri, 18 Mar 2011 21:02:36 -0000

At 05:46 PM 3/17/2011, Lou Berger wrote:
>I too think this is useful work and worth bringing into the WG.

Thanks!!


>Authors,
>
>I have some comments/questions that can be addressed as the draft moves
>forward (and don't need discussing if the draft isn't):
>
>1) a real nit:
>I suspect that the <flow descriptor list> RBNF is broken, and
>[MULTI_FLOWSPEC] should be [ <MULTI_FLOWSPEC> ] .

yep, sorry - this is obvious

>  (You might want to add a reference to 5511 too.)

probably


>2) I could see this as a more generally applicable problem, in
>particular it could apply to the non-IntServ class types supported by
>RSVP (TSPEC/FLOWSPEC).  What do you think about having the MULT_xxSPEC
>objects being defined solely on the RSVP level (perhaps using
>subobjects) rather than as defined now which is a change to RSVP and
>IntServ?

Hadn't thought about this before. We'll think about how this would 
work and if there are any gotchas.

Thanks for the comments and support.

James


>Lou
>
>PS I'm on the rsv-dir mailing list, but not listed on the web page so
>have no idea if this means this is a comment as a directorate member or not.
>
>PPS I won't be in the Prague session as I'll be chairing a WG at the
>same time, but do support this work as a WG document if the topic comes up.
>
>
>On 3/17/2011 10:16 AM, Bruce Davie wrote:
> >
> > On Mar 17, 2011, at 4:29 AM, Gorry Fairhurst wrote:
> >
> >>
> >> I'm happy to discuss the future steps for this draft.
> >>
> >> I'll also take an action to check the status and then seek help 
> from the RSVP directorate, the last note I saw from rsv-dir was 09/11/2010.
> >>
> >
> > You'll note that Fred recently posted my note from Nov 1, 2010, 
> and Scott Bradner just commented as a directorate member.
> >
> > So, the 3 directorate members who have commented are in favor of 
> adopting this draft.
> >
> > Bruce
> >
> >> I'll also try to sumarise where I see this draft has reached. I 
> can't do this today though.
> >>
> >> Gorry
> >>
> >> -------- Original Message --------
> >> Subject: Re: draft-polk-tsvwg-intserv-multiple-tspec-06
> >> Date: Wed, 16 Mar 2011 15:23:32 -0700
> >> From: Fred Baker <fred@cisco.com>
> >> To: ken carlberg <carlberg@g11.org.uk>
> >> CC: tsvwg <tsvwg@ietf.org>
> >>
> >>
> >> On Mar 16, 2011, at 10:56 AM, ken carlberg wrote:
> >>
> >>> hello,
> >>>
> >>> my understanding is that the decision is still open as to 
> whether this individual draft should become a working group 
> draft.  I'd like to express my interest in making that 
> migration.  My first comments on the draft came way back at the 
> IETF-stockholm meeting in '09, where I brought up questions about 
> multicast.  The current draft satisfies these questions, and other 
> comments I have made since then.  I think this effort is properly 
> baked for acceptance as a working group draft.
> >>>
> >>> But perhaps more importantly, I very much like its focus on 
> optimization.  The bulk of the work we come across at the IETF 
> either introduces new stuff, or augmentations to existing 
> efforts.  Its refreshing to see work that focuses on optimizing 
> something we already have.
> >>>
> >>> my 2 cents,
> >>>
> >>> -ken
> >>
> >> I think a relevant note is:
> >>
> >> On Nov 1, 2010, at 4:14 PM, Bruce Davie wrote:
> >>> On these 2 drafts:
> >>> On Oct 26, 2010, at 8:29 AM, Gorry Fairhurst wrote:
> >>>
> >>>> draft-polk-tsvwg-intserv-multiple-tspec
> >>>>    RSVP directorate to be consulted.
> >>>>    WG interest in this topic recorded at IETF-78.
> >>>>    Charter update would be needed to progress this work.
> >>>>    5 Reviews needed to determine energy/technical direction.
> >>>>    Author will update -04.
> >>>>    New revision expected.
> >>>>
> >>>> draft-lefaucheur-tsvwg-rsvp-multiple-preemption
> >>>>    RSVP directorate to be consulted.
> >>>>    WG needs to assess if this topic should be a work item.
> >>>
> >>> Two members of the RSVP directorate (myself and Lixia) have 
> read these drafts and support their adoption by the WG. Below are 
> some specific comments that I sent to the chairs, but I failed to 
> send earlier to the WG. I believe at least one more directorate 
> member has read these drafts but I've not received feedback one way 
> or another about adoption from other directorate members.
> >>
> >> It would be good to know whether other members of the RSVP 
> Directorate have commented. If there has been a charter discussion, 
> I have managed to miss it.
> >>
> >> As to the draft itself, I think there is reason to support it, 
> as we now have multi-rate codecs that can interact with it; rather 
> than firing up, disturbing competing traffic to a degree that the 
> codec data experiences loss and other traffic presumably does as 
> well, and then backing off to a more acceptable rate (which is what 
> rate-adaptive codecs do), it would be nice of the network could say 
> "that will happen if you choose this rate, but if you choose this 
> lower rate you will be better off." Having multiple T-Specs gives 
> the network the option of making that choice on the first pas 
> rather than taking binary decisions on multiple sequential decision steps.
> >>
> >>
> >
> >
> >
> >
> >


From randall@lakerest.net  Fri Mar 18 16:00:14 2011
Return-Path: <randall@lakerest.net>
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 97BB93A6A58 for <tsvwg@core3.amsl.com>; Fri, 18 Mar 2011 16:00:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.371
X-Spam-Level: 
X-Spam-Status: No, score=-0.371 tagged_above=-999 required=5 tests=[AWL=1.572,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 RdbHoPpqT2ru for <tsvwg@core3.amsl.com>; Fri, 18 Mar 2011 16:00:13 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id A928B3A6A53 for <tsvwg@ietf.org>; Fri, 18 Mar 2011 16:00:11 -0700 (PDT)
Received: from [32.177.20.94] ([32.177.20.94]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2IN1R6t013320 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 18 Mar 2011 19:01:32 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <E21487FF-A3D4-44CF-AB97-3FE04B4804CD@lurchi.franken.de>
Date: Fri, 18 Mar 2011 19:01:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <89A36FB2-C4B4-473A-AFBD-99EE683F9689@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <20110318010103.GA1531@openss7.org> <E21487FF-A3D4-44CF-AB97-3FE04B4804CD@lurchi.franken.de>
To: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.1082)
Cc: bidulock@openss7.org, 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: Fri, 18 Mar 2011 23:00:14 -0000

On Mar 18, 2011, at 4:19 AM, Michael T=FCxen wrote:

> On Mar 18, 2011, at 2:01 AM, Brian F. G. Bidulock wrote:
>=20
>> James,
>>=20
>> I'd like to weigh in on this draft.
>>=20
>> I have review the draft and, in summary, I do not think that it
>> is sufficient to proceed and needs significant rework before
>> doing so.  I have the following issues with the current draft:
>>=20
>> 1) There is no ability to "close" (remove) a stream.
>>=20
>> 2) The protocol mechanisms proposed are overly complex.
>>=20
>> 3) The protocol mechanisms proposed are lacking.
>>=20
>> (More detail on these issues at the end of this long note.)
>>=20
>> On the plus side, just about any application that uses more than
>> one stream can benefit from the capability to dynamically
>> allocate and deallocate a stream to and from an association.
>> Without this capability, one must pre-allocate the maximum
>> number of streams at association establishment.  An application,
>> such as SIGTRAN, can have difficulty in predicting the maximum
>> number of required streams as association initialization, and
>> may not know the number of required streams until a number of
>> them are already in active use.
>>=20
>> For example, M2UA would prefer to have one stream per interface
>> identifier (IID), however, the number of interface identifiers
>> (IIDs) supported by a given association changes over time.
>> Dropping the association and reopening it to reallocate the
>> number of available streams is far too disruptive to be usable
>> for M2UA: message loss and network degradation can occur from
>> the resulting changeovers.  Currently, M2UA multiplexes the IIDs
>> over the available streams, with the result that HOL blocking on
>> a stream affects more than one IID, which is bad, because M2UA
>> has no knowledge of which IIDs belong to a link-set, and one IID
>> may attempt to changeover to another IID in the same stream.
>>=20
>> So, I agree with the authors that the concept is generally
>> useful.
>>=20
>> As to whether it should be implemented in the transport layer
>> rather than the application or shim layer, there is one aspect
>> (when the draft is done correctly) that makes the transport
>> layer the appropriate place.  The SCTP stack can free the
>> transport layer resources associated with a stream when it is
>> "closed".  In particular, the current SSN and data fragmentation
>> state.
>>=20
>> So, I agree with the authors that the best placement is in the
>> transport layer, but only if the ability to "close" a stream is
>> provided.
>>=20
>> 1) There is no ability to "close" (remove) a stream.
>>=20
>>  Although, from discussions on the list, the major use of this
>>  capability is to be able to "open" and "close" a stream
>>  independent of opening and closing the association.
>>=20
>>  The draft falls short of addressing that capability.  I only
>>  has some ability to add a stream and reset an SSN.
>>=20
>>  Streams cannot be "closed" (removed).  This is a significant
>>  deficiency.  If 65,000 streams are "opened" (added) and then
>>  no longer required, the SCTP stack cannot free the unused
>>  resources associated with the 65,000 streams.
>>=20
>>  Resetting the SSN can be viewed simply as "closing" and
>>  "opening" (or possibly "reopening") a stream.  If closing and
>>  opening are provided, resetting SSN is simply a natural
>>  consequence of reopening a stream.
> Hi Brian,
>=20
> removing streams is much more difficult than adding streams.
> Assume that you have 10 streams, SID=3D0, ..., SID=3D9. Now you want
> to "close" the stream SID=3D1. Then you need to renumber all streams
> with SID > 1 or handle holes in the SIDs. Handling holes requires
> a major change, since some implementations handle streams by using
> an array...=20
>>=20
>> 2) The protocol mechanisms proposed are too complex.
>>=20
>>  The draft proposes what I would call an "out-of-band"
>>  solution for stream reset.  Chunks and parameters are
>>  defined, a procedural state machine and timers.  There are
>>  difficulties with the complexity of this approach.
>>=20
>>  A simpler approach is what I would call an "in-band"
>>  approach, where a chunk is treated by the stream logic in
>>  SCTP just as any other ordered stream DATA chunk.  One to
>>  close the stream would simply be transmitted after the last
>>  ordered DATA chunk on the stream.  To open a stream, one
>>  would be sent before the first ordered DATA chunk on the
>>  stream.  Then no extra state machine nor timers are required.
>>=20
>> 3) The protocol mechanisms proposed are lacking.
>>=20
>>  As a ramification of choosing an "out-of-band" approach, the
>>  draft requires that all data for a stream be held until the
>>  "out-of-band" procedure completes (for resetting an SSN).
>>  This can cause transmit buffer blocking of the entire
>>  association and is unsuitable for high performance
>>  applications.
>>=20
>>  With an "in-band" approach, reuse of a stream can be
>>  immediate (simple receipt of the in-band OPEN chunk is
>>  sufficient to reopen (reset) the stream for reuse.
>>=20
>> Because of these issues, I think that progressing this draft is
>> premature.  I would like an opportunity to discuss an alternate
>> "in-band" approach.  (This note is already too long...)
> Hmm. An in-band approach. Something like a DATA chunk with a
> specific flag set, or something else?
>=20
> The problem with the in-band approach I see is that the stream
> is not a uni-directional channel, where *all* messages are
> in a sequence, since we have unordered delivery.
>=20
> And what would you send if there is not DATA message to piggyback
> the reset info?
>=20
> I think you need some message independent from user data on
> the wire to signal that you reset the stream.


Two other issues with in-band is that

a) You can't reset multiple streams .. each stream must have
   some data message (as you illustrate above).

and

b) Adding a stream by definition is an out-of-band thing so you are =
mixing
   out-of-band with in-band.

One other little side effect is that yes you avoid stopping sending =
data, but
you will end up holding it on the other side if something is lost... I =
suppose
even the current out of band method could do that.. i.e. continue to =
send the new
sequence right away.. but I was leery about putting that since some =
implementations
make sure that a stream is with in 2^^15 incrementing and will abort an =
association
that gets such an out-of-order SSN (in its view.. assuming the TSN with =
the SSN got
lost)..

R

>=20
> Best regards
> Michael
>>=20
>> --brian
>>=20
>> --=20
>> Brian F. G. Bidulock
>> bidulock@openss7.org
>> http://www.openss7.org/
>>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From sambasiva.manchili@nexustelecom.com  Sat Feb 19 09:10:04 2011
Return-Path: <sambasiva.manchili@nexustelecom.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 E5C253A6CFB; Sat, 19 Feb 2011 09:10:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_34=0.6, J_CHICKENPOX_42=0.6]
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 O9oq42kOmvPp; Sat, 19 Feb 2011 09:10:04 -0800 (PST)
Received: from typhon.nexustelecom.com (typhon.nexustelecom.com [212.203.104.229]) by core3.amsl.com (Postfix) with ESMTP id 5DD3D3A6F7E; Sat, 19 Feb 2011 09:09:59 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.62,192,1297033200";  d="scan'208";a="2344874"
Received: from unknown (HELO hermes.nexustelecom.com) ([172.29.1.4]) by typhon.nexustelecom.com with ESMTP; 19 Feb 2011 18:10:35 +0100
Received: from hermes.nexustelecom.com (localhost [127.0.0.1]) by hermes.nexustelecom.com (Postfix) with ESMTP id 0ECC3159F64; Sat, 19 Feb 2011 18:10:35 +0100 (CET)
Received: from poseidon.nexus-ag.com (unknown [172.29.2.111]) by hermes.nexustelecom.com (Postfix) with ESMTP id 6B6CF159F63; Sat, 19 Feb 2011 18:10:17 +0100 (CET)
Received: from poseidon.nexus-ag.com ([172.29.2.111]) by poseidon.nexus-ag.com ([172.29.2.111]) with mapi; Sat, 19 Feb 2011 18:10:17 +0100
From: Sambasiva Rao Manchili <sambasiva.manchili@nexustelecom.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, "payload@ietf.org" <payload@ietf.org>,  "avtcore@ietf.org" <avtcore@ietf.org>, "codec@ietf.org" <codec@ietf.org>
Subject: RTP Timestamping in Control messages of IuCS interface.
Thread-Topic: RTP Timestamping in Control messages of IuCS interface.
Thread-Index: AQHL0FeK//SQUrZ5dEaOQI5XewDSTg==
Message-ID: <509DA52866E38F47878413CF102D751F7099C582BD@poseidon.nexus-ag.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TBoneOriginalFrom: Sambasiva Rao Manchili <sambasiva.manchili@nexustelecom.com>
X-TBoneOriginalTo: "tsvwg@ietf.org" <tsvwg@ietf.org>, "payload@ietf.org" <payload@ietf.org>,  "avtcore@ietf.org" <avtcore@ietf.org>, "codec@ietf.org" <codec@ietf.org>
X-TBoneOriginalCC: Antonio Gambin <antonio.gambin@nexustelecom.com>, Markus Locher <markus.locher@nexustelecom.com>, =?iso-8859-1?Q?Ralf_K=FChl?= <ralf.kuehl@nexustelecom.com>
X-TBoneDomainSigned: false
X-Mailman-Approved-At: Sat, 19 Mar 2011 09:06:59 -0700
Cc: Antonio Gambin <antonio.gambin@nexustelecom.com>, =?iso-8859-1?Q?Ralf_K=FChl?= <ralf.kuehl@nexustelecom.com>, Markus Locher <markus.locher@nexustelecom.com>
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>
Date: Sat, 19 Feb 2011 17:10:05 -0000
X-Original-Date: Sat, 19 Feb 2011 18:07:51 +0100
X-List-Received-Date: Sat, 19 Feb 2011 17:10:05 -0000

Hallo,

Can some one in IETF list, please help me to clarify the point w.r.t the Ti=
me stamping in RTP header for Audio Stream AMR 5.9.
I hope I am addressing to right group.

Our implementation of RTP is not accepting the two control messages belongi=
ng to the UPP(User plane protocol above RTP) if the two consecutive control=
 packets arrived has same time stamp with different sequence numbers.
The two control messages are UPP_INIT_ACK and Rate Control Message which be=
longs to UPP layer on IuCS user plane stack.
Our implementation expects the time stamp of second packet to be 320ms grea=
ter than the time stamp arrived in 1st Control message of RTP header.

Our counter part RTP stack says their implementation is right and can have =
the same time stamp in the RTP header of these control messages.

 RFC 3350 tells about equal timestamps for Video stream belonging to same f=
rame, but does not specifically tell about the control messages of its uppe=
r layer.
We have read the RFC 3550 , section 5.1 does NOT prevent RTP packets
from having equal timestamps but rather explicitly allows for it:

      Several consecutive RTP packets will have equal timestamps if
      they are (logically) generated at once, e.g., belong to the same
      video frame.  Consecutive RTP packets MAY contain timestamps that
      are not monotonic if the data is not transmitted in the order it
      was sampled, as in the case of MPEG interpolated video frames.
      (The sequence numbers of the packets as transmitted will still be
      monotonic.)

May I kindly ask the RTP experts in Audio Stream area(or specific to IuCS )=
 can please clarify me.

Thank you very much for your time.

Best Regads,
Samba.

This email and any attachment may contain confidential information which is=
 intended for use only by the addressee(s) named above. If you received thi=
s email by mistake, please notify the sender immediately, and delete the em=
ail from your system. You are prohibited from copying, disseminating or oth=
erwise using the email or any attachment.


From will.v.yu@gmail.com  Sun Mar 13 19:35:37 2011
Return-Path: <will.v.yu@gmail.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 21E013A6AC9; Sun, 13 Mar 2011 19:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.327
X-Spam-Level: 
X-Spam-Status: No, score=-3.327 tagged_above=-999 required=5 tests=[AWL=-0.028, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 wbQcY7ap6v7D; Sun, 13 Mar 2011 19:35:35 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 7CF313A6AB9; Sun, 13 Mar 2011 19:35:35 -0700 (PDT)
Received: by qyk29 with SMTP id 29so968440qyk.10 for <multiple recipients>; Sun, 13 Mar 2011 19:36:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=oLZJb/mn4cqwrPnu7gpC2lF2eNB55L+6Zq4VuOMkeAg=; b=QOY/s9OrwNOSpqilJc7GTgMklrEwI3OyLb9Upve9H1cIlY3YRHcpEqeUkoxpxXz+wn ZBsTr7Btn1/NGtF8czsk0IHPIeVZk6shj7eyDTOcZke0SbRwlnBTuye0CnZn0sr03Qb7 uHOOAzq9eu0pLyS2L44tpsAdEF2s0Up4lPtaU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=VZzoJyXEfXtbpZgqpPSl7uLXvW5IOMHUhx2lsmlnjkcFFYTLs20YwPajNVX7mldfq3 08syL2KC6OBxG0tQSPv1la2UBp0ZygMNzRazwwIQ/21h2icpa8nUXajsCDT+WP5wwCew dkRp3aznwVXbnr0m1k68HGuROCG+YAq45b4WY=
MIME-Version: 1.0
Received: by 10.229.234.12 with SMTP id ka12mr9570270qcb.66.1300070217950; Sun, 13 Mar 2011 19:36:57 -0700 (PDT)
Received: by 10.229.223.204 with HTTP; Sun, 13 Mar 2011 19:36:57 -0700 (PDT)
In-Reply-To: <117BBC30-5365-44AB-8CB9-5E8F3F1AAE47@lurchi.franken.de>
References: <AANLkTik1vsK8biL_ohqAVhHXRw99seF34LzSKaAFwi1B@mail.gmail.com> <117BBC30-5365-44AB-8CB9-5E8F3F1AAE47@lurchi.franken.de>
Date: Mon, 14 Mar 2011 10:36:57 +0800
Message-ID: <AANLkTimva9OxsLM3bbcBktUvxxMChekqbxPx0-vEim2S@mail.gmail.com>
Subject: Re: SCTP Path Max Retransmission Query
From: Will Yu <will.v.yu@gmail.com>
To: =?ISO-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>,  tsvwg@ietf.org
Content-Type: multipart/alternative; boundary=00163641754d862709049e682fd4
X-Mailman-Approved-At: Sat, 19 Mar 2011 09:06:59 -0700
Cc: will.yu@ericsson.com, ietf@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, 14 Mar 2011 02:35:37 -0000

--00163641754d862709049e682fd4
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hello dear Michael,

Thank you for your reply. There is an additional query about your reply:
In our realization, the remote address is regarded as unreachable until the
Heartbeat Message from TWO different local address(IP1 and IP2) exceed PMR.
It means that IP1 sent 4(PMR value) Heartbeat and IP2 sent 4(PMR value)
Heartbeat as well. In your describing, is this method not accord with RFC?

Thanks again.

Brs,
Will Yu

2011/3/12 Michael T=FCxen <Michael.Tuexen@lurchi.franken.de>

>
> On Mar 11, 2011, at 7:44 AM, Will Yu wrote:
>
> > Hello,
> >
> > I have a query on SCTP standard (RFC 4960). In section 8.2 Path Failure
> Detection, it describes the action which end points should take in detect=
ing
> path unavailable.
> >
> >    When its peer endpoint is multi-homed, an endpoint should keep an
> >    error counter for each of the destination transport addresses of the
> >    peer endpoint.
> >    Each time the T3-rtx timer expires on any address, or when a
> >    HEARTBEAT sent to an idle address is not acknowledged within an RTO,
> >    the error counter of that destination address will be incremented.
> >    When the value in the error counter exceeds the protocol parameter
> >    =92Path.Max.Retrans=92 of that destination address, the endpoint sho=
uld
> >    mark the destination transport address as inactive, and a
> >    notification SHOULD be sent to the upper layer.
> >
> > In my case, I connected two end points through four IP address. EP1 own=
s
> IP1 and IP2, EP2 owns IP3 and IP4. And IP1 is the primary address for EP1=
,
> while IP3 is the primary address for EP2. There is no other packet in thi=
s
> association except with Heartbeat and Heartbeat_ACK.
> >
> >                 IP1--------------------IP3
> >     End                   \ /                   End
> >    Point1                 *                   Point2
> >                              / \
> >                 IP2--------------------IP4
> >
> > When IP4 is unavailable, the heartbeat messages from IP1 and IP2 with t=
he
> destination IP4 cannot received acknowledgement. In this case, PMR in eac=
h
> EP is set to 4. I observed that EP1 used IP1 and IP2 as source address to
> send the heartbeat messages to IP4 respectively. When the heartbeat messa=
ge
> from source address IP2 exceed 4 times, it marked the path(IP2-IP4) is
> unreachable. And then IP1 exceed, it would mark the destination IP4 is
> unavailable. In my opinion, this result is
> There is no state for the path IP2-IP4, only for the remote address IP4.
> > reasonable with the recognition of IP2-IP4 is a path and IP1-IP4 is
> another path for the association. Consequently, the PMR parameter is for
> determining which PATH could regard as unavailable.
> SCTP supervises remote addresses. So EP1 is supervising IP3 and IP4. So
> there is one  error counter for IP3
> and one for IP4. There is also only a state per remote IP address. So aft=
er
> the error counter for IP4
> exceeds PMR, the IP address IP4 should be marked as unreachable.
> > But in the section 8.2 Path Failure Detection, the increasing counter
> action is based on different destination transport address, not on the
> different source-destination address pair. I think it make me confused th=
at
> counter will impact the result in my case with the assumption RFC regard =
the
> destination address failure as the critical element for Path Failure
> Detection.
> >
> > Would you kindly help me clarify the behaviors in Path Failure Detectio=
n,
> or figure out if I have any misunderstanding in this case?
> As said above, SCTP supervises remote addresses, not paths.
>
> Best regards
> Michael
>
> PS: It might be better to send SCTP related questions to tsvwg@ietf.org
> >
> > Brs,
> > Will Yu
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
>
>

--00163641754d862709049e682fd4
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hello dear Michael,<div><br></div><div>Thank you for your reply. There is a=
n additional query about your reply:</div><div>In our=A0realization, the re=
mote address is regarded as unreachable until the Heartbeat Message from TW=
O different local address(IP1 and IP2) exceed PMR. It means that IP1 sent 4=
(PMR value) Heartbeat and IP2 sent 4(PMR value) Heartbeat as well. In your=
=A0describing, is this method not accord with RFC?</div>
<div><br></div><div>Thanks again.</div><div><br></div><div>Brs,</div><div>W=
ill Yu</div><div><br><div class=3D"gmail_quote">2011/3/12 Michael T=FCxen <=
span dir=3D"ltr">&lt;<a href=3D"mailto:Michael.Tuexen@lurchi.franken.de">Mi=
chael.Tuexen@lurchi.franken.de</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div class=3D"im"><br>
On Mar 11, 2011, at 7:44 AM, Will Yu wrote:<br>
<br>
&gt; Hello,<br>
&gt;<br>
&gt; I have a query on SCTP standard (RFC 4960). In section 8.2 Path Failur=
e Detection, it describes the action which end points should take in detect=
ing path unavailable.<br>
&gt;<br>
&gt; =A0 =A0When its peer endpoint is multi-homed, an endpoint should keep =
an<br>
&gt; =A0 =A0error counter for each of the destination transport addresses o=
f the<br>
&gt; =A0 =A0peer endpoint.<br>
&gt; =A0 =A0Each time the T3-rtx timer expires on any address, or when a<br=
>
&gt; =A0 =A0HEARTBEAT sent to an idle address is not acknowledged within an=
 RTO,<br>
&gt; =A0 =A0the error counter of that destination address will be increment=
ed.<br>
&gt; =A0 =A0When the value in the error counter exceeds the protocol parame=
ter<br>
&gt; =A0 =A0=92Path.Max.Retrans=92 of that destination address, the endpoin=
t should<br>
&gt; =A0 =A0mark the destination transport address as inactive, and a<br>
&gt; =A0 =A0notification SHOULD be sent to the upper layer.<br>
&gt;<br>
&gt; In my case, I connected two end points through four IP address. EP1 ow=
ns IP1 and IP2, EP2 owns IP3 and IP4. And IP1 is the primary address for EP=
1, while IP3 is the primary address for EP2. There is no other packet in th=
is association except with Heartbeat and Heartbeat_ACK.<br>

&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 IP1--------------------IP3<br>
&gt; =A0 =A0 End =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 \ / =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 End<br>
&gt; =A0 =A0Point1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 * =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 Point2<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/ \<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 IP2--------------------IP4<br>
&gt;<br>
&gt; When IP4 is unavailable, the heartbeat messages from IP1 and IP2 with =
the destination IP4 cannot received acknowledgement. In this case, PMR in e=
ach EP is set to 4. I observed that EP1 used IP1 and IP2 as source address =
to send the heartbeat messages to IP4 respectively. When the heartbeat mess=
age from source address IP2 exceed 4 times, it marked the path(IP2-IP4) is =
unreachable. And then IP1 exceed, it would mark the destination IP4 is unav=
ailable. In my opinion, this result is<br>

</div>There is no state for the path IP2-IP4, only for the remote address I=
P4.<br>
<div class=3D"im">&gt; reasonable with the recognition of IP2-IP4 is a path=
 and IP1-IP4 is another path for the association. Consequently, the PMR par=
ameter is for determining which PATH could regard as unavailable.<br>
</div>SCTP supervises remote addresses. So EP1 is supervising IP3 and IP4. =
So there is one =A0error counter for IP3<br>
and one for IP4. There is also only a state per remote IP address. So after=
 the error counter for IP4<br>
exceeds PMR, the IP address IP4 should be marked as unreachable.<br>
<div class=3D"im">&gt; But in the section 8.2 Path Failure Detection, the i=
ncreasing counter action is based on different destination transport addres=
s, not on the different source-destination address pair. I think it make me=
 confused that counter will impact the result in my case with the assumptio=
n RFC regard the destination address failure as the critical element for Pa=
th Failure Detection.<br>

&gt;<br>
&gt; Would you kindly help me clarify the behaviors in Path Failure Detecti=
on, or figure out if I have any misunderstanding in this case?<br>
</div>As said above, SCTP supervises remote addresses, not paths.<br>
<br>
Best regards<br>
Michael<br>
<br>
PS: It might be better to send SCTP related questions to <a href=3D"mailto:=
tsvwg@ietf.org">tsvwg@ietf.org</a><br>
&gt;<br>
&gt; Brs,<br>
&gt; Will Yu<br>
&gt; _______________________________________________<br>
&gt; Ietf mailing list<br>
&gt; <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ietf</a><br>
<br>
</blockquote></div><br></div>

--00163641754d862709049e682fd4--

From Michael.Larsen@tieto.com  Fri Mar 18 02:29:39 2011
Return-Path: <Michael.Larsen@tieto.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 4B5E13A6A4B for <tsvwg@core3.amsl.com>; Fri, 18 Mar 2011 02:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 ZBguWe0vxLgo for <tsvwg@core3.amsl.com>; Fri, 18 Mar 2011 02:29:38 -0700 (PDT)
Received: from ebb05.tieto.com (ebb05.tieto.com [131.207.168.36]) by core3.amsl.com (Postfix) with ESMTP id C13263A682E for <tsvwg@ietf.org>; Fri, 18 Mar 2011 02:29:37 -0700 (PDT)
X-AuditID: 83cfa824-b7b21ae000000a96-cc-4d832659f544
Received: from FIHGA-EXHUB01.eu.tieto.com ( [131.207.136.34]) by ebb05.tieto.com (SMTP Mailer) with SMTP id 6A.3B.02710.956238D4; Fri, 18 Mar 2011 11:31:05 +0200 (EET)
Received: from ul000431.localnet (10.48.99.19) by inbound.tieto.com (131.207.136.49) with Microsoft SMTP Server id 8.3.106.1; Fri, 18 Mar 2011 11:31:04 +0200
From: Michael Larsen <michael.larsen@tieto.com>
To: <tsvwg@ietf.org>
Subject: SCTP zero-window probing and path selection
Date: Fri, 18 Mar 2011 10:31:03 +0100
User-Agent: KMail/1.13.5 (Linux/2.6.32-29-generic; KDE/4.4.5; i686; ; )
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <201103181031.03591.michael.larsen@tieto.com>
X-Brightmail-Tracker: AAAAAQW74bY=
X-Mailman-Approved-At: Sat, 19 Mar 2011 09:06:59 -0700
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: Fri, 18 Mar 2011 10:15:22 -0000

Hello list,

Looking into SCTP zero window probing on a multi-homed association and path 
failures, it looks to me like RFC4960 has room for an improvement.

Imagine the following setup with two host and a multi-homed association:

Local                    Peer

IP1 -------------------- IPa

IP2 -------------------- IPb

Imagine that we ('Local') is sending data on IP1-IPa while peer is sending 
data on IP2-IPb.  Subsequently, imagine that peer announces a_rwnd=0 and we 
begin zero-window probing (on IP1-IPa).  In the mean-time peer continues to 
send data on IP2-IPb and we dutifully return SACK of that data on IP2-IPb.

Now IP1-IPa breaks and our window-probes no longer reaches peer. Reading 4960 
literally we will not detect this and may never detect when peer rwnd opens.

The reason for this is the following statement from 4960 (Section 6.1, item 
A):

     "If the sender continues to receive new packets from the receiver
      while doing zero window probing, the unacknowledged window probes
      should not increment the error counter for the association or any
      destination transport address."

I.e. we are receiving "new packets" (albeit DATA chunks on IP2-IPb) so we do 
not increment the error counter and does not change destination of the window 
probes.

4960 is not clear on whether IP1-IPa is "idle" in this situation such that the 
destination is probed through heartbeats (we have sent data so strictly 
speaking HBs should not be sent). IF we read 4960 such that HBs should be sent 
then they will eventually clear up the reachability problem but this is a 
side-effect and given that heartbeat intervals can be tuned and heartbeat 
disabled this reaction may come too late or not at all.

The solution seems to me that instead of "new packets" 4960 should have said 
"SACK chunks" because the SACK chunk is the proper 'alive indication' returned 
in response to our window probe.  DATA chunks are not, because they belong to 
the independent data-flow going in the other direction.

Regards,
Michael

From sambainietf@gmail.com  Sat Mar 19 04:11:40 2011
Return-Path: <sambainietf@gmail.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 7437C3A6A66; Sat, 19 Mar 2011 04:11:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.97
X-Spam-Level: 
X-Spam-Status: No, score=-2.97 tagged_above=-999 required=5 tests=[AWL=-0.572,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, J_CHICKENPOX_39=0.6, RCVD_IN_DNSWL_LOW=-1]
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 Ae7ESVo5Q07h; Sat, 19 Mar 2011 04:11:39 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id A39483A6A5F; Sat, 19 Mar 2011 04:11:38 -0700 (PDT)
Received: by fxm15 with SMTP id 15so4715895fxm.31 for <multiple recipients>; Sat, 19 Mar 2011 04:13:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=q2wrxjfw556HtUTbJk9Bp2hPQWnsD9a1BUWilmJk/sc=; b=PeqJVeOUINjyapKV4neomNfkR/gykG0nMrGSEnPzWLk6vr01RwbBnJLfFjLcW/Nb+i vMefLGsfrSJouuFBftvFXc8RO6eYhysPzv+7xNpb6mNCoQiOSimREm0NePbwM3djAVr1 JtRcx184VFmh24rnz2pdHv5HOTM8/E62/gIcg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=grNpFEMp8RIzNn0L0L93neflfYwS+eF9DkftXOkCkI3FreqgP97+gNq3urXu5GTjYo NJaEXV8cH+5En+SFIXCLzaDuOrJtJ0fUxP773PlpCqnQND6txvzPaDB2TKJ23qgOrVx9 aYhia77U3UQtibatyRURMgof2TvA+ZwrIC2mk=
MIME-Version: 1.0
Received: by 10.223.6.220 with SMTP id a28mr2427376faa.94.1300533188707; Sat, 19 Mar 2011 04:13:08 -0700 (PDT)
Received: by 10.223.89.134 with HTTP; Sat, 19 Mar 2011 04:13:08 -0700 (PDT)
Date: Sat, 19 Mar 2011 12:13:08 +0100
Message-ID: <AANLkTikat5-b3gzjGT2shV1bsj=wmQdPBxPswHcHSEgG@mail.gmail.com>
Subject: SIP UDP packet loss?
From: Sambasiva Rao MANCHILI <sambainietf@gmail.com>
To: sipcore@ietf.org, soc@ietf.org, p2psip@ietf.org, tsvwg@ietf.org,  ietf@ietf.org
Content-Type: multipart/alternative; boundary=00151744791abb4682049ed3fac9
X-Mailman-Approved-At: Sat, 19 Mar 2011 09:06:59 -0700
Cc: sambasiva.manchili@nexustelecom.com
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: Sat, 19 Mar 2011 11:11:40 -0000

--00151744791abb4682049ed3fac9
Content-Type: text/plain; charset=ISO-8859-1

Hallo  Sip Experts / Transport Group Experts,
I am not a SIP expert of application layer. I am part of Test System
Development where we simulate the SIP traffic over different transport types
like UDP,TCP and SCTP.
When we are simulating just SIP signalling messages between our two test
systems at the rate of  greater than 500  UDP packets per second, we
observed some of
Subscribers fail Signalling.After further investigations it is found that
UDP packets are lost  consequently Signalling is failing for
some subscribers intermittently.

To overcome this we then increased the udp.recvspace and udp.sendspace and
socketbuffer size in our Networking stack.
This helped the packet loss to reduce by 70% but could not achieve 0% packet
loss .
*Qeury 1*:- Is increasing buffer space is a solution or workaround for our
Network stack  to overcome packet loss ?

Default values of our Network stack  were 40K for udp.recvspace and 9K for
udp.sendspace and socketbuffers are 256K.
We changed these values in our Network stack  to 256K  for udp.recvspace,
256K for udp.sendspace and socketbuffers to 1024K.
This change has reduced packet loss but can could not make 0% packet loss.

Query2:- Can you please suggest us what should be the right values for such
buffer space if this is right approach ?

We have yet to enable the voice transmission as a next immediate step, then
again SIP RTP UDP packets will further increase based on the codec chosen
and this will
cause even more packet loss.

Query3:-  What is the ultimate  solution for eliminating packet loss both on
Signalling and on speech path ?

Thank you in advance for your time.
Samba.

--00151744791abb4682049ed3fac9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hallo =A0Sip Experts / Transport Group Experts,<div>I am not a SIP expert o=
f application layer. I am part of Test System Development where we simulate=
 the SIP traffic over different transport types like UDP,TCP and SCTP.</div=
>
<div>When we are simulating just SIP signalling messages between our two te=
st systems at the rate of =A0greater than 500 =A0UDP packets per second,=A0=
we observed some of=A0</div><div>Subscribers fail Signalling.After further =
investigations it is found that UDP packets are lost =A0consequently Signal=
ling is failing for some=A0subscribers=A0intermittently.</div>
<div><br></div><div>To overcome this we then increased the udp.recvspace an=
d udp.sendspace and socketbuffer size in our Networking stack.=A0</div><div=
>This helped the packet loss to reduce by 70% but could not achieve 0% pack=
et loss . =A0</div>
<div><u>Qeury 1</u>:- Is increasing buffer space is a solution or workaroun=
d for our Network stack =A0to overcome packet loss ?</div><div><br></div><d=
iv>Default values of our Network stack =A0were 40K for udp.recvspace and 9K=
 for udp.sendspace and socketbuffers are 256K. =A0</div>
<div>We changed these values in our Network stack =A0to 256K =A0for udp.rec=
vspace, 256K for udp.sendspace and socketbuffers to 1024K.=A0</div><div>Thi=
s change has=A0reduced=A0packet loss but can could not make 0% packet loss.=
 =A0</div>
<div><br></div><div>Query2:- Can you please suggest us what should be the r=
ight values for such buffer space if this is right approach ?</div><div><br=
></div><div>We have yet to enable the voice transmission as a next immediat=
e step, then again SIP RTP UDP packets will further increase based on the c=
odec=A0chosen and this will</div>
<div>cause even more packet loss.</div><div><br></div><div>Query3:- =A0What=
 is the ultimate =A0solution for=A0eliminating=A0packet loss both on Signal=
ling and on speech path ?=A0</div><div><br></div><div>Thank you in advance =
for your time.</div>
<div>Samba.</div>

--00151744791abb4682049ed3fac9--

From sambainietf@gmail.com  Sat Mar 19 04:27:12 2011
Return-Path: <sambainietf@gmail.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 D30743A6A66; Sat, 19 Mar 2011 04:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.855
X-Spam-Level: 
X-Spam-Status: No, score=-2.855 tagged_above=-999 required=5 tests=[AWL=-0.457, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, J_CHICKENPOX_39=0.6, RCVD_IN_DNSWL_LOW=-1]
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 HEttsYZCuFqu; Sat, 19 Mar 2011 04:27:12 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id DA7DA3A6A90; Sat, 19 Mar 2011 04:27:10 -0700 (PDT)
Received: by fxm15 with SMTP id 15so4721527fxm.31 for <multiple recipients>; Sat, 19 Mar 2011 04:28:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=aOu2cYBhrozdwzvNtP8RqjJf5X+La0K21yFDpqRUWtU=; b=sj7F6Xc7BH+oMqYWfuCO8BQPhT15g+y439Y00sQKzGPW3lSf3fNs/QpkhTGsOcUuWr sJpRNJ0cKC1yGjmnen5NE/6PMFbx15llpwMUG+I5RWeVf0eEjsjdn4Vu6zsVsyx6THR6 ZGVrY+uOOGMEr+r/ZaVp2GNebx0BLQn8tCTVs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=sQ0Mo6rWn254+1T1jsk9nWoNz0cKMq1hdRIJAz/F5QB22JxFz/MjAw079Kzm67F5iw PgTbLrS8DexDMsAznVhfIzvJWxZLam1h5ek50T7vutmQByG7scRaG6dpe9CEyKVGQUc7 ZHblpftlaRdd5hgGAz3ROo35oO2CQye1EqUog=
MIME-Version: 1.0
Received: by 10.223.63.212 with SMTP id c20mr2468331fai.37.1300534120951; Sat, 19 Mar 2011 04:28:40 -0700 (PDT)
Received: by 10.223.89.134 with HTTP; Sat, 19 Mar 2011 04:28:40 -0700 (PDT)
In-Reply-To: <AANLkTikat5-b3gzjGT2shV1bsj=wmQdPBxPswHcHSEgG@mail.gmail.com>
References: <AANLkTikat5-b3gzjGT2shV1bsj=wmQdPBxPswHcHSEgG@mail.gmail.com>
Date: Sat, 19 Mar 2011 12:28:40 +0100
Message-ID: <AANLkTim6K21RYJMkYTPxcxVOUT_42m_MUDzGDNsNJ73V@mail.gmail.com>
Subject: Re: SIP UDP packet loss?
From: Sambasiva Rao MANCHILI <sambainietf@gmail.com>
To: sipcore@ietf.org, soc@ietf.org, p2psip@ietf.org, tsvwg@ietf.org,  ietf@ietf.org
Content-Type: multipart/alternative; boundary=0015174758284c30ec049ed43236
X-Mailman-Approved-At: Sat, 19 Mar 2011 09:06:59 -0700
Cc: sambasiva.manchili@nexustelecom.com
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: Sat, 19 Mar 2011 11:27:13 -0000

--0015174758284c30ec049ed43236
Content-Type: text/plain; charset=ISO-8859-1

Hallo,
A Correction in my mail
>>This helped the packet loss to reduce by 70% but could not achieve 0%
packet loss .
This helped the packet loss to reduce by 10%.
Before increasing buffers we have Faults rate of ~8 to 10% after increasing
buffers we have fault rate of 0.9%.
Thank you,
Samba.

On Sat, Mar 19, 2011 at 12:13 PM, Sambasiva Rao MANCHILI <
sambainietf@gmail.com> wrote:

> Hallo  Sip Experts / Transport Group Experts,
> I am not a SIP expert of application layer. I am part of Test System
> Development where we simulate the SIP traffic over different transport types
> like UDP,TCP and SCTP.
> When we are simulating just SIP signalling messages between our two test
> systems at the rate of  greater than 500  UDP packets per second, we
> observed some of
> Subscribers fail Signalling.After further investigations it is found that
> UDP packets are lost  consequently Signalling is failing for
> some subscribers intermittently.
>
> To overcome this we then increased the udp.recvspace and udp.sendspace and
> socketbuffer size in our Networking stack.
> This helped the packet loss to reduce by 70% but could not achieve 0%
> packet loss .
> *Qeury 1*:- Is increasing buffer space is a solution or workaround for our
> Network stack  to overcome packet loss ?
>
> Default values of our Network stack  were 40K for udp.recvspace and 9K for
> udp.sendspace and socketbuffers are 256K.
> We changed these values in our Network stack  to 256K  for udp.recvspace,
> 256K for udp.sendspace and socketbuffers to 1024K.
> This change has reduced packet loss but can could not make 0% packet loss.
>
>
> Query2:- Can you please suggest us what should be the right values for such
> buffer space if this is right approach ?
>
> We have yet to enable the voice transmission as a next immediate step, then
> again SIP RTP UDP packets will further increase based on the codec chosen
> and this will
> cause even more packet loss.
>
> Query3:-  What is the ultimate  solution for eliminating packet loss both
> on Signalling and on speech path ?
>
> Thank you in advance for your time.
> Samba.
>

--0015174758284c30ec049ed43236
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hallo,<div>A Correction in my mail</div><div>&gt;&gt;This helped the packet=
 loss to reduce by 70% but could not achieve 0% packet loss .</div><div>Thi=
s helped the=A0packet=A0loss to reduce by 10%.=A0</div><div>Before increasi=
ng buffers we have Faults rate of ~8 to 10% after increasing buffers we hav=
e fault rate of 0.9%.<br>
Thank you,</div><div>Samba.</div><div><br><div class=3D"gmail_quote">On Sat=
, Mar 19, 2011 at 12:13 PM, Sambasiva Rao MANCHILI <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:sambainietf@gmail.com">sambainietf@gmail.com</a>&gt;</span>=
 wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Hallo =A0Sip Experts / Transport Group Expe=
rts,<div>I am not a SIP expert of application layer. I am part of Test Syst=
em Development where we simulate the SIP traffic over different transport t=
ypes like UDP,TCP and SCTP.</div>

<div>When we are simulating just SIP signalling messages between our two te=
st systems at the rate of =A0greater than 500 =A0UDP packets per second,=A0=
we observed some of=A0</div><div>Subscribers fail Signalling.After further =
investigations it is found that UDP packets are lost =A0consequently Signal=
ling is failing for some=A0subscribers=A0intermittently.</div>

<div><br></div><div>To overcome this we then increased the udp.recvspace an=
d udp.sendspace and socketbuffer size in our Networking stack.=A0</div><div=
>This helped the packet loss to reduce by 70% but could not achieve 0% pack=
et loss . =A0</div>

<div><u>Qeury 1</u>:- Is increasing buffer space is a solution or workaroun=
d for our Network stack =A0to overcome packet loss ?</div><div><br></div><d=
iv>Default values of our Network stack =A0were 40K for udp.recvspace and 9K=
 for udp.sendspace and socketbuffers are 256K. =A0</div>

<div>We changed these values in our Network stack =A0to 256K =A0for udp.rec=
vspace, 256K for udp.sendspace and socketbuffers to 1024K.=A0</div><div>Thi=
s change has=A0reduced=A0packet loss but can could not make 0% packet loss.=
 =A0</div>

<div><br></div><div>Query2:- Can you please suggest us what should be the r=
ight values for such buffer space if this is right approach ?</div><div><br=
></div><div>We have yet to enable the voice transmission as a next immediat=
e step, then again SIP RTP UDP packets will further increase based on the c=
odec=A0chosen and this will</div>

<div>cause even more packet loss.</div><div><br></div><div>Query3:- =A0What=
 is the ultimate =A0solution for=A0eliminating=A0packet loss both on Signal=
ling and on speech path ?=A0</div><div><br></div><div>Thank you in advance =
for your time.</div>

<div>Samba.</div>
</blockquote></div><br></div>

--0015174758284c30ec049ed43236--

From adrian@olddog.co.uk  Sat Mar 19 13:12:49 2011
Return-Path: <adrian@olddog.co.uk>
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 78E9B3A69BD for <tsvwg@core3.amsl.com>; Sat, 19 Mar 2011 13:12:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 FvRSnlQMK98F for <tsvwg@core3.amsl.com>; Sat, 19 Mar 2011 13:12:48 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by core3.amsl.com (Postfix) with ESMTP id 8303B3A69BB for <tsvwg@ietf.org>; Sat, 19 Mar 2011 13:12:48 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id p2JKEIPe018182 for <tsvwg@ietf.org>; Sat, 19 Mar 2011 20:14:18 GMT
Received: from 950129200 (genld-224-034.t-mobile.co.uk [149.254.224.34]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id p2JKDROE017994 for <tsvwg@ietf.org>; Sat, 19 Mar 2011 20:14:10 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <tsvwg@ietf.org>
References: <20110316220948.75DF39962F7@newdev.eecs.harvard.edu>
In-Reply-To: <20110316220948.75DF39962F7@newdev.eecs.harvard.edu>
Subject: RE: draft-polk-tsvwg-intserv-multiple-tspec-06
Date: Sat, 19 Mar 2011 20:13:26 -0000
Message-ID: <002d01cbe672$37594a90$a60bdfb0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIxYdjC4UXKcLcisfKszLFThIp3SpNqGbuQ
Content-Language: en-gb
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Sat, 19 Mar 2011 20:12:49 -0000

I, too, think it would be good to advance and complete this draft.

I have a preference for WG-driven where we have a WG that covers the area since
it removes ambiguity in the consensus process.

Seems like tsvwg would be a fine place for this.
I do not think it is one of the drafts that should find its way to one of the
Routing Area working groups.

Cheers,
Adrian (RSVP Directorate member - for all that that means!)

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> Scott O. Bradner
> Sent: 16 March 2011 22:10
> To: tsvwg@ietf.org
> Subject: Re: draft-polk-tsvwg-intserv-multiple-tspec-06
> 
> 
> I very much support this doc being finished up - it is very
> useful technology
> 
> if the tsvwg is able to do the work I'd support that  path
> 
> thanks
> 
> Scott


From ietfc@btconnect.com  Sat Mar 19 14:00:18 2011
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 8437E3A69B3 for <tsvwg@core3.amsl.com>; Sat, 19 Mar 2011 14:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.229
X-Spam-Level: 
X-Spam-Status: No, score=-0.229 tagged_above=-999 required=5 tests=[AWL=-1.486, BAYES_50=0.001, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, 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 Akys+cOUgnM4 for <tsvwg@core3.amsl.com>; Sat, 19 Mar 2011 14:00:17 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by core3.amsl.com (Postfix) with ESMTP id B78D53A69A1 for <tsvwg@ietf.org>; Sat, 19 Mar 2011 14:00:16 -0700 (PDT)
Received: from host217-44-145-106.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.106]) by c2beaomr08.btconnect.com with SMTP id CDN83364; Sat, 19 Mar 2011 21:01:34 +0000 (GMT)
Message-ID: <01ae01cbe66f$c4d2d1a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net> <29AEBA37-6157-44E9-8FD7-B44023DF6CD7@lakerest.net> <024801cbe593$4f2d1960$4001a8c0@gateway.2wire.net> <646C4AFE-1AAE-419B-BB6D-8670D292F563@lurchi.franken.de>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Date: Sat, 19 Mar 2011 20:56:38 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4D8519AD.00A4, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0207.4D8519AF.00F5,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: "James M. Polk" <jmpolk@cisco.com>, tsvwg <tsvwg@ietf.org>, Randy Stewart <randall@lakerest.net>
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: Sat, 19 Mar 2011 21:00:18 -0000

----- Original Message -----
From: "Michael Tüxen" <Michael.Tuexen@lurchi.franken.de>
To: "t.petch" <ietfc@btconnect.com>
Cc: "Randy Stewart" <randall@lakerest.net>; "James M. Polk" <jmpolk@cisco.com>;
"tsvwg" <tsvwg@ietf.org>
Sent: Friday, March 18, 2011 8:45 PM
On Mar 18, 2011, at 6:38 PM, t.petch wrote:

> Randy
>
> Yes, I did get your e-mail and did understand that you would implement it
> in -10 after WGLC.  My point was rather a process one, that I thought
> that at least one earlier version of the I-D came out too soon, before
> consensus had been reached on the list, leading to extra work and
> the possibility of errors.
>
> And I see something of the same now, that K. Poon comes up with
> suggestions and you say yes good we will do that.  I think no, that that
> is premature, wait for others to catch up and comment.  And if noone
> comments, then I suspect that there is no consensus and that the
> change should not be made.  At WGLC time, in my book, you need
> a solid reason to change, not a 'good idea' from one participant.
> At least give others a chance to say yea or nay.
>
> For myself, I think that punctuation in a short label is a bad thing ie
> RE-CONFIG
> is always a mistake.  Some will forget it, some will misplace it.  It can
> only create errors (a longer label, eg channel-binding, is a different
matter).
>
> And if the suggested change has not come up in the 10 previous iterations
> of the I-D, then I suspect that the benefit of it is not great, not enough to
be
> worth making it at this time; with my previous suggestions, you did miss out
> some, for all the power of sed, grep etc, so I suspect that some will be
missed
> now, which will be worse than either the old wording or new.

Hi Tom,

I can send you the current version, which we have in CVS and you can have a
look.
While doing the changes I fixed some editorial errors which I missed earlier.

Let me know if you want a copy.
<tp>
Michael

Thanks for the offer but I'll take a raincheck.

I think that more time should be given to consider Brian's comments before
I want to see fresh text.  His point on removing streams seems a good
one, and that on in- versus out of- band is interesting.

Tom
</tp>

Best regards
Michael

> Tom Petch
>
> ----- Original Message -----
> From: "Randy Stewart" <randall@lakerest.net>
> To: "t.petch" <ietfc@btconnect.com>
> Cc: "tsvwg" <tsvwg@ietf.org>; "James M. Polk" <jmpolk@cisco.com>
> Sent: Wednesday, March 16, 2011 3:05 PM
> Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
>
>
>
> On Mar 16, 2011, at 4:31 AM, t.petch wrote:
>
>> ----- Original Message -----
>> From: "James M. Polk" <jmpolk@cisco.com>
>> To: "tsvwg" <tsvwg@ietf.org>
>> Sent: Sunday, March 13, 2011 9:48 PM
>>
>>> TSVWG
>>>
>>> The WG chairs have determined the WGLC for our SCTP Stream
>>> Reconfiguration ID continues (i.e., it has not concluded at the 2
>>> week window) due to lack of feedback to the list. No one has
>>> commented in a review format that they believe this ID should
>>> progress. No one has even sent a note merely saying this ID in its
>>> present form is good to go. That lack of any feedback is troubling
>>> and could be a sign of a lack of interest in this ID.
>>>
>>> The WG chairs like the idea of (and within) this draft, but we need
>>> transport experts to tell us this, and if the ID in its present form
>>> is good enough to implement to without those implementations having
>>> errors or causing bad behavior in SCTP because of how the ID is
>>> written (focusing mostly on the instructions to implementers in the ID).
>>>
>>> We chairs want folks to show or assert they have reviewed this ID and
>>> give feedback to the list (and not unicast to the chairs). This ID
>>> cannot progress without that feedback.
>>
>> I am sitting on my hands because I did not consider the I-D ready for last
> call
>> but also, I do not have a view as to whether or not this I-D will be
>> implemented,
>
>
> Can't say on other implementations but it is in FreeBSD ;-)
>
>> whether or not the additional function is worth standardising - I simply do
> not
>> have the contacts to make a judgement on this.
>>
>> I did comment on a previous version, and the comment was not resolved so I
>> decided to wait
>> until it was before commenting further, be that at IETF LC if so it be.  I
did
>> get
>> a response about not wanting to push out too many revisions but, perversely,
>
>
> Tom, I did too respond to your comment.. and the update was posted on the
> mailing
> list... Did you not receive the email (sometimes my emails do not get through
it
> would appear)..  I can wander back on the mailing list archives and find it
...
> let me see:
>
> Here it is from Feb 9th:
>
********************************************************************************
> *******
> Tom:
>
> Just to let you know I did NOT forget about this... Here is the text that is
> waiting in the xml for the -10 revision:
> ***********************************************************
>  When a peer endpoint requests a Incoming SSN Reset Request it is
>  possible that the local endpoint has just sent an Outgoing SSN Reset
>  Request on the same stream and has not yet received a response.  In
>  such a case the local endpoint MUST do the following:
>
>  1) If the stream reset overlaps the outstanding request completely
>     respond to the requestor with an acknowledgment indicating that
>     there was 'Nothing to do'.
>
>  2) Otherwise process the stream reset request normally responding to
>     the requestor with an acknowledgment.
>
>  It is also possible that the Incoming request will arrive after the
>  Outgoing SSN Reset Request just completed.  In such a case the local
>  endpoint MUST do the following:
>
>  1) If the stream reset overlaps the outstanding request completely
>     all of the streams being requested will be already set to 0.  If
>     so, the local endpoint SHOULD send back a Stream Reset Response
>     with the success code "Nothing to do".
>
>  2) Otherwise process the stream reset request normally responding to
>     the requestor an acknowledgment.
>
>  Note that in either race condition the local endpoint could
>  optionally also perform the reset.  This would result in streams that
>  are already at sequence 0 being reset again to 0 which would cause no
>  harm to the application but will add an extra message to the network.
>
>  Note also that in any of the race conditions listed above the
>  receiver MUST NOT send more than one response.  In other words two
>  responses MUST NOT be sent for the same request.
>
> *******************************************************************
>
> When we get any other comments after LC I will issue the updated draft with
the
> above...
>
> If you would like further changes or this does not satisfy your comments below
> let me know.. you can even send suggested text :-)
>
> Best wishes
>
> R
> On Jan 15, 2011, at 6:49 AM, t.petch wrote:
>
>> I like the change to 5.2.3 but think that it needs to go further.
>>
>> -08 split out two cases,
>>
>> Incoming SSN Reset Request received but no response yet to the Outgoing
> request
>> Incoming SSN Reset Request received after response to the Outgoing request
>>
>> assuming that the Incoming and Outgoing requests have overlapping stream
>> numbers.
>>
>> -09 subdivides the first case into overlaps completely and overlaps partially
>> but
>> I think that the second case is also in need of subdivision in the same way.
>>
>> And, a point of clarification, in any of the four cases, is it required to
> send
>> just
>> the one response, ie you cannot send two responses in the partial overlap
> case,
>> one saying no-op and the will do (or won't do!)?
>>
>>
>> Tom Petch
>>
>
********************************************************************************
> ********
>
> You never replied to that so I had assumed you were happy with the changes..
if
> not
> I would be more than glad to hear your suggested changes...
>
>
> R
>
>
>> that is the problem, that the latest revision was pushed out too soon, before
>> the comments on the previous version had been adequately (IMO) resolved.
>> Which, in turn, brings us full circle, that insufficient interest was
> expressed
>> by the WG in that previous version to get the comments resolved; so should
>> this progress to RFC or no, is it worth standardising? I have no basis on
> which
>> to say.
>>
>> Tom Petch
>>
>>> James & Gorry
>>> TSVWG chairs
>>>
>>>
>>> At 10:07 PM 2/7/2011, James M. Polk wrote:
>>>> TSVWG
>>>>
>>>> I am starting the WGLC for
>>>>
>>>> "Stream Control Transmission Protocol (SCTP) Stream Reconfiguration"
>>>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-strrst/
>>>>
>>>> this is a 2 week WGLC, ending February 22nd, 2011 or when the chairs
>>>> feel the WG has reviewed the draft and reached consensus to progress
>>>> towards the ADs with the goal of becoming a proposed standard (PS) RFC.
>>>>
>>>> The chairs require substantive feedback from the WG regarding this
>>>> draft before consensus can be called.
>>>>
>>>> I will be the document shepherd.
>>>>
>>>> James
>>>> TSVWG chair
>>>
>>
>
> -----
> Randall Stewart
> randall@lakerest.net
>
>
>
>
>


From randall@lakerest.net  Sat Mar 19 16:42:51 2011
Return-Path: <randall@lakerest.net>
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 4E34A3A6A53 for <tsvwg@core3.amsl.com>; Sat, 19 Mar 2011 16:42:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.943
X-Spam-Level: 
X-Spam-Status: No, score=-1.943 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 PrkfqIu3TECb for <tsvwg@core3.amsl.com>; Sat, 19 Mar 2011 16:42:50 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 55ACB3A6A41 for <tsvwg@ietf.org>; Sat, 19 Mar 2011 16:42:47 -0700 (PDT)
Received: from [192.168.2.69] (pool-173-67-89-161.snfcca.dsl-w.verizon.net [173.67.89.161]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2JNeIus066110 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 19 Mar 2011 19:40:22 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Randy Stewart <randall@lakerest.net>
X-Priority: 3
In-Reply-To: <01ae01cbe66f$c4d2d1a0$4001a8c0@gateway.2wire.net>
Date: Sat, 19 Mar 2011 19:40:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <95CA9565-AD4E-487F-9109-1A62F5863A69@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net> <29AEBA37-6157-44E9-8FD7-B44023DF6CD7@lakerest.net> <024801cbe593$4f2d1960$4001a8c0@gateway.2wire.net> <646C4AFE-1AAE-419B-BB6D-8670D292F563@lurchi.franken.de> <01ae01cbe66f$c4d2d1a0$4001a8c0@gateway.2wire.net>
To: "t.petch" <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.1082)
Cc: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>, "James M. Polk" <jmpolk@cisco.com>, tsvwg <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: Sat, 19 Mar 2011 23:42:51 -0000

Tom:

I actually agree with Michael on this one. Removing streams is
a messy business and cause a huge number of headaches. The original
drafts way back in 2000 had this (and addition) in them and it was =
removed
and was quite a relief implementation wise.

I don't support the removal of streams. Start small, grow them (by =
adding) but if
you want to remove, shutdown and restart.=20

Otherwise you end up with all sorts of issues with missing streams and =
other such
nasty items.

As to his other comments.. you can't eliminate out-of-band if you want =
to add. And=20
having things in-band creates all sorts of additional traffic (if I want =
to reset
more than one stream)... It really heads down the path of the debate =
with Kacheong.. more
of preference then substantial difference.

R
On Mar 19, 2011, at 3:56 PM, t.petch wrote:

> ----- Original Message -----
> From: "Michael T=FCxen" <Michael.Tuexen@lurchi.franken.de>
> To: "t.petch" <ietfc@btconnect.com>
> Cc: "Randy Stewart" <randall@lakerest.net>; "James M. Polk" =
<jmpolk@cisco.com>;
> "tsvwg" <tsvwg@ietf.org>
> Sent: Friday, March 18, 2011 8:45 PM
> On Mar 18, 2011, at 6:38 PM, t.petch wrote:
>=20
>> Randy
>>=20
>> Yes, I did get your e-mail and did understand that you would =
implement it
>> in -10 after WGLC.  My point was rather a process one, that I thought
>> that at least one earlier version of the I-D came out too soon, =
before
>> consensus had been reached on the list, leading to extra work and
>> the possibility of errors.
>>=20
>> And I see something of the same now, that K. Poon comes up with
>> suggestions and you say yes good we will do that.  I think no, that =
that
>> is premature, wait for others to catch up and comment.  And if noone
>> comments, then I suspect that there is no consensus and that the
>> change should not be made.  At WGLC time, in my book, you need
>> a solid reason to change, not a 'good idea' from one participant.
>> At least give others a chance to say yea or nay.
>>=20
>> For myself, I think that punctuation in a short label is a bad thing =
ie
>> RE-CONFIG
>> is always a mistake.  Some will forget it, some will misplace it.  It =
can
>> only create errors (a longer label, eg channel-binding, is a =
different
> matter).
>>=20
>> And if the suggested change has not come up in the 10 previous =
iterations
>> of the I-D, then I suspect that the benefit of it is not great, not =
enough to
> be
>> worth making it at this time; with my previous suggestions, you did =
miss out
>> some, for all the power of sed, grep etc, so I suspect that some will =
be
> missed
>> now, which will be worse than either the old wording or new.
>=20
> Hi Tom,
>=20
> I can send you the current version, which we have in CVS and you can =
have a
> look.
> While doing the changes I fixed some editorial errors which I missed =
earlier.
>=20
> Let me know if you want a copy.
> <tp>
> Michael
>=20
> Thanks for the offer but I'll take a raincheck.
>=20
> I think that more time should be given to consider Brian's comments =
before
> I want to see fresh text.  His point on removing streams seems a good
> one, and that on in- versus out of- band is interesting.
>=20
> Tom
> </tp>
>=20
> Best regards
> Michael
>=20
>> Tom Petch
>>=20
>> ----- Original Message -----
>> From: "Randy Stewart" <randall@lakerest.net>
>> To: "t.petch" <ietfc@btconnect.com>
>> Cc: "tsvwg" <tsvwg@ietf.org>; "James M. Polk" <jmpolk@cisco.com>
>> Sent: Wednesday, March 16, 2011 3:05 PM
>> Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
>>=20
>>=20
>>=20
>> On Mar 16, 2011, at 4:31 AM, t.petch wrote:
>>=20
>>> ----- Original Message -----
>>> From: "James M. Polk" <jmpolk@cisco.com>
>>> To: "tsvwg" <tsvwg@ietf.org>
>>> Sent: Sunday, March 13, 2011 9:48 PM
>>>=20
>>>> TSVWG
>>>>=20
>>>> The WG chairs have determined the WGLC for our SCTP Stream
>>>> Reconfiguration ID continues (i.e., it has not concluded at the 2
>>>> week window) due to lack of feedback to the list. No one has
>>>> commented in a review format that they believe this ID should
>>>> progress. No one has even sent a note merely saying this ID in its
>>>> present form is good to go. That lack of any feedback is troubling
>>>> and could be a sign of a lack of interest in this ID.
>>>>=20
>>>> The WG chairs like the idea of (and within) this draft, but we need
>>>> transport experts to tell us this, and if the ID in its present =
form
>>>> is good enough to implement to without those implementations having
>>>> errors or causing bad behavior in SCTP because of how the ID is
>>>> written (focusing mostly on the instructions to implementers in the =
ID).
>>>>=20
>>>> We chairs want folks to show or assert they have reviewed this ID =
and
>>>> give feedback to the list (and not unicast to the chairs). This ID
>>>> cannot progress without that feedback.
>>>=20
>>> I am sitting on my hands because I did not consider the I-D ready =
for last
>> call
>>> but also, I do not have a view as to whether or not this I-D will be
>>> implemented,
>>=20
>>=20
>> Can't say on other implementations but it is in FreeBSD ;-)
>>=20
>>> whether or not the additional function is worth standardising - I =
simply do
>> not
>>> have the contacts to make a judgement on this.
>>>=20
>>> I did comment on a previous version, and the comment was not =
resolved so I
>>> decided to wait
>>> until it was before commenting further, be that at IETF LC if so it =
be.  I
> did
>>> get
>>> a response about not wanting to push out too many revisions but, =
perversely,
>>=20
>>=20
>> Tom, I did too respond to your comment.. and the update was posted on =
the
>> mailing
>> list... Did you not receive the email (sometimes my emails do not get =
through
> it
>> would appear)..  I can wander back on the mailing list archives and =
find it
> ...
>> let me see:
>>=20
>> Here it is from Feb 9th:
>>=20
> =
**************************************************************************=
******
>> *******
>> Tom:
>>=20
>> Just to let you know I did NOT forget about this... Here is the text =
that is
>> waiting in the xml for the -10 revision:
>> ***********************************************************
>> When a peer endpoint requests a Incoming SSN Reset Request it is
>> possible that the local endpoint has just sent an Outgoing SSN Reset
>> Request on the same stream and has not yet received a response.  In
>> such a case the local endpoint MUST do the following:
>>=20
>> 1) If the stream reset overlaps the outstanding request completely
>>    respond to the requestor with an acknowledgment indicating that
>>    there was 'Nothing to do'.
>>=20
>> 2) Otherwise process the stream reset request normally responding to
>>    the requestor with an acknowledgment.
>>=20
>> It is also possible that the Incoming request will arrive after the
>> Outgoing SSN Reset Request just completed.  In such a case the local
>> endpoint MUST do the following:
>>=20
>> 1) If the stream reset overlaps the outstanding request completely
>>    all of the streams being requested will be already set to 0.  If
>>    so, the local endpoint SHOULD send back a Stream Reset Response
>>    with the success code "Nothing to do".
>>=20
>> 2) Otherwise process the stream reset request normally responding to
>>    the requestor an acknowledgment.
>>=20
>> Note that in either race condition the local endpoint could
>> optionally also perform the reset.  This would result in streams that
>> are already at sequence 0 being reset again to 0 which would cause no
>> harm to the application but will add an extra message to the network.
>>=20
>> Note also that in any of the race conditions listed above the
>> receiver MUST NOT send more than one response.  In other words two
>> responses MUST NOT be sent for the same request.
>>=20
>> *******************************************************************
>>=20
>> When we get any other comments after LC I will issue the updated =
draft with
> the
>> above...
>>=20
>> If you would like further changes or this does not satisfy your =
comments below
>> let me know.. you can even send suggested text :-)
>>=20
>> Best wishes
>>=20
>> R
>> On Jan 15, 2011, at 6:49 AM, t.petch wrote:
>>=20
>>> I like the change to 5.2.3 but think that it needs to go further.
>>>=20
>>> -08 split out two cases,
>>>=20
>>> Incoming SSN Reset Request received but no response yet to the =
Outgoing
>> request
>>> Incoming SSN Reset Request received after response to the Outgoing =
request
>>>=20
>>> assuming that the Incoming and Outgoing requests have overlapping =
stream
>>> numbers.
>>>=20
>>> -09 subdivides the first case into overlaps completely and overlaps =
partially
>>> but
>>> I think that the second case is also in need of subdivision in the =
same way.
>>>=20
>>> And, a point of clarification, in any of the four cases, is it =
required to
>> send
>>> just
>>> the one response, ie you cannot send two responses in the partial =
overlap
>> case,
>>> one saying no-op and the will do (or won't do!)?
>>>=20
>>>=20
>>> Tom Petch
>>>=20
>>=20
> =
**************************************************************************=
******
>> ********
>>=20
>> You never replied to that so I had assumed you were happy with the =
changes..
> if
>> not
>> I would be more than glad to hear your suggested changes...
>>=20
>>=20
>> R
>>=20
>>=20
>>> that is the problem, that the latest revision was pushed out too =
soon, before
>>> the comments on the previous version had been adequately (IMO) =
resolved.
>>> Which, in turn, brings us full circle, that insufficient interest =
was
>> expressed
>>> by the WG in that previous version to get the comments resolved; so =
should
>>> this progress to RFC or no, is it worth standardising? I have no =
basis on
>> which
>>> to say.
>>>=20
>>> Tom Petch
>>>=20
>>>> James & Gorry
>>>> TSVWG chairs
>>>>=20
>>>>=20
>>>> At 10:07 PM 2/7/2011, James M. Polk wrote:
>>>>> TSVWG
>>>>>=20
>>>>> I am starting the WGLC for
>>>>>=20
>>>>> "Stream Control Transmission Protocol (SCTP) Stream =
Reconfiguration"
>>>>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-strrst/
>>>>>=20
>>>>> this is a 2 week WGLC, ending February 22nd, 2011 or when the =
chairs
>>>>> feel the WG has reviewed the draft and reached consensus to =
progress
>>>>> towards the ADs with the goal of becoming a proposed standard (PS) =
RFC.
>>>>>=20
>>>>> The chairs require substantive feedback from the WG regarding this
>>>>> draft before consensus can be called.
>>>>>=20
>>>>> I will be the document shepherd.
>>>>>=20
>>>>> James
>>>>> TSVWG chair
>>>>=20
>>>=20
>>=20
>> -----
>> Randall Stewart
>> randall@lakerest.net
>>=20
>>=20
>>=20
>>=20
>>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From ietfc@btconnect.com  Sun Mar 20 02:51:32 2011
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 311683A6A20 for <tsvwg@core3.amsl.com>; Sun, 20 Mar 2011 02:51:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.662
X-Spam-Level: 
X-Spam-Status: No, score=-0.662 tagged_above=-999 required=5 tests=[AWL=-0.878, BAYES_20=-0.74, J_CHICKENPOX_15=0.6, 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 A24+8x1Ip0qY for <tsvwg@core3.amsl.com>; Sun, 20 Mar 2011 02:51:30 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by core3.amsl.com (Postfix) with ESMTP id 44F773A6A0D for <tsvwg@ietf.org>; Sun, 20 Mar 2011 02:51:29 -0700 (PDT)
Received: from host217-44-145-106.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.106]) by c2beaomr10.btconnect.com with SMTP id CDR05753; Sun, 20 Mar 2011 09:52:50 +0000 (GMT)
Message-ID: <006901cbe6db$832bc060$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Randy Stewart" <randall@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net> <29AEBA37-6157-44E9-8FD7-B44023DF6CD7@lakerest.net> <024801cbe593$4f2d1960$4001a8c0@gateway.2wire.net> <646C4AFE-1AAE-419B-BB6D-8670D292F563@lurchi.franken.de> <01ae01cbe66f$c4d2d1a0$4001a8c0@gateway.2wire.net> <95CA9565-AD4E-487F-9109-1A62F5863A69@lakerest.net>
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Date: Sun, 20 Mar 2011 09:47:54 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4D85CE71.00AC, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0207.4D85CE72.0174,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>, "James M. Polk" <jmpolk@cisco.com>, tsvwg <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: Sun, 20 Mar 2011 09:51:32 -0000

----- Original Message -----
From: "Randy Stewart" <randall@lakerest.net>
To: "t.petch" <ietfc@btconnect.com>
Cc: "Michael Tüxen" <Michael.Tuexen@lurchi.franken.de>; "James M. Polk"
<jmpolk@cisco.com>; "tsvwg" <tsvwg@ietf.org>
Sent: Sunday, March 20, 2011 12:40 AM

Tom:

I actually agree with Michael on this one. Removing streams is
a messy business and cause a huge number of headaches. The original
drafts way back in 2000 had this (and addition) in them and it was removed
and was quite a relief implementation wise.

I don't support the removal of streams. Start small, grow them (by adding) but
if
you want to remove, shutdown and restart.

Otherwise you end up with all sorts of issues with missing streams and other
such
nasty items.

<tp>
Yes, restart is what I had assumed people would do, although I had not
realised the (unfortunate) implementation detail of how people had
used the stream number.  (I would have expected a bit matrix of
streams in use).

Still, I am in favour of sitting on my hands for a bit longer to see what others
may
say about Brian's ideas, before going through the text again.

Tom Petch
</tp>

As to his other comments.. you can't eliminate out-of-band if you want to add.
And
having things in-band creates all sorts of additional traffic (if I want to
reset
more than one stream)... It really heads down the path of the debate with
Kacheong.. more
of preference then substantial difference.

R
On Mar 19, 2011, at 3:56 PM, t.petch wrote:

> ----- Original Message -----
> From: "Michael Tüxen" <Michael.Tuexen@lurchi.franken.de>
> To: "t.petch" <ietfc@btconnect.com>
> Cc: "Randy Stewart" <randall@lakerest.net>; "James M. Polk"
<jmpolk@cisco.com>;
> "tsvwg" <tsvwg@ietf.org>
> Sent: Friday, March 18, 2011 8:45 PM
> On Mar 18, 2011, at 6:38 PM, t.petch wrote:
>
>> Randy
>>
>> Yes, I did get your e-mail and did understand that you would implement it
>> in -10 after WGLC.  My point was rather a process one, that I thought
>> that at least one earlier version of the I-D came out too soon, before
>> consensus had been reached on the list, leading to extra work and
>> the possibility of errors.
>>
>> And I see something of the same now, that K. Poon comes up with
>> suggestions and you say yes good we will do that.  I think no, that that
>> is premature, wait for others to catch up and comment.  And if noone
>> comments, then I suspect that there is no consensus and that the
>> change should not be made.  At WGLC time, in my book, you need
>> a solid reason to change, not a 'good idea' from one participant.
>> At least give others a chance to say yea or nay.
>>
>> For myself, I think that punctuation in a short label is a bad thing ie
>> RE-CONFIG
>> is always a mistake.  Some will forget it, some will misplace it.  It can
>> only create errors (a longer label, eg channel-binding, is a different
> matter).
>>
>> And if the suggested change has not come up in the 10 previous iterations
>> of the I-D, then I suspect that the benefit of it is not great, not enough to
> be
>> worth making it at this time; with my previous suggestions, you did miss out
>> some, for all the power of sed, grep etc, so I suspect that some will be
> missed
>> now, which will be worse than either the old wording or new.
>
> Hi Tom,
>
> I can send you the current version, which we have in CVS and you can have a
> look.
> While doing the changes I fixed some editorial errors which I missed earlier.
>
> Let me know if you want a copy.
> <tp>
> Michael
>
> Thanks for the offer but I'll take a raincheck.
>
> I think that more time should be given to consider Brian's comments before
> I want to see fresh text.  His point on removing streams seems a good
> one, and that on in- versus out of- band is interesting.
>
> Tom
> </tp>
>
> Best regards
> Michael
>
>> Tom Petch
>>
>> ----- Original Message -----
>> From: "Randy Stewart" <randall@lakerest.net>
>> To: "t.petch" <ietfc@btconnect.com>
>> Cc: "tsvwg" <tsvwg@ietf.org>; "James M. Polk" <jmpolk@cisco.com>
>> Sent: Wednesday, March 16, 2011 3:05 PM
>> Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
>>
>>
>>
>> On Mar 16, 2011, at 4:31 AM, t.petch wrote:
>>
>>> ----- Original Message -----
>>> From: "James M. Polk" <jmpolk@cisco.com>
>>> To: "tsvwg" <tsvwg@ietf.org>
>>> Sent: Sunday, March 13, 2011 9:48 PM
>>>
>>>> TSVWG
>>>>
>>>> The WG chairs have determined the WGLC for our SCTP Stream
>>>> Reconfiguration ID continues (i.e., it has not concluded at the 2
>>>> week window) due to lack of feedback to the list. No one has
>>>> commented in a review format that they believe this ID should
>>>> progress. No one has even sent a note merely saying this ID in its
>>>> present form is good to go. That lack of any feedback is troubling
>>>> and could be a sign of a lack of interest in this ID.
>>>>
>>>> The WG chairs like the idea of (and within) this draft, but we need
>>>> transport experts to tell us this, and if the ID in its present form
>>>> is good enough to implement to without those implementations having
>>>> errors or causing bad behavior in SCTP because of how the ID is
>>>> written (focusing mostly on the instructions to implementers in the ID).
>>>>
>>>> We chairs want folks to show or assert they have reviewed this ID and
>>>> give feedback to the list (and not unicast to the chairs). This ID
>>>> cannot progress without that feedback.
>>>
>>> I am sitting on my hands because I did not consider the I-D ready for last
>> call
>>> but also, I do not have a view as to whether or not this I-D will be
>>> implemented,
>>
>>
>> Can't say on other implementations but it is in FreeBSD ;-)
>>
>>> whether or not the additional function is worth standardising - I simply do
>> not
>>> have the contacts to make a judgement on this.
>>>
>>> I did comment on a previous version, and the comment was not resolved so I
>>> decided to wait
>>> until it was before commenting further, be that at IETF LC if so it be.  I
> did
>>> get
>>> a response about not wanting to push out too many revisions but, perversely,
>>
>>
>> Tom, I did too respond to your comment.. and the update was posted on the
>> mailing
>> list... Did you not receive the email (sometimes my emails do not get through
> it
>> would appear)..  I can wander back on the mailing list archives and find it
> ...
>> let me see:
>>
>> Here it is from Feb 9th:
>>
>
********************************************************************************
>> *******
>> Tom:
>>
>> Just to let you know I did NOT forget about this... Here is the text that is
>> waiting in the xml for the -10 revision:
>> ***********************************************************
>> When a peer endpoint requests a Incoming SSN Reset Request it is
>> possible that the local endpoint has just sent an Outgoing SSN Reset
>> Request on the same stream and has not yet received a response.  In
>> such a case the local endpoint MUST do the following:
>>
>> 1) If the stream reset overlaps the outstanding request completely
>>    respond to the requestor with an acknowledgment indicating that
>>    there was 'Nothing to do'.
>>
>> 2) Otherwise process the stream reset request normally responding to
>>    the requestor with an acknowledgment.
>>
>> It is also possible that the Incoming request will arrive after the
>> Outgoing SSN Reset Request just completed.  In such a case the local
>> endpoint MUST do the following:
>>
>> 1) If the stream reset overlaps the outstanding request completely
>>    all of the streams being requested will be already set to 0.  If
>>    so, the local endpoint SHOULD send back a Stream Reset Response
>>    with the success code "Nothing to do".
>>
>> 2) Otherwise process the stream reset request normally responding to
>>    the requestor an acknowledgment.
>>
>> Note that in either race condition the local endpoint could
>> optionally also perform the reset.  This would result in streams that
>> are already at sequence 0 being reset again to 0 which would cause no
>> harm to the application but will add an extra message to the network.
>>
>> Note also that in any of the race conditions listed above the
>> receiver MUST NOT send more than one response.  In other words two
>> responses MUST NOT be sent for the same request.
>>
>> *******************************************************************
>>
>> When we get any other comments after LC I will issue the updated draft with
> the
>> above...
>>
>> If you would like further changes or this does not satisfy your comments
below
>> let me know.. you can even send suggested text :-)
>>
>> Best wishes
>>
>> R
>> On Jan 15, 2011, at 6:49 AM, t.petch wrote:
>>
>>> I like the change to 5.2.3 but think that it needs to go further.
>>>
>>> -08 split out two cases,
>>>
>>> Incoming SSN Reset Request received but no response yet to the Outgoing
>> request
>>> Incoming SSN Reset Request received after response to the Outgoing request
>>>
>>> assuming that the Incoming and Outgoing requests have overlapping stream
>>> numbers.
>>>
>>> -09 subdivides the first case into overlaps completely and overlaps
partially
>>> but
>>> I think that the second case is also in need of subdivision in the same way.
>>>
>>> And, a point of clarification, in any of the four cases, is it required to
>> send
>>> just
>>> the one response, ie you cannot send two responses in the partial overlap
>> case,
>>> one saying no-op and the will do (or won't do!)?
>>>
>>>
>>> Tom Petch
>>>
*******************************************************************************
>>
>> You never replied to that so I had assumed you were happy with the changes..
> if
>> not
>> I would be more than glad to hear your suggested changes...
>>
>> R
>>
>>> that is the problem, that the latest revision was pushed out too soon,
before
>>> the comments on the previous version had been adequately (IMO) resolved.
>>> Which, in turn, brings us full circle, that insufficient interest was
>> expressed
>>> by the WG in that previous version to get the comments resolved; so should
>>> this progress to RFC or no, is it worth standardising? I have no basis on
>> which
>>> to say.
>>>
>>> Tom Petch
>>>
>>>> James & Gorry
>>>> TSVWG chairs
>>>> At 10:07 PM 2/7/2011, James M. Polk wrote:
>>>>> TSVWG
>>>>>
>>>>> I am starting the WGLC for
>>>>>
>>>>> "Stream Control Transmission Protocol (SCTP) Stream Reconfiguration"
>>>>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-strrst/
>>>>>
>>>>> this is a 2 week WGLC, ending February 22nd, 2011 or when the chairs
>>>>> feel the WG has reviewed the draft and reached consensus to progress
>>>>> towards the ADs with the goal of becoming a proposed standard (PS) RFC.
>>>>>
>>>>> The chairs require substantive feedback from the WG regarding this
>>>>> draft before consensus can be called.
>>>>>
>>>>> I will be the document shepherd.
>>>>>
>>>>> James
>>>>> TSVWG chair
>> -----
>> Randall Stewart
>> randall@lakerest.net
-----
Randall Stewart
randall@lakerest.net


From ka-cheong.poon@oracle.com  Sun Mar 20 21:11:18 2011
Return-Path: <ka-cheong.poon@oracle.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 31D1F3A66B4 for <tsvwg@core3.amsl.com>; Sun, 20 Mar 2011 21:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.839
X-Spam-Level: 
X-Spam-Status: No, score=-3.839 tagged_above=-999 required=5 tests=[AWL=-1.584, BAYES_00=-2.599, FRT_STOCK2=3.988, RCVD_IN_DNSWL_MED=-4, 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 8HaP8ZvS7V8w for <tsvwg@core3.amsl.com>; Sun, 20 Mar 2011 21:11:17 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id AB5A73A6765 for <tsvwg@ietf.org>; Sun, 20 Mar 2011 21:11:16 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2L4Clwr021643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Mon, 21 Mar 2011 04:12:48 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2L4CkYv022346 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Mon, 21 Mar 2011 04:12:47 GMT
Received: from abhmt004.oracle.com (abhmt004.oracle.com [141.146.116.13]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2L4CkS8028855 for <tsvwg@ietf.org>; Sun, 20 Mar 2011 23:12:46 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 20 Mar 2011 21:12:45 -0700
Message-ID: <4D86D034.4020704@oracle.com>
Date: Mon, 21 Mar 2011 12:12:36 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <0DF4BFE2-2E9C-42E5-9377-F5CD427D5E30@lurchi.franken.de> <4D809432.5050601@oracle.com> <F3AF1842-07FB-4F06-8501-B2EDB1309438@lurchi.franken.de> <4D81E2D1.3010201@oracle.com> <41FD39DE-A3C4-4A01-BD0E-16EA0F7525D7@lurchi.franken.de>
In-Reply-To: <41FD39DE-A3C4-4A01-BD0E-16EA0F7525D7@lurchi.franken.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Source-IP: acsmt358.oracle.com [141.146.40.158]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090209.4D86D03F.0077,ss=1,fgs=0
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, 21 Mar 2011 04:11:18 -0000

On 03/18/11 04:09 AM, Michael Tüxen wrote:
> On Mar 17, 2011, at 11:30 AM, Kacheong Poon wrote:
>
>> On 03/16/11 08:32 PM, Michael Tüxen wrote:
>>
>>> But the above is not sufficient. Resetting a stream does not
>>> only reset the counter but also
>>> * signals that it is requested
>>> * acknowledges that is has been performed
>>
>>
>> The above is started by the app layer, right?  So
>> the app layer already needs to perform the action.  It
>> is not something which is initiated by the transport
>> layer and must be done in the transport layer.  It is
>> an app layer protocol.
> The request is initiated by the app (a setsockopt call), but
> it does not perform the request (creating a packet, sending it,
> waiting for the response, parsing the response). In particular
> the other side does not have to perform anything.


What you wrote above is still that the handling should not
be done in the app layer (again it can be in a library), which
I honestly don't see why...


> At least I do not think so...
> The service we are discussing is not an arbitrary service
> an application requires, but it is tightly related to the
> streams.
>
> I think it can be described extending the service SCTP
> provides from:
> * a static number of non-resettable uni-directional message channels
> to
> * a dynamic number of resettable uni-directional message channels
>
> I think this is not an arbitrary service...


Why is a reset needed at the transport layer?  So far, the
only reason given is about app layer wanting to do something
very simple.  And it can be done at the app layer easily, and
much simpler than in the transport layer.  IMHO, this simple
reason does not justify the need to have a transport layer
reset mechanism.  The authors must provide more concrete
reasoning why a reset is needed at the transport layer.


>> While the meaning of adding and removing an SCTP stream is
>> clear, I think "reuse" needs to be defined carefully.  An
>> app can use a stream and then not use it for a while.  There
>> is nothing to prevent an app to re-use it later.
> It is especially about the signalling of "I'm done with this stream".


And why is it so difficult for an app to just send, say an
unordered message to signal that?  Or any other mechanism
currently defined in the socket API?  Isn't it much simpler
to do it at the app layer?


>> Can you explain why resetting SSN/TSN is equivalent to
>> re-using a stream or the association?  BTW, there is still
>> no example given to the use of resetting TSN.  I think this
>> must be added to the draft.
> Regarding the SSN/TSN reset, see Randys examples.


Then please pull out the reset stuff from the current draft
and create another one.  As it stands, I can understand
the need to have a re-config chunk for adding additional
streams.  This is reasonable and can only be done at the
SCTP layer.  And there is another IETF protocol already
making use of it.  It makes sense to go ahead with it alone.


>> So far, I think the key point you've raised to support
>> doing it at the transport layer is that it can then be
>> used by any apps.  I think doing it in a library achieves
>> the same thing.  Don't you agree?
> Somewhat. You need to define a protocol for that. Including
> negotiating for it. So in case of HTTP proxy communication,
> it might be hard to do this in an interoperable way without
> extending the HTTP, i.e. the application protocol.


I am not sure I understand this.  In your example, you
want to use a SCTP proxy for TCP HTTP connections.  So
multiple HTTP/TCP connections can be multiplexed into one
SCTP associations.  This means that there must be two ends
talking SCTP with each other.  And the other end of SCTP
associations de=multiplexes the single SCTP associations
back to multiple HTTP/TCP connections.  You can do whatever
you want between these two SCTP proxies.  There is no need
to extend HTTP.


> What you could do is to use HTTP/Kacheongs layer/SCTP.
> But what would you send initially to figure out that you peer
> talks HTTP/Kacheongs layer/SCTP and not only HTTP/SCTP?


The above is not correct.  HTTP still runs on top of TCP.
The SCTP proxy talks TCP on one side and SCTP on the
other side.  There are two SCTP proxies talking to each
other.  I don't think you are saying that an SCTP
association can communicate with a TCP connection, right?
Or which example are you referring to?


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Sun Mar 20 21:31:39 2011
Return-Path: <ka-cheong.poon@oracle.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 5FBF63A65A5 for <tsvwg@core3.amsl.com>; Sun, 20 Mar 2011 21:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.728
X-Spam-Level: 
X-Spam-Status: No, score=-5.728 tagged_above=-999 required=5 tests=[AWL=0.515,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 izniM2ojFvZT for <tsvwg@core3.amsl.com>; Sun, 20 Mar 2011 21:31:37 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 5C9E53A6405 for <tsvwg@ietf.org>; Sun, 20 Mar 2011 21:31:37 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2L4X8UZ019643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Mon, 21 Mar 2011 04:33:09 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2L4X7WQ028553 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Mon, 21 Mar 2011 04:33:08 GMT
Received: from abhmt018.oracle.com (abhmt018.oracle.com [141.146.116.27]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2L4X7XN008585 for <tsvwg@ietf.org>; Sun, 20 Mar 2011 23:33:07 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 20 Mar 2011 21:33:06 -0700
Message-ID: <4D86D500.80807@oracle.com>
Date: Mon, 21 Mar 2011 12:33:04 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>
In-Reply-To: <201102080311.p183BpvU025288@sj-core-2.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt358.oracle.com [141.146.40.158]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090203.4D86D504.0035,ss=1,fgs=0
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, 21 Mar 2011 04:31:39 -0000

On 02/ 8/11 11:07 AM, James M. Polk wrote:

> this is a 2 week WGLC, ending February 22nd, 2011 or when the chairs
> feel the WG has reviewed the draft and reached consensus to progress
> towards the ADs with the goal of becoming a proposed standard (PS) RFC.


There has been a long email chain.  But I guess one main issue
with the current draft is that there is not enough supporting
reason for adding the SSN reset mechanism and no reason given
to support the TSN reset mechanism.  The reason given so far
is about removing the need to have app layer protocol mechanism.
But in all the example use given, the app layer protocol mechanism
is actually very easy to do and much simpler to implement.  There
is no need to have a transport layer mechanism.  It is a dangerous
design approach to keep on making the transport layer "fatter"
just to satisfy such app requests which should be done at the app
layer.  There may be reason to have such reset mechanism in the
transport layer.  But we need concrete proposal.

I don't think it is a  good idea to have a standard track draft
to be a PS RFC without much justification.  The stream addition
mechanism in the draft is justified and the mechanism itself
is sound.  Since it is also requested by IPFIX, I'd suggest that
the authors pull out the reset stuff and go ahead with a draft
about the stream addition mechanism alone.  The author can then
have another draft focusing on the reset stuff and reasoning.
And we can comment on that and on whether that mechanism is sound.

Just my $0.02...


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From randall@lakerest.net  Mon Mar 21 08:16:52 2011
Return-Path: <randall@lakerest.net>
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 B7DD528C14F for <tsvwg@core3.amsl.com>; Mon, 21 Mar 2011 08:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.097
X-Spam-Level: 
X-Spam-Status: No, score=-0.097 tagged_above=-999 required=5 tests=[AWL=2.146,  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 Jpbp4v3GcySz for <tsvwg@core3.amsl.com>; Mon, 21 Mar 2011 08:16:51 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 0A5163A687C for <tsvwg@ietf.org>; Mon, 21 Mar 2011 08:16:50 -0700 (PDT)
Received: from mobile-166-187-199-103.mycingular.net (mobile-166-187-199-103.mycingular.net [166.187.199.103] (may be forged)) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2LFID1L055060 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 21 Mar 2011 11:18:19 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <4D86D500.80807@oracle.com>
Date: Mon, 21 Mar 2011 11:18:07 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <FF1809C0-5493-4D54-8FF0-56767F252117@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <4D86D500.80807@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
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, 21 Mar 2011 15:16:52 -0000

Kacheong:

I see a large number of responses here... most
from you, Michael and a few from Tom/Benoit and Brian.

How I assess statements on the list (correct me if you
feel I have interpreted your statements on the list wrong) are
as follows:

1) You are definitely against anything but the add feature
   and you are ok with the current out-of-band mechanisms.

2) Tom wished we had reve'd the spec one more time with the
   his previous comments, is not sure of the use case for any
   of it but sees value in it possibly. Would like to see more
   comments on Brian's thoughts...

3) Beniot needs the ADD stream for IPFIX and wants it out :-)

4) Brian likes the idea of stream reconfiguration and thinks
   we have not gone far enough (no delete stream) and would like
   to see the mechanism changed to do all this to be "in-band". 

5) Michael Peter and I (not surprisingly) are in favor of the document
   as it is.... of course I am not sure how much authors count in all
   of this ;-)


So I think, in my assessment, you are the only one speaking against
everything (except the ADD)...

My 2Cents ;-)

R


On Mar 21, 2011, at 12:33 AM, Kacheong Poon wrote:

> On 02/ 8/11 11:07 AM, James M. Polk wrote:
> 
>> this is a 2 week WGLC, ending February 22nd, 2011 or when the chairs
>> feel the WG has reviewed the draft and reached consensus to progress
>> towards the ADs with the goal of becoming a proposed standard (PS) RFC.
> 
> 
> There has been a long email chain.  But I guess one main issue
> with the current draft is that there is not enough supporting
> reason for adding the SSN reset mechanism and no reason given
> to support the TSN reset mechanism.  The reason given so far
> is about removing the need to have app layer protocol mechanism.
> But in all the example use given, the app layer protocol mechanism
> is actually very easy to do and much simpler to implement.  There
> is no need to have a transport layer mechanism.  It is a dangerous
> design approach to keep on making the transport layer "fatter"
> just to satisfy such app requests which should be done at the app
> layer.  There may be reason to have such reset mechanism in the
> transport layer.  But we need concrete proposal.
> 
> I don't think it is a  good idea to have a standard track draft
> to be a PS RFC without much justification.  The stream addition
> mechanism in the draft is justified and the mechanism itself
> is sound.  Since it is also requested by IPFIX, I'd suggest that
> the authors pull out the reset stuff and go ahead with a draft
> about the stream addition mechanism alone.  The author can then
> have another draft focusing on the reset stuff and reasoning.
> And we can comment on that and on whether that mechanism is sound.
> 
> Just my $0.02...
> 
> 
> -- 
> 
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
> 

-----
Randall Stewart
randall@lakerest.net





From wweiss@peerpark.com  Wed Mar 23 23:12:58 2011
Return-Path: <wweiss@peerpark.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 DCA283A67FB for <tsvwg@core3.amsl.com>; Wed, 23 Mar 2011 23:12:58 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ibcepSUB8uAj for <tsvwg@core3.amsl.com>; Wed, 23 Mar 2011 23:12:58 -0700 (PDT)
Received: from p3plsmtpa01-01.prod.phx3.secureserver.net (p3plsmtpa01-01.prod.phx3.secureserver.net [72.167.82.81]) by core3.amsl.com (Postfix) with SMTP id 102BE3A67EE for <tsvwg@ietf.org>; Wed, 23 Mar 2011 23:12:57 -0700 (PDT)
Received: (qmail 8227 invoked from network); 24 Mar 2011 06:14:31 -0000
Received: from unknown (108.20.211.213) by p3plsmtpa01-01.prod.phx3.secureserver.net (72.167.82.81) with ESMTP; 24 Mar 2011 06:14:30 -0000
From: "Walter Weiss" <wweiss@peerpark.com>
To: <tsvwg@ietf.org>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net>	<29AEBA37-6157-44E9-8FD7-B44023DF6CD7@lakerest.net>	<024801cbe593$4f2d1960$4001a8c0@gateway.2wire.net>	<646C4AFE-1AAE-419B-BB6D-8670D292F563@lurchi.franken.de>	<01ae01cbe66f$c4d2d1a0$4001a8c0@gateway.2wire.net> <95CA9565-AD4E-487F-9109-1A62F5863A69@lakerest.net>
In-Reply-To: <95CA9565-AD4E-487F-9109-1A62F5863A69@lakerest.net>
Subject: RE: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Date: Thu, 24 Mar 2011 02:14:32 -0400
Message-ID: <000901cbe9ea$bef64220$3ce2c660$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acvmj5Xpx5lxsGu0RHa55CSqmn5yYQDTFaJg
Content-Language: en-us
Cc: 'Randy Stewart' <randall@lakerest.net>
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: Thu, 24 Mar 2011 06:12:59 -0000

Randy,

>And
>having things in-band creates all sorts of additional traffic (if I want to
reset
>more than one stream)...

Sorry for the delayed feedback. I for one would agree with Brian's
assessment. Personally I would favor an "in-band" reset (that leverages the
existing SACK mechanism) over timers and added complexity in the protocol. I
don't see a significant distinction between a single chunk with many stream
resets and many chunks each with an In-Band Reset other than that you can
support more resets in a single packet. The "Out-Of-Band" approach allows
roughly 7x more resets in a single packet. However, I question the need or
desirability of en mass RESETs. Further, the overhead of "In-Band"
acknowledgements is 0.

While "In-Band" reset is more attractive to me, it has three drawbacks that
I am aware of:
1. Either the non-zero length data chunk requirement must be relaxed or a
new EXTENDED-OPTIONS-DATA chunk that co-exists with DATA chunks must be
defined. The second approach would imply a hybrid chunk which includes all
DATA fields and optional parameters.
2. For either of these approaches, the extension to the protocol must be
negotiated during Association INITialization.
3. There are some unattractive interactions between "In-Band" reset and
PR-SCTP. Most notably a Forward Cumulative TSN chunk cannot be advanced
beyond the oldest un-SACKed reset.

However, the benefits to this approach are that:
1. It is simple.
2. There is no reason (from protocol perspective) for a reset stream to
block either the stream or the association, even when the reset has not been
acknowledged.

I don't see an issue with unordered DATA on a reset stream provided that an
"In-Band" reset is only considered acknowledged when the CUM_TSN_ACK is
advanced and implementations don't propagate unordered data from Gap-Acked
chunks.

My second choice would be to advance the ADD portions independently and use
application level mechanisms to implement reset functionality.

Regards,

-Walter


From randall@lakerest.net  Thu Mar 24 06:54:40 2011
Return-Path: <randall@lakerest.net>
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 E1F453A68CE for <tsvwg@core3.amsl.com>; Thu, 24 Mar 2011 06:54:40 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O-+TiNKkSyUv for <tsvwg@core3.amsl.com>; Thu, 24 Mar 2011 06:54:40 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 73EAD3A68AA for <tsvwg@ietf.org>; Thu, 24 Mar 2011 06:54:37 -0700 (PDT)
Received: from [10.1.1.53] ([10.1.1.53]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2ODu7Hj015959 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 24 Mar 2011 09:56:08 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <000901cbe9ea$bef64220$3ce2c660$@com>
Date: Thu, 24 Mar 2011 09:56:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <79F23C16-2D3D-405D-B410-5F8F952A2697@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net>	<29AEBA37-6157-44E9-8FD7-B44023DF6CD7@lakerest.net>	<024801cbe593$4f2d1960$4001a8c0@gateway.2wire.net>	<646C4AFE-1AAE-419B-BB6D-8670D292F563@lurchi.franken.de>	<01ae01cbe66f$c4d2d1a0$4001a8c0@gateway.2wire.net> <95CA9565-AD4E-487F-9109-1A62F5863A69@lakerest.net> <000901cbe9ea$bef64220$3ce2c660$@com>
To: Walter Weiss <wweiss@peerpark.com>
X-Mailer: Apple Mail (2.1084)
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: Thu, 24 Mar 2011 13:54:41 -0000

Walter:

A few comments in-line..

On Mar 24, 2011, at 2:14 AM, Walter Weiss wrote:

> Randy,
>=20
>> And
>> having things in-band creates all sorts of additional traffic (if I =
want to
> reset
>> more than one stream)...
>=20
> Sorry for the delayed feedback. I for one would agree with Brian's
> assessment. Personally I would favor an "in-band" reset (that =
leverages the
> existing SACK mechanism) over timers and added complexity in the =
protocol. I
> don't see a significant distinction between a single chunk with many =
stream
> resets and many chunks each with an In-Band Reset other than that you =
can
> support more resets in a single packet. The "Out-Of-Band" approach =
allows
> roughly 7x more resets in a single packet. However, I question the =
need or
> desirability of en mass RESETs. Further, the overhead of "In-Band"
> acknowledgements is 0.
>=20
> While "In-Band" reset is more attractive to me, it has three drawbacks =
that
> I am aware of:
> 1. Either the non-zero length data chunk requirement must be relaxed =
or a
> new EXTENDED-OPTIONS-DATA chunk that co-exists with DATA chunks must =
be
> defined. The second approach would imply a hybrid chunk which includes =
all
> DATA fields and optional parameters.
> 2. For either of these approaches, the extension to the protocol must =
be
> negotiated during Association INITialization.
> 3. There are some unattractive interactions between "In-Band" reset =
and
> PR-SCTP. Most notably a Forward Cumulative TSN chunk cannot be =
advanced
> beyond the oldest un-SACKed reset.
>=20
> However, the benefits to this approach are that:
> 1. It is simple.

Its simple only if you count not having to add a new Data chunk type. Or =
if
you don't implement a new data chunk type then you need two types of =
handling of
data chunks and negotiation when you are going to use them. That is not
simple... I think its easier to add the reconfig chunk. Especially when =
you
need this anyway to do the add no matter if you do in-band reset or =
out-of-band
reset. The procedures to handle a "reconfiguration" must be put in place =
i.e.
the add-stream + ack of such.

So instead of just adding one mechanism, you add two..

> 2. There is no reason (from protocol perspective) for a reset stream =
to
> block either the stream or the association, even when the reset has =
not been
> acknowledged.

I think you are incorrect here..

Consider

----SSN1--->
----SSN2--->
----SSN3+Reset??--->XLost
<X>----SSN0--->=20
----SSN1--->
----SSN2--->

Note now there are some difficulties here.

a) First of all many implementations make sure a SSN is within the valid
   range i.e. at point X, normally you consider SSN3-32k(approx its =
actually 2^^16-1) valid and anything
   below 3 or above 32k invalid. Sending an abort to the peer is the =
usual method
   with a protocol violation (this is actually something we tested at =
one of the interops).
   This protection (because it does protect you agains malicious peers) =
now must be thrown away.
   This is an extreme disadvantage.

b) You end up holding SSN0/1 and 2 (which the current draft suggests =
holding on the sending
   side instead of the receiving side). I don't see a lot of difference =
in that.. one
   side will have to hold them... no matter what if there is a loss.... =
if there is no
   loss you delay sending but that does not stop other streams from =
sending... only
   the streams being reset. Which from an application perspective I =
doubt is an issue
   since you are in the process of recycling the stream for a different =
purpose anyway=20
   (or an indication that I am done with the current purpose for stream =
X.. which would
    imply no more data for a moment until the stream is reassigned for =
other work)...



>=20
> I don't see an issue with unordered DATA on a reset stream provided =
that an
> "In-Band" reset is only considered acknowledged when the CUM_TSN_ACK =
is
> advanced and implementations don't propagate unordered data from =
Gap-Acked
> chunks.

And here would be another problem. Why would you not want unordered data
delivered right away? Right now implementations DO propagate unordered =
data
on gap-acked chunks... its why SCTP can free up rwnd space for the =
sender
by delivering such as soon as it arrives...

That to me would be an extreme disadvantage.

So in summary:

1) You still add an out-of-band mechanism.. i.e. the ADD_Stream with
   a necessary ACK so the sender can start using the new stream.
2) You add a new data chunk <or> two types of data chunk handling =20
   with negotiation.
3) You take away some sanity checks that protect against a malicious =
sender.
4) You restrict the delivery of Unordered data...

All of the above seems to me reasons why doing a mixed in-band PLUS =
out-of-band=20
implementation is the wrong approach (unless you get rid of ADD-Stream
you can't escape doing an out-of-band mechanism with an ACK).=20



R

>=20
> My second choice would be to advance the ADD portions independently =
and use
> application level mechanisms to implement reset functionality.
>=20
> Regards,
>=20
> -Walter
>=20

-----
Randall Stewart
randall@lakerest.net





From wweiss@peerpark.com  Thu Mar 24 10:18:07 2011
Return-Path: <wweiss@peerpark.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 45B493A68F2 for <tsvwg@core3.amsl.com>; Thu, 24 Mar 2011 10:18:07 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id taoHsurQQZUO for <tsvwg@core3.amsl.com>; Thu, 24 Mar 2011 10:18:06 -0700 (PDT)
Received: from smtpauth05.prod.mesa1.secureserver.net (smtpauth05.prod.mesa1.secureserver.net [64.202.165.99]) by core3.amsl.com (Postfix) with SMTP id EEF9D3A68F1 for <tsvwg@ietf.org>; Thu, 24 Mar 2011 10:18:05 -0700 (PDT)
Received: (qmail 21983 invoked from network); 24 Mar 2011 17:19:40 -0000
Received: from unknown (108.20.211.213) by smtpauth05.prod.mesa1.secureserver.net (64.202.165.99) with ESMTP; 24 Mar 2011 17:19:39 -0000
From: "Walter Weiss" <wweiss@peerpark.com>
To: "'Randy Stewart'" <randall@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net>	<29AEBA37-6157-44E9-8FD7-B44023DF6CD7@lakerest.net>	<024801cbe593$4f2d1960$4001a8c0@gateway.2wire.net>	<646C4AFE-1AAE-419B-BB6D-8670D292F563@lurchi.franken.de>	<01ae01cbe66f$c4d2d1a0$4001a8c0@gateway.2wire.net> <95CA9565-AD4E-487F-9109-1A62F5863A69@lakerest.net> <000901cbe9ea$bef64220$3ce2c660$@com> <79F23C16-2D3D-405D-B410-5F8F952A2697@lakerest.net>
In-Reply-To: <79F23C16-2D3D-405D-B410-5F8F952A2697@lakerest.net>
Subject: RE: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Date: Thu, 24 Mar 2011 13:19:42 -0400
Message-ID: <000c01cbea47$aacb2a10$00617e30$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvqK0Hhw8V818b3QLKkjI6c/HLYOgAGefww
Content-Language: en-us
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: Thu, 24 Mar 2011 17:18:07 -0000

>-----Original Message-----
>From: Randy Stewart [mailto:randall@lakerest.net]
>Sent: Thursday, March 24, 2011 9:56 AM
>To: Walter Weiss
>Cc: tsvwg@ietf.org
>Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
>
>Walter:
>
>A few comments in-line..
>
>On Mar 24, 2011, at 2:14 AM, Walter Weiss wrote:
>
>> Randy,
>>
>>> And
>>> having things in-band creates all sorts of additional traffic (if I want
to reset
>>> more than one stream)...
>>
>> Sorry for the delayed feedback. I for one would agree with Brian's
>> assessment. Personally I would favor an "in-band" reset (that leverages
the
>> existing SACK mechanism) over timers and added complexity in the
protocol. I
>> don't see a significant distinction between a single chunk with many
stream
>> resets and many chunks each with an In-Band Reset other than that you can
>> support more resets in a single packet. The "Out-Of-Band" approach allows
>> roughly 7x more resets in a single packet. However, I question the need
or
>> desirability of en mass RESETs. Further, the overhead of "In-Band"
>> acknowledgements is 0.
>>
>> While "In-Band" reset is more attractive to me, it has three drawbacks
that
>> I am aware of:
>> 1. Either the non-zero length data chunk requirement must be relaxed or a
>> new EXTENDED-OPTIONS-DATA chunk that co-exists with DATA chunks must be
>> defined. The second approach would imply a hybrid chunk which includes
all
>> DATA fields and optional parameters.
>> 2. For either of these approaches, the extension to the protocol must be
>> negotiated during Association INITialization.
>> 3. There are some unattractive interactions between "In-Band" reset and
>> PR-SCTP. Most notably a Forward Cumulative TSN chunk cannot be advanced
>> beyond the oldest un-SACKed reset.
>>
>> However, the benefits to this approach are that:
>> 1. It is simple.
>
>Its simple only if you count not having to add a new Data chunk type. Or if
>you don't implement a new data chunk type then you need two types of
>handling of
>data chunks and negotiation when you are going to use them. That is not
>simple... I think its easier to add the reconfig chunk. Especially when
>you
>need this anyway to do the add no matter if you do in-band reset or out-
>of-band
>reset. The procedures to handle a "reconfiguration" must be put in place
>i.e.
>the add-stream + ack of such.
>
>So instead of just adding one mechanism, you add two..
>
>> 2. There is no reason (from protocol perspective) for a reset stream
>to
>> block either the stream or the association, even when the reset has
>not been
>> acknowledged.
>
>I think you are incorrect here..
>
>Consider
>
>----SSN1--->
>----SSN2--->
>----SSN3+Reset??--->XLost
><X>----SSN0--->
>----SSN1--->
>----SSN2--->
>
>Note now there are some difficulties here.
>
>a) First of all many implementations make sure a SSN is within the valid
>   range i.e. at point X, normally you consider SSN3-32k(approx its
>actually 2^^16-1) valid and anything
>   below 3 or above 32k invalid. Sending an abort to the peer is the
>usual method
>   with a protocol violation (this is actually something we tested at
>one of the interops).
>   This protection (because it does protect you agains malicious peers)
>now must be thrown away.
>   This is an extreme disadvantage.
>
>b) You end up holding SSN0/1 and 2 (which the current draft suggests
>holding on the sending
>   side instead of the receiving side). I don't see a lot of difference
>in that.. one
>   side will have to hold them... no matter what if there is a loss....
>if there is no
>   loss you delay sending but that does not stop other streams from
>sending... only
>   the streams being reset. Which from an application perspective I
>doubt is an issue
>   since you are in the process of recycling the stream for a different
>purpose anyway
>   (or an indication that I am done with the current purpose for stream
>X.. which would
>    imply no more data for a moment until the stream is reassigned for
>other work)...

Both these points would be true if you restart the SSN to 0. However, if you
continued incrementing the SSN (SSNs should be transparent to the
application), there is no blocking (just a protocol detected gap).

>> I don't see an issue with unordered DATA on a reset stream provided
>that an
>> "In-Band" reset is only considered acknowledged when the CUM_TSN_ACK
>is
>> advanced and implementations don't propagate unordered data from Gap-
>Acked
>> chunks.
>
>And here would be another problem. Why would you not want unordered data
>delivered right away? Right now implementations DO propagate unordered
>data
>on gap-acked chunks... its why SCTP can free up rwnd space for the
>sender
>by delivering such as soon as it arrives...
>
>That to me would be an extreme disadvantage.

Personally, I would prefer receiver side blocking of an unordered DATA chunk
(when there is a gap) to sender side blocking (until reset negotiation has
completed).

Regards,

-Walter


From randall@lakerest.net  Thu Mar 24 15:53:01 2011
Return-Path: <randall@lakerest.net>
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 1F07B3A6906 for <tsvwg@core3.amsl.com>; Thu, 24 Mar 2011 15:53:01 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fOkVxx00WAqP for <tsvwg@core3.amsl.com>; Thu, 24 Mar 2011 15:53:00 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 9F9063A6905 for <tsvwg@ietf.org>; Thu, 24 Mar 2011 15:52:57 -0700 (PDT)
Received: from [10.1.1.53] ([10.1.1.53]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2OMsT84036333 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 24 Mar 2011 18:54:30 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <000c01cbea47$aacb2a10$00617e30$@com>
Date: Thu, 24 Mar 2011 18:54:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <07F575F4-8816-498E-9640-88EEACB48AB0@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net>	<29AEBA37-6157-44E9-8FD7-B44023DF6CD7@lakerest.net>	<024801cbe593$4f2d1960$4001a8c0@gateway.2wire.net>	<646C4AFE-1AAE-419B-BB6D-8670D292F563@lurchi.franken.de>	<01ae01cbe66f$c4d2d1a0$4001a8c0@gateway.2wire.net> <95CA9565-AD4E-487F-9109-1A62F5863A69@lakerest.net> <000901cbe9ea$bef64220$3ce2c660$@com> <79F23C16-2D3D-405D-B410-5F8F952A2697@lakerest.net> <000c01cbea47$aacb2a10$00617e30$@com>
To: Walter Weiss <wweiss@peerpark.com>
X-Mailer: Apple Mail (2.1084)
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: Thu, 24 Mar 2011 22:53:01 -0000

In-line..

On Mar 24, 2011, at 1:19 PM, Walter Weiss wrote:

>=20
>=20
>> -----Original Message-----
>> From: Randy Stewart [mailto:randall@lakerest.net]
>> Sent: Thursday, March 24, 2011 9:56 AM
>> To: Walter Weiss
>> Cc: tsvwg@ietf.org
>> Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
>>=20
>> Walter:
>>=20
>> A few comments in-line..
>>=20
>> On Mar 24, 2011, at 2:14 AM, Walter Weiss wrote:
>>=20
>>> Randy,
>>>=20
>>>> And
>>>> having things in-band creates all sorts of additional traffic (if I =
want
> to reset
>>>> more than one stream)...
>>>=20
>>> Sorry for the delayed feedback. I for one would agree with Brian's
>>> assessment. Personally I would favor an "in-band" reset (that =
leverages
> the
>>> existing SACK mechanism) over timers and added complexity in the
> protocol. I
>>> don't see a significant distinction between a single chunk with many
> stream
>>> resets and many chunks each with an In-Band Reset other than that =
you can
>>> support more resets in a single packet. The "Out-Of-Band" approach =
allows
>>> roughly 7x more resets in a single packet. However, I question the =
need
> or
>>> desirability of en mass RESETs. Further, the overhead of "In-Band"
>>> acknowledgements is 0.
>>>=20
>>> While "In-Band" reset is more attractive to me, it has three =
drawbacks
> that
>>> I am aware of:
>>> 1. Either the non-zero length data chunk requirement must be relaxed =
or a
>>> new EXTENDED-OPTIONS-DATA chunk that co-exists with DATA chunks must =
be
>>> defined. The second approach would imply a hybrid chunk which =
includes
> all
>>> DATA fields and optional parameters.
>>> 2. For either of these approaches, the extension to the protocol =
must be
>>> negotiated during Association INITialization.
>>> 3. There are some unattractive interactions between "In-Band" reset =
and
>>> PR-SCTP. Most notably a Forward Cumulative TSN chunk cannot be =
advanced
>>> beyond the oldest un-SACKed reset.
>>>=20
>>> However, the benefits to this approach are that:
>>> 1. It is simple.
>>=20
>> Its simple only if you count not having to add a new Data chunk type. =
Or if
>> you don't implement a new data chunk type then you need two types of
>> handling of
>> data chunks and negotiation when you are going to use them. That is =
not
>> simple... I think its easier to add the reconfig chunk. Especially =
when
>> you
>> need this anyway to do the add no matter if you do in-band reset or =
out-
>> of-band
>> reset. The procedures to handle a "reconfiguration" must be put in =
place
>> i.e.
>> the add-stream + ack of such.
>>=20
>> So instead of just adding one mechanism, you add two..
>>=20
>>> 2. There is no reason (from protocol perspective) for a reset stream
>> to
>>> block either the stream or the association, even when the reset has
>> not been
>>> acknowledged.
>>=20
>> I think you are incorrect here..
>>=20
>> Consider
>>=20
>> ----SSN1--->
>> ----SSN2--->
>> ----SSN3+Reset??--->XLost
>> <X>----SSN0--->
>> ----SSN1--->
>> ----SSN2--->
>>=20
>> Note now there are some difficulties here.
>>=20
>> a) First of all many implementations make sure a SSN is within the =
valid
>>  range i.e. at point X, normally you consider SSN3-32k(approx its
>> actually 2^^16-1) valid and anything
>>  below 3 or above 32k invalid. Sending an abort to the peer is the
>> usual method
>>  with a protocol violation (this is actually something we tested at
>> one of the interops).
>>  This protection (because it does protect you agains malicious peers)
>> now must be thrown away.
>>  This is an extreme disadvantage.
>>=20
>> b) You end up holding SSN0/1 and 2 (which the current draft suggests
>> holding on the sending
>>  side instead of the receiving side). I don't see a lot of difference
>> in that.. one
>>  side will have to hold them... no matter what if there is a loss....
>> if there is no
>>  loss you delay sending but that does not stop other streams from
>> sending... only
>>  the streams being reset. Which from an application perspective I
>> doubt is an issue
>>  since you are in the process of recycling the stream for a different
>> purpose anyway
>>  (or an indication that I am done with the current purpose for stream
>> X.. which would
>>   imply no more data for a moment until the stream is reassigned for
>> other work)...
>=20
> Both these points would be true if you restart the SSN to 0. However, =
if you
> continued incrementing the SSN (SSNs should be transparent to the
> application), there is no blocking (just a protocol detected gap).

The whole idea of stream-reset is the SSN to go back to 0..

>=20
>>> I don't see an issue with unordered DATA on a reset stream provided
>> that an
>>> "In-Band" reset is only considered acknowledged when the CUM_TSN_ACK
>> is
>>> advanced and implementations don't propagate unordered data from =
Gap-
>> Acked
>>> chunks.
>>=20
>> And here would be another problem. Why would you not want unordered =
data
>> delivered right away? Right now implementations DO propagate =
unordered
>> data
>> on gap-acked chunks... its why SCTP can free up rwnd space for the
>> sender
>> by delivering such as soon as it arrives...
>>=20
>> That to me would be an extreme disadvantage.
>=20
> Personally, I would prefer receiver side blocking of an unordered DATA =
chunk
> (when there is a gap) to sender side blocking (until reset negotiation =
has
> completed).


I don't think Unordered should ever be blocked.. rec or send side..

that is a good point to add to the draft... that blocking should only
be done on ordered sends to streams being reset..

R

>=20
> Regards,
>=20
> -Walter
>=20

-----
Randall Stewart
randall@lakerest.net





From wweiss@peerpark.com  Thu Mar 24 17:56:14 2011
Return-Path: <wweiss@peerpark.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 2012728C15F for <tsvwg@core3.amsl.com>; Thu, 24 Mar 2011 17:56:14 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O+n9WUPr97ul for <tsvwg@core3.amsl.com>; Thu, 24 Mar 2011 17:56:12 -0700 (PDT)
Received: from smtpauth22.prod.mesa1.secureserver.net (smtpauth22.prod.mesa1.secureserver.net [64.202.165.44]) by core3.amsl.com (Postfix) with SMTP id A586E28C159 for <tsvwg@ietf.org>; Thu, 24 Mar 2011 17:56:12 -0700 (PDT)
Received: (qmail 29013 invoked from network); 25 Mar 2011 00:57:46 -0000
Received: from unknown (108.20.211.213) by smtpauth22.prod.mesa1.secureserver.net (64.202.165.44) with ESMTP; 25 Mar 2011 00:57:46 -0000
From: "Walter Weiss" <wweiss@peerpark.com>
To: "'Randy Stewart'" <randall@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com>	<201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com>	<00b301cbe3b4$828a20e0$4001a8c0@gateway.2wire.net>	<29AEBA37-6157-44E9-8FD7-B44023DF6CD7@lakerest.net>	<024801cbe593$4f2d1960$4001a8c0@gateway.2wire.net>	<646C4AFE-1AAE-419B-BB6D-8670D292F563@lurchi.franken.de>	<01ae01cbe66f$c4d2d1a0$4001a8c0@gateway.2wire.net> <95CA9565-AD4E-487F-9109-1A62F5863A69@lakerest.net> <000901cbe9ea$bef64220$3ce2c660$@com> <79F23C16-2D3D-405D-B410-5F8F952A2697@lakerest.net> <000c01cbea47$aacb2a10$00617e30$@com> <07F575F4-8816-498E-9640-88EEACB48AB0@lakerest.net>
In-Reply-To: <07F575F4-8816-498E-9640-88EEACB48AB0@lakerest.net>
Subject: RE: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Date: Thu, 24 Mar 2011 20:57:48 -0400
Message-ID: <001601cbea87$aa2ecef0$fe8c6cd0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvqdnRkgpkSB5hUTjKcVukRt0cjVgADpPEg
Content-Language: en-us
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: Fri, 25 Mar 2011 00:56:14 -0000

In-line..


>>> Walter:
>>>
>>> A few comments in-line..
>>>
>>> On Mar 24, 2011, at 2:14 AM, Walter Weiss wrote:
>>>
>>>> Randy,
>>>>
>>>>> And
>>>>> having things in-band creates all sorts of additional traffic (if I
>want
>> to reset
>>>>> more than one stream)...
>>>>
>>>> Sorry for the delayed feedback. I for one would agree with Brian's
>>>> assessment. Personally I would favor an "in-band" reset (that
>leverages
>> the
>>>> existing SACK mechanism) over timers and added complexity in the
>> protocol. I
>>>> don't see a significant distinction between a single chunk with many
>> stream
>>>> resets and many chunks each with an In-Band Reset other than that
>you can
>>>> support more resets in a single packet. The "Out-Of-Band" approach
>allows
>>>> roughly 7x more resets in a single packet. However, I question the
>need
>> or
>>>> desirability of en mass RESETs. Further, the overhead of "In-Band"
>>>> acknowledgements is 0.
>>>>
>>>> While "In-Band" reset is more attractive to me, it has three
>drawbacks
>> that
>>>> I am aware of:
>>>> 1. Either the non-zero length data chunk requirement must be relaxed
>or a
>>>> new EXTENDED-OPTIONS-DATA chunk that co-exists with DATA chunks must
>be
>>>> defined. The second approach would imply a hybrid chunk which
>includes
>> all
>>>> DATA fields and optional parameters.
>>>> 2. For either of these approaches, the extension to the protocol
>must be
>>>> negotiated during Association INITialization.
>>>> 3. There are some unattractive interactions between "In-Band" reset
>and
>>>> PR-SCTP. Most notably a Forward Cumulative TSN chunk cannot be
>advanced
>>>> beyond the oldest un-SACKed reset.
>>>>
>>>> However, the benefits to this approach are that:
>>>> 1. It is simple.
>>>
>>> Its simple only if you count not having to add a new Data chunk type.
>Or if
>>> you don't implement a new data chunk type then you need two types of
>>> handling of
>>> data chunks and negotiation when you are going to use them. That is
>not
>>> simple... I think its easier to add the reconfig chunk. Especially
>when
>>> you
>>> need this anyway to do the add no matter if you do in-band reset or
>out-
>>> of-band
>>> reset. The procedures to handle a "reconfiguration" must be put in
>place
>>> i.e.
>>> the add-stream + ack of such.
>>>
>>> So instead of just adding one mechanism, you add two..
>>>
>>>> 2. There is no reason (from protocol perspective) for a reset stream
>>> to
>>>> block either the stream or the association, even when the reset has
>>> not been
>>>> acknowledged.
>>>
>>> I think you are incorrect here..
>>>
>>> Consider
>>>
>>> ----SSN1--->
>>> ----SSN2--->
>>> ----SSN3+Reset??--->XLost
>>> <X>----SSN0--->
>>> ----SSN1--->
>>> ----SSN2--->
>>>
>>> Note now there are some difficulties here.
>>>
>>> a) First of all many implementations make sure a SSN is within the
>valid
>>>  range i.e. at point X, normally you consider SSN3-32k(approx its
>>> actually 2^^16-1) valid and anything
>>>  below 3 or above 32k invalid. Sending an abort to the peer is the
>>> usual method
>>>  with a protocol violation (this is actually something we tested at
>>> one of the interops).
>>>  This protection (because it does protect you agains malicious peers)
>>> now must be thrown away.
>>>  This is an extreme disadvantage.
>>>
>>> b) You end up holding SSN0/1 and 2 (which the current draft suggests
>>> holding on the sending
>>>  side instead of the receiving side). I don't see a lot of difference
>>> in that.. one
>>>  side will have to hold them... no matter what if there is a loss....
>>> if there is no
>>>  loss you delay sending but that does not stop other streams from
>>> sending... only
>>>  the streams being reset. Which from an application perspective I
>>> doubt is an issue
>>>  since you are in the process of recycling the stream for a different
>>> purpose anyway
>>>  (or an indication that I am done with the current purpose for stream
>>> X.. which would
>>>   imply no more data for a moment until the stream is reassigned for
>>> other work)...
>>
>> Both these points would be true if you restart the SSN to 0. However,
>if you
>> continued incrementing the SSN (SSNs should be transparent to the
>> application), there is no blocking (just a protocol detected gap).
>
>The whole idea of stream-reset is the SSN to go back to 0..

But the SSN is and should be transparent to the application layer. I can't
think of any reason why the first message after a reset should have a SSN of
0, when the goal of a reset is to propagate the reset from one application
to the other.

>>
>>>> I don't see an issue with unordered DATA on a reset stream provided
>>> that an
>>>> "In-Band" reset is only considered acknowledged when the CUM_TSN_ACK
>>> is
>>>> advanced and implementations don't propagate unordered data from
>Gap-
>>> Acked
>>>> chunks.
>>>
>>> And here would be another problem. Why would you not want unordered
>data
>>> delivered right away? Right now implementations DO propagate
>unordered
>>> data
>>> on gap-acked chunks... its why SCTP can free up rwnd space for the
>>> sender
>>> by delivering such as soon as it arrives...
>>>
>>> That to me would be an extreme disadvantage.
>>
>> Personally, I would prefer receiver side blocking of an unordered DATA
>chunk
>> (when there is a gap) to sender side blocking (until reset negotiation
>has
>> completed).
>
>
>I don't think Unordered should ever be blocked.. rec or send side..

Good point. So if it is critical that Unordered DATA should not be blocked
on the receiver side (when there it is a gap chunk), a better solution would
be to have the sender delay transmission of Unordered DATA until after the
SACK for the "In-Band" reset has been processed by the reset sender. This
would preserve all existing behavior and avoid Send side blocking for all
cases except for Unordered DATA.

Regards,

-Walter


From randall@lakerest.net  Sat Mar 26 10:06:38 2011
Return-Path: <randall@lakerest.net>
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 6FD253A6955 for <tsvwg@core3.amsl.com>; Sat, 26 Mar 2011 10:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.421
X-Spam-Level: 
X-Spam-Status: No, score=-2.421 tagged_above=-999 required=5 tests=[AWL=0.178,  BAYES_00=-2.599]
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 VLMWmgrrL4Fz for <tsvwg@core3.amsl.com>; Sat, 26 Mar 2011 10:06:17 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id CF7CB3A67D1 for <tsvwg@ietf.org>; Sat, 26 Mar 2011 10:06:15 -0700 (PDT)
Received: from dhcp-1318.meeting.ietf.org ([130.129.19.24]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2QH7jAK036477 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 26 Mar 2011 13:07:49 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: SCTP zero-window probing and path selection
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <201103181031.03591.michael.larsen@tieto.com>
Date: Sat, 26 Mar 2011 13:06:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D91BB66-9D89-49B6-9EFB-835045D1A701@lakerest.net>
References: <201103181031.03591.michael.larsen@tieto.com>
To: Michael Larsen <michael.larsen@tieto.com>
X-Mailer: Apple Mail (2.1084)
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: Sat, 26 Mar 2011 17:06:38 -0000

Michael:

I thought I had responded to this already... I know I typed
an email in response.. but somehow it never got sent ... sorry about
that :-)

Some comments for you below.


On Mar 18, 2011, at 5:31 AM, Michael Larsen wrote:

> Hello list,
>=20
> Looking into SCTP zero window probing on a multi-homed association and =
path=20
> failures, it looks to me like RFC4960 has room for an improvement.
>=20
> Imagine the following setup with two host and a multi-homed =
association:
>=20
> Local                    Peer
>=20
> IP1 -------------------- IPa
>=20
> IP2 -------------------- IPb
>=20
> Imagine that we ('Local') is sending data on IP1-IPa while peer is =
sending=20
> data on IP2-IPb.  Subsequently, imagine that peer announces a_rwnd=3D0 =
and we=20
> begin zero-window probing (on IP1-IPa).  In the mean-time peer =
continues to=20
> send data on IP2-IPb and we dutifully return SACK of that data on =
IP2-IPb.
>=20
> Now IP1-IPa breaks and our window-probes no longer reaches peer. =
Reading 4960=20
> literally we will not detect this and may never detect when peer rwnd =
opens.
>=20
> The reason for this is the following statement from 4960 (Section 6.1, =
item=20
> A):
>=20
>     "If the sender continues to receive new packets from the receiver
>      while doing zero window probing, the unacknowledged window probes
>      should not increment the error counter for the association or any
>      destination transport address."
>=20
> I.e. we are receiving "new packets" (albeit DATA chunks on IP2-IPb) so =
we do=20
> not increment the error counter and does not change destination of the =
window=20
> probes.
>=20
> 4960 is not clear on whether IP1-IPa is "idle" in this situation such =
that the=20
> destination is probed through heartbeats (we have sent data so =
strictly=20
> speaking HBs should not be sent). IF we read 4960 such that HBs should =
be sent=20
> then they will eventually clear up the reachability problem but this =
is a=20
> side-effect and given that heartbeat intervals can be tuned and =
heartbeat=20
> disabled this reaction may come too late or not at all.
>=20
> The solution seems to me that instead of "new packets" 4960 should =
have said=20
> "SACK chunks" because the SACK chunk is the proper 'alive indication' =
returned=20
> in response to our window probe.  DATA chunks are not, because they =
belong to=20
> the independent data-flow going in the other direction.

When writing a protocol specification many things are left to =
implementations. Notice
that none of the text you quote has MUST or even SHOULD in the wording.

So yes, you could do as you suggest and consider only SACK's (as an =
implementation
decision) to not advance the error counter on the net... but there are a =
few
other things you should consider on this:

1) Since the peer is sending on path-2 data, often times it will send a =
window
   update sack... if it fits I would expect it to come bundled on the =
path-2 with
   the data.

2) When the retransmission timer on the window-probe expires and no sack =
has
   been seen since the original transmission, I would expect the =
implementation
   to be moving the data to the alternate path. After all in most cases =
when
   the T3-Timer fires this is what an implementation does... unless of =
course
   they are zero-window probing and they HAVE seen a SACK since the last =
send (if
   they track such).

Throughout the RFC you will find things "left to the implementation". =
This allows
some freedom in how things are implemented.. which is important.

I don't see this as a defect in the spec since as an implementor you can =
interpret
it the way you say... only sacks... or you can do it with the second =
method.. i.e.
move the data to the alternate path. In fact a third way would be to =
always move
the data to the alternate path.. no matter if its a window probe or not. =
That way
one does not have to keep track of a "did a sack happen since my last =
send of the
probe" field...

Again I think the key here is to let implementers have room to innovate =
and yet
still stay compatible and within the bounds of all of the cc issues and =
of course giving
a complete service to the user...

Best wishes

R




>=20
> Regards,
> Michael
>=20

-----
Randall Stewart
randall@lakerest.net





From randall@lakerest.net  Sat Mar 26 10:06:38 2011
Return-Path: <randall@lakerest.net>
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 827F63A67D1 for <tsvwg@core3.amsl.com>; Sat, 26 Mar 2011 10:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.48
X-Spam-Level: 
X-Spam-Status: No, score=-2.48 tagged_above=-999 required=5 tests=[AWL=0.119,  BAYES_00=-2.599]
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 QZTGQaiAD9Ig for <tsvwg@core3.amsl.com>; Sat, 26 Mar 2011 10:06:17 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id D9A6F3A693B for <tsvwg@ietf.org>; Sat, 26 Mar 2011 10:06:15 -0700 (PDT)
Received: from dhcp-1318.meeting.ietf.org ([130.129.19.24]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2QH7jAL036477 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 26 Mar 2011 13:07:50 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: SCTP zero-window probing and path selection
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <201103181031.03591.michael.larsen@tieto.com>
Date: Sat, 26 Mar 2011 13:07:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <071CCEA7-0E76-40DD-BF9A-C42BB06B76D1@lakerest.net>
References: <201103181031.03591.michael.larsen@tieto.com>
To: Michael Larsen <michael.larsen@tieto.com>
X-Mailer: Apple Mail (2.1084)
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: Sat, 26 Mar 2011 17:06:38 -0000

Michael:

I thought I had responded to this already... I know I typed
an email in response.. but somehow it never got sent ... sorry about
that :-)

Some comments for you below.


On Mar 18, 2011, at 5:31 AM, Michael Larsen wrote:

> Hello list,
>=20
> Looking into SCTP zero window probing on a multi-homed association and =
path=20
> failures, it looks to me like RFC4960 has room for an improvement.
>=20
> Imagine the following setup with two host and a multi-homed =
association:
>=20
> Local                    Peer
>=20
> IP1 -------------------- IPa
>=20
> IP2 -------------------- IPb
>=20
> Imagine that we ('Local') is sending data on IP1-IPa while peer is =
sending=20
> data on IP2-IPb.  Subsequently, imagine that peer announces a_rwnd=3D0 =
and we=20
> begin zero-window probing (on IP1-IPa).  In the mean-time peer =
continues to=20
> send data on IP2-IPb and we dutifully return SACK of that data on =
IP2-IPb.
>=20
> Now IP1-IPa breaks and our window-probes no longer reaches peer. =
Reading 4960=20
> literally we will not detect this and may never detect when peer rwnd =
opens.
>=20
> The reason for this is the following statement from 4960 (Section 6.1, =
item=20
> A):
>=20
>    "If the sender continues to receive new packets from the receiver
>     while doing zero window probing, the unacknowledged window probes
>     should not increment the error counter for the association or any
>     destination transport address."
>=20
> I.e. we are receiving "new packets" (albeit DATA chunks on IP2-IPb) so =
we do=20
> not increment the error counter and does not change destination of the =
window=20
> probes.
>=20
> 4960 is not clear on whether IP1-IPa is "idle" in this situation such =
that the=20
> destination is probed through heartbeats (we have sent data so =
strictly=20
> speaking HBs should not be sent). IF we read 4960 such that HBs should =
be sent=20
> then they will eventually clear up the reachability problem but this =
is a=20
> side-effect and given that heartbeat intervals can be tuned and =
heartbeat=20
> disabled this reaction may come too late or not at all.
>=20
> The solution seems to me that instead of "new packets" 4960 should =
have said=20
> "SACK chunks" because the SACK chunk is the proper 'alive indication' =
returned=20
> in response to our window probe.  DATA chunks are not, because they =
belong to=20
> the independent data-flow going in the other direction.

When writing a protocol specification many things are left to =
implementations. Notice
that none of the text you quote has MUST or even SHOULD in the wording.

So yes, you could do as you suggest and consider only SACK's (as an =
implementation
decision) to not advance the error counter on the net... but there are a =
few
other things you should consider on this:

1) Since the peer is sending on path-2 data, often times it will send a =
window
  update sack... if it fits I would expect it to come bundled on the =
path-2 with
  the data.

2) When the retransmission timer on the window-probe expires and no sack =
has
  been seen since the original transmission, I would expect the =
implementation
  to be moving the data to the alternate path. After all in most cases =
when
  the T3-Timer fires this is what an implementation does... unless of =
course
  they are zero-window probing and they HAVE seen a SACK since the last =
send (if
  they track such).

Throughout the RFC you will find things "left to the implementation". =
This allows
some freedom in how things are implemented.. which is important.

I don't see this as a defect in the spec since as an implementor you can =
interpret
it the way you say... only sacks... or you can do it with the second =
method.. i.e.
move the data to the alternate path. In fact a third way would be to =
always move
the data to the alternate path.. no matter if its a window probe or not. =
That way
one does not have to keep track of a "did a sack happen since my last =
send of the
probe" field...

Again I think the key here is to let implementers have room to innovate =
and yet
still stay compatible and within the bounds of all of the cc issues and =
of course giving
a complete service to the user...

Best wishes

R




>=20
> Regards,
> Michael
>=20

-----
Randall Stewart
randall@lakerest.net





From jmpolk@cisco.com  Sun Mar 27 04:06:39 2011
Return-Path: <jmpolk@cisco.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 C811C3A67A6 for <tsvwg@core3.amsl.com>; Sun, 27 Mar 2011 04:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 bsT4H8wATaCp for <tsvwg@core3.amsl.com>; Sun, 27 Mar 2011 04:06:38 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id DF2FE3A67A5 for <tsvwg@ietf.org>; Sun, 27 Mar 2011 04:06:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=1141; q=dns/txt; s=iport; t=1301224095; x=1302433695; h=message-id:date:to:from:subject:mime-version; bh=xBo/uK82g3nxMJ9gdWgOQ5B+eAq6zNyHcKS+v7b2UTo=; b=RV9grEhdb5kT8Au/8DbVn/erWhseOQNwIDzAD1mlFxxwWn1gU4BmEqwp vVlQZ4H1+oUDaIjj0gxsv3BigUtMs5nEdxD5mlgKNoi/niuP1NZilgkoM bMtbQ8eQUugJGd+sdzbF4/aUo0M6wmJPpUexWjdkg1c6T5wgVXqY2vkBo Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEFALYZj02rRDoH/2dsb2JhbABJpRd3pWWafIVpBIU6
X-IronPort-AV: E=Sophos;i="4.63,250,1299456000"; d="scan'208";a="325304895"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-2.cisco.com with ESMTP; 27 Mar 2011 11:07:59 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-vpn-client-10-89-7-9.cisco.com [10.89.7.9]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2RB7vZL014387 for <tsvwg@ietf.org>; Sun, 27 Mar 2011 11:07:58 GMT
Message-Id: <201103271107.p2RB7vZL014387@mtv-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 27 Mar 2011 06:07:57 -0500
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Final Agenda just changed in TSVWG
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Sun, 27 Mar 2011 11:06:39 -0000

TSVWG

Sorry for the late notice, but the chairs have bashed themselves and 
added a few items to the agenda. Please see the link below for the 
final agenda for TSVWG.

	http://www.ietf.org/proceedings/80/agenda/tsvwg.txt

We have added two discussions:

First

IANA Procedures for the Management of the Transport
Protocol Port Number and Service Name Registry
    draft-ietf-tsvwg-iana-ports (15 min)

because of the discussion within the IESG caused some changes to the 
text that were not passed by the WG, and our AD David thought it best 
to have the WG review these changes before issuing another short WGLC 
(if all goes well).

Second, we added the discussion on SCTP Failover and SCTP Multipath 
IDs because of very active recent list discussion and the possibility 
that the two collide or are a superset/subset pairing. The timing of 
this list discussion talked the chairs into bringing this to the WGs 
attention to make sure either or both items are desired and going in 
the right direction.

Otherwise, or in parallel to this - let further agenda bashing begin...

James & Gorry
TSVWG chairs


From bob.briscoe@bt.com  Mon Mar 28 01:55:14 2011
Return-Path: <bob.briscoe@bt.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 1DFD33A68EE for <tsvwg@core3.amsl.com>; Mon, 28 Mar 2011 01:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.435
X-Spam-Level: 
X-Spam-Status: No, score=-3.435 tagged_above=-999 required=5 tests=[AWL=0.164,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 iS4Jy7BBgs52 for <tsvwg@core3.amsl.com>; Mon, 28 Mar 2011 01:55:12 -0700 (PDT)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151]) by core3.amsl.com (Postfix) with ESMTP id C59633A68B1 for <tsvwg@ietf.org>; Mon, 28 Mar 2011 01:55:11 -0700 (PDT)
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 09:56:48 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by i2kc06-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 28 Mar 2011 09:56:47 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt05.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1301302606932; Mon, 28 Mar 2011 09:56:46 +0100
Received: from MUT.jungle.bt.co.uk ([10.142.66.49]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id p2S8uifk028758; Mon, 28 Mar 2011 09:56:45 +0100
Message-Id: <201103280856.p2S8uifk028758@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 28 Mar 2011 09:31:26 +0100
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
From: Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: Comments on draft-briscoe-tsvwg-ecn-encap-guidelines-00
In-Reply-To: <4D903B5A.9070905@erg.abdn.ac.uk>
References: <4D8F7A0B.5060808@erg.abdn.ac.uk> <201103280102.p2S11wvh025605@bagheera.jungle.bt.co.uk> <4D903B5A.9070905@erg.abdn.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 28 Mar 2011 08:56:47.0821 (UTC) FILETIME=[1216B7D0:01CBED26]
Cc: tsvwg IETF list <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, 28 Mar 2011 08:55:14 -0000

Gorry,

Yes, we're either agreeing, or deferring to later for details.

Thanks again.

cc'd to list as agreed.

Bob

At 08:40 28/03/2011, Gorry Fairhurst wrote:
>We seem to agree mostly. See brief notes below:
>
>On 28/03/2011 03:01, Bob Briscoe wrote:
>>Gorry,
>>
>>Thank you for your v useful (as always) and comprehensive (as always)
>>review and chair comments.
>>
>>Inline responses...
>>
>>
>>At 18:55 27/03/2011, Gorry Fairhurst wrote:
>>
>>>draft-briscoe-tsvwg-ecn-encap-guidelines-00
>>>
>>>Thanks for uploading the draft on Congestion Notification for link
>>>layers. I have some comments and suggestions below.
>>>
>>>Best wishes,
>>>
>>>Gorry
>>>
>>>I have reviewed the above draft as a member of TSVWG (Chair hat
>>>comments at the end).
>>>
>>>- I'm interested in this topic and would be happy to read and
>>>contribute to the evolution of this draft.
>>>
>>>" Even a whole
>>>meshed subnetwork can be made immune to interior congestion by
>>>careful network design; interior links can be sufficiently
>>>provisioned relative to the edge capacities to absorb even worst-case
>>>patterns of load."
>>>- This seems to imply internal congestion can always be avoided. Is
>>>this always the case? I'm not sure I believe this. In contrast, I'd
>>>suggest the "worst-case" is that the interface/subnetwork drops
>>>packets under load.
>>
>>I only said 'a network can be'. I was thinking of a 3-stage clos network
>>as discussed in S.8 of the (long but highly interesting) paper below
>>[Reid05]. It becomes prohibitive to scale this to keep it guaranteed
>>non-blocking, but such a multipath topology does strongly reduce the
>>chances of congestion on interior links.
>>
>>Reid, A., "Economics and Scalability of QoS Solutions," BT Technology
>>Journal 23(2):97--117 (April 2005) ((access requires registration but no
>>fee)) Abstract URL:
>>http://www.btplc.com/Innovation/Journal/BTTJ/archive/Abstract.aspx?JType=
=3DBTTJ&IDVol=3D23&IDArt=3D2&IDAbs=3D19
>I just didn't want to give the impression that=20
>L2 offered a generic solution in all cases.
>
>>
>>>- RFC3819 S 13 says something about L2 buffers and congestion, and may
>>>also be useful reference point on some terminology.
>>
>>Thank you - I had completely forgotten about that.
>>
>>
>>>"Also it might be costly to find an IP
>>>header (v4 or v6) when it may be encapsulated by more than one
>>>Ethernet header (e.g. when using multiple encapsulations of MAC in
>>>MAC [IEEE802.1Qah])."
>>>- IP encapsulation in its various forms also makes this deep pack
>>>inspection more complex. The IP router at the L2 edge of subnet needs
>>>to do this anyway?
>>
>>Well no, the whole point is that if the marking is being done in a L3
>>queue, the IP header is the one being acted on - it's already been
>>decapsulated and doesn't have to be looked for - it *is* the outer. But
>>if marking is being done by a switch that is acting on a L2 header,
>>there's no saying how deep it will have to bury to find the first IP
>>header to mark.
>This was probably just language clarity - we agree.
>
>>>"the end-station"
>>>- I wonder if we can find a better term? Can you describe this as the
>>>L2 destination, link egress or the L2 network edge or something like
>>>this? Later sections speak of "subnets" - how does this relate to
>>>these terms?
>>
>>OK. I mentioned all this, when I defined the terms encapsulator &
>>decapsulator, but then I've been inconsistent in the text itself. Thanks.
>>
>>>"reaches the destination transport"
>>>- I think this would be a good place to mention "endpoint" or "host"
>>>or something.
>>>
>>>"the source transport"
>>>- Would transport layer at the sending endpoint be better, since
>>>destination transport is a term that can have multiple meanings to L2
>>>people.
>>
>>Good point. I'll work on these.
>>
>>
>>>Page 4:
>>>
>>>- I think the word "transport" would benefit from being very clearly
>>>explained including a diagram to show what the IETF means by
>>>transport. I suspect many in the intended group of "users" for the
>>>document will think of transport as being below IP, in contrast to
>>>where the IETF places this term.
>>
>>Yes - I argue with them that they should disambiguate, so I should.
>>
>>[However, I must add that when I challenge them to refer to any document
>>at all for a definition for their use of the word transport, they have
>>absolutely nothing formal to cite. It's just a general word for stuff
>>that carries things, much like we talk of cars and buses as transport.
> >
>Agree.
>>
>>>- Inner header and outer header are also terms that may benefit from a
>>>little more detail for a layer 2 audience?
>>
>>I assume you are saying the terminology section entries are not even
>>enough.
>>
>>
>>>- Congestion baseline: I didn't understand this definition, and
>>>suspect this is important, can you explain?
>>
>>OK, yes, the definition is unclear. "Congestion notification baseline"
>>would be a more intuitive but longer phrase. The place where congestion
>>notification was last zeroed (typically at the ultimate source endpoint).
>The shorter form seems OK, but more info, e.g. a picture may help.
>
>>
>>>Page 5:
>>>"If the lower layer has its own
>>>feedback and load regulation, there is no need to propagate
>>>congestion signalling up the layers. "
>>>- Is this *always* true?
>>
>>There is no need to have a *deliberate* mechanism to propagate
>>signalling up the layers. But that doesn't mean it won't happen
>>naturally - when the lower layer cannot clear the load, the higher layer
>>queue at the subnet ingress will back-up and *it* might then signal
>>congestion (without any direct link to the lower layer congestion
>>notification signalling).
>>
>>I've seen this approach described in a patent filed by someone working
>>on QCN (IEEE 802.1Qau).
>>
>>
>>>S 3.1
>>>
>>>- The statement that lower layer protocols need to distinguish ECN
>>>support by PDU seems harsh? I'd have thought that many do not not, and
>>>the implication is that the egress of the L2 network then needs to
>>>take appropriate action.
>>
>>You're right - I had evolved my thinking since writing that, but
>>overlooked changing it. Will do next rev.
>>
>>
>>>- Is the sentence below correct?
>>>"For instance, ECN-
>>>capable transports might only be allowed to use PDUs identified by a
>>>particular set of labels or tags."
>>>- Or is it "For instance, Only ECN-capable transports may be allowed=85"
>>
>>you're right
>>
>>
>>>"This strategy might not be appropriate for
>>>other link technologies targeted at zero-configuration deployment by
>>>the general public (e.g. "
>>>- I wonder if the issue here is more about "zero-configuration
>>>deployment" and the "general public" is an example of typical usage,
>>>i.e. I'd have expected any zero-conf approach to have these properties.
>>
>>yes. The general public ought to be an example of users of zero-conf.
>>
>>
>>>S 3.2 bullet 1.
>>>
>>>- I think my comment may resemble ones for other sections, but I'd
>>>like to understand: This talks about copying ECN markings, but is it
>>>acceptable also to discard packets that are marked at this point?
>>
>>Ooh no. At ingress, an arriving marking will arrive in the IP header, so
>>one has to assume it was put there after safely checking the IP header
>>said the transport was ECN aware.
>>
>>At the ingress, the issue is about checking whether the ECN capability
>>of the lower layer (the one about to encapsulate) would be appropriately
>>handled when it is decapsulated. There's no need to resort to drop for
>>that - just turn off ECN capability in the outer.
>I see. We can thrash-out the guidance detail later.
>
>>
>>>S 3.2 bullet 2.
>>>- Is the assumption that the outer header does carry an ECN marking?
>>>Is it possible that the ECN properties of a flow could be in the
>>>control plane and therefore not part of the PDU, but would be visible
>>>at the egress. How would this best be handled?
>>
>>Yes, I need to treat in- and out-of-band congestion signalling as two
>>separate cases. So far I've only dealt with the former.
>>
>>You'll see I say in my slides I need help making this doc less
>>prescriptive about what the lower layer looks like (without making it so
>>abstract it becomes confusing).
>>
>>
>>>S 3.2 final para.
>>>- The actors and intention for this point were not clear to me.
>>
>>OK, I need to flesh this out - perhaps I'll use an example like an ATM
>>subnet.
>>
>>>/the whole path/ - is this end-to-end path or something else?
>>
>>e2e
>>
>>>/divided into segments/ - i.e. several segments combine to make the
>>>path or do you mean several L2 functions combine together (i
>>>parallel?) to provide the subnet service? /start of segment/, I
>>>presume this is ingress to the L2?
>>
>>"segments" aren't necessarily congruent with L2 subnets. They can be
>>aligned with the scope of tunnels (e.g. pseudowires). A sequence of PCN
>>domains would be another case. They are characterised by a load
>>regulator at the segment ingress and a feedback loop between segment
>>egress and ingress.
>>
>>
>>>S 3.3 bullet 1
>>>
>>>" * If the outer header carries an explicit congestion marking,
>>>the packet SHOULD be dropped--the only indication of
>>>congestion the transport will understand."
>>>- Why isn't this a MUST?
>>>- If the intention is to indicate something to the endpoint, then the
>>>packet needs to be dropped. Otherwise don't pass the marking upwards
>>>to IP. Am I missing something?
>>
>>Because I said I would say nothing as a MUST :)
>>
>>Even in RFC6040, this ended up being a SHOULD in one case (where the
>>marking wasn't the most severe).
> >
>Not sure, but can be thrashed-out later.
>
>>
>>>S 3.3 bullet 1
>>>- Is it possible to insist that the Highest marking MUST either set an
>>>IP marking or result in discard (using the above rule to decide
>>>which), lesser levels MAY have the same behaviour. That way we have
>>>more "sense" that the endpoint will react.
>>
>>Seriously, I don't like MUST in guidelines. But you're right, SHOULD
>>gives a liberal impression that is unwarranted. Your solution is one
>>approach - I'll think about it.
>I think it's more than "should".
>
>>
>>>S 3.3 bullet 4
>>>- I think this should also refer to the RFC that defines alternate ECN
>>>markings with DS.
>>
>>Yup.
>>
>>
>>>--- Chair comments ---
>>>
>>>I didn't do a complete review of this revision as a TSVWG Chair, and I
>>>am making no judgement at this time about whether this should be made
>>>a TSVWG work item. I suggest it would be first good to see more
>>>discussion on the contents voa the TSVWG list.
>>>
>>>I have the following comments that may be useful to consider for the
>>>next edit:
>>>
>>>- The draft proposes work on a topic that has been brought to the IETF
>>>before, although I am not aware of a published IETF document on this.
>>>However, this does not alone justify why the IETF should work on this
>>>topic: What are the risks and threats of NOT publishing this document?
>>
>>I've addressed this in my slides.
>>We need a place for temporal motivation text. It's not appropriate for
>>RFCs which are meant to be timeless, but we need to record somewhere why
>>we did something at a particular time.
>Exactly. it's best handled in email/meeting notes.
>
>>I have the same problem with trying to find a motivation for RSVP drafts.
>>
>>Perhaps there ought to be a requirement for a motivation statement on
>>the mailing list when a draft is first posted.
>That would suit me.
>
>>
>>>- This document does not appear to change an existing IETF
>>>specification, are there any current or proposed IETF documents that
>>>would be updated if this were to be published?
>>
>>Amazingly, I couldn't find one. Altho I'll have to look at 3819.
>>
>>
>>>- Section 1 says "The IETF would like to encourage this trend." - This
>>>is a consensus judgement that maybe needs to be confirmed by TSVWG.
>>
>>Of course. The idea of putting it in is to allow people to either agree
>>or not.
>OK
>>
>>>- The topic may benefit from coordination with other groups outside of
>>>he IETF.
>>
>>Yup - if it is adopted as WG item, it could benefit from a note at least
>>to IEEE, and possibly 3GPP (see slides about next steps - to include
>>propagating ECN through tunnelling protocol modules in the stack, even
>>tho they aren't ever the outer on the wire, e.g. GTP).
>>
>>Even if they aren't working on this, the statement to the IEEE might say
>>they ought to consider it, because switch vendors are putting out kit
>>that is getting used for this without a standard.
>OK
>
>>>--- END Chair comments ---
>>
>>Excellent - thank you - as always highly useful comments.
>>
>>
>>Bob
>>
>>
>>________________________________________________________________
>>Bob Briscoe, BT Innovate & Design
>
>

________________________________________________________________
Bob Briscoe,                                BT Innovate & Design=20


From ka-cheong.poon@oracle.com  Mon Mar 28 03:17:50 2011
Return-Path: <ka-cheong.poon@oracle.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 03A5E3A6A31 for <tsvwg@core3.amsl.com>; Mon, 28 Mar 2011 03:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.76
X-Spam-Level: 
X-Spam-Status: No, score=-5.76 tagged_above=-999 required=5 tests=[AWL=0.483,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 ThrXuyk8l05d for <tsvwg@core3.amsl.com>; Mon, 28 Mar 2011 03:17:49 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 017C63A6A1C for <tsvwg@ietf.org>; Mon, 28 Mar 2011 03:17:48 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2SAJOF8025810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Mon, 28 Mar 2011 10:19:26 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2SAJOU7004659 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Mon, 28 Mar 2011 10:19:24 GMT
Received: from abhmt016.oracle.com (abhmt016.oracle.com [141.146.116.25]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2SAJOX3009899 for <tsvwg@ietf.org>; Mon, 28 Mar 2011 05:19:24 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 28 Mar 2011 03:19:23 -0700
Message-ID: <4D9060A9.5080703@oracle.com>
Date: Mon, 28 Mar 2011 18:19:21 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <4D86D500.80807@oracle.com> <FF1809C0-5493-4D54-8FF0-56767F252117@lakerest.net>
In-Reply-To: <FF1809C0-5493-4D54-8FF0-56767F252117@lakerest.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt358.oracle.com [141.146.40.158]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090205.4D9060AC.00D2,ss=1,fgs=0
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, 28 Mar 2011 10:17:50 -0000

On 03/21/11 11:18 PM, Randy Stewart wrote:

> I see a large number of responses here... most
> from you, Michael and a few from Tom/Benoit and Brian.
>
> How I assess statements on the list (correct me if you
> feel I have interpreted your statements on the list wrong) are
> as follows:
>
> 1) You are definitely against anything but the add feature
>     and you are ok with the current out-of-band mechanisms.


I have strong reservation on the idea of TSN/SSN reset.
AFAICT, there is no clear and convincing usage example
of this mechanism.  At least, none is given in the current
draft, which I think is not a usual practice in proposing
a standard track protocol mechanism.  On this account,
my opinion is that more substantial argument of the
proposed mechanism should be put in the draft first, if
the authors still want to have this mechanism tied to
stream addition.

I am OK with the out of band mechanism on the stream
addition.  Since I don't see any convincing reason why
the TSN/SSN mechanism is needed, I've not spent time in
checking it out carefully.  So I won't say I'm OK or not
OK about this.


> 2) Tom wished we had reve'd the spec one more time with the
>     his previous comments, is not sure of the use case for any
>     of it but sees value in it possibly. Would like to see more
>     comments on Brian's thoughts...
>
> 3) Beniot needs the ADD stream for IPFIX and wants it out :-)


My suggestion is to have a draft on stream addition only.
There is a clear usage and is better be done at the protocol
layer.


> 4) Brian likes the idea of stream reconfiguration and thinks
>     we have not gone far enough (no delete stream) and would like
>     to see the mechanism changed to do all this to be "in-band".
>
> 5) Michael Peter and I (not surprisingly) are in favor of the document
>     as it is.... of course I am not sure how much authors count in all
>     of this ;-)
>
>
> So I think, in my assessment, you are the only one speaking against
> everything (except the ADD)...


I hope this is not a popularity contest and we should focus
on technical aspect.  If we do a simple mapping of this TSN/SSN
reset idea to TCP, I think many people will have strong reservation
on it.

My $0.02 is that this draft is not ready for LC with the current
content, hence my suggestion that this draft can be separated
into two.


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From Michael.Tuexen@lurchi.franken.de  Mon Mar 28 04:08:27 2011
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 34D293A6784 for <tsvwg@core3.amsl.com>; Mon, 28 Mar 2011 04:08:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.745
X-Spam-Level: 
X-Spam-Status: No, score=-1.745 tagged_above=-999 required=5 tests=[AWL=0.198,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 sOOIl1ly6VoC for <tsvwg@core3.amsl.com>; Mon, 28 Mar 2011 04:08:26 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id F262D3A6452 for <tsvwg@ietf.org>; Mon, 28 Mar 2011 04:08:25 -0700 (PDT)
Received: from [192.168.1.113] (p508FD736.dip.t-dialin.net [80.143.215.54]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 2EAEA1C0B461C; Mon, 28 Mar 2011 13:10:01 +0200 (CEST)
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4D9060A9.5080703@oracle.com>
Date: Mon, 28 Mar 2011 13:10:00 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <82BEF99E-28C0-4428-9964-650A3772CC64@lurchi.franken.de>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <4D86D500.80807@oracle.com> <FF1809C0-5493-4D54-8FF0-56767F252117@lakerest.net> <4D9060A9.5080703@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1084)
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, 28 Mar 2011 11:08:27 -0000

On Mar 28, 2011, at 12:19 PM, Kacheong Poon wrote:

> On 03/21/11 11:18 PM, Randy Stewart wrote:
> 
>> I see a large number of responses here... most
>> from you, Michael and a few from Tom/Benoit and Brian.
>> 
>> How I assess statements on the list (correct me if you
>> feel I have interpreted your statements on the list wrong) are
>> as follows:
>> 
>> 1) You are definitely against anything but the add feature
>>    and you are ok with the current out-of-band mechanisms.
> 
> 
> I have strong reservation on the idea of TSN/SSN reset.
> AFAICT, there is no clear and convincing usage example
> of this mechanism.  At least, none is given in the current
> draft, which I think is not a usual practice in proposing
> a standard track protocol mechanism.  On this account,
> my opinion is that more substantial argument of the
> proposed mechanism should be put in the draft first, if
> the authors still want to have this mechanism tied to
> stream addition.
> 
> I am OK with the out of band mechanism on the stream
> addition.  Since I don't see any convincing reason why
> the TSN/SSN mechanism is needed, I've not spent time in
> checking it out carefully.  So I won't say I'm OK or not
> OK about this.
Hi Kacheong,

you to be sure what you are talking about:
* Are you talking about the TSN/SSN Reset (I think so)
* Are you talking about the SSN Reset (I'm not sure, since
  I provided use-cases for it, but we did not agree on
  it)

Best regards
Michael

> 
> 
>> 2) Tom wished we had reve'd the spec one more time with the
>>    his previous comments, is not sure of the use case for any
>>    of it but sees value in it possibly. Would like to see more
>>    comments on Brian's thoughts...
>> 
>> 3) Beniot needs the ADD stream for IPFIX and wants it out :-)
> 
> 
> My suggestion is to have a draft on stream addition only.
> There is a clear usage and is better be done at the protocol
> layer.
> 
> 
>> 4) Brian likes the idea of stream reconfiguration and thinks
>>    we have not gone far enough (no delete stream) and would like
>>    to see the mechanism changed to do all this to be "in-band".
>> 
>> 5) Michael Peter and I (not surprisingly) are in favor of the document
>>    as it is.... of course I am not sure how much authors count in all
>>    of this ;-)
>> 
>> 
>> So I think, in my assessment, you are the only one speaking against
>> everything (except the ADD)...
> 
> 
> I hope this is not a popularity contest and we should focus
> on technical aspect.  If we do a simple mapping of this TSN/SSN
> reset idea to TCP, I think many people will have strong reservation
> on it.
> 
> My $0.02 is that this draft is not ready for LC with the current
> content, hence my suggestion that this draft can be separated
> into two.
> 
> 
> -- 
> 
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
> 


From ietfc@btconnect.com  Mon Mar 28 04:26:58 2011
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 DE87C3A67A5 for <tsvwg@core3.amsl.com>; Mon, 28 Mar 2011 04:26:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.843
X-Spam-Level: 
X-Spam-Status: No, score=-1.843 tagged_above=-999 required=5 tests=[AWL=0.400,  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 2M7hLYHvc1RI for <tsvwg@core3.amsl.com>; Mon, 28 Mar 2011 04:26:58 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr09.btconnect.com [213.123.20.127]) by core3.amsl.com (Postfix) with ESMTP id 9CFB43A63D2 for <tsvwg@ietf.org>; Mon, 28 Mar 2011 04:26:57 -0700 (PDT)
Received: from host217-44-145-1.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.1]) by c2bthomr09.btconnect.com with SMTP id CIB98365; Mon, 28 Mar 2011 12:28:31 +0100 (BST)
Message-ID: <022701cbed32$d21db0e0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Kacheong Poon" <ka-cheong.poon@oracle.com>, <tsvwg@ietf.org>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com><4D86D500.80807@oracle.com><FF1809C0-5493-4D54-8FF0-56767F252117@lakerest.net> <4D9060A9.5080703@oracle.com>
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Date: Mon, 28 Mar 2011 12:27:56 +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-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A0B0303.4D9070DE.00F3, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020C.4D9070DF.009B,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
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, 28 Mar 2011 11:26:59 -0000

---- Original Message ----- 
From: "Kacheong Poon" <ka-cheong.poon@oracle.com>
To: <tsvwg@ietf.org>
Sent: Monday, March 28, 2011 12:19 PM
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started


> On 03/21/11 11:18 PM, Randy Stewart wrote:
> 
> > I see a large number of responses here... most
> > from you, Michael and a few from Tom/Benoit and Brian.
> >
> > How I assess statements on the list (correct me if you
> > feel I have interpreted your statements on the list wrong) are
> > as follows:
> >
> > 1) You are definitely against anything but the add feature
> >     and you are ok with the current out-of-band mechanisms.
> 
> 
> I have strong reservation on the idea of TSN/SSN reset.
> AFAICT, there is no clear and convincing usage example
> of this mechanism.  At least, none is given in the current
> draft, which I think is not a usual practice in proposing
> a standard track protocol mechanism.  On this account,

I am not so sure about this one.  There can be an applicability
statement, which says why, in the same or a different RFC,
but they are by no means universal.

And while an RFC never changes, a standard can drop 
things as it progresses, if it turns out that they are not
or can not be implemented, so the change from Proposed to
Draft Standard can lose the features that did not catch on,
even if there were running code at the time of the I-D.

As I have said before, this is a network protocol,
networks get knotted (and I would be surprised if
SCTP were an exception to this) so reset is a less
disruptive way of getting unknotted than tearing
everything down and restarting.  That is the
theoretical justification, don't know how well it
stands up in practice.

Tom Petch

> my opinion is that more substantial argument of the
> proposed mechanism should be put in the draft first, if
> the authors still want to have this mechanism tied to
> stream addition.
> 
> I am OK with the out of band mechanism on the stream
> addition.  Since I don't see any convincing reason why
> the TSN/SSN mechanism is needed, I've not spent time in
> checking it out carefully.  So I won't say I'm OK or not
> OK about this.
> 
> > 2) Tom wished we had reve'd the spec one more time with the
> >     his previous comments, is not sure of the use case for any
> >     of it but sees value in it possibly. Would like to see more
> >     comments on Brian's thoughts...
> >
> > 3) Beniot needs the ADD stream for IPFIX and wants it out :-)
> 
> My suggestion is to have a draft on stream addition only.
> There is a clear usage and is better be done at the protocol
> layer.
> 
> > 4) Brian likes the idea of stream reconfiguration and thinks
> >     we have not gone far enough (no delete stream) and would like
> >     to see the mechanism changed to do all this to be "in-band".
> >
> > 5) Michael Peter and I (not surprisingly) are in favor of the document
> >     as it is.... of course I am not sure how much authors count in all
> >     of this ;-)
> >
> > So I think, in my assessment, you are the only one speaking against
> > everything (except the ADD)...
> 
> I hope this is not a popularity contest and we should focus
> on technical aspect.  If we do a simple mapping of this TSN/SSN
> reset idea to TCP, I think many people will have strong reservation
> on it.
> 
> My $0.02 is that this draft is not ready for LC with the current
> content, hence my suggestion that this draft can be separated
> into two.
> -- 
> 
> K. Poon.
> ka-cheong.poon@oracle.com

From alexey.melnikov@isode.com  Mon Mar 28 05:12:53 2011
Return-Path: <alexey.melnikov@isode.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 2C0A73A67DF; Mon, 28 Mar 2011 05:12:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.465
X-Spam-Level: 
X-Spam-Status: No, score=-102.465 tagged_above=-999 required=5 tests=[AWL=0.134, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8jWslAYJm0r1; Mon, 28 Mar 2011 05:12:52 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 080503A6845; Mon, 28 Mar 2011 05:12:52 -0700 (PDT)
Received: from [130.129.20.248] (dhcp-14f8.meeting.ietf.org [130.129.20.248])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TZB7pAADL1cM@rufus.isode.com>; Mon, 28 Mar 2011 13:14:28 +0100
Message-ID: <4D907B90.2090709@isode.com>
Date: Mon, 28 Mar 2011 14:14:08 +0200
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt>  (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <4D413827.7040407@ericsson.com> <B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com> <4D46B3B9.4050804@ericsson.com> <755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com> <4D4920F0.1070204@ericsson.com> <49CDF352-D900-4883-8D67-19172DBC8474@cisco.com> <4D5B4B98.4060704@vpnc.org> <6AA482E6-924C-4981-9E7F-69AD8EE3DD6F@cisco.com> <4D5B4D86.3020102@stpeter.im> <4D5BB0E8.5000503@isode.com>
In-Reply-To: <4D5BB0E8.5000503@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: iesg@ietf.org, 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, 28 Mar 2011 12:12:53 -0000

Alexey Melnikov wrote:

> Peter Saint-Andre wrote:
>
>> Agreed, thanks to Paul for the proposed text.
>>
>> On 2/15/11 9:02 PM, Cullen Jennings wrote:
>>
>>> Paul's text is much better than mine. That was what I trying to get
>>> at.
>>
> Agreed, I will add this as an RFC Editor's note.
>
>>> On Feb 15, 2011, at 8:59 PM, Paul Hoffman wrote:
>>>
>>>> On 2/15/11 7:34 PM, Cullen Jennings wrote:
>>>>
>>>>> I propose some text for the draft near the bottom of this
>>>>> email.... For the user ports the document should have some text
>>>>> along the lines of:
>>>>>
>>>>> There is not IETF consensus on when it is appropriate to use a
>>>>> second port for a secure version of protocol therefor the export
>>>>> reviewer should not reject a request for a second port to run a
>>>>> secure variant of the protocol over.
>>>>
>>>> That feels close, but too prescriptive. Also, the requests are
>>>> usually for a protocol with two ports, not a later request for a
>>>> second port. How about:
>>>>
>>>> There is not IETF consensus on when it is appropriate to use a
>>>> second port for a secure version of protocol. Therefore, an expert
>>>> reviewer should not reject a proposal for a protocol that uses a
>>>> second part to run a secure variant for the sole reason that it
>>>> is using two ports.
>>>
After discussing this new text with IESG and some participants of the 
TSVWG, it became clear that while there is clear agreement for adding 
the first sentence quoted above ("There is no IETF consensus..."), there 
is no clear cut consensus for adding the second sentence ("Therefore, an 
expert reviewer should not reject a proposal").

After even further discussions with proponents of this text, with 
editors, IANA, etc., the proposal is to strike the second sentence, i.e. 
only the following sentence is going to be added to the document:

  There is no IETF consensus on when it is appropriate to use a second 
port for an insecure version of protocol.

The IESG is already alerted when there are problems with IANA 
registrations, so the requirement being removed is not needed.

If people have problems with this change, please send your objections by 
4pm Prague time on Wednesday, March 30th, as I would like to approve the 
document before my IESG term ends.


From lars.eggert@nokia.com  Mon Mar 28 05:44:52 2011
Return-Path: <lars.eggert@nokia.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 A918E3A6A55; Mon, 28 Mar 2011 05:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.764
X-Spam-Level: 
X-Spam-Status: No, score=-102.764 tagged_above=-999 required=5 tests=[AWL=-0.165, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 G+1pntr7KqQT; Mon, 28 Mar 2011 05:44:51 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by core3.amsl.com (Postfix) with ESMTP id AE99D3A69C0; Mon, 28 Mar 2011 05:44:51 -0700 (PDT)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da02.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p2SCkRAM017923 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Mar 2011 15:46:28 +0300
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.97 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <4D907B90.2090709@isode.com>
Date: Mon, 28 Mar 2011 14:46:18 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD6D9E22-16FC-455B-9A26-606610C470D3@nokia.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <4D413827.7040407@ericsson.com> <B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com> <4D46B3B9.4050804@ericsson.com> <755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com> <4D4920F0.1070204@ericsson.com> <49CDF352-D900-4883-8D67-19172DBC8474@cisco.com> <4D5B4B98.4060704@vpnc.org> <6AA482E6-924C-4981-9E7F-69AD8EE3DD6F@cisco.com> <4D5B4D86.3020102@stpeter.im> <4D5BB0E8.5000503@isode.com> <4D907B90.2090709@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Mon, 28 Mar 2011 15:46:24 +0300 (EEST)
X-Nokia-AV: Clean
Cc: tsvwg@ietf.org, IETF discussion list <ietf@ietf.org>, iesg@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, 28 Mar 2011 12:44:52 -0000

As one of the authors/editors, I am fine with this change. Thanks!

On 2011-3-28, at 14:14, Alexey Melnikov wrote:
> After discussing this new text with IESG and some participants of the =
TSVWG, it became clear that while there is clear agreement for adding =
the first sentence quoted above ("There is no IETF consensus..."), there =
is no clear cut consensus for adding the second sentence ("Therefore, an =
expert reviewer should not reject a proposal").
>=20
> After even further discussions with proponents of this text, with =
editors, IANA, etc., the proposal is to strike the second sentence, i.e. =
only the following sentence is going to be added to the document:
>=20
> There is no IETF consensus on when it is appropriate to use a second =
port for an insecure version of protocol.
>=20
> The IESG is already alerted when there are problems with IANA =
registrations, so the requirement being removed is not needed.
>=20
> If people have problems with this change, please send your objections =
by 4pm Prague time on Wednesday, March 30th, as I would like to approve =
the document before my IESG term ends.


From touch@isi.edu  Mon Mar 28 06:33:03 2011
Return-Path: <touch@isi.edu>
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 C3E823A6841; Mon, 28 Mar 2011 06:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.099
X-Spam-Level: 
X-Spam-Status: No, score=-104.099 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 jfNk8EnW04u5; Mon, 28 Mar 2011 06:33:03 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 748693A691E; Mon, 28 Mar 2011 06:33:02 -0700 (PDT)
Received: from [130.129.21.87] (dhcp-1557.meeting.ietf.org [130.129.21.87]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p2SDY0Bi020030 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 28 Mar 2011 06:34:15 -0700 (PDT)
Message-ID: <4D908E47.2070609@isi.edu>
Date: Mon, 28 Mar 2011 06:33:59 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet	Assigned Numbers Authority (IANA) Procedures for the Management	of the Service Name and Transport Protocol Port Number	Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<4D413827.7040407@ericsson.com>	<B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com>	<4D46B3B9.4050804@ericsson.com>	<755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com>	<4D4920F0.1070204@ericsson.com>	<49CDF352-D900-4883-8D67-19172DBC8474@cisco.com>	<4D5B4B98.4060704@vpnc.org>	<6AA482E6-924C-4981-9E7F-69AD8EE3DD6F@cisco.com>	<4D5B4D86.3020102@stpeter.im> <4D5BB0E8.5000503@isode.com>	<4D907B90.2090709@isode.com> <AD6D9E22-16FC-455B-9A26-606610C470D3@nokia.com>
In-Reply-To: <AD6D9E22-16FC-455B-9A26-606610C470D3@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: iesg@ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>, tsvwg@ietf.org, IETF discussion list <ietf@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, 28 Mar 2011 13:33:03 -0000

As one of the authors, I'm fine with this change too.

Joe

On 3/28/2011 5:46 AM, Lars Eggert wrote:
> As one of the authors/editors, I am fine with this change. Thanks!
>
> On 2011-3-28, at 14:14, Alexey Melnikov wrote:
>> After discussing this new text with IESG and some participants of the TSVWG, it became clear that while there is clear agreement for adding the first sentence quoted above ("There is no IETF consensus..."), there is no clear cut consensus for adding the second sentence ("Therefore, an expert reviewer should not reject a proposal").
>>
>> After even further discussions with proponents of this text, with editors, IANA, etc., the proposal is to strike the second sentence, i.e. only the following sentence is going to be added to the document:
>>
>> There is no IETF consensus on when it is appropriate to use a second port for an insecure version of protocol.
>>
>> The IESG is already alerted when there are problems with IANA registrations, so the requirement being removed is not needed.
>>
>> If people have problems with this change, please send your objections by 4pm Prague time on Wednesday, March 30th, as I would like to approve the document before my IESG term ends.
>

From magnus.westerlund@ericsson.com  Mon Mar 28 06:45:24 2011
Return-Path: <magnus.westerlund@ericsson.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 E40923A6A4B; Mon, 28 Mar 2011 06:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.527
X-Spam-Level: 
X-Spam-Status: No, score=-106.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 hCkIjoEA7hEv; Mon, 28 Mar 2011 06:45:24 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 661253A6A29; Mon, 28 Mar 2011 06:45:23 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bbbae000005311-5b-4d909153b331
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 95.2E.21265.351909D4; Mon, 28 Mar 2011 15:47:00 +0200 (CEST)
Received: from [153.88.19.49] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.137.0; Mon, 28 Mar 2011 15:46:59 +0200
Message-ID: <4D909153.6040401@ericsson.com>
Date: Mon, 28 Mar 2011 15:46:59 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet	Assigned Numbers Authority (IANA) Procedures for the Management	of the Service	Name and Transport Protocol Port Number	Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<4D413827.7040407@ericsson.com>	<B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com>	<4D46B3B9.4050804@ericsson.com>	<755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com>	<4D4920F0.1070204@ericsson.com>	<49CDF352-D900-4883-8D67-19172DBC8474@cisco.com>	<4D5B4B98.4060704@vpnc.org>	<6AA482E6-924C-4981-9E7F-69AD8EE3DD6F@cisco.com>	<4D5B4D86.3020102@stpeter.im>	<4D5BB0E8.5000503@isode.com>	<4D907B90.2090709@isode.com>	<AD6D9E22-16FC-455B-9A26-606610C470D3@nokia.com> <4D908E47.2070609@isi.edu>
In-Reply-To: <4D908E47.2070609@isi.edu>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, IETF discussion list <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "tsvwg@ietf.org" <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, 28 Mar 2011 13:45:25 -0000

Joe Touch skrev 2011-03-28 15:33:
> As one of the authors, I'm fine with this change too.

Me too,

Magnus Westerlund

From michelle.cotton@icann.org  Mon Mar 28 06:51:04 2011
Return-Path: <michelle.cotton@icann.org>
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 5F95B3A682B; Mon, 28 Mar 2011 06:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.271
X-Spam-Level: 
X-Spam-Status: No, score=-106.271 tagged_above=-999 required=5 tests=[AWL=0.328, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 Vf0qP9DPD13i; Mon, 28 Mar 2011 06:51:02 -0700 (PDT)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by core3.amsl.com (Postfix) with ESMTP id CAAFD3A67E3; Mon, 28 Mar 2011 06:51:02 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Mon, 28 Mar 2011 06:52:40 -0700
From: Michelle Cotton <michelle.cotton@icann.org>
To: Lars Eggert <lars.eggert@nokia.com>, Alexey Melnikov <alexey.melnikov@isode.com>
Date: Mon, 28 Mar 2011 06:52:34 -0700
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
Thread-Topic: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
Thread-Index: AcvtRjnfV4p5azEuRTOGZcZIRHF2bwACSnDy
Message-ID: <C9B5E0B2.2E4AD%michelle.cotton@icann.org>
In-Reply-To: <AD6D9E22-16FC-455B-9A26-606610C470D3@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.8.0.101117
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: The IESG <iesg@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, IETF discussion list <ietf@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, 28 Mar 2011 13:51:04 -0000

+1=20

Michelle


On 3/28/11 5:46 AM, "Lars Eggert" <lars.eggert@nokia.com> wrote:

> As one of the authors/editors, I am fine with this change. Thanks!
>=20
> On 2011-3-28, at 14:14, Alexey Melnikov wrote:
>> After discussing this new text with IESG and some participants of the TS=
VWG,
>> it became clear that while there is clear agreement for adding the first
>> sentence quoted above ("There is no IETF consensus..."), there is no cle=
ar
>> cut consensus for adding the second sentence ("Therefore, an expert revi=
ewer
>> should not reject a proposal").
>>=20
>> After even further discussions with proponents of this text, with editor=
s,
>> IANA, etc., the proposal is to strike the second sentence, i.e. only the
>> following sentence is going to be added to the document:
>>=20
>> There is no IETF consensus on when it is appropriate to use a second por=
t for
>> an insecure version of protocol.
>>=20
>> The IESG is already alerted when there are problems with IANA registrati=
ons,
>> so the requirement being removed is not needed.
>>=20
>> If people have problems with this change, please send your objections by=
 4pm
>> Prague time on Wednesday, March 30th, as I would like to approve the doc=
ument
>> before my IESG term ends.
>=20


From gorry@erg.abdn.ac.uk  Mon Mar 28 06:55:20 2011
Return-Path: <gorry@erg.abdn.ac.uk>
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 7D90D3A6994 for <tsvwg@core3.amsl.com>; Mon, 28 Mar 2011 06:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.472
X-Spam-Level: 
X-Spam-Status: No, score=-102.472 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 YBtpu17ymi6h for <tsvwg@core3.amsl.com>; Mon, 28 Mar 2011 06:55:19 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id 93E603A6856 for <tsvwg@ietf.org>; Mon, 28 Mar 2011 06:55:18 -0700 (PDT)
Received: from ra-gorry.erg.abdn.ac.uk ([IPv6:2001:df8:0:64:5ab0:35ff:fe7b:b828]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id p2SDumBF010817 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 28 Mar 2011 14:56:50 +0100 (BST)
Message-ID: <4D9093A0.9020605@erg.abdn.ac.uk>
Date: Mon, 28 Mar 2011 15:56:48 +0200
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: tsvwg list <tsvwg@ietf.org>
Subject: Additional comments on draft-ietf-tsvwg-byte-pkt-congest-04 (mostly editorial)
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
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, 28 Mar 2011 13:55:20 -0000

I enclose additional (mostly editorial) comments of the above draft.

S 1 para 1
/long term. But it also/long term. It also/

S 1 para 2
- thus concludes: /deployments we have already/
- this could be read as to refer to networks operated by the authors or 
IETF community, a better choice is /existing deployments/.

p6
/problems of one specific transport, as byte-mode variant of RED was 
designed to do/problems of one specific transport./
- This point us covered elsewhere.

p6
/The primary purpose of this memo is to build a definitive consensus
    against deliberate preferential treatment for small packets in AQM
    algorithms and to record this advice within the RFC series./
- This may have been true of the draft, would you consider rewording 
this, e.g.:
/This memo documents a consensus
    against deliberate preferential treatment for small packets in AQM
    algorithms./

S 1.1
- Please expand /RED/ when defining the term.

S 2.2
- This section concludes by a one para reference to the review. This 
seemed an unnecessary para. Please consider if you can simply point to 
this section rather than summarising the results and reiterating points 
noted elsewhere. e.g.

/   The byte mode packet drop variant of RED was recommended in the past
    (see Section 4.2.1 for how thinking evolved).  However, our survey of
    84 vendors across the industry (Section 4.2.5) has found that none of
    the 19% who responded have implemented byte mode drop in RED.  Given
    there appears to be little, if any, installed base it seems we can
    deprecate byte-mode drop in RED with little, if any, incremental
    deployment impact./
    A survey [XREF] showed that there appears to be little, if any,
    installed base of byte-mode drop using RED. This suggests that
    deprecate byte-mode drop will have little, if any, incremental
    deployment impact./

S 3.1
- This section discusses interpretation of loss. RFC 5348's 
interpretation seems different to that discussed here - where congestion 
is characterised by a Loss Event Rate (p). Is it worth saying a few 
words also about this?

S 3.1
This section introduces a new term that I don't feel happy about: 
"Congestion excursion"
- Is there an alternative term that could be used, I see section 1.1 
defines the term "Congestion Notification" to cover the concept of 
indicating congestion to a transport. I strongly suggest the document 
sticks to this term.

S 4
- The intro to this section appears to review/repeat other material. 
Could the set of paragraphs be removed? - If not please rework these 
more concisely and remove the reference to the "paper" - or state what 
this is intended to refer to.

S 4.1.1
- para 1, first sentence is long and hard to read. please rephrase, and 
please use alternate words instead of: /is fairly well understood these 
days/

S 4.1.2
- This makes a conclusion for all wireless spectrum, which is not true 
for all cases and is probably a function of the design of the physical 
layer and medium access method:

/ For instance,
    wireless spectrum is bit-congestible (for a given coding scheme), /
-is it possible to say, in /most cases/ or /is usely regarded as/

S 4.2.1
/But it went on to give advice we now disagree with./
- Who is the we… tsvwg?
- Is it possible to instead say the offered advice is updated by this memo.

S.4.2.1
/But it is not consistent with the
    present recommendations of Section 2./
- Is it possible to instead say this memo makes different 
recommendations in section 2.

S 4.2.1
   /No-one seems to have pointed out that this changed algorithm
    can often lead to drop probabilities of greater than 1 (which should
    ring alarm bells hinting that there's a mistake in the theory
    somewhere)./
- Is it please possible to rephrase this?


S 4.2.2
/   The above proposals to alter the network equipment to bias towards
    smaller packets have largely carried on outside the IETF process
    (unless one counts a reference in an informational RFC to an archived
    email!).  /
- I'd recommend that you delete the part in parenthesis - If not, you 
need to justify this and explain fully the context.

S 4.2.2
- final para of section needs to be rewritten. This refers to PCN as a 
proposal. This is now an IETF work item documents have been produced 
defining marking algorithms.

S 4.2.3
/Although no proposals exist as far as we know/
- Avoid "we", e.g. /Although there are no known proposals.../

S 4.2.3
/are there are bound to still exist/
- please rephrase.

S 5.1
/we believe the recommended position is now inarguably clear ---/
- This para needs to be rewritten. Once published this memo will specify 
this, it will not then be a matter of argument.

S 5.1
/  The sample of returns from our vendor survey Section 4.2.4 suggest
    that byte-mode packet drop seems not to be implemented at all let
    alone deployed, or if it is, it is likely to be very sparse.
    Therefore, we do not really need a migration strategy from all but
    nothing to nothing./
- This should be said simpler, or preferably removed. It's not essential 
to restate this here.

S6
/This draft/This memo/

S6
/  Of course, if
    transports really want to make the greatest gains, they don't have to
    respond to congestion anyway.  But we don't want applications that
    are trying to behave to discover that they can go faster by using
    smaller packets. /
- I think this could be misread, could we remove the first sentence or both?

S7
- I'm not sure the document needs a conclusion section. There is an 
abstract and a clear summary of recommendations. The conclusion does not 
appear to intend to further add to these. I'd rather keep all the 
recommendations in section 2.
- If a revised conclusion seems necessary, please omit /strongly/ from 
the wording.
( The current conclusion specifically delegates an issue to ICCRG on the 
final line. I don't think this is strictly necessary. A better phrase 
may be /ICCRG is currently chartered to work on these issues./)

Refs:
/RFC4348/ was obsoleted by /RFC5348/
- Is there a specific need to cite the obsolete spec.?


From stpeter@stpeter.im  Mon Mar 28 05:39:36 2011
Return-Path: <stpeter@stpeter.im>
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 EBEE93A6817; Mon, 28 Mar 2011 05:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.504
X-Spam-Level: 
X-Spam-Status: No, score=-102.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 vO0ggkTJkfvd; Mon, 28 Mar 2011 05:39:35 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 852FA3A67E4; Mon, 28 Mar 2011 05:39:35 -0700 (PDT)
Received: from dhcp-12cb.meeting.ietf.org (64-103-25-233.cisco.com [64.103.25.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 51AA74006D; Mon, 28 Mar 2011 06:42:47 -0600 (MDT)
Message-ID: <4D9081E5.4050107@stpeter.im>
Date: Mon, 28 Mar 2011 14:41:09 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the	Management of the Service Name and Transport Protocol Port	Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<4D413827.7040407@ericsson.com>	<B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com>	<4D46B3B9.4050804@ericsson.com>	<755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com>	<4D4920F0.1070204@ericsson.com>	<49CDF352-D900-4883-8D67-19172DBC8474@cisco.com>	<4D5B4B98.4060704@vpnc.org>	<6AA482E6-924C-4981-9E7F-69AD8EE3DD6F@cisco.com>	<4D5B4D86.3020102@stpeter.im> <4D5BB0E8.5000503@isode.com> <4D907B90.2090709@isode.com>
In-Reply-To: <4D907B90.2090709@isode.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms000704080901090105080801"
X-Mailman-Approved-At: Mon, 28 Mar 2011 08:30:07 -0700
Cc: tsvwg@ietf.org, IETF discussion list <ietf@ietf.org>, iesg@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, 28 Mar 2011 12:39:37 -0000

This is a cryptographically signed message in MIME format.

--------------ms000704080901090105080801
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 3/28/11 2:14 PM, Alexey Melnikov wrote:
> Alexey Melnikov wrote:
>=20
>> Peter Saint-Andre wrote:
>>
>>> Agreed, thanks to Paul for the proposed text.
>>>
>>> On 2/15/11 9:02 PM, Cullen Jennings wrote:
>>>
>>>> Paul's text is much better than mine. That was what I trying to get
>>>> at.
>>>
>> Agreed, I will add this as an RFC Editor's note.
>>
>>>> On Feb 15, 2011, at 8:59 PM, Paul Hoffman wrote:
>>>>
>>>>> On 2/15/11 7:34 PM, Cullen Jennings wrote:
>>>>>
>>>>>> I propose some text for the draft near the bottom of this
>>>>>> email.... For the user ports the document should have some text
>>>>>> along the lines of:
>>>>>>
>>>>>> There is not IETF consensus on when it is appropriate to use a
>>>>>> second port for a secure version of protocol therefor the export
>>>>>> reviewer should not reject a request for a second port to run a
>>>>>> secure variant of the protocol over.
>>>>>
>>>>> That feels close, but too prescriptive. Also, the requests are
>>>>> usually for a protocol with two ports, not a later request for a
>>>>> second port. How about:
>>>>>
>>>>> There is not IETF consensus on when it is appropriate to use a
>>>>> second port for a secure version of protocol. Therefore, an expert
>>>>> reviewer should not reject a proposal for a protocol that uses a
>>>>> second part to run a secure variant for the sole reason that it
>>>>> is using two ports.
>>>>
> After discussing this new text with IESG and some participants of the
> TSVWG, it became clear that while there is clear agreement for adding
> the first sentence quoted above ("There is no IETF consensus..."), ther=
e
> is no clear cut consensus for adding the second sentence ("Therefore, a=
n
> expert reviewer should not reject a proposal").
>=20
> After even further discussions with proponents of this text, with
> editors, IANA, etc., the proposal is to strike the second sentence, i.e=
=2E
> only the following sentence is going to be added to the document:
>=20
>  There is no IETF consensus on when it is appropriate to use a second
> port for an insecure version of protocol.
>=20
> The IESG is already alerted when there are problems with IANA
> registrations, so the requirement being removed is not needed.
>=20
> If people have problems with this change, please send your objections b=
y
> 4pm Prague time on Wednesday, March 30th, as I would like to approve th=
e
> document before my IESG term ends.

As someone who was involved in formulating the two-sentence text and who
raised concerns about removing the second sentence within the IESG, I'd
like to publicly affirm that I find this resolution acceptable.

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms000704080901090105080801
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDMy
ODEyNDEwOVowIwYJKoZIhvcNAQkEMRYEFJw65MYHMYQDZaU2jtYOUJMqYzzXMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQBQJ2XukNwvt0HcRZKLdruUnLrtwMW2wpvcnG+Krn5avQVZetfXW/xDGvp6
IWblHewDZAw9gjekwbYGxh7LI36aX+euGl84jg8pU3XRkd3dbuD/pmb2El6Fs5RP9tx6XkBG
nuSM3k6MTE6QJKr+pOTwcb3Ge/Pl4uX8ypH+ahRDCACvtOVfETiqBICtUq1ny1Tvkf9/GsiO
2bpxU4Et7De6ta/xDuQiwuoYGkTEHMrMjrNXqO933i3AM/kTbRsrX94tlbh1Q8de/ErpPSXR
Qi8wGFGxVA0KuzJGoJt1VhFYzGjda2krT36e1ybvAGFFkcLGQrmWkDAN0uYeA4bwDIb1AAAA
AAAA
--------------ms000704080901090105080801--

From gorry@erg.abdn.ac.uk  Mon Mar 28 08:33:08 2011
Return-Path: <gorry@erg.abdn.ac.uk>
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 BEF3C3A6A21 for <tsvwg@core3.amsl.com>; Mon, 28 Mar 2011 08:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 445pZUHLs3vx for <tsvwg@core3.amsl.com>; Mon, 28 Mar 2011 08:33:07 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id 4D7F23A6828 for <tsvwg@ietf.org>; Mon, 28 Mar 2011 08:33:06 -0700 (PDT)
Received: from dhcp-1773.meeting.ietf.org ([IPv6:2001:df8:0:16:5ab0:35ff:fe7b:b828]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id p2SFYcOK013181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <tsvwg@ietf.org>; Mon, 28 Mar 2011 16:34:38 +0100 (BST)
Message-ID: <4D90AA8E.8040400@erg.abdn.ac.uk>
Date: Mon, 28 Mar 2011 17:34:38 +0200
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: tsvwg list <tsvwg@ietf.org>
Subject: Comments on draft-ietf-tsvwg-byte-pkt-congest-04
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
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, 28 Mar 2011 15:33:08 -0000

draft-ietf-tsvwg-byte-pkt-congest-04

I enclose a review of the above draft.

This draft appears to tackle an important issue and makes clear
recommendations. I like the way these have been focussed into one
specific section. I think though there is work to be done to finalise
the text.

The document is proposed as Informational. The document's
recommendations impact other IETF working groups, notably TCPM. The
recommendations also expand on the usage of a number of other IETF
specification. A decision needs to be taken as to whether these
constitute actual document Updates to RFCs.

Best wishes,

Gorry

---

S 2.1

S 2.2 point 2
/it is strongly RECOMMENDED that it SHOULD be/
- I am not sure what strongly RECOMMENDED means in combination with
SHOULD. Would /SHOULD/ be sufficient?

S 2.3 point 2
/, this should be
        done by modifying TCP (Section 4.2.3), not network equipment./
- Is this a requirement, should it be /SHOULD/?

S 2.4 para 2
- This section seems to omit any RFC2119 requirement, please consider
what is required.

S 3.1
- This appears to conclude with a statement recommending the direction
of work within the TCPM working group. I don't personally see an issue
with this if TSVWG agrees, but is this conclusion also OK for the TCPM WG?

S 4.2.5
- I am little concerned that the IETF document will two specific
vendor's response to personal equerries without a reference. In this
case, I'm not sure that para 1 adds important facts and suggest this is
removed.

S 4.2.5
/Turning to our more formal survey/
- Was this survey performed by TSVWG or by the authors?
- I think the survey adds value, but I would much prefer to see this as
an appendix.

S 4.2.5
Para starting /Finally,/
- This para appears to be restatement. I would much prefer this to be
deleted and see all RFC 2119 recommendations in section 2.

S 5.2
- I would like to discuss the need for this section, and whether this
could be omitted.

Conclusion
- The current conclusion specifically delegates an issue to ICCRG on the
final line. I don't think this is strictly necessary. A better phrase
may be /ICCRG is currently chartered to work on these issues./

S Appendix A
- I would like to discuss the need for this section, and whether this
could be omitted.

Appendix B
- This describes MTU as a parameter. I do not understand this: It seems
that what actually matters is the packet size being used, not the
pre-configured maximum for a particular interface.

Editorial comments sent separately.



From jmpolk@cisco.com  Tue Mar 29 02:21:57 2011
Return-Path: <jmpolk@cisco.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 A106B3A6906 for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 02:21:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 Rb577rnvyqxQ for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 02:21:56 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 464F73A684E for <tsvwg@ietf.org>; Tue, 29 Mar 2011 02:21:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=327; q=dns/txt; s=iport; t=1301390614; x=1302600214; h=message-id:date:to:from:subject:mime-version; bh=W+uPPbCALps+q3GYkU9a94FXpGqCHdbxqxkaHWQRreY=; b=J9ay4za1J3Rax3ckflMAtnlsaiiidLXnAGReMEjLogNT4sM8wzS10GPp YbkRE87wxBcXEqs35yOTJ4ioagfz1jj0MEfVhYqYmAwwPbeg3lx6168pa /Cx0NDwaAaMMm4oM3o85tQ6D29Yf/8S7XD38Ey+zF5AVgK0XWDVL/iuZS w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAB+kkU2rRDoG/2dsb2JhbAClRXenWZxFhWoEhTw
X-IronPort-AV: E=Sophos;i="4.63,260,1299456000"; d="scan'208";a="326509421"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-2.cisco.com with ESMTP; 29 Mar 2011 09:23:34 +0000
Received: from jmpolk-wxp01.cisco.com ([10.89.8.40]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p2T9NVPr024129 for <tsvwg@ietf.org>; Tue, 29 Mar 2011 09:23:32 GMT
Message-Id: <201103290923.p2T9NVPr024129@mtv-core-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 29 Mar 2011 04:23:29 -0500
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: TSVWG Presenter slides required Wed noon CET
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Tue, 29 Mar 2011 09:21:57 -0000

Prague Presenters

I need you to send me your TSVWG slides (unicast or to both of us) by 
Wed noon CET (i.e., Prague time). I have to upload them to the IETF 
server, and won't be happy if I have to scramble because someone 
didn't do what I have reasonably asked for.

(harsh I know)

James & Gorry
(chair hats on)


From lear@cisco.com  Tue Mar 29 02:34:15 2011
Return-Path: <lear@cisco.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 64B7F3A690E; Tue, 29 Mar 2011 02:34:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.582
X-Spam-Level: 
X-Spam-Status: No, score=-110.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 JgzwPCZeT6XU; Tue, 29 Mar 2011 02:34:14 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 7967E3A67B7; Tue, 29 Mar 2011 02:34:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=1330; q=dns/txt; s=iport; t=1301391352; x=1302600952; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=GTJXELIinxNTtcvakAJhB30u4Iv5rLk5h7u9Gid2sHs=; b=ffYzhrL+05Qb2EZJyUKZtwflGYSy7BIUfmS8fnFuLmRo3MIKvwpZvr3E MMfmZnAaaUr+q9zdwCsiEGL5slAm9O8NsJrDjeTzKiMnE9MrR5WJJtFI6 NPZEfZ3uiUOUKIpyFh6fWhHPJ/pWK150mrrbYCwn5ouqC1ODGaalW51kM o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtkEAGinkU2Q/khNgWdsb2JhbACESaB8FAEBFiYlp12LPZEFgSeEQwSNAg
X-IronPort-AV: E=Sophos;i="4.63,260,1299456000"; d="scan'208";a="81250518"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 29 Mar 2011 09:31:42 +0000
Received: from dhcp-10-61-106-212.cisco.com (dhcp-10-61-106-212.cisco.com [10.61.106.212]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2T9Vfmx027073; Tue, 29 Mar 2011 09:31:41 GMT
Message-ID: <4D91A6D6.7010302@cisco.com>
Date: Tue, 29 Mar 2011 11:31:02 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Michelle Cotton <michelle.cotton@icann.org>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet	Assigned Numbers Authority (IANA) Procedures for the Management of the	Service Name and Transport Protocol Port Number Registry) to BCP
References: <C9B5E0B2.2E4AD%michelle.cotton@icann.org>
In-Reply-To: <C9B5E0B2.2E4AD%michelle.cotton@icann.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, IETF discussion list <ietf@ietf.org>, The IESG <iesg@ietf.org>, "tsvwg@ietf.org" <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: Tue, 29 Mar 2011 09:34:15 -0000

+1.

On 3/28/11 3:52 PM, Michelle Cotton wrote:
> +1 
>
> Michelle
>
>
> On 3/28/11 5:46 AM, "Lars Eggert" <lars.eggert@nokia.com> wrote:
>
>> As one of the authors/editors, I am fine with this change. Thanks!
>>
>> On 2011-3-28, at 14:14, Alexey Melnikov wrote:
>>> After discussing this new text with IESG and some participants of the TSVWG,
>>> it became clear that while there is clear agreement for adding the first
>>> sentence quoted above ("There is no IETF consensus..."), there is no clear
>>> cut consensus for adding the second sentence ("Therefore, an expert reviewer
>>> should not reject a proposal").
>>>
>>> After even further discussions with proponents of this text, with editors,
>>> IANA, etc., the proposal is to strike the second sentence, i.e. only the
>>> following sentence is going to be added to the document:
>>>
>>> There is no IETF consensus on when it is appropriate to use a second port for
>>> an insecure version of protocol.
>>>
>>> The IESG is already alerted when there are problems with IANA registrations,
>>> so the requirement being removed is not needed.
>>>
>>> If people have problems with this change, please send your objections by 4pm
>>> Prague time on Wednesday, March 30th, as I would like to approve the document
>>> before my IESG term ends.
>

From fernando.gont.netbook.win@gmail.com  Tue Mar 29 03:24:03 2011
Return-Path: <fernando.gont.netbook.win@gmail.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 718D13A693E for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 03:24:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.065
X-Spam-Level: 
X-Spam-Status: No, score=-3.065 tagged_above=-999 required=5 tests=[AWL=-0.535, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, RCVD_IN_DNSWL_LOW=-1]
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 3xX3AqbnCUYX for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 03:24:02 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 4BABB3A690E for <tsvwg@ietf.org>; Tue, 29 Mar 2011 03:24:02 -0700 (PDT)
Received: by bwz13 with SMTP id 13so66846bwz.31 for <tsvwg@ietf.org>; Tue, 29 Mar 2011 03:25:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=MTgRRqd2apMYw1gY8+lTIHjJO6vrVQojMqp+iNA5E6U=; b=p+/G/ISOy3n3JBhf2uI37fhBTLuxpF6nUu72+as8Z7AG/HvaNbilnFk0OA6y9D6XGO B/TLrEp54JkoKH23Qo4OLCkJCggA5/f8aIxUgnU+c81QpwWIYImj4WokUIGvD1i+KHe8 rzLTz8gcViDg0jjl/uCzUR2aCPmxkFnkqsE50=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=hp4yL8X7WFUrPFC+OTuHzJhfYmKa9xDMWGQSCs0dOoN+Ss6xjaks5SvwHN37nTjV4y 4PP5O7x8yMdzEVK9m0hzdOQCN8ySjRODfemqxBtvgupQPCotS8AEBN+AfSvXYr/kimO6 nk+vaqDOFzRQR4xyC7DcQyQKWOutB4jaRrQk8=
Received: by 10.204.84.137 with SMTP id j9mr4584764bkl.120.1301394339416; Tue, 29 Mar 2011 03:25:39 -0700 (PDT)
Received: from [130.129.16.243] (dhcp-10f3.meeting.ietf.org [130.129.16.243]) by mx.google.com with ESMTPS id x6sm3306102bkv.12.2011.03.29.03.25.33 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 29 Mar 2011 03:25:38 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D911D37.2050700@gont.com.ar>
Date: Mon, 28 Mar 2011 20:43:51 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [Editorial Errata Reported] RFC6056 (2750)
References: <20110313184954.35D74E070A@rfc-editor.org>
In-Reply-To: <20110313184954.35D74E070A@rfc-editor.org>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: gorry@erg.abdn.ac.uk, bzeeb+ieft@zabbadoz.net, tsvwg@ietf.org, michael.larsen@tieto.com, jmpolk@cisco.com
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: Tue, 29 Mar 2011 10:24:03 -0000

Folks,

This errata is correct. (FWIW, I screwed up during IESG review at the time).

Thanks!

Best regards,
Fernando




On 13/03/2011 03:49 p.m., RFC Errata System wrote:
> The following errata report has been submitted for RFC6056,
> "Recommendations for Transport-Protocol Port Randomization".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6056&eid=2750
> 
> --------------------------------------
> Type: Editorial
> Reported by: Bjoern A. Zeeb <bzeeb+ieft@zabbadoz.net>
> 
> Section: 3.3
> 
> Original Text
> -------------
> 3.3.1.  Algorithm 1: Simple Port Randomization Algorithm
> 
> -           if(check_suitable_port(port))
> 
> 3.3.2.  Algorithm 2: Another Simple Port Randomization Algorithm
> 
> -           if(check_suitable_port(port))
> 
> Corrected Text
> --------------
> 3.3.1.  Algorithm 1: Simple Port Randomization Algorithm
> 
> +           if(check_suitable_port(next_ephemeral))
> 
> 3.3.2.  Algorithm 2: Another Simple Port Randomization Algorithm
> 
> +           if(check_suitable_port(next_ephemeral))
> 
> Notes
> -----
> For neither Algorithm 1 or 2 the pseudo code defines "port" as a valid variable.
> The variable passed to check_suitable_port() should be "next_ephemeral" in these cases.
> It looks like a copy and paste error. The technical meaning is still clear.
> 
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC6056 (draft-ietf-tsvwg-port-randomization-09)
> --------------------------------------
> Title               : Recommendations for Transport-Protocol Port Randomization
> Publication Date    : January 2011
> Author(s)           : M. Larsen, F. Gont
> Category            : BEST CURRENT PRACTICE
> Source              : Transport Area Working Group
> Area                : Transport
> Stream              : IETF
> Verifying Party     : IESG
> 

-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From gasheare@cisco.com  Tue Mar 29 04:03:37 2011
Return-Path: <gasheare@cisco.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 DF7CD28C15B for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 04:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.243
X-Spam-Level: 
X-Spam-Status: No, score=-10.243 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 KLU3dzWC1Kfw for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 04:03:35 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 62F2628C153 for <tsvwg@ietf.org>; Tue, 29 Mar 2011 04:03:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=gasheare@cisco.com; l=22428; q=dns/txt; s=iport; t=1301396712; x=1302606312; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=QWDqXGsSV89w73WwZKe02S71okGhI/2mOAPNTbEDbfo=; b=U5nEVRfDTcV0ghnrDwbvmQ+2706l69RtU89YP9uCMWUzxkHkt9kHCVeE 5Uj0cSpYGdCOL0no0cgkQyTVKJosyLNAmWC4uXXMH42P57MSb3oQkEJlW T4qAPeDFob48U2+kMyfVx5oXFq3KxkFqeqJ1K9pO1Eacq8xXJZBW6qx39 M=;
X-IronPort-AV: E=Sophos;i="4.63,261,1299456000"; d="scan'208";a="23610827"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 29 Mar 2011 11:05:11 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2TB5Bq2016092; Tue, 29 Mar 2011 11:05:11 GMT
Received: from xmb-ams-202.cisco.com ([144.254.75.13]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 29 Mar 2011 13:05:11 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Review of draft-ietf-tsvwg-sctp-strrst-09.txt
Date: Tue, 29 Mar 2011 13:05:09 +0200
Message-ID: <53A68C67A0118048A3E3F2C0827667EF5EB59C@XMB-AMS-202.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Review of draft-ietf-tsvwg-sctp-strrst-09.txt
Thread-Index: Acvt//fsduOwfXoaRX+sQVoNKUsaRgAAEF1A
From: "Gavin Shearer (gasheare)" <gasheare@cisco.com>
To: <tsvwg@ietf.org>
X-OriginalArrivalTime: 29 Mar 2011 11:05:11.0910 (UTC) FILETIME=[2C7F2860:01CBEE01]
X-Mailman-Approved-At: Tue, 29 Mar 2011 04:09:34 -0700
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: Tue, 29 Mar 2011 11:06:20 -0000

Hi,

I have been reviewing the draft RFC:

   Stream Control Transmission Protocol (SCTP) Stream Reconfiguration
                  draft-ietf-tsvwg-sctp-strrst-09.txt

I think the RFC is useful, especially the option to add more outgoing
streams, which is used in "IPFIX Export per SCTP Stream"
(draft-ietf-ipfix-export-per-sctp-stream-08)i, so I believe the ID
should progress. However, I do have some review comments, though most
of them are document text suggestions, and I think with the few changes
I have suggested, that the information to implementors is quite clear.

One area I am questioning is why there needs to be a feature to reset
both SSN and TSN, but if that is needed by others, then I will accept it
as part of this draft.

Cheers, Gavin Shearer



The following are my comments and suggestions on:

My comments are marked below with #### GSS. I have included
some context of the document to aid locating where the comments relates.
I have some general comments first.

What is the purpose of the TSN/SSN reset? What do you gain from
allowing the TSNs to also be reset considering that they are not set to
a specific value in the first place, and when changed the way it
"SHOULD"
be changed does not allow much control of the values the TSNs are
changed
to? It also adds more complexity as you have to be concerned whether the

the TSN's of recent chunks before the change may be muddled with new
chunks after the change if the "SHOULD" suggestions on values are not
followed.=20

As the new STREAM_RESET chunk is for more than just resetting streams
(i.e.
adding extra outgoing streams), should it be named STREAM_RECONFIG
instead of STREAM_RESET?
Other similar changes in line with this are suggested below:
    Stream Reset Response Parameter ->
	Stream Reconfig Response Parameter
    Stream Reset Request Sequence Number ->
	Stream Reconfig Request Sequence Number
    Stream Reset Response Sequence Number ->
	Stream Reconfig Response Sequence Number
    Stream Reset Chunk[s] ->
	Stream Reconfig Chunk[s]
    Stream Reset Timer ->
	Stream Reconfig Timer
    reset request parameter ->
	reconfig request parameter

For consistency should decide on STREAM_RESET or STREAM RESET when
discussing
the chunk (it also uses Stream Reset ...).

For the Sockets API, what should happen if the timer is already running
when a request is received? Should the request be failed (and so a
failure
event needs specified) or should the request be queued?



3.1.  STREAM RESET Chunk
.
.
.
   Note that each STREAM RESET chunk holds at least one parameter and at
   most two parameters.  Only the following combinations are allowed:

   1.  Outgoing SSN Reset Request Parameter.

   2.  Incoming SSN Reset Request Parameter.

   3.  Outgoing SSN Reset Request Parameter, Incoming SSN Reset Request
       Parameter.

   4.  SSN/TSN Reset Request Parameter.

   5.  Add Outgoing Streams Request Parameter.

   6.  Stream Reset Response Parameter.

   7.  Stream Reset Response Parameter, Outgoing SSN Reset Request
       Parameter.

   8.  Stream Reset Response Parameter, Stream Reset Response Parameter.

#### GSS: Under what situation do you expect there to be 2 response
#### GSS: parameters?
.
.
.
4.1.  Outgoing SSN Reset Request Parameter

   This parameter is used by the sender to request the reset of some or
   all outgoing streams.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Parameter Type =3D 0x000d   | Parameter Length =3D 16 + 2 * N |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             Stream Reset Request Sequence Number              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             Stream Reset Response Sequence Number             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                Sender's Last Assigned TSN                     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Stream Number 1 (optional)   |    Stream Number 2 (optional) |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   /                            ......                             /
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Stream Number N-1 (optional) |    Stream Number N (optional) |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Parameter Type: 2 bytes (unsigned integer)
      This field holds the IANA defined parameter type for Stream Reset

#### GSS: Change "Stream Reset Request Parameter" to
#### GSS: "Outgoing SSN Reset Request Parameter"

      Request Parameter.  The suggested value of this field for IANA is
      0x000d.

   Parameter Length: 2 bytes (unsigned integer)
      This field holds the length in bytes of the parameter; the value
      MUST be 16 + 2 * N.

   Stream Reset Request Sequence Number: 4 bytes (unsigned integer)
      This field is used to identify the request.  It is a monotonically
      increasing number that is initialized to the same value as the
      Initial TSN number.  It is increased by 1 whenever sending a new
      Stream Reset Request parameter.

#### GSS: Change "Stream Reset Request parameter" to "request
parameter",
#### GSS: as also used when adding additional streams, and there is also
#### GSS: no specific parameter named "Stream Reset Request"

.
.
.


4.2.  Incoming SSN Reset Request Parameter

   This parameter is used by the sender to request that the peer resets
   some or all of its outgoing streams.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Parameter Type =3D 0x000e   |  Parameter Length =3D 8 + 2 * N |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Stream Reset Request Sequence Number               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Stream Number 1 (optional)   |    Stream Number 2 (optional) |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   /                            ......                             /
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Stream Number N-1 (optional) |    Stream Number N (optional) |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Parameter Type: 2 bytes (unsigned integer)
      This field holds the IANA defined parameter type for Stream Reset

#### GSS: Change "Stream Reset Request Parameter" to
#### GSS: "Incoming SSN Reset Request Parameter"

      Request Parameter.  The suggested value of this field for IANA is
      0x000e.

   Parameter Length: 2 bytes (unsigned integer)
      This field holds the length in bytes of the parameter; the value
      MUST be 8 + 2 * N.

   Stream Reset Request Sequence Number: 4 bytes (unsigned integer)
      This field is used to identify the request.  It is a monotonically
      increasing number that is initialized to the same value as the
      Initial TSN number.  It is increased by 1 whenever sending a new
      Stream Reset Request parameter.

#### GSS: Change "Stream Reset Request parameter" to "request
parameter",
#### GSS: as also used when adding additional streams, and there is also
#### GSS: no specific parameter named "Stream Reset Request"

   Stream Number 1..N: 2 bytes (unsigned integer)
      This optional field, if included, is used to indicate specific
      streams that are to be reset.  If no streams are listed, then all
      streams are to be reset.

   This parameter can appear in a STREAM RESET chunk.  This parameter
   MUST NOT appear in any other chunk type.

4.3.  SSN/TSN Reset Request Parameter

   This parameter is used by the sender to request a reset of the TSN
   and SSN numbering of all streams.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Parameter Type =3D 0x000f   |      Parameter Length =3D 8     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Stream Reset Request Sequence Number                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Parameter Type: 2 bytes (unsigned integer)
      This field holds the IANA defined parameter type for Stream Reset

#### GSS: Change "Stream Reset Request Parameter" to
#### GSS: "SSN/TSN Reset Request Parameter"

      Request Parameter.  The suggested value of this field for IANA is
      0x000f.

   Parameter Length: 2 bytes (unsigned integer)
      This field holds the length in bytes of the parameter; the value
      MUST be 8.

   Stream Reset Request Sequence Number: 4 bytes (unsigned integer)
      This field is used to identify the request.  It is a monotonically
      increasing number that is initialized to the same value as the
      Initial TSN number.  It is increased by 1 whenever sending a new
      Stream Reset Request parameter.

#### GSS: Change "Stream Reset Request parameter" to "request
parameter",
#### GSS: as also used when adding additional streams, and there is also
#### GSS: no specific parameter named "Stream Reset Request"

   This parameter can appear in a STREAM RESET chunk.  This parameter
   MUST NOT appear in any other chunk type.

4.4.  Stream Reset Response Parameter

   This parameter is used by the receiver of a stream reset request
   parameter to respond to the stream reset request.

#### GSS: As also used for adding additional streams change to:
#### GSS: "This parameter is used by the receiver of a request parameter
#### GSS: to respond to the request."
.
.
.
   Sender's next TSN: 4 bytes (unsigned integer)
      This field holds the TSN the sender of the Response will use to

#### GSS: lower case "R" in response


4.5.  Add Outgoing Streams Request Parameter

   This parameter is used by the sender to request that an additional
   number of outgoing streams (i.e. the receiver's incoming streams) be
   added to the association.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Parameter Type =3D 0x0011   |      Parameter Length =3D 12    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Stream Reset Request Sequence Number               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Number of new streams    |         Reserved              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Parameter Type: 2 bytes (unsigned integer)
      This field holds the IANA defined parameter type for the Add
      Streams Parameter.  The suggested value of this field for IANA is

#### GSS: Change "Add Streams Parameter" to
#### GSS: "Add Outgoing Streams Request Parameter"

      0x0011.

   Parameter Length: 2 bytes (unsigned integer)
      This field holds the length in bytes of the parameter; the value
      MUST be 12.

   Stream Reset Request Sequence Number: 4 bytes (unsigned integer)
      This field is used to identify the request.  It is a monotonically
      increasing number that is initialized to the same value as the
      Initial TSN number.  It is increased by 1 whenever sending a new
      Stream Reset Request parameter.

#### GSS: Change "Stream Reset Request parameter" to "request
parameter",
#### GSS: as also used when adding additional streams, and there is also
#### GSS: no specific parameter named "Stream Reset Request"
.
.
.

5.  Procedures

   This section defines the procedures used by both the sender and
   receiver of a stream reset.  We also give various example stream
   reset scenarios.

#### GSS: As it gives more than reset, maybe change to talk about
handling of
#### GSS: the chunks, e.g.:
#### GSS: This section defines the procedures used by both the sender
and
#### GSS: receiver of a STREAMS_RESET chunk.

#### GSS: I don't think this section gives example scenarios (they are
in
#### GSS: Appendix A), so remove the line: "We also give various example
#### GSS: stream reset scenarios".

   One important thing to remember about SCTP streams is that they are
   uni-directional and there is no coorespondance between outgoing and

#### GSS: Typo: coorespondance -> correspondance

   incoming streams.  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 stream
   reset 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 proceedure and once that

#### GSS: Typo: proceedure -> procedure

   request is acknowledged let the peer actually control the reset
   operation.

5.1.  Sender Side Procedures

   This section describes the procedures related to the sending of
   Stream Reset Chunks.  A Stream Reset Chunk is composed of one or two
   Type Length Value (TLV) parameters.

5.1.1.  Sender Side Procedures for the Stream Reset Chunk

   This SCTP extension uses the Supported Extensions Parameter defined
   in [RFC5061] for negotiating the support for it.

   An SCTP endpoint supporting this extension MUST include the chunk
   type of the STREAM_RESET chunk in the Supported Extensions Parameter
   in either the INIT or INIT-ACK.  Before sending a Stream Reset Chunk
   the sender MUST ensure that the peer advertised support for the
   stream reset extension.  If the chunk type of the STREAM_RESET chunk
   does not appear in the supported extensions list of chunks, then the
   sender MUST NOT send any stream reset request to the peer, and any
   request by the application for such service SHOULD be responded to
   with an appropriate error indicating the peer SCTP stack does not
   support the stream reset extension.

   After packaging the Stream Reset Chunk and sending it to the peer the
   sender MUST start a 'Stream Reset Timer' if the STREAM RESET chunk
   contains at least one request parameter.  If it contains no request
   parameter, the Stream Reset Timer MUST NOT be started.  This timer

#### GSS: Typo: parameter -> parameters

   MUST use the same value as SCTP's Data transmission timer (i.e. the
   RTO timer) and MUST use exponential backoff doubling the value at
   every expiration.  If the timer expires, besides doubling the value,
   the sender MUST retransmit the Stream Reset Chunk, increment the
   appropriate error counts (both for the association and the
   destination), and perform threshold management possibly destroying
   the association if SCTP retransmission thresholds are exceeded.

5.1.2.  Sender Side Procedures for the Outgoing SSN Reset Request
        Parameter

   When an SCTP sender wants to reset the SSNs of some or all outgoing
   streams it can send an Outgoing SSN Reset Request Parameter provided
   that the Stream Reset Timer is not running.  The following steps must
   be followed:

   A1:  The sender MUST stop assigning new SSNs to new user data
        provided by the upper layer for the affected streams and queue
        it.  This is because it is not known whether the receiver of the
        request will accept or deny it and moreover, a lost request
        might cause an out-of-sequence error in a stream that the
        receiver is not yet prepared to handle.

#### GSS: What happens to user data already assigned SSNs, or do we
assume
#### GSS: that they are only assigned just before sending? If we do not
#### GSS: assume this, should it say that the request can only be sent
#### GSS: out after all data with assigned SSNs have been sent?

#### GSS: Also should it emphasize that transmission of data must be
suspended
#### GSS: until a response is received for the request?

.
.
.

5.1.3.  Sender Side Procedures for the Incoming SSN Reset Request
        Parameter

.
.
.

   When sending a Incoming SSN Reset Request their is a potential that

#### GSS: Typos: a -> an, their -> there

   the peer has just reset or is in the process of resetting the same
   streams via an Outgoing SSN Reset Request.  This collision scenario
   is discussed in Section 5.2.3.

5.1.4.  Sender Side Procedures for the SSN/TSN Reset Request Parameter

   When an SCTP sender wants to reset the SSNs and TSNs it can send an
   SSN/TSN Reset Request Parameter provided that the Stream Reset Timer
   is not running.  The following steps must be followed:

   C1:  The sender MUST assign the next stream reset request sequence
        number and put it into the Stream Reset Request Sequence Number
        field of the SSN/TSN Reset Request Parameter.  After assigning
        it the next stream reset request sequence number MUST be
        incremented by 1.

   C2:  The sender MUST queue any user data suspending any new
        transmissions and TSN assignment until the reset procedure is

#### GSS: change "TSN" to "TSN and SSN"

        finished by the peer either acknowledging or denying the
        request.

#### GSS: What happens to data already assigned TSN and/or SSNs but have
#### GSS: but have not been sent, or do we assume that they are only
#### GSS: assigned just before sending? If we do not
#### GSS: assume this, should it say that the request can only be sent
#### GSS: out after all data with assigned TSNs and SSNs have been sent?

   C3:  The SSN/TSN Reset Request Parameter MUST be put into a STREAM
        RESET Chunk.  There MUST NOT be any other parameter in this
        chunk.

   C4:  The STREAM RESET Chunk MUST be sent following the rules given in
        Section 5.1.1.

   Only one SSN/TSN Reset Request SHOULD be sent within 30 seconds,
   which is considered a maximum segment lifetime, the IP MSL.

5.1.5.  Sender Side Procedures for the Stream Reset Response Parameter

   When an implementation receives a reset request parameter it must
   respond with a Stream Reset Response Parameter in the following
   manner:

   D1:  The Stream Reset Request Sequence number of the incoming request
        MUST be copied to the Stream Reset Response Sequence Number
        field of the Stream Reset Response Parameter.

   D2:  The result of the processing of the incoming request according
        to Table 3 MUST be placed in the Result field of the Stream
        Reset Response Parameter.

   D3:  If the incoming request is an SSN/TSN reset request, the
        Sender's next TSN field MUST be filled with the next TSN the
        sender of this Stream Reset Response Parameter will assign.  For

#### GSS: should D3 also mention the SHOULD in G2?

        other requests the Sender's next TSN field, which is optional,
        MUST NOT be used.

.
.
.

5.2.2.  Receiver Side Procedures for the Outgoing SSN Reset Request
        Parameter
.
.
.
   E6:  The STREAM RESET chunk MUST be sent after the incoming STREAM
        RESET chunk is processed completely.

#### GSS Should it say about sending "Denied" if not supporting the
change,
#### GSS similar to  5.2.3

5.2.3.  Receiver Side Procedures for the Incoming SSN Reset Request
        Parameter

   In the case that the endpoint is willing to perform a stream reset
   the following steps must be followed:

   F1:  An Outgoing SSN Reset Request Parameter MUST be put into an
        STREAM RESET chunk according to Section 5.1.2.

   F2:  The STREAM RESET chunk MUST be sent after the incoming STREAM
        RESET chunk is processed completely.

   If the endpoint is un-willing to perform the stream reset it MUST
   send a Stream Reset Response Parameter with the appropriate error set
   to "Denied".

   When a peer endpoint requests a Incoming SSN Reset Request it is

#### GSS: Typo: a -> an

   possible that the local endpoint has just sent an Outgoing SSN Reset
   Request on the same stream and has not yet received a response.  In

#### GSS: stream -> association?

   such a case the local endpoint MUST do the following:

   1) If the stream reset overlaps the outstanding request completely

#### GSS: make clearer which is which? e.g.
#### GSS: "If the just sent Outgoing SSN Reset Request Parameter
completely=20
#### GSS: overlaps the received Incoming SSN Reset Request Parameter
..."

      respond to the requestor with a acknowledgment indicating that

#### GSS: Typo: a -> an

      there was 'Nothing to do'.

   2) Otherwise process the stream reset request normally responding to
      the requestor with a acknowledgment.

#### GSS: Typo: a -> an
.
.
.

5.2.4.  Receiver Side Procedures for the SSN/TSN Reset Request Parameter

   In the case that the endpoint is willing to perform an SSN/TSN reset
   the following steps must be followed:

   G1:  Compute an appropriate value for the Receiver's next TSN, the
        TSN the peer should use to send the next DATA chunk.  The value
        SHOULD be the smallest TSN not acknowledged by the receiver of
        the request plus 2^31.

   G2:  Compute an appropriate value for the local endpoint's next TSN,
        i.e. the receiver of the SSN/TSN reset chunk next TSN to be
        assigned.  The value SHOULD be the highest TSN sent by the
        receiver of the request plus 1.

#### GSS: Is this recommended value not the value the other size would
#### GSS: normally expect at the TSN? If other values are allowed, are
#### GSS: there recommendations, e.g. add 2^31

From braun@net.in.tum.de  Tue Mar 29 08:51:03 2011
Return-Path: <braun@net.in.tum.de>
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 BCA903A6812 for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 08:51:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level: 
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 GVi8dM7q295r for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 08:51:02 -0700 (PDT)
Received: from mail-out1.informatik.tu-muenchen.de (mail-out1.informatik.tu-muenchen.de [131.159.0.8]) by core3.amsl.com (Postfix) with ESMTP id 0A47C3A67E4 for <tsvwg@ietf.org>; Tue, 29 Mar 2011 08:50:58 -0700 (PDT)
Received: from dhcp-9227.meeting.ietf.org (unknown [130.129.10.39]) by mail.net.in.tum.de (Postfix) with ESMTPSA id 8D80E204BE31 for <tsvwg@ietf.org>; Tue, 29 Mar 2011 17:52:35 +0200 (CEST)
From: Lothar Braun <braun@net.in.tum.de>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Date: Tue, 29 Mar 2011 17:52:06 +0200
Message-Id: <A4337C52-5E68-4846-877C-BD8F06BAAB54@net.in.tum.de>
To: tsvwg@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
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: Tue, 29 Mar 2011 15:51:03 -0000

Hi,

I used the last few hours to read through the discussion on sctp-strrst, =
and the posting from Randy Stewart (quoted at the end of the mail) seems =
to be a good summary of the discussion.

And I'm now wondering if there are any objections against the ADD stream =
feature in the draft. =46rom my point of view, as someone who is not a =
transport layer export, I don't see any objections against this part of =
the draft after reading it.
Does someone have arguments against the add stream feature?

Considering the past discussion, there seems to be some time necessary =
to reach consensus on the reset feature. Am I getting this right?
I'm now wondering if anyone can estimate how long it will take to =
address all the open issues and reach an consensus?=20

If we look at the IPFIX WG, we can see that =
draft-ietf-ipfix-export-per-sctp-stream-08 has been sitting on the RFC =
editor queue for over eight months =
(https://datatracker.ietf.org/wg/ipfix/). I think it shouldn't sit there =
much longer.=20

Can there be a discussion at the WG meeting on thursday, on how to get =
the add stream feature into PS status if people agree that =
draft-ietf-tsvwg-sctp-strrst needs a lot more time in order to be =
finished?

If thursdays' discussion concludes that there is a significant time =
necessary to complete the draft due to the reset feature, can =
sctp-strrst be split in two parts?

1.) sctp-add-stream -> get it ready as fast as possible
2.) sctp-reset-stream -> discuss open issues, take the time that is =
necessary to reach the necessary rough consensus.

Best regards,
  Lothar


> Kacheong:
>=20
> I see a large number of responses here... most
> from you, Michael and a few from Tom/Benoit and Brian.
>=20
> How I assess statements on the list (correct me if you
> feel I have interpreted your statements on the list wrong) are
> as follows:
>=20
> 1) You are definitely against anything but the add feature
>    and you are ok with the current out-of-band mechanisms.
>=20
> 2) Tom wished we had reve'd the spec one more time with the
>    his previous comments, is not sure of the use case for any
>    of it but sees value in it possibly. Would like to see more
>    comments on Brian's thoughts...
>=20
> 3) Beniot needs the ADD stream for IPFIX and wants it out :-)
>=20
> 4) Brian likes the idea of stream reconfiguration and thinks
>    we have not gone far enough (no delete stream) and would like
>    to see the mechanism changed to do all this to be "in-band".=20
>=20
> 5) Michael Peter and I (not surprisingly) are in favor of the document
>    as it is.... of course I am not sure how much authors count in all
>    of this ;-)
>=20
>=20
> So I think, in my assessment, you are the only one speaking against
> everything (except the ADD)...
>=20
> My 2Cents ;-)
>=20
> R
--
Lothar Braun
Chair for Network Architectures and Services (I8)
Department of Informatics
Technische Universit=E4t M=FCnchen
Boltzmannstr. 3, 85748 Garching bei M=FCnchen, Germany
Phone:  +49 89 289-18010       Fax: +49 89 289-18033
E-mail: braun@net.in.tum.de=20







From jukka.manner@tkk.fi  Tue Mar 29 12:51:57 2011
Return-Path: <jukka.manner@tkk.fi>
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 6064328B797 for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 12:51:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 MysdbyfsfWTI for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 12:51:55 -0700 (PDT)
Received: from smtp.netlab.hut.fi (luuri.netlab.hut.fi [130.233.154.177]) by core3.amsl.com (Postfix) with ESMTP id 777FB3A6AA1 for <tsvwg@ietf.org>; Tue, 29 Mar 2011 12:51:55 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.netlab.hut.fi (Postfix) with ESMTP id 28B481E125; Tue, 29 Mar 2011 22:53:33 +0300 (EEST)
X-Virus-Scanned: by amavisd-new at luuri.netlab.hut.fi
Received: from smtp.netlab.hut.fi ([127.0.0.1]) by localhost (luuri.netlab.hut.fi [127.0.0.1]) (amavisd-new, port 10024) with LMTP id phpL933KmrTP; Tue, 29 Mar 2011 22:53:29 +0300 (EEST)
Received: from [130.129.70.40] (dhcp-4628.meeting.ietf.org [130.129.70.40]) by smtp.netlab.hut.fi (Postfix) with ESMTPSA id F35F31E0BF; Tue, 29 Mar 2011 22:53:28 +0300 (EEST)
Message-ID: <4D9238B8.5080902@tkk.fi>
Date: Tue, 29 Mar 2011 22:53:28 +0300
From: Jukka Manner <jukka.manner@tkk.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9pre) Gecko/20100818 Lanikai/3.1.3pre
MIME-Version: 1.0
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Subject: Re: Additional comments on draft-ietf-tsvwg-byte-pkt-congest-04 (mostly editorial)
References: <9610_1301320628_ZZ0LIR00GLCTF719.00_6995_1301320626_4D9093B2_6995_440_1_4D9093A0.9020605@erg.abdn.ac.uk>
In-Reply-To: <9610_1301320628_ZZ0LIR00GLCTF719.00_6995_1301320626_4D9093B2_6995_440_1_4D9093A0.9020605@erg.abdn.ac.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: tsvwg list <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: Tue, 29 Mar 2011 19:51:57 -0000

Hi Gorry,

Thank you for a detailed review. I'll fix those together with Bob.

regards,
Jukka

On 03/28/2011 04:56 PM, Gorry Fairhurst wrote:
> I enclose additional (mostly editorial) comments of the above draft.
>
> S 1 para 1
> /long term. But it also/long term. It also/
>
> S 1 para 2
> - thus concludes: /deployments we have already/
> - this could be read as to refer to networks operated by the authors or
> IETF community, a better choice is /existing deployments/.
>
> p6
> /problems of one specific transport, as byte-mode variant of RED was
> designed to do/problems of one specific transport./
> - This point us covered elsewhere.
>
> p6
> /The primary purpose of this memo is to build a definitive consensus
> against deliberate preferential treatment for small packets in AQM
> algorithms and to record this advice within the RFC series./
> - This may have been true of the draft, would you consider rewording
> this, e.g.:
> /This memo documents a consensus
> against deliberate preferential treatment for small packets in AQM
> algorithms./
>
> S 1.1
> - Please expand /RED/ when defining the term.
>
> S 2.2
> - This section concludes by a one para reference to the review. This
> seemed an unnecessary para. Please consider if you can simply point to
> this section rather than summarising the results and reiterating points
> noted elsewhere. e.g.
>
> / The byte mode packet drop variant of RED was recommended in the past
> (see Section 4.2.1 for how thinking evolved). However, our survey of
> 84 vendors across the industry (Section 4.2.5) has found that none of
> the 19% who responded have implemented byte mode drop in RED. Given
> there appears to be little, if any, installed base it seems we can
> deprecate byte-mode drop in RED with little, if any, incremental
> deployment impact./
> A survey [XREF] showed that there appears to be little, if any,
> installed base of byte-mode drop using RED. This suggests that
> deprecate byte-mode drop will have little, if any, incremental
> deployment impact./
>
> S 3.1
> - This section discusses interpretation of loss. RFC 5348's
> interpretation seems different to that discussed here - where congestion
> is characterised by a Loss Event Rate (p). Is it worth saying a few
> words also about this?
>
> S 3.1
> This section introduces a new term that I don't feel happy about:
> "Congestion excursion"
> - Is there an alternative term that could be used, I see section 1.1
> defines the term "Congestion Notification" to cover the concept of
> indicating congestion to a transport. I strongly suggest the document
> sticks to this term.
>
> S 4
> - The intro to this section appears to review/repeat other material.
> Could the set of paragraphs be removed? - If not please rework these
> more concisely and remove the reference to the "paper" - or state what
> this is intended to refer to.
>
> S 4.1.1
> - para 1, first sentence is long and hard to read. please rephrase, and
> please use alternate words instead of: /is fairly well understood these
> days/
>
> S 4.1.2
> - This makes a conclusion for all wireless spectrum, which is not true
> for all cases and is probably a function of the design of the physical
> layer and medium access method:
>
> / For instance,
> wireless spectrum is bit-congestible (for a given coding scheme), /
> -is it possible to say, in /most cases/ or /is usely regarded as/
>
> S 4.2.1
> /But it went on to give advice we now disagree with./
> - Who is the we… tsvwg?
> - Is it possible to instead say the offered advice is updated by this memo.
>
> S.4.2.1
> /But it is not consistent with the
> present recommendations of Section 2./
> - Is it possible to instead say this memo makes different
> recommendations in section 2.
>
> S 4.2.1
> /No-one seems to have pointed out that this changed algorithm
> can often lead to drop probabilities of greater than 1 (which should
> ring alarm bells hinting that there's a mistake in the theory
> somewhere)./
> - Is it please possible to rephrase this?
>
>
> S 4.2.2
> / The above proposals to alter the network equipment to bias towards
> smaller packets have largely carried on outside the IETF process
> (unless one counts a reference in an informational RFC to an archived
> email!). /
> - I'd recommend that you delete the part in parenthesis - If not, you
> need to justify this and explain fully the context.
>
> S 4.2.2
> - final para of section needs to be rewritten. This refers to PCN as a
> proposal. This is now an IETF work item documents have been produced
> defining marking algorithms.
>
> S 4.2.3
> /Although no proposals exist as far as we know/
> - Avoid "we", e.g. /Although there are no known proposals.../
>
> S 4.2.3
> /are there are bound to still exist/
> - please rephrase.
>
> S 5.1
> /we believe the recommended position is now inarguably clear ---/
> - This para needs to be rewritten. Once published this memo will specify
> this, it will not then be a matter of argument.
>
> S 5.1
> / The sample of returns from our vendor survey Section 4.2.4 suggest
> that byte-mode packet drop seems not to be implemented at all let
> alone deployed, or if it is, it is likely to be very sparse.
> Therefore, we do not really need a migration strategy from all but
> nothing to nothing./
> - This should be said simpler, or preferably removed. It's not essential
> to restate this here.
>
> S6
> /This draft/This memo/
>
> S6
> / Of course, if
> transports really want to make the greatest gains, they don't have to
> respond to congestion anyway. But we don't want applications that
> are trying to behave to discover that they can go faster by using
> smaller packets. /
> - I think this could be misread, could we remove the first sentence or
> both?
>
> S7
> - I'm not sure the document needs a conclusion section. There is an
> abstract and a clear summary of recommendations. The conclusion does not
> appear to intend to further add to these. I'd rather keep all the
> recommendations in section 2.
> - If a revised conclusion seems necessary, please omit /strongly/ from
> the wording.
> ( The current conclusion specifically delegates an issue to ICCRG on the
> final line. I don't think this is strictly necessary. A better phrase
> may be /ICCRG is currently chartered to work on these issues./)
>
> Refs:
> /RFC4348/ was obsoleted by /RFC5348/
> - Is there a specific need to cite the obsolete spec.?
>

-- 
Jukka MJ Manner, Professor, PhD.  Phone:  +358+(0)9+470 22481
Aalto University                  Mobile: +358+(0)50+5112973
Department of Communications      Fax:    +358+(0)9+470 22474
and Networking (Comnet)           Office: G320a (Otakaari 5A)
P.O. Box 13000, FIN-00076 Aalto   E-mail: jukka.manner@tkk.fi
Finland                           WWW:    www.comnet.tkk.fi

From ka-cheong.poon@oracle.com  Tue Mar 29 21:21:39 2011
Return-Path: <ka-cheong.poon@oracle.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 DC4073A68DE for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 21:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.488
X-Spam-Level: 
X-Spam-Status: No, score=-5.488 tagged_above=-999 required=5 tests=[AWL=0.155,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4, 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 eawdZIB+HkCa for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 21:21:39 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 121E03A687D for <tsvwg@ietf.org>; Tue, 29 Mar 2011 21:21:39 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2U4NE31016558 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 30 Mar 2011 04:23:16 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2U4NEnu000809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Mar 2011 04:23:14 GMT
Received: from abhmt007.oracle.com (abhmt007.oracle.com [141.146.116.16]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2U4NDfD020752; Tue, 29 Mar 2011 23:23:13 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 29 Mar 2011 21:23:13 -0700
Message-ID: <4D92B02E.8020609@oracle.com>
Date: Wed, 30 Mar 2011 12:23:10 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: "t.petch" <ietfc@btconnect.com>
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com><4D86D500.80807@oracle.com><FF1809C0-5493-4D54-8FF0-56767F252117@lakerest.net> <4D9060A9.5080703@oracle.com> <022701cbed32$d21db0e0$4001a8c0@gateway.2wire.net>
In-Reply-To: <022701cbed32$d21db0e0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt358.oracle.com [141.146.40.158]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090204.4D92B032.0132,ss=1,fgs=0
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: Wed, 30 Mar 2011 04:21:40 -0000

On 03/28/11 06:27 PM, t.petch wrote:

> As I have said before, this is a network protocol,
> networks get knotted (and I would be surprised if
> SCTP were an exception to this) so reset is a less
> disruptive way of getting unknotted than tearing
> everything down and restarting.  That is the
> theoretical justification, don't know how well it
> stands up in practice.


Could you define what "knotted" means?  It is unclear how
the proposed mechanism can apply to your "knotted situation."


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Tue Mar 29 21:27:18 2011
Return-Path: <ka-cheong.poon@oracle.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 2F16E3A6989 for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 21:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[AWL=0.296,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, 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 M-MbveWhKUgH for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 21:27:17 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 5FEC93A68F8 for <tsvwg@ietf.org>; Tue, 29 Mar 2011 21:27:17 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2U4SsSd024189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 30 Mar 2011 04:28:55 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2U4SrQe025576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Mar 2011 04:28:53 GMT
Received: from abhmt010.oracle.com (abhmt010.oracle.com [141.146.116.19]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2U4SrLP030508; Tue, 29 Mar 2011 23:28:53 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 29 Mar 2011 21:28:52 -0700
Message-ID: <4D92B181.50208@oracle.com>
Date: Wed, 30 Mar 2011 12:28:49 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <4D86D500.80807@oracle.com> <FF1809C0-5493-4D54-8FF0-56767F252117@lakerest.net> <4D9060A9.5080703@oracle.com> <82BEF99E-28C0-4428-9964-650A3772CC64@lurchi.franken.de>
In-Reply-To: <82BEF99E-28C0-4428-9964-650A3772CC64@lurchi.franken.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Source-IP: acsmt357.oracle.com [141.146.40.157]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090205.4D92B186.004F,ss=1,fgs=0
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: Wed, 30 Mar 2011 04:27:18 -0000

On 03/28/11 07:10 PM, Michael Tüxen wrote:
> On Mar 28, 2011, at 12:19 PM, Kacheong Poon wrote:

>> I have strong reservation on the idea of TSN/SSN reset.
>> AFAICT, there is no clear and convincing usage example
>> of this mechanism.  At least, none is given in the current
>> draft, which I think is not a usual practice in proposing
>> a standard track protocol mechanism.  On this account,
>> my opinion is that more substantial argument of the
>> proposed mechanism should be put in the draft first, if
>> the authors still want to have this mechanism tied to
>> stream addition.
>>
>> I am OK with the out of band mechanism on the stream
>> addition.  Since I don't see any convincing reason why
>> the TSN/SSN mechanism is needed, I've not spent time in
>> checking it out carefully.  So I won't say I'm OK or not
>> OK about this.
> Hi Kacheong,
>
> you to be sure what you are talking about:
> * Are you talking about the TSN/SSN Reset (I think so)


Right, there is nothing mentioned in the draft.


> * Are you talking about the SSN Reset (I'm not sure, since
>    I provided use-cases for it, but we did not agree on
>    it)


But as I mentioned before, the only rationale I can see from
the example use case is for "easy app writing in some
particular situations."  I cannot consider this as a reason
for a quite fundamental transport protocol mechanism feature.
Making the transport protocol "fatter" is usually not a good
design choice, especially in the case to move some of work
what an app layer should do down to the transport.


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Tue Mar 29 21:33:21 2011
Return-Path: <ka-cheong.poon@oracle.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 8DDE83A6A3D for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 21:33:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.812
X-Spam-Level: 
X-Spam-Status: No, score=-5.812 tagged_above=-999 required=5 tests=[AWL=0.431,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 gipHsfcKmJ5X for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 21:33:20 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id E827C3A6A37 for <tsvwg@ietf.org>; Tue, 29 Mar 2011 21:33:19 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2U4YvEb000328 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Wed, 30 Mar 2011 04:34:58 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2U4YuCP030070 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 30 Mar 2011 04:34:56 GMT
Received: from abhmt004.oracle.com (abhmt004.oracle.com [141.146.116.13]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2U4Yumc028147 for <tsvwg@ietf.org>; Tue, 29 Mar 2011 23:34:56 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 29 Mar 2011 21:34:55 -0700
Message-ID: <4D92B2ED.3070705@oracle.com>
Date: Wed, 30 Mar 2011 12:34:53 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
References: <A4337C52-5E68-4846-877C-BD8F06BAAB54@net.in.tum.de>
In-Reply-To: <A4337C52-5E68-4846-877C-BD8F06BAAB54@net.in.tum.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt358.oracle.com [141.146.40.158]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090205.4D92B2F0.0134,ss=1,fgs=0
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: Wed, 30 Mar 2011 04:33:22 -0000

On 03/29/11 11:52 PM, Lothar Braun wrote:

> I used the last few hours to read through the discussion on sctp-strrst, and the posting from Randy Stewart (quoted at the end of the mail) seems to be a good summary of the discussion.
>
> And I'm now wondering if there are any objections against the ADD stream feature in the draft. From my point of view, as someone who is not a transport layer export, I don't see any objections against this part of the draft after reading it.
> Does someone have arguments against the add stream feature?
>
> Considering the past discussion, there seems to be some time necessary to reach consensus on the reset feature. Am I getting this right?
> I'm now wondering if anyone can estimate how long it will take to address all the open issues and reach an consensus?
>
> If we look at the IPFIX WG, we can see that draft-ietf-ipfix-export-per-sctp-stream-08 has been sitting on the RFC editor queue for over eight months (https://datatracker.ietf.org/wg/ipfix/). I think it shouldn't sit there much longer.
>
> Can there be a discussion at the WG meeting on thursday, on how to get the add stream feature into PS status if people agree that draft-ietf-tsvwg-sctp-strrst needs a lot more time in order to be finished?
>
> If thursdays' discussion concludes that there is a significant time necessary to complete the draft due to the reset feature, can sctp-strrst be split in two parts?
>
> 1.) sctp-add-stream ->  get it ready as fast as possible
> 2.) sctp-reset-stream ->  discuss open issues, take the time that is necessary to reach the necessary rough consensus.


I agree that the above separation is a good way to move forward.
AFAICT, no one has mentioned anything concrete that the SSN and
TSN/SSN reset are used anywhere right now and must move forward
as a PS.  There is no urgent need and I suggest that folks to
think harder before moving forward.


-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From randall@lakerest.net  Tue Mar 29 23:32:07 2011
Return-Path: <randall@lakerest.net>
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 5F2513A6B01 for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 23:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.35
X-Spam-Level: 
X-Spam-Status: No, score=-2.35 tagged_above=-999 required=5 tests=[AWL=-0.107,  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 qDPgBRxa6+EO for <tsvwg@core3.amsl.com>; Tue, 29 Mar 2011 23:32:06 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 0C5073A6A9A for <tsvwg@ietf.org>; Tue, 29 Mar 2011 23:32:05 -0700 (PDT)
Received: from dhcp-54bc.meeting.ietf.org (dhcp-54bc.meeting.ietf.org [130.129.84.188]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2U6Xdhb086921 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 30 Mar 2011 02:33:42 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <4D92B2ED.3070705@oracle.com>
Date: Wed, 30 Mar 2011 02:33:37 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <ADEE5FEA-4BB5-4EEE-9C92-CB4BA880AD99@lakerest.net>
References: <A4337C52-5E68-4846-877C-BD8F06BAAB54@net.in.tum.de> <4D92B2ED.3070705@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1084)
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: Wed, 30 Mar 2011 06:32:07 -0000

Question for you Kacheong:

Did you get my email on the use-case draft?

I don't see it went to tsvwg for some reason (I seem to
be having some mail problems sigh)..

There is now a draft:

draft-stewart-tsvwg-reconfuse-sctp

That talks about uses.. its a bit drafty yet.. and I am
hoping my co-authors will add some more text (I whipped it together
quickly)..

Best wishes

R

-----
Randall Stewart
randall@lakerest.net





From ka-cheong.poon@oracle.com  Wed Mar 30 00:00:53 2011
Return-Path: <ka-cheong.poon@oracle.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 EA9AC3A6B0F for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 00:00:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.834
X-Spam-Level: 
X-Spam-Status: No, score=-5.834 tagged_above=-999 required=5 tests=[AWL=0.409,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 HgAo-lUmp2f5 for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 00:00:53 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id E884A3A67F8 for <tsvwg@ietf.org>; Wed, 30 Mar 2011 00:00:52 -0700 (PDT)
Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2U72S3n009351 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 30 Mar 2011 07:02:30 GMT
Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2U72RfL005090 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Mar 2011 07:02:28 GMT
Received: from abhmt017.oracle.com (abhmt017.oracle.com [141.146.116.26]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2U72QO3002880; Wed, 30 Mar 2011 02:02:26 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 30 Mar 2011 00:02:26 -0700
Message-ID: <4D92D580.6000508@oracle.com>
Date: Wed, 30 Mar 2011 15:02:24 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Randy Stewart <randall@lakerest.net>
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
References: <A4337C52-5E68-4846-877C-BD8F06BAAB54@net.in.tum.de> <4D92B2ED.3070705@oracle.com> <ADEE5FEA-4BB5-4EEE-9C92-CB4BA880AD99@lakerest.net>
In-Reply-To: <ADEE5FEA-4BB5-4EEE-9C92-CB4BA880AD99@lakerest.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt356.oracle.com [141.146.40.156]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090209.4D92D584.010E,ss=1,fgs=0
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: Wed, 30 Mar 2011 07:00:54 -0000

On 03/30/11 02:33 PM, Randy Stewart wrote:
> Question for you Kacheong:
>
> Did you get my email on the use-case draft?


Yes.  But I have not yet checked it out.



-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From randall@lakerest.net  Wed Mar 30 00:09:14 2011
Return-Path: <randall@lakerest.net>
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 3618C3A6A46 for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 00:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.332
X-Spam-Level: 
X-Spam-Status: No, score=-2.332 tagged_above=-999 required=5 tests=[AWL=-0.089, 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 AK7DQp3O2KKX for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 00:09:13 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 3FE953A67EF for <tsvwg@ietf.org>; Wed, 30 Mar 2011 00:09:11 -0700 (PDT)
Received: from dhcp-1318.meeting.ietf.org (dhcp-1318.meeting.ietf.org [130.129.19.24]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2U7Ajhs088352 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 30 Mar 2011 03:10:48 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <A4337C52-5E68-4846-877C-BD8F06BAAB54@net.in.tum.de>
Date: Wed, 30 Mar 2011 03:10:45 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B2CB20AC-D970-458F-A5E5-91003CC876EF@lakerest.net>
References: <A4337C52-5E68-4846-877C-BD8F06BAAB54@net.in.tum.de>
To: Lothar Braun <braun@net.in.tum.de>
X-Mailer: Apple Mail (2.1084)
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: Wed, 30 Mar 2011 07:09:14 -0000

Lothar:

The problem I have with this approach is that this draft
has been around a LONG LONG time. No discussion was ever
made UNTIL we did a LC.... which is sad commentary on things.

If we separate it we will surely end up with one small piece of =
reconfiguration
moving forward and the rest just sitting with no comments... which seems =
to be the
usual situation

Right now as I count things we have:

10 different people that have commented on the list... something like =
the
following
                       FOR      AGAINST       DoesNotCare

ADD-STR                10          0           0
SSN-RESET               7          1           2
TSN/SSN-RESET           6          1           3

Note: FOR also includes folks that have said "we can take it out later
if no one uses it going to Draft Standard"... (Note I am counting you
as a "don't care").

Also Note: there are a couple of folks that would like both an in-band =
mechanism
in addition to the out-of-band mechanism... and even more I think there =
is
at least two that would even like to see a DELETE-STR...=20

Of course the "use case" draft that was just published may or may-not =
change
some opinions... even though it is not complete and a bit drafty...


I see no reason that this cannot move forward... Has Tom as pointed out, =
if no one
uses/implements a feature when we move to Draft standard we can remove =
it.... I see no reason
why the draft as it sits cannot move forward..

We may need to have further discussion on in-band vs out-of-band... I am =
not sure on
that. For all I know Brian as a method to do ADD-Str in-band... If not I =
think it just
adds more work.. but thats a separate discussion.

R


On Mar 29, 2011, at 11:52 AM, Lothar Braun wrote:

> Hi,
>=20
> I used the last few hours to read through the discussion on =
sctp-strrst, and the posting from Randy Stewart (quoted at the end of =
the mail) seems to be a good summary of the discussion.
>=20
> And I'm now wondering if there are any objections against the ADD =
stream feature in the draft. =46rom my point of view, as someone who is =
not a transport layer export, I don't see any objections against this =
part of the draft after reading it.
> Does someone have arguments against the add stream feature?
>=20
> Considering the past discussion, there seems to be some time necessary =
to reach consensus on the reset feature. Am I getting this right?
> I'm now wondering if anyone can estimate how long it will take to =
address all the open issues and reach an consensus?=20
>=20
> If we look at the IPFIX WG, we can see that =
draft-ietf-ipfix-export-per-sctp-stream-08 has been sitting on the RFC =
editor queue for over eight months =
(https://datatracker.ietf.org/wg/ipfix/). I think it shouldn't sit there =
much longer.=20
>=20
> Can there be a discussion at the WG meeting on thursday, on how to get =
the add stream feature into PS status if people agree that =
draft-ietf-tsvwg-sctp-strrst needs a lot more time in order to be =
finished?
>=20
> If thursdays' discussion concludes that there is a significant time =
necessary to complete the draft due to the reset feature, can =
sctp-strrst be split in two parts?
>=20
> 1.) sctp-add-stream -> get it ready as fast as possible
> 2.) sctp-reset-stream -> discuss open issues, take the time that is =
necessary to reach the necessary rough consensus.
>=20
> Best regards,
>  Lothar
>=20
>=20
>> Kacheong:
>>=20
>> I see a large number of responses here... most
>> from you, Michael and a few from Tom/Benoit and Brian.
>>=20
>> How I assess statements on the list (correct me if you
>> feel I have interpreted your statements on the list wrong) are
>> as follows:
>>=20
>> 1) You are definitely against anything but the add feature
>>   and you are ok with the current out-of-band mechanisms.
>>=20
>> 2) Tom wished we had reve'd the spec one more time with the
>>   his previous comments, is not sure of the use case for any
>>   of it but sees value in it possibly. Would like to see more
>>   comments on Brian's thoughts...
>>=20
>> 3) Beniot needs the ADD stream for IPFIX and wants it out :-)
>>=20
>> 4) Brian likes the idea of stream reconfiguration and thinks
>>   we have not gone far enough (no delete stream) and would like
>>   to see the mechanism changed to do all this to be "in-band".=20
>>=20
>> 5) Michael Peter and I (not surprisingly) are in favor of the =
document
>>   as it is.... of course I am not sure how much authors count in all
>>   of this ;-)
>>=20
>>=20
>> So I think, in my assessment, you are the only one speaking against
>> everything (except the ADD)...
>>=20
>> My 2Cents ;-)
>>=20
>> R
> --
> Lothar Braun
> Chair for Network Architectures and Services (I8)
> Department of Informatics
> Technische Universit=E4t M=FCnchen
> Boltzmannstr. 3, 85748 Garching bei M=FCnchen, Germany
> Phone:  +49 89 289-18010       Fax: +49 89 289-18033
> E-mail: braun@net.in.tum.de=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From braun@net.in.tum.de  Wed Mar 30 00:58:06 2011
Return-Path: <braun@net.in.tum.de>
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 D0C2C3A6A1F for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 00:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level: 
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 261e7288H6-D for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 00:58:06 -0700 (PDT)
Received: from mail-out1.informatik.tu-muenchen.de (mail-out1.informatik.tu-muenchen.de [131.159.0.8]) by core3.amsl.com (Postfix) with ESMTP id EF5733A6903 for <tsvwg@ietf.org>; Wed, 30 Mar 2011 00:58:05 -0700 (PDT)
Received: from dhcp-9227.meeting.ietf.org (unknown [130.129.10.39]) by mail.net.in.tum.de (Postfix) with ESMTPSA id 22CF7208C748; Wed, 30 Mar 2011 09:59:39 +0200 (CEST)
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Lothar Braun <braun@net.in.tum.de>
In-Reply-To: <B2CB20AC-D970-458F-A5E5-91003CC876EF@lakerest.net>
Date: Wed, 30 Mar 2011 09:59:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <91F8F65C-3BDE-4F28-8FB7-8A97BBF61748@net.in.tum.de>
References: <A4337C52-5E68-4846-877C-BD8F06BAAB54@net.in.tum.de> <B2CB20AC-D970-458F-A5E5-91003CC876EF@lakerest.net>
To: Randy Stewart <randall@lakerest.net>
X-Mailer: Apple Mail (2.1084)
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: Wed, 30 Mar 2011 07:58:06 -0000

Hi Randy,

On Mar 30, 2011, at 9:10 AM, Randy Stewart wrote:

> Lothar:
>=20
> The problem I have with this approach is that this draft
> has been around a LONG LONG time. No discussion was ever
> made UNTIL we did a LC.... which is sad commentary on things.
>=20
> If we separate it we will surely end up with one small piece of =
reconfiguration
> moving forward and the rest just sitting with no comments... which =
seems to be the
> usual situation
>=20
> Right now as I count things we have:
>=20
> 10 different people that have commented on the list... something like =
the
> following
>                       FOR      AGAINST       DoesNotCare
>=20
> ADD-STR                10          0           0
> SSN-RESET               7          1           2
> TSN/SSN-RESET           6          1           3


Please note that I'm not requesting the split of the document. I just =
wanted to say, that there should be a discussion on splitting *IF* we =
can see that moving sctp-strrst to PS will take quite some time because =
of the reset-feature.=20
And your figures seem to indicate that there is a consensus on moving it =
to PS.

> Note: FOR also includes folks that have said "we can take it out later
> if no one uses it going to Draft Standard"... (Note I am counting you
> as a "don't care").

Please move me into the FOR group. I think the draft should progress =
into PS including the reset-feature.

Best regards,
  Lothar

--
Lothar Braun
Chair for Network Architectures and Services (I8)
Department of Informatics
Technische Universit=E4t M=FCnchen
Boltzmannstr. 3, 85748 Garching bei M=FCnchen, Germany
Phone:  +49 89 289-18010       Fax: +49 89 289-18033
E-mail: braun@net.in.tum.de=20







From randall@lakerest.net  Wed Mar 30 01:17:32 2011
Return-Path: <randall@lakerest.net>
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 A523428C115 for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 01:17:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.319
X-Spam-Level: 
X-Spam-Status: No, score=-2.319 tagged_above=-999 required=5 tests=[AWL=-0.076, 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 nrRG5vbBBVeA for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 01:17:31 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 15BA23A6821 for <tsvwg@ietf.org>; Wed, 30 Mar 2011 01:17:30 -0700 (PDT)
Received: from dhcp-1318.meeting.ietf.org (dhcp-1318.meeting.ietf.org [130.129.19.24]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2U8J5qt091067 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 30 Mar 2011 04:19:07 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <91F8F65C-3BDE-4F28-8FB7-8A97BBF61748@net.in.tum.de>
Date: Wed, 30 Mar 2011 04:19:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <08F5DEDA-5A2B-4FAB-852A-73CCAE65D761@lakerest.net>
References: <A4337C52-5E68-4846-877C-BD8F06BAAB54@net.in.tum.de> <B2CB20AC-D970-458F-A5E5-91003CC876EF@lakerest.net> <91F8F65C-3BDE-4F28-8FB7-8A97BBF61748@net.in.tum.de>
To: Lothar Braun <braun@net.in.tum.de>
X-Mailer: Apple Mail (2.1084)
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: Wed, 30 Mar 2011 08:17:32 -0000

Lothar:

Ok thanks.. its a bit late to correct my slides for tsvwg.. but I
will note that the numbers have changed..

Thanks

R
On Mar 30, 2011, at 3:59 AM, Lothar Braun wrote:

> Hi Randy,
>=20
> On Mar 30, 2011, at 9:10 AM, Randy Stewart wrote:
>=20
>> Lothar:
>>=20
>> The problem I have with this approach is that this draft
>> has been around a LONG LONG time. No discussion was ever
>> made UNTIL we did a LC.... which is sad commentary on things.
>>=20
>> If we separate it we will surely end up with one small piece of =
reconfiguration
>> moving forward and the rest just sitting with no comments... which =
seems to be the
>> usual situation
>>=20
>> Right now as I count things we have:
>>=20
>> 10 different people that have commented on the list... something like =
the
>> following
>>                      FOR      AGAINST       DoesNotCare
>>=20
>> ADD-STR                10          0           0
>> SSN-RESET               7          1           2
>> TSN/SSN-RESET           6          1           3
>=20
>=20
> Please note that I'm not requesting the split of the document. I just =
wanted to say, that there should be a discussion on splitting *IF* we =
can see that moving sctp-strrst to PS will take quite some time because =
of the reset-feature.=20
> And your figures seem to indicate that there is a consensus on moving =
it to PS.
>=20
>> Note: FOR also includes folks that have said "we can take it out =
later
>> if no one uses it going to Draft Standard"... (Note I am counting you
>> as a "don't care").
>=20
> Please move me into the FOR group. I think the draft should progress =
into PS including the reset-feature.
>=20
> Best regards,
>  Lothar
>=20
> --
> Lothar Braun
> Chair for Network Architectures and Services (I8)
> Department of Informatics
> Technische Universit=E4t M=FCnchen
> Boltzmannstr. 3, 85748 Garching bei M=FCnchen, Germany
> Phone:  +49 89 289-18010       Fax: +49 89 289-18033
> E-mail: braun@net.in.tum.de=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From martin.becke@uni-due.de  Wed Mar 30 01:22:56 2011
Return-Path: <martin.becke@uni-due.de>
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 5E2B33A6AA0 for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 01:22:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.071
X-Spam-Level: 
X-Spam-Status: No, score=-2.071 tagged_above=-999 required=5 tests=[AWL=-0.178, BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 bi3ycj+6mZXg for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 01:22:55 -0700 (PDT)
Received: from mailoutzim.uni-due.de (mailoutzim.uni-due.de [132.252.185.16]) by core3.amsl.com (Postfix) with ESMTP id D5E7E3A6B29 for <tsvwg@ietf.org>; Wed, 30 Mar 2011 01:22:54 -0700 (PDT)
Received: from HT01.win.uni-due.de (virt080.zim.uni-duisburg-essen.de [132.252.185.80]) by mailoutzim.uni-due.de (8.13.1/8.13.1) with ESMTP id p2U8OVn9021767;  Wed, 30 Mar 2011 10:24:31 +0200
Received: from ccr02.win.uni-due.de ([169.254.2.244]) by HT01.win.uni-due.de ([132.252.190.233]) with mapi id 14.01.0218.012; Wed, 30 Mar 2011 10:24:31 +0200
From: "Becke, Martin" <martin.becke@uni-due.de>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: AW: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Thread-Topic: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Thread-Index: AQHL7ilAy+tyZQ+iifoS3aptxo4f8pRFVVOAgAA0ZGA=
Date: Wed, 30 Mar 2011 08:24:30 +0000
Message-ID: <A33D17830EBE774E8AEFAED600DD54E201193894@ccr02.win.uni-due.de>
References: <A4337C52-5E68-4846-877C-BD8F06BAAB54@net.in.tum.de> <B2CB20AC-D970-458F-A5E5-91003CC876EF@lakerest.net>
In-Reply-To: <B2CB20AC-D970-458F-A5E5-91003CC876EF@lakerest.net>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [132.252.151.202]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Virus-Scanned: Clam Anti Virus - http://www.clamav.net
X-Spam-Scanned: SpamAssassin: 3.002004 - http://www.spamassassin.org
X-Scanned-By: MIMEDefang 2.57 on 132.252.185.16
Cc: Randy Stewart <randall@lakerest.net>
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: Wed, 30 Mar 2011 08:22:56 -0000

I have been reviewing the draft RFC:

   Stream Control Transmission Protocol (SCTP) Stream Reconfiguration
                  draft-ietf-tsvwg-sctp-strrst-09.txt

I think the RFC is useful.
To make it short  (for the presentation):

ADD-STR                FOR +1
SSN-RESET             FOR +1
TSN/SSN-RESET           DoesNotCare+1



> -----Urspr=FCngliche Nachricht-----
> Von: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] Im Auftrag
> von Randy Stewart
> Gesendet: Mittwoch, 30. M=E4rz 2011 09:11
> An: Lothar Braun
> Cc: tsvwg@ietf.org
> Betreff: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
>=20
> Lothar:
>=20
> The problem I have with this approach is that this draft has been around =
a
> LONG LONG time. No discussion was ever made UNTIL we did a LC.... which
> is sad commentary on things.
>=20
> If we separate it we will surely end up with one small piece of
> reconfiguration moving forward and the rest just sitting with no comments=
...
> which seems to be the usual situation
>=20
> Right now as I count things we have:
>=20
> 10 different people that have commented on the list... something like the
> following
>                        FOR      AGAINST       DoesNotCare
>=20
> ADD-STR                10          0           0
> SSN-RESET               7          1           2
> TSN/SSN-RESET           6          1           3
>=20
> Note: FOR also includes folks that have said "we can take it out later if=
 no
> one uses it going to Draft Standard"... (Note I am counting you as a "don=
't
> care").
>=20
> Also Note: there are a couple of folks that would like both an in-band
> mechanism in addition to the out-of-band mechanism... and even more I
> think there is at least two that would even like to see a DELETE-STR...
>=20
> Of course the "use case" draft that was just published may or may-not
> change some opinions... even though it is not complete and a bit drafty..=
.
>=20
>=20
> I see no reason that this cannot move forward... Has Tom as pointed out, =
if
> no one uses/implements a feature when we move to Draft standard we can
> remove it.... I see no reason why the draft as it sits cannot move forwar=
d..
>=20
> We may need to have further discussion on in-band vs out-of-band... I am
> not sure on that. For all I know Brian as a method to do ADD-Str in-band.=
.. If
> not I think it just adds more work.. but thats a separate discussion.
>=20
> R
>=20
>=20
> On Mar 29, 2011, at 11:52 AM, Lothar Braun wrote:
>=20
> > Hi,
> >
> > I used the last few hours to read through the discussion on sctp-strrst=
, and
> the posting from Randy Stewart (quoted at the end of the mail) seems to b=
e
> a good summary of the discussion.
> >
> > And I'm now wondering if there are any objections against the ADD strea=
m
> feature in the draft. From my point of view, as someone who is not a
> transport layer export, I don't see any objections against this part of t=
he
> draft after reading it.
> > Does someone have arguments against the add stream feature?
> >
> > Considering the past discussion, there seems to be some time necessary =
to
> reach consensus on the reset feature. Am I getting this right?
> > I'm now wondering if anyone can estimate how long it will take to addre=
ss
> all the open issues and reach an consensus?
> >
> > If we look at the IPFIX WG, we can see that draft-ietf-ipfix-export-per=
-sctp-
> stream-08 has been sitting on the RFC editor queue for over eight months
> (https://datatracker.ietf.org/wg/ipfix/). I think it shouldn't sit there =
much
> longer.
> >
> > Can there be a discussion at the WG meeting on thursday, on how to get
> the add stream feature into PS status if people agree that draft-ietf-tsv=
wg-
> sctp-strrst needs a lot more time in order to be finished?
> >
> > If thursdays' discussion concludes that there is a significant time nec=
essary
> to complete the draft due to the reset feature, can sctp-strrst be split =
in two
> parts?
> >
> > 1.) sctp-add-stream -> get it ready as fast as possible
> > 2.) sctp-reset-stream -> discuss open issues, take the time that is nec=
essary
> to reach the necessary rough consensus.
> >
> > Best regards,
> >  Lothar
> >
> >
> >> Kacheong:
> >>
> >> I see a large number of responses here... most from you, Michael and
> >> a few from Tom/Benoit and Brian.
> >>
> >> How I assess statements on the list (correct me if you feel I have
> >> interpreted your statements on the list wrong) are as follows:
> >>
> >> 1) You are definitely against anything but the add feature
> >>   and you are ok with the current out-of-band mechanisms.
> >>
> >> 2) Tom wished we had reve'd the spec one more time with the
> >>   his previous comments, is not sure of the use case for any
> >>   of it but sees value in it possibly. Would like to see more
> >>   comments on Brian's thoughts...
> >>
> >> 3) Beniot needs the ADD stream for IPFIX and wants it out :-)
> >>
> >> 4) Brian likes the idea of stream reconfiguration and thinks
> >>   we have not gone far enough (no delete stream) and would like
> >>   to see the mechanism changed to do all this to be "in-band".
> >>
> >> 5) Michael Peter and I (not surprisingly) are in favor of the document
> >>   as it is.... of course I am not sure how much authors count in all
> >>   of this ;-)
> >>
> >>
> >> So I think, in my assessment, you are the only one speaking against
> >> everything (except the ADD)...
> >>
> >> My 2Cents ;-)
> >>
> >> R
> > --
> > Lothar Braun
> > Chair for Network Architectures and Services (I8) Department of
> > Informatics Technische Universit=E4t M=FCnchen Boltzmannstr. 3, 85748
> > Garching bei M=FCnchen, Germany
> > Phone:  +49 89 289-18010       Fax: +49 89 289-18033
> > E-mail: braun@net.in.tum.de
> >
> >
> >
> >
> >
> >
> >
>=20
> -----
> Randall Stewart
> randall@lakerest.net
>=20
>=20
>=20


From ka-cheong.poon@oracle.com  Wed Mar 30 01:28:16 2011
Return-Path: <ka-cheong.poon@oracle.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 399433A6B23 for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 01:28:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.703
X-Spam-Level: 
X-Spam-Status: No, score=-4.703 tagged_above=-999 required=5 tests=[AWL=-0.760, BAYES_00=-2.599, MANGLED_PREMTR=2.3, RCVD_IN_DNSWL_MED=-4, 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 ZPpbzAxN0YCM for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 01:28:15 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 38D893A6B28 for <tsvwg@ietf.org>; Wed, 30 Mar 2011 01:28:15 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2U8TqQI022308 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tsvwg@ietf.org>; Wed, 30 Mar 2011 08:29:53 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2U8TpPk010608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 30 Mar 2011 08:29:51 GMT
Received: from abhmt019.oracle.com (abhmt019.oracle.com [141.146.116.28]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2U8To7d004841 for <tsvwg@ietf.org>; Wed, 30 Mar 2011 03:29:50 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 30 Mar 2011 01:29:50 -0700
Message-ID: <4D92E9FB.2020704@oracle.com>
Date: Wed, 30 Mar 2011 16:29:47 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
References: <A4337C52-5E68-4846-877C-BD8F06BAAB54@net.in.tum.de> <B2CB20AC-D970-458F-A5E5-91003CC876EF@lakerest.net>
In-Reply-To: <B2CB20AC-D970-458F-A5E5-91003CC876EF@lakerest.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt357.oracle.com [141.146.40.157]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090206.4D92E9FF.009C,ss=1,fgs=0
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: Wed, 30 Mar 2011 08:28:16 -0000

On 03/30/11 03:10 PM, Randy Stewart wrote:

> The problem I have with this approach is that this draft
> has been around a LONG LONG time. No discussion was ever
> made UNTIL we did a LC.... which is sad commentary on things.


There can be many interpretations.  One is that nobody cares
about this.  So does it make sense to have a PS which nobody
cares?  And IMHO it is sad that although the draft has been
around for quite some time, it still does not contain a
substantial argument that the mechanism is needed.


> If we separate it we will surely end up with one small piece of reconfiguration
> moving forward and the rest just sitting with no comments... which seems to be the
> usual situation


So the draft has one mechanism which is used and requested.
And some other mechanisms which are not in use and requested
are "bundled" together with that.  Because of this bundling,
which does not seem to be necessary technically, all of them
must move together. Is it the correct approach?

Suppose the two are separated and as you said and the TSN/SSN
reset mechanism just sits there without further comments.
Does this fact say something that this mechanism is not
needed after all?

Can the WG chairs comment on this?  This seems to me to be
the wrong approach in moving forward a mechanism as a PS.
And IMHO, there is really not enough discussion from the
transport level design perspective in justifying such a
mechanism.  I think it is pre-mature to have a LC on this
mechanism and move it as a PS.




-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From touch@isi.edu  Wed Mar 30 01:46:42 2011
Return-Path: <touch@isi.edu>
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 223073A6919 for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 01:46:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.849
X-Spam-Level: 
X-Spam-Status: No, score=-105.849 tagged_above=-999 required=5 tests=[AWL=0.750, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 ZmZdMUw2348Q for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 01:46:40 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 95D643A6909 for <tsvwg@ietf.org>; Wed, 30 Mar 2011 01:46:40 -0700 (PDT)
Received: from [130.129.21.87] (dhcp-1557.meeting.ietf.org [130.129.21.87]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p2U8lLq7015985 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 30 Mar 2011 01:47:36 -0700 (PDT)
Message-ID: <4D92EE18.1000100@isi.edu>
Date: Wed, 30 Mar 2011 01:47:20 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: reference from IETF TSVAREA bufferbloat discussion
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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: Wed, 30 Mar 2011 08:46:42 -0000

Hi, all,

Here's the reference I raised during the discussion today:

TCP behavior with many flows
R. Morris
ICNP 1997
Atlanta, GA
October 28-October 31
http://www.computer.org/portal/web/csdl/doi/10.1109/ICNP.1997.643715

FYI.

Joe

From ietfc@btconnect.com  Wed Mar 30 04:56:55 2011
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 71E0E28C126 for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 04:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.564
X-Spam-Level: 
X-Spam-Status: No, score=-1.564 tagged_above=-999 required=5 tests=[AWL=0.079,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 CXPVd3Zz8HiX for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 04:56:54 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr10.btconnect.com [213.123.20.128]) by core3.amsl.com (Postfix) with ESMTP id 55A5628C0E6 for <tsvwg@ietf.org>; Wed, 30 Mar 2011 04:56:53 -0700 (PDT)
Received: from host217-44-145-1.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.1]) by c2bthomr10.btconnect.com with SMTP id CIR00324; Wed, 30 Mar 2011 12:58:26 +0100 (BST)
Message-ID: <02b001cbeec9$539e1fa0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Kacheong Poon" <ka-cheong.poon@oracle.com>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com><4D86D500.80807@oracle.com><FF1809C0-5493-4D54-8FF0-56767F252117@lakerest.net> <4D9060A9.5080703@oracle.com> <022701cbed32$d21db0e0$4001a8c0@gateway.2wire.net> <4D92B02E.8020609@oracle.com>
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Date: Wed, 30 Mar 2011 12:57:52 +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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4D931AE2.000E, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020A.4D931AE5.00DB,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, 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: Wed, 30 Mar 2011 11:56:55 -0000

----- Original Message ----- 
From: "Kacheong Poon" <ka-cheong.poon@oracle.com>
To: "t.petch" <ietfc@btconnect.com>
Cc: <tsvwg@ietf.org>
Sent: Wednesday, March 30, 2011 6:23 AM
> On 03/28/11 06:27 PM, t.petch wrote:
> 
> > As I have said before, this is a network protocol,
> > networks get knotted (and I would be surprised if
> > SCTP were an exception to this) so reset is a less
> > disruptive way of getting unknotted than tearing
> > everything down and restarting.  That is the
> > theoretical justification, don't know how well it
> > stands up in practice.
> 
> 
> Could you define what "knotted" means?  It is unclear how
> the proposed mechanism can apply to your "knotted situation."

That the two ends of a transport connection get out of step due
to unforeseen sequences of packet exchange, loss, corruption
or malicious attack, errors in implementation etc etc requiring the
connection to be terminated and re-established, potentially a
costly process in the absence of a reset capability.

A number of protocols saw this later rather than sooner and 
so have added reset capabilities.  To add it to SCTP seems
rather sensible.

It is, perhaps, the difference between spending years working
with real networks, and spending years studying the theory
of networks.

Tom Petch

> 
> K. Poon.
> ka-cheong.poon@oracle.com

From ietfc@btconnect.com  Wed Mar 30 04:59:55 2011
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 1156528C164 for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 04:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.868
X-Spam-Level: 
X-Spam-Status: No, score=-1.868 tagged_above=-999 required=5 tests=[AWL=0.375,  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 SfLWdVZxF+mE for <tsvwg@core3.amsl.com>; Wed, 30 Mar 2011 04:59:54 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr10.btconnect.com [213.123.20.128]) by core3.amsl.com (Postfix) with ESMTP id CC56E28C15F for <tsvwg@ietf.org>; Wed, 30 Mar 2011 04:59:53 -0700 (PDT)
Received: from host217-44-145-1.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.1]) by c2bthomr10.btconnect.com with SMTP id CIR04211; Wed, 30 Mar 2011 13:01:28 +0100 (BST)
Message-ID: <02b801cbeec9$c0701840$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Kacheong Poon" <ka-cheong.poon@oracle.com>, <tsvwg@ietf.org>
References: <A4337C52-5E68-4846-877C-BD8F06BAAB54@net.in.tum.de> <4D92B2ED.3070705@oracle.com>
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Date: Wed, 30 Mar 2011 13:00:55 +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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4D931B98.00B3, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020D.4D931B99.00FF,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
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: Wed, 30 Mar 2011 11:59:55 -0000

----- Original Message -----
From: "Kacheong Poon" <ka-cheong.poon@oracle.com>
To: <tsvwg@ietf.org>
Sent: Wednesday, March 30, 2011 6:34 AM
> On 03/29/11 11:52 PM, Lothar Braun wrote:
>
> > I used the last few hours to read through the discussion on sctp-strrst, and
the posting from Randy Stewart (quoted at the end of the mail) seems to be a
good summary of the discussion.
> >
> > And I'm now wondering if there are any objections against the ADD stream
feature in the draft. From my point of view, as someone who is not a transport
layer export, I don't see any objections against this part of the draft after
reading it.
> > Does someone have arguments against the add stream feature?
> >
> > Considering the past discussion, there seems to be some time necessary to
reach consensus on the reset feature. Am I getting this right?
> > I'm now wondering if anyone can estimate how long it will take to address
all the open issues and reach an consensus?
> >
> > If we look at the IPFIX WG, we can see that
draft-ietf-ipfix-export-per-sctp-stream-08 has been sitting on the RFC editor
queue for over eight months (https://datatracker.ietf.org/wg/ipfix/). I think it
shouldn't sit there much longer.
> >
> > Can there be a discussion at the WG meeting on thursday, on how to get the
add stream feature into PS status if people agree that
draft-ietf-tsvwg-sctp-strrst needs a lot more time in order to be finished?
> >
> > If thursdays' discussion concludes that there is a significant time
necessary to complete the draft due to the reset feature, can sctp-strrst be
split in two parts?
> >
> > 1.) sctp-add-stream ->  get it ready as fast as possible
> > 2.) sctp-reset-stream ->  discuss open issues, take the time that is
necessary to reach the necessary rough consensus.
>
> I agree that the above separation is a good way to move forward.
> AFAICT, no one has mentioned anything concrete that the SSN and
> TSN/SSN reset are used anywhere right now and must move forward
> as a PS.  There is no urgent need and I suggest that folks to
> think harder before moving forward.

I have a concern about the amount of work carving out a subset of
an existing I-D and producing a coherent result.

Perhaps you would consider producing a
draft-poon-tsvwg-sctp-changestream-00
in line with your proposal.

Tom Petch

>
> --
>
> K. Poon.
> ka-cheong.poon@oracle.com


From kojo@cs.helsinki.fi  Wed Mar 30 08:06:04 2011
Return-Path: <kojo@cs.helsinki.fi>
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 5EFA93A6B65; Wed, 30 Mar 2011 08:06:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 tjsTGzhrsiGv; Wed, 30 Mar 2011 08:06:03 -0700 (PDT)
Received: from mail.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by core3.amsl.com (Postfix) with ESMTP id 5E52D3A6847; Wed, 30 Mar 2011 08:06:02 -0700 (PDT)
Received: from x301-5.cs.helsinki.fi (dhcp-11e3.meeting.ietf.org [130.129.17.227]) (AUTH: PLAIN cs-relay, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Wed, 30 Mar 2011 18:07:40 +0300 id 00093E5B.4D93473C.00002FB5
Received: by x301-5.cs.helsinki.fi (Postfix, from userid 3011) id DCE182E1410; Wed, 30 Mar 2011 18:07:38 +0300 (EEST)
Received: from localhost (localhost [127.0.0.1]) by x301-5.cs.helsinki.fi (Postfix) with ESMTP id D7B4F2E01FF; Wed, 30 Mar 2011 18:07:38 +0300 (EEST)
Date: Wed, 30 Mar 2011 18:07:38 +0300 (EEST)
From: Markku Kojo <kojo@cs.helsinki.fi>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet	Assigned Numbers Authority (IANA) Procedures for the Management of the	Service Name and Transport Protocol Port Number Registry) to BCP
In-Reply-To: <C9B5E0B2.2E4AD%michelle.cotton@icann.org>
Message-ID: <alpine.DEB.2.00.1103301755070.22906@x301-5.cs.helsinki.fi>
References: <C9B5E0B2.2E4AD%michelle.cotton@icann.org>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Michelle Cotton <michelle.cotton@icann.org>, The IESG <iesg@ietf.org>, "tsvwg@ietf.org" <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: Wed, 30 Mar 2011 15:06:04 -0000

+1

/Markku

On Mon, 28 Mar 2011, Michelle Cotton wrote:

> +1
>
> Michelle
>
>
> On 3/28/11 5:46 AM, "Lars Eggert" <lars.eggert@nokia.com> wrote:
>
>> As one of the authors/editors, I am fine with this change. Thanks!
>>
>> On 2011-3-28, at 14:14, Alexey Melnikov wrote:
>>> After discussing this new text with IESG and some participants of the TSVWG,
>>> it became clear that while there is clear agreement for adding the first
>>> sentence quoted above ("There is no IETF consensus..."), there is no clear
>>> cut consensus for adding the second sentence ("Therefore, an expert reviewer
>>> should not reject a proposal").
>>>
>>> After even further discussions with proponents of this text, with editors,
>>> IANA, etc., the proposal is to strike the second sentence, i.e. only the
>>> following sentence is going to be added to the document:
>>>
>>> There is no IETF consensus on when it is appropriate to use a second port for
>>> an insecure version of protocol.
>>>
>>> The IESG is already alerted when there are problems with IANA registrations,
>>> so the requirement being removed is not needed.
>>>
>>> If people have problems with this change, please send your objections by 4pm
>>> Prague time on Wednesday, March 30th, as I would like to approve the document
>>> before my IESG term ends.
>>
>
>

From sob@harvard.edu  Thu Mar 31 00:27:40 2011
Return-Path: <sob@harvard.edu>
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 1CE9028C265 for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 00:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.461
X-Spam-Level: 
X-Spam-Status: No, score=-102.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 kyFhvhg8i-YD for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 00:27:39 -0700 (PDT)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id 2825628C1F5 for <tsvwg@ietf.org>; Thu, 31 Mar 2011 00:27:39 -0700 (PDT)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id 9EE6AA0646E; Thu, 31 Mar 2011 03:29:18 -0400 (EDT)
To: tsvwg@ietf.org
Subject: draft-ietf-tsvwg-source-quench-00.txt
Message-Id: <20110331072918.9EE6AA0646E@newdev.eecs.harvard.edu>
Date: Thu, 31 Mar 2011 03:29:18 -0400 (EDT)
From: sob@harvard.edu (Scott O. Bradner)
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: Thu, 31 Mar 2011 07:27:40 -0000

why does section 3 say both that a received source quench MAY be 
and also SHOULD be ignored (discarded)?  seems like it would be
good to be consistent

re SHOULD, (echoing Scott Brim) if SHOULD is used (rather than MUST) it
is good to provide guidance as to when it might be reasonable to
violate the SHOULD

Scott

From bob.briscoe@bt.com  Thu Mar 31 00:32:07 2011
Return-Path: <bob.briscoe@bt.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 65FAE28C1FD for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 00:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.472
X-Spam-Level: 
X-Spam-Status: No, score=-3.472 tagged_above=-999 required=5 tests=[AWL=0.127,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 68VNzIhntB0d for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 00:32:06 -0700 (PDT)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id 2D6C028C1F4 for <tsvwg@ietf.org>; Thu, 31 Mar 2011 00:32:06 -0700 (PDT)
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 31 Mar 2011 08:33:44 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by i2kc08-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.4675); Thu, 31 Mar 2011 08:33:44 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1301556823178; Thu, 31 Mar 2011 08:33:43 +0100
Received: from MUT.jungle.bt.co.uk ([10.73.129.212]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id p2V7XfNH022948; Thu, 31 Mar 2011 08:33:41 +0100
Message-Id: <201103310733.p2V7XfNH022948@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 31 Mar 2011 08:32:40 +0100
To: draft-ietf-tsvwg-source-quench@tools.ietf.org
From: Bob Briscoe <bob.briscoe@bt.com>
Subject: Content for deprecating source-quench
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 31 Mar 2011 07:33:44.0638 (UTC) FILETIME=[F71E95E0:01CBEF75]
Cc: "CROWCROFT, Jon" <Jon.Crowcroft@cl.cam.ac.uk>, tsvwg IETF list <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: Thu, 31 Mar 2011 07:32:07 -0000

Hi Fernando,

Pls feel free to use any of this content that will help, from a 
posting of mine to the TERNLI list in 2006:
<http://www.ietf.org/mail-archive/web/ternli/current/msg00036.html>

Please ack Jon Crowcroft, who gave me a lot of the reasons.


Bob

PS. I guess you might be able to tell I'm a researcher, when an email 
cites 16 references :)



________________________________________________________________
Bob Briscoe,                                BT Innovate & Design 


From ka-cheong.poon@oracle.com  Thu Mar 31 02:04:06 2011
Return-Path: <ka-cheong.poon@oracle.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 0E2D228C185 for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 02:04:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.997
X-Spam-Level: 
X-Spam-Status: No, score=-5.997 tagged_above=-999 required=5 tests=[AWL=0.602,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 qzYTrW+ij2HQ for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 02:04:05 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id EE22128C0E1 for <tsvwg@ietf.org>; Thu, 31 Mar 2011 02:04:04 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2V95gXI007848 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 31 Mar 2011 09:05:43 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2V95fW9026052 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 31 Mar 2011 09:05:42 GMT
Received: from abhmt018.oracle.com (abhmt018.oracle.com [141.146.116.27]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2V95f5d024471; Thu, 31 Mar 2011 04:05:41 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 31 Mar 2011 02:05:41 -0700
Message-ID: <4D9443E2.6050208@oracle.com>
Date: Thu, 31 Mar 2011 17:05:38 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Randy Stewart <randall@lakerest.net>
Subject: Re: Fwd: New Version Notification for draft-stewart-tsvwg-reconfuse-sctp-00
References: <20110329152523.C5C753A6927@core3.amsl.com> <663F18AA-9878-4A5F-856D-AB1CCEE0D955@lakerest.net>
In-Reply-To: <663F18AA-9878-4A5F-856D-AB1CCEE0D955@lakerest.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt357.oracle.com [141.146.40.157]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090206.4D9443E6.004A:SCFSTAT5015188,ss=1,fgs=0
Cc: tsvwg <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: Thu, 31 Mar 2011 09:04:06 -0000

On 03/29/11 11:30 PM, Randy Stewart wrote:

> Per our previous discussion on the list.. this is a real drafty draft... I
> just threw it together in-between sessions here.. it needs a lot
> of polishing.. and some more examples.. but I think it gets
> the point across to my previous speculation..


I took a quick look at the draft.  There are two examples given.
The first one has been mentioned in the list before.  Let me
repeat my comments here.  The way the proposed changes made to
ftp to use SCTP is only one of many ways.  IMHO, choosing the
proposed way is not a reason to support that SSN reset are
needed at the transport layer.  There are other ways to change
ftp to use SCTP streams which can achieve the same thing.
Resetting SSN is not a requirement to make the ftp modifications
work with SCTP.

The second example is more interesting.  But then why does the
existing SCTP mechanism not enough to handle this case?  The
example can be seen as an SCTP association restart case if
Host-A~ assumes the address(es) of Host-A as suggested in the
draft.  Isn't it sufficient?



-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From ka-cheong.poon@oracle.com  Thu Mar 31 02:28:30 2011
Return-Path: <ka-cheong.poon@oracle.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 E1EF83A6919 for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 02:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.545
X-Spam-Level: 
X-Spam-Status: No, score=-5.545 tagged_above=-999 required=5 tests=[AWL=0.098,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4, 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 b+npcGc5C0iS for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 02:28:29 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 5ECCE3A69B8 for <tsvwg@ietf.org>; Thu, 31 Mar 2011 02:27:43 -0700 (PDT)
Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2V9TKBV004417 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 31 Mar 2011 09:29:21 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2V9TJPi016992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 31 Mar 2011 09:29:19 GMT
Received: from abhmt008.oracle.com (abhmt008.oracle.com [141.146.116.17]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2V9TJx1011876; Thu, 31 Mar 2011 04:29:19 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 31 Mar 2011 02:29:19 -0700
Message-ID: <4D94496B.8030402@oracle.com>
Date: Thu, 31 Mar 2011 17:29:15 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: "t.petch" <ietfc@btconnect.com>
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com><4D86D500.80807@oracle.com><FF1809C0-5493-4D54-8FF0-56767F252117@lakerest.net> <4D9060A9.5080703@oracle.com> <022701cbed32$d21db0e0$4001a8c0@gateway.2wire.net> <4D92B02E.8020609@oracle.com> <02b001cbeec9$539e1fa0$4001a8c0@gateway.2wire.net>
In-Reply-To: <02b001cbeec9$539e1fa0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt357.oracle.com [141.146.40.157]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090208.4D944970.0057:SCFSTAT5015188,ss=1,fgs=0
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: Thu, 31 Mar 2011 09:28:31 -0000

On 03/30/11 06:57 PM, t.petch wrote:

> That the two ends of a transport connection get out of step due
> to unforeseen sequences of packet exchange, loss, corruption
> or malicious attack, errors in implementation etc etc requiring the
> connection to be terminated and re-established, potentially a
> costly process in the absence of a reset capability.


The current proposed SCTP reset mechanism also requires
protocol handshake, which is not exactly light weight.
And in this situation, it may make sense to tear down
the association and re-establish a new one even if it
is not cheap.  The SCTP state engine is not supposed to
get out of sync between the two end points.  If it is
out of sync, maybe because of an attack, continuing with
the existing association may as well get back to the
same out of sync situation.  For example, the same attack,
which should know the vtags/ports and other info of the
association, will make it go out of sync again.  Re-
establishing a new association may get away from the attack
as the association info will be different.


> A number of protocols saw this later rather than sooner and
> so have added reset capabilities.  To add it to SCTP seems
> rather sensible.


Could you give some references?  It is interesting to
see why those protocols need a reset mechanism and in what
situations it is needed.




-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From randall@lakerest.net  Thu Mar 31 04:34:38 2011
Return-Path: <randall@lakerest.net>
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 35B783A6906 for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 04:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.488
X-Spam-Level: 
X-Spam-Status: No, score=-2.488 tagged_above=-999 required=5 tests=[AWL=0.111,  BAYES_00=-2.599]
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 if4xq+sYzXym for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 04:34:37 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 7DB043A6875 for <tsvwg@ietf.org>; Thu, 31 Mar 2011 04:34:36 -0700 (PDT)
Received: from dhcp-54bc.meeting.ietf.org (dhcp-54bc.meeting.ietf.org [130.129.84.188]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2VBaBuE051939 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 31 Mar 2011 07:36:14 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: New Version Notification for draft-stewart-tsvwg-reconfuse-sctp-00
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <4D9443E2.6050208@oracle.com>
Date: Thu, 31 Mar 2011 07:36:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <88B43C20-C843-4B51-81B4-B34548CB7C89@lakerest.net>
References: <20110329152523.C5C753A6927@core3.amsl.com> <663F18AA-9878-4A5F-856D-AB1CCEE0D955@lakerest.net> <4D9443E2.6050208@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1084)
Cc: tsvwg <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: Thu, 31 Mar 2011 11:34:38 -0000

On Mar 31, 2011, at 5:05 AM, Kacheong Poon wrote:

> On 03/29/11 11:30 PM, Randy Stewart wrote:
>=20
>> Per our previous discussion on the list.. this is a real drafty =
draft... I
>> just threw it together in-between sessions here.. it needs a lot
>> of polishing.. and some more examples.. but I think it gets
>> the point across to my previous speculation..
>=20
>=20
> I took a quick look at the draft.  There are two examples given.
> The first one has been mentioned in the list before.  Let me
> repeat my comments here.  The way the proposed changes made to
> ftp to use SCTP is only one of many ways.  IMHO, choosing the
> proposed way is not a reason to support that SSN reset are
> needed at the transport layer.  There are other ways to change
> ftp to use SCTP streams which can achieve the same thing.
> Resetting SSN is not a requirement to make the ftp modifications
> work with SCTP.


Here I think we must agree to disagree and from the list I think
you are alone here. Most everyone else is supportive of the idea of
reseting a stream as well as adding. I will let the chairs of course
be the judge of consensus...

I think the big question is the in-band/out-ofband one. The
rest of the stuff I think has rough consensus (but of course thats
my opinion).

The big question for the in-band proponents is can we come up with an=20
alternative mechanism that adds a stream that is NOT out-of-band. If so
then I think its a possible option.. However if you still must implement
two mechanism's then I think an out-of-band mechanism is the best =
approach
(only one method ;-D)





>=20
> The second example is more interesting.  But then why does the
> existing SCTP mechanism not enough to handle this case?  The
> example can be seen as an SCTP association restart case if
> Host-A~ assumes the address(es) of Host-A as suggested in the
> draft.  Isn't it sufficient?


Hmm.. that would be an interesting approach and an alternative. But the
only down side is applications like Sigtran which if I remember Michael =
told
me change a RESTART event into a DISCONNECT/CONNECT.. which is the whole =
thing
you are trying to avoid...

It would also be a bit heavier weight to do of course... but it is =
possible...


R



>=20
>=20
>=20
> --=20
>=20
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
>=20

-----
Randall Stewart
randall@lakerest.net





From ietfc@btconnect.com  Thu Mar 31 04:51:12 2011
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 DB82028C149 for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 04:51:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.593
X-Spam-Level: 
X-Spam-Status: No, score=-1.593 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 upbTg9PKNP-L for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 04:51:12 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr14.btconnect.com [213.123.20.132]) by core3.amsl.com (Postfix) with ESMTP id 93AE628C141 for <tsvwg@ietf.org>; Thu, 31 Mar 2011 04:51:11 -0700 (PDT)
Received: from host217-44-145-1.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.1]) by c2bthomr14.btconnect.com with SMTP id CHQ89531; Thu, 31 Mar 2011 12:52:45 +0100 (BST)
Message-ID: <011401cbef91$b22bc360$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Kacheong Poon" <ka-cheong.poon@oracle.com>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com><4D86D500.80807@oracle.com><FF1809C0-5493-4D54-8FF0-56767F252117@lakerest.net> <4D9060A9.5080703@oracle.com> <022701cbed32$d21db0e0$4001a8c0@gateway.2wire.net> <4D92B02E.8020609@oracle.com> <02b001cbeec9$539e1fa0$4001a8c0@gateway.2wire.net> <4D94496B.8030402@oracle.com>
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Date: Thu, 31 Mar 2011 12:51:36 +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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4D946B0D.00AC, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr14.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020C.4D946B0F.011D,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, 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: Thu, 31 Mar 2011 11:51:13 -0000

----- Original Message ----- 
From: "Kacheong Poon" <ka-cheong.poon@oracle.com>
To: "t.petch" <ietfc@btconnect.com>
Cc: <tsvwg@ietf.org>
Sent: Thursday, March 31, 2011 11:29 AM
> On 03/30/11 06:57 PM, t.petch wrote:
> 
> > That the two ends of a transport connection get out of step due
> > to unforeseen sequences of packet exchange, loss, corruption
> > or malicious attack, errors in implementation etc etc requiring the
> > connection to be terminated and re-established, potentially a
> > costly process in the absence of a reset capability.
> 
> The current proposed SCTP reset mechanism also requires
> protocol handshake, which is not exactly light weight.
> And in this situation, it may make sense to tear down
> the association and re-establish a new one even if it
> is not cheap.  The SCTP state engine is not supposed to
> get out of sync between the two end points.  If it is

As I said before, that is the usual view of a computer
scientist (great fellows, but sometimes limited in 
experience:-); in reality, end points do get out of step and
the question is how to recover.  If you are downloading
50 items to make a web page and then ending the 
connection anyway, easy, kill the connection and start
again (most Windows users will be very familiar with 
the concept of 'Power On Reset':-(.  If your connection lasts for
weeks and builds up state that would take hours
to recreate, then you want something more sensitive
to re-establish the connection.  (As I have said before,
I do not know the use cases of SCTP well enough to
know whether it is used to download web pages or
to build long term databases:-).  Of course this can be
done at the application level but if it is purely the
transport that has failed, then it makes sense to have
a transport level reset.

I see many mechanisms of this kind often under 
the name of graceful restart, in eg BGP, LDP, MPLS, RSVP,
OSPF.  (The last is interesting since it has its own transport as, 
arguably, have the second and third).
All of these are (much) later additions to the original 
protocol reflecting the need that emerged not to 
have to tear everything down and start again.  So when
SCTP says that this is something to standardise, my
answer is yes, what took you so long:-)

As far as I know, none of these RFC give much of a reason
why this facility was introduced; they probably thought it
rather obvious:-)

Tom Petch

> out of sync, maybe because of an attack, continuing with
> the existing association may as well get back to the
> same out of sync situation.  For example, the same attack,
> which should know the vtags/ports and other info of the
> association, will make it go out of sync again.  Re-
> establishing a new association may get away from the attack
> as the association info will be different.
> 
> 
> > A number of protocols saw this later rather than sooner and
> > so have added reset capabilities.  To add it to SCTP seems
> > rather sensible.
> 
> 
> Could you give some references?  It is interesting to
> see why those protocols need a reset mechanism and in what
> situations it is needed.
> 
> K. Poon.
> ka-cheong.poon@oracle.com

From fernando.gont.netbook.win@gmail.com  Thu Mar 31 05:49:01 2011
Return-Path: <fernando.gont.netbook.win@gmail.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 676B23A6952 for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 05:49:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.465
X-Spam-Level: 
X-Spam-Status: No, score=-3.465 tagged_above=-999 required=5 tests=[AWL=0.134,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 tLIoOlBFEYaw for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 05:49:00 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 1B67F3A6767 for <tsvwg@ietf.org>; Thu, 31 Mar 2011 05:48:59 -0700 (PDT)
Received: by wyb29 with SMTP id 29so2230578wyb.31 for <tsvwg@ietf.org>; Thu, 31 Mar 2011 05:50:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=IdcZ+mByS/J3FogkAYBuTTFONNF9e+wo2XHRysX9Yog=; b=wxIRefTq948suAgn6xtyaE+jnw3s6nF/ENh2+r7sxPj8U15gx405jfw9JMCjLbU4j1 ITMhIc2os52bNWaDcuwX2UP8P7rWlF7l0xNyHu2yBtw3gnDziwdoiZxsiz3ODfHiv+F0 NJNCqaD7zB4lLuo07i7cuOvGMi07j33Q5XBfo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=KR5bec8DOxHS3OW98q/HPdgglz1CMQInc68fUQjE3utcsAMJzlpFpjOA+baJW+Oq4/ dGevZ7BqVG+amdeexGDje6dPgbnhLIx6px8VH/cCtaWUqYhIIfcu6BF+G9bINqR0PgfB Td/F4JRsAA4+iTAZtH69alBuDsF55Fd/MrbAc=
Received: by 10.216.87.8 with SMTP id x8mr194717wee.46.1301575839185; Thu, 31 Mar 2011 05:50:39 -0700 (PDT)
Received: from [130.129.16.243] (dhcp-10f3.meeting.ietf.org [130.129.16.243]) by mx.google.com with ESMTPS id m73sm496520wej.16.2011.03.31.05.50.34 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 31 Mar 2011 05:50:38 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D946EBA.2070800@gont.com.ar>
Date: Thu, 31 Mar 2011 09:08:26 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: "Scott O. Bradner" <sob@harvard.edu>
Subject: Re: draft-ietf-tsvwg-source-quench-00.txt
References: <20110331072918.9EE6AA0646E@newdev.eecs.harvard.edu>
In-Reply-To: <20110331072918.9EE6AA0646E@newdev.eecs.harvard.edu>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Thu, 31 Mar 2011 12:49:01 -0000

Hi, Scott,

Thanks so much for your feedback. Please find my comments inline...

On 31/03/2011 04:29 a.m., Scott O. Bradner wrote:
> why does section 3 say both that a received source quench MAY be 
> and also SHOULD be ignored (discarded)?  seems like it would be
> good to be consistent

It says that it MAY be discarded by the network layer, but that it
SHOULD be discarded by TCP.

i.e., you MAY simply drop the SQ at the network layer (without relaying
it to the transport layer). But if TCP receives a SQ, it SHOULD drop it.

I guess the reationale for this is that you may drop the SQ at the
internet-layer (e.g., to avoid cointinue processing the packet at higher
layers). But the important thing is that, if TCP receives it, it SHOULD
drop it.

Note: I'm just the messenger... :-)



> re SHOULD, (echoing Scott Brim) if SHOULD is used (rather than MUST) it
> is good to provide guidance as to when it might be reasonable to
> violate the SHOULD

As far as I am concerned, there's no reason to violate the SHOULD, and
this requirement should probably be a "MUST".

However, so far the comments I have received on list in favor of a
"SHOULD" (as opposed to "MUST") is that "processing ICMP SQs does not
cause interoperability problems".

I'd like to hear what others think... and have no problem at all with
changing this if the wg agrees to do so.

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From fernando.gont.netbook.win@gmail.com  Thu Mar 31 05:49:56 2011
Return-Path: <fernando.gont.netbook.win@gmail.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 9244D3A6914 for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 05:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.492
X-Spam-Level: 
X-Spam-Status: No, score=-3.492 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 CBo9efN2NFj5 for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 05:49:55 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 60E053A6767 for <tsvwg@ietf.org>; Thu, 31 Mar 2011 05:49:55 -0700 (PDT)
Received: by wyb29 with SMTP id 29so2231384wyb.31 for <tsvwg@ietf.org>; Thu, 31 Mar 2011 05:51:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=WC2/f56W3fSCPqW3l2gAMwlAb4WdgbRu14KADvOg4gY=; b=kQbvMT+BRU9S3MPjBj35nbIdYVJEaYzwpMpZX1NK8HdAfYZv/JtlRByrvT34FenWHg cPOUsB/UFYOE/MgYkuwOaignVazhpbjwtYMTB/olh4iX34gAjAHnu5DgVoxXFNGa8Vcq wIdEjwP4J3mahIaWLV0PddstSDCUpeSVoUFJ0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=nc2n3bxYhfF5QmXcnrqNnMHS/VKMRP9zFScEzG4Sokd6/aUJWqj/TLHJX7eEnVlcCk KixzTUPiz5TS4LKL+kavZi8UoNW6skkPIvAO48aVLMpLOxz72SwQdpobDR3jijuNpSaR 7mh/mLJ9R6T0D4H3JaVH0jbHCvN2QdL+lAUpM=
Received: by 10.227.159.69 with SMTP id i5mr2671359wbx.133.1301575894344; Thu, 31 Mar 2011 05:51:34 -0700 (PDT)
Received: from [130.129.16.243] (dhcp-10f3.meeting.ietf.org [130.129.16.243]) by mx.google.com with ESMTPS id w25sm636693wbd.5.2011.03.31.05.51.32 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 31 Mar 2011 05:51:33 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D94730E.8050104@gont.com.ar>
Date: Thu, 31 Mar 2011 09:26:54 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: Content for deprecating source-quench
References: <201103310733.p2V7XfNH022948@bagheera.jungle.bt.co.uk>
In-Reply-To: <201103310733.p2V7XfNH022948@bagheera.jungle.bt.co.uk>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "CROWCROFT, Jon" <Jon.Crowcroft@cl.cam.ac.uk>, tsvwg IETF list <tsvwg@ietf.org>, draft-ietf-tsvwg-source-quench@tools.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: Thu, 31 Mar 2011 12:49:56 -0000

Hi, Bob,

Thanks so much for your feedback! Please find my comments inline...

On 31/03/2011 04:32 a.m., Bob Briscoe wrote:
> Pls feel free to use any of this content that will help, from a posting
> of mine to the TERNLI list in 2006:
> <http://www.ietf.org/mail-archive/web/ternli/current/msg00036.html>

This was indeed very interesting and useful information.

Now, considering possible ways forward with this: Do you think it would
be best to:
* include a reference (in Section 2) to your post "for further
information on why ICMP SQ have become deprecated"?, or,
* that we should enhance the current Section 2 and incorporate at least
part of the contents of your e-mail?, or,
* that we should incorporate the contents of your e-mail into a Appendix?

What do you (and others) think?

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From gorry@erg.abdn.ac.uk  Thu Mar 31 06:02:22 2011
Return-Path: <gorry@erg.abdn.ac.uk>
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 3D8FB28C175 for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 06:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.386
X-Spam-Level: 
X-Spam-Status: No, score=-102.386 tagged_above=-999 required=5 tests=[AWL=0.214, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 v932-l961n2R for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 06:02:21 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id E263928C17B for <tsvwg@ietf.org>; Thu, 31 Mar 2011 06:02:19 -0700 (PDT)
Received: from ra-gorry.erg.abdn.ac.uk ([IPv6:2001:df8:0:16:5ab0:35ff:fe7b:b828]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id p2VD3sS9028664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <tsvwg@ietf.org>; Thu, 31 Mar 2011 14:03:55 +0100 (BST)
Message-ID: <4D947BBB.3020100@erg.abdn.ac.uk>
Date: Thu, 31 Mar 2011 15:03:55 +0200
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: Content for deprecating source-quench
References: <201103310733.p2V7XfNH022948@bagheera.jungle.bt.co.uk> <4D94730E.8050104@gont.com.ar>
In-Reply-To: <4D94730E.8050104@gont.com.ar>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
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: Thu, 31 Mar 2011 13:02:22 -0000

TSVWG today talked about the need for more context on the issues that 
motivate obsoleting source quench. My suggestion would be to use this as 
an input to section 2, rather than including a reference or placing the 
text directly into the document.

I expect more comments will are also emerge from the discussion at the 
Mic today.

Gorry

On 31/03/2011 14:26, Fernando Gont wrote:
> Hi, Bob,
>
> Thanks so much for your feedback! Please find my comments inline...
>
> On 31/03/2011 04:32 a.m., Bob Briscoe wrote:
>> Pls feel free to use any of this content that will help, from a posting
>> of mine to the TERNLI list in 2006:
>> <http://www.ietf.org/mail-archive/web/ternli/current/msg00036.html>
>
> This was indeed very interesting and useful information.
>
> Now, considering possible ways forward with this: Do you think it would
> be best to:
> * include a reference (in Section 2) to your post "for further
> information on why ICMP SQ have become deprecated"?, or,
> * that we should enhance the current Section 2 and incorporate at least
> part of the contents of your e-mail?, or,
> * that we should incorporate the contents of your e-mail into a Appendix?
>
> What do you (and others) think?
>
> Thanks!
>
> Best regards,


From ka-cheong.poon@oracle.com  Thu Mar 31 06:26:13 2011
Return-Path: <ka-cheong.poon@oracle.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 8743D28C0EB for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 06:26:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.549
X-Spam-Level: 
X-Spam-Status: No, score=-5.549 tagged_above=-999 required=5 tests=[AWL=0.094,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4, 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 9p2+wqMQSGnX for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 06:26:12 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 77F7028C0DB for <tsvwg@ietf.org>; Thu, 31 Mar 2011 06:26:12 -0700 (PDT)
Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2VDRnIB018847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 31 Mar 2011 13:27:50 GMT
Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2VDRmXI017015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 31 Mar 2011 13:27:49 GMT
Received: from abhmt005.oracle.com (abhmt005.oracle.com [141.146.116.14]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2VDRmxQ014508; Thu, 31 Mar 2011 08:27:48 -0500
Received: from [10.7.251.223] (/10.7.251.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 31 Mar 2011 06:27:47 -0700
Message-ID: <4D94814D.5080906@oracle.com>
Date: Thu, 31 Mar 2011 21:27:41 +0800
From: Kacheong Poon <ka-cheong.poon@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.15) Gecko/20110304 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: "t.petch" <ietfc@btconnect.com>
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com><4D86D500.80807@oracle.com><FF1809C0-5493-4D54-8FF0-56767F252117@lakerest.net> <4D9060A9.5080703@oracle.com> <022701cbed32$d21db0e0$4001a8c0@gateway.2wire.net> <4D92B02E.8020609@oracle.com> <02b001cbeec9$539e1fa0$4001a8c0@gateway.2wire.net> <4D94496B.8030402@oracle.com> <011401cbef91$b22bc360$4001a8c0@gateway.2wire.net>
In-Reply-To: <011401cbef91$b22bc360$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsmt356.oracle.com [141.146.40.156]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090203.4D948155.0072:SCFSTAT5015188,ss=1,fgs=0
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: Thu, 31 Mar 2011 13:26:13 -0000

On 03/31/11 06:51 PM, t.petch wrote:

> As I said before, that is the usual view of a computer
> scientist (great fellows, but sometimes limited in
> experience:-); in reality, end points do get out of step and
> the question is how to recover.


I agree that end points can get out of sync, because
of say, an attack.  So TSN/SSN on both sides may not
match.  But I think the key point here is why using the
same association is OK given that the condition making
the end points out of sync can just happen again, like
when under an attack.


> If you are downloading
> 50 items to make a web page and then ending the
> connection anyway, easy, kill the connection and start
> again (most Windows users will be very familiar with
> the concept of 'Power On Reset':-(.  If your connection lasts for
> weeks and builds up state that would take hours
> to recreate, then you want something more sensitive
> to re-establish the connection.  (As I have said before,
> I do not know the use cases of SCTP well enough to
> know whether it is used to download web pages or
> to build long term databases:-).  Of course this can be
> done at the application level but if it is purely the
> transport that has failed, then it makes sense to have
> a transport level reset.


I think the above do not apply to SCTP.  An SCTP
association only needs to keep states for the protocol
engine.  Regardless of how long an association lasts,
the same set of states is kept.  If you are referring
to application data, then it is not SCTP's job to keep
state about them after it is delivered to the higher
layer.  In fact, SCTP cannot keep states about those
delivered data and it does not understand why they are.
If the stack on both sides of an association is out of
sync, it is more appropriate to terminate the association
and restart a new one.


> I see many mechanisms of this kind often under
> the name of graceful restart, in eg BGP, LDP, MPLS, RSVP,
> OSPF.  (The last is interesting since it has its own transport as,
> arguably, have the second and third).
> All of these are (much) later additions to the original
> protocol reflecting the need that emerged not to
> have to tear everything down and start again.  So when
> SCTP says that this is something to standardise, my
> answer is yes, what took you so long:-)


My understanding of graceful restart of, say BGP, OSPF,
is not really the same as SCTP TSN/SSN reset.  In those
cases, a peer is restarted and they want to get back in
sync.  And SCTP already handles this case without the
need of TSN/SSN reset.  If graceful restart is what you
have in mind when thinking about TSN/SSN reset, then I
guess we don't really need the new mechanism.




-- 

					K. Poon.
					ka-cheong.poon@oracle.com

From randall@lakerest.net  Thu Mar 31 08:42:10 2011
Return-Path: <randall@lakerest.net>
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 63C7A3A6B13 for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 08:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.322
X-Spam-Level: 
X-Spam-Status: No, score=-2.322 tagged_above=-999 required=5 tests=[AWL=-0.079, 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 ZjuCnpopgcGY for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 08:42:09 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 14A733A694C for <tsvwg@ietf.org>; Thu, 31 Mar 2011 08:42:08 -0700 (PDT)
Received: from dhcp-54bc.meeting.ietf.org (dhcp-54bc.meeting.ietf.org [130.129.84.188]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2VFhe0k061615 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 31 Mar 2011 11:43:43 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <4D94814D.5080906@oracle.com>
Date: Thu, 31 Mar 2011 11:43:40 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <E1CF9817-BFC5-4744-81E2-3D6AD0D088C0@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com><4D86D500.80807@oracle.com><FF1809C0-5493-4D54-8FF0-56767F252117@lakerest.net> <4D9060A9.5080703@oracle.com> <022701cbed32$d21db0e0$4001a8c0@gateway.2wire.net> <4D92B02E.8020609@oracle.com> <02b001cbeec9$539e1fa0$4001a8c0@gateway.2wire.net> <4D94496B.8030402@oracle.com> <011401cbef91$b22bc360$4001a8c0@gateway.2wire.net> <4D94814D.5080906@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1084)
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: Thu, 31 Mar 2011 15:42:10 -0000

On Mar 31, 2011, at 9:27 AM, Kacheong Poon wrote:
> 
> My understanding of graceful restart of, say BGP, OSPF,
> is not really the same as SCTP TSN/SSN reset.  In those
> cases, a peer is restarted and they want to get back in
> sync.  And SCTP already handles this case without the
> need of TSN/SSN reset.  If graceful restart is what you
> have in mind when thinking about TSN/SSN reset, then I
> guess we don't really need the new mechanism.

Actually one of the things the NAT draft does is disable the
restart mechanism... this is because the nat's can tell the 
difference between two associations behind the same NAT
going to the same server socket port coming from the
client ports, but the server can not... So part of that
NAT support TLV in the INIT/INIT-ACK ends up turning off
the restart mechanism..

R

-----
Randall Stewart
randall@lakerest.net





From ietfc@btconnect.com  Thu Mar 31 09:10:42 2011
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 C47193A6B3C for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 09:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.595
X-Spam-Level: 
X-Spam-Status: No, score=-1.595 tagged_above=-999 required=5 tests=[AWL=0.048,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 nZf1wXzQW8bE for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 09:10:40 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr09.btconnect.com [213.123.20.127]) by core3.amsl.com (Postfix) with ESMTP id 100B53A69BF for <tsvwg@ietf.org>; Thu, 31 Mar 2011 09:10:38 -0700 (PDT)
Received: from host217-44-145-1.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.1]) by c2bthomr09.btconnect.com with SMTP id CJL25207; Thu, 31 Mar 2011 17:12:13 +0100 (BST)
Message-ID: <007301cbefb5$f15e4fc0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Kacheong Poon" <ka-cheong.poon@oracle.com>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com><4D86D500.80807@oracle.com><FF1809C0-5493-4D54-8FF0-56767F252117@lakerest.net> <4D9060A9.5080703@oracle.com> <022701cbed32$d21db0e0$4001a8c0@gateway.2wire.net> <4D92B02E.8020609@oracle.com> <02b001cbeec9$539e1fa0$4001a8c0@gateway.2wire.net> <4D94496B.8030402@oracle.com> <011401cbef91$b22bc360$4001a8c0@gateway.2wire.net> <4D94814D.5080906@oracle.com>
Subject: Re: wglc FOR draft-ietf-tsvwg-sctp-strrst-09 started
Date: Thu, 31 Mar 2011 17:11:34 +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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4D94A7DC.00C3, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0208.4D94A7DE.000D,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, 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: Thu, 31 Mar 2011 16:10:42 -0000

----- Original Message ----- 
From: "Kacheong Poon" <ka-cheong.poon@oracle.com>
To: "t.petch" <ietfc@btconnect.com>
Cc: <tsvwg@ietf.org>
Sent: Thursday, March 31, 2011 3:27 PM
> On 03/31/11 06:51 PM, t.petch wrote:
> 
> > As I said before, that is the usual view of a computer
> > scientist (great fellows, but sometimes limited in
> > experience:-); in reality, end points do get out of step and
> > the question is how to recover.
> 
> I agree that end points can get out of sync, because
> of say, an attack.  So TSN/SSN on both sides may not
> match.  But I think the key point here is why using the
> same association is OK given that the condition making
> the end points out of sync can just happen again, like
> when under an attack.
> 
> > If you are downloading
> > 50 items to make a web page and then ending the
> > connection anyway, easy, kill the connection and start
> > again (most Windows users will be very familiar with
> > the concept of 'Power On Reset':-(.  If your connection lasts for
> > weeks and builds up state that would take hours
> > to recreate, then you want something more sensitive
> > to re-establish the connection.  (As I have said before,
> > I do not know the use cases of SCTP well enough to
> > know whether it is used to download web pages or
> > to build long term databases:-).  Of course this can be
> > done at the application level but if it is purely the
> > transport that has failed, then it makes sense to have
> > a transport level reset.
> 
> I think the above do not apply to SCTP.  An SCTP
> association only needs to keep states for the protocol
> engine.  Regardless of how long an association lasts,
> the same set of states is kept.  If you are referring
> to application data, then it is not SCTP's job to keep
> state about them after it is delivered to the higher
> layer.  In fact, SCTP cannot keep states about those
> delivered data and it does not understand why they are.
> If the stack on both sides of an association is out of
> sync, it is more appropriate to terminate the association
> and restart a new one.
> 
> > I see many mechanisms of this kind often under
> > the name of graceful restart, in eg BGP, LDP, MPLS, RSVP,
> > OSPF.  (The last is interesting since it has its own transport as,
> > arguably, have the second and third).
> > All of these are (much) later additions to the original
> > protocol reflecting the need that emerged not to
> > have to tear everything down and start again.  So when
> > SCTP says that this is something to standardise, my
> > answer is yes, what took you so long:-)
> 
> My understanding of graceful restart of, say BGP, OSPF,
> is not really the same as SCTP TSN/SSN reset.  In those
> cases, a peer is restarted and they want to get back in
> sync.  And SCTP already handles this case without the
> need of TSN/SSN reset.  If graceful restart is what you
> have in mind when thinking about TSN/SSN reset, then I
> guess we don't really need the new mechanism.

No, reset is what I have in mind, but the IETF is a bit short
of transport layer protocols with which to illustrate my point:-(
so these are (more or less) application layer doing a similar job.
For example, how many of the BGP restarts (with consequent
ripple effects throughout the Internet) prior to Graceful
Restart were caused by TCP problems which a proper 
TCP reset (not the current 'kill the connection') would have
obviated?  I do not know of any research into that issue
but if you look at BGP prior to Graceful Restart, then when
anything went wrong, it more or less had to take the connection
down and begin all over again with ripple effects etc.  So a TCP reset
of the kind proposed for SCTP could have been quite beneficial.
(Usual caveat about my lack of familiarity with the deployed 
use of SCTP).

Remember too that the SCTP association may have underlying state
as part of security which may be expensive or time consuming
to re-establish which would be unnecessary if all the problem is
is with SSN/TSN, which is also part of the SCTP state.  (I think
that implementation error is the most likely cause of getting knotted,
 as I put it, not an attack, although the latter cannot be ruled out).

Tom Petch

> 
> K. Poon.
> ka-cheong.poon@oracle.com

From bob.briscoe@bt.com  Thu Mar 31 09:46:04 2011
Return-Path: <bob.briscoe@bt.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 689AB3A6930 for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 09:46:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.477
X-Spam-Level: 
X-Spam-Status: No, score=-3.477 tagged_above=-999 required=5 tests=[AWL=0.122,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 MKu0x9TPWIMZ for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 09:46:03 -0700 (PDT)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by core3.amsl.com (Postfix) with ESMTP id 5EB9A3A684E for <tsvwg@ietf.org>; Thu, 31 Mar 2011 09:46:03 -0700 (PDT)
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 31 Mar 2011 17:47:42 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by i2kc06-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.4675); Thu, 31 Mar 2011 17:47:41 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt05.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1301590060357; Thu, 31 Mar 2011 17:47:40 +0100
Received: from MUT.jungle.bt.co.uk ([10.73.0.95]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id p2VGld01025257; Thu, 31 Mar 2011 17:47:39 +0100
Message-Id: <201103311647.p2VGld01025257@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 31 Mar 2011 17:47:36 +0100
To: Fernando Gont <fernando@gont.com.ar>
From: Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: Content for deprecating source-quench
In-Reply-To: <4D94730E.8050104@gont.com.ar>
References: <201103310733.p2V7XfNH022948@bagheera.jungle.bt.co.uk> <4D94730E.8050104@gont.com.ar>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 31 Mar 2011 16:47:41.0877 (UTC) FILETIME=[5A0EC650:01CBEFC3]
Cc: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, tsvwg IETF list <tsvwg@ietf.org>, draft-ietf-tsvwg-source-quench@tools.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: Thu, 31 Mar 2011 16:46:04 -0000

Fernando,

Personally I think, if an RFC is going to deprecate something, it 
needs to say why. Referencing an email archive is a bad idea.

This will make more work, but writing standards isn't meant to be easy.

I have no preference between body & appendix - your doc. But it's not 
as if the doc is too long so far.


Bob

PS. Anantha cc'd as he's having tsvwg list problems.

At 13:26 31/03/2011, Fernando Gont wrote:
>Hi, Bob,
>
>Thanks so much for your feedback! Please find my comments inline...
>
>On 31/03/2011 04:32 a.m., Bob Briscoe wrote:
> > Pls feel free to use any of this content that will help, from a posting
> > of mine to the TERNLI list in 2006:
> > <http://www.ietf.org/mail-archive/web/ternli/current/msg00036.html>
>
>This was indeed very interesting and useful information.
>
>Now, considering possible ways forward with this: Do you think it would
>be best to:
>* include a reference (in Section 2) to your post "for further
>information on why ICMP SQ have become deprecated"?, or,
>* that we should enhance the current Section 2 and incorporate at least
>part of the contents of your e-mail?, or,
>* that we should incorporate the contents of your e-mail into a Appendix?
>
>What do you (and others) think?
>
>Thanks!
>
>Best regards,
>--
>Fernando Gont
>e-mail: fernando@gont.com.ar || fgont@acm.org
>PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1

________________________________________________________________
Bob Briscoe,                                BT Innovate & Design 


From fernando.gont.netbook@gmail.com  Thu Mar 31 10:41:06 2011
Return-Path: <fernando.gont.netbook@gmail.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 C3BD328C108 for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 10:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 sYAqdndF+rQK for <tsvwg@core3.amsl.com>; Thu, 31 Mar 2011 10:41:06 -0700 (PDT)
Received: from mail-fx0-f66.google.com (mail-fx0-f66.google.com [209.85.161.66]) by core3.amsl.com (Postfix) with ESMTP id B5E3228C102 for <tsvwg@ietf.org>; Thu, 31 Mar 2011 10:41:05 -0700 (PDT)
Received: by fxm1 with SMTP id 1so444979fxm.1 for <tsvwg@ietf.org>; Thu, 31 Mar 2011 10:42:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=nCFK5+pnoGYghP/W5T1UsQrhGwOHT4Zy7QORIJlw4vw=; b=W7VyICaAWuiThMKb7YSkufPtkBv3z6bB1MD4ckJ8O1kdxLheACHAY3rHmT+8c0U37V hzp56+eh3qxP8DOnXuH3xFPNlv+yu/zEOsZ9cqokKl4eg/4N7a6QUNV1DnfnGmW/yzbl 1gvxAsIErN6zM6kZ9LPfd3hKB6okjE27Z1oa4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=LixJguN7CaDjIbL+2jqrdeWhqN0c4ucQRin9iyE6/hiSdfpoE2WMFQVacY7CKaoSia YvyNaaWaEN+TqItzqSPnc2mVNSLLBBLey+m5FNDIXpFrDLxgfQ0gBJGio/me/dOWnOPy 9CljcHJ6EcmrVjkiQeR7VROV0mfcfGboXT4vc=
MIME-Version: 1.0
Received: by 10.223.72.132 with SMTP id m4mr890673faj.86.1301593364818; Thu, 31 Mar 2011 10:42:44 -0700 (PDT)
Sender: fernando.gont.netbook@gmail.com
Received: by 10.223.121.79 with HTTP; Thu, 31 Mar 2011 10:42:44 -0700 (PDT)
In-Reply-To: <201103311647.p2VGld01025257@bagheera.jungle.bt.co.uk>
References: <201103310733.p2V7XfNH022948@bagheera.jungle.bt.co.uk> <4D94730E.8050104@gont.com.ar> <201103311647.p2VGld01025257@bagheera.jungle.bt.co.uk>
Date: Thu, 31 Mar 2011 14:42:44 -0300
X-Google-Sender-Auth: t-kkY9wBks3vknH2zHFGS1OBq2c
Message-ID: <AANLkTikQjj9a79rpQTo8BgJA-fNtYrR9yJ51oOqtBTzs@mail.gmail.com>
Subject: Re: Content for deprecating source-quench
From: Fernando Gont <fernando@gont.com.ar>
To: Bob Briscoe <bob.briscoe@bt.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, tsvwg IETF list <tsvwg@ietf.org>, fernando@gont.com.ar, draft-ietf-tsvwg-source-quench@tools.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: Thu, 31 Mar 2011 17:41:06 -0000

On Thu, Mar 31, 2011 at 1:47 PM, Bob Briscoe <bob.briscoe@bt.com> wrote:
>
> Personally I think, if an RFC is going to deprecate something, it needs to
> say why.

I fully agree. The current doc is what it is because at the time the
idea of formally deprecating ICMP SQ originated, folks argued that a
kinda a single page document would do. That's it. But I do agree with
your view.


> Referencing an email archive is a bad idea.

Yes. I just asked which option would make you happier. :-) Unless
somebody yells, I'll incorporate this in the current Section 2 of the
I-D.

Thanks!
Fernando
