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.

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

QUIC Transport references #4147

Closed
gorryfair opened this issue Sep 23, 2020 · 4 comments
Closed

QUIC Transport references #4147

gorryfair opened this issue Sep 23, 2020 · 4 comments
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@gorryfair
Copy link
Contributor

Reference Formats:
(i) Some references have a citation by RFC number, some by BCP (but not all BCPs)
(ii) Some reference tags are also by name, some are by than RFC number. Is this intentional?
(iii) draft-ietf-tsvwg-datagram-plpmtud was published as RFC8899.

@martinthomson martinthomson added -transport editorial An issue that does not affect the design of the protocol; does not require consensus. labels Sep 24, 2020
@martinthomson
Copy link
Member

We've fixed the last one in #4115.

I'm comfortable with the split between RFC numbers and symbols. I generally prefer symbols, especially for citations that are made multiple times, where context might be otherwise light (did you know that [RFC7301] was ALPN? did the context provide that information?). But it can be the case that the obvious symbol isn't helpful or is too long, so for things that have just one citation the RFC number is fine, because context will establish what the citation is for. And of course there are RFCs that are more recognizable by their number (BCP 38, RFC 1918), for which a symbolic name would only serve to obscure meaning for those of us who have that shared understanding.

It's probably worth going through and ensuring that any citation that appears multiple times has a useful symbol. But consistency isn't my goal here.

@janaiyengar
Copy link
Contributor

I think that loose consistency is good enough here. We should ensure that the same RFC/name don't appear in both forms, but I don't believe that is the case (I haven't done a thorough search).

@martinthomson
Copy link
Member

Lars did, found a few, and fixed them :)

@larseggert larseggert added this to Triage in Late Stage Processing via automation Sep 24, 2020
@martinthomson
Copy link
Member

Discussed on the call; closing.

Late Stage Processing automation moved this from Triage to Issue Handled Sep 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing
  
Issue Handled
Development

No branches or pull requests

3 participants