Transparent Interconnection of Lots of Links (trill) ---------------------------------------------------- Charter Last Modified: 2010-04-12 Current Status: Active Working Group Chair(s): Erik Nordmark Donald Eastlake 3rd Internet Area Director(s): Ralph Droms Jari Arkko Internet Area Advisor: Ralph Droms Mailing Lists: General Discussion:rbridge@postel.org To Subscribe: http://www.postel.org/mailman/listinfo/rbridge Archive: http://www.postel.org/pipermail/rbridge 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. The current work of the working group is around operational and deployment support for the protocol. This includes a MIB module and other pieces needed for operations, but also additional ways to extend and optimize TRILL for the properties of the networks on which it is deployed. The WG will work on the following items: (1) A MIB module for TRILL which specifies the unique pieces needed for the protocol while reusing what is in the IS-IS MIB module and the IEEE 802.1 MIB modules for pieces that are not unique to TRILL (draft-ietf-trill-rbridge-mib). (2) Development, within the TRILL protocol context, of requirements and specifications for broadcast/multicast (multi-destination) frame reduction; e.g., ARP/ND (Neighbor Discovery) reduction through use of the TRILL ESADI protocol. (3) Refinement of TRILL Header Options, as initially defined in draft-ietf-trill-rbridge-protocol and specification of an initial base set of options (draft-ietf-trill-rbridge-options). (4) Provide documentation for the handling of Operations, Administration, and Maintenance (OAM) in networks using TRILL. Any documentation will take into consideration any existing OAM mechanisms that might apply to TRILL. (5) Publish an implementation report for TRILL. (6) Analyze use of IS-IS security in TRILL and determine if any work is needed to accommodate the specific application of IS-IS security in TRILL forwarding. (7) Publish a description of the adjacency state machine in TRILL (draft-ietf-trill-adj). The trill WG will continue to work with other IETF working groups such as the isis WG, and SDO groups such as IEEE 802.1 through established inter-WG relationships and SDO liaison processes, including early and WG last call review by the isis WG of documents modifying the IS-IS protocol. The trill WG will have a Routing Area Advisor for advice on the IS-IS protocol and liaison with the isis WG. 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 Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- May 2006 Mar 2010 Rbridges: Base Protocol Specification Jan 2009 Oct 2010 RBridges: Campus VLAN and Priority Regions Dec 2009 Oct 2010 RBridges: TRILL Header Options Mar 2010 Sep 2010 Definitions of Managed Objects for RBridges Dec 2010 Feb 2011 RBridges: Adjacency Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC5556 I May 2009 Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement