IEEE P802.3ae D4.0 Comment Resolution
80 Pages
English
Downloading requires you to have access to the YouScribe library
Learn all about the services we offer

IEEE P802.3ae D4.0 Comment Resolution

-

Downloading requires you to have access to the YouScribe library
Learn all about the services we offer
80 Pages
English

Description

P802.3ae Draft 4.0 CommentsCl SC P L Cl SC P L00 # 148 00 # 324Booth, Brad Intel Maus, Kyle AITGComment Type E Comment Status A Comment Type E Comment Status RAs per recommendation of IEEE editor: equation numbering should include clause number. For Throughout the document there are instances of the phrase "collision detect signal." The phrase example, in Clause 44, equation (1) should be (44-1). "collision detect" should be hyphenated, as it is an adjectival phrase modifying the noun "signal."SuggestedRemedy SuggestedRemedyFix.Response Response Status C Response Response Status CACCEPT. REJECT. Cl 00 SC P L # This terminology has been used in 802.3 for many years and has become the accepted 328terminology.Maus, Kyle AITGCl 00 SC P L #Comment Type E Comment Status R 147Booth, Brad IntelThroughout the document there are instances of the phrase "network management functions." The phrase "network management" should be hyphenated, as it is an adjectival phrase Comment Type E Comment Status Amodifying the noun "functions."As per recommendation of IEEE editor: footnotes in tables should be lowercase letters, not SuggestedRemedy numbers.Put a hyphen between "network" and "management." SuggestedRemedyResponse Response Status C Change.REJECT. Response Response Status CACCEPT. This terminology has been used in 802.3 for many years and has become the accepted terminology.Cl 00 SC P L # 49000Cl 00 SC P L # 327 Pat ThalerMaus, Kyle AITGComment Type ...

Subjects

Informations

Published by
Reads 46
Language English

Exrait

P802.3ae Draft 4.0 Comments Cl00SC P L# 14Cl00 LSC P# 32 Booth, Brad Intel Maus, Kyle AITG Comment TypeEComment StatusAComment TypeEComment StatusR As per recommendation of IEEE editor: equation numbering should include clause number. For Throu example, in Clause 44, equation (1) should be (44-1). "collision detect" should be hyphenated, as it is an adjectival phrase modifying the noun "signal." SuggestedRemedy SuggestedRemedy Fix. Response Response StatusC ACCEPT. Cl00SC P L# 32 Maus, Kyle AITG Comment TypeEComment StatusR Throughout the document there are instances of the phrase "network management functions." The phrase "network management" should be hyphenated, as it is an adjectival phrase modifying the noun "functions." SuggestedRemedy Put a hyphen between "network" and "management." Response Response StatusC REJECT. This terminology has been used in 802.3 for many years and has become the accepted terminology. Cl00 LSC P# 32 Maus, Kyle AITG Comment TypeEComment StatusR Throughout the document there are instances of the phrase "half duplex operation." The phrase "half duplex" should be hyphenated, as it is an adjectival phrase modifying the noun "operation." SuggestedRemedy Put a hyphen between "half" and "duplex." Response Response StatusC REJECT. This terminology has been used in 802.3 for many years and has become the accepted terminology.
Response Response StatusC REJECT. This terminology has been used in 802.3 for many years and has become the accepted terminology. Cl00SC P L# 14 Booth, Brad Intel Comment TypeEComment StatusA As per recommendation of IEEE editor: footnotes in tables should be lowercase letters, not numbers. SuggestedRemedy Change. Response Response StatusC ACCEPT. Cl00 LSC P# 4900 Pat Thaler Comment TypeEComment StatusA Existing 802.3 uses octet almost exclusively. (There are 4 instances of byte all of which look like errors in consistancy.) 802.3ae uses a mix of byte and octet often with both appearing on the same page or in the same paragraph. SuggestedRemedy All instnaces of byte should be converted to octet unless there is a suitable reason to retain byte (e.g. if it is part of a name from another standard). Response Response StatusC ACCEPT IN PRINCIPLE. Replace byte with code-group, octet or symbol where appropriate.
TYPE: TR/technical required T/technical E/editorial COMMENT STATUS: D/dispatched A/accepted R/rejected SORT ORDER: Clause, Page, Line, Subclause Page 1 of 80 RESPONSE STATUS: O/open W/written C/closed U/unsatisfied Z/withdrawnCl00SC
P802.3ae Draft 4.0 Comments Cl00SC P L# 33Cl00SC P L# 14 Maus, Kyle AITG Booth, Brad Intel Comment TypeEComment StatusRComment TypeEComment StatusA Throughout the document there are instances of the phrase "media access mechanism." The As per IEEE editor recommendation: copyright year should be 2002. "pmhreacshea "nimsemd.i"a access" should be hyphenated, as it is an adjectival phrase modifying the noun SuggestedRemedy SuggestedRemedyUpdate. "Response Response StatusC Put a hyphen between "media" and access." Response Response StatusCACCEPT. REJECT.Cl00SC P L# 33 This terminology has been used in 802.3 for many years and has become the accepted Jay Warrior Agilent terminology.Comment TypeTRComment StatusR Note: This is a re-submission to ensure that this is recognized as a “technical required” Cl00SC P L# 332 syntax used in the state diagrams is undefined, imprecise and open tocomment. The Maus, Kyle AITG ambiguous interpretation. In particular Figures 48-6 to 48-9 and 49-10 are particularly egregious violaters. These appear to be normative and need to be corrected. Principally: Comment TypeEComment StatusR1) Use of non standard (*,+) symbols to represent logic operations, particularly since some of Throughout the document there are instances of the phrase "frame check sequence field." The the logical” statements operate on numeric values tphher ansoeu "nf r"afimled .c"heck sequence" should be hyphenated, as it is an adjectival phrase modifying 2) Lack of sufficient parentheses to disambiguate logical expressions e 3) Mixture of syntax ( e.g. ++ to indicate auto-increment, but left arrow to indicate assignment) SuggestedRemedySuggestedRemedy Put hyphens between "frame," "check," and sequence." 1) Add a definition section to the introductory boilerplate, specifying the syntax to be used, or Response Response StatusCalternatively referencing a standard syntax. (I would suggest “C”). You may also have to add a REJECTnote about lazy evaluation” if you use autoincrements as part of a computed condition. . 2) Revise each of the state diagrams so that the transition triggering conditions and actions are This terminology has been used in 802.3 for many years and has become the accepted unambiguous and consistent with the chosen syntax. terminology. StatusResponse ResponseC REJECT. Cl00 LSC P# 32 Maus, Kyle AITG All clauses with state diagrams point to 21.5 as a reference for the "boilerplate" material. Comment TypeEComment StatusRCommenter agrees that this text satisfies his concern. Throughout the document there are instances of the phrase "frame check sequence generation." The phrase "frame check sequence" should be hyphenated, as it is an adjectival phrase modifying the noun "generation." SuggestedRemedy Put hyphens between "frame," "check," and sequence." Response Response StatusC REJECT. This terminology has been used in 802.3 for many years and has become the accepted terminology.
TYPE: TR/technical required T/technical E/editorial COMMENT STATUS: D/dispatched A/accepted R/rejected SORT ORDER: Clause, Page, Line, Subclause RESPONSE STATUS: O/open W/written C/closed U/unsatisfied Z/withdrawn
Page 2 of 80 Cl00SC
P802.3ae Draft 4.0 Comments Cl00SC P L# 322Cl00 LSC P# 32 Maus, Kyle AITG Maus, Kyle AITG Comment TypeEComment StatusRComment TypeEComment StatusR Throughout the document there are instances of the phrase "frame check sequence." The Throughout the document there are instances of "half duplex mode." In each case the phrase phrase "frame check" should be hyphenated, as it is an adjectival phrase modifying the noun "half duplex" should be hyphenated, as it is an adjectival phrase modifying the noun "mode." "sequence."SuggestedRemedy SuggestedRemedyPut a hyphen between "half" and "duplex." Put a hyphen between "frame" and "check." StatusResponse ResponseC Response Response StatusCREJECT. REJECT. This terminology has been used in 802.3 for many years and has become the accepted This terminology has been used in 802.3 for many years and has become the accepted terminology. terminology. Cl00SC P L# 25 Cl00 LSC P# 321Booth, Brad Intel Maus, Kyle AITGComment TypeEComment StatusA Comment TypeEComment StatusRAs per IEEE editor: all figures and tables must have the appropriate permissions and Throughout the document there are instances of the phrase "carrier sense signal." In each case identifications if any have been taken from another source. tnhoeu np h"rsaigsne a"lc."arrier sense" should be hyphenated, as it is an adjectival phrase modifying the SuggestedRemedy S tedRemedyEditors to ensure that required permissions and identifications have been obtained. ugges Hyphenate "carrier" and "sense." StatusResponse ResponseC ACCEPT. Response Response StatusC REJECT.Cl00SC P L# 5201 David Kabal This terminology has been used in 802.3 for many years and has become the accepted terminology.Comment TypeTComment StatusA Cl00SC P L# 30Return loss is ambiguous Maus, Kyle AITGSuggestedRemedy Specify: Comment TypeEComment StatusROptical return loss tolerance, Transmitter reflectance, and Receiver reflectance for 10GBASE-The phrase "media independent" shoud be hyphenated, as it is an adjectival phrase modifying S/L/E. the noun "interface." medReflectance should be negative. SuggPeuts tae dhyRpehen by loss tolerance should be positive. Returnetween "media" and "independent." Response Response StatusC Response Response StatusC Add only footnote to Table 52-12: Return loss is defined looking intoACCEPT IN PRINCIPLE. REJECT. the transmitter. This terminology has been used in 802.3 for many years and has become the accepted terminology.
TYPE: TR/technical required T/technical E/editorial COMMENT STATUS: D/dispatched A/accepted R/rejected SORT ORDER: Clause, Page, Line, Subclause Page 3 of 80 RESPONSE STATUS: O/open W/written C/closed U/unsatisfied Z/withdrawnCl00SC
P802.3ae Draft 4.0 Comments Cl00SC4.1.2.1.1P14L 3250 #Cl00SCGeneralP L# 33 Maus, Kyle AITG Grow, Robert Intel Comment TypeEComment StatusRComment TypeEComment StatusA Throughout the document there are instances of the phrase "full duplex mode." The phrase "full Capitilization is inconsistent and generally not in harmony with with IEEE style. While the IEEE duplex" should be hyphenated, as it is an adjectival phrase modifying the noun "mode." Style Guide doesn't specifically address this, only proper nouns are to be consistently SuggestedRemedytsnenoisi cnt ehinedintay maralleneg dna ,noitazlitapicaf  oonticedud  icyrontcpaatilized.  An incepsnoit fo EEEItd S80. 3,2.00 2tioi 0dEidac nnithattes E ed IEEah srotirongi ev phe tedrafeliro  Put a hyphen between "full" and "duplex." by editorial teams of major projects. While some may consider this inconsistency one of the Response Response StatusCidosynchrocies of the standard, I do not see a reason to perpetuate the "charm" in thischarming revision. REJECT. Subclause 1.5 is a reasonable starting point for candidate offenses. In this subclause the This terminology has been used in 802.3 for many years and has become the accepted acronym expansion is not capatilized but in many cases, this is the only place where the terminology. expansion isn't capitalized (e.g., AIS, BIP, SAUI, XGMII, XSBI, etc.) Cl00SC52.4P443L# 27SuggestedRemedy Lindsay, Tom Stratos Lightwave Get an opinion from the IEEE Editor on capitalization of expanded acronyms, and search and Comment TypeTComment StatusAdestroy inconsistencies per recommended IEEE Style. There is no explanation of what is meant by "local". Some think it means detected locally, others StatusResponse ResponseC think it means caused locally. I would like this clarified, as I have already seen it cause ACCEPT. significant confusion and debate. Cl00SCIntroP3L 893 # This applies to PMD local fault, PMD transmit local fault, and PMD receive local fault. Thompson, Geoffrey Nortel SuggestedRemedy Comment TypeEComment StatusA I do not have a remedy, but would like one to be determined and clarified in the document. I When the Standard is published in PDF there still needs to be some way to assure that the  personally prefer the concept of caused locally, although this is opposite of the position haracter int expressed by Pat Thaler. special c s pr correctly on the customer's printer Response Response StatusCSugIgnecsltueddeRtheem"eSdpyecial symbols and operators (Line 20 thru line 9 of the next page) in issued ACCEPT IN PRINCIPLE. published PDF version of the final Standard. (I would suggest that it go at the end of the book.) Add as first paragraph to 46.3.4 (with some degree of latitude): StatusResponse ResponseC Link fault signaling operates between the remote RS and the local RS. Faults detected between ACCEPT IN PRINCIPLE. the remote RS and local RS are received by the local RS as local fault. Only an RS signals remote fault. Add an editor's note to request that the IEEE Editor perform this function prior to publication of the Standard. Also all Editors to search and change: Register bits and fault detection that use the term "local fault" to indicate a fault or failure condition that is detected in that subla only. Exceptions are descriptions of the local fault messaging or function.
TYPE: TR/technical required T/technical E/editorial COMMENT STATUS: D/dispatched A/accepted R/rejected SORT ORDER: Clause, Page, Line, Subclause RESPONSE STATUS: O/open W/written C/closed U/unsatisfied Z/withdrawn
Page 4 of 80 Cl00SCIntro
# 29
P802.3ae Draft 4.0 Comments Cl01SC1.1P6L8 # 90Cl01SC1.1.2.2P7L 331 # Thompson, Geoffrey Nortel Grow, Robert Intel Comment TypeTRComment StatusAComment TypeEComment StatusA The removal of the half duplex requirement from the 10 Gigabit amendment to 802.3 is not Inconsistent capalitization. Capitalization of gigabit in f), g) and h) varies and is inconsistent justification for removing the specification of CSMA/CD as the shared media access method for with other uses in Clause 1 (i.e., 1.4 and 1.5). Ethernet/802.3.SuggestedRemedy SuggestedRemedy Pendingeditor recommendation on capitalization of expanded acronyms. thatFix per IEEE Change revision of introductory sentence to read:"This is a comprehensive International determination, capapitalization of "10 Gigabit ..." is consistent with the majority of the document. Standard for Local and Metropolitan Area Networks (LANs and MANs), employing CSMA/CDResponse Response StatusC as the shared media access method and the 802.3 communication." ACCEPT. Response Response StatusCWill capitalize "gigabit" in this subclause. ACCEPT. Cl01SC1.2.1P4L14 Cl01SC1.1.1.1P2L 3324 # AITGMaus, Kyle Sharam Hakimi ConsultantComment TypeEComment StatusA Comment TypeEComment StatusAThe comma after the word "ports" is not needed. This section refers to section 4.2.7 for allowable configuration for half duplex operation. One would need to go through the code to figure this information out.SuggestedRemedy Delete the comma. SuggestedRemedy I would suggest the following table either at 1.1.1.1 or 4.2.7 so that the reader can easily accessResponse Response StatusC this information ACCEPT.  Media Type optionsCl01SC1.3P4L? Speed half Full copper fiber Jonathan Thatcher World Wide Packets Comment StatusR 10Mb X X X XComment TypeE 100Mb X X X X Reference to TIA-445-203 on page 445 is missing. 1000Mb X X X X Reference to TIA/EIA-455-175A on page 455 line 37 is missing 10000Mb X X Reference to TIA/EIA-455-127 on page 458 line 49 is missing Response Response StatusCactF.E ACCEPT IN PRINCIPLE. OTP-107 on p ge 461.41 SuggestedRemedy Change the reference in 1.1.1.1 from 4.2.7 to 4.4.2 which already includes a table Add appropriate reference; intimidate committee into scrubbing for all missing references. with the relevant information. StatusResponse ResponseC REJECT. In this committee intimidation tactics are rarely successful. The comment has merit. However, it is rejected due to insufficient information. As an expert in this area the commenter is strongly encouraged to resubmit the comment during the next recirculation with the following information: - A comprehensive list of all missing references.  - A full title of the referenced document. - Date of the referenced document. TYPE: TR/technical required T/technical E/editorial COMMENT STATUS: D/dispatched A/accepted R/rejected SORT ORDER: Clause, Page, Line, Subclause Page 5 of 80 RESPONSE STATUS: O/open W/written C/closed U/unsatisfied Z/withdrawnCl01SC1.3
# 34
# 29
# 29
Cl01SC4P6L35 Maus, Kyle AITG Comment TypeEComment StatusA There is an unnecessary comma after the word "symbols." SuggestedRemedy Remove the comma. Response Response StatusC ACCEPT. Cl01SC4P6L40 Maus, Kyle AITG Comment TypeEComment StatusA There is an unnecessary comma after the word "pattern." SuggestedRemedy Remove the comma. Response Response StatusC ACCEPT. Cl01SC4P6L45 # 29 Maus, Kyle AITG Comment TypeEComment StatusA The phrase "125 microsecond" shoud be hyphenated, as it is an adjectival phrase modifying the noun "frame." SuggestedRemedy Add a hyphen between "125" and "microsecond"." Response Response StatusC ACCEPT. Cl02SC2.1P10L12 Maus, Kyle AITG Comment TypeEComment StatusA There is an unnecessary comma after the word "implementation." SuggestedRemedy Remove the comma. Response Response StatusC ACCEPT.
P802.3ae Draft 4.0 Comments Cl02SC2.3.1.2P10L41 # 31 Maus, Kyle AITG Comment TypeEComment StatusR The phrase "mac service data unit" should have underscores connecting each word. Due to the way Acrobat underlines, I can't tell if the underscores exist. SuggestedRemedy If there are no underscores between the words "mac," "service," "data," and "uinit," then put them in place. Response Response StatusC REJECT. The undescrores do exist. Try to zoom in/out in the acrobat window and you will be able to see them. Cl02SC2.3.1.2P10L43 # 311 Maus, Kyle AITG Comment TypeEComment StatusR The phrase "mac service data unit" should have underscores connecting each word. Due to the way Acrobat underlines, I can't tell if the underscores exist. SuggestedRemedy If there are no underscores between the words "mac," "service," "data," and "uinit," then put them in place. Response Response StatusC REJECT. The undescrores do exist. Try to zoom in/out in the acrobat window and you will be able to see them. Cl02SC2.3.1.2P10L44 # 312 Maus, Kyle AITG Comment TypeEComment StatusR The second instance of the phrase "frame check sequence" should have underscores between each word. Due to the way Acrobat underlines, I can't tell if there are underscores linking these words. SuggestedRemedy If they do not currently exist, underscores should be placed between "frame," check," and "sequence." Response Response StatusC REJECT. The undescrores do exist. Try to zoom in/out in the acrobat window and you will be able to see them.
# 301
TYPE: TR/technical required T/technical E/editorial COMMENT STATUS: D/dispatched A/accepted R/rejected SORT ORDER: Clause, Page, Line, Subclause Page 6 of 80 RESPONSE STATUS: O/open W/written C/closed U/unsatisfied Z/withdrawnCl02SC2.3.1.2
P802.3ae Draft 4.0 Comments Cl02SC2.3.1.2P10L 3145 #Cl02SC2.3.1.5P11L15 # 30 Maus, Kyle AITG Maus, Kyle AITG Comment TypeEComment StatusRComment TypeEComment StatusR The phrase "frame check sequence" should have underscores between each word. Due to the The phrase "frame check sequence parameter" should be hyphenated, as "frame check way Acrobat underlines, I can't tell if there are underscores linking these words. sequence" is an adjectival phrase modifying the noun "parameter." Due to the way Acrobat SuggestedRemedyn  ohtnenetas" dna ";ecneuqehe tif"  resenilrednuhc" ,kcearf"",emnklig incorss rera enued fhtre et tell i, I can' If they do not currently exist, underscores should be placed between "frame " check," andSarees,t edRemehdyyph ion is required. , "sequence."ugg Response Response StatusCedsrocerb teewne "frame" and "chIthf e er nisuno en tetween bhyphsd.w roehesmerapa "nd ak"ec a tup neht "ret REJECT. Response Response StatusC The undescrores do exist. Try to zoom in/out in the acrobat window and you will REJECT. be able to see them. Cl02SC2.3.1.5P11L11 # 30nd you willbe abcaorab tiwdnwoa t eles oht e.mey to zooxist. Tri  nht e mnio/tue Th sere odednuorcs Maus, Kyle AITGCl02SC2.3.1.5P11L20 # 30 Comment TypeEComment StatusR Maus, Kyle AITG The phrase "user priority parameter" should be hyphenated, as "user priority" is an adjectival phrase modifying the noun "parameter." Due to the way Acrobat underlines, I can't tell if there isComment TypeEComment StatusR an underscore linking "user" and "priority;" if there is, then no hyphenation is required. The phrase "frame type parameter" should be hyphenated, as "frame type" is an adjectival SuggestedRemedy euDt otw ehA yaobcr uaterndneli,sI c nat't le lif there is an urocsrednniknil emera"fsa eprh ".retemarap" nunoe thg infydimo If there is no underscore between "user" and "priority" then put a hyphen between these words.SuggestedRemedythere is, then no hyphenation is required.g " and "type;" if Response Response StatusCno underscore between "frame" and "type" then put a hyphen between these words.If there is REJECT. Response Response StatusC The undescrores do exist. Try to zoom in/out in the acrobat window and you will REJECT. be able to see them. The undescrores do exist. Try to zoom in/out in the acrobat window and you will Cl02SC2.3.1.5P11L13 # 30 be able to see them. Maus, Kyle AITGCl02SC2.3.1.5P11L 3022 # Comment TypeEComment StatusR AITGMaus, Kyle The phrase "access priority parameter" should be hyphenated, as "access priority" is an adjectival phrase modifying the noun "parameter." Due to the way Acrobat underlines, I can't tellComment TypeEComment StatusR if there is an underscore linking "access" and "priority;" if there is, then no hyphenation is The phrase "mac action parameter" should be hyphenated, as "mac action" is an adjectival required. phrase modifying the noun "parameter." Due to the way Acrobat underlines, I can't tell if there is SuggestedRemedyan underscore linking "mac" and "action;" if there is, then no hyphenation is required. If there is no underscore between "access" and "priority" then put a hyphen between theseSuggestedRemedy words. If there is no underscore between "mac" and "action" then put a hyphen between these words. Response Response StatusC StatusResponse ResponseC REJECT.  REJECT  . The undescrores do exist. Try to zoom in/out in the acrobat window and you will The undescrores do exist. Try to zoom in/out in the acrobat window and you will be able to see them. be able to see them.
TYPE: TR/technical required T/technical E/editorial COMMENT STATUS: D/dispatched A/accepted R/rejected SORT ORDER: Clause, Page, Line, Subclause Page 7 of 80 RESPONSE STATUS: O/open W/written C/closed U/unsatisfied Z/withdrawnCl02SC2.3.1.5
P802.3ae Draft 4.0 Comments Cl02SC2.3.1.5P11L 3024 #Cl02SC2.3.1.5P11L5 # 31 Maus, Kyle AITG Maus, Kyle AITG Comment TypeEComment StatusRComment TypeEComment StatusR The phrase "user priority parameter" should be hyphenated, as "user priority" is an adjectival The phrase "frame check sequence" should have underscores between each word. Due to the phrase modifying the noun "parameter." Due to the way Acrobat underlines, I can't tell if there is way Acrobat underlines, I can't tell if there are underscores linking these words. an underscore linking "user" and "priority;" if there is, then no hyphenation is required.SuggestedRemedy SuggestedRemedyIf they do not currently exist, underscores should be placed between "frame," check," and If there is no underscore between "user" and "priority" then put a hyphen between these words. "sequence." Response Response StatusC StatusResponse ResponseC REJECT. REJECT. The undescrores do exist. Try to zoom in/out in the acrobat window and you will The undescrores do exist. Try to zoom in/out in the acrobat window and you will be able to see them. be able to see them. Cl02SC2.3.1.5P11L26 # 30Cl02SC2.3.2.2P11L 3149 # Maus, Kyle AITG Maus, Kyle AITG Comment TypeEComment StatusRComment TypeEComment StatusR The phrase "access priority parameter" should be hyphenated, as "access priority" is an The phrase "frame check sequence" should have underscores between each word. Due to the adjectival phrase modifying the noun "parameter." Due to the way Acrobat underlines, I can't tell way Acrobat underlines, I can't tell if there are underscores linking these words. if there is an underscore linking "access" and "priority;" if there is, then no hyphenation isSuggestedRemedy required. If they do not currently exist, underscores should be placed between "frame," check," and SuggestedRemedy"sequence." If there is no underscore between "access" and "priority" then put a hyphen between theses onse words. Status ResponseRe pC REJECT. Response Response StatusC REJECT. The undescrores do exist. Try to zoom in/out in the acrobat window and you will be able to see them. The undescrores do exist. Try to zoom in/out in the acrobat window and you willCl02SC2.3.2.5P12L11 # 31 be able to see them. Maus, Kyle AITG Cl02SC2.3.1.5P11L5 # 302 , le AIComment TypeEComment StatusR Maus Ky TG The phrase "frame check sequence" should have underscores between each word. Due to the Comment TypeEComment StatusAunderlines, I can't tell if there are underscores linking these words.way Acrobat The phrase "bit transmission" should be hyphenated, as it is an adjectival phrase modifying theSuggestedRemedy noun "order." If t ntl SuggestedRemedyld bshoures rscoewneb tecade elpk,ecch" e,amfr ".ecneuqes" dna ""y exist, undeeh yodn toc ruer Put a hyphen between "bit" and "transmission." StatusResponse ResponseC Response Response StatusCREJECT. ACCEPT. The undescrores do exist. Try to zoom in/out in the acrobat window and you will be able to see them.
TYPE: TR/technical required T/technical E/editorial COMMENT STATUS: D/dispatched A/accepted R/rejected SORT ORDER: Clause, Page, Line, Subclause Page 8 of 80 RESPONSE STATUS: O/open W/written C/closed U/unsatisfied Z/withdrawnCl02SC2.3.2.5