datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Transparent Interconnection of Lots of Links (trill)

Group
Name: Transparent Interconnection of Lots of Links
Acronym:trill
Area:Internet Area (int)
State: Active
Charter: charter-ietf-trill-05 (Approved)
Personnel
Chairs: Jon Hudson <jon.hudson@gmail.com>
Donald Eastlake <d3e3e3@gmail.com>
Area Director: Ted Lemon <ted.lemon@nominum.com>
Secretary: Susan Hares <skh@ndzh.com>
Mailing List
Address:trill@ietf.org
To Subscribe:https://www.ietf.org/mailman/listinfo/trill
Archive:http://www.ietf.org/mail-archive/web/trill/current/maillist.html
Jabber Chat
Room Address: xmpp:trill@jabber.ietf.org
Logs: http://jabber.ietf.org/logs/trill/

Charter for Working Group

The TRILL WG has specified a solution for transparent unicast
shortest-path and multi-destination frame routing in multi-hop
networks with arbitrary topology. End stations, including Layer 3
routers, connected to TRILL switches are assumed to be IEEE 802.1Q
compliant end stations. TRILL switches may be interconnected with
multi-access or point-to-point links of arbitrary technology.

The current work of the working group is around operational support
and additional extensions and optimizations of TRILL for the
properties of the networks on which it is deployed. The TRILL WG may
also produce corrections, clarifications, and updates of existing
TRILL RFCs.

The WG will work on the following items:

(1) Following on from the TRILL OAM requirements (RFC 6905), specify a
framework and specific protocols for the handling of Operations,
Administration, and Maintenance (OAM) in networks using TRILL,
focusing on fault management and performance and preferring existing
OAM mechanisms that might apply to TRILL, such as SNMP, Netconf/Yang
and mechanisms based on the IEEE 802.1 CFM framework.

(2) Specify protocols to support "active-active" service to end
stations that are multiply connected to a TRILL campus to provide them
with flow level traffic spreading and rapid adaptation to link failure
similar to that provided by TRILL for TRILL switches.

(3) Develop, within the TRILL protocol context, protocol
specifications for broadcast/multicast (multi-destination) frame
reduction. Examples: protocol extensions supporting replacement of
broadcast/multicast by unicast where appropriate; ARP/ND (Neighbor
Discovery) reduction through extensions to the TRILL ESADI protocol.

(4) Specify protocols for TRILL over pseudowires and TRILL over IP
tunnels, for example to connect branch office TRILL switches to a
central TRILL campus over the Internet.

(5) Specify extensions to the TRILL protocol to support multi-level
routing to improve scaling and multi-topology routing to provide
different topologies for different classes or types of traffic, based
existing IS-IS multi-level and multi-topology routing facilities.

(6) Specify a reduced TRILL control plane protocol for
interconnection, with improved error isolation, between TRILL campuses
under coordinated management.

(7) Analyze the use of IS-IS security (RFC 5310) in TRILL and
determine if any work is needed to accommodate any specific TRILL
control or data plane security leveraging IS-IS security.

(8) Produce an interoperability / implementation report for TRILL.

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 extending IS-IS
routing.

Milestones

Done
Accept base protocol specification as a WG document
Done
Accept problem statement and applicability 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
Initial WG draft on VLAN Mapping (draft-ietf-trill-rbridge-vlan-mapping)
Done
Initial WG draft on trill adjacency state machine (draft-ietf-trill-adj)
Done
Submit trill adjacency state machine to IESG for publication as Proposed Standard (draft-ietf-trill-adj)
Done
Submit RBridge MIB module to IESG for publication as Proposed Standard (draft-ietf-trill-rbridge-mib)
Done
Submit TRILL Header Options to IESG for publication as Proposed Standard (draft-ietf-trill-rbridge-options)
Done
Initial WG draft on RBridge OAM (draft-bond-trill-rbridge-oam)
Done
Initial WG draft on RBridge OAM (draft-bond-trill-rbridge-oam)
Done
Submit RBridge OAM requirements document to the IESG for publication
draft-ietf-trill-oam-req
Done
Initial WG framework document on RBridge OAM
draft-ietf-trill-oam-framework
Done
Initial WG document on RBridge OAM fault management
draft-ietf-trill-oam-fm
Done
Initial WG document on RBridge OAM performance management
draft-ietf-trill-loss-delay
Dec 2013
Initial WG draft on ARP/ND optimizations
Jan 2014
Initial WG draft on TRILL over IP
Done
Submit RBridge OAM framework document to the IESG for publication
draft-ietf-trill-oam-framework
Feb 2014
Submit OAM Fault Management to IESG for Proposed Standard
Mar 2014
Submit TRILL ARP/ND optimizations to IESG for publication as Proposed Standard
Mar 2014
Initial WG draft on TRILL Implementation Report
Apr 2014
Submit Active-Active to IESG for Proposed Standard
Apr 2014
Submit OAM Performance Management to IESG for Proposed Standard
Jun 2014
Submit TRILL-over-IP to IESG for Proposed Standard
Jul 2014
Submit Multi-level TRILL to IESG for Proposed Standard
Aug 2014
Submit Multi-topology TRILL to IESG for Proposed Standard
Nov 2014
Initial WG draft on TRILL IS-IS Security
Mar 2015
Submit RBridge support of Data Center Bridging to IESG for publication as Proposed Standard (draft-eastlake-trill-rbridge-dcb)
Dec 2015
Re-charter or shut down the WG