IETF Logo Mail Archive

Re: Spin bit decision

Lars Eggert <lars@eggert.org> Tue, 02 October 2018 12:56 UTC

Return-Path: <lars@eggert.org>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17AA91277BB for <quic@ietfa.amsl.com>; Tue, 2 Oct 2018 05:56:01 -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 oMJIfSdmcW3z for <quic@ietfa.amsl.com>; Tue, 2 Oct 2018 05:55:58 -0700 (PDT)
Received: from emh03.mail.saunalahti.fi (emh03.mail.saunalahti.fi [62.142.5.109]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D41F130E5C for <quic@ietf.org>; Tue, 2 Oct 2018 05:55:58 -0700 (PDT)
Received: from eggert.org (unknown [62.248.255.56]) by emh03.mail.saunalahti.fi (Postfix) with ESMTP id A7AAB40208; Tue, 2 Oct 2018 15:55:56 +0300 (EEST)
Received: from slate.eggert.org (pf.eggert.org [172.16.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id B587361DC23; Tue, 2 Oct 2018 15:55:51 +0300 (EEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Re: Spin bit decision
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com>
Date: Tue, 02 Oct 2018 15:55:50 +0300
Cc: IETF QUIC WG <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com>
To: "<alexandre.ferrieux@orange.com>" <alexandre.ferrieux@orange.com>
X-Mailer: Apple Mail (2.3445.100.39)
X-MailScanner-ID: B587361DC23.A3499
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/t-GYUFYML8OtC_gDnAiczuknGeE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Oct 2018 12:56:01 -0000

Hi,

again, as an individual:

On 2018-10-2, at 15:41, <alexandre.ferrieux@orange.com> <alexandre.ferrieux@orange.com> wrote:
> Well, if the spec says that en endpoint MUST copy of flip a bit, an implementor would be fairly ill-advised not do comply.

sure, it may be "ill-advised", but in practice, it won't affect interop at all.

> And nothing prevents from adding a "does it spin ?" criterion to the interop test suite.

We can certainly consider this - it may give us some data about the current capabilities and configurations of the participating stacks.

> Clearly you now have this degree of freedom: weaken that MUST into a MAY or a SHOULD, separately for each role. But for what purpose ?

The point I'm trying to make is that it in practice doesn't matter if the spec says "MUST", "SHOULD" or "MAY", since it doesn't affect interop, and doesn't affect performance. Essentially, each stack can decide in isolation whether to spin, echo, do nothing, grease the bits, etc., no matter what language we put in the spec.

Lars

v2.23.0 | Report a Bug | By Email