1 / 9

Section 2 Comment Resolution Summary Jim Mollenauer Steve Wood Dave Meyer Med Belhadj

Section 2 Comment Resolution Summary Jim Mollenauer Steve Wood Dave Meyer Med Belhadj. Summary. Total of 491 comments against Clause5/Clause8 124 / 90 Editorial 185 / 144 Technicals All technical comments dealt with (resolved or forwarded to WG) 185 on clause 5 144 on clause 8

Jimmy
Download Presentation

Section 2 Comment Resolution Summary Jim Mollenauer Steve Wood Dave Meyer Med Belhadj

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. Section 2 Comment Resolution Summary Jim MollenauerSteve WoodDave MeyerMed Belhadj 802-17-01-nnnnn, iii_xxxxx_vv

  2. Summary • Total of 491 comments against Clause5/Clause8 • 124 / 90 Editorial • 185 / 144 Technicals • All technical comments dealt with (resolved or forwarded to WG) • 185 on clause 5 • 144 on clause 8 • All editorial comments dealt with • 25 Comments Rejected, 9 Rejected-duplicate • 8 comments deferred to WG 802-17-01-nnnnn, iii_xxxxx_vv

  3. Issues Covered – Clause 5 • In profile class B description Bug • Mapping of ClassB traffic to STQ • Dynamic traffic shaping • Descriptions to be moved to clause 6 • Ringlet Selection • Improvements to the text • Adhoc to be formed to create draft text/proposals • Control Channel • Remove the text & concept. • Specify mapping of control traffic to service class/transit path • MAC Reference Model • WG asked to adopt newly proposed reference model as presented at May02 interim • Remove subclause 5.2 and fix figure 5-1. • Single TB service mapping not well described • MAC is NOT reflective 802-17-01-nnnnn, iii_xxxxx_vv

  4. Issues Covered – Clause 5 • Congestion Status conveyance via the service interface • Request/response a bad idea, should just be conveyed via indicates as received • Classes of service • Needs to be changed to 3 • Improve description of reserved service 802-17-01-nnnnn, iii_xxxxx_vv

  5. Issues Covered – Clause 8 • Frame Format Changes • New header format proposed • Remainder of formats untouched • Header, Payload, Trailer, HEC coverage explicitly defined • Request for contributions on HEC replacement with CRC32 • Change to fairness frame format deferred to WG. • Priority Handling • Text describing this should be removed from clause 8 • Bit ordering • Figure 8-1 to be reworked to clarify bit ordering and PHY responsibilities • Ringlet Selection • Text needed, adhoc to be formed • Control TTL Field questions • Questions answered, field retained • Application dependent frame formats moved to informative annex 802-17-01-nnnnn, iii_xxxxx_vv

  6. Issues Covered – Clause 8 • MAC Address definition subclause • To be removed and replaced with reference to 802-2001 • 802.17 should adopt Ethernet CRC definition 802-17-01-nnnnn, iii_xxxxx_vv

  7. Pending Resolution • Opcodes/Functions list for Control.req/ind primitive (#123) • 123, 591 etc. Small Adhoc to be formed to start defining the complete list • WG asked to refrain from further comments on this issue until September • Primitive Parameter list contents (#192, 194) • WG asked to provide a single contribution on what needs to be there and why • WG asked to refrain from commenting against draft until such time as the recommendations are adopted • New header format proposed (#539) • See RPR_hdr_flds_jl_nu.pdf on website/server • Resolves many comments – needs to be adopted by WG • Should 64 bit MAC addresses by supported in future (#775) • Claim is that RAC will object unless objective to support transparent bridging • Definition of Minimum and Maximum frame size (#178, #1139) • Needs to be defined by WG 802-17-01-nnnnn, iii_xxxxx_vv

  8. Pending Resolution • Change requested for header protection: HEC-16 to CRC-32 (#289) • David James asked to provide presentation on the cost/benefit of CRC32 over HEC16 • Straw poll 11 to 1 in favour of HEC16 • Change requested to fairness packet format (#298) • Make it another control frame type • Straw poll 17 to 1 in favour of no change 802-17-01-nnnnn, iii_xxxxx_vv

  9. Action Items – Part 1 • Contribution requested for • Describing processing of invalid frames to be included in Clause 6 • Describing definition of what an invalid frame is to be included in Clause 8 • Cost/Benefit of CRC32 as header protection (David James) • Primitive Ad-hoc • Enumerate a normative list of logical control opcodes/operands that describe client interactions with the MAC control sublayer for inclusion in clause 5 • Decide which header parameters need to be in the primitive formal list and present rationales to WG for adoption (Marc Holness) • Determine why SA included in 802.3 service primitives (Italo Busi) • Ringlet Selection Ad-hoc • Provide presentation and normative text describing how ringlet selection is performed by the MAC • Provide presentation and normative text describing how ringlet selection may be controlled by the client 802-17-01-nnnnn, iii_xxxxx_vv

More Related