<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>classics on Sparse Notes</title>
    <link>https://sparsenotes.com/tags/classics/</link>
    <description>Recent content in classics on Sparse Notes</description>
    <image>
      <url>https://sparsenotes.com/images/og-default.png</url>
      <link>https://sparsenotes.com/images/og-default.png</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Sat, 13 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sparsenotes.com/tags/classics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>End-to-End Arguments in System Design (1984)</title>
      <link>https://sparsenotes.com/posts/2026/06/papers/2026-06-13-end-to-end-arguments/</link>
      <pubDate>Sat, 13 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://sparsenotes.com/posts/2026/06/papers/2026-06-13-end-to-end-arguments/</guid>
      <description>Saltzer, Reed and Clark&amp;#39;s foundational argument that application-level functions usually cannot — and should not — be implemented in the network or lower layers, and why this still drives modern protocol and platform design.</description>
    </item>
    
  </channel>
</rss>
