Re: Genart last call review of draft-ietf-httpbis-header-structure-18

David Schinazi <dschinazi.ietf@gmail.com> Tue, 05 May 2020 19:45 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9F253A041E for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 5 May 2020 12:45:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.75
X-Spam-Level:
X-Spam-Status: No, score=-2.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 qXcPwgStNR5z for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 5 May 2020 12:45:43 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA0C33A0418 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 5 May 2020 12:45:42 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1jW3Sc-00046U-AC for ietf-http-wg-dist@listhub.w3.org; Tue, 05 May 2020 19:42:34 +0000
Resent-Date: Tue, 05 May 2020 19:42:34 +0000
Resent-Message-Id: <E1jW3Sc-00046U-AC@lyra.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <dschinazi.ietf@gmail.com>) id 1jW3Sb-00045e-Fm for ietf-http-wg@listhub.w3.org; Tue, 05 May 2020 19:42:33 +0000
Received: from mail-lj1-x22a.google.com ([2a00:1450:4864:20::22a]) by titan.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <dschinazi.ietf@gmail.com>) id 1jW3SZ-0006Sm-L9 for ietf-http-wg@w3.org; Tue, 05 May 2020 19:42:33 +0000
Received: by mail-lj1-x22a.google.com with SMTP id f18so2921274lja.13 for <ietf-http-wg@w3.org>; Tue, 05 May 2020 12:42:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eQ7ZesUCaB0aM9LhaOgPybm3zQ2q2qNEuqftqIhec44=; b=jXF5nweYDghcRNbpDQRncXxKPWUW0KT3p8jvd67q6R/ClfCTmWT2hzDtFz3nKeGhVh mA5ol6gG+zsqpK5S7h50J85/n5NKg1LDWCeKKeJK6aCME/YW0Db/bzBLgCxpISw/EUNM ZnY8QE37pcYaosPcALqvyH7EM4DMrOgssTsnUX0ko0JEMchhl5QUpXddJiqCC6yeNohc 5oGui2kKFbdLdbVbpLskDW0D/CJBqBIsF6Pywg0tuzrPdB0zTbmjfe5anN5QqLvnGsmo wiZo3RNAOJh8ZTKIJUGvmgr1e87sZYK63lxOqcbEkspSpkTmh/kjv3b5qd+0DcY4XdCc HVhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eQ7ZesUCaB0aM9LhaOgPybm3zQ2q2qNEuqftqIhec44=; b=glZjOiiMnEtoFHpTiSG8WJdRr400uhwtssctiiVIqhHgLUXZaaKxgNnm613/TB3wCh Is8hGLKGYVyB4+0mhJzvlRnQ53YYphGVWK1SIBoT2Qqg29+TGM2+ttWGUGEcZieDrzkP U/t9EZzMN88lOdQzXFbCmlYHX+craU9Bi8XKE750dm8Q1EY7EQ+pl6K4B+kjQwO4omgb 7bsNPggucujHb1Zh/QNYMrNf6idThbW9lSjTfOgFaBThLjNkqGGIV7M/T9Lqmmo8Im1O YTvGwp7fdJJrhNaXE4j6c5vv/2/9WwUQG1t+I2G/grN4HyLG4eBlcnPQEmbR4r9j61/B XVxQ==
X-Gm-Message-State: AGi0PubVXJyA9VKKSNa0IsHMRu73G37EGkw4W0nW8Tn8ylYBp0gM6B/E fELGvaAqrTsEctxa0HCHVcZx0ky8vrKXOw9QRsQo/DVt
X-Google-Smtp-Source: APiQypKgh+Q3WKxwjMJ4Ibrf2maVrrxVAWtWiATHlA4k+V22pR5//XUsa+FbJ0vhzs5YxPV3TNnnNv3vDggTTvzldPI=
X-Received: by 2002:a2e:9012:: with SMTP id h18mr2835625ljg.28.1588707739890; Tue, 05 May 2020 12:42:19 -0700 (PDT)
MIME-Version: 1.0
References: <158864148815.25056.4870473086918483854@ietfa.amsl.com> <2E578812-9E59-426E-85A9-B3A5AEA12853@mnot.net>
In-Reply-To: <2E578812-9E59-426E-85A9-B3A5AEA12853@mnot.net>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Tue, 5 May 2020 12:42:09 -0700
Message-ID: <CAPDSy+4y9ZZ-f=MyV1b_-t5OygyYgdr3W4V4soiLVGOgzXKdMg@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: gen-art <gen-art@ietf.org>, draft-ietf-httpbis-header-structure.all@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>, last-call@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007cf9ae05a4ebd8dc"
Received-SPF: pass client-ip=2a00:1450:4864:20::22a; envelope-from=dschinazi.ietf@gmail.com; helo=mail-lj1-x22a.google.com
X-W3C-Hub-Spam-Status: No, score=-5.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1jW3SZ-0006Sm-L9 3b6651dfe9f491f82b18071140d3e8ab
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Genart last call review of draft-ietf-httpbis-header-structure-18
Archived-At: <https://www.w3.org/mid/CAPDSy+4y9ZZ-f=MyV1b_-t5OygyYgdr3W4V4soiLVGOgzXKdMg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37568
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Mon, May 4, 2020 at 10:02 PM Mark Nottingham <mnot@mnot.net> wrote:

> Hi David,
>
> Thanks for the comments. Responses below; I've committed in <
> https://github.com/httpwg/http-extensions/commit/001023>gt;.
>

Thanks for making the changes! That commit looks good to me.


> > On 5 May 2020, at 11:18 am, David Schinazi via Datatracker <
> noreply@ietf.org> wrote:
> >
> > Nits/editorial comments:
> >
> > In s1.2 (Notational Conventions), I didn't understand what greedy meant
> in:
> >   In some places, the algorithms are "greedy" with
> >   whitespace, but this should not affect conformance.
>
> Hmm, I think we can remove that sentence.
>
> > In s2 (Defining New Structured Fields), perhaps "Reference this
> specification."
> >  should instead be "Normatively reference this specification." ?
>
> Sounds good.
>
> > In s2, the definition of Foo-Example Header seems to be enclosed in
> >  "--8<--" and "-->8--" in the TXT version, could be a bug in the tools?
>
> Our AD commented that it was difficult to distinguish the example spec
> text from the surrounding spec text in the text/plain rendering. These
> "scissor" marks were intended to serve that purpose; I suppose they're not
> as common as they used to be. My assumption is that the RFC Editor is going
> to propose a more suitable way to do this.
>

Ah! Now I see it :) Happy to let the RFC editor decide what's best here.


> > In s3.1.2 and s3.2, in the example, I was confused by "a=?0" and "b=?0"
> until I
> > s3.3.6.
> >    Perhaps reordering sections or adding a reference would help?
>
> I think a reference.
>
> > Should there be some guidance for defining new integer fields that don't
> fit in
> > 10^15?
> >    Is a String the recommended approach?
>
> I'm a little wary of giving a single recommendation here; it depends on
> the use case. It might be that it would be better to use two integers, for
> example, and add, multiply or otherwise combine them. Or it might make
> sense to implicitly multiple (e.g., *100) the value. Or it might make sense
> to yes, use a string -- or binary.
>

Sounds good. I was mainly curious because I defined a sh-integer in one of
my drafts for a value that can in theory go up to 2^62-1, and I wonder if
it's worth the added complexity to support values between 10^15 and 2^62...
https://tools.ietf.org/html/draft-schinazi-masque-connect-udp-00#section-5
But we can figure that out in the context of that draft, no need to answer
that question in draft-ietf-httpbis-header-structure if there's no easy
solution that fits all.