Talk:Internet Protocol Suite

To do. Please write a brief definition or description of this article at Internet Protocol Suite/Definition.

Metadata here

Howard's Signed Article

Please feel free to check the "signed articles" tab for conflict of interest. Howard C. Berkowitz 20:23, 13 July 2008 (CDT)

Howard, as far as I can tell, since July 2008, there has been an article placed on Internet Protocol Suite/Signed Articles that has not been approved or publicly commented on by any Citizendium Computers Editor. You surely know that you cannot approve your own articles. The relevant policy is found on CZ:Signed Articles. --Larry Sanger 20:07, 15 January 2009 (UTC)

Howard's "Signed Article"

There have been a variety of observations that warn youth of the problems of overindulgence in layering. Many of these observations consider the apparent mystical significance of things with seven parts, such as the Deadly Sins or Snow White's dwarven friends.

The Seven Deadly Layers

Originally presented by Howard C. Berkowitz, when representing the OSI research consortium, the Corporation for Open Systems (COS). At COS, it was axiomatic that OSI was the answer. Unfortunately, COS never definitively stated the question.

Berkowitz's theological explanation

Here is a version of my original writeup, published on USENET. Howard C. Berkowitz 20:51, 13 July 2008 (CDT)

• Newsgroups: alt.humor.best-of-usenet
• From: (Eric Henderson)
• Subject: [comp.protocols.iso] 7 deadly layers of OSI
• Date: Wed, 4 Aug 1993 23:53:08 GMT

• From: (Howard C Berkowitz)
• Subject: FAQ you were afraid to ask
• Newsgroups: comp.protocols.iso

Among the most frequent questions I'm asked in OSI teaching is "do I need to know what all the layers do?" This is especially true of management audiences, who _need_ to know the power centers. They may not know what a layer is, but they know there are seven of them and they don't want a single one to go unsupervised. :-)

Over the years, I have found a useful analogy. Educational theory suggests we should start with something that the student knows, and build from there.

Therefore, I ask management audiences to reflect not on theoretical network architecture, but on sin. Specifically, I ask them to consider the Seven Deadly Sins.

These sins have definite relevance to the OSI Reference Model. The "most popular" deadly sins are analogies for the layers most important for non-developers to know about.

Audiences think of sins in a fairly consistent way. Approximately 75% immediately think of Lust.

Lust, clearly, relates directly to the Physical Layer. It is essential to be aware of the function of the Lust Layer, for that defines how to Plug In.

Most of the remaining audience splits among Avarice and Gluttony. These also are important in OSI.

Avarice, or Greed, is often realized as the Bottom Line in business. One is closer to understanding the Tao of OSI when one realizes that it places the Bottom Line (i.e., what OSI does for real user applications programs) on Top. The top of the Avarice Layer is the Service Access Point to the Application, or Avarice, Layer.

Those members of the audience who thought first of Gluttony also have some understanding of OSI. Gluttony deals with establishing a relationship between a mouth entity and a food entity; Network deals with the next course while Transport deals with the end goal of dessert.

Users really need to know the [ISO TR 10000] functions of Application, Transport/Network (as the distinction blurs here), and Physical. International Standardized Profiles follow this model: Application is the visible part of A-, B-, or Avarice Profiles; Transport and Network define T- and U- profiles, and Physical deals with the bottom of T- and U- profiles. These four components also, for instructional purposes, nicely describe the major protocol levels of the Internet Protocol Suite: application protocols, TCP and UDP,IP, and interface protocols.

There is always one in the audience, however, who thinks of Sloth.

Sloth is a difficult sin. How does one confess it? "Bless me, I have slothed?" "Forgive me for committing sloth? How can I commit not doing something?"

Since Sloth is a sin we really have trouble talking about,and involves not doing useful things, it is a relevant analogy to the Session Layer. Both Sloth and Session are needed for theological completeness, but their relevance to the ordinary sinner or the OSI user is fairly limited.

An alternative theology

As with any theology, there are other explanations, as presented by Harris

ISO Layer	Corresponding sin	Rationale
Application	Wrath	Application is forever angry at the mess it sees below (it should point fingers?).
Presentation	Sloth	Presentation is too lazy to do anything productive itself.
Session	Lust	Session always lusted after what truly was Application functionality.
Transport	Avarice	Transport always wanted all of the end-to-end functionality (of course, it deserved it, but life ain't fair).
Network	Gluttony	Network, more precisely Connection Oriented Network, was always overweight and overbearing, the result of trying too often to eat Transport's lunch.
Data Link	Envy	Poor DLL is always starved for attention (with Asynchronous Transfer Mode (ATM), maybe it is finally feeling less neglected).
Physical	Pride	Phy roundly averted much of the controversy and nearly all of the embarrassment.

Harris' Snow White model

Harris presented an alternative to theology:

OSI layer	Dwarf	Rationale
Application	Doc	is acting as if it is in charge, but sometimes muddling its syntax.
Presentation	Sleepy	is behaving in accord with its sin of Sloth.
Session	Dopey	is confused because its charter is not very clear.
Transport	Grumpy	is irritated because Network has encroached onto its turf.
Network	Happy	is smiling for the same reason that Transport is irritated.
Data Link	Sneezy	is making loud noises in the hope of attracting attention.
Physical	Bashful	is quietly going about its work, unnoticed by the others.