All,
Here is my recollection of what we looked at that needed discussion before we resolve the comments on Wednesday. These are based on my memories, which may not be completely accurate.
General task: Are there additional common PMA functions that should be moved to 201.7, e.g. Reset? This could be added to the comment #405 rewrite.
Comment #403 - should this change be made or not, or should the text be changed in another way.
Comment #390, 391, 392, 393 - It didn't appear that there was a desire to reorganize the spec, but introductory text could be added to:
#390: 201.3 Physical Coding Sublayer (PCS) functions, high speed path (HS_PATH) There is some text, does it need to be modified?
#391: 201.4 Physical Coding Sublayer (PCS) functions, low speed path (LS_PATH) There is no text
#392: 201.5 Physical Medium Attachment (PMA) sublayer, high speed path (HS_PATH) We modified this section for comment #394, but we didn't add anything at the top level. Do we need anything?
#393: 201.6 Physical Medium Attachment (PMA) sublayer, low speed path (LS_PATH) There is some text, does it need to be modified?
Comment #217, I said I would look at this as we already have a definition of DME, but it is moving
Current proposal (relevant text): For definition of Tn, append the below text as Clause 201.4.5.1, page 106, line 18:
"201.4.5.1 Generation of symbol Tn
The bit Sn is encoded to the DME transmit symbol Tn applying the following rules:
— A “clock transition” shall always be generated at the start of each bit.
— A “data transition” in the middle of a nominal bit period shall be generated if the bit to be transmitted is a logical '1'. Otherwise, no transition shall be generated until the next bit"
My proposal to replace the above text: For definition of Tn, append the below text as Clause 201.4.5.1, page 106, line 18:
"201.4.5.1 Generation of symbol Tn
The bit Sn is encoded to the DME transmit symbol Tn as defined in 201.6.2.2.1. (moved to this location by comment #396.)
Comment #183: George and Ragnar said they would work on the wording.
Comment #370: Discussion as to whether support for PHY-D as follower is optional or mandatory.
Comment #333: Related to measuring rise and fall time of 100M DME signal. Text is needed.
Comment #368: Time to reset PMA for both ACT and TDD. Currently 100 ms, request to change to 50 ms, discussion in meeting to possibly change to 70 ms.
Comment #274: Concern over this sentence in the Suggested Remedy, should it be left as is, removed, or modified?: This implies that MAC, MAC Control sublayer, and PHY implementers conform to certain delay maxima, and that network planners and administrators conform to constraints regarding the cable topology and concatenation of devices.
Comments #209, 211, 212, and 404: Changes to Figure 201-17. There was to be an offline discussion on this.
Comment #214: Change to Figure 201-20: There was to be an offline discussion on this. (Comment #397 which modifies this figure was already accepted.)
Comment #186: We briefly discussed this. The TDD experts need to determine what their intent is for the speeds and determine if any changes are needed.
There may be others, but these are the ones I remember.
There are many other comments we didn't look at yesterday. Please review these today so that comment resolution can go quicker tomorrow.
There are 11 "late" comments added to the latest database. The TF will need to decide if they want to consider these late comments or not.
Natalie Wienckowski
In-Vehicle Networking Solutions LLC
natalie@xxxxxxxxxxxxxxxxxxx
To unsubscribe from the STDS-802-3-ISAAC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-ISAAC&A=1