IETF Logo Mail Archive

Re: [tcpm] SCTP socket API section needed for rto-restart?

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Tue, 24 March 2015 15:39 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9C591A898A; Tue, 24 Mar 2015 08:39:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level:
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LEuF-iRSly_e; Tue, 24 Mar 2015 08:39:56 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE5191A8980; Tue, 24 Mar 2015 08:39:55 -0700 (PDT)
Received: from [IPv6:2001:67c:370:152:c42a:ebe5:8100:c6c1] (unknown [IPv6:2001:67c:370:152:c42a:ebe5:8100:c6c1]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 06A691C104349; Tue, 24 Mar 2015 16:39:51 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <55117D21.9030708@kau.se>
Date: Tue, 24 Mar 2015 10:39:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F6B508F-9349-4110-9EC6-9BE216C2EB6F@lurchi.franken.de>
References: <55117D21.9030708@kau.se>
To: Anna Brunstrom <anna.brunstrom@kau.se>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tcpm/fiVB85RrfxP6ErMULgbuKOuGhE4>
Cc: "tcpm@ietf.org" <tcpm@ietf.org>, tsvwg@ietf.org
Subject: Re: [tcpm] SCTP socket API section needed for rto-restart?
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Mar 2015 15:39:58 -0000

> On 24 Mar 2015, at 10:05, Anna Brunstrom <anna.brunstrom@kau.se> wrote:
> 
> Dear all,
> 
> In the tcpm session just now there was a discussion as to weather a SCTP socket API section should be added to the rto-restart draft or not. As there was no consensus in the room, we would like feedback from the mailing list.
> 
> As tsvwg handles SCTP, the question goes to both the tcpm and the tsvwg mailing lists.
> 
> The draft is at https://tools.ietf.org/html/draft-ietf-tcpm-rtorestart-05, and describes a small update to the RTO timer management algorithm.
Since I brought the point up, let me give the argument on the list again.
For SCTP extensions, we usually provide an informational section how to
extend the SCTP socket API defined in RFC 6458. So I brought up the question
whether it is envisioned that you allow an application to enable/disable
this feature. If yes, it makes sense to me to add a socket API section
describing how to control it for SCTP.
I'm willing to contribute text, if wanted.

Best regards
Michael
> 
> Any other feedback on the document is of course also welcome.
> 
> Thanks,
> Anna
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
>

v2.23.0 | Report a Bug | By Email