Browse Prior Art Database

Some Internet Architectural Guidelines and Philosophy (RFC3439)

IP.com Disclosure Number: IPCOM000010524D
Original Publication Date: 2002-Dec-01
Included in the Prior Art Database: 2002-Dec-11
Document File: 29 page(s) / 70K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Bush: AUTHOR [+2]

Abstract

This document extends RFC 1958 by outlining some of the philosophical guidelines to which architects and designers of Internet backbone networks should adhere. We describe the Simplicity Principle, which states that complexity is the primary mechanism that impedes efficient scaling, and discuss its implications on the architecture, design and engineering issues found in large scale Internet backbones.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Network Working Group                                            R. Bush

Request for Comments: 3439                                      D. Meyer

Updates: 1958                                              December 2002

Category: Informational

         Some Internet Architectural Guidelines and Philosophy

Status of this Memo

   This memo provides information for the Internet community.  It does

   not specify an Internet standard of any kind.  Distribution of this

   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   This document extends RFC 1958 by outlining some of the philosophical

   guidelines to which architects and designers of Internet backbone

   networks should adhere.  We describe the Simplicity Principle, which

   states that complexity is the primary mechanism that impedes

   efficient scaling, and discuss its implications on the architecture,

   design and engineering issues found in large scale Internet

   backbones.

Table of Contents

   1. Introduction . . . . . . . . . . . . . . . . . . . . . . . .  2

   2. Large Systems and The Simplicity Principle . . . . . . . . .  3

   2.1. The End-to-End Argument and Simplicity   . . . . . . . . .  3

   2.2. Non-linearity and Network Complexity   . . . . . . . . . .  3

   2.2.1. The Amplification Principle. . . . . . . . . . . . . . .  4

   2.2.2. The Coupling Principle . . . . . . . . . . . . . . . . .  5

   2.3. Complexity lesson from voice. . . . .  . . . . . . . . . .  6

   2.4. Upgrade cost of complexity. . . . . .  . . . . . . . . . .  7

   3. Layering Considered Harmful. . . . . . . . . . . . . . . . .  7

   3.1. Optimization Considered Harmful . . .  . . . . . . . . . .  8

   3.2. Feature Richness Considered Harmful .  . . . . . . . . . .  9

   3.3. Evolution of Transport Efficiency for IP.  . . . . . . . .  9

   3.4. Convergence Layering. . . . . . . . . . .  . . . . . . . .  9

   3.4.1. Note on Transport Protocol Layering. . . . . . . . . . . 11

   3.5. Second Order Effects   . . . . . . . . . . . . . . . . . . 11

   3.6. Instantiating the EOSL Model with IP   . . . . . . . . . . 12

   4. Avoid the Universal Interworking Function. . . . . . . . . . 12

   4.1. Avoid Control Plane Interworking . . . . . . . . . . . . . 13

Bush, et. al.                Informational                      [Page 1]

RFC 3439           Internet Architectural Guidelines       December 2002

   5. Packet versus Circuit Switching: Fundamental Differences . . 13

   5.1. Is PS is inherently more efficient than CS?  . . . . . . . 13

   5.2. Is PS simpler than CS? . . . . . . . . . . . . . . . . . . 14

   5.2.1. Software/Firmware Complexity . . . . . . . . . . . . . . 15

   5.2.2. Macro Operation Complexity . . . . . . . . . . . . . . ....