Re: [quicwg/base-drafts] Clarify use of the term "supports ECN" (#1631)
Mike Bishop <notifications@github.com> Thu, 09 August 2018 17:13 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 F38FE130E7F for <quic-issues@ietfa.amsl.com>; Thu, 9 Aug 2018 10:13:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 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, 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 U3rBeXrcRg9r for <quic-issues@ietfa.amsl.com>; Thu, 9 Aug 2018 10:13:36 -0700 (PDT)
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 8A0601292AD for <quic-issues@ietf.org>; Thu, 9 Aug 2018 10:13:36 -0700 (PDT)
Date: Thu, 09 Aug 2018 10:13:35 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1533834815; bh=hIZTZPLHIj49pUOrdXoE5bbEk6bO+nquZYngZt22b/s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k7PgEjvy+LLmwtHpQjHhychLLdnuCgeN/urrTc9ZQMU2qMa5H7JotJMrupLC/KRAb j19DPvUwqJryoJc1gZl3OqVuxVHUahAaUDP1X6NOfKk3FAtx26InLabYkbNu7x3uNP dkAgzM3aT9RlBaUZ7XVvwHZ7Sa5n5Jxzf8e/enjg=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd2229562fda8261badee80ad70e90e448121bdca92cf000000011784383f92a169ce14a9568b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1631/review/144939922@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1631@github.com>
References: <quicwg/base-drafts/pull/1631@github.com>
Subject: Re: [quicwg/base-drafts] Clarify use of the term "supports ECN" (#1631)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b6c763f6f7ed_70073ffb0c0be61c7946c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/LALQ6b7iSEyTYA2hg4c4AfEZK5o>
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, 09 Aug 2018 17:13:39 -0000
MikeBishop commented on this pull request.
> @@ -1862,9 +1867,8 @@ concerns.
If an endpoint receives a packet without an ECT or CE codepoint, it responds per
{{processing-and-ack}} with an ACK frame.
-If an endpoint does not support ECN or does not have access to received ECN
-codepoints, it acknowledges received packets per {{processing-and-ack}} with an
-ACK frame.
+If an endpoint does not have access to received ECN codepoints, it acknowledges
Rewrap, but without making the line long enough to produce a build break.
--
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/pull/1631#pullrequestreview-144939922
- [quicwg/base-drafts] Clarify use of the term "sup… mirjak
- Re: [quicwg/base-drafts] Clarify use of the term … Martin Thomson
- Re: [quicwg/base-drafts] Clarify use of the term … mirjak
- Re: [quicwg/base-drafts] Clarify use of the term … Martin Thomson
- Re: [quicwg/base-drafts] Clarify use of the term … mirjak
- Re: [quicwg/base-drafts] Clarify use of the term … Martin Thomson
- Re: [quicwg/base-drafts] Clarify use of the term … mirjak
- Re: [quicwg/base-drafts] Clarify use of the term … janaiyengar
- Re: [quicwg/base-drafts] Clarify use of the term … Mike Bishop
- Re: [quicwg/base-drafts] Clarify use of the term … mirjak
- Re: [quicwg/base-drafts] Clarify use of the term … mirjak
- Re: [quicwg/base-drafts] Clarify use of the term … Mike Bishop
- Re: [quicwg/base-drafts] Clarify use of the term … mirjak
- Re: [quicwg/base-drafts] Clarify use of the term … mirjak
- Re: [quicwg/base-drafts] Clarify use of the term … mirjak
- Re: [quicwg/base-drafts] Clarify use of the term … mirjak
- Re: [quicwg/base-drafts] Clarify use of the term … Martin Thomson