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

Use of BCP14 language for requirements #75

Open
SpencerDawkins opened this issue Nov 15, 2022 · 5 comments
Open

Use of BCP14 language for requirements #75

SpencerDawkins opened this issue Nov 15, 2022 · 5 comments
Assignees
Labels
AfterNextMeeting Not ready to propose text until after next meeting requirement Impacts Requirements section

Comments

@SpencerDawkins
Copy link
Collaborator

@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.

@SpencerDawkins SpencerDawkins added the requirement Impacts Requirements section label Nov 15, 2022
@SpencerDawkins
Copy link
Collaborator Author

From @fluffy,

I don’t care much about this and fine if you do but just to explain … the definitions are not really very clearly defined in the requirements context. They ware written about the way a protocol would interoperate. Then we end up in arguments about if something is SHOULD or MUST and should gets uses as “nice to have” which is not what it is defined as. Finally we get into the question of if the requirements say MUST be able to do X, but the WG protocol does not do X, what does that mean for doing the pub request of the protocol draft.

@SpencerDawkins SpencerDawkins self-assigned this Jan 27, 2023
@SpencerDawkins SpencerDawkins added Deferred for now We need other issues to be resolved first labels Jan 27, 2023
@SpencerDawkins
Copy link
Collaborator Author

From @afrind in private email

Throughout the doc there is a mix of "should" and "SHOULD", which is a bit confusing.

I agree that we need to figure this out ...

@SpencerDawkins SpencerDawkins added Priority for discussion Requesting agenda time for this issue at next meeting and removed Deferred for now We need other issues to be resolved first labels May 2, 2023
@SpencerDawkins
Copy link
Collaborator Author

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.

@SpencerDawkins SpencerDawkins added IETF 118 Target PR text for IETF 118 Priority for discussion Requesting agenda time for this issue at next meeting and removed Priority for discussion Requesting agenda time for this issue at next meeting labels Sep 28, 2023
@SpencerDawkins
Copy link
Collaborator Author

From @SpencerDawkins and @fiestajetsam -

  • James still thinks normative language is helpful in this draft
  • Spencer doesn't strongly think that it's not
  • James will scan the existing BCP14 language in the draft for consistency, and propose a PR accordingly.

@SpencerDawkins SpencerDawkins removed the Priority for discussion Requesting agenda time for this issue at next meeting label Oct 17, 2023
@SpencerDawkins SpencerDawkins added AfterNextMeeting Not ready to propose text until after next meeting and removed IETF 118 Target PR text for IETF 118 labels Jan 9, 2024
@SpencerDawkins
Copy link
Collaborator Author

SpencerDawkins commented Jan 9, 2024

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AfterNextMeeting Not ready to propose text until after next meeting requirement Impacts Requirements section
Projects
None yet
Development

No branches or pull requests

2 participants