Breakout --- Mick Seaman 1/25/96
Internal/External Addressing
(Addressing model)

Perceived benefits (relative to flat addressing)
1.Simplified high speed Decapsulation
	-only look at DA Field to make decision, & not have to decide
	subsequently to look at other fields in the grand prize
2.Reduced size interior address tables.

Q1.Do the savings (2) in interior addresses amount to anything ?
   How many do we save. Are 50,000 addresses a big deal? 
   what # is significantly less than 50K?
Q2.Are switches with only trunk ports gong to be common?
   What are the target real topologies?
Q3.How much do we map to an interior address.  
   Can we assure the whole of the degap process is defined.
   Will the guys next door define a simple enough tag?
   Is a fast path/slow path viable?
Q4.Do we learn interior addresses of do we pass them around explicitly
   (e.g. using a variation of a will known well wrung out routing
   protocol, or other related protocol).
Q5.Extension to other encapsulation types -e.g. IP + Sockeets.
Q6.What happens when the topology changes - particularly if a mix
   of exterior addressed bridges & interior addressed bridges 
   attach to the same LAN.
Q7.What is the algorithm really (For interior to Exterior Bridging).
Q8.MAC(n) instead of MAC(n,m) please. Is there any (forgotten)
   Reason for (n,m).

Action: Understand the Algorithm and work with Backward 
         compatability case.

	Mcast addressing considerations...  IPV6 ???  TR ???