Final Comment Resolution for D3.2

P802.3ae Draft 3.2 CommentsCl SC P L Cl SC P L00 # 352 00 # 351Dawe, Piers Agilent Dawe, Piers AgilentComment Type E Comment Status R Comment Type E Comment Status AWeird control code in table headings. e.g. Tabl e 44?1, Tabl e 52?25 and many but not all Hexadecimal notation "0x" hasn't been introduced. If it's something to do with software, this isn't others. Stops the "find" working. principally a software standard. Clauses 30, 31, 45 don't use it (e.g. "hexadecimal 89". 50 and 35 use e.g. "89 hexadecimal" 49 uses it and calls it "normal hexadecimal", hmm. 46 or 48 have SuggestedRemedyhex numbers with and without the "0x". 52.9.1, 3.5.4, 40.3, 31A use "0x" without explanation. Fix it please, O FrameMeisters! 43.3.6.2 uses it and mentions "canonical format". 23.5 has "73 hex". IEEE Standards Style Manual doesn't mention hexadecimal but says: "13.6 Abbreviations and acronyms Response Response Status CTechnical abbreviations and acronyms should be used to save time and space, but only if their REJECT. This comment does not relate to the text of the draft, only to a "Find" operation within meaning is unquestionably clear to the reader. The first use shall be spelled out, followed by the Adobe. Please forward more information to Brad Booth (bradley.booth@intel.com), so that this abbreviation or acronym itself in parentheses. Exceptions to this are approved SI units. A list of issue may be investigated outside the comment resolution process. ...