%FDF-1.2 %âãÏÓ 1 0 obj<]/F(/C/pub/SCSI/sas2r14_with_comments_orig.pdf)>>>> endobj 3 0 obj<> endobj 4 0 obj<

Global: I think we have a p\ roblem with the generic term "zone permission table". We have several "zone permission tables" defined: - Current - Shadow - Default - Saved Collectively, all 4 of these may be referred to "zone permissio\ n tables". I think most current usages are intended to be "current zone permission table". There are also 2 instance of "active zone permission table", which is undefined and I think really are "current zone\ permission table". This same concern applies to the term "active values". The most obvious changes to me are: 1\) Use "active" instead of "current" throughout when referring to zoning permissi\ on tables and zone manager password \(I counted 25 occurrences that would need to be changed\). 2\) add "active" qualifier added to several instances of "zone permission table".

)/Type/Annot/Popup 3 0 R/Page 0>> endobj 6 0 obj<> endobj 7 0 obj<

The CONFIGURING bit is \(unfortunate\ ly\) overloaded by both zoning and the self-discovery process. There are several cases like: ....shall set the CONFIGURING bit to zero when... \ ;That is not correct behavior when both processes are outstanding.

)/Type/Annot/Popup 6 0 R/Page 0>> endobj 9 0 obj<> endobj 10 0 obj<

At the enterprise level there is a n\ eed to have an attached SAS device perform a deep reset, where all device software or firmware is re-initialised. [Typically in this scenario, enterprise would ask for a debug dump to be taken for future analysis too.] This would equate to a reset at the \ protocol level. This reset should apply to all devices, expanders, drives etc. I don't see how is this done in SAS?

)/Type/Annot/Popup 9 0 R/Page 0/BE<>>> endobj 12 0 obj<> endobj 13 0 obj<

At the enterprise level and possibly\ for other environments, there is also a need to specify behaviour for EPOW. SAS seems to have no method of indicating EPOW to devices, potentially leaving disk systems with 'damaged' sectors that will then fail on array rebuilds, causing data loss. This \ is unacceptable for the enterprise market and some method of signalling EPOW is required.

)/Type/Annot/Popup 12 0 R/Page 0/BE<>>> endobj 15 0 obj<> endobj 16 0 obj<

Proposal posted with items that need\ to be covered: 08-186r0.pdf

)/Type/Annot/Popup 15 0 R/Page 0/BE<>>> endobj 18 0 obj<> endobj 19 0 obj<

Author \ Total comments: | Accept - Done: | | Accept - Todo: | | | Accept - Last: | | | | Accept \(only\): \ | | | | | Reject - Todo: | | | | | | Reject \(only\): | | | | | | | Refer PHY: | | | | | | | | Refe\ r PROTOCOL: | | | | | | | | | Refer - Vote: | | | | | | | | | | Refer: | | | | | | | | | | | Todo \(only\)\ : | | | | | | | | | | | | Total worked: | | | | | | | | | | | | | Left: Chapter 0: 18 0 0 0 0 0 0 0 0 0 0 \ 0 0 18 Chapter 1: 5 0 0 0 0 0 0 0 0 0 0 0 0 5 Chapter 10: 237 0 0 0 0 0 0 0 0 0 0 0 0 237 Chapter 11: 21 0 0 0 0 0 0 0 0 0 0 0 \ 0 21 Chapter 12: 88 0 0 0 0 0 0 0 0 0 0 0 0 88 Chapter 13: 14 0 0 0 0 0 0 0 0 0 0 0 0 14 Chapter 2: 10 0 0 0 0 0 0 0 0 0 0 0 0\ 10 Chapter 3: 145 0 0 0 0 0 0 0 0 0 0 0 0 145 Chapter 4: 246 0 0 0 0 0 0 0 0 0 0 0 0 246 Chapter 5: 288 0 0 0 0 0 0 0 0 0 0 0 0 28\ 8 Chapter 6: 219 0 0 0 0 0 0 0 0 0 0 0 0 219 Chapter 7: 438 0 0 0 0 0 0 0 0 0 0 0 0 438 Chapter 8: 39 0 0 0 0 0 0 0 0 0 0 0 0 39&#\ 13; Chapter 9: 157 0 0 0 0 0 0 0 0 0 0 0 0 157 elx-bmartin: 66 0 0 0 0 0 0 0 0 0 0 0 0 66 elx-nayalasomayajula: 2 0 0 0 0 0 0 0 0 0 0 0 0 2 \ hpq-bolawsky: 15 0 0 0 0 0 0 0 0 0 0 0 0 15 hpq-curtisb: 1 0 0 0 0 0 0 0 0 0 0 0 0 1 hpq-relliott: 59 0 0 0 0 0 0 0 0 0 0 0 0 59 \ ibm-jay-diepenbrock: 4 0 0 0 0 0 0 0 0 0 0 0 0 4 ibm-pcashman: 2 0 0 0 0 0 0 0 0 0 0 0 0 2 ibm-sandy-shirk-heath: 1 0 0 0 0 0 0 0 0 0 0 0 0 1 i\ bm-steve-wallace: 4 0 0 0 0 0 0 0 0 0 0 0 0 4 ibm-ted-vojnovich: 4 0 0 0 0 0 0 0 0 0 0 0 0 4 ifx-hnewman: 9 0 0 0 0 0 0 0 0 0 0 0 0 9 \ intc-mseidel: 47 0 0 0 0 0 0 0 0 0 0 0 0 47 ktek-dmoore: 16 0 0 0 0 0 0 0 0 0 0 0 0 16 lsi-bbesmer: 86 0 0 0 0 0 0 0 0 0 0 0 0 86 \ lsi-bday: 81 0 0 0 0 0 0 0 0 0 0 0 0 81 lsi-gpenokie: 519 0 0 0 0 0 0 0 0 0 0 0 0 519 lsi-jenkins: 16 0 0 0 0 0 0 0 0 0 0 0 0 16 mxi\ m-kwitt: 46 0 0 0 0 0 0 0 0 0 0 0 0 46 mxim-mbari: 14 0 0 0 0 0 0 0 0 0 0 0 0 14 pmcs-gfortin: 33 0 0 0 0 0 0 0 0 0 0 0 0 33 pmcs-rherna\ ndez: 1 0 0 0 0 0 0 0 0 0 0 0 0 1 pmcs-tsymons: 1 0 0 0 0 0 0 0 0 0 0 0 0 1 stx-alvin-cox: 26 0 0 0 0 0 0 0 0 0 0 0 0 26 stx-ghoulde\ r: 148 0 0 0 0 0 0 0 0 0 0 0 0 148 wdc-mevans: 724 0 0 0 0 0 0 0 0 0 0 0 0 724 ---------------- Total comments: 1925 Accept - Done: 0 \(0.00%\) Accept - Last: 0 \(0.00%\ \) Accept - Todo: 0 \(0.00%\) Accept \(only\): 0 \(0.00%\) Reject - Todo: 0 \(0.00%\) Reject \(only\): 0 \(0.00%\) Refer PHY: 0 \(0.00%\) Refer PROTOCOL: 0 \(0.00%\) Refer - Vote: 0 \(0.00%\) Refer: 0 \(\ 0.00%\) Todo \(only\): 0 \(0.00%\) Total worked: 0 \(0.00%\) Left: 1925 \(100.00%\)

)/Type/Annot/Popup 18 0 R/Page 0>> endobj 21 0 obj<> endobj 22 0 obj<

Is SAS always intended to be compatible with SATA physical interconnect? There are issues of keying, and perhaps there are conditions for some blocks that don't support SATA 6G that may not meet their performanc\ e. It is a goal, but SATA 6G is a moving target.

)/Type/Annot/Popup 21 0 R/Page 2>> endobj 24 0 obj<> endobj 25 0 obj<

Fix long section names so that the wrap-around does not clutter the page number portion.

)/Type/Annot/Popup 24 0 R/Page 4>> endobj 27 0 obj<> endobj 28 0 obj<

Fix long table and figure names so that the wrap-around does not clutter the page number portion or the table/figure number portion.

)/Type/Annot/Popup 27 0 R/Page 26>> endobj 30 0 obj<> endobj 31 0 obj<

Fix the format on the page number for Table 70 to be the same font size as the rest of the page numbers.

)/Type/Annot/Popup 30 0 R/Page 27>> endobj 33 0 obj<> endobj 34 0 obj<

Fix the format on the page number for Figure 107 to be the same font size as the rest of the page numbers.

)/Type/Annot/Popup 33 0 R/Page 34>> endobj 36 0 obj<> endobj 37 0 obj<

The revision information needs to be removed.

)/Type/Annot/Popup 36 0 R/Page 38>> endobj 39 0 obj<> endobj 40 0 obj<

07-076r1 s/b 07-067r1

)/Type/Annot/Popup 39 0 R/Page 43>> endobj 42 0 obj<> endobj 43 0 obj<

layer. It describes s/b laye\ r, including definition of the

)/Type/Annot/Popup 42 0 R/Page 48>> endobj 45 0 obj<> endobj 46 0 obj<

defines [Delete this word.]

)/Type/Annot/Popup 45 0 R/Page 48>> endobj 48 0 obj<> endobj 49 0 obj<

layer. It describes s/b laye\ r, including definition of the

)/Type/Annot/Popup 48 0 R/Page 48>> endobj 51 0 obj<> endobj 52 0 obj<

layer. It describes s/b laye\ r, including definition of the

)/Type/Annot/Popup 51 0 R/Page 48>> endobj 54 0 obj<> endobj 55 0 obj<

layer. It describes s/b laye\ r, including definition of the

)/Type/Annot/Popup 54 0 R/Page 48>> endobj 57 0 obj<> endobj 58 0 obj<

layer. It describes s/b laye\ r, including definition of the

)/Type/Annot/Popup 57 0 R/Page 48>> endobj 60 0 obj<> endobj 61 0 obj<

Should SAT be included in this? SAT-\ 2 Figure 3 indicates how SAT fits in overall.

)/Type/Annot/Popup 60 0 R/Page 50>> endobj 63 0 obj<> endobj 64 0 obj<

I don't think putting an unknown standard here is a good idea. It looks like a TBD. Either delete it or get a real number. IEC xxxxx-xxx

)/Type/Annot/Popup 63 0 R/Page 51>> endobj 66 0 obj<> endobj 67 0 obj<

I don't think putting an unknown standard here is a good idea. It looks like a TBD. Either delete it or get a real number. ISO/IEC xxxxx-xxx

)/Type/Annot/Popup 66 0 R/Page 51>> endobj 69 0 obj<> endobj 70 0 obj<

ATA8-AAM and ATA8-ACS do not have co\ rrect ISO/IEC numbers.

)/Type/Annot/Popup 69 0 R/Page 51>> endobj 72 0 obj<> endobj 73 0 obj<

this standard What part of this standard defines the ATA physical interconnect?

)/Type/Annot/Popup 72 0 R/Page 51>> endobj 75 0 obj<> endobj 76 0 obj<

I don't think putting an unknown standard here is a good idea. It looks like a TBD. Either delete it or get a real number. ISO/IEC xxxxx-xxx,

)/Type/Annot/Popup 75 0 R/Page 52>> endobj 78 0 obj<> endobj 79 0 obj<

I don't think putting an unknown standard here is a good idea. It looks like a TBD. Either delete it or get a real number. ISO/IEC xxxxx-xxx,

)/Type/Annot/Popup 78 0 R/Page 52>> endobj 81 0 obj<> endobj 82 0 obj<

Should this table include the SATA I\ O organization?

)/Type/Annot/Popup 81 0 R/Page 52>> endobj 84 0 obj<> endobj 85 0 obj<

the FC Port terminology used within MJSQ should be substituted with SAS phy terminology. s/b [There should be more about how to do this, at the very least a couple of "e.g."s would be helpful.]

)/Type/Annot/Popup 84 0 R/Page 52>> endobj 87 0 obj<> endobj 88 0 obj<

xxxxx-xxx This is incorrect ISO num\ ber.

)/Type/Annot/Popup 87 0 R/Page 52>> endobj 90 0 obj<> endobj 91 0 obj<

xxxxx-xxx, This is incorrect ISO n\ umber.

)/Type/Annot/Popup 90 0 R/Page 52>> endobj 93 0 obj<> endobj 94 0 obj<

SATA-2 s/b SATA rev 2.6 Global change. The SATA-IO organization says there is no such thing as SATA-2 and does not want the term used. Maybe a definition of "SATA" equals "Serial ATA 2.6" in this standa\ rd and make a global change of SATA-2 to SATA.

)/Type/Annot/Popup 93 0 R/Page 53>> endobj 96 0 obj<> endobj 97 0 obj<

Should StatEye \(www.stateye.org\) n\ eed to be added to the list of other references?

)/Type/Annot/Popup 96 0 R/Page 53>> endobj 99 0 obj<> endobj 100 0 obj<

Add SAT-2 to this list?

)/Type/Annot/Popup 99 0 R/Page 53>> endobj 102 0 obj<> endobj 103 0 obj<

Serial ATA 2.6 \(SATA-2\). s/b&#\ 13;Serial ATA Revision 2.6.

)/Type/Annot/Popup 102 0 R/Page 53>> endobj 105 0 obj<> endobj 106 0 obj<>)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[185.88 365.35 257.018 365.35 185.88 352.08 257.018 352.08]/RC(

If you insist on all things be cross referenced then there needs to be one here . << An object that is >>

)/Type/Annot/Popup 105 0 R/Page 54>> endobj 108 0 obj<> endobj 109 0 obj<

I have pointed out a few missing cross-references to other glossary entries. I question the benefits of adding in cross-references to within section 3.1.xx as is see on way to get them all. I recommend removing them all.

)/Type/Annot/Popup 108 0 R/Page 54>> endobj 111 0 obj<> endobj 112 0 obj<

Train-SNW s/b SNW-1, SNW-2, \ or Final-SNW

)/Type/Annot/Popup 111 0 R/Page 54>> endobj 114 0 obj<> endobj 115 0 obj<

\(see 6.7.4.2.3.4\). s/b 6.7\ .4.2.3.2

)/Type/Annot/Popup 114 0 R/Page 54>> endobj 117 0 obj<> endobj 118 0 obj<

task file registers s/b fiel\ ds [this is how they are defined in ATA8-ACS]

)/Type/Annot/Popup 117 0 R/Page 54>> endobj 120 0 obj<> endobj 121 0 obj<

\(see 6.7.4.2.3.4\). Make see references at the end of definitions consistent either \(see x.y\) or See x.y.

)/Type/Annot/Popup 120 0 R/Page 54>> endobj 123 0 obj<> endobj 124 0 obj<

a s.b. the a implies any zoning expander, while this refers to the zone manager that locked the zoning expander device that is being referenced.

)/Type/Annot/Popup 123 0 R/Page 54>> endobj 126 0 obj<> endobj 127 0 obj<

A storage peripheral \(analogous to a SCSI target device\). Clarify this as a storage device that processes requests originated by an ATA host.

)/Type/Annot/Popup 126 0 R/Page 54>> endobj 129 0 obj<> endobj 130 0 obj<

"jitter, bounded uncorrellated \(BUJ\)" should appear in the list of definitions.

)/Type/Annot/Popup 129 0 R/Page 54>> endobj 132 0 obj<> endobj 133 0 obj<> endobj 135 0 obj<> endobj 136 0 obj<

The definition for ALT does not conform to that in Table 95. Table 95 is correct.

)/Type/Annot/Popup 135 0 R/Page 54>> endobj 138 0 obj<> endobj 139 0 obj<>)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[294.48 489.37 378.305 489.37 294.48 476.1 378.305 476.1]/RC(

If you insist on all things be cross referenced then there needs to be one here . << An object within an >>

)/Type/Annot/Popup 138 0 R/Page 55>> endobj 141 0 obj<> endobj 142 0 obj<

bits, divided s/b bits divid\ ed

)/Type/Annot/Popup 141 0 R/Page 55>> endobj 144 0 obj<> endobj 145 0 obj<

domain, communicated s/b dom\ ain communicated

)/Type/Annot/Popup 144 0 R/Page 55>> endobj 147 0 obj<> endobj 148 0 obj<

The directive "See MJSQ." is not well-defined in this context. It should point to a section number \("See MJSQ in 2.2."\). There are other occurrences of this phrase in the standard.

<\ /body>)/Type/Annot/Popup 147 0 R/Page 55>> endobj 150 0 obj<> endobj 151 0 obj<> and there is nothing in section 3.6 that would help. I suggest it be deleted.)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[431.152 669.37 544.606 669.37 431.152 656.099 544.606 656.099 64.7998 657.37 381.291 657.37 64.7998 644.099 381.291 644.099]/RC(

I have no clue what this statement is trying to tell me << and sometimes relaying a response \(see 3.1.189\) from a peer higher layer state machine. >> and there is nothing in section 3.6 that would help. I sugge\ st it be deleted.

)/Type/Annot/Popup 150 0 R/Page 56>> endobj 153 0 obj<> endobj 154 0 obj<>)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[121.461 549.37 192.434 549.37 121.461 536.099 192.434 536.099]/RC(

If you insist on all things be cross referenced then there needs to be one here .<< SAS target port >>

)/Type/Annot/Popup 153 0 R/Page 56>> endobj 156 0 obj<> endobj 157 0 obj<>)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[508.407 597.37 528.374 597.37 508.407 584.1 528.374 584.1 64.8002 585.37 115.922 585.37 64.8002 572.099 115.922 572.099]/RC(

If you insist on all things be cross referenced then there needs to be one here . <<SAS initiator phys >>

)/Type/Annot/Popup 156 0 R/Page 56>> endobj 159 0 obj<> endobj 160 0 obj<>)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[146.405 585.37 213.563 585.37 146.405 572.099 213.563 572.099]/RC(

If you insist on all things be cross referenced then there needs to be one here . << SAS target phy >>

)/Type/Annot/Popup 159 0 R/Page 56>> endobj 162 0 obj<> endobj 163 0 obj<> should be expressed mathematically.)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[238.679 143.034 292.616 143.034 238.679 131.055 292.616 131.055]/RC(

This << one-twentieth >> should be expressed mathematically.

)/Type/Annot/Popup 162 0 R/Page 56>> endobj 165 0 obj<> endobj 166 0 obj<

from a peer higher layer state machi\ ne. s/b from a peer higher layer state machine in a different SCSI device.

)/Type/Annot/Popup 165 0 R/Page 56>> endobj 168 0 obj<> endobj 169 0 obj<

A dB is ten times the common log of the power ratio, not one-tenth. It also should incorporate Note 6.

)/Type/Annot/Popup 168 0 R/Page 56>> endobj 171 0 obj<> endobj 172 0 obj<> endobj 174 0 obj<> endobj 175 0 obj<

Notes 7 and 8 should be incorporated into the definitions of dBmv and dBm.

)/Type/Annot/Popup 174 0 R/Page 56>> endobj 177 0 obj<> endobj 178 0 obj<> should be << electronics or electrical equipment. >>)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[318.292 146.35 460.532 146.35 318.292 133.08 460.532 133.08]/RC(

This << electronics/electrical equipment. >> should be << electronics or electrical equipment. >>

)/Type/Annot/Popup 177 0 R/Page 57>> endobj 180 0 obj<> endobj 181 0 obj<

This implies dword is only on the re\ ceive path. Also applies prior to 8b10b encoding \(ie. when transmitting a dword\).

)/Type/Annot/Popup 180 0 R/Page 57>> endobj 183 0 obj<> endobj 184 0 obj<

its s.b. the receiver's

)/Type/Annot/Popup 183 0 R/Page 57>> endobj 186 0 obj<> endobj 187 0 obj<

The process performed by a management application client to discover all the SAS devices \(see 3.1.197\) and expander devices \(see 3.1.77\) in the SAS domain \(see 3.1.198\) that invokes the configuration subprocess \(see 3\ .1.35\) as needed. See 4.7. add comas as shown The process performed by a management application client, to discover all the SAS devices \(see 3.1.197\) and expander devices \(see 3.1.77\) in the SAS domain \(see 3.1.198\), that invokes the c\ onfiguration subprocess \(see 3.1.35\) as needed. See 4.7.

)/Type/Annot/Popup 186 0 R/Page 57>> endobj 189 0 obj<> endobj 190 0 obj<

Broadcast -- why is this capitalized\ but none of the other objects within an expander are capitalized?

)/Type/Annot/Popup 189 0 R/Page 58>> endobj 192 0 obj<> endobj 193 0 obj<

application layer should be &q\ uot;SCSI application layer".

)/Type/Annot/Popup 192 0 R/Page 58>> endobj 195 0 obj<> endobj 196 0 obj<

end to s/b end and to\

)/Type/Annot/Popup 195 0 R/Page 59>> endobj 198 0 obj<> endobj 199 0 obj<

value. s/b value \(see Annex\ E\).

)/Type/Annot/Popup 198 0 R/Page 59>> endobj 201 0 obj<> endobj 202 0 obj<

that exists [Delete these words \ here or add them in the other nexus definitions.]

)/Type/Annot/Popup 201 0 R/Page 59>> endobj 204 0 obj<> endobj 205 0 obj<

wide connector There is no definition of "wide connector" modify this reference to refer to multiple phys or something of that nature.

)/Type/Annot/Popup 204 0 R/Page 59>> endobj 207 0 obj<> endobj 208 0 obj<

narrow connectors There is no definition of "narrow connector" modify this reference to refer to single phy or something of that nature.

)/Type/Annot/Popup 207 0 R/Page 59>> endobj 210 0 obj<> endobj 211 0 obj<

one s.b. two We never refer to a one bit field, we always refer to that as a bit.

)/Type/Annot/Popup 210 0 R/Page 59>> endobj 213 0 obj<> endobj 214 0 obj<

prior This term is unnecessary and is confusing as I_T nexus is 2 definitions above this one.

)/Type/Annot/Popup 213 0 R/Page 59>> endobj 216 0 obj<> endobj 217 0 obj<

"SATA-2" is not defined in this standard, but is in the list of abbreviations. The pointer should be to a section number \(2.4\). There may be other occurrences of this phrase in the standard.

)/Type/Annot/Popup 216 0 R/Page 59>> endobj 219 0 obj<> endobj 220 0 obj<> term should be deleted.)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[218.739 501.37 327.096 501.37 218.739 488.1 327.096 488.1]/RC(

Is there any case in this standard when it is expressed in something other than dB? I think not so the << usually >> term should be deleted.

)/Type/Annot/Popup 219 0 R/Page 60>> endobj 222 0 obj<> endobj 223 0 obj<>)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[100.378 261.4 200.591 261.4 100.378 247.595 200.591 247.595]/RC(

This should be << data dependent jitter >>

)/Type/Annot/Popup 222 0 R/Page 60>> endobj 225 0 obj<> endobj 226 0 obj<>)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[100.396 225.4 189.192 225.4 100.396 211.595 189.192 211.595]/RC(

This should be << deterministic jitter >>

)/Type/Annot/Popup 225 0 R/Page 60>> endobj 228 0 obj<> endobj 229 0 obj<> and the second , should be deleted.)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[100.408 201.4 163.674 201.4 100.408 187.595 163.674 187.595]/RC(

This should be << random jitter >> and the second , should be deleted.

)/Type/Annot/Popup 228 0 R/Page 60>> endobj 231 0 obj<> endobj 232 0 obj<>)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[97.5813 165.4 176.48 165.4 97.5813 151.595 176.48 151.595]/RC(

This should be << sinusoidal jitter >>

)/Type/Annot/Popup 231 0 R/Page 60>> endobj 234 0 obj<> endobj 235 0 obj<>)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[100.931 141.4 148.389 141.4 100.931 127.595 148.389 127.595]/RC(

This should be << total jitter >>

)/Type/Annot/Popup 234 0 R/Page 60>> endobj 237 0 obj<> endobj 238 0 obj<

If I'm going to the glossary to look for any of these types of jitter I would not look in the j's I would look in d, r, or s and not find it.

)/Type/Annot/Popup 237 0 R/Page 60>> endobj 240 0 obj<> endobj 241 0 obj<> in most cases should be changed to << command >>)/M(D:20080328102705-05'00')/T(lsi-gpenokie)/Subj(Highlight)/QuadPoints[521.056 741.37 541.796 741.37 521.056 728.1 541.796 728.1]/RC(

The term << task >> in most cases should be changed to << command >>

)/Type/Annot/Popup 240 0 R/Page 60>> endobj 243 0 obj<> endobj 244 0 obj<

device, or s/b device or

)/Type/Annot/Popup 243 0 R/Page 60>> endobj 246 0 obj<> endobj 247 0 obj<

interleaved with OOB burst \(see 3.1\ .153\). [Delete the unnecessary words.]

)/Type/Annot/Popup 246 0 R/Page 60>> endobj 249 0 obj<> endobj 250 0 obj<

from a peer higher layer state machi\ ne. s/b from a peer higher layer state machine in a different SCSI device.

)/Type/Annot/Popup 249 0 R/Page 60>> endobj 252 0 obj<> endobj 253 0 obj<

random, \(RJ\): s/b random \(\ RJ\):

)/Type/Annot/Popup 252 0 R/Page 60>> endobj 255 0 obj<> endobj 256 0 obj<

usually relaying a request \(see 3.1\ .187\) from a peer higher layer state machine. -- the "peer higher layer" phrase totally loses me. If you are a lower level machine passing a message to a higher layer machine, how can there be a peer higher layer machine to the lower layer \ machine? I think this entire phrase should be deleted.

)/Type/Annot/Popup 255 0 R/Page 60>> endobj 258 0 obj<> endobj 259 0 obj<

prior This term is unnecessary and is confusing as to what is meant by prior. Prior in time or what?

)/Type/Annot/Popup 258 0 R/Page 60>> endobj 261 0 obj<> endobj 262 0 obj<

3.1.116 jitter, data dependent Change 3.1.116 to 3.1.120 to be the proper name not "jitter, qualifier" \(e.g., "data dependent jitter" not "jitter, data dependent"\).

)/Type/Annot/Popup 261 0 R/Page 60>> endobj 264 0 obj<> endobj 265 0 obj<

Unmarked set by WDC-Mark Evans

)/StateModel(Marked)/Type/Annot/Popup 264 0 R/Page 61>> endobj 267 0 obj<> endobj 268 0 obj<

\(see 3.1.278\) \(see 6.7.4.2.3.4\). do not put two parenthetical references next to each other.

)/Type/Annot/Popup 267 0 R/Page 61>> endobj 270 0 obj<> endobj 271 0 obj<