trill working group
Download
Skip this Video
Download Presentation
TRILL Working Group

Loading in 2 Seconds...

play fullscreen
1 / 15

TRILL Working Group - PowerPoint PPT Presentation


  • 69 Views
  • Uploaded on

TRILL Working Group. From draft 03 to draft 04 Dinesh Dutt, Cisco Silvano Gai, Nuova Radia Perlman, Sun. Agenda. Bridge vs RBridge: Reuse/Specify SVL vs IVL ST compatibility: to which extent? Other 802.1 protocols compatibility? IS-IS TLV formats. Bridge vs RBridge: Reuse/Specify.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' TRILL Working Group' - abdul-haney


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
trill working group

TRILL Working Group

From draft 03 to draft 04

Dinesh Dutt, Cisco

Silvano Gai, Nuova

Radia Perlman, Sun

68th IETF - Prague

agenda
Agenda
  • Bridge vs RBridge: Reuse/Specify
    • SVL vs IVL
    • ST compatibility: to which extent?
    • Other 802.1 protocols compatibility?
  • IS-IS TLV formats

From draft 03 to draft 04

bridge vs rbridge reuse specify
Bridge vs RBridge: Reuse/Specify
  • Data Plane
    • What is leveraged from .1Q and what is new
  • Learning
    • Do we support IVL and SVL?
  • Control Plane
    • What versions of STP will we support
    • What about non-STP protocols such as GARP, GVRP etc.

From draft 03 to draft 04

data plane 1
Data Plane (1)

LLC

LLC

Ingress

Rules

Ingress

Rules

Port

State

Port

State

Forwarding

Process

EISS

EISS

Filtering

Database

Bridge Port TX/RX

Bridge Port TX/RX

ISS

ISS

802.n

802.n

LAN

LAN

Reuse

Specify

Not Sure

From draft 03 to draft 04

data plane 2
Data Plane (2)
  • From IEEE 802.1Q, TRILL uses:
    • Bridge port transmit and receive
    • EISS
      • It includes port-and-protocol-based VLAN classification
    • Port States
      • no new states are defined
    • Ingress Rule / Egress Rule

From draft 03 to draft 04

eiss enhanced internal sublayer service
EISS (Enhanced Internal Sublayer Service)
  • API that provides a normalized frame (independent of tagging) to the forwarding process:
    • Shall we assume that the RBridge’s interface is the same ?
    • Assumes that TRILL header encap/decap is part of forwarding process

EM_UNITDATA.indication (

destination_address,

source_address,

mac_service_data_unit,

priority,

vlan_identifier,

frame_check_sequence,

canonical_format_indicator,

rif_information (optional)

)

EM_UNITDATA.request (

destination_address,

source_address,

mac_service_data_unit,

priority,

vlan_identifier,

frame_check_sequence,

canonical_format_indicator,

rif_information (optional)

)

From draft 03 to draft 04

data plane 3
Data Plane (3)
  • TRILL specifies:
    • Forwarding Process
      • Includes Encap/Decap of shim header
    • Filtering database extension to:
      • Support TRILL encap decision
      • Identify Egress RBridge
      • Identify distribution tree for multi-destination frames
      • Identify encapsulation and address to reach Next Hop Rbridge

From draft 03 to draft 04

learning 1
Learning (1)

IS-IS

LLC

LLC

Ingress

Rules

Ingress

Rules

EISS

EISS

Filtering

Database

Bridge Port TX/RX

Bridge Port TX/RX

ISS

ISS

802.n

802.n

LAN

LAN

Reuse

Specify

Not Sure

From draft 03 to draft 04

learning 2
Learning (2)

IEEE 802.1Q distinguishes between

VID: VLAN ID

FID: Filtering ID

This allows:

IVL (Independent VLAN learning): one VID equal one FID

SVL (Shared VLAN learning): multiple VIDs map to one FID

TRILL assumes the IVL model

It announces through IS-IS {MAC Address, VID} pairs learnt locally

Does TRILL care about IVL and SVL issues or not ?

SVL has not been fully investigated

Should TRILL additionally announce FID to VID association ?

From draft 03 to draft 04

control plane 1
Control Plane (1)

IS-IS

ST (per port)

LLC

LLC

Ingress

Rules

Ingress

Rules

Port

State

+

+

Port

State

EISS

EISS

Filtering

Database

Bridge Port TX/RX

Bridge Port TX/RX

ISS

ISS

802.n

802.n

LAN

LAN

Reuse

Specify

Not Sure

From draft 03 to draft 04

control plane 2
Control Plane (2)
  • TRILL adds IS-IS
    • Need to formally specify IS-IS TLVs
  • The port state is controlled by:
    • Designated RBridge election
    • Spanning Tree
      • We need a ST per port per VLAN
      • Different from classical ST that is common to all ports
  • We need to add an algorithm to combine the ST state and the DR state into a port State

From draft 03 to draft 04

spanning trees 1
Spanning Trees (1)
  • Which styles does TRILL support:
    • STP – YES
    • RSTP – YES
    • MSTP - ???

Since the original Spanning Tree Protocol (STP) has been removed from the 2004 revision of IEEE Std 802.1D, an implementation of RSTP is required for any claim of conformance for an implementation of

IEEE Std 802.1Q-2003 that refers to the current revision of IEEE Std 802.1D unless that implementation includes the Multiple Spanning Tree Protocol (MSTP) specified in IEEE Std 802.1Q-2003. MSTP is based

on RSTP, extended to provide support for multiple spanning trees.

From draft 03 to draft 04

other restrictions of the first version of trill
Other Restrictions ofthe first version of TRILL
  • No support for:
    • GARP and its derivatives such as GVRP, GMRP
    • RIF (Routing Information)
    • CFI different from 0

From draft 03 to draft 04

arp nd
ARP/ND
  • Is ARP/ND support mandatory for an RBridge ?
  • One suggestion :
    • TRILL MUST provide mechanisms to carry this information in IS-IS, if known
    • To avoid interoperability issues
      • TRILL SHOULD NOT specify how to learn it
      • TRILL SHOULD NOT specify proxy ARP/ND behavior
    • TRILL implementation may decide to optimize ARP/ND
    • ARP/ND optimization and such can be called out in a separate draft

From draft 03 to draft 04

is is tlv formats
IS-IS TLV Formats
  • draft-ward-l2isis-01.txt has expired
  • Need to restart and finalize TLV formats

From draft 03 to draft 04

ad