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

*AD Section 5 #2007

Closed
mnot opened this issue Mar 16, 2022 · 2 comments
Closed

*AD Section 5 #2007

mnot opened this issue Mar 16, 2022 · 2 comments

Comments

@mnot
Copy link
Member

mnot commented Mar 16, 2022

*AD Section 5: FYI, a normative reference to RFC 5234 has been added because this document contains ABNF. See the IESG statement on "Guidelines for the Use of Formal Languages in IETF Specifications" (https://ietf.org/blog/guidelines-use-formal-languages-ietf-specifications/) - specifically "The use of a language requires a reference to the specification for that language. This reference is normative, and needs to fulfil the usual requirements for normative references (Section 7 of RFC 2026)." Please review where RFC 5234 is cited and let us know if you prefer otherwise.

Original:

   Priority is a Dictionary (Section 3.2 of [STRUCTURED-FIELDS]): 

Priority = sf-dictionary

Current:
Priority is a Dictionary (Section 3.2 of [STRUCTURED-FIELDS]).
The following is its ABNF [RFC5234]:

Priority = sf-dictionary

@LPardue
Copy link
Contributor

LPardue commented Mar 18, 2022

I think we can just remove the ABNF entirely as part of #1975, which would remove the need to ref rfc 5234

@LPardue
Copy link
Contributor

LPardue commented Apr 6, 2022

Fixed now

@LPardue LPardue closed this as completed Apr 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants