[rbridge] Starting to think about re-chartering TRILL

[Donald Eastlake]

Hi,

Wearing my co-chair hat, I think the posting to the mailing list justify
adding ARP/ND optimization  the draft Charter text. I'd also like to
generalize the "data center" item a bit since there seems to be a little
controversy at the Anaheim meeting as to what was intended. And, if we want
a Charter that will be stable for some time, I'm thinking we should add
doing an interoperability report as support for advancement to draft
standard. I've also taken a stab at some milestone dates.

So, below is a revised draft, which is still fully open for discussion,
suggestions, and comments.

Thanks,
Donald


Description of Working Group:

  The TRILL WG has specified a solution for shortest-path frame
  routing in multi-hop IEEE 802.1-compliant Ethernet networks with
  arbitrary topologies, using an existing link-state routing protocol
  technology and encapsulation with a hop count.  [Add reference to
  RFC?]

  The current work of the working group is around operational and
  deployment support for the protocol. This includes a MIB and other
  pieces needed for operations, but also extensions to handle the
  characteristics of the networks in which there is a desire to deploy
  TRILL.

  The WG will work on the following items:

  (1) A MIB for TRILL which specifies the unique pieces needed for the
  protocol while reusing what is in the IS-IS MIB and the Bridge
  MIB for pieces that are not unique to TRILL.

  (2) Support for VLAN mapping between different regions of an RBridge
  campus that will require configuration only at border RBridges.

  (3) Refinement of the TRILL Header Options feature and specification
  of an initial base set of options.

  (4) Write up how Operations and Management (OAM) will be handled in
  networks using TRILL.

  (5) Determine how TRILL will provide improved support for data
  centers such as support of the IEEE 802.1 "Data Center Bridging"
  standards.

  (6) Addition of optional support for ARP / Neighbor Discovery
  optimization.

  (7) Document interoperability test results of protocol
  implementations.

Goals and Milestones:
  Done     - Accept base protocol specification as a WG document
  Done     - Accept problem statement and applicability as a WG work
             item
  Done     - Start work with routing area WG(s) to undertake TRILL
             extensions
  Done     - Accept architecture document as a WG work item
  Done     - Accept routing protocol requirements as a WG work item
  Done     - Choose routing protocol(s) that can meet the requirements
  Done     - Submit problem statement and applicability to IESG for
             Informational RFC
  Done     - Submit base protocol specification to IEEE/IETF expert
             review
  Done     - Base protocol specification submitted to the IESG for
             publication as a Proposed Standard RFC
  Done     - First draft showing what is needed for MIB
  Jul 2010 - Re-charter or shut down the WG

NEW:
  Done     - Initial WG draft on VLAN Mapping

  Done     - Initial WG draft TRILL Header Options

  Jun 2010 - Submit VLAN Mapping to IESG for publication as Proposed
             Standard

  Oct 2010 - Submit RBridge MIB to IESG for publication as Proposed
             Standard

  Aug 2010 - Submit TRILL Header Options to IESG for publication as
             Proposed Standard

  Oct 2010 - Initial WG draft for RBridge support of Data Center
             Bridging

  Oct 2010 - Initial WG draft on RBridge OAM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.postel.org/pipermail/rbridge/attachments/20100331/620f2261/attachment.html