60 likes | 189 Vues
This document discusses advances in TRILL (Transparent Interconnection of Lots of Links), focusing on multi-topology encoding and nickname expansion. Key improvements include maintaining the TRILL header integrity while enabling selective inclusion of proposed extensions. The approach allows compatibility with legacy RBridges and aims to reduce the need for Topology ID mapping. New methodologies are introduced for encoding Multi-Topology IDs and nicknames, facilitating interoperability between MT-aware and non-MT-aware clouds, and ensuring efficient communication across diverse RBridge topologies.
E N D
TRILL Multi Topology Encoding and Nickname Expansiondraft-tissa-trill-mt-encode-01 Tissa Senevirathne Naveen Nimmu Sam Aldrin
No Changes to the TRILL header • Ability to selectively include or exclude proposed extensions • Allow to interface with older RBridges • Minimize or eliminate need for mapping of Topology ID space Objective
Encode as part of the outer header • Separate EtherTypeto demarcate Multi Topology ID • Separate EtherTypeto demarcate Upper bits of nicknames Methodology
Outer Header MT-ID EthType=X EthType=Y EG-NK IG-NK TRILL Header Encoding Inner Frame
Older Rbridges belong only to a single topology • New Rbridges selectively encode the MT-ID MT Aware cloud New RB New RB Old RB Multi Topology Interoperability Non MT Aware cloud They belong only to a single topology Encode MT-ID Do not Encode MT-ID
Green field deployments use entire 24bits. • In mixed mode • Old RBridges in a different set of topologies • New RBridges in 24bitRBridge specific topologies • Old and new RBridges can not communicate, directly. Nickname Interoperability