About: TRILL (computing) is a research topic. Over the lifetime, 276 publications have been published within this topic receiving 2346 citations. The topic is also known as: Transparent Interconnect of Lots of Links & TRansparent Interconnection of Lots of Links.
TL;DR: This document assumes that solutions would not address issues of scalability beyond that of existing bridged (802.1) links, but that a solution would be backward compatible with 802.1, including hubs, bridges, and their existing plug-and-play capabilities.
Abstract: Current Ethernet (802.1) link layers use spanning tree protocols that
have a number of challenges. These protocols need to strictly avoid
loops, even temporary ones, during route propagation, because of the
lack of header loop detection support. Routing tends not to take full
advantage of alternate paths, or even non-overlapping pairwise paths
(in the case of spanning trees). This document addresses these
concerns and suggests that they can be addressed by applying modern
network layer routing protocols at the link layer. This document
assumes that solutions would not address issues of scalability beyond
that of existing bridged (802.1) links, but that a solution would be
backward compatible with 802.1, including hubs, bridges, and their
existing plug-and-play capabilities.
TL;DR: In this paper, the authors present a switch that includes a first port configured to receive Transparent Interconnection of Lots of Links (TRILL) traffic, a second port configurable to receive Fiber Channel (FC) traffic and a third port configured for transmit received TRILL or FC traffic based on a Fiber Channel over IP (FCIP) protocol.
Abstract: One embodiment of the present invention provides a switch. The switch includes a first port configured to receive Transparent Interconnection of Lots of Links (TRILL) traffic; a second port configured to receive Fiber Channel (FC) traffic; and a third port configured to transmit received TRILL or FC traffic based on a Fiber Channel over IP (FCIP) protocol.
TL;DR: In this paper, an apparatus for forwarding an FCoE data frame into an Ethernet network comprising a processor configured to receive a data frame on a input port, obtain a first destination address and a virtual local area network identifier (VID), determine whether the first destination addresses and the VID matches an entry within a forwarding table, construct a key, and forward the data frame as an outgoing data frame via an output port when the key matches a rule that permits forwarding the dataframe.
Abstract: An apparatus for forwarding an Fiber Channel over Ethernet (FCoE) data frame into an Ethernet network comprising a processor configured to receive a data frame on a input port, obtain a first destination address and a virtual local area network identifier (VID), determine whether the first destination address and the VID matches an entry within a forwarding table, construct a key when the first destination address and VID matches the entry and the data frame is a FCoE frame, and forward the data frame as an outgoing data frame via an output port when the key matches a rule that permits forwarding the data frame.
TL;DR: In this paper, an IP header processor identifies a destination IP address in a packet encapsulated with an inner Ethernet header, a TRILL header, and an outer Ethernet header and a forwarding mechanism.
Abstract: One embodiment of the present invention provides a switch. The switch includes an IP header processor and a forwarding mechanism. The IP header processor identifies a destination IP address in a packet encapsulated with an inner Ethernet header, a TRILL header, and an outer Ethernet header. The forwarding mechanism determines an output port and constructs a new header for the packet based on the destination IP address. The switch also includes a packet processor which determines whether (1) an inner destination media access control (MAC) address corresponds to a local MAC address assigned to the switch; (2) a destination RBridge identifier corresponds to a local RBridge identifier assigned to the switch; and (3) an outer destination MAC address corresponds to the local MAC address.
TL;DR: In this paper, the authors describe an ingress switch that uses a QoS mapping mechanism to map a first set of QoS bits in a packet received from a customer to a second set for use in a Transparent Interconnection of Lots of Links (TRILL) packet which encapsulates the packet.
Abstract: Systems and techniques for processing and/or forwarding packets are described. An ingress switch can use a QoS mapping mechanism to map a first set of Quality of Service (QoS) bits in a packet received from a customer to a second set of QoS bits for use in a Transparent Interconnection of Lots of Links (TRILL) packet which encapsulates the packet. The first set of QoS bits can be different from the second set of QoS bits. The TRILL packet can be processed and/or forwarded in the network based on the second set of QoS bits. At the egress switch, the TRILL packet can be decapsulated and the original packet with the original QoS bits (or QoS bits that are different from the original QoS bits) can be forwarded to the customer's network. In this manner, some embodiments of the present invention can preserve the QoS bits across a TRILL network.