1 / 7

Options for LFB-level multicast and related issues

Options for LFB-level multicast and related issues. Robert Haas, rha@zurich.ibm.com Nov 2, 2004. LFB Class A. FE Protocol LFB. LFB Class A. LFB Class A. LFB ID z. LFB ID 0x01. LFB ID y. LFB ID x. Attributes Events. Attributes Events. Attributes Events. PL ucast ID = {u1}

upton
Download Presentation

Options for LFB-level multicast and related issues

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Options for LFB-level multicast and related issues Robert Haas, rha@zurich.ibm.com Nov 2, 2004

  2. LFB Class A FE Protocol LFB LFB Class A LFB Class A LFB ID z LFB ID 0x01 LFB ID y LFB ID x Attributes Events Attributes Events Attributes Events PL ucast ID = {u1} PL mcast ID = {(m1, {x,y}), …} Merged: m1 = PL-level mcast ID CE FE 1 Dest. ID = m1 FE 3 FE 2

  3. LFB Class A FE Protocol LFB LFB Class A LFB Class A LFB ID z LFB ID 0x01 LFB ID x LFB ID y Attributes Events PL ucast ID = {u1} PL mcast ID = {m1, …} Virtual LFB IDs = {(i1, {x, y}), …} Attributes Events Attributes Events Split: m1= PL-level mcast IDi1 = virtual LFB instance ID CE FE 1 Dest. ID = m1 LFB ID = i1 FE 3 FE 2

  4. LFB Class A LFB Class A FE Protocol LFB LFB Class A LFB ID 0x01 LFB ID y LFB ID z LFB ID x Attributes Events Attributes Events Attributes Events PL ucast ID = {u1} Xcast: x,y= list of LFB instance IDs CE FE 1 Dest. ID = u1 LFB ID = x,y

  5. Comparison • Merged mcast • NE-wide group of LFBs is identified with a PL-level mcast ID • Does not respect strict layering between FE level and LFB level. • No LFB_select within PL message needed • Split mcast • NE-wide group of LFBs is identified via a Virtual LFB Instance ID (=MIID) • Decoupled from the PL-level mcast ID • Can address various MIIDs in the same PL message • Risk of inconsistency. Example: • sending a PL-level message to a PL mcast ID that only covers a subset of the FEs with LFBs identified with the same MIID • Xcast list • Only unicast PL messages • No prior configuration of PL mcast ID or MIIDs required. • Lists can become long if no ranges can be used (depends on the LFB Instance ID allocation)

  6. Additional issues • Splitting LFBSelect into two separate TLVs: Class and Instance ID • When addressing many same-class LFBs in the same FE, but each LFB with a different command, no need to repeat the class. • Really saving anything ?

  7. Header Batching: Multiple LFB Instances LFBClass LFBInstance Operation Path-data Operation Path-data LFBInstance Operation Path-data

More Related