1 / 10

Clauses 1 – 4 and Annex A

IEEE 802.17 Resilient Packet Ring Draft D0.2 Section 1 Comment Resolution May, 2002 Ottawa, Canada ra_sultan@yahoo.com. Clauses 1 – 4 and Annex A. Intro material derived from clauses Due on same date as other clauses Follows that intro always lags by one cycle (2 months)

malory
Download Presentation

Clauses 1 – 4 and Annex A

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. IEEE 802.17 Resilient Packet Ring Draft D0.2 Section 1 Comment ResolutionMay, 2002Ottawa, Canadara_sultan@yahoo.com IEEE 802.17 RPRWG

  2. Clauses 1 – 4 and Annex A • Intro material derived from clauses • Due on same date as other clauses • Follows that intro always lags by one cycle (2 months) • exceptions when material provided early to editor • Clause 1 provides an overview of the specification • Some text too detailed and will be adjusted • Reflects normative text of other clauses • Technical decisions not made in the overview IEEE 802.17 RPRWG

  3. Statistics • 50 technical non-binding • 1 rejected • 29 accepted-modified • 23 accepted • 49 technical binding • 5 referred to section 0 (and resolved) • 7 rejected • 25 accepted modified • 8 accepted • 69 editorial IEEE 802.17 RPRWG

  4. Rejected / Referred • Rejected • Disallow ‘jumbo’ frames • Incorrect comment on ‘ringlet’ figure • Mandatory wrapping • Five items referred to chief editor • Notation will be moved to clause 3 (will move for change to ‘Terms, Definitions, and Notation’ • Should, shall, etc. referenced in Style Manual IEEE 802.17 RPRWG

  5. Significant Resolved Issues • Frame size 9216 (jumbo) as specified in D02C8.1 (11) • Least cost vs. shortest path / ring selection by client or MAC (8) • Classes A0, A1, B, C from RAH (7) • Circumference, not span (4) clause? • Editor’s questions (4) no action needed • Maximum number of stations on ring (3) clause? • Remove HOL blocking reference (3) • Ringlet naming (3) (eg. CW, CCW) clause? Chief editor? • Intent is to be lossless (3) (avoid specifying conditions) IEEE 802.17 RPRWG

  6. Significant Resolved Issues • Describe multicast operation (4) • Delete reference to cut-through (4) • Delete material on reservation and provide editors’ note until defined (4) clause ? • Reject mandatory wrapping (conflicts D0.2) (1) • Remove reference to authentication/encryption (1) IEEE 802.17 RPRWG

  7. Editorial In Nature • Remove unnecessary NOTE describing ‘fairness’ (2) • Fairness algorithm doesn’t restrict traffic (1) • Not all fairness message hop-by-hop (1) • RPR header terminology included in overview when adopted in clause 8 (1) • Correction in Qtag description (2) • Remove Qtag/CID from features list as too detailed. (1) IEEE 802.17 RPRWG

  8. Editorial in Nature • Omit justification for header checksum (2) • Additions/corrections to notation (2) • Editors’ note on reference to OIF docs (1) • Add steering for multicast when available (1) • Add HEC and IOP to acronyms (understood that IOP may change) (2) IEEE 802.17 RPRWG

  9. Editorial in Nature • Picture improvements (3) • Provisioning terminology included when approved (1) • Correct description of allowed rate (1) • Clarification of delay properties (1) • Header clarifications (2) • Move notation subclause to clause 3 (1) • Add c-code reference to references (1) • Remove text regarding network layer as client (1) • ‘Looping’ replaced by ‘indefinite circulation’ (1) • Description of insert, strip, etc. (1) (will edit into overview as appropriate) IEEE 802.17 RPRWG

  10. Editorial in Nature • Specify ‘fairness’ as ‘weighted fairness’ (1) Correct definition of ‘reclaimable’ (1) • Remove incorrect reference to leaky bucket (just refer to policing) (1) • Replace description of “uncommitted and reclaimable” from approved text (1) • Remove “uncommitted and reclaimable” as too detailed for features list (1) IEEE 802.17 RPRWG

More Related