Taxonomy for writing tours

	7/27/2000:   probably need to add PDU header somewhere

---------------------------------------------------------------------------
Architecture Overview
	Identify the components of this architecture (i.e. the "players"
			such as IMP, Host, TIP... or Gateway, Host....)
		and diagram an 8 host example with 2 hosts per location
	Write a brief description of each component.

Layering...  Draw a layer diagram for each component.

---------------------------------------------------------------------------
For each layer (such as TCP, IP) or component interaction(such as IMP-IMP,
					Host-Host, IMP-Host)

PDU
	Name (what term is used)
	length (fixed/variable)

Addressing 
	Definition: the "name" that is supported at this layer
	Range of Designs: 
		Hierachically organized name vs flat address space
		local name vs global name
		quantity of receivers indicated by name:
		 support for unicast, broadcast, multicast, anycast, concast
				1	all	  all in     1 in     many sdr
						 a group    a group   only need
								      to rcv 1
		Does the name indicate anything else (such as location, route)
		How to translate a name from 1 layer to a name at another layer
		Are names fixed length vs variable length

Multiplexing
	Definition: from 1 layer to the next 
	Range of Designs:
		for physical layer: synchronous
				    asynchronous
				    time division, frequency division, 
		other layers use a demultiplexing key

Fragmentation and Reassembly
	Range of Designs:
		Source fragments
			vs fragmented at any "switch" along the route
		Destination reassembles
			vs any other component reassembles
			does this protocol handle a channel that reorders

Routing Updates
	Definition
	Range of Designs:
		Flooding
		Random  (variant Hot Potato)
		Source
		Hierarchical
		Distributed

Connection (or Connection Management or separate Connection Establishment
		from Connection Teardown (or closing a connection)...???)
	Definition:  creating and tearing down a connection and ensuring
		that data from 1 connection is not received by another
		connection by synchronizing sequence numbers
	Range of Designs:
		2-way handshake vs 3-way handshake
		full-duplex vs half-duplex
		distinguishing connections via timeouts
		distinguishing connections via identifiers 
		connectionless
	Closing a Connection uniqueness
			the only one that I'm aware of is 
		the need for a timeout (they all need it, so may be trite)
		and the separation of 
			a) sending the ack of the received close vs
	        	b) sending the responding close 

Error Detection
	Definition: 
	Range of Designs:
		Parity
		Checksums such as CRC16, CRC32, ...

Error Recovery
	Definition: 
	Range of Designs:
		FEC (Forward Error Recovery)
		ARQ (aka Backward Error Recovery)
			Cumulative Ack
			Individual Ack
			Block Ack 
			sliding Window (probably here)
			Alternating bit (probably go here)
			stop and wait

Flow Control / Congestion Control
	Definition
	Range of Designs:
		Window control
		Rate control
		...
	
Security features
	Definition
	Range of Features
		authentication
		privacy
		integrity 

Compression
-----------------------------------------------------------------------------
Subnet Issues

Hardware
	Is there anything nifty to say about the hardware in this architecture?
	(maybe not, however if it was XTP yes.)

Applications...
	Range of Designs
	Design goals: i.e. what type of traffic does this network support
		Best effort
			Bulk transfer
			Interactive
		Real time
	Application Paradigm:
		client/server, publisher/subscriber

Basic Implementation issues
	buffer mgmt
	scheduling
	design