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
Use of BCP14 language for requirements #75
Comments
From @fluffy,
|
From @afrind in private email
I agree that we need to figure this out ... |
I added the "Priority for discussion" tag before IETF 117, but since we didn't present this draft at IETF 117, I still don't know what the working group thinks. 🙃 Given that this issue has been stalled for a while, I agree with @fiestajetsam, that we do a brief review of existing language, and write a PR where required. At a minimum, I need to be looking for uses of lower-case BCP 14 terminology, to make sure they are intentional. |
From @SpencerDawkins and @fiestajetsam -
|
@SpencerDawkins and @fiestajetsam agree that we don't need (and don't want) normative text in this document. James will execute the existing BCP14 text and remove the reference to BCP14. |
@fluffy mentioned the use of BCP14 terms for requirements in this draft. That's allowed, but not required (:upside_down_face:), and is left to each working group. I'm entering the issue here, so we don't forget to talk about it.
When we know what the working group expects, we can do what's necessary to reflect working group consensus.
The text was updated successfully, but these errors were encountered: