Alternatives for Multilevel Transparent Interconnection of Lots of Links (TRILL)

Zhai, Hongjun; Perlman, Radia; Ghanwani, Anoop; Zhang, Mingui

doi:10.17487/rfc8243

Cited by 2 publications

(8 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The multiple-level feature of [IS-IS] can increase the scalability of TRILL as discussed in [RFC8243]. However, multilevel IS-IS needs some extensions to support the TRILL multilevel feature.…”

Section: Introductionmentioning

confidence: 99%

“…However, multilevel IS-IS needs some extensions to support the TRILL multilevel feature. The two most significant extensions are how TRILL switch nicknames are managed and how distribution trees are handled [RFC8243].…”

Section: Introductionmentioning

confidence: 99%

“…There are two primary alternatives to realize TRILL multilevel [RFC8243]. One approach, which is referred to as the "aggregated nickname" approach, involves assigning nicknames to the areas, and allowing nicknames to be reused in different areas by having the border TRILL switches rewrite nickname fields when entering or leaving an area.…”

Section: Introductionmentioning

confidence: 99%

“…One approach, which is referred to as the "aggregated nickname" approach, involves assigning nicknames to the areas, and allowing nicknames to be reused in different areas by having the border TRILL switches rewrite nickname fields when entering or leaving an area. For more description of the aggregated nickname approach, one can refer to [RFC8243] and [SingleN]. The other approach, which is referred to as the "unique nickname" approach, is specified in this document.…”

Section: Introductionmentioning

confidence: 99%

“…If a border RBridge is a transit node on a forwarding path, it does not learn MAC addresses of the TRILL data packets forwarded along this path. Testing and maintenance operations that originate in one area and terminate in a different area are also simplified [RFC8243]. For these reasons, the unique nickname approach might realize simpler border RBridges than the aggregated nickname approach.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique Nicknames

Zhai¹,

Perlman²,

Liu³

et al. 2018

Self Cite

View full text Add to dashboard Cite

TRILL (Transparent Interconnection of Lots of Links) routing can be extended to support multiple levels by building on the multilevel feature of IS-IS routing. Depending on how nicknames are managed, there are two primary alternatives to realize TRILL multilevel: the unique nickname approach and the aggregated nickname approach as discussed in RFC 8243. This document specifies a unique nickname approach. This approach gives unique nicknames to all TRILL switches across the multilevel TRILL campus.

show abstract

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique Nicknames

Zhai¹,

Perlman²,

Liu³

et al. 2018

Self Cite

View full text Add to dashboard Cite

show abstract

Links as a Service (LaaS): Guaranteed Tenant Isolation in the Shared Cloud

Zahavi

Shpiner

Rottenstreich

et al. 2019

IEEE J. Select. Areas Commun.

View full text Add to dashboard Cite

The most demanding tenants of shared clouds require complete isolation from their neighbors, in order to guarantee that their application performance is not affected by other tenants. Unfortunately, while shared clouds can offer an option whereby tenants obtain dedicated servers, they do not offer any network provisioning service, which would shield these tenants from network interference.In this paper, we introduce Links as a Service (LaaS), a new abstraction for cloud service that provides isolation of network links. Each tenant gets an exclusive set of links forming a virtual fat-tree, and is guaranteed to receive the exact same bandwidth and delay as if it were alone in the shared cloud. Consequently, each tenant can use the forwarding method that best fits its application. Under simple assumptions, we derive theoretical conditions for enabling LaaS without capacity over-provisioning in fat-trees. New tenants are only admitted in the network when they can be allocated hosts and links that maintain these conditions. LaaS is implementable with common network gear, tested to scale to large networks and provides full tenant isolation at the worst cost of a 10% reduction in the cloud utilization.

show abstract

Alternatives for Multilevel Transparent Interconnection of Lots of Links (TRILL)

Cited by 2 publications

References 0 publications

Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique Nicknames

Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique Nicknames

Links as a Service (LaaS): Guaranteed Tenant Isolation in the Shared Cloud

Contact Info

Product

Resources

About