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

Section 16.3.1: is a specification required for non-permanent field registrations? #950

Closed
Tracked by #914
reschke opened this issue Aug 12, 2021 · 1 comment · Fixed by #957
Closed
Tracked by #914
Assignees

Comments

@reschke
Copy link
Contributor

reschke commented Aug 12, 2021

Registration requests consist of at least the following information:
[...]
Specification document(s):
Reference to the document that specifies the field, preferably

If the registration consists of "at least" a group of information that
includes a specification document, doesn't that mean the policy is
always "Specification Required", not just for permanent registrations?

@reschke reschke changed the title Section 16.3.1 Section 16.3.1: is a specification required for non-permanent field registrations? Aug 12, 2021
@mnot mnot self-assigned this Aug 14, 2021
@mnot
Copy link
Member

mnot commented Aug 16, 2021

I think the intent here was to encourage but not require a specification for provisional registration. Will PR.

mnot added a commit that referenced this issue Aug 16, 2021
@mnot mnot linked a pull request Aug 16, 2021 that will close this issue
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.

2 participants