Presentation by Floyd Backes

   ---------------------
Foil1
An Architectural Framework for VLAN Standardization in IEEE 802
Floyd Backes, 3COM	
Norm Finn, Cisco
24-Jan-1996
Milpitas, CA
   ---------------------
Foil2
Discussion So Far
-Requirements and difinitions
-Some specific aspects of VLANS:
	-Switch to switch protocol
	-Tagging/encapsulation
	-Mapping
	-Configuration
	-Protocols
	-etc.
There is a need to agree on an overall framework in which work
may proceed...
   ----------------------
Foil3
3 Level Framework Proposed
-Configuration
-Distribution/Resolution
-Mapping
	(picture)
Configuration          ---MIBs
Distribution/Resolution---VLMP ---Req/Resp
Mapping              ---Explicit Tagging ---Implicit Tagging ---Other stuff
   ---------------------
Foil4
Configuration
-How does the configuration get specified in the first place?
   SNMP manages a MIB in a database
	"in a "server" or
	"Distributed" or
	"whatever"
-Globally Significant names
	-ASCII names
	-propagated between switches
-Globally significant names are static (modulo operator input)
   ---------------------
Foil5
Distribution
-"Middleware",i.e."How do I know what VLAN this packet belongs to?
  -Possibilities:
	-VLMP-like protocol distributes VLAN associations
	-Request/Response Protocol requests a specific association
-If encapsulation used, taggings must be negotiated
-etc.
   -----------------------
Foil6
More on Configuration and Distribution
  There is and additional dimention to these two
  layers on the architecture ... (Config & Distr)
picture:

All information      <---Extent of Information--->Some information
Everywhere           <---  Distribution       --->in a few places
   .                                                    .
   .                                                    . 
   .                                                    . 
General              <---Range of             --->Request
Distribution         <---Solutions            --->Response
Mechanism                                         Protocol
   ----------------------
Foil7 
Mapping
-Tagging, in some agreed form
-Source Address to VLAN mapping
-Protocol to VLAN mapping
-etc.
   ---------------------
Foil8
Things to do (1)
-We have to think about multiple media types up front -
  can't leave this until later
	-For example, implications of source routing in token Ring
 	 environments can affect-
		Addressing
		encapsulation formats
		naming convections
   ----------------
Foil9
Things to do (2)
Need to construct complete service diagrams (like the
ones in 802.1h) to ensure that you can't generate new
problems by shoving two services together.
  .. picture..

What goes in, comes out!
csma/cd  ... fddi/tr

network: Encapsulation, mapping, VLMP, Req./Resp
   ---------------
Foil10
Things to do (3)
-Ensure that any VLAN has a single
representation on any segement, so that it is
possible to determine the service to be
represented - In other words, say the user says...

"I want these two things on the same VLAN".

This may imply two different services depending on
which "end" you look at it from, two different
mechanisms may be assumed.  What constitutes the
interworking unit between these two services and
where does it sit?
---------------------------end of presentation----