IETF Logo Mail Archive

[quicwg/base-drafts] Can we make a normative ref to RFC8085? (#3244)

Gorry Fairhurst <notifications@github.com> Sun, 17 November 2019 04:24 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 3CC31120046 for <quic-issues@ietfa.amsl.com>; Sat, 16 Nov 2019 20:24:41 -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 okPFCDphNZpu for <quic-issues@ietfa.amsl.com>; Sat, 16 Nov 2019 20:24:40 -0800 (PST)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2AEB120041 for <quic-issues@ietf.org>; Sat, 16 Nov 2019 20:24:39 -0800 (PST)
Received: from github-lowworker-39b4a70.va3-iad.github.net (github-lowworker-39b4a70.va3-iad.github.net [10.48.16.66]) by smtp.github.com (Postfix) with ESMTP id 425A666060E for <quic-issues@ietf.org>; Sat, 16 Nov 2019 20:24:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1573964679; bh=iJq58YqsAXmCSD7SLtYOi6WwOrkmqy3sjXNCEtsI3Do=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=isajdDLOIvGqoXW8JzJvmnh80gs2TltZ/24/9OZADBW6RJCELChneXQ1LRqv7PD6t fgyF2FFGtGXlkkAcsTOc25UPb9uyhCv+2Z1BXu0cPFQwcx6nx08zHJL8OnaWl4aQYs DWLlxe7C9/uQOa018X7+dvIi9AwV1Tuyd6c4iuds=
Date: Sat, 16 Nov 2019 20:24:39 -0800
From: Gorry Fairhurst <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7TQXJ7GL7DEUBDOXF33X7APEVBNHHB6OUW5E@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3244@github.com>
Subject: [quicwg/base-drafts] Can we make a normative ref to RFC8085? (#3244)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dd0cb8732781_51903f8f4b6cd96883169"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gorryfair
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/RIRheJw_gUxWI9n_Etqc3FyMUW4>
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: Sun, 17 Nov 2019 04:24:41 -0000

I would like to suggest that RFC8085 is normative. 

This RFC was written as BCP for UDP usage, and QUIC implementations need to comply with that or describe the difference and reach consensus about why it differs.

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

v2.23.0 | Report a Bug | By Email