IETF Logo Mail Archive

Re: [quicwg/base-drafts] clarify what happens when consuming CIDs excessively (#2428)

Mike Bishop <notifications@github.com> Wed, 27 February 2019 19:23 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 45EE312D4EB for <quic-issues@ietfa.amsl.com>; Wed, 27 Feb 2019 11:23:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.383
X-Spam-Level:
X-Spam-Status: No, score=-1.383 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 YJ4rHd0VDK4s for <quic-issues@ietfa.amsl.com>; Wed, 27 Feb 2019 11:23:25 -0800 (PST)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 5AD2A1310A9 for <quic-issues@ietf.org>; Wed, 27 Feb 2019 11:23:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=scwggi5TcElswBaKk9tJWKODwHg=; b=e/JgcHvw10WT4g+U fcUZmSLRT2RlhCFtjBLdEtir+P7i2ViGwS1EotF4XBmDcj8eC8thPY2KyHbbz/wC uI4ohposwwnRCcaZ/SmsjVUXVOsX0IAjZbGgbTADlJMmggCyBTkKpEd0kjSkFjvp 9sC84xGgIdlFmQEbJHmCT3qX9ds=
Received: by filter0428p1iad2.sendgrid.net with SMTP id filter0428p1iad2-13206-5C76E3AB-10 2019-02-27 19:23:23.312515321 +0000 UTC m=+38231.332660156
Received: from github-lowworker-e51511d.cp1-iad.github.net (unknown [192.30.252.34]) by ismtpd0027p1iad2.sendgrid.net (SG) with ESMTP id vc6wBcNjRbSS1CgmHw8wOg for <quic-issues@ietf.org>; Wed, 27 Feb 2019 19:23:23.275 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e51511d.cp1-iad.github.net (Postfix) with ESMTP id 3D8DA80C30 for <quic-issues@ietf.org>; Wed, 27 Feb 2019 11:23:23 -0800 (PST)
Date: Wed, 27 Feb 2019 19:23:23 +0000
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1bb01e89a93ec206df8ea15ce17d1ac3d749429b92cf00000001188ea5ab92a169ce184361c4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2428/review/208717492@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2428@github.com>
References: <quicwg/base-drafts/pull/2428@github.com>
Subject: Re: [quicwg/base-drafts] clarify what happens when consuming CIDs excessively (#2428)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c76e3ab3c2f8_31893f9b98ad45bc5918ba"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3mLuX7UWvcLRdxWEqjeUU6+/c+IH5+pUYwdx GEWiiQvVqN5MS5CLTq4ue8MfHCpmvVq6BkG1kcuCuHdA7dYRzmGsOz1+NUi4hORYncNqqwUCTG/cf5 vr+dhlvc5hV3RyoIuhLCTQxiiOPprocuNjVywfLOWMCKoKBLFi63E+hMzC2I2ZrM33znlkk9a7LkxW 0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/1coPf0clg6_5i9cCCyiyofPVFq8>
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: Wed, 27 Feb 2019 19:23:26 -0000

MikeBishop approved this pull request.

I'm not convinced this is a design change -- there was previously a SHOULD, and this adds additional text (including a MAY) around when you might choose to violate the SHOULD.  However, no mandatory behavior is added, changed, or removed.



-- 
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/2428#pullrequestreview-208717492

v2.27.6 | Report a Bug | By Email | System Status