IETF Logo Mail Archive

[quicwg/base-drafts] RFC Editor comment 8 (Issue #4974)

Lucas Pardue <notifications@github.com> Fri, 25 March 2022 17:40 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 3F63C3A1745 for <quic-issues@ietfa.amsl.com>; Fri, 25 Mar 2022 10:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.696
X-Spam-Level:
X-Spam-Status: No, score=-6.696 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-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 H95AsFtO7RXW for <quic-issues@ietfa.amsl.com>; Fri, 25 Mar 2022 10:40:31 -0700 (PDT)
Received: from smtp.github.com (out-17.smtp.github.com [192.30.252.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 983003A1746 for <quic-issues@ietf.org>; Fri, 25 Mar 2022 10:40:31 -0700 (PDT)
Received: from github-lowworker-b767462.ash1-iad.github.net (github-lowworker-b767462.ash1-iad.github.net [10.56.120.90]) by smtp.github.com (Postfix) with ESMTP id 6D05E5C0DDB for <quic-issues@ietf.org>; Fri, 25 Mar 2022 10:40:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1648230030; bh=xmLhDVKmTXcADbLLTFLO0wgG9r5ky+ZSDDUKn9GFyeg=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=PqD5xKoHNjYYXLGHteaFiG9bhur0B0HY96b4WKktQX0D4jAUEx1ezfvtrP5qBRPv1 SB4lW4H3IjlstoWJQrX3LPVUaQXJRSt4q7n9hqeb4izD/CjMjRV3x4tM8zNagYMFdL tIaCRM6bPgRWfcTrXLJnHSFBpWHkctDNSekFEk5o=
Date: Fri, 25 Mar 2022 10:40:30 -0700
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3OZTO773BD6MHULYWAJMYQ5EVBNHHEMZM6KM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4974@github.com>
Subject: [quicwg/base-drafts] RFC Editor comment 8 (Issue #4974)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_623dfe8e5fb7a_5007c6fc13716a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/SwIfWQCMjk2FltjKzHnn5U9SA1Q>
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, 25 Mar 2022 17:40:37 -0000

RFC-to-be 9114 (draft-ietf-quic-http) includes the following note to indicate that the registrations have a status of permanent and the Change Controller is the IETF.  Should a similar statement be included in this document?  

>From RFC-to-be 9114:
   The initial allocations in these registries created in this document
   are all assigned permanent status and list a change controller of the
   IETF and a contact of the HTTP working group (ietf-http-wg@w3.org).

In addition, note that the padding in the Settings, Stream Types, and Error Codes differs from what appears in the IANA registry.  IANA included the following note when they notified us that their actions for RFC-to-be 9114 were complete:

   NOTE: In the new registries, the padding has been adjusted for consistency from one
   registry to another and with iana.org/assignments/quic. We understand that there may
   be a request to change it.

We have asked Mike (as editor of RFC-to-be 9114) to review, as the padding for the HTTP/3 registries is now inconsistent with the padding for the HTTP/2 registries.  Please review and dicuss and let us  know if any updates are needed. 


-- 
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/4974
You are receiving this because you are subscribed to this thread.

Message ID: <quicwg/base-drafts/issues/4974@github.com>

v2.23.0 | Report a Bug | By Email