如何撰写和提出 RFC？
我发现 IMAPv4 有一个缺点，因为它强制用户下载整个正文（文本/HTML + 附件）。
如何编写并提出 RFC 来解决该问题？
如果您之前有撰写技术文档、提案，尤其是 RFC 的经验，请分享。
I found that IMAPv4 has a shortcoming as it forces users to download whole body (text/HTML + attachments).
How to write and propose an RFC to address the issue?
Please kindly share if you had experience of previously writing technical documents, proposals, especially RFCs.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
这既是一个答案，也是一个进一步的问题。
鉴于编写 RFC“需要时间、奉献精神、艰苦的技术工作和大量的社交互动”，在做这一切之前与其他知识渊博的人讨论不是一个好主意吗？（可能是徒劳的）？
我认为正确的位置是“IETF（互联网工程任务组）邮件列表”，不是吗？
（我曾经参加过 IETF 的讨论，内容是“我怎样才能正确地写出我的名字 André？”（当时这是一个笑话，但一般项目使用 UTF8 取得了非常好的成功（这只是一种编码，但它成为了通用字符代码 ISO 10646，因为它是唯一的）））。
所以，我想知道为什么 RFC 7322 等的第一个主题。不是“如何开始初步讨论（推荐）”。
This is both an answer and a further question.
Given that writing an RFC "requires time, dedication, a hard technical work and a lot of social interactions", wouldn't a good idea be to talk about it with other knowledgeable people before doing all that, possibly in vain?
I think that the correct place to do that is on the "IETF (Internet Engineering Task Force) mailing list" isn't it?
(I once participated in IETF discussions amounting to say "How can I correctly write my name André?" (it was the joke at that time but the general project succeeded extremely well with UTF8 (which is just an encoding but that became the synonym of the universal character code ISO 10646 because it is unique))).
So, I wonder why the first topic of RFC 7322 et al. is not "how to start preliminary discussions (recommended)".
实际上有一个 RFC：RFC 7322 - RFC 样式指南。
There's actually an RFC for that: RFC 7322 - RFC Style Guide.
Jörg W Mittag 和 Darin Dimitrov 的回答完全正确，但他们忘记补充一点，编写 RFC 并使其采用是一个漫长的过程，需要时间、奉献精神、艰苦的技术工作和大量的工作。社交互动。
The responses by Jörg W Mittag and Darin Dimitrov are perfectly correct but they forget to add that writing a RFC and having it adopted is a long process which requires time, dedication, a hard technical work and a lot of social interactions.