Configuration/Distribution Breakout session...  1/25/96

-Discussion on Relationship of VLANs to ELANs
	-Functionallity; ELAN is "just another LAN"
	-Configuration; VLAN info may by configured into LECs.
	-Tagging, Muxing, OUIs, etc.
	-Synergy is in the configuration.

----------||--------------||---------||----------||-----------
implicit        explicitA    ExplicitB   ExplicitA    implicit

COnfiguration infor:
	Mapping info...
		i)membership criterea
		ii)mapping tag on Explicit A to Explicit B
		iii)mapping Name --> Explicit A
		            Name --> explicit B  
foil2-----------
Distribution Mechanisms
-Request/Response or "propogated"
	may need both, can't decide until we know more about config information
-Observed similarity between req/resp & LANE's config req/resp...
-LImiting Broadcase domain
	-limit by default or allow by default
	-similar to security vs connectivity
	-need dynamic "pruning" protocol to determine current necessary
         broadcast limit.
foil3---------------------------
Membershhip Criteria Mechanisms
-EG. Customers would like to say
	IP_subnet X  ---->  VLAN_Y 
   two possibilities discussed
1)Config-Response returns a
 	 mask & value
    to make against frames to determine which VLAN
2)or a "predicate based" (?) ASCII strings
	-a "language"
	-only a few or extensibility

	LOOK @ RMON-2
   complier jocks, <------> hardware eng...
foil4----------------------
Other issures.
1) Plug & Play
	-default data needed?
	-where does it come from if not fixed?
2)When is a link a "trunk"
	-configure
	-auto negotiate
	   (may be hard, especially in non point-to-point topologies)