Chartercharter-ietf-trill-05

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.