IETF Logo Mail Archive

[quicwg/base-drafts] Use of "supports ECN" is confusing (#1587)

mirjak <notifications@github.com> Thu, 19 July 2018 21:12 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 A50BA130F96 for <quic-issues@ietfa.amsl.com>; Thu, 19 Jul 2018 14:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01] 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 fNTPdfmonQfU for <quic-issues@ietfa.amsl.com>; Thu, 19 Jul 2018 14:12:29 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 171DD130F76 for <quic-issues@ietf.org>; Thu, 19 Jul 2018 14:12:29 -0700 (PDT)
Date: Thu, 19 Jul 2018 14:12:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1532034747; bh=pV0SD2qo8EmHeHjh52CpV7hMJjvvAj8Iz/qXtT3EcCs=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Rw81jo4gWEyNM94Bbo3AeBkeb8qYkXcx0/6M2La5ttpp2taIRbQdiUwsp4McJxGzq u6DF3u4f15aQP8fmiqkbx08QxG9bd89g6sWgN9rcK9nzI5C3W41zfEgzS8L5N0fjar aFSkaUCcMYsJJz7WSn+4c27TdHyTw1zQbNmjUjQ4=
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1064e8170896329b5252637a757dafca0148966f92cf000000011768c0bb92a169ce14701b1c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1587@github.com>
Subject: [quicwg/base-drafts] Use of "supports ECN" is confusing (#1587)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b50febbaf0e5_5f3d3fe40f8ccf5c8452c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
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/01s3eJJ4SllDrJit01idmaZ-xo8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Thu, 19 Jul 2018 21:12:33 -0000

The texts should not talk about supporting ECN because all QUIC endpoints support it. An endpoint that decides to not send ECT marked packets (for what every reason) still needs to send feedback. Even if the receiver cannot access the IP codepoint it will never see one and never send an ECN-ACK frame (but still supoort it).

-- 
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/1587

v2.23.0 | Report a Bug | By Email