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

preferred_address TP is not normatively defined #3803

Closed
MikeBishop opened this issue Jun 30, 2020 · 1 comment · Fixed by #3807
Closed

preferred_address TP is not normatively defined #3803

MikeBishop opened this issue Jun 30, 2020 · 1 comment · Fixed by #3807
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing

Comments

@MikeBishop
Copy link
Contributor

MikeBishop commented Jun 30, 2020 •
edited by martinthomson

In section 18.2, the definition of preferred_address says:

The format of this transport parameter is shown in Figure 21.

In section 1.3, we say:

Packet and frame diagrams in this document use a bespoke format. The purpose of this format is to summarize, not define, protocol elements. Prose defines the complete semantics and details of structures.

The prose does not define the sequence of fields in this transport parameter.
@MikeBishop MikeBishop added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport labels Jun 30, 2020
@martinthomson martinthomson changed the title Disable Active Migration TP is not normatively defined preferred_address TP is not normatively defined Jul 1, 2020
martinthomson added a commit that referenced this issue Jul 1, 2020
@martinthomson
Define preferred_address
49ab8ce 
Closes #3803.
@martinthomson martinthomson mentioned this issue Jul 1, 2020
Merged
@MikeBishop
Copy link
Contributor Author

Thanks for catching that I was looking at the wrong TP definition and knowing what I meant. Eyes glaze over indeed!

@larseggert larseggert added this to Triage in Late Stage Processing via automation Jul 1, 2020
@larseggert larseggert moved this from Triage to Editorial Issues in Late Stage Processing Jul 1, 2020
Late Stage Processing automation moved this from Editorial Issues to Issue Handled Jul 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing
  
Issue Handled
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Define preferred_address quicwg/base-drafts
1 participant
@MikeBishop