1 / 7

I-TAG

I-TAG. A multiplexing tag for service instance scaling in Provider Bridged Networks Mick Seaman mick_seaman@ieee.org. I-TAG. Purpose Architecture Format Context. ITAG : Purpose. Allow upto 2 20 service instances in a PBN Particularly to address the E-LINE reqmt

zelig
Download Presentation

I-TAG

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. I-TAG A multiplexing tag forservice instance scalingin Provider Bridged Networks Mick Seaman mick_seaman@ieee.org

  2. I-TAG • Purpose • Architecture • Format • Context Service instance multiplexing

  3. ITAG : Purpose • Allow upto 220 service instances in a PBN • Particularly to address the E-LINE reqmt • Use for E-LAN, E-TREE optional/as reqd(more later on benefits of choice) • Leverages existing solutions • Complements .1Q, .1ad, .1D • GVRP, GMRP • No major new protocols required for scaling Service instance multiplexing

  4. ITAG : Architecture I-tagging systems are “end-stations” on a provider backbone or core network. The backbone can be either bridged (.1D) or virtual bridged (.1Q /.1ad) If backbone is .1Q then tagging, detagging (ingress and egress) rules are exactly as they are today Tag can be added/not added and tag value dependent on frame C-VID just as for “dual bridge model” in .1Q <<see Paul Bottorff’s slides from Monday for diagram>> Service instance multiplexing

  5. I-TAG : Format (1) • I-TAG EtherType (16 bits) • I-TAG TCI (Tag Control Info, i.e. version, flags8 bits) • PRI/DE (priority, drop eligible 4 bits) • SID (Service Instance ID – 20 bits) • User DA (Destn. Address of conveyed ‘frame’ – 48 bits) • User SA (Source Address of conveyed ‘frame’ – 48 bits) 16 + 128 bits total Service instance multiplexing

  6. I-TAG : Format (2) Service instance multiplexing

  7. I-TAG : Context Service instance multiplexing

More Related