TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

RFC 1984 status updated to “best current practice”

3 点作者 ending超过 9 年前

1 comment

ending超过 9 年前
The rationale for this decision is discussed here: <a href="https:&#x2F;&#x2F;mailarchive.ietf.org&#x2F;arch&#x2F;msg&#x2F;ietf-announce&#x2F;FXpz3-UELhF7S5kBxXvTrRDXSgs" rel="nofollow">https:&#x2F;&#x2F;mailarchive.ietf.org&#x2F;arch&#x2F;msg&#x2F;ietf-announce&#x2F;FXpz3-UE...</a><p>An excerpt:<p>&quot;For both symbolic reasons (that the technical position then is the technical position now) and to better ensure that IETF specifications reflect the spirit of RFC1984, a number of participants in the discussion felt it would be advantageous to recognize the substantive content of RFC1984 as a BCP.&quot;<p>Also, the RFC number is worth emphasizing.