Skip to content

Proposal to "define" path a bit better #642

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

Merged
mirjak merged 3 commits into from
Feb 13, 2026
Merged

Proposal to "define" path a bit better #642

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2040f67
Proposal to "define" path a bit better
mirjak Feb 6, 2026
4d3e466
Merge branch 'main' into mirjak-patch-5
mirjak Feb 13, 2026
43ae3d4
Apply suggestion from @qdeconinck
mirjak Feb 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions draft-ietf-quic-multipath.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,8 +83,9 @@ Emerging networking experiments and technologies, ACM"

This document specifies a multipath extension for the QUIC protocol to
enable the simultaneous usage of multiple paths for a single connection.
It proposes a standard way to create, delete, and manage paths using identifiers.
It does not specify address discovery or management, nor
It proposes a standard way to create, delete, and manage paths.
A path is determined by an explicit path identifier in this extension.
Copy link
Contributor

@huitema huitema Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need something like that, but the words don't feel right.
How about:

It proposes to define paths using path identifiers, and defines a
standard way to create, delete, and manage paths using these identifiers.

Copy link
Collaborator Author

@mirjak mirjak Feb 9, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"proposes to define" also doesn't sounds great.

Maybe just:

It introduces the concept of explicit path identifiers that are used to define a standard way to create, delete, and manage paths.

Or even just:

It introduces explicit path identifiers to create, delete, and manage multiple paths.

?

Copy link
Contributor

@huitema huitema Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either way. The second one is more concise.

Copy link
Contributor

@qdeconinck qdeconinck Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Second version is fine.

This document does not specify address discovery or management, nor
how applications using QUIC schedule traffic over multiple paths.

--- middle
Expand All @@ -102,7 +103,8 @@ a new preferred path, and, if successful, to release resources
associated with the old path. The multipath extension specified in this document
builds on this mechanism but introduces a path identifier, or path ID,
to manage connection IDs and packet number spaces per path, enabling the use
of multiple paths simultaneously.
of multiple paths simultaneously. As such, a path in this extension is defined
by its path ID. Note that it therefore is possible to have multiple paths/paths ID for the same 4-tuple.

The connection ID of a packet binds the packet to a path ID, and therefore
to a packet number space. That means each connection ID is associated with exactly one path ID
Expand Down
Loading