A Design Team for Layer Two Switching

["Adrian Farrel" <adrian@olddog.co.uk>]

Hi,

In Minneapolis there was some discussion about solutions for layer two
switching and in particular for GMPLS control of Ethernet devices.

After much discussion backwards and forwards I am setting up a team to
develop a framework and the basic requirements. Their charter (which
limits their scope quite tightly) is found below. Please help them and
look forward to reviewing their output in Paris.

Thanks,
Adrian

========
Charter for the CCAMP Layer 2 Ethernet Design Team

    GMPLS signaling and routing is applicable to Layer 2.
    However, up to now, very little attention has been given to the
    control of Ethernet switches using GMPLS protocols.

    This Design Team is chartered to start the work of applying
    GMPLS to Ethernet devices by developing a framework draft that
    covers possible deployment scenarios, identifies the consequent
    requirements, and highlights possible interactions with other
    SDOs.

    The sole objective of the Design Team is to produce this
    framework draft which should be around 10 pages in length.
    Solutions work is out of scope at this time.

    The draft will be ready for discussion at the Paris IETF.

    The Design Team members are as follows...

    - Dimitri Papadimitriou (Team Lead and Editor)
      Dimitri.Papadimitriou@alcatel.be
    - Jaihyung Cho (Co-Editor)
      jaihyung@etri.re.kr
    - Loa Andersson
      loa@pi.se
    - Arthi Ayyangar
      arthi@juniper.net
    - Anders Gavler
      Anders.Gavler@acreo.se
    - Martin Vigoureux
      Martin.Vigoureux@alcatel.fr
    - Deborah Brungard
      dbrungard@att.com
    - Simon Delord
      simon.delord@francetelecom.com
    - Avri Doria
      avri@psg.com
    - Tomohiro Otani
      otani@kddilabs.jp
    - Jean-Louis Le Roux
      jeanlouis.leroux@francetelecom.com

Standard design team disclaimer: this design team has no special
status in the CCAMP WG. Any document produced is subject to the usual WG
procedures. Individuals are encouraged to interact with the design team,
to offer suggestions and, if they feel so inclined, to submit their own
drafts.

===

Suggested contents of framework I-D (fully open for revision)
- half page introduction
   - what does GMPLS currently do
   - L2 switching is in scope
   - Ethernet not previously examined
   - state that MPLS over Ethernet is not the same thing
- half page overview of the objectives
- four pages of figures and deployment scenarios
- two pages of requirements (just brief statements)
   - which nodes participate in signaling and routing?
   - what needs to be labeled?
       - don't get sucked into *how* to label anything
   - any scoping requirements for labels
   - is link discovery needed?
   - what needs to be advertised in routing?
   - etc.
   Each requirement should note which scenarios do/don't
   depend on the requirement
- half page to reference other SDOs (I think IEEE and ITU-T SG15)
- half page on security implications of control of Ethernet

===