Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Address IESG comments #6

Merged
merged 5 commits into from Feb 8, 2020
Merged

Address IESG comments #6

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
c666c10
Address block from Magnus
DavidSchinazi Feb 3, 2020
032c74a
Edits from Bernard
DavidSchinazi Feb 4, 2020
b4657a6
Address Alissa's BLOCK
DavidSchinazi Feb 7, 2020
da37101
Clarify extensions
DavidSchinazi Feb 7, 2020
31ebbcf
Cleanup
aboba Feb 8, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
36 changes: 21 additions & 15 deletions charter.md
View file
Open in desktop
Expand Up @@ -21,31 +21,37 @@

The WebTransport working group will define new client-server protocols
or protocol extensions in order to support the development of the
W3C WebTransport API <https://wicg.github.io/web-transport>.

The WebTransport working group will define a protocol or suite of
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,
in particular protocol overheads and the potential for head-of-line
WebTransport API <https://quic.rocks/webtransport-api>.

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, in particular protocol overhead and the potential for head-of-line
blocking; its ability to be deployed and used reliably under different
network conditions; and the ability to integrate protocol use into
the Web security model.
network conditions; and the ability to integrate the protocol 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 ensure against creation of new
modes of attack.

To assist in the coordination with W3C, the group will
initially develop an overview document containing use cases
and requirements in order to clarify the goals of the effort.
To assist in the coordination with the 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.
This will include requirements 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 W3C WebTransport API.
work and the needs of the WebTransport API.

The group will also coordinate with other working groups within
the IETF (e.g. QUIC, HTTPBIS) as appropriate.
the IETF (e.g. QUIC, HTTPBIS, TLS) as appropriate. In particular, any changes
to these core protocols shall be discussed in their respective working groups.
The WebTransport working group may define extensions to these protocols,
but any working group last call defining such extensions shall also be sent to
the mailing list of the respective working group.

### Goals and Milestones

Expand Down