From ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org Wed Feb 1 19:42:23 2023 Return-Path: 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 C4BB3C151551 for ; Wed, 1 Feb 2023 19:42:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.748 X-Spam-Level: X-Spam-Status: No, score=-7.748 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.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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="fZsEjZOV"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="Q+hSKqRV" 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 BkYJP7n-EfSq for ; Wed, 1 Feb 2023 19:42:19 -0800 (PST) Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D011CC151544 for ; Wed, 1 Feb 2023 19:42:18 -0800 (PST) Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from ) id 1pNQS1-002hfW-Ue for ietf-http-wg-dist@listhub.w3.org; Thu, 02 Feb 2023 03:39:53 +0000 Resent-Date: Thu, 02 Feb 2023 03:39:53 +0000 Resent-Message-Id: Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pNQRz-002he4-QG for ietf-http-wg@listhub.w3.org; Thu, 02 Feb 2023 03:39:51 +0000 Received: from new1-smtp.messagingengine.com ([66.111.4.221]) by titan.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pNQRw-008uTI-3j; Thu, 02 Feb 2023 03:39:51 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 14AEF5818FC; Wed, 1 Feb 2023 22:39:36 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 01 Feb 2023 22:39:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm1; t=1675309176; x= 1675316376; bh=JiZwoX8OBmB+JYkJT0yjc5qTOWFKZopmYx6+2VWinLc=; b=f ZsEjZOViK6r0FQe1Gq92ZUQ22kGY/cgtjfOjyG+XwuIoC2qXj583LRoZXV/FNblV Yhdw7yaMYvRW85AX+JLF0/VrVI5qBrzNw/ZJZRUYebPQIhZQOUbi6h66b2Ry7SXO mCYjjqzFZZe8ly89VDszNtm5D+S5dYE57YBbqix5pWC4LqL6dGefdYntNwljk6Yc w0Lcsw2diCf48kRa7exhXvkhyXp1ssNEfjRWUuPOWBOX2BZQMHNbq8eKqmCU4h65 46+Fx11iXgglDIBA/eBGvncK8zNdX643fJWWnWsPhm40BBpfJ3tpzi5ZCSOzYrgK pY9mYX2bF7fE+/b5JVuwA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1675309176; x= 1675316376; bh=JiZwoX8OBmB+JYkJT0yjc5qTOWFKZopmYx6+2VWinLc=; b=Q +hSKqRVAZmZT2JBcFZEgd62lHz+HAQjOXIr0yamOX1PfSuQxejK3LQOmYefW5iZP 7Tbn7SM4ZfNcC5R03d4z8Fwf+WgNqpUdRAVGYPAD+lFq925Se75IdYQsshe71Mhf Bh09q28h28IOB4w3QJai2zumE15Pu53esWlbmSuA7uTpNXAsdjNlg40ML/ZbK58d nTTFmyqTWUK5m8zVzHlfSExPHoBv5/1HwkzeAyW9NH4A1045IhjO32UFwQkDehkT cYaGqiIvkfRlAILB7vy/ezu1d9pI3cTgjwncc7qYCCf6z7ZjHD6FHVbmGYVo63vq toy7hDnbICXI2dB2U8aPg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudefjedgieegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne goufhushhpvggtthffohhmrghinhculdegledmnegovfgvgihtqfhnlhihqddqufhprghm sghothdqkgegvdehqddtheculdeftddtmdenucfjughrpegtggfuhfgjffevgffkfhfvof esthhqmhdthhdtjeenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcuoehmnhho thesmhhnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpeefieekteevvdegudetvdeftd dvkefgheffueevheefteekgeevteeigfffjefhudenucffohhmrghinhepudhhohhsthgv gigrmhhplhgvrdgtohhmpdhhthhtphifghdrohhrghdpghhithhhuhgsrdgtohhmpdiffe drohhrghdpghhithhhuhgsrdhiohdpmhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvth X-ME-Proxy: Feedback-ID: ie6694242:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 1 Feb 2023 22:39:34 -0500 (EST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\)) From: Mark Nottingham In-Reply-To: Date: Thu, 2 Feb 2023 14:39:11 +1100 Cc: "ietf-http-wg@w3.org" , Sergey Kanzhelev , =?utf-8?Q?Philippe_Le_H=C3=A9garet?= Content-Transfer-Encoding: quoted-printable Message-Id: <2179E538-3756-4BB3-81D5-F5B8CB0F0514@mnot.net> References: To: "J. Kalyana Sundaram" X-Mailer: Apple Mail (2.3731.400.51.1.1) Received-SPF: pass client-ip=66.111.4.221; envelope-from=mnot@mnot.net; helo=new1-smtp.messagingengine.com X-W3C-Hub-DKIM-Status: validation passed: (address=mnot@mnot.net domain=mnot.net), signature is good X-W3C-Hub-DKIM-Status: validation passed: (address=mnot@mnot.net domain=messagingengine.com), signature is good X-W3C-Hub-Spam-Status: No, score=-9.8 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1 X-W3C-Scan-Sig: titan.w3.org 1pNQRw-008uTI-3j 99accae25814be481f94ee1933dff57e X-Original-To: ietf-http-wg@w3.org Subject: Re: W3C Trace Context Level 2 & Baggage specifications Archived-At: Resent-From: ietf-http-wg@w3.org X-Mailing-List: archive/latest/50668 X-Loop: ietf-http-wg@w3.org Resent-Sender: ietf-http-wg-request@w3.org Precedence: list List-Id: List-Help: List-Post: List-Unsubscribe: Hi Kalyan, Thanks for the heads-up. Just a few observations from a quick read = through -- * 3.2.1 Header Name (and 3.3.2) > In order to increase interoperability across multiple protocols and = encourage successful integration, tracing systems SHOULD encode the = header name as ASCII lowercase. It's a bit unusual to specify this; HTTP header names are widely = implemented as case-insensitive. Why is it felt necessary to say this? = Same question for the preceding paragraph. * 3.2.3 Examples of HTTP traceparent Headers ~~~ Valid traceparent when caller sampled this request: Value =3D 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01 base16(version) =3D 00 base16(trace-id) =3D 4bf92f3577b34da6a3ce929d0e0e4736 base16(parent-id) =3D 00f067aa0ba902b7 base16(trace-flags) =3D 01 // sampled ~~~ This is confusing, because it doesn't actually include the header field. = It'd be more clear if it were an entire request header section, followed = by information about it; e.g., ~~~ GET /foo HTTP/1.1 Host: example.com TraceParent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01 The above request has the following traceparent values: * base16(version) =3D 00 * base16(trace-id) =3D 4bf92f3577b34da6a3ce929d0e0e4736 * base16(parent-id) =3D 00f067aa0ba902b7 * base16(trace-flags) =3D 01 // sampled ~~~ * 3.2.4 Versioning of traceparent Generally, we don't recommend versioning HTTP fields; it's better to = just define a new field name for the new, incompatible semantics or = syntax. Are you using a version flag here because you expect this = structure to appear outside of HTTP headers? * Syntax These headers are somewhat unusual; e.g., tracestate doesn't allow = commas, when it could have just used a quoted value; trace parent has a = very specific encoding rather than using more typical key/value pairs or = lists. Why was this approach taken? We're encouraging new fields to be defined as Structured Fields, rather = than using ABNF; see: https://httpwg.org/specs/rfc8941.html * Other The defining document for HTTP is now RFC9110, not RFC7230/1; please = update your references accordingly. Please see the list of considerations for new fields at = = and make sure you have addressed the points there. See also for the = preferred editorial style for HTTP-related documents. Finally, make sure you register the fields with IANA; see: https://github.com/protocol-registries/http-fields/ (it's good practice to put the registration template in your = specification, but not required) Cheers, > On 1 Feb 2023, at 1:29 pm, J. Kalyana Sundaram = wrote: >=20 > Hello IETF HTTP WG: > Sergey and I are the co-chairs for the W3C Distributed Tracing = Working Group. We are currently in the Wide Review process for the = following two specifications: =20 > =20 > =E2=80=A2 Trace Context Level 2 specification: Trace Context Level = 2 (w3.org), Latest Editor=E2=80=99s Draft: Trace Context Level 2 = (w3c.github.io) > =E2=80=A2 Baggage specification: Propagation format for = distributed context: Baggage (w3.org), Latest Editor=E2=80=99s Draft: = Propagation format for distributed context: Baggage (w3c.github.io) > As part of this wide review process, we wanted to notify you about = the above two specifications and get your approval. Please let us know = if you have any feedback / questions, or if you need any additional = information. > Thanks, > Kalyan -- Mark Nottingham https://www.mnot.net/