IETF Logo Mail Archive

Re: [quicwg/base-drafts] ECN not required (#2156)

Magnus Westerlund <notifications@github.com> Fri, 14 December 2018 12:47 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8676C12F1AC for <quic-issues@ietfa.amsl.com>; Fri, 14 Dec 2018 04:47:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.459
X-Spam-Level:
X-Spam-Status: No, score=-9.459 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
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 JIrtyhSAx46q for <quic-issues@ietfa.amsl.com>; Fri, 14 Dec 2018 04:47:28 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D4861294D7 for <quic-issues@ietf.org>; Fri, 14 Dec 2018 04:47:28 -0800 (PST)
Date: Fri, 14 Dec 2018 04:47:26 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544791646; bh=f7ddmlXgA5cdB48Lb1hXQ0pZtI4MVvZVcPQ0lKJHJm8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HTgHgz9frQ6DuRZ4XuyJ+tr6Q+DHqAwS021TzZJGcwVTaGVKDLxyooEC0yJx186w2 e7LDJ9VR+6B4EwdZ6r7Ubw3gGu5TElClNoKx4Fbbhz2KVfeeP/N+V2tuxsngvpZx9G mMFwPhB/jT47c+2QNhkMtLMNNi9IcwIKvZVQjTx0=
From: Magnus Westerlund <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab55a372c8fda38820df9d70f2343a7aba0af37fdb92cf00000001182b685e92a169ce174bff2c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2156/447315123@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2156@github.com>
References: <quicwg/base-drafts/issues/2156@github.com>
Subject: Re: [quicwg/base-drafts] ECN not required (#2156)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c13a65e6e07b_46f13f850e0d45bc1005d0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gloinul
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/TNdkDWErjnjibkLqcL5Eoxw8pJ8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2018 12:47:31 -0000

@larseggert  did state the following on the mailing list on the 8th of November:

"Both the -14 ACK_ECN frame and any new unified frame will be mandatory to parse on RX for compliance. But there is no enforceable requirement to act on the content.

Likewise, on TX, it's not enforceable that a stack must obtain the ECN bits from the kernel and encode them. With -14, it would simply always encode ACK frames (and never encode ACK_ECN frames), and with any unified approach, it could simply always encode "nothing marked".

There is maybe a slight nudge towards doing ECN properly with a unified approach, since you need to encode something for ECN, and so you might as well do the right thing. But it remains fully possible to not support ECN, with either approach. (Unfortunately.)"

https://mailarchive.ietf.org/arch/msg/quic/7-VL8efXCDg4q-YWEDzrHG1Gia8

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2156#issuecomment-447315123

v2.23.0 | Report a Bug | By Email