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

Sec 5.8 #97

Closed
larseggert opened this issue Aug 31, 2021 · 5 comments · Fixed by #115
Closed

Sec 5.8 #97

larseggert opened this issue Aug 31, 2021 · 5 comments · Fixed by #115
Assignees

Comments

@larseggert
Copy link
Member

@larseggert larseggert commented Aug 31, 2021

Markku Kojo said:

Sec 5.8

The MUST NOT requirement would be much better placed with other specifications in Sec 4 and would benefit from more accurate description.

@lisongxu lisongxu self-assigned this Sep 1, 2021
@bbriscoe
Copy link
Contributor

@bbriscoe bbriscoe commented Sep 15, 2021

I agree with Markku, that it would be best to move this 'MUST NOT' out of the discussion section to where it will be noticed by implementers.

@larseggert
Copy link
Member Author

@larseggert larseggert commented Sep 15, 2021

@bbriscoe @markkukojo: would one of you want to propose a PR?

@larseggert
Copy link
Member Author

@larseggert larseggert commented Sep 16, 2021

Or @lisongxu, since he self-assigned this issue?

@bbriscoe
Copy link
Contributor

@bbriscoe bbriscoe commented Sep 23, 2021

I have proposed changes in a local topic branch, but I don't have permission to push it. Is this what you were expecting me to do?

I've att'd a patch instead, in case it's useful.
app-limited.patch.txt

@larseggert
Copy link
Member Author

@larseggert larseggert commented Sep 23, 2021

@bbriscoe you create a PR by pushing your branch to a fork or this repo on GitHub, and then click the PR button.

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

Successfully merging a pull request may close this issue.

3 participants