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

use terms header field and header section #101

Closed
brong opened this issue Jul 17, 2017 · 2 comments
Closed

use terms header field and header section #101

brong opened this issue Jul 17, 2017 · 2 comments
Assignees
@neilj

Comments

@brong
Copy link
Member

brong commented Jul 17, 2017

From the mailing list:

From: Stan Kalisch stan@glyphein.mailforce.net
Message-Id: 8B35955B-C77A-44FE-9CDB-872FBF6C3B10@glyphein.mailforce.net

Minor point: should not the terms "header field" and "header section" be used as in RFC 5322?

Stan
@neilj
Copy link
Member

neilj commented Sep 4, 2017

I can't find "header field" anywhere in the spec anymore, so this is no longer relevant.

@neilj neilj closed this as completed Sep 4, 2017
@skalisch
Copy link

skalisch commented Sep 9, 2017

A number of RFCs subsequent to RFC 5322 hew to these terms as conventions, presumably for a clarity of syntax across specs. In any event, whatever you decide, you should also resolve the usage of these kinds of terms in the implementation guide at http://jmap.io/server.html.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@neilj neilj

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@brong @neilj @skalisch