Re: [tsvwg] SCTP question

Michael Tuexen <michael.tuexen@lurchi.franken.de> Mon, 22 October 2018 20:31 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 C14E312DD85 for <tsvwg@ietfa.amsl.com>; Mon, 22 Oct 2018 13:31:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=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 hjU67WUZR5LD for <tsvwg@ietfa.amsl.com>; Mon, 22 Oct 2018 13:31:56 -0700 (PDT)
Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFE69130EE7 for <tsvwg@ietf.org>; Mon, 22 Oct 2018 13:31:55 -0700 (PDT)
Received: from [IPv6:2003:cd:6f29:a600:7863:59df:e367:d044] (p200300CD6F29A600786359DFE367D044.dip0.t-ipconnect.de [IPv6:2003:cd:6f29:a600:7863:59df:e367:d044]) (Authenticated sender: lurchi) by drew.franken.de (Postfix) with ESMTPSA id 671B9721E280C; Mon, 22 Oct 2018 22:31:52 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
From: Michael Tuexen <michael.tuexen@lurchi.franken.de>
In-Reply-To: <LOXP123MB080505C9DDEC754008CEC070EBF40@LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM>
Date: Mon, 22 Oct 2018 22:31:51 +0200
Cc: "Proshin, Maksim" <mproshin@mera.ru>, nhorman@tuxdriver.com, perry.wilks@bt.com, tsvwg@ietf.org, draft-ietf-tsvwg-2960bis@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <F0B8D93E-699D-4C69-BC2C-6A338FABBA93@lurchi.franken.de>
References: <LOXP123MB08050FABE8A17B6BF1F7E64EEBFE0@LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM> <20181016173620.GB20870@hmswarspite.think-freely.org> <5e9e468a035341cea28066c14fddcc26@mera.ru> <LOXP123MB080505C9DDEC754008CEC070EBF40@LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM>
To: philip.eardley@bt.com
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/cSP-ZxmpnTwKbnWzw4yeTFt5ej4>
Subject: Re: [tsvwg] SCTP question
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 22 Oct 2018 20:32:06 -0000

> On 22. Oct 2018, at 12:01, philip.eardley@bt.com wrote:
> 
> Do other people agree?- especially Randall, as editor of RFC4960, and other people who've been involved a lot with SCTP?
I agree with the other people... I interpret it as a SHALL.

When doing conformance testing (which I do once in a while), I expect the INITs and COOKIE-ECHOs to be retransmitted
based on the timer rules (Start with RTO.Initial, double until reaching RTO.Max). If the peer is multihomed and this
is configured, one has to consider if the multiple address are used for retransmitting the INITs and COOKIE-ECHOs.

I know that the use of shall sometimes causes confusion and we will likely resolve this when working on RFC 4960bis.

You can forward my address to your colleague in case he has further questions. I wrote two implementations of the
ETSI conformance test suite for SCTP:
* https://github.com/nplab/ETSI-SCTP-Conformance-Testsuite
  This is based on an extended version of packetdrill and can be used to test socket based
  implementations like the FreeBSD or Linux kernel implementation. Working on Solaris support.
* https://github.com/nplab/sctp-tests
  This can be used for blackbox testing and is based on the SCTP Test Tool stt.

Best regards
Michael
> Thanks
> phil
> 
> 
> -----Original Message-----
> From: Proshin, Maksim [mailto:mproshin@mera.ru] 
> Sent: 17 October 2018 09:32
> To: Neil Horman <nhorman@tuxdriver.com>; Eardley,PL,Philip,TUD1 R <philip.eardley@bt.com>
> Cc: Wilks,PB,Perry,TLB35 R <perry.wilks@bt.com>; tsvwg@ietf.org
> Subject: RE: [tsvwg] SCTP question
> 
> Hi Neil,
> 
> In general it's not correct to say that "shall" is the same as SHALL. Thus RFC 8174 explains that "only UPPERCASE usage of the key words have the defined special meanings".
> Saying this anyway I think that RFC 4960 actually means SHALL/MUST in that note.  
> 
> BR, Maxim
> 
> 
> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Neil Horman
> Sent: Tuesday, October 16, 2018 20:36
> To: philip.eardley@bt.com
> Cc: perry.wilks@bt.com; tsvwg@ietf.org
> Subject: Re: [tsvwg] SCTP question
> 
> On Tue, Oct 16, 2018 at 02:42:05PM +0000, philip.eardley@bt.com wrote:
>> A colleague of mine, Perry, has a couple of questions about SCTP RFC4960. He's in the BT design team on Signalling protocols and concerned about conformance testing amongst other issues.
>> 
>> The statement is on page 57 of RFC4960  (section on Association initialisation) "Note: T1-init timer and T1-cookie timer shall follow the same rules given in Section 6.3."
>> The question is: how should the "shall" be interpreted in this sentence? Does it mean that the S6.3 rules MUST be followed? Or does it mean that the S6.3 rules are optional - in which case, are there any thoughts about rules other than those in S6.3?
>> 
> The conventions section indicates that they keyword SHALL is goverened by RFC2119, which asserts SHALL is synonomous with the keywork MUST.  That is to say that the phrase above on page 57 of RFC4960 is an absolute requirement.  You have to have the T1-init and T1-cookie timer follow the same rules given in Section 6.3
> 
> Neil
> 
>> Thanks,
>> Best wishes,
>> Philip Eardley
>> Research and Innovation
>> This email contains BT information, which may be privileged or confidential.. It's meant only for the individual(s) or entity named above. If you're not the intended recipient, note that disclosing, copying, distributing or using this information is prohibited. If you've received this email in error, please let me know immediately on the email address above. Thank you.
>> We monitor our email system, and may record your emails.
>> British Telecommunications plc
>> Registered office: 81 Newgate Street London EC1A 7AJ Registered in 
>> England no: 1800000
>> 
>