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.

Sign up for GitHub

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

Jump to bottom

451 Editorial Feedback #102

Closed
mnot opened this issue Oct 13, 2015 · 1 comment
Closed

451 Editorial Feedback #102

mnot opened this issue Oct 13, 2015 · 1 comment
Labels
451 editorial

Comments

@mnot
Copy link
Member

mnot commented Oct 13, 2015

From Julian.

1

Feedback should occur on the ietf-http-wg@w3.org mailing list.

(This should go in the boilerplate, not the actual spec text; and yes, the RFC production center will catch it)

2

The example should use the link header field.

3

  1. Security Considerations
  1. We don't need a nested subsection here.
  2. Avoid use of lowercased BCP14 terms...

4

We'll need the IANA considerations for the new link relation as well.
@timbray
Copy link
Contributor

timbray commented Oct 25, 2015

#1 I'll leave for rfc-ed
#2 added in -03
#3.1/2 added in -03
#4 added in -03

@mnot mnot closed this as completed Nov 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
451 editorial
Milestone
No milestone
Development

No branches or pull requests
2 participants
@timbray @mnot