Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues

Randy Stewart <randall@lakerest.net> Mon, 14 March 2011 23:23 UTC

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: Michael Tüxen <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üxen wrote:

> 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?

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

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

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