1 / 4

Requirements January 15-17, 2007 London, England

This document outlines the proposed requirements for IEEE 802.17 RPRWG 802.17c, including support for dual-station homing, sub 50msec protection, prevention of loops, load balancing techniques, multiple network topologies, and more.

rwheatley
Download Presentation

Requirements January 15-17, 2007 London, England

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. RequirementsJanuary 15-17, 2007London, England IEEE 802.17 RPRWG

  2. 802.17c Proposed Requirements • Requires no changes to non-interconnect stations on the ring (running previous versions of 802.17) to benefit from PIRC • Support rings interconnect through dual-station homing • Provide sub 50msec protection • Prevent loops in normal and protection states, and during the transient process between the states • Support for local tributary interfaces in interconnecting stations • Allow for various load balancing techniques across interconnect stations • The load balancing shall allow unicast forwarding (prevent persistent flooding) IEEE 802.17 RPRWG

  3. 802.17c Proposed Requirements (cont’) • Support multiple network topologies: • an interconnect station may belong to multiple protection groups • an interconnection station may peer with different interconnection stations for different interconnect groups • interconnect stations may occupy any relative position in a ring • PIRC will be used on networks that do not have loops aside from those created by a single PIRC group • (majority but not unanimous support) • PIRC will be used on networks that do not have loops aside from those created by PIRC groups (john’s preference) • Allow implementation of interconnecting station as two separate stations with back-to-back connections IEEE 802.17 RPRWG

  4. 802.17c Proposed Requirements (cont’) • Provide maintenance commands (e.g. manual switch-over) • Support both point-to-point and multi-point-to-multi-point services • Attend the MAC table scalability issue • controversial • Support for efficient selective MAC table flush IEEE 802.17 RPRWG

More Related