Re: [tsvwg] SCTP question

Neil Horman <nhorman@tuxdriver.com> Tue, 16 October 2018 17:36 UTC

Return-Path: <nhorman@tuxdriver.com>
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 0AD27130E17 for <tsvwg@ietfa.amsl.com>; Tue, 16 Oct 2018 10:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.098
X-Spam-Level:
X-Spam-Status: No, score=0.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=1.999, SPF_PASS=-0.001] autolearn=no 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 POzMfVe4XhY4 for <tsvwg@ietfa.amsl.com>; Tue, 16 Oct 2018 10:36:30 -0700 (PDT)
Received: from smtp.tuxdriver.com (tunnel92311-pt.tunnel.tserv13.ash1.ipv6.he.net [IPv6:2001:470:7:9c9::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9400130E11 for <tsvwg@ietf.org>; Tue, 16 Oct 2018 10:36:29 -0700 (PDT)
Received: from [107.15.85.130] (helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <nhorman@tuxdriver.com>) id 1gCDND-00070i-Be; Mon, 15 Oct 2018 20:38:13 -0400
Date: Tue, 16 Oct 2018 13:36:20 -0400
From: Neil Horman <nhorman@tuxdriver.com>
To: philip.eardley@bt.com
Cc: tsvwg@ietf.org, perry.wilks@bt.com
Message-ID: <20181016173620.GB20870@hmswarspite.think-freely.org>
References: <LOXP123MB08050FABE8A17B6BF1F7E64EEBFE0@LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <LOXP123MB08050FABE8A17B6BF1F7E64EEBFE0@LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/TbIYKX52Uorft24BE8p_6XeUYFw>
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: Tue, 16 Oct 2018 17:36:32 -0000

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
>