1 / 9

RPR OAM

IEEE 802.17 Draft 2.4 OAM Comment Resolution San Jose, CA - August 2003 Section Editor: Glenn Parsons Technical Editors: Leon Bruckman, Gal Mor. RPR OAM. Met in 1 session (6 long hours) for: 72 comments reviewed Did not deal with most Editorials

jamesnorris
Download Presentation

RPR OAM

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 Draft 2.4OAM Comment ResolutionSan Jose, CA - August 2003Section Editor: Glenn ParsonsTechnical Editors: Leon Bruckman, Gal Mor

  2. RPR OAM • Met in 1 session (6 long hours) for: • 72 comments reviewed • Did not deal with most Editorials • Will ask for editorial license for 41 remaining editorials • Punted 2 comment to WG • Highlight of CRG resolutions • Response to IETF on MIB

  3. OAM Comments Summary • Clause 11: OAM 43 • Accepted 21 • Superseded 3 • Annex L: Echo & Flush OAM 1 • Accepted 1 • Clause 12: Management 18 • Accepted 6 • Annex D: MIB 51 • Accepted 39 • Superseded 1 • Rejected 1 All Technical done

  4. Remove oamType Remove definitions Rename performance monitoring clause Improve state table definitions Fix RPR alarms references Fix PICS Various binding editorials Improve table 11.4 Clean up figures 11.2, 11.4 & 11.5 Add table to explain figure 11.3 Move fig 11.6 to Annex L Modify Figure 11.15 Punt to WG: 578 610 Clause 11 Highlights

  5. Improve reporting period Align alarms IETF question resolution (625) Add counter for client receive/transmit broadcast Clause 12 Highlights

  6. Various binding editorials Clarify various text (intro & security) Follow IETF MIB Doctor guidance Use new High Cap TCs Disagree on clearing of Conuterxx Table D.2 improvements MIB Editor to work with editors on list of MIB variables for cross-reference to clauses Rejected 696 sysName Clause D Highlights

  7. Rejected • Clause 12 • 696 - sysName • Should provide value for sysName. • sysName is not an RPR MAC property and is not directly reported in the MIB and does not need to be reported.

  8. Punt to WG • 578 - organizationEUI • The definition of organizationEUI is not a definition, its a functional specification for a specific service primitive. • Since it can also be used by Clause 10, this is inappropriate. Redefine in clause 3 as: • 11.2.1.2 organizationEUI: A 64-bit unique value that specifies the format and meaning of other data bytes. • 610 - EUI • The term "EUI" is a shorthand for the IEEE term EUI64, of which this is an instance. • Since it can also be used by Clause 10, this is inappropriate. Redefine in clause 3 as ‘EUI64’.

  9. Ongoing review Issues • OAM Editors need some extra time at the end of the draft writing to align the MIB cross-references • IETF MIB experts will be informed of the disposition of their comments and continue to be offered to provide comments on future WG ballots

More Related