1. some highly
selective internet
history

2. with apologies to the
many key people i left out

3. benjamin black
b@b3k.us

5. part 1: packet
switching

7. Paul Baran

8. RAND

9. 1960-1962

10. On Distributed
Communications

11. communications
networks

12. surviving nuclear
war

15. packet-switching

16. 1965

18. Donald Davies

19. 1962

21. Leonard
Kleinrock

22. Information Flow
in Large
Communication
Nets

23. theoretical basis
for packet-
switching

24. packet-switching

25. invented
3 times
3 places
3 reasons

26. we are on the
right track

27. 1969

28. ARPANet

29. part 2: ip

31. Vint Cerf

33. Bob Kahn

34. 1973

35. tcp/ip

36. simple & open

37. separation of
concerns

38. ip - global routing

39. tcp - reliable
delivery

40. decoupled from
hardware

41. application
presentation
COMPLEXITY
session
transport
network
data link
physical

42. independent
administrative
domains

43. federated

44. addressing
routing
policies

45. “network of
networks”

46. part 3: protocol
wars

47. meanwhile,
outside
academia...

48. explosion of
communication
demand

49. explosion of
communication
protocols

51. mainframe &
mini

52. sna
decnet

53. telco

54. x.25
frame relay
atm

55. pc

56. ip
ipx/spx
appletalk
ethernet
...

57. complexity down
the stack

58. expensive
(opex & capex)

59. upgrades mean
forklifts

60. proprietary
incompatible

61. no value-add for
protocol proliferation

62. what we needed:

63. simple & open

64. separation of
concerns

65. decoupled from
hardware

66. federated/
hierarchical

67. ip

68. now:

69. ip over *

70. ethernet
frame relay
tdm
...

71. * over ip

72. ipsec and ssl vpn
voip
web
email
...

73. part 4: partly
cloudy

74. cloud computing
2008

75. packet-switching
1968

76. it won’t take 40
years this time

77. less than 10

78. we can expect:

79. wild proliferation
of protocols

80. complexity will
move up the stack

81. ...into the apps.

82. and then...

83. rapid convergence
of protocol

84. Baran’s diagrams

87. apps for the cloud
will follow these
models

88. winning protocol
features?

89. simple & open

90. separation of
concerns

91. decoupled from
hardware

92. federated/
hierarchical

93. [this slide intentionally left blank]

94. benjamin black
b@b3k.us