Re: Comments regarding draft-nishida-tsvwg-sctp-failover-03.txt

Michael Tüxen <Michael.Tuexen@lurchi.franken.de> Wed, 24 August 2011 12:25 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6147F21F86DF for <tsvwg@ietfa.amsl.com>; Wed, 24 Aug 2011 05:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.171
X-Spam-Level:
X-Spam-Status: No, score=-2.171 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JdXh-f7cvHMD for <tsvwg@ietfa.amsl.com>; Wed, 24 Aug 2011 05:25:53 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id DAEB521F8584 for <tsvwg@ietf.org>; Wed, 24 Aug 2011 05:25:52 -0700 (PDT)
Received: from [192.168.1.103] (p5481D9CE.dip.t-dialin.net [84.129.217.206]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id BCE941C0C0BD9; Wed, 24 Aug 2011 14:27:02 +0200 (CEST)
Subject: Re: Comments regarding draft-nishida-tsvwg-sctp-failover-03.txt
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: Michael Tüxen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <CABxaRLE3BQTvQ69ga8F8FTSGBBh+YiXqBVy_HwNJp06bQ9D8ig@mail.gmail.com>
Date: Wed, 24 Aug 2011 14:27:01 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <91A7771A-DFD8-401D-B9E1-BB1199C12CC6@lurchi.franken.de>
References: <D9D4D27D-0234-444C-801A-B4916F1D9A5A@lurchi.franken.de> <CABxaRLE3BQTvQ69ga8F8FTSGBBh+YiXqBVy_HwNJp06bQ9D8ig@mail.gmail.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
X-Mailer: Apple Mail (2.1084)
Cc: tsvwg list <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 24 Aug 2011 12:25:53 -0000

On Aug 24, 2011, at 12:24 PM, Yoshifumi Nishida wrote:

> Hi Michael,
> 
> Thank you so much for the review.  Most points were addressed by Preethi.
> So, I just would like to clarify one point.
> 
> 2011/8/22 Michael Tüxen <Michael.Tuexen@lurchi.franken.de>:
> 
>> 
>>   o  When the sender receives an heartbeat ACK from a PF destination,
>>      the sender clears the destination's error counter and transitions
>>      the PF destination back to active state.  This state transition
>>      MUST NOT be notified to the ULP unless it is explicitly requested.
>>      This destination's cwnd is set to 1 MTU (TODO: or 2?  Needs more
>>      text discussing rationale; can revisit later?)
>> 
>> We don't have defined a notification. I don't see the value
>> of it. So maybe you want to get rid of it?
> 
> Hmm. I might miss your point, but I believe we cannot use arbitrary value..
> Shall we refer 7.2.1 in RFC4960?
I was not clear... I'm referring to the sentence:

This state transition MUST NOT be notified to the ULP unless it
is explicitly requested.

Currently we do not have such a notification. That is why I'm asking,
if it would be better to remove it.

Best regards
Michael
> 
> --
> Yoshifumi Nishida
> nishida@sfc.wide.ad.jp
>