Re: [quicwg/base-drafts] conflicting advice how to handle Retire Prior To (#3195)

Eric Kinnear <notifications@github.com> Fri, 08 November 2019 06:16 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 6D79B1208D4 for <quic-issues@ietfa.amsl.com>; Thu, 7 Nov 2019 22:16:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-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 cN42nfwgOf2f for <quic-issues@ietfa.amsl.com>; Thu, 7 Nov 2019 22:16:06 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C24CE1201B7 for <quic-issues@ietf.org>; Thu, 7 Nov 2019 22:16:05 -0800 (PST)
Received: from github-lowworker-f045d1f.ac4-iad.github.net (github-lowworker-f045d1f.ac4-iad.github.net [10.52.19.54]) by smtp.github.com (Postfix) with ESMTP id 02D3C1C3061 for <quic-issues@ietf.org>; Thu, 7 Nov 2019 22:16:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1573193765; bh=qTf/qjqSTzfr6KeDWwyoQPX7RRF5mTWzkMMA/RV1Efo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tkkH70PhYMjnCP82GT04sHM5hNrHmhITJGM39Diqaas8XNuVsh+uPLWBGF88FW3gs 9zCj8+o+U4qchwGhj5EusfvbTXdkAGKxz4F4fUMwUWlia1ZY/r0UMa54cvJdXeJfHf 0C96mqRtF4mxsfI9UePxPfojcRUD+k2geCpKo+v8=
Date: Thu, 07 Nov 2019 22:16:04 -0800
From: Eric Kinnear <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZKJKVKYKI2APSGBU532I5KJEVBNHHB5ZQDTM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3195/551400183@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3195@github.com>
References: <quicwg/base-drafts/issues/3195@github.com>
Subject: Re: [quicwg/base-drafts] conflicting advice how to handle Retire Prior To (#3195)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dc50824e7391_268b3fd207ecd95c18657d"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: erickinnear
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/65zdrAwLWF1HNZaVYO9gLg5lvQA>
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, 08 Nov 2019 06:16:08 -0000

Definitely agree that this is editorial, we just missed this duplicate requirement in the original change. Removed that duplication and cleaned up the frame description a bit.

-- 
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/3195#issuecomment-551400183