<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>RequestForComments on emsenn.net</title>
    <link>https://emsenn.net/tags/requestforcomments/</link>
    <description>Recent content in RequestForComments on emsenn.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 07 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://emsenn.net/tags/requestforcomments/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>RFC and Design Document Processes</title>
      <link>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/software-engineering/domains/structured-work-paradigms/texts/rfc-and-design-document-processes/</link>
      <pubDate>Sat, 07 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/software-engineering/domains/structured-work-paradigms/texts/rfc-and-design-document-processes/</guid>
      <description>&lt;p&gt;Requests for Comments (RFCs) and design documents are written&#xA;proposals that describe a planned technical change, solicit feedback&#xA;from stakeholders, and build consensus before implementation begins.&#xA;The practice originates with the Internet Engineering Task Force&#xA;(IETF), where Steve Crocker wrote the first RFC in April 1969 to&#xA;document the ARPANET&amp;rsquo;s host software protocols. The IETF process&#xA;established the core pattern: write down the proposed change, invite&#xA;comment, iterate, and reach agreement before committing to code.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
