IETF-94 Proceedings
Introduction | Area, Working Goup & BoF Reports | Plenaries | Training | Internet Research Task Force
Transparent Interconnection of Lots of Links (trill) (WG)
Additional information is available at tools.ietf.org/wg/trill
Chair(s):
Secretary
Routing Area Area Director(s):
Assigned Area Director
|
Recordings:
Meeting Slides:
Blue Sheets:
Internet-Drafts:
Request for Comments:
- Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement (RFC 5556) (41657 bytes)
- Routing Bridges (RBridges): Base Protocol Specification (RFC 6325) (243158 bytes)
updated by RFC 6327,RFC 6439,RFC 7357,RFC 7180,RFC 7179,RFC 7177,RFC 7172,RFC 7455,RFC 7780,RFC 7783
- Definitions of Managed Objects for Routing Bridges (RBridges) (RFC 6850) (104287 bytes)
- PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol (RFC 6361) (17705 bytes)
- Transparent Interconnection of Lots of Links (TRILL): Bidirectional Forwarding Detection (BFD) Support (RFC 7175) (24954 bytes)
- Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Support (RFC 7178) (49461 bytes)
- Routing Bridges (RBridges): Adjacency (RFC 6327) (59014 bytes)
obsoleted by RFC 7177
updates RFC6325updated by RFC 7180
- Routing Bridges (RBridges): Appointed Forwarders (RFC 6439) (36978 bytes)
updates RFC6325updated by RFC 7180
- Transparent Interconnection of Lots of Links (TRILL): Header Extension (RFC 7179) (25422 bytes)
updates RFC6325updated by RFC 7780
- Transparent Interconnection of Lots of Links (TRILL): Fine-Grained Labeling (RFC 7172) (61855 bytes)
updates RFC6325
- Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates (RFC 7180) (56276 bytes)
obsoleted by RFC 7780
updates RFC6439,RFC6327,RFC6325
- Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) Protocol (RFC 7357) (72379 bytes)
updates RFC6325
- Requirements for Operations, Administration, and Maintenance (OAM) in Transparent Interconnection of Lots of Links (TRILL) (RFC 6905) (24278 bytes)
- Directory Assistance Problem and High-Level Design Proposal (RFC 7067) (34720 bytes)
- Transparent Interconnection of Lots of Links (TRILL): Adjacency (RFC 7177) (77117 bytes)
obsoletes rfc6327 updates RFC6325updated by RFC 7780
- Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) Framework (RFC 7174) (73464 bytes)
- Transparent Interconnection of Lots of Links (TRILL): Fault Management (RFC 7455) (126153 bytes)
updates RFC6325
- Transparent Interconnection of Lots of Links (TRILL) Transport Using Pseudowires (RFC 7173) (21280 bytes)
- Loss and Delay Measurement in Transparent Interconnection of Lots of Links (TRILL) (RFC 7456) (66752 bytes)
- Problem Statement and Goals for Active-Active Connection at the Transparent Interconnection of Lots of Links (TRILL) Edge (RFC 7379) (26764 bytes)
- Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates (RFC 7780) (125037 bytes)
obsoletes rfc7180 updates RFC6325,RFC7177,RFC7179
- Transparent Interconnection of Lots of Links (TRILL) Active-Active Edge Using Multiple MAC Attachments (RFC 7782) (47989 bytes)
- Transparent Interconnection of Lots of Links (TRILL): Pseudo-Nickname for Active-Active Access (RFC 7781) (79489 bytes)
- Coordinated Multicast Trees (CMT) for Transparent Interconnection of Lots of Links (TRILL) (RFC 7783) (36970 bytes)
updates RFC6325
- Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) MIB (RFC 7784) (99471 bytes)
Charter (as of 2013-08-19):
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.