Re: [httpapi] Structured Fields for HTTP APIs
Sanjay Dalal <sanjay.dalal@cal.berkeley.edu> Sat, 04 February 2023 17:15 UTC
Return-Path: <sanjay.dalal@gmail.com>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F350C16953E for <httpapi@ietfa.amsl.com>; Sat, 4 Feb 2023 09:15:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.549
X-Spam-Level:
X-Spam-Status: No, score=-1.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.096, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=berkeley.edu
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SKYry7RRx3xG for <httpapi@ietfa.amsl.com>; Sat, 4 Feb 2023 09:15:26 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0037C16953A for <httpapi@ietf.org>; Sat, 4 Feb 2023 09:15:26 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id d2so4239981pjd.5 for <httpapi@ietf.org>; Sat, 04 Feb 2023 09:15:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berkeley.edu; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=BpA1zY2mn6dM8qfMos67s3cE0dqAwbLgmd9j/8c1P8U=; b=sdBpeo7G0Ac541BndTm/EvIbDaWGenLagwTLaC3G1N5ln/1CZlufS2ZIAuFGYk2uei Rwh9mPqml4APdU0MZ0kt82ZcDdiDXeokEMMNxsSrW+EdrHn1eOUnOgm1fUJDFbtaYoKr BsYYx2i5kHErujSuKj5YZlE4BKBwU5NkieLCkwwtREcT+SwkbQsix0OA7lpv4roYZqJA lpePmBga5IgeEZaEwIt4T7QZEHP+O+Q8iX+x1jP6ZsQRstlgJslYS80l80+KXukSlB8V dC/1+8LiqsNulx13tUzA40XeHCg8U768ScIFZVNz2g+x+cMbuOVDOjhdvdysBTW8shpr 68qA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=BpA1zY2mn6dM8qfMos67s3cE0dqAwbLgmd9j/8c1P8U=; b=O1hxJrE5H9GQhTv4DsHDGh9bZCZwjxXpYS/4MA+0sCWiP7I7Wh0MSlic90UjHYR3LN H/x2SHSUKxvLapYcUOfWJm0iTQnVqTAbVGL1278t7p+6tQsGgbKzM/pd5ZOyLm2+RZNE 4hA/5OIrldVBhUC8jF5eOHHmpGw8uFydx/yuRv68kNRgzCuDzEiWywQ3coxpkn5Nlr2e wUbWuYa/vYCS2dChHlX/PyTmg4axZszLAfORs5LDS8Z0hYH8u7odh2otANkIKBZ6G3+4 KMljQeUl11VeK6C89kwJeG9OOx5W1JVqyUqndA+XS2ND10YsgjFabxljllCa4dzcxLHP fIkA==
X-Gm-Message-State: AO0yUKXD/zTBURBcoAuKXl14tqwiLHi6hq0UzibC7+fL2ue8tygvBK7Q bbZWIUutST4hq5ngNdv7FQ0cOsAY3YhcXObjG5ToT179
X-Google-Smtp-Source: AK7set9L2QK/ltAh87DXh2rtOrX+lEX/KeQ2c4HRYQjH7Twxsy7uEdE6fnvHB9SuslWvT/AfiJRERN2/olo0Qx4uLdY=
X-Received: by 2002:a17:902:7d93:b0:198:eeb5:637b with SMTP id a19-20020a1709027d9300b00198eeb5637bmr668961plm.23.1675530925966; Sat, 04 Feb 2023 09:15:25 -0800 (PST)
MIME-Version: 1.0
References: <DM6PR01MB59649603A686559109383E41A3C89@DM6PR01MB5964.prod.exchangelabs.com> <479442be-2bd2-3e0c-9c75-655e62d3af26@gmx.de> <CAP9qbHU7DfPgHUP_GyvtJC1HfwMUj=rqZSR2c7U+yGho=JU0Ow@mail.gmail.com> <3758a944-7cfa-a471-03fc-d256d2a83c16@gmx.de> <B87E31FF-587E-4B45-BAD4-1A58DE736D1D@mnot.net> <5b7b2c1f-b594-7955-a861-cba7e6ecfcf1@gmx.de> <DM6PR01MB5964141ED97D30C893D93220A3D49@DM6PR01MB5964.prod.exchangelabs.com>
In-Reply-To: <DM6PR01MB5964141ED97D30C893D93220A3D49@DM6PR01MB5964.prod.exchangelabs.com>
From: Sanjay Dalal <sanjay.dalal@cal.berkeley.edu>
Date: Sat, 04 Feb 2023 09:15:14 -0800
Message-ID: <CAC5fHGPu_QJ7eEhTUMfUJZ6T9ryWhe82oBWVEQGR5zP4EtWhOQ@mail.gmail.com>
To: Darrel Miller <darrel@tavis.ca>
Cc: "httpapi@ietf.org" <httpapi@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a70a1505f3e2f17f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/663DXv5eg1p2R8gVGalb2JpdQW8>
Subject: Re: [httpapi] Structured Fields for HTTP APIs
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2023 17:15:31 -0000
Is it possible to come up with a middle ground approach where both SF and RFC 3339 be accommodated? The latter being optional as it is more human readable and it would help in debugging with logs. Of course, both must resolve to the same date time value. Thanks. On Sat, Feb 4, 2023 at 7:22 AM Darrel Miller <darrel@tavis.ca> wrote: > > > On 04.02.2023 07:24, Mark Nottingham wrote: > > Regarding Date, I have to say I'm concerned. The HTTP WG had what I'd > consider a strong consensus for the current unix date approach, but it's > not clear to me whether it's actually going to be used. An unambiguous > signal (yes or no) about whether this community will use it in its drafts > would be helpful, IMO. > > Speaking as an API community member, without chair hat, I don’t like the > idea of using unix timestamps for dates in headers. That is perhaps because > I am not used to seeing them and I have rarely worked with them in the > past. It also is unfortunate that we are not taking the guidance from RFC > 3339 RFC 3339: Date and Time on the Internet: Timestamps (rfc-editor.org) > <https://www.rfc-editor.org/rfc/rfc3339#section-5.6> > > > > However, I understand the merits of using this format and I accept that > tooling can largely mitigate the challenges of these values not being human > readable. Although, it is still going to make reading log files harder. > > > > The benefits of consistency and programmatic simplicity are sufficient to > convince me to support an effort to align httpapi documents with the > guidance of the httpwg. > > > > One minor nit from the sfbis document is the phrase “Dates have a data > model that is similar to Integers”. I do hope this will not lead naïve > implementations to use a 32bit signed integer to process the value or we > may have some surprises in 2038. > https://www.ietf.org/archive/id/draft-ietf-httpbis-sfbis-01.html#section-3.3.7 > Calling out that the capital I in that sentence is doing a lot of heavy > lifting might be worthwhile. > > > > Darrel > > -- > httpapi mailing list > httpapi@ietf.org > https://www.ietf.org/mailman/listinfo/httpapi >
- [httpapi] Structured Fields for HTTP APIs Darrel Miller
- Re: [httpapi] Structured Fields for HTTP APIs Julian Reschke
- Re: [httpapi] Structured Fields for HTTP APIs Martin J. Dürst
- Re: [httpapi] Structured Fields for HTTP APIs Roberto Polli
- Re: [httpapi] Structured Fields for HTTP APIs Julian Reschke
- Re: [httpapi] Structured Fields for HTTP APIs Mark Nottingham
- Re: [httpapi] Structured Fields for HTTP APIs Julian Reschke
- Re: [httpapi] Structured Fields for HTTP APIs Darrel Miller
- Re: [httpapi] Structured Fields for HTTP APIs Sanjay Dalal
- Re: [httpapi] Structured Fields for HTTP APIs Erik Wilde
- Re: [httpapi] Structured Fields for HTTP APIs Julian Reschke
- Re: [httpapi] Structured Fields for HTTP APIs Erik Wilde
- Re: [httpapi] Structured Fields for HTTP APIs Julian Reschke
- Re: [httpapi] Structured Fields for HTTP APIs Mark Nottingham