Re: New I-D: The Transport-Info HTTP Header-01

Piers O'Hanlon <piers.ohanlon@bbc.co.uk> Wed, 22 April 2020 13:53 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 1D6023A0DC9 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 22 Apr 2020 06:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.65
X-Spam-Level:
X-Spam-Status: No, score=-2.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 zTQyXsvJ6Pm0 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 22 Apr 2020 06:53:48 -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 04CA73A0D7B for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 22 Apr 2020 06:53:35 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1jRFli-0002tl-RO for ietf-http-wg-dist@listhub.w3.org; Wed, 22 Apr 2020 13:50:26 +0000
Resent-Date: Wed, 22 Apr 2020 13:50:26 +0000
Resent-Message-Id: <E1jRFli-0002tl-RO@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 <piers.ohanlon@bbc.co.uk>) id 1jRFli-0002sy-20 for ietf-http-wg@listhub.w3.org; Wed, 22 Apr 2020 13:50:26 +0000
Received: from mailout0.cwwtf.bbc.co.uk ([132.185.160.179]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <piers.ohanlon@bbc.co.uk>) id 1jRFlg-0001qj-5x for ietf-http-wg@w3.org; Wed, 22 Apr 2020 13:50:25 +0000
Received: from BGB01XI1007.national.core.bbc.co.uk (bgb01xi1007.national.core.bbc.co.uk [10.161.14.21]) by mailout0.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id 03MDoCLJ024762 for <ietf-http-wg@w3.org>; Wed, 22 Apr 2020 14:50:12 +0100 (BST)
Received: from BGB01XUD1009.national.core.bbc.co.uk ([10.161.14.7]) by BGB01XI1007.national.core.bbc.co.uk ([10.161.14.21]) with mapi id 14.03.0408.000; Wed, 22 Apr 2020 14:50:11 +0100
From: "Piers O'Hanlon" <piers.ohanlon@bbc.co.uk>
To: HTTP Working Group <ietf-http-wg@w3.org>
Thread-Topic: New I-D: The Transport-Info HTTP Header-01
Thread-Index: AQHV8WsrvEHmXWiRikufJaSY/2tmKqiFZkYA
Date: Wed, 22 Apr 2020 13:50:10 +0000
Message-ID: <772E0D50-99CC-49BC-B39D-0CB235B63B62@bbc.co.uk>
References: <9F8F4C9C-5893-476A-BBD2-ECD46615659F@bbc.co.uk>
In-Reply-To: <9F8F4C9C-5893-476A-BBD2-ECD46615659F@bbc.co.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.161.213]
x-exclaimer-md-config: c91d45b2-6e10-4209-9543-d9970fac71b7
x-tm-as-product-ver: SMEX-12.5.0.1300-8.5.1020-24054.007
x-tm-as-result: No-9.280800-8.000000-10
x-tmase-matchedrid: byfwvk+IcRm7lpQUW6Uvz7iMC5wdwKqdwZLXS0hN8p02JxgqT664EsOp fMZV+vayd80ToizEc9B/HnCRuPeXJ4x8jP90278eL9hNDj2bBwdy4VFP6muDhrEz/84sct8sujw 9BXXmuOAJ+yennTdi3z6i5CDDnj5U3VslvqfCvOKzI1v7J4hECnzVh6U+16DkZwDIvuFZp+1McG GFFcF4CzvqjGF99ejxVwPRsVbotegWlD7t5608OAD9gX5aXd4f9mnDjfUPq56M2ehTV+imi2mCt i+JzZB13UwJgnKc1S7yBiodcotINrlepOYfePOtd7Dt86/2u/i4fXb7uySbzA5SzgJNSArLW2ni 8nJOWfyAkCtYGok49OTb/OmIigVgoayr11+eKrnmAId+2bAQwn0tCKdnhB581B0Hk1Q1KyLUZxE AlFPo8/cUt5lc1lLgoGRyAacnhaaHo7+LG2d3+8EDiyx3WHL5QqUaA8y8QsmluUc/V36avn7cGd 19dSFd
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
x-tmase-result: 10--9.280800-8.000000
x-tmase-version: SMEX-12.5.0.1300-8.5.1020-24054.007
Content-Type: text/plain; charset="utf-8"
Content-ID: <B20413496D2AFE4497CD6196833ED7B1@bbc.co.uk>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Received-SPF: pass client-ip=132.185.160.179; envelope-from=piers.ohanlon@bbc.co.uk; helo=mailout0.cwwtf.bbc.co.uk
X-W3C-Hub-Spam-Status: No, score=-7.2
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1jRFlg-0001qj-5x dbd7f32fe8da45a9432c1752d7541b42
X-Original-To: ietf-http-wg@w3.org
Subject: Re: New I-D: The Transport-Info HTTP Header-01
Archived-At: <https://www.w3.org/mid/772E0D50-99CC-49BC-B39D-0CB235B63B62@bbc.co.uk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37539
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>

Hi folks,

If you’d not had a chance to read the draft - It’s a new proposed header to convey metrics about the transport layer which may be used by a receiver. This is already happening using arbitrary headers so it would be good to standardise this practice so we can encourage compliance with an agreed set of approaches. 

This is our latest version with a couple minor tweaks since the 01 draft release:
https://bbc.github.io/draft-ohanlon-transport-info-header/draft-ohanlon-transport-info-header.html

Here’s the list of updates to the latest version:

- Added new Privacy Considerations section and updated security section (issue #5)
- Updated motivation and added use-cases section. (Issue #10)
- Updated text to describe both server and client use, and their implications. (Issue #4)
- Added text regarding the use of HTTP CONNECT. (Issue #1)
- Changed from UNIX Epoch to RFC3339 time format. (Issue #3)
- Added text to address CORS usage. (Issue #9)

Any feedback welcome.

Cheers,

Piers and James

> On 3 Mar 2020, at 14:51, Piers O'Hanlon <piers.ohanlon@bbc.co.uk> wrote:
> 
> Hi,
> 
> We have just published a new version of our draft on the Transport-Info HTTP Header. We have made various updates in the light of feedback at IETF106 and from the mail list:
> 
> Title:		The Transport-Info HTTP Header
> Name:		draft-ohanlon-transport-info-header
> Authors: 		Piers O’Hanlon, James Gruessing
> Date:		2020-03-03
> Pages:		12
> URL:            https://www.ietf.org/internet-drafts/draft-ohanlon-transport-info-header-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-ohanlon-transport-info-header/
> Htmlized:       https://tools.ietf.org/html/draft-ohanlon-transport-info-header-01
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ohanlon-transport-info-header
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ohanlon-transport-info-header-01
> 
> Abstract:
>  The Transport-Info header provides a mechanism to transmit network
>  transport related information such as current delivery rate and
>  round-trip time, from a server or a client.  This information has a
>  wide range of uses such as client monitoring and diagnostics, or
>  allowing a client to adapt to current network conditions.
> 
> Source code and issues for this draft can be found at:
>  https://github.com/bbc/draft-ohanlon-transport-info-header
> 
> Any feedback welcome.
> 
> Thanks,
> 
> Piers and James
>