WG Action: Formed WebTransport (webtrans)
The IESG <email@example.com> Fri, 06 March 2020 17:53 UTC
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B10113A0C2D; Fri, 6 Mar 2020 09:53:48 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
From: The IESG <firstname.lastname@example.org>
To: "IETF-Announce" <email@example.com>
Subject: WG Action: Formed WebTransport (webtrans)
Cc: firstname.lastname@example.org, email@example.com, The IESG <firstname.lastname@example.org>
Content-Type: text/plain; charset="utf-8"
Date: Fri, 06 Mar 2020 09:53:48 -0800
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:firstname.lastname@example.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2020 17:53:49 -0000
A new IETF WG has been formed in the Applications and Real-Time Area. For additional information, please contact the Area Directors or the WG Chairs. WebTransport (webtrans) ----------------------------------------------------------------------- Current status: Proposed WG Chairs: Bernard Aboba <email@example.com> David Schinazi <firstname.lastname@example.org> Assigned Area Director: Barry Leiba <email@example.com> Applications and Real-Time Area Directors: Adam Roach <firstname.lastname@example.org> Alexey Melnikov <email@example.com> Barry Leiba <firstname.lastname@example.org> Mailing list: Address: email@example.com To subscribe: https://www.ietf.org/mailman/listinfo/webtransport Archive: https://mailarchive.ietf.org/arch/browse/webtransport/ Group page: https://datatracker.ietf.org/group/webtrans/ Charter: https://datatracker.ietf.org/doc/charter-ietf-webtrans/ Description of Working Group The WebTransport working group will define new client-server protocols or protocol extensions in order to support the development of the WebTransport API https://wicg.github.io/web-transport. The WebTransport working group will define an application-layer protocol or suite of application-layer protocols that support a range of simple communication methods. These must include unreliable messages (that might be limited by the path MTU), reliable messages, and ordered streams of reliable messages. Attention will be paid to the performance of the protocol, with particular attention to the protocol’s overhead and the potential for head-of-line blocking; its ability to be deployed and used reliably under different network conditions; and its ability to integrate into the Web security model. The working group will not define new transport protocols but will instead use existing protocols such as QUIC and TLS/TCP. The group will pay attention to security issues arising from the above scenarios so as to protect against creation of new modes of attack. To assist in the coordination with owners of the WebTransport API, the group will initially develop an overview document containing use cases and requirements in order to clarify the goals of the effort. The requirements will include those arising from the WebTransport API. Feedback will also be solicited at various points along the way in order to ensure the best possible match between the protocol extensions and the needs of the WebTransport API. The group will also coordinate with related working groups within the IETF, such as QUIC and HTTPBIS, as appropriate. In particular, if the working group needs any changes to or extensions of the core protocols, those issues will be raised with the relevant working groups for decisions on how best to handle them. If those decisions result in work in WebTrans, the working group last calls for that work will again be sent to the relevant working groups. The group also needs to coordinate with TAPS, as they are working on related message-based APIs and it's important to make sure there aren't conflicts and/or duplications. Milestones: Mar 2020 - Adopt a WebTransport Overview draft as a WG work item Mar 2020 - Adopt a draft defining a WebTransport protocol as a WG work item Oct 2020 - Issue WG last call of the WebTransport Overview document. Jan 2021 - Issue WG last call on the first WebTransport protocol document