InterChassis Communication Protocol for L 2 VPN PE

  • Slides: 9
Download presentation
Inter-Chassis Communication Protocol for L 2 VPN PE Redundancy draft-ietf-pwe 3 -iccp-01. txt Luca

Inter-Chassis Communication Protocol for L 2 VPN PE Redundancy draft-ietf-pwe 3 -iccp-01. txt Luca Martini, Chris Metz (Cisco) lmartini@cisco. com Samer. Salam (Cisco)ssalam@cisco. com Ali Sajassi (Cisco) sajassi@cisco. com Matthew Bocci (Alcatel-Lucent) Matthew. Bocci@alcatel-lucent. com Satoru Matsushima (Softbank) satoru. matsushima@tm. softbank. co. jp Thomas D. Nadeau (BT) tom. nadeau@bt. com

Introduce ROs and ROID • Need an abstract way of referencing protected entities (VLAN,

Introduce ROs and ROID • Need an abstract way of referencing protected entities (VLAN, port, BD, etc…) across PEs. Redundant Objects defined for this purpose • ROID is 64 -bit opaque RO identifier, must match between PEs in the same RG. RO = Redundant Object ROID = Redundant Object Identifier draft-ietf-pwe 3 -iccp 01. txt, IETF 75, Stockholm 2

Limit RG Application Data message to 1 application per message • Enhances performance of

Limit RG Application Data message to 1 application per message • Enhances performance of ICCP & provides better ICC / Application layer modularity (minimize memory copies, and allows passing entire memory buffer from ICCP to client application) • Also to address complexity with NAK handling. RG = Redundancy Group draft-ietf-pwe 3 -iccp 01. txt, IETF 75, Stockholm 3

m. LACP: Port Config TLV • Change so this TLV carries the ‘administrative’ LACP

m. LACP: Port Config TLV • Change so this TLV carries the ‘administrative’ LACP port priority only. • Have the ‘operational’ port priority advertised in a new dedicated TLV: m. LACP Port Priority TLV draft-ietf-pwe 3 -iccp 01. txt, IETF 75, Stockholm 4

m. LACP Separate TLVs for Aggregators vs. Member Ports • Separate out the port

m. LACP Separate TLVs for Aggregators vs. Member Ports • Separate out the port state TLV (and config TLV) for Aggregators (i. e. bundles) vs. for member ports. • For bundle config TLV: add partner key and system priority • Config TLVs: – Aggregator: ROID, Aggregator ID, mac address, key, priority, flags, aggregator name – Port: number, mac address, key, priority, flags, interface name, speed • State TLVs – Aggregator: partner system ID, partner key, aggregator id, actor key, port state – Port: partner (sys ID, sys priority, port #, port priority, key, state), actor (state, port #, port priority, key), selected, port state, aggregator ID draft-ietf-pwe 3 -iccp 01. txt, IETF 75, Stockholm 5

m. LACP Add new sync TLVs • Provide a way for a PE to

m. LACP Add new sync TLVs • Provide a way for a PE to solicit m. LACP data from its peer. • 3 TLVs: – Sync Request – Sync Reply Start – Sync Reply End draft-ietf-pwe 3 -iccp 01. txt, IETF 75, Stockholm 6

m. LACP: Communicate the ‘SELECTED' • This is needed to distinguish the LACP WAITING

m. LACP: Communicate the ‘SELECTED' • This is needed to distinguish the LACP WAITING and DETACHED states (useful if PEs have different Selection Logic) • Added to the m. LACP Port State TLV draft-ietf-pwe 3 -iccp 01. txt, IETF 75, Stockholm 7

m. LACP: Communicate link BW • Added this to the Port Config TLV •

m. LACP: Communicate link BW • Added this to the Port Config TLV • Same as the if. High. Speed object of IF-MIB [RFC 2863] draft-ietf-pwe 3 -iccp 01. txt, IETF 75, Stockholm 8

Next ? • Comments ? draft-ietf-pwe 3 -iccp 01. txt, IETF 75, Stockholm 9

Next ? • Comments ? draft-ietf-pwe 3 -iccp 01. txt, IETF 75, Stockholm 9