1 / 9

PHY Comment Resolution in Atlanta Jan 2003 – Operating Procedure Highlights

This document outlines the resolution process for technical and editorial comments on PHY standards at the Atlanta meeting in January 2003. It covers allotted time for discussions, tracking of issues, and the need to contact the chief editor for unresolved comments. Specific highlights and summaries for PHY General, Ethernet RS, and SONET/SDH RS sections are provided. The document also addresses the key issues, such as CRC error susceptibility and signal fail I/O handling, with corresponding action items and resolutions.

ursa-schmidt
Download Presentation

PHY Comment Resolution in Atlanta Jan 2003 – Operating Procedure Highlights

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. Atlanta Jan 2003PHY Comment Resolution Harry Peng P802.17/D2.0 PHY CR

  2. Operating Procedure • Allotted 8 hr for total of • 36 technical binding • 20 technical non-binding • 60 editorial • Log tracking of issues • Highlight of discussion group summary agenda • Not accepted technical binding need to contact commenter: chief editor • Write down commenter agreed or not. • DVJ is next door P802.17/D2.0 PHY CR

  3. PHY Comments Summary • Clause 7: PHY General • Technical binding 19 • Technical non-binding 16 • Editorial 24 59 • Annex B: Ethernet RS • Technical binding 5 • Technical non-binding 1 • Editorial 8 14 • Annex C: SONET/SDH RS • Technical binding 12 • Technical non-binding 3 • Editorial 28 43 116 total P802.17/D2.0 PHY CR

  4. Clause 7 Highlights • PICS • Are specific PHY defined? • Consistent PHY around the ring • Consistent PHY at both MACDataPath interface P802.17/D2.0 PHY CR

  5. Clause B Highlights • Missing PICS • Data bit ordering • Frame format labeling: • <inter-frame><preamble><SFD><data><EFD> P802.17/D2.0 PHY CR

  6. Clause C Highlights • Missing PICS…. • Signal fail I/O • SF and SD status handling • Clarification of field names and bit ordering to be consistent to clause 3 P802.17/D2.0 PHY CR

  7. Carried Over Comments • #2308: CRC Burst error susceptibility • TA contact NS to provide presentation • #2102: wet noodle PHY • #2103:PHY requirements P802.17/D2.0 PHY CR

  8. Issues • All comments addressed • #1297 SF and SD RS punt to Protection • Attended Protection CRG comment resolved. • Punt to WG #579, 580, 582, and 583 optional length field processing in PSAP • what is the function in the MAC • Punt #2102 and 2103: PHY specification • Punt #569 to working group Uniform PHY connected to the MACDatapath • #572 Asymmetrical span punt to WG P802.17/D2.0 PHY CR

  9. All comments addressed by CRG. • Except for editorial comments • Request to accept CRG resolution • Request to grant editorial license for editorial comments • Reminder: support LAPS P802.17/D2.0 PHY CR

More Related