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

Reserving connection options #285

Closed
mnot opened this issue Feb 2, 2020 · 0 comments · Fixed by #315
Closed

Reserving connection options #285

mnot opened this issue Feb 2, 2020 · 0 comments · Fixed by #315

Comments

@mnot
Copy link
Member

mnot commented Feb 2, 2020

   When defining new connection options, specification authors ought to survey
   existing field names and ensure that the new connection option does
   not share the same name as an already deployed field.
   Defining a new connection option essentially reserves that potential
   field name for carrying additional information related to the
   connection option, since it would be unwise for senders to use
   that field name for anything else.

We should explicitly tell them to reserve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

1 participant