1 / 9

Topology/Protection Comment Resolution Summary

This report summarizes the resolutions and comments regarding topology and protection aspects of Clause 10 and Clause 11 from the recent discussions. It includes the outcomes of various technical and editorial comments, detailing the accepted, deferred, and rejected items. Key highlights involve the enhancement of topology database descriptions, modifications to state machines to utilize C code, and specifications around vendor-specific TLV implementations. The report encapsulates the decisions taken by the Adhoc group and provides insights into future considerations for managing MAC address duplication and protection state machine operations.

paytah
Télécharger la présentation

Topology/Protection Comment Resolution Summary

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. Topology/Protection CommentResolution Summary Jason Fan, Section Editor (jason@luminous.com) Jim Kao, Technical Editor (jkao@cisco.com)

  2. Clause 10 • 154 comments • 39 technical binding • 25 technical non-binding • 90 editorial • Adhoc group resolution (technicals) • 48 accepted, accepted/mod, accepted/dup • 6 superceded • 3 deferred (2 technical binding) • 1 rejected (1 technical binding) • 5 punted to WG (3 technical binding) • 1 punted to OAM • Editorial license requested

  3. Clause 11, Annex J • 74 comments • 14 technical binding • 19 technical non-binding • 41 editorial • Adhoc group resolution (technicals) • 27 accepted, accepted/mod, accepted/dup • 4 superceded • 1 deferred • 1 punted to OAM • Editorial license requested

  4. Issues Covered: Highlights • PICS to be added • Description of topology database to be enhanced • Station will alarm based on duplicate MAC address detection but will not intentionally drop frames • State machines to be modified to use C code • State machine to be added defining topology database updates • Topology message split into vendor-specific TLV and station TLV messages • Station weight TLV optional, not mandatory

  5. Issues Covered: Highlights • A jumbo frame preferred station on an RPR ring will behave as a non jumbo frame preferred station if any station on that ring reports that it is not jumbo frame preferred. The behavior of a non jumbo frame preferred station will be defined in Clause 6 as the following: • The stage queue processing state machine will discard any frame larger than the currently permitted MTU, which never exceeds the jumbo frame size specified in Clause 8. • The transit path has the option of either passing or discarding frames larger than the currently permitted MTU. • Wrapping will be used on an RPR ring if all stations on that ring report that they prefer wrapping

  6. Issues Covered: Highlights • In vendor-specific TLV, vendor will be identified by a 24-bit OUI and a 24-bit OUI-dependent field • TLV periodic timer default value will be changed from 100 ms to 1 second • Chief Editor is requested to provide guidance on where the conversion equations between clause-specified values and MIB defined values is specified. Likely candidates include the clause which specifies the value or the MIB clause. • In case of the failure of a station’s pass-through path, a station shall not wrap on both sides. • Additional description of how internal equipment failures may affect the externally visible behavior of a station will be provided by the PAH to the editors of the implementation guidelines annex.

  7. Issues Covered: Highlights • Wrap preferred and jumbo preferred bits will both be contained in the protection message. The station capabilities TLV will be removed. • Additional description to be added describing triggering of protection messages • Editors will provide clarification of what is needed at protection state machine running on one side of station from protection state machine running on the other side of the station • Protection state machine cleanup • Protection message modified to contain protection information from both the east and west sides of a station.

  8. Summary of Deferrals and Rejections • 1017, 2239: Deferred to PAH • Definition of MAC address duplication checks • 1137: Deferred to PAH • Definition of additional state machines for topology • 21491: Deferred to PAH • Additional overview needed for topology and protection • 21477: Rejected (commenter agrees) • Commenter believes dynamic bandwidth reservation can be handled at a later date

  9. Punts • 5 punts to WG • 988, 1011 (TB), 1067, 1087 (TB), 1106 (TB) • Punted to OAM • 1010, 1491 (TB) • Punted from MAC • 334 (input provided and punted back) • Punted from PHY • 1297 (TB) • Accepted/modified

More Related