Re: [Gen-art] Gen-ART Last Call review of draft-ietf-httpbis-cache-header-08

Mark Nottingham <mnot@mnot.net> Wed, 07 July 2021 04:32 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE2643A1129 for <gen-art@ietfa.amsl.com>; Tue, 6 Jul 2021 21:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=jytq01y+; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=JOA2aXJO
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 tnFTIYWsfQi8 for <gen-art@ietfa.amsl.com>; Tue, 6 Jul 2021 21:32:07 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DB4C3A1125 for <gen-art@ietf.org>; Tue, 6 Jul 2021 21:32:07 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id EBA985C00BC; Wed, 7 Jul 2021 00:32:02 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 07 Jul 2021 00:32:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=z ViWRZPO+4f7ziCW8SHZYTv86z6V0inZ5C0+SM2yEPw=; b=jytq01y+2qeQ0sBkw if5TjAS4e8klSyuyAfZWbbsk7VUwrmOPXG3lQHPQ2Dw74lp1UYKivlalMXdG9Lba ReKyBnj1kDFQ76uOh44bMbK6suqX/MG2csYtBLRY2yVjT7MEB1qrsb07PydEJWEv Yg7odD5gpGAEvjwy43uB4pAP2U9QKdKtlZqlXfDETbmPMpdo1j14OvHFYTw8nFSY S5/Y2J2qwsJ1Iwks/qxnVeP4O7hR+bLA6LeuWMKUfIxw93l40I7O/+dVGaVaB5Ef ZYCmTXaeQOcd0cVATjVsB7Qe6hBst+s5flz+VB7lXj4ZcvofxMEy7MAZELFuph36 y7Gow==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=zViWRZPO+4f7ziCW8SHZYTv86z6V0inZ5C0+SM2yE Pw=; b=JOA2aXJOZoXK1p0mBxeMR2J4cBHWiHrFAOuRkmMR51t9qi4/48s5C3lhb MN9WNMQv/nMPMD1a8Yc9u6sqYmEsxPdjeTEiJgPpoP6X6Wwvi2xUmXjpYc+mQur6 L5VuBRMlZwJFi7tJ3X1+lj2xJ0DdvAkgEk4eP7vDC2OouusXpkdG/m/MTcPfnPSk EiMIzilJCXQSfUTa0t6HpokjRa6jcF7rNDkX+vsi7vfAo7C6b5kgMILX5p2isAUM GkIgyGuu+7YmR1a2GWpPCO5kpof9D6YuBgMlWc3xAv4/4nS0/5E+lxLHLBgv2hKc KCQ5aGoqYjfFU+QlRUeYnhAn9FKmw==
X-ME-Sender: <xms:Qi7lYJL-1CYqfg_IT_l_00qsd2777QvnXXqIwzRDAF-I1GVOE2jUvw> <xme:Qi7lYFKs9XfKnQrVR9J537wtSBsbR40J5641Y5-9v5OXQh7eVqwSfKSo7SJfXHVwL Veaemslc3nbODgfFQ>
X-ME-Received: <xmr:Qi7lYBtjZLtrhDYc_agBF4sRSgjxVc5kqznVNRa-4FJaVoeebK4p4guNks0MvNzoXMoPYd-RjSA7hDRx5G--TmBVod7hk6LAh3C6c3AD5k8d1sQr9eG5MMNc>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrtddugdehiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrthhtvg hrnhepvefffffhudetveevhfeuffeigedtuedtheffleetffeftddtgeegjeehieeuteet necuffhomhgrihhnpehmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedtnecurf grrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:Qi7lYKbgjwb8AsAP3wap8WfPhdbEsdAfNtXww1DE-lmvOLla0BiDMg> <xmx:Qi7lYAaPY1i_iuhMSAyc_Fk8CnXAraynXRlinFynC2k4MJ9hKDd7nQ> <xmx:Qi7lYODlUaM0zZfRVjm51XMcx-cozljvxcmgrx38KDl_gZbsZVf1iw> <xmx:Qi7lYHVXp9wUN4uDaB9LNPGduQr0zzEQIrVgOrAjvc-DVyCGHXT-8A>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 7 Jul 2021 00:32:01 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <62a2fed6-481c-5444-0ebb-465cf19bbadf@alum.mit.edu>
Date: Wed, 7 Jul 2021 14:31:58 +1000
Cc: General Area Review Team <gen-art@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B66A803-AC07-430F-826F-392E297F5C96@mnot.net>
References: <e8c8b750-0f10-c462-3bd2-525770aaf51f@alum.mit.edu> <5E5C07AE-AB5B-4909-8A3B-C3EDBCDAF540@mnot.net> <62a2fed6-481c-5444-0ebb-465cf19bbadf@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/gmTZl8xYsZihlo8SbJJFU5VDxj0>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-httpbis-cache-header-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jul 2021 04:32:12 -0000


> On 3 Jul 2021, at 2:00 am, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>> 
>>> I suggest you provide IANA with a template for the registry, and provide authors of extension parameters with a template for what should be included in a specification document.
>> There's a registration template in Section 4, referenced from the IANA considerations.
> 
> Yes, I saw that. But IANA isn't instructed to make a registry containing those things. (They are described as being input to the expert. I'm greatly in favor of specifying what input the expert should consider.)
> 
> Also, IANA is asked to populate the registry from section 2. But section 2 isn't consistent with that template.
> 
> I suggest you be clear about how the IANA registry should be formatted, and then provide a filled in template containing what you want to go into the registry from section 2.

Since this discussion, IANA has commented on the draft, and didn't have any issues with identifying how to populate the registry. I did, however, forget to register the HTTP header itself :)

Cheers,

--
Mark Nottingham   https://www.mnot.net/