Fwd: [IANA #1180850] Last Call: <draft-ietf-quic-recovery-32.txt> (QUIC Loss Detection and Congestion Control) to Proposed Standard

Lars Eggert <lars@eggert.org> Tue, 17 November 2020 05:40 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 A5C363A0E4D for <quic@ietfa.amsl.com>; Mon, 16 Nov 2020 21:40:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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=eggert.org
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 hcE-kAhuMZka for <quic@ietfa.amsl.com>; Mon, 16 Nov 2020 21:40:28 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2CB23A1082 for <quic@ietf.org>; Mon, 16 Nov 2020 21:40:04 -0800 (PST)
Received: from [IPv6:2a00:ac00:4000:400:f87a:925d:978e:33a7] (unknown [IPv6:2a00:ac00:4000:400:f87a:925d:978e:33a7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 82E49610588 for <quic@ietf.org>; Tue, 17 Nov 2020 07:39:56 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1605591596; bh=sFK8uede/jXTyAoHnQJIniad+TCTVgTtXclAqI/Tw88=; h=From:Subject:References:To:Date; b=f2eRVBo4whD0J0B/ay+MzE8Ex1DrYMMh8AKEmgyupfLXhXBNpikHD+gtTGLEk3cXv koFyrfNKoLZgp35rS7R35wnmMmt47GLSAxijgCxLQUlKmvAKtgll+Xgz+q7jYw60Vo mgpiP9Sgp/VJF54Rk6k4cbuPfeOpSY/3K3eeByZ0=
From: Lars Eggert <lars@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_0C33A468-A89B-46B4-A887-CC53CF121A7A"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Fwd: [IANA #1180850] Last Call: <draft-ietf-quic-recovery-32.txt> (QUIC Loss Detection and Congestion Control) to Proposed Standard
Message-Id: <0A11547B-E130-4E8D-A006-2525938BD9E7@eggert.org>
References: <rt-4.4.3-3420-1605545339-376.1180850-37-0@icann.org>
To: QUIC WG <quic@ietf.org>
Date: Tue, 17 Nov 2020 07:39:56 +0200
X-MailScanner-ID: 82E49610588.A28F3
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/wU0JNC4AtmGIH8F-stDYPNVTB7I>
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, 17 Nov 2020 05:40:30 -0000


> Begin forwarded message:
> 
> From: "Sabrina Tanamal via RT" <drafts-lastcall@iana.org>
> Subject: [IANA #1180850] Last Call: <draft-ietf-quic-recovery-32.txt> (QUIC Loss Detection and Congestion Control) to Proposed Standard
> Date: November 16, 2020 at 18:48:59 GMT+2
> Cc: iesg@ietf.org, jri.ietf@gmail.com, ianswett@google.com, lucaspardue.24.7@gmail.com, lars@eggert.org, martin.h.duke@gmail.com, magnus.westerlund@ericsson.com, quic-chairs@ietf.org
> Reply-To: drafts-lastcall@iana.org
> 
> (BEGIN IANA COMMENTS)
> 
> IESG/Authors/WG Chairs:
> 
> The IANA Functions Operator has reviewed draft-ietf-quic-recovery-32, which is currently in Last Call, and has the following comments:
> 
> We understand that this document doesn't require any registry actions.
> 
> While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object.
> 
> If this assessment is not accurate, please respond as soon as possible.
> 
> Thank you,
> 
> Sabrina Tanamal
> Senior IANA Services Specialist
> 
> (END IANA COMMENTS)
>