breakout meeting report, 96-03-13 pm LaJolla,Ca
Configuration, Distribution and Mapping
John Bartlett
 ----
(group participants:
        Floyd Backes (cameo)
        John Bartlett
        Dennis Cave
        Paul Congdon
        Milan Merhar
        Koichiro Seto
        Ayman Sinjed
        Bob Watson
        --------------
-Definitions:
        configuration:
                -definition of classiifications
                -identification of vLAN Name
                -Assignment of an ID
                        (here and/or in Distribution ?)
                -Binding of a Name, classificaion and an ID
        Distribution
                -Getting the configuration information into individual switches
        Mapping and Classification
                -Classificaion is the definition of what types of frames belong
                 in each vLASN
                        -All frames received on this port -> vLAN Blue
                        -All frames from MAC AA:BB:CC:DD:EE:F:GG: -> vLAN Red
                -Mapping is the dynamic act of determining to which
                 vLAN this frame belongs
                -------------------
Configuration:
-Configuration can be:
        -static (determined by the network)
                -human entered specification
                -built into system sofrware
                -built into switch hardware
        -dynamic (determined by end station)
                -may be interesting to allow endstations to request vLAN
                 membership via some protocol based on inherent knowledge of
                 the vLAN they would like to join
                 (ie.,"phone 1-800-555-1234, and ask for conference call IEEE-VLANS")
-Configuration Results In:
        -A definition of membership in a vLAN (a Classification)
        -A vLAN NAme (Red)
        -A vLAN ID (0x37D)
        --------------------------------
Distribution:
        -We ignored this issue
        -------------------------------
Mapping and Classifications:
        -Some possible Classifications (eek!)
                Source Port
                SA                                 Protocol / Subnet Address
                SA / DA                            Protcol / Destination Address
                SA / DA / Ethertype                     .
                Ethertype                               .
                Ethertype / Higher Level Info.          .
                DA                                      .
                Source Port / Ethertype            Protocol / Adress / Socket
                Mac LAyer Priority (FDDI, VG)
        ------------------------------------
        (cont.)
        What do we do? We could:
        -Specify a minumum requirement (i.e. port based and MAC
         based vLANs must be implemented) and let the network work
         at the lowest common denominator
        -Specify levels of capability.  Define how switches interoperate
         between different levels
        -Define only those classification parameters that are not
         embedded in the frame data (source port and media priority?),
         then let implementers determine how deep they look into the packet.
                -Could define depths as standard depths
                        -48 bits (DA)
                        -14 bytes (DA / SA / Ethertype)
                        - ???
        Do we address the issues on the PAR is we do not
        completely specify some standards?
----------------------------------------
Pictures....  vLAN Levels Problem...