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

Resent-Date: Wed, 22 Apr 2020 13:50:26 +0000
Resent-Message-Id: <E1jRFli-0002tl-RO@lyra.w3.org>
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
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
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
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

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
>

New I-D: The Transport-Info HTTP Header-01 Piers O'Hanlon
Re: New I-D: The Transport-Info HTTP Header-01 Piers O'Hanlon