T10/08-097r0 Voting Results on T10 Letter Ballot 08-096r0 on Forwarding SSC-3 to First Public Review Ballot closed: 2008/03/03 12:00 noon MST Organization Name S Vote Add'l Info --------------------------------- -------------------- - ---- ---------- AMCC Paul von Stamwitz P Yes Amphenol Interconnect Gregory McSorley P Yes ATL Technology Brad Brown P Yes Brocade David Peterson P No Cmnts Dell, Inc. Kevin Marks P Yes EMC Corp. David Black A Yes Cmnts Emulex Robert H. Nixon A Yes Cmnts ENDL Ralph O. Weber P Yes FCI Douglas Wagner P Yes Finisar Corp. Chris Cicchetti A Yes Foxconn Electronics Elwood Parsons P Abs Cmnts Fujitsu Mike Fitzpatrick P Yes General Dynamics Nathan Hastad P Yes Hewlett Packard Co. Curtis Ballard A No Cmnts Hitachi Global Storage Tech. Dan Colegrove P Yes IBM Corp. Kevin Butt P No Cmnts Intel Corp. Mark Seidel P Yes Iomega Corp. Robert Payne P Yes Kawasaki Microelectronics Am Joel Silverman P Yes KnowledgeTek, Inc. Dennis Moore P Yes Lexar Media, Inc. John Geldman P Abs Cmnts LSI Corp. John Lohmeyer P Yes Marvell Semiconductor, Inc. David Geddes P Yes Maxim Integrated Products Gregory Tabor P Abs Cmnts Microsoft Corp. Robert Griswold A Yes Molex Inc. Jay Neer P Yes NeoScale Systems Inc. DNV Network Appliance Frederick Knight P Yes Nvidia Corp. Mark Overby P Abs Cmnts PMC-Sierra Tim Symons P Yes Quantum Corp. Paul Suhler P No Cmnts Samsung Michael Rogers A Abs Cmnts SanDisk Corporation Avraham Shimor P Yes Seagate Technology Gerald Houlder P Abs Cmnts STMicroelectronics, Inc. Stephen Finch P Yes Sun Microsystems, Inc. Erich Oetting P Yes Symantec Roger Cummings P No Cmnts TycoElectronics Dan Gorenc A Abs Cmnts Western Digital Mark Evans P Yes Ballot totals: (26:5:7:1=39) 26 Yes 5 No 7 Abstain 1 Organization(s) did not vote 39 Total voting organizations 14 Ballot(s) included comments This 2/3rds majority ballot passed. 26 Yes are more than half the membership eligible to vote [greater than 19] AND 26 Yes are at least 21 (2/3rds of those voting YES or NO [31]). Key: P Voter is principal member A Voter is alternate member Abs Abstain vote DNV Organization did not vote Cmnts Comments were included with ballot NoCmnts No comments were included with a vote that requires comments [This report prepared by LB2 v2.3.] ************************************************************** Comments attached to No ballot from David Peterson of Brocade: Brocade-001 T 56 4.2.21.6 Resolve editors note. This editors note applies to the whole standard. see note Brocade-002 T 60 4.2.21.11 Resolve editors note. This editors note applies to the whole standard. see note Brocade-003 T 67 4.2.23.3 Resolve editors note. This editors note applies to the whole standard. see note Brocade-004 T 195 8.5.3.2.1 Resolve editors note. see note ************************************************************** Comments attached to Yes ballot from David Black of EMC Corp.: From the spec it looks like if the SDK_C bit is set then the device supports supplemental decryption keys but the only way to determine how many is by setting the SDK's until you get a MAXIMUM NUMBER OF SUPPLEMENTAL DECRYPTION KEYS EXCEEDED error (Set Data Encryption Page for SECURITY PROTOCOL OUT - 8.5.3.2.1, p.192). It would be nice if SECURITY PROTOCOL IN could provide that info before the error occurs, perhaps in the Data Encryption Algorithm descriptor. ************************************************************** Comments attached to Yes ballot from Robert H. Nixon of Emulex: ELX-001 (e) Page: 2 Location: Problem Description: The list of Physical Interconnects is significantly out-of-date concerning Fibre Channel Suggested Solution: The list of Physical Interconnects should includethe following: Fibre Channel Arbitrated Loop 2nd Generation FC-AL-2 [ANSI INCITS 332-1999 R2004] Fibre Channel Arbitrated Loop 2nd Generation Amendment 1 FC-AL-2 AM [ISO/IEC 14165-122:2005]1[ANSI INCITS 332:1999 AM1-2003] Fibre Channel Arbitrated Loop 2nd Generation Amendment 2 FC-AL-2 AM2 [ISO/IEC 14165-122:2005 AM1] [ANSI INCITS 332:1999 AM2-2006] Fibre Channel Framing and Signaling Interface FC-FS [ISO/IEC 14165-251:2008] [ANSI INCITS 373 - 2003] Fibre Channel Framing and Signaling Interface 2nd Generation FC-FS-2 [ANSI INCITS 424 - 2007] Fibre Channel Framing and Signaling Interface 3rd Generation FC-FS-3 [T11/1861-D] ELX-002 (e) Page: 2 Location: Problem Description: The list of Transport Protocols does not have current publication numbers for FCP-2 and FCP-3 Suggested Solution: The list of Transport Protocols should be amended to show these: SCSI-3 Fibre Channel Protocol - 2 FCP-2 [ISO/IEC 14776-222] [ANSI INCITS 350 - 2003 R2008] SCSI-3 Fibre Channel Protocol - 3 FCP-3 [ISO/IEC 14776-223] [ANSI INCITS 416-2006] ************************************************************** Comments attached to Abs ballot from Elwood Parsons of Foxconn Electronics: Lack of expertise ************************************************************** Comments attached to No ballot from Curtis Ballard of Hewlett Packard Co.: Comment Number: HPQ-1 Page Number: 1 PDF Comment Subtype: Text PDF Comment Type: Note Locator: Title Page Comment= "At 2.32 in. down and 0.77 in. from left Set PDF page numbers to match printed page numbers" ------- Comment Number: HPQ-2 Page Number: 1 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: Title Page Comment= "At 9.87 in. down and 6.32 in. from left Global ANSI INCITS.***:200x s/b ANSI INCITS xxx-200x (space and dash instead of periods)" ------- Comment Number: HPQ-3 Page Number: 2 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: Points of Contact page Comment= "At 1.92 in. down and 3.95 in. from left George O. Penokie s/b Mark S. Evans with appropriate contact info" ------- Comment Number: HPQ-4 Page Number: 3 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: Changes Comment= "At 1.14 in. down and 0.95 in. from left Global Header and footer should use same font as rest of text." ------- Comment Number: HPQ-5 Page Number: 3 PDF Comment Subtype: Text PDF Comment Type: Note Locator: Changes Comment= "At 1.61 in. down and 0.42 in. from left Global: use 0.9"" margin on left and right" ------- Comment Number: HPQ-6 Page Number: 6 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: Abstract Comment= "At 6.12 in. down and 7.26 in. from left StrikeOut: stream" ------- Comment Number: HPQ-7 Page Number: 6 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: Abstract Comment= "At 6.29 in. down and 4.77 in. from left StrikeOut: stream" ------- Comment Number: HPQ-8 Page Number: 13 PDF Comment Subtype: Text PDF Comment Type: Note Locator: LIst of Tables Comment= "At 1.72 in. down and 0.61 in. from left Add PDF bookmarks for Tables and Figures" ------- Comment Number: HPQ-9 Page Number: 13 PDF Comment Subtype: Text PDF Comment Type: Note Locator: LIst of Tables Comment= "At 9.42 in. down and 0.50 in. from left many field names should be small caps in the table of tables, including: 40, 43, 92, 100, 101, 107, 109, 110, 112, 129, 133, " ------- Comment Number: HPQ-10 Page Number: 18 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: Foreword Comment= "At 2.50 in. down and 0.69 in. from left DEVICE TYPE field of the INQUIRY command response data. s/b PERIPHERAL DEVICE TYPE field of the Standard INQUIRY data (see SPC-4)." ------- Comment Number: HPQ-11 Page Number: 18 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: Foreword Comment= "At 2.51 in. down and 4.34 in. from left StrikeOut: This device type is known as a stream device." ------- Comment Number: HPQ-12 Page Number: 18 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: Foreword Comment= "At 2.67 in. down and 2.02 in. from left SCSI Architecture Model - 3 (T10/1561-D) s/b SAM-4" ------- Comment Number: HPQ-13 Page Number: 18 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: Foreword Comment= "At 8.67 in. down and 1.23 in. from left Technical Committee T10 on Lower Level Interfaces s/b Technical Committee T10 - SCSI Storage Interfaces" ------- Comment Number: HPQ-14 Page Number: 19 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: Introduction Comment= "At 2.73 in. down and 3.35 in. from left definitions, symbols, and abbreviations s/b definitions, acronyms, keywords, and conventions" ------- Comment Number: HPQ-15 Page Number: 20 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 1 Scope Comment= "At 3.43 in. down and 0.44 in. from left StrikeOut: member of the SCSI stream device class" ------- Comment Number: HPQ-16 Page Number: 20 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 1 Scope Comment= "At 3.59 in. down and 1.56 in. from left the SCSI Primary Commands - 3 standard s/b SPC-4" ------- Comment Number: HPQ-17 Page Number: 20 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 1 Scope Comment= "At 3.76 in. down and 2.33 in. from left StrikeOut: member of the SCSI stream device class" ------- Comment Number: HPQ-18 Page Number: 20 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 1 Scope Comment= "At 4.59 in. down and 4.59 in. from left device type s/b smallcaps" ------- Comment Number: HPQ-19 Page Number: 20 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 1 Scope Comment= "At 4.75 in. down and 0.95 in. from left the INQUIRY command response data s/b the standard INQUIRY data (see SPC-3)" ------- Comment Number: HPQ-20 Page Number: 21 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 1 Scope Comment= "At 1.65 in. down and 0.95 in. from left StrikeOut: Delete this list: At the time this standard was generated, examples of the SCSI general structure included: ..." ------- Comment Number: HPQ-21 Page Number: 23 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 2.2 Comment= "At 2.04 in. down and 0.95 in. from left StrikeOut: ISO/IEC 14776-411, SCSI-3 Architecture Model standard" ------- Comment Number: HPQ-22 Page Number: 23 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 2.2 Comment= "At 2.20 in. down and 0.95 in. from left StrikeOut: ISO/IEC 14776-313, SCSI Primary Commands - 3 standard" ------- Comment Number: HPQ-23 Page Number: 23 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 2.2 Comment= "At 2.26 in. down and 0.43 in. from left Add SPC-2 since the ONLY IF RESERVED (OIR) bit definition refers to it" ------- Comment Number: HPQ-24 Page Number: 23 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 2.2 Comment= "At 2.61 in. down and 0.50 in. from left Add: ISO/IEC 18033-2 used in pg 219" ------- Comment Number: HPQ-25 Page Number: 23 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 2.3 Comment= "At 4.14 in. down and 0.95 in. from left ISO/IEC 14776-xxx the xxx numbers are known: SAM-4 is 414 SPC-4 is 454" ------- Comment Number: HPQ-26 Page Number: 23 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 2.3 Comment= "At 4.14 in. down and 3.36 in. from left Model - 4 s/b Model - 4 (SAM-4)" ------- Comment Number: HPQ-27 Page Number: 23 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 2.3 Comment= "At 4.31 in. down and 3.10 in. from left Commands - 4 s/b Commands - 4 (SPC-4)" ------- Comment Number: HPQ-28 Page Number: 23 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 2.4 Comment= "At 6.02 in. down and 0.71 in. from left Add: NIST SP800-56A which is used in: Table 152 - ECIES-HC requirements and parameters for ECIES-KEM" ------- Comment Number: HPQ-29 Page Number: 23 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 2.4 Comment= "At 6.35 in. down and 0.70 in. from left Add: FIPS 140-2 FIPS 856-2 which are referred to in 8.5.3.2.4.3 Key wrapping with ECC 521" ------- Comment Number: HPQ-30 Page Number: 24 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 3.1.4 Comment= "At 3.77 in. down and 0.44 in. from left StrikeOut: 3.1.4 BOx: Either beginning-of-medium (see 3.1.5) or beginning-of-partition (see 3.1.6)." ------- Comment Number: HPQ-31 Page Number: 24 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 3.1.5 Comment= "At 4.25 in. down and 5.45 in. from left beginning-of-partition s/b BOP (see 3.1.6)" ------- Comment Number: HPQ-32 Page Number: 24 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 3.1.6 Comment= "At 4.75 in. down and 3.32 in. from left beginning-of-medium s/b BOM (see 3.1.5)" ------- Comment Number: HPQ-33 Page Number: 24 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 3.1 Comment= "At 5.07 in. down and 0.18 in. from left Global: use the BOM, BOP, EOM, EOP, and EW acronyms almost everywhere. Only spell them out the first time they are used in the text." ------- Comment Number: HPQ-34 Page Number: 25 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 3.1.18 Comment= "At 1.81 in. down and 1.22 in. from left end-of-partition s/b EOP (see 3.1.20)" ------- Comment Number: HPQ-35 Page Number: 25 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 3.1.19 Comment= "At 2.31 in. down and 5.39 in. from left a s/b an" ------- Comment Number: HPQ-36 Page Number: 27 PDF Comment Subtype: PDF Comment Type: Locator: 3.1.72 Comment= It would be helpful if references such as the (see 4.2.10) in this definition could be linked to the referenced section so you can follow them in the PDF with a click. Change Suggestion= ------- Comment Number: HPQ-37 Page Number: 28 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 3.1.85 Comment= "At 8.38 in. down and 4.85 in. from left In 3.1.85 volume, add ""See 4.2.2.""" ------- Comment Number: HPQ-38 Page Number: 28 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 3.1.85 Comment= "At 8.39 in. down and 0.26 in. from left SPC-4 refers to SSC for its definition of ""volume"". One reference is: ""The VOLUME NUMBER field specifies a volume (see SSC-2) within the medium auxiliary memory. The number of volumes of the medium auxiliary memory shall equal that of the attached medium. If the medium only has a single volume, then its volume number shall be zero."" This doesn't seem to match the SSC definition. Either SPC-4 or SSC-3 should change." ------- Comment Number: HPQ-39 Page Number: 28 PDF Comment Subtype: PDF Comment Type: Locator: 3.2 Comment= It would be helpful if locations in the document that use these acronyms could be linked to their definition in this table so that the reader can select the acryonym in the text to get to the definition quickly. Change Suggestion= ------- Comment Number: HPQ-40 Page Number: 29 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 3.2 Comment= "At 2.41 in. down and 4.82 in. from left After each acronym that is a term defined in 3.1.xx, add (see 3.1.xx) BOM BOP EOD EOM EOP EW" ------- Comment Number: HPQ-41 Page Number: 29 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 3.2 Comment= "At 5.81 in. down and 0.35 in. from left Add PEWZ programmable early warning zone" ------- Comment Number: HPQ-42 Page Number: 29 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 3.2 Comment= "At 6.41 in. down and 0.34 in. from left Global: change SAM-3 to SAM-4" ------- Comment Number: HPQ-43 Page Number: 29 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 3.2 Comment= "At 6.48 in. down and 0.95 in. from left StrikeOut: SBCSCSI-3 Block Commands" ------- Comment Number: HPQ-44 Page Number: 29 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 3.2 Comment= "At 6.98 in. down and 0.95 in. from left StrikeOut: SCSI-3Small Computer System Interface - 3" ------- Comment Number: HPQ-45 Page Number: 31 PDF Comment Subtype: PDF Comment Type: Locator: 3.4 Table 1 Comment= "I think the American example for ""1 323 462.95"" should be ""1,323,462.95""" Change Suggestion= ------- Comment Number: HPQ-46 Page Number: 33 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 4.1 Comment= "At 2.95 in. down and 0.95 in. from left StrikeOut: The SCSI stream device class specifies the behavior of a logical unit that is primarily a streaming data device. Two device types are members of this class: sequential-access and printer devices. This standard addresses the sequential-access device type only." ------- Comment Number: HPQ-47 Page Number: 33 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 4.1 Comment= "At 3.45 in. down and 0.95 in. from left StrikeOut: (see SBC-2 for a description of a random-access device)." ------- Comment Number: HPQ-48 Page Number: 33 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 4.2 Comment= "At 7.35 in. down and 0.69 in. from left Add a section 4.2.x Removable media Include these points: - the RMB bit is set to one in Standard INQUIRY data (see SPC-4) - a unit attention condition is established whenever the media changes (e.g. with an additional sense code set to NOT READY TO READY CHANGE, MEDIUM MAY HAVE CHANGED) - the LOAD UNLOAD command (see 7.2) is used to add or remove the medium" ------- Comment Number: HPQ-49 Page Number: 34 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 1.81 in. down and 0.45 in. from left Beginning-of-medium s/b BOM" ------- Comment Number: HPQ-50 Page Number: 34 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 1.81 in. down and 5.70 in. from left End-of-medium s/b EOM" ------- Comment Number: HPQ-51 Page Number: 34 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 2.98 in. down and 0.45 in. from left Mounted is the state of a volume when s/b A volume is defined as mounted when" ------- Comment Number: HPQ-52 Page Number: 34 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 3.14 in. down and 2.47 in. from left is demounted s/b is defined as demounted" ------- Comment Number: HPQ-53 Page Number: 34 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 3.64 in. down and 0.45 in. from left Ready is the state of the logical unit s/b A logical unit is defined as ready" ------- Comment Number: HPQ-54 Page Number: 34 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 3.81 in. down and 0.45 in. from left The logical unit is not ready s/b A logical unit is defined as not ready" ------- Comment Number: HPQ-55 Page Number: 34 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 4.14 in. down and 3.56 in. from left not mounted s/b demounted" ------- Comment Number: HPQ-56 Page Number: 34 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 4.14 in. down and 4.58 in. from left not mounted s/b demounted" ------- Comment Number: HPQ-57 Page Number: 34 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 4.81 in. down and 4.93 in. from left beginning-of-medium s/b BOM" ------- Comment Number: HPQ-58 Page Number: 34 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 4.98 in. down and 0.45 in. from left end-of-medium position s/b EOM" ------- Comment Number: HPQ-59 Page Number: 35 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 4.57 in. down and 0.95 in. from left beginning-of-medium s/b BOM" ------- Comment Number: HPQ-60 Page Number: 35 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 4.57 in. down and 2.82 in. from left end-of-medium s/b EOM" ------- Comment Number: HPQ-61 Page Number: 35 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.2 Comment= "First paragraph last sentence is difficult to understand. There is a phrase ""course of tracks"" which is not used anywhere else." Change Suggestion= "Recommend: ""The number of tracks written at one time is called a track group (TrkGrp). --The tape motion while writting a TrkGrp is called the course of tracks.--- Track groups may be used by any recording format. For recorded volumes, reading in the forward direction follows the same course of tracks --that was used--when writing." ------- Comment Number: HPQ-62 Page Number: 35 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 5.24 in. down and 6.66 in. from left end-of-medium s/b EOM" ------- Comment Number: HPQ-63 Page Number: 35 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.2 Comment= "At 5.40 in. down and 0.95 in. from left beginning-of-medium s/b BOM" ------- Comment Number: HPQ-64 Page Number: 36 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.3 Comment= "Pysical device introductory paragraph: ""A physical device performs operations upon the medium"" -- this wording implies that the physical device only performs operations but the physical device also contains modifiable settings that are shared between multiple device servers." Change Suggestion= "Recommend: ""TA sequential-access device contains one or more physical devices. A physical device provides storage for values that are shared between multiple device servers and performs operations upon the medium""" ------- Comment Number: HPQ-65 Page Number: 37 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.3 figure 8 Comment= "Both top boxes Device Serve s/b Device Server" ------- Comment Number: HPQ-66 Page Number: 37 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.3 figure 8 Comment= "Under the top right box for the ADC device server The ADC device server is optional for SSC devices so the relationship should be 1 to 0..1 instead of 1 to 1." ------- Comment Number: HPQ-67 Page Number: 37 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.3 Comment= "At 4.52 in. down and 2.95 in. from left Physical Devic s/b Physical Device" ------- Comment Number: HPQ-68 Page Number: 38 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.3 figure 8 Comment= "At 1.64 in. down and 4.43 in. from left in figure 8.. delete extra ." ------- Comment Number: HPQ-69 Page Number: 38 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 4.2.3 Table 2 Comment= "At 7.60 in. down and 6.23 in. from left After ""table 10"" add ""in 4.2.17.1 """ ------- Comment Number: HPQ-70 Page Number: 39 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.5 Comment= "First paragraph in the section - "". . . enough space in the partition for the application client to write any buffered logical object in the application client buffer to the medium."" - What is the application client buffer? Is that different from the object buffer? If so then a definition is needed." Change Suggestion= ------- Comment Number: HPQ-71 Page Number: 40 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.6 Comment= "At 4.48 in. down and 5.63 in. from left beginning-of-medium s/b BOM" ------- Comment Number: HPQ-72 Page Number: 40 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.6 Comment= "At 4.64 in. down and 0.45 in. from left end-of-partition zero (EOP 0) s/b EOP 0" ------- Comment Number: HPQ-73 Page Number: 40 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.6 Comment= "At 4.64 in. down and 3.92 in. from left end-of-medium s/b EOM" ------- Comment Number: HPQ-74 Page Number: 40 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.6 Comment= "At 4.81 in. down and 4.67 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-75 Page Number: 40 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.6 Comment= "At 5.31 in. down and 5.28 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-76 Page Number: 41 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.6 Comment= "At 4.32 in. down and 0.95 in. from left beginning and ending points for a partition aligned with physical bounds of the medium s/b BOP and EOP aligned with BOM and EOM." ------- Comment Number: HPQ-77 Page Number: 41 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.6 Comment= "At 4.32 in. down and 2.20 in. from left a mandatory requirement s/b required" ------- Comment Number: HPQ-78 Page Number: 44 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.11 Comment= "At 5.98 in. down and 3.80 in. from left end-of-partition s/b EOP" ------- Comment Number: HPQ-79 Page Number: 45 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.12.2 Comment= "At 1.98 in. down and 2.15 in. from left streams s/b stream (to match the term used in SPC-4)" ------- Comment Number: HPQ-80 Page Number: 45 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.12.3 Comment= "At 6.93 in. down and 3.20 in. from left generated s/b established" ------- Comment Number: HPQ-81 Page Number: 46 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 4.2.12.3 Table 4 Comment= "At 4.73 in. down and 0.23 in. from left The information sense data descriptor needs to end with byte 11 not byte 10." ------- Comment Number: HPQ-82 Page Number: 46 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.12.4 Comment= "At 6.59 in. down and 1.20 in. from left following conditions s/b conditions listed in table 5" ------- Comment Number: HPQ-83 Page Number: 46 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.12.4 Comment= "At 6.92 in. down and 0.45 in. from left the device server shall return CHECK CONDITION status. The appropriate sense key and additional sense code should be set. s/b the command shall be terminated with CHECK CONDITION status with the sense key set to the specified value and the additional sense code set to the appropriate value for the condition." ------- Comment Number: HPQ-84 Page Number: 46 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.12.4 Comment= "At 6.92 in. down and 3.53 in. from left illustrates s/b lists" ------- Comment Number: HPQ-85 Page Number: 46 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.12.4 Comment= "At 7.09 in. down and 2.26 in. from left exhaustive enumeration s/b complete list" ------- Comment Number: HPQ-86 Page Number: 46 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 4.2.12.4 Table 5 Comment= "At 7.99 in. down and 0.53 in. from left Keep table 5 on one page" ------- Comment Number: HPQ-87 Page Number: 48 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 4.2.13.1 Comment= "At 5.15 in. down and 4.72 in. from left StrikeOut: MODE SELECT command with the" ------- Comment Number: HPQ-88 Page Number: 48 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.13.2 Comment= List of other conditions that may cause a DATA PROTECT sense key should add encryption errors Change Suggestion= "May add a new item d) for ""the set of data encryption parameters in the physical device is not correct for the operation requested.""" ------- Comment Number: HPQ-89 Page Number: 49 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.13.6 Comment= "Third sentence - ""The state of permanent write protection shall be recorded with the volume and the persistent write protection shall only affect the application client accessible medium.""" Change Suggestion= "The word ""persistent"" 2/3 through the sentence should be ""permanent""" ------- Comment Number: HPQ-90 Page Number: 50 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 4.2.14 Note 1 Comment= "At 7.54 in. down and 0.29 in. from left (Global) Add a - after the NOTE numbers" ------- Comment Number: HPQ-91 Page Number: 51 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.15.2 item e) Comment= "At 4.93 in. down and 1.45 in. from left an s/b the" ------- Comment Number: HPQ-92 Page Number: 51 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 4.2.15.2 Comment= "At 4.94 in. down and 7.95 in. from left StrikeOut: " ------- Comment Number: HPQ-93 Page Number: 51 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.15.2 item f) Comment= "At 5.27 in. down and 1.45 in. from left an s/b the" ------- Comment Number: HPQ-94 Page Number: 52 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.16.2 Comment= "When a reference is given such as the (see 4.2.10) in the middle paragraph in this section, it would be good to actually have a definition of the term in the referenced section rather than requiring following another reference to section 3.1.72 from 4.2.10 to find the definition." Change Suggestion= ------- Comment Number: HPQ-95 Page Number: 61 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 4.2.17.1 Table 9 Comment= "At 7.90 in. down and 0.83 in. from left (Global) In tables with more than 3 columns with rows labeled Reserved or Obsolete, join the rightmost columns together. This avoids leaving a blank cell or putting a ""-"" in the cell. Table 19h's last row would be: All others | Reserved" ------- Comment Number: HPQ-96 Page Number: 62 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 4.2.17.1 Table 10 Comment= "At 2.79 in. down and 4.07 in. from left Table 10 needs a footnote describing the abbreviations for the severity column." ------- Comment Number: HPQ-97 Page Number: 62 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 4.2.17.1 Table 10 Comment= "At 9.97 in. down and 6.46 in. from left Straddle cells in the footing" ------- Comment Number: HPQ-98 Page Number: 66 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.17.2.4 item d) Comment= "At 2.48 in. down and 2.14 in. from left etc s/b smallcaps" ------- Comment Number: HPQ-99 Page Number: 66 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.17.2.4 Comment= "At 3.43 in. down and 5.30 in. from left unit attention s/b unit attention condition" ------- Comment Number: HPQ-100 Page Number: 66 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.17.2.4 Comment= "At 4.43 in. down and 4.92 in. from left generates s/b establishes" ------- Comment Number: HPQ-101 Page Number: 67 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 4.2.17.4 Comment= "At 8.33 in. down and 0.38 in. from left The last paragraph of 4.2.17.4 should be b)" ------- Comment Number: HPQ-102 Page Number: 69 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.19 Note 10 Comment= "At 5.07 in. down and 3.09 in. from left streaming device types s/b the sequential-access device type" ------- Comment Number: HPQ-103 Page Number: 70 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 4.2.20.1 Comment= "At 9.36 in. down and 5.05 in. from left StrikeOut: s at end of sentence (devices server)" ------- Comment Number: HPQ-104 Page Number: 70 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.20.2 Comment= "At 10.02 in. down and 0.45 in. from left What exactly is an archive tape? Should there be a definition in 3.1?" ------- Comment Number: HPQ-105 Page Number: 71 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.20.3 Comment= "At 3.81 in. down and 5.14 in. from left Third paragraph first sentence if THE medium ?" ------- HPQ-106 Page Number: numerous PDF Comment Subtype: PSF Comment Type: Locator: "4.2.21.n, 8.5.n" Comment= "4.2.2.2 sentence 2 defines encryption control as being on an I_T_L nexus basis, but most references after this use I_T nexus" Change references to I_T_L Nexus for Encryption control as already marked in red in 4a draft. ------- Comment Number: HPQ-107 Page Number: 71 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.1 Comment= "Most encryption processing has been moved from the device server to the physical device but not all references to capabilities in the device server were updated. Several comments to follow will point out areas where device server should be changed to physical device. Those comments will all start with ""Device Server -> Physical Device"" to help identify them as all part of the same change. First paragraph second to last sentence - ""encryption and decryption processes within the device server"" - those processes were moved to the physical device" "Change ""device server"" to ""physical device""" ------- Comment Number: HPQ-108 Page Number: 72 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.3 Comment= "Device Server -> Physical Device Second paragraph - ""A device server that supports encryption should be capable of distinguishing encrypted . . ."" Detection of blocks will occur in the physical device not the device server." Change Suggestion= "Change ""device server"" to ""physical device""" ------- Comment Number: HPQ-109 Page Number: 72 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.3 Comment= "Device Server -> Physical Device Second paragraph second sentence - ""The device server reports it's capability of distinguishing encrypted blocks"" " Change Suggestion= "Should be ""The device server reports that capability of the physical device for distinguishing encrypted blocks""" ------- Comment Number: HPQ-110 Page Number: 72 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.3 Comment= "Device Server -> Physical Device Second paragraph third sentence ""If the device server is capable of distinguishing""" Change Suggestion= "Should be ""If the physical device is capable of distinguishing""" ------- Comment Number: HPQ-111 Page Number: 72 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.3 Comment= "Device Server -> Physical Device Second paragraph last sentence ""The device server shall establish the logical position""" Change Suggestion= "Should be ""The physical device shall establish . . .""" ------- Comment Number: HPQ-112 Page Number: 72 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.21.3 Comment= "At 6.78 in. down and 1.20 in. from left Note 11 not sure this is correct; it may attempt to decrypt data but it will not actually manage it. Better to say something like "".. to run the decryption process on data that was not encrypted""" ------- Comment Number: HPQ-113 Page Number: 72 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.3 Comment= "Device Server -> Physical Device Note 11 ""It is possible for a device server that is not capable of distinguishing""" Change Suggestion= "Should be ""It is possible for a physical device that is not . . .""" ------- Comment Number: HPQ-114 Page Number: 72 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.3 Comment= "Device Server -> Physical Device Third paragraph first sentence ""A device server that supports encryption""" Change Suggestion= "Should be ""A physical device that supports encryption""" ------- Comment Number: HPQ-115 Page Number: 72 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.3 Comment= "Device Server -> Physical Device Third paragraph fourth sentence ""If the device server is capable of determining that the encryption key is correct""" Change Suggestion= "Should be ""If the physical device is capable . . . """ ------- Comment Number: HPQ-116 Page Number: 72 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.3 Comment= "Device Server -> Physical Device Third paragraph last sentence ""The device server shall establish the logical position""" Change Suggestion= "Should be ""The physical device shall establish . . .""" ------- Comment Number: HPQ-117 Page Number: 72 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.3 Comment= "Device Server -> Physical Device Fourth paragraph first sentence ""A device server that supports encryption""" Change Suggestion= "Should be ""A physical device that supports encryption""" ------- Comment Number: HPQ-118 Page Number: 72 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.3 Comment= "Device Server -> Physical Device Fourth paragraph second sentence ""If the device server is capable of validating the integrity of the data""" Change Suggestion= "Should be ""If the physical device is capable . . . """ ------- Comment Number: HPQ-119 Page Number: 72 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.3 Comment= "Device Server -> Physical Device Fourth paragraph last sentence ""The device server shall establish the logical position""" Change Suggestion= "Should be ""The physical device shall establish . . .""" ------- Comment Number: HPQ-120 Page Number: 72 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.3 Comment= "Device Server -> Physical Device Fifth paragraph first sentence ""A device server that is capable of distinguishing encrypted blocks""" Change Suggestion= "Should be ""A physical device that is capable . . .""" ------- Comment Number: HPQ-121 Page Number: 72 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.3 Comment= "Device Server -> Physical Device Sixth paragraph first sentence ""A device server that is capable of both determining if the encryption key or""" Change Suggestion= "Should be ""A physical device that is capable . . .""" ------- Comment Number: HPQ-122 Page Number: 73 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.21.4 Comment= "At 5.64 in. down and 1.77 in. from left SPECIFC s/b SPECIFIC" ------- Comment Number: HPQ-123 Page Number: 73 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.21.4 Comment= "At 5.64 in. down and 5.20 in. from left DECRYPT field or ENCRYPT field s/b DECRYPTION MODE field or ENCRYPTION MODE field using smallcaps" ------- Comment Number: HPQ-124 Page Number: 73 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.21.4 Comment= "At 5.98 in. down and 4.35 in. from left DECRYPTION If this is reported because the ENCRYPT field (should be ENCRYPTION MODE field) is set incorrectly, this name does not make sense. Add an additional sense code with ENCRYPTION in the name or delete the ENCRYPT field from the discussion. " ------- Comment Number: HPQ-125 Page Number: 74 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 4.2.21.5 Comment= "At 1.65 in. down and 6.34 in. from left StrikeOut: is" ------- Comment Number: HPQ-126 Page Number: 74 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.21.5 Comment= "At 2.48 in. down and 2.13 in. from left ENCRYPTION MODE s/b small caps" ------- Comment Number: HPQ-127 Page Number: 74 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.21.5 Comment= "At 4.14 in. down and 2.84 in. from left ALGORITHM INDEX s/b smallcaps" ------- Comment Number: HPQ-128 Page Number: 74 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.5 Comment= "Device Server -> Physical Device Fourth paragraph on the page ""If the encryption algorithm provides this capability, the device server may support a feature to check during read and verify operations""" Change Suggestion= "Should be ""If the encryption algorithm provides this capability, the physical device may . . . """ ------- Comment Number: HPQ-129 Page Number: 74 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.5 Comment= "Device Server -> Physical Device First lettered list on page - 1) ""the device server shall verify that each encrypted block that is processed for read and verify. . . """ Change Suggestion= "Should be ""the physical device shall verify . . .""" ------- Comment Number: HPQ-130 Page Number: 74 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.5 Comment= "Device Server -> Physical Device Second lettered list on page - 1) ""the device server shall verify that each encrypted block that is processed""" Change Suggestion= "Should be ""the physical device shall verify . . .""" ------- Comment Number: HPQ-131 Page Number: 74 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.5 Comment= "Device Server -> Physical Device Third lettered list on page - 1) ""the device server shall check the format specific indication that disables . . . """ Change Suggestion= "Should be ""the physical device shall check . . .""" ------- Comment Number: HPQ-132 Page Number: 75 PDF Comment Subtype: PDF Comment Type: Locator: Editors Note 1 Comment= "I don't see the ambiguity in ""data encryption parameter"" " Data encryption Parameters are already specified in 4.2.21.8. ------- Comment Number: HPQ-133 Page Number: 76 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.21.6 Comment= "At 2.98 in. down and 0.95 in. from left It would be clearer if the phrase ""registered for encryption unit attentions state"" (and where else it's referenced) was clearly marked out as a variable. Not sure of the right format - caps, bold, etc - but it would make it easier to read." ------- Comment Number: HPQ-134 Page Number: 76 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.21.6 Comment= "Paragraph following first a/b list last sentence at the physical device shall" Change Suggestion= "Should be: ""and the physical device shall""" ------- Comment Number: HPQ-135 Page Number: 77 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.21.7 item c) Comment= "At 1.81 in. down and 1.98 in. from left after NEXUS add a period" ------- Comment Number: HPQ-136 Page Number: 77 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.21.7 Comment= "At 5.81 in. down and 1.19 in. from left registered for encryption unit attentions state Consider creating an acronym for this wordy name (REUA state?). Since it is in lowercase, it is hard to read." ------- Comment Number: HPQ-137 Page Number: 77 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.21.7 Comment= "At 5.98 in. down and 1.28 in. from left generate s/b establish" ------- Comment Number: HPQ-138 Page Number: 79 PDF Comment Subtype: PDF Comment Type: Locator: Editors Note 2 Comment = """data"" replaced with ""logical block""in numerous places" Substitution seems reasonable. Leave as substituted in 4a draft. ------- Comment Number: HPQ-139 Page Number: 80 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.22.2.1 Comment= "Second paragraph first sentence ""data encryption capabilities""" It would be good to reference this to (see 4.2.21.9) ------- Comment Number: HPQ-140 Page Number: 80 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.22.2.1 Comment= "At 6.31 in. down and 3.71 in. from left nexus s/b nexuses" ------- Comment Number: HPQ-141 Page Number: 80 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.22.2.2 Comment= "Next to last a/b list item b/B - ""report the encryption algorithm in the Data Encryption Capabilities page with the DISABLED bit set to one.."" - The DISABLED bit has been removed" Change Suggestion= "Should be ""report the encryption algorithm in the Data Encryption Capabilities page with the DECRYPT_C field set to No Capability and the ENCRYPT_C field set to No Capability.""" ------- Comment Number: HPQ-142 Page Number: 80 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.22.2.2 Comment= "In the last paragraph on the page the statement ""If external data encryption control has been used to configure the physical device to prevent device server control of data encryption parameters"" does not clearly state what conditions would cause this state." Change Suggestion= "Add an example at the end of the sentence (e.g., the device contains a device server that reports itself as an ADC device and the data encryption parameters control policy is set to a policy type where control of encryption algorithms by this device server is prevented, see ADC-3)" ------- Comment Number: HPQ-143 Page Number: 81 PDF Comment Subtype: PDF Comment Type: Locator: 4.2.22.3.2 Comment= "Last paragraph on the page ""If external data encryption control is not being used, then the data encryption control policies shall be set to defaults."" - Should use consistent naming." Change Suggestion= "Should be "". . . then the data encryption parameters request policies . . .""" ------- Comment Number: HPQ-144 Page Number: 83 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.22.3.2 Table 16 Comment= "At 3.28 in. down and 6.73 in. from left encryptionparam s/b encryption param" ------- Comment Number: HPQ-145 Page Number: 83 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 4.2.22.3 Table 16 Comment= "At 3.52 in. down and 0.55 in. from left Should RECOVER BUFFERED DATA also be in the list in table 16?" ------- Comment Number: HPQ-146 Page Number: 86 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 4.2.23.3 Comment= "At 4.63 in. down and 4.99 in. from left StrikeOut: ," ------- Comment Number: HPQ-147 Page Number: 86 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 4.2.23.3 Comment= "At 4.96 in. down and 2.84 in. from left sent to it s/b that it receives" ------- Comment Number: HPQ-148 Page Number: 89 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 5.1 Table 21 Comment= "At 4.27 in. down and 0.37 in. from left SPC-4 lists A5h MOVE MEDIUM as being optional for this device type" ------- Comment Number: HPQ-149 Page Number: 89 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 5.1 Table 21 Comment= "At 6.70 in. down and 0.54 in. from left LOCATE(16) is listed as optional in SPC-4" ------- Comment Number: HPQ-150 Page Number: 90 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 5.1 Table 21 Comment= "At 3.55 in. down and 0.21 in. from left SPC-4 lists commands like READ(16) and WRITE (16) as mandatory for the SSC device type. However, they're really only mandatory for explicit addressing; they're not even supported for implicit addressing. Similarly, VERIFY (16) is optional for explicit addressing, but not allowed for implicit addressing. Perhaps a new letter should be used in the SPC-4 table defined as ""Y see the command standard""" ------- Comment Number: HPQ-151 Page Number: 90 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 5.1 Table 21 Comment= "At 5.64 in. down and 1.15 in. from left ALIAS s/b ALIASES" ------- Comment Number: HPQ-152 Page Number: 90 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 5.1 Table 21 Comment= "At 6.15 in. down and 1.15 in. from left DEVICE IDENTIFIER s/b IDENTIFYING INFORMATION" ------- Comment Number: HPQ-153 Page Number: 90 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 5.1 Table 21 Comment= "At 6.49 in. down and 0.21 in. from left REPORT LUNS is supposed to be M not X. The old rules along the lines of ""mandatory for LUN 0, optional for the rest"" were eliminated by 02-260r1 per minutes 02-273r0." ------- Comment Number: HPQ-154 Page Number: 90 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 5.1 Table 21 Comment= "At 6.88 in. down and 0.20 in. from left Add: A3h/0Dh REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS A3h/0Eh REPORT PRIORITY A3h/0Fh REPORT TIMESTAMP A3h/10h MANAGEMENT PROTOCOL IN" ------- Comment Number: HPQ-155 Page Number: 90 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 5.1 Table 21 Comment= "At 7.27 in. down and 0.26 in. from left Add: A4h/0Eh SET PRIORITY A4h/0Fh SET TIMESTAMP A4h/10h MANAGEMENT PROTOCOL OUT" ------- Comment Number: HPQ-156 Page Number: 93 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 5.2 Table 23 Comment= "At 4.08 in. down and 0.43 in. from left Global for all table headers: Table headers are inconsistent. XYZ field values (sometimes) or XYZ field definition (sometimes) or XYZ field (sometimes) I recommend just: XYZ field" ------- Comment Number: HPQ-157 Page Number: 93 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 5.2 Table 23 Comment= "At 4.28 in. down and 1.40 in. from left Value s/b Code" ------- Comment Number: HPQ-158 Page Number: 94 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 5.3 Comment= "At 9.88 in. down and 3.27 in. from left end-of-partition s/b EOP" ------- Comment Number: HPQ-159 Page Number: 98 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 5.4 Comment= "At 1.98 in. down and 2.62 in. from left (beginning-of-partition s/b BOP" ------- Comment Number: HPQ-160 Page Number: 98 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 5.4 Comment= "At 2.31 in. down and 2.61 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-161 Page Number: 104 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 6.1 Table 29 Comment= "At 4.24 in. down and 0.24 in. from left Need to list obsolete command opcodes for this device type per SPC-4 16h RESERVE (6) 17h RELEASE (6) 39h COMPARE 3Ah COPY AND VERIFY 40h CHANGE DEFINITION 56h RESERVE(10) 57h RELEASE(10)" ------- Comment Number: HPQ-162 Page Number: 104 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 6.1 Table 29 Comment= "At 4.87 in. down and 0.30 in. from left 7Eh extended CDB is listed as optional for this device type in SPC-4" ------- Comment Number: HPQ-163 Page Number: 104 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 6.1 Table 29 Comment= "At 5.29 in. down and 0.28 in. from left SPC-4 lists these opcodes A5h MOVE MEDIUM B8h READ ELEMENT STATUS as being optional for this device type. They should probably be listed as obsolete" ------- Comment Number: HPQ-164 Page Number: 104 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 6.1 Table 29 Comment= "At 5.65 in. down and 0.25 in. from left Mention that these opcodes A7h MOVE MEDIUM ATTACHED B4h READ ELEMENT STATUS ATTACHED are obsolete for this device type" ------- Comment Number: HPQ-165 Page Number: 104 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 6.1 Table 29 Comment= "At 7.22 in. down and 0.50 in. from left LOCATE (10) is listed as optional in SPC-4" ------- Comment Number: HPQ-166 Page Number: 104 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 6.1 Table 29 Comment= "At 7.50 in. down and 0.32 in. from left LOCATE (16) is listed as optional in SPC-4" ------- Comment Number: HPQ-167 Page Number: 104 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 6.1 Table 29 Comment= "At 9.12 in. down and 0.37 in. from left PR IN/OUT are listed as optional in SPC-4" ------- Comment Number: HPQ-168 Page Number: 105 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 6.1 Table 29 Comment= "At 2.87 in. down and 0.83 in. from left The PREVENT ALLOW MEDIUM REMOVAL command needs to be defined in this standard; it was evicted from SPC-4 since MMC-5 was not following the general definition." ------- Comment Number: HPQ-169 Page Number: 105 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.1 Table 29 Comment= "At 5.41 in. down and 1.97 in. from left ALIAS s/b ALIASES" ------- Comment Number: HPQ-170 Page Number: 105 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.1 Table 29 Comment= "At 5.68 in. down and 1.97 in. from left DEVICE IDENTIFIER s/b IDENTIFYING INFORMATION" ------- Comment Number: HPQ-171 Page Number: 105 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 6.1 Table 29 Comment= "At 6.00 in. down and 0.71 in. from left REPORT LUNS is supposed to be M not X. The old rules along the lines of ""mandatory for LUN 0, optional for the rest"" were eliminated by 02-260r1 per minutes 02-273r0." ------- Comment Number: HPQ-172 Page Number: 105 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 6.1 Table 29 Comment= "At 6.39 in. down and 0.63 in. from left Add: A3h/0Dh REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS A3h/0Eh REPORT PRIORITY A3h/0Fh REPORT TIMESTAMP A3h/10h MANAGEMENT PROTOCOL IN" ------- Comment Number: HPQ-173 Page Number: 105 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 6.1 Table 29 Comment= "At 8.06 in. down and 0.53 in. from left Add: A4h/0Eh SET PRIORITY A4h/0Fh SET TIMESTAMP A4h/10h MANAGEMENT PROTOCOL OUT" ------- Comment Number: HPQ-174 Page Number: 105 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.1 Table 29 Comment= "At 8.19 in. down and 1.67 in. from left DEVICE IDENTIFIER s/b IDENTIFYING INFORMATION" ------- Comment Number: HPQ-175 Page Number: 111 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.5 Comment= "At 5.30 in. down and 1.00 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-176 Page Number: 111 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.5 Comment= "At 7.30 in. down and 2.73 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-177 Page Number: 111 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.5 Comment= "At 7.63 in. down and 3.14 in. from left beginning-of-partition s/b the BOP" ------- Comment Number: HPQ-178 Page Number: 112 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.6 Comment= "At 7.91 in. down and 5.21 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-179 Page Number: 112 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.6 Comment= "At 8.07 in. down and 1.87 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-180 Page Number: 112 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.6 Comment= "At 9.74 in. down and 2.34 in. from left end-of-partition s/b EOP" ------- Comment Number: HPQ-181 Page Number: 112 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.6 Comment= "At 9.91 in. down and 0.68 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-182 Page Number: 113 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.6 Comment= "At 5.12 in. down and 1.07 in. from left beginning-of-partition s/b the BOP" ------- Comment Number: HPQ-183 Page Number: 113 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.6 Comment= "At 6.12 in. down and 3.92 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-184 Page Number: 113 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.6 Comment= "At 6.45 in. down and 3.71 in. from left count s/b smallcaps" ------- Comment Number: HPQ-185 Page Number: 113 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.6 Comment= "At 7.45 in. down and 5.62 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-186 Page Number: 113 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 6.6 Comment= "At 7.95 in. down and 1.08 in. from left end-of-partition s/b EOP" ------- Comment Number: HPQ-187 Page Number: 119 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.1 Comment= "At 5.71 in. down and 5.95 in. from left beginning-of-partition 0 (BOP 0) s/b BOP 0" ------- Comment Number: HPQ-188 Page Number: 120 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.1 Table 40 Comment= "At 1.96 in. down and 3.60 in. from left Format field definition s/b FORMAT field" ------- Comment Number: HPQ-189 Page Number: 120 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.1 Table 40 Comment= "At 2.29 in. down and 2.51 in. from left Value s/b Code" ------- Comment Number: HPQ-190 Page Number: 121 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.2 Comment= "At 6.20 in. down and 0.95 in. from left the beginning-of-partition zero s/b BOP 0" ------- Comment Number: HPQ-191 Page Number: 121 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.2 Comment= "At 7.70 in. down and 2.76 in. from left generate s/b establish" ------- Comment Number: HPQ-192 Page Number: 121 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.2 Comment= "At 10.20 in. down and 4.52 in. from left beginning-of-medium s/b BOM" ------- Comment Number: HPQ-193 Page Number: 124 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.4 Table 45 Comment= "At 5.60 in. down and 2.48 in. from left PREVENT s/b Code" ------- Comment Number: HPQ-194 Page Number: 128 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.6.2 Comment= "At 7.88 in. down and 5.20 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-195 Page Number: 128 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.6.2 Comment= "At 8.05 in. down and 5.06 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-196 Page Number: 128 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.6.2 Comment= "At 8.38 in. down and 6.22 in. from left early-warning s/b EW" ------- Comment Number: HPQ-197 Page Number: 128 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.6.2 Comment= "At 8.55 in. down and 0.45 in. from left end-of-partition s/b EOP" ------- Comment Number: HPQ-198 Page Number: 128 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.6.2 Comment= "At 8.71 in. down and 0.45 in. from left early-warning s/b EW" ------- Comment Number: HPQ-199 Page Number: 128 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.6.2 Comment= "At 8.71 in. down and 1.59 in. from left end-of-partition s/b EOP" ------- Comment Number: HPQ-200 Page Number: 131 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.6.3 Comment= "At 5.14 in. down and 5.62 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-201 Page Number: 138 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.8.4 Comment= "At 8.64 in. down and 4.84 in. from left field bit s/b bit" ------- Comment Number: HPQ-202 Page Number: 140 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.9 Comment= "At 7.16 in. down and 5.31 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-203 Page Number: 141 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.1 Comment= "At 8.14 in. down and 5.82 in. from left beginning-of-partition 0 (BOP 0) s/b BOP 0" ------- Comment Number: HPQ-204 Page Number: 141 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.1 Comment= "At 9.14 in. down and 5.21 in. from left generate s/b establish" ------- Comment Number: HPQ-205 Page Number: 142 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.11 Comment= "At 10.50 in. down and 4.71 in. from left (toward beginning-of-partition) s/b (towards BOP)" ------- Comment Number: HPQ-206 Page Number: 143 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.11 Comment= "At 1.64 in. down and 2.37 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-207 Page Number: 144 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.11 Comment= "At 2.48 in. down and 0.68 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-208 Page Number: 144 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.11 Comment= "At 7.43 in. down and 0.57 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-209 Page Number: 144 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 7.11 Comment= "At 8.43 in. down and 3.49 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-210 Page Number: 146 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.1 Table 63 Comment= "At 6.78 in. down and 0.35 in. from left Add log page subpages to table 63." ------- Comment Number: HPQ-211 Page Number: 146 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.1 Table 63 Comment= "At 9.22 in. down and 0.33 in. from left Log page 08h/00h is listed in SPC-4 as ""Format Status"" for tape drives. If it is obsolete, it should be mentioned in table 63. If it never existed, it should be removed from SPC-4." ------- Comment Number: HPQ-212 Page Number: 146 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.2.1 Table 63 Comment= "At 9.25 in. down and 2.79 in. from left Error Events s/b Error or Asynchronous Events" ------- Comment Number: HPQ-213 Page Number: 147 PDF Comment Subtype: PDF Comment Type: Locator: 8.2.2 Comment= "The following text is difficult to read: The Sequential-Access Device log page defines data counters associated with data bytes transferred to and from the medium and to and from the application client, binary list parameters describing native capacities, and a binary list parameter related to cleaning." Change Suggestion= "The Sequential-Access Device log page defines: a) data counters associated with data bytes transferred to and from the medium and to and from the application client, b) binary list parameters describing native capacities, and c) a binary list parameter related to cleaning." ------- Comment Number: HPQ-214 Page Number: 147 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.2.1 Table 63 Comment= "At 2.24 in. down and 2.58 in. from left test s/b Test" ------- Comment Number: HPQ-215 Page Number: 147 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.1 Table 63 Comment= "At 2.87 in. down and 0.76 in. from left Log page 12h/00h is not listed in SPC-4 for this device type" ------- Comment Number: HPQ-216 Page Number: 147 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.1 Table 63 Comment= "At 2.99 in. down and 1.00 in. from left Log page 13h/00h is not listed in SPC-4 for this device type" ------- Comment Number: HPQ-217 Page Number: 147 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.1 Table 63 Comment= "At 3.92 in. down and 0.83 in. from left Log page 18h/xxh is Protocol Specific Port" ------- Comment Number: HPQ-218 Page Number: 147 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.1 Table 63 Comment= "At 4.26 in. down and 0.85 in. from left Log page 2Dh/00h is not listed in SPC-4" ------- Comment Number: HPQ-219 Page Number: 149 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.3 Table 65 Comment= "At 4.49 in. down and 6.02 in. from left Add ""(see table 66)"" in rows 4 and n-y+1" ------- Comment Number: HPQ-220 Page Number: 149 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.3 Table 65 Comment= "At 4.68 in. down and 0.61 in. from left Since the parameter length is fixed: Change x+3 to 8 Delete Length x=5 Change n-y+1 to n-4 Delete Length x=5" ------- Comment Number: HPQ-221 Page Number: 149 PDF Comment Subtype: PDF Comment Type: Locator: 8.2.3 Comment= "Update use of DS, LBIN and LP to be consistent with latest SPC4 log parameter fields" ------- Comment Number: HPQ-222 Page Number: 150 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.4.1 Table 67 Comment= "At 6.97 in. down and 5.67 in. from left Add ""(see table 69 in 8.2.4.2)"" in rows 4 and n" ------- Comment Number: HPQ-223 Page Number: 152 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 8.2.4.3 Table 70 Byte 4 Comment= "At 5.23 in. down and 3.56 in. from left StrikeOut: log" ------- Comment Number: HPQ-224 Page Number: 152 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 8.2.4.3 Table 70 Byte n Comment= "At 5.72 in. down and 3.57 in. from left StrikeOut: log" ------- Comment Number: HPQ-225 Page Number: 153 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.5 Table 72 Comment= "At 8.80 in. down and 6.51 in. from left Add ""(see table 73)"" in rows 4 and n" ------- Comment Number: HPQ-226 Page Number: 154 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.5 Table 73 Comment= "At 1.95 in. down and 5.97 in. from left In table 73 header, add ""(part 1 of 2)""" ------- Comment Number: HPQ-227 Page Number: 155 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 8.2.5 Table 73 Comment= "At 2.86 in. down and 1.30 in. from left Between bytes 32 and 63 StrikeOut: : :" ------- Comment Number: HPQ-228 Page Number: 156 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.6.1 Table 74 Comment= "At 9.30 in. down and 5.69 in. from left Add ""(see table 75)"" in rows 4 and n" ------- Comment Number: HPQ-229 Page Number: 156 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.6.1 Table 74 Comment= "At 9.32 in. down and 1.26 in. from left Make row 4 and row n each two rows tall, since they contain more than one byte" ------- Comment Number: HPQ-230 Page Number: 157 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.2.6.1 Table 75 Comment= "At 4.44 in. down and 6.10 in. from left Add ""(see table 76)"" in rows 16 and t" ------- Comment Number: HPQ-231 Page Number: 158 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.2.6.1 Comment= "At 1.81 in. down and 6.09 in. from left End of first sentence on page .. s/b ." ------- Comment Number: HPQ-232 Page Number: 159 PDF Comment Subtype: PDF Comment Type: Locator: 8.2.6.3 Comment= The DEVICE ELEMENT CODE (DEC) . Change Suggestion= The device element code (DEC) . ------- Comment Number: HPQ-233 Page Number: 159 PDF Comment Subtype: PDF Comment Type: Locator: 8.2.6.3 Comment= The DEVICE ELEMENT CODE QUALIFIER (DECQ) . Change Suggestion= The device element code qualifier (DECQ). ------- Comment Number: HPQ-234 Page Number: 160 PDF Comment Subtype: PDF Comment Type: Locator: 8.2.6.3 Comment: The DEVICE ELEMENT CODE TEXT (DECT) . Change Suggestion= The device element code text (DECT) . ------- Comment Number: HPQ-235 Page Number: 160 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.2.6.3 Comment= "At 2.81 in. down and 7.16 in. from left .. s/b ." ------- Comment Number: HPQ-236 Page Number: 160 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.2.6.4 Table 82 Comment= "At 7.52 in. down and 5.02 in. from left VOLUME INFORMATION LENGTH (n) s/b VOLUME INFORMATION LENGTH (n - 1)" ------- Comment Number: HPQ-237 Page Number: 161 PDF Comment Subtype: PDF Comment Type: Locator: 8.2.6.4 Comment= The VOLUME INFORMATION CODE (VIC) . Change Suggestion= The volume information code (VIC) ... ------- Comment Number: HPQ-238 Page Number: 161 PDF Comment Subtype: PDF Comment Type: Locator: 8.2.6.4 Comment= The VOLUME INFORMATION CODE QUALIFIER (VICQ) . Change Suggestion= The volume information code qualifier (VICQ) ... ------- Comment Number: HPQ-239 Page Number: 161 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.2.6.4 Comment= "At 5.82 in. down and 5.63 in. from left Following VOLUME INFORMATION CODE QUALIFIER .. s/b ." ------- Comment Number: HPQ-240 Page Number: 161 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.2.6.4 Comment= "At 10.03 in. down and 2.42 in. from left exsits s/b exists" ------- Comment Number: HPQ-241 Page Number: 162 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.2.6.5 Table 85 Comment= "At 4.28 in. down and 5.46 in. from left 2 s/b 02h" ------- Comment Number: HPQ-242 Page Number: 162 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.2.6.5 Comment= "At 5.27 in. down and 3.18 in. from left 16384 s/b 16 384 (add ISO style spaces throughout this page)" ------- Comment Number: HPQ-243 Page Number: 163 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.2.7.1 Table 86 Comment= "At 4.94 in. down and 3.64 in. from left Reqested s/b Requested" ------- Comment Number: HPQ-244 Page Number: 166 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.3.1 Table 92 Comment= "At 9.69 in. down and 1.31 in. from left Keep table 92 on one page" ------- Comment Number: HPQ-245 Page Number: 167 PDF Comment Subtype: PDF Comment Type: Locator: 8.3.1 Comment= "e) following an unsuccessful read operation or a successful write operation, while at beginning-of-partition, the device server shall report a density code value as described for item b);" Change Suggestion= "Believe this should be: e) following an unsuccessful read operation or an unsuccessful write operation, while at beginning-of-partition, the device server shall report a density code value as described for item b);" ------- Comment Number: HPQ-246 Page Number: 167 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.3.1 Comment= "At 7.63 in. down and 6.61 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-247 Page Number: 167 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.3.1 Table 93 Comment= "At 9.55 in. down and 0.24 in. from left Keep table 93 on one page" ------- Comment Number: HPQ-248 Page Number: 167 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.3.1 Table 93 Comment= "At 9.78 in. down and 1.26 in. from left Code value s/b Code" ------- Comment Number: HPQ-249 Page Number: 168 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.3.1 Table 94 Comment= "At 6.09 in. down and 0.28 in. from left SPC-4 claims that 0Ah/F1h is Parallel ATA Control and 0Ah/F2h is Serial ATA Control. I think those are incorrect; SAT does not define translation into SSC logical units, so SSC should not define those mode page codes as supported." ------- Comment Number: HPQ-250 Page Number: 168 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.3.1 Table 94 Comment= "At 6.86 in. down and 0.27 in. from left Mode page 10h/01h is not listed in SPC-4." ------- Comment Number: HPQ-251 Page Number: 168 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.3.1 Table 94 Comment= "At 7.22 in. down and 0.33 in. from left 11h/00h is called ""Medium Partition (1)"" in SPC-4" ------- Comment Number: HPQ-252 Page Number: 168 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.3.1 Table 94 Comment= "At 7.57 in. down and 0.35 in. from left 12h and 13h are not marked obsolete in SPC-4" ------- Comment Number: HPQ-253 Page Number: 168 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.3.1 Table 94 Comment= "At 7.93 in. down and 0.35 in. from left 14h/00h is labeled Enclosure Services Management in SPC-4" ------- Comment Number: HPQ-254 Page Number: 168 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.3.1 Table 94 Comment= "At 8.13 in. down and 0.76 in. from left 15h and 16h are not assigned for the SSC device type in SPC-4" ------- Comment Number: HPQ-255 Page Number: 168 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.3.1 Table 94 Comment= "At 8.68 in. down and 3.65 in. from left LUN s/b Logical Unit" ------- Comment Number: HPQ-256 Page Number: 168 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.3.1 Table 94 Comment= "At 8.77 in. down and 0.28 in. from left 18h and 19h with non-zero subpage codes are also assigned in SPC-4 for this device type" ------- Comment Number: HPQ-257 Page Number: 169 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.3.1 Table 94 Comment= "At 3.23 in. down and 0.53 in. from left 1Dh/00h is not in SPC-4" ------- Comment Number: HPQ-258 Page Number: 169 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.3.1 Table 94 Comment= "At 3.46 in. down and 1.17 in. from left 1Dh s/b 1Eh" ------- Comment Number: HPQ-259 Page Number: 174 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.3.3 Comment= "At 8.24 in. down and 3.40 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-260 Page Number: 175 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.3.3 Table 99 Comment= "At 8.91 in. down and 4.22 in. from left EOD DEFINED values s/b EOD DEFINED field definition" ------- Comment Number: HPQ-261 Page Number: 176 PDF Comment Subtype: PDF Comment Type: Locator: 8.3.3 Comment= The WORM Tamper Read Enable (WTRE) field specifies how the device server responds to detection of comprimised integrity ... Change Suggestion= The WORM Tamper Read Enable (WTRE) field specifies how the device server responds to detection of compromised integrity ... ------- Comment Number: HPQ-262 Page Number: 177 PDF Comment Subtype: PDF Comment Type: Locator: 8.3.3 Table 100 Code 00b Comment= The device server shall respond in a vendor-specific manner. Change Suggestion= The device server shall respond in a vendor specific manner. ------- Comment Number: HPQ-263 Page Number: 177 PDF Comment Subtype: PDF Comment Type: Locator: 8.3.3 Table 100 Code 01b Comment= Detection of comprimised integrity on a WORM medium shall not affect processing of a task. Change Suggestion= Detection of compromised integrity on a WORM medium shall not affect processing of a task. ------- Comment Number: HPQ-264 Page Number: 177 PDF Comment Subtype: PDF Comment Type: Locator: 8.3.3 Note 63 Comment= NOTE 63 An application client should set the WTRE field to 01b only for the recovery of data from a WORM medium where the integrity of the stored data has been comprimised. Change Suggestion= NOTE 63 An application client should set the WTRE field to 01b only for the recovery of data from a WORM medium where the integrity of the stored data has been compromised. ------- Comment Number: HPQ-265 Page Number: 177 PDF Comment Subtype: PDF Comment Type: Locator: 8.3.3 Comment= "Commands that shall not be effected by the OIR bit set to one are defined as Allowed in the presence of persistent reservations in table 14 or SPC-4, or are defined in SPC-2 as Allowed in the presence of reservations. Commands that shall be effected by the OIR bit set to one are defined as Conflict ..." Change Suggestion= "Commands that shall not be affected by the OIR bit set to one are defined as Allowed in the presence of persistent reservations in table 14 or SPC-4, or are defined in SPC-2 as Allowed in the presence of reservations. Commands that shall be affected by the OIR bit set to one are defined as Conflict ..." ------- Comment Number: HPQ-266 Page Number: 179 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.3.4 Comment= "At 8.60 in. down and 1.12 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-267 Page Number: 179 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.3.4 Comment= "At 10.24 in. down and 4.67 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-268 Page Number: 180 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.3.4 Comment= "At 2.48 in. down and 3.53 in. from left beginning-of-partition s/b BOP" ------- Comment Number: HPQ-269 Page Number: 181 PDF Comment Subtype: PDF Comment Type: Locator: 8.3.4 Comment= An ADDP bit of one and .. Change Suggestion= An additional partitions (??) (ADDP) bit of one and .. ------- Comment Number: HPQ-270 Page Number: 181 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.3.4 Table 104 Comment= "At 8.12 in. down and 3.74 in. from left Medium format recognition values s/b MEDIUM FORMAT RECOGNITION field definition" ------- Comment Number: HPQ-271 Page Number: 182 PDF Comment Subtype: PDF Comment Type: Locator: 8.3.4 Comment= "NOTE 68 It is recommended, but not required, that the number of partition size descriptors available through the Medium Partition mode page equal at least the number of maximum addition partitions + 1." Change Suggestion= "NOTE 68 It is recommended, but not required, that the number of partition size descriptors available through the Medium Partition mode page equal at least the number of maximum additional partitions + 1." ------- Comment Number: HPQ-272 Page Number: 185 PDF Comment Subtype: PDF Comment Type: Locator: 8.3.6 Comment= "Table 107 field 32767 Reads ""Activate all supported TapeAlert flags. Report the informational exception condition for the TapeAlert flag with an additional sense code of FAILURE PREDICTION THRESHOLD EXCEEDED (FALSE) and based on the DEXCPT, MRIE, INTERVAL TIMER, and REPORT COUNT values."" Change Suggestion= I believe the ""and"" is not needed after (FALSE). " ------- Comment Number: HPQ-273 Page Number: 185 PDF Comment Subtype: PDF Comment Type: Locator: 8.3.6 . Comment= if the DEXCPT bit is set to zero and the taser bit in the Device Configuration Extension mode page is set to zero . . Change Suggestion= if the DEXCPT bit is set to zero and the TASER bit in the Device Configuration Extension mode page is set to zero ------- Comment Number: HPQ-274 Page Number: 186 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.3.7 Table 108 Comment= "At 4.64 in. down and 1.54 in. from left Global (e.g. Table 108) Use 2 rows for Reserved" ------- Comment Number: HPQ-275 Page Number: 186 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.3.7 Table 109 Comment= "At 7.46 in. down and 1.30 in. from left Value s/b Code" ------- Comment Number: HPQ-276 Page Number: 187 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.3.7 Table 110 Comment= "At 2.46 in. down and 1.80 in. from left Value s/b Code" ------- Comment Number: HPQ-277 Page Number: 189 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.4.1 Table 113 Comment= "At 2.76 in. down and 0.41 in. from left Global used Mixed Case for VPD page names" ------- Comment Number: HPQ-278 Page Number: 189 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.4.1 Table 113 Comment= "At 4.32 in. down and 0.57 in. from left B3h Automation Device Serial Number is not listed in SPC-4" ------- Comment Number: HPQ-279 Page Number: 189 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.4.2 Comment= "At 8.99 in. down and 0.95 in. from left If the Write Once Read Many... s/b A Write Once Read Many bit set to one indicates that ... A WORM bit set to zero indicates that..." ------- Comment Number: HPQ-280 Page Number: 190 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.4.3 Comment= "At 5.49 in. down and 0.29 in. from left For the SERIAL NUMBER fields in 8.4.3 and 8.4.5: If the serial number is not available, wouldn't the device server just return a PAGE LENGTH of 0? How many spaces would it be expected to provide?" ------- Comment Number: HPQ-281 Page Number: 191 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.1 Comment= "Device Server -> Physical Device First paragraph first sentence - ""requests the device server to return information about the data security methods in the device server and on the medium.""" Change Suggestion= "Should be ""requests the device server to return information about the data security methods in the physical device and on the medium.""" ------- Comment Number: HPQ-282 Page Number: 192 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.1 Comment= "At 1.81 in. down and 0.45 in. from left Tape Data Encryption security protocol s/b 20h (i.e., Tape Data Encryption) (see SPC-4)" ------- Comment Number: HPQ-283 Page Number: 192 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.1 Table 118 Comment= "At 6.07 in. down and 1.40 in. from left 30h s/b 0030h" ------- Comment Number: HPQ-284 Page Number: 192 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.1 Table 118 Comment= "At 6.31 in. down and 1.40 in. from left 31h s/b 0031h" ------- Comment Number: HPQ-285 Page Number: 194 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.5.2.4 Table 121 Comment= "At 5.54 in. down and 5.89 in. from left Add ""(see table 124)"" in rows 20 and n" ------- Comment Number: HPQ-286 Page Number: 194 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.5.2.4 Table 121 Comment= "At 5.74 in. down and 0.74 in. from left This descriptor size is 24 bytes, so change first blank to 43 and the second to n - 23" ------- Comment Number: HPQ-287 Page Number: 194 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.4 Comment= "At 6.73 in. down and 3.30 in. from left field s/b field and the" ------- Comment Number: HPQ-288 Page Number: 194 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.4 Comment= "At 6.73 in. down and 5.02 in. from left page code s/b smallcaps" ------- Comment Number: HPQ-289 Page Number: 195 PDF Comment Subtype: 176 PDF Comment Type: Locator: "8.5.2.4 table 123, code 01b description" Comment= The physical device configured. Change Suggestion= change to: The physical device is configured.. ------- Comment Number: HPQ-290 Page Number: 195 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.5.2.4 Table 124 Comment= "At 6.63 in. down and 0.53 in. from left add vertical line in row 4 and 5" ------- Comment Number: HPQ-291 Page Number: 196 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.4 Comment= "Device Server -> Physical Device Second paragraph on page - ""The supplemental decryption key capable bit shall be set to one if the device server is capable . . . shall be set to zero if the device server is not capable""" Change Suggestion= "Should be - ""The supplemental decryption key capable bit shall be set to one if the physical device is capable . . . shall be set to zero if the physical device is not capable . . . """ ------- Comment Number: HPQ-292 Page Number: 196 PDF Comment Subtype: PDF Comment Type: Locator: "3rd parag., last line" Comment= """in any format that the device supports"" It is not clear whether this means ""any"" as in 1 or more, or ""any"" as in all." Change Suggestion= I believe this was supposed to mean : 1 or more supported formats. Change wording to clarify. ------- Comment Number: HPQ-293 Page Number: 196 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.4 Comment= "Device Server -> Physical Device Third paragraph on page - ""The distinguish encrypted data capable bit shall be set to one if the device server is capable of distinguishing encrypted data from unencrypted data when reading it from the medium. The DEC_C bit shall be set to zero if the device server is not capable . . . If no volume is mounted, the DEC_C bit shall be set to one if the device server is capable. . . """ Change Suggestion= "Should be ""The distinguish encrypted data capable (DED_C) bit shall be set to one if the physical device is capable of distinguishing encrypted data from unencrypted data when reading it from the medium. The DEC_C bit shall be set to zero if the physical device is not capable . . . If no volume is mounted, the DEC_C bit shall be set to one if the physical device is capable. . . """ ------- Comment Number: HPQ-294 Page Number: 197 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.4 Table 127 Comment= "At 5.91 in. down and 2.62 in. from left ecryption s/b encryption" ------- Comment Number: HPQ-295 Page Number: 197 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.4 Table 127 Comment= "At 6.31 in. down and 2.62 in. from left ecryption s/b encryption" ------- Comment Number: HPQ-296 Page Number: 197 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.4 Comment= "Device Server -> Physical Device Table 128 Items 1,2,3 all show nonce as part of device server when it has moved to the physical device" Change Suggestion= "1 - The physical device generates the nonce value. 2 - The physical device requires all of part . . . 3 - The physical device supports all of part of the nonce . . . does not include a nonce value descriptor, the physical device generates the nonce value." ------- Comment Number: HPQ-297 Page Number: 200 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.6 Comment= "At 5.52 in. down and 5.54 in. from left Set Data Encryption page. s/b Set Data Encryption page (see 8.5.3.2)." ------- Comment Number: HPQ-298 Page Number: 201 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.5.2.7 Table 132 Comment= "At 6.30 in. down and 0.63 in. from left Change 24..n Key-associated data descriptors list to: Key-associated data descriptor list (shaded or with double lines on top and bottom) 24 Key-associated data descriptor (first) ... Key-associated data descriptor (last) n" ------- Comment Number: HPQ-299 Page Number: 201 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.7 Comment= I_T nexus should be changed as per HPQ-105 - instances not marked in red as per earlier changes ------- Comment Number: HPQ-300 Page Number: 202 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.7 Comment= "At 5.57 in. down and 0.45 in. from left Change: If the VCELB_C bit is set to one in the Data Encryption Capabilities page, then the volume contains encrypted logical blocks (VCELB) bit shall be set to one when a mounted volume contains an encrypted logical block. The VCELB bit shall be set to zero if: a)the mounted volume does not contain any encrypted logical blocks; b)there is no volume mounted; or c)the VCELB_C bit in the Data Encryption Capabilities page is set to zero. to: A volume contains encrypted logical blocks (VCELB) bit set to one indicates that the mounted volume contains an encrypted logical block. A VCELB bit set to zero indicates that either: a)the mounted volume does not contain any encrypted logical blocks; b)there is no volume mounted; or c)the VCELB_C bit in the Data Encryption Capabilities page is set to zero." ------- Comment Number: HPQ-301 Page Number: 202 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.7 Comment= "Device Server -> Physical Device Paragraph following a/b/c list - ""The raw decryption mode disabled (RDMD) bit shall be set to one if the device server is configured to mark each encrypted record . . . """ Change Suggestion= "Should be ""The raw decryption mode disabled (RDMD) bit shall be set to one if the physical device is configured . . . """ ------- Comment Number: HPQ-302 Page Number: 202 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.7 Comment= "Device Server -> Physical Device fourth from last paragraph on page, near end of first sentence ""at the time the key was established in the device server""" Change Suggestion= "Should be ""at the time the key was established in the physical device""" ------- Comment Number: HPQ-303 Page Number: 202 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.7 Comment= "Device Server -> Physical Device Third from last paragraph on the page near end of first sentence ""when the key was established in the device server""" Change Suggestion= "Should be ""when the key was established in the physical device""" ------- Comment Number: HPQ-304 Page Number: 202 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.7 Comment= "Device Server -> Physical Device Next to last paragraph ""when the key was established in the device server""" Change Suggestion= "Should be ""when the key was established in the physical device""" ------- Comment Number: HPQ-305 Page Number: 202 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.7 Comment= "Device Server -> Physical Device Last paragraph ""when the key was established in the device server""" Change Suggestion= "Should be ""when the key was established in the physical device""" ------- Comment Number: HPQ-306 Page Number: 203 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.5.2.8 Table 134 Comment= "At 5.37 in. down and 0.85 in. from left It would be better to align the 8-byte LOGICAL OBJECT NUMBER field on an 8 byte boundary" ------- Comment Number: HPQ-307 Page Number: 203 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.7 Comment= "Device Server -> Physical Device First paragraph continued from previous page middle sentence ""when the key was established in the device server. In this case, the KEY DESCRIPTOR field shall be set to the nonce value established by the device server for use with the selected key.""" Change Suggestion= "Should be ""when the key was established in the physical device. In this case, the KEY DESCRIPTOR field shall be set to the nonce value established by the physical device for use with the selected key.""" ------- Comment Number: HPQ-308 Page Number: 204 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.8 Comment= "Device Server -> Physical Device Table 135 references the device server for determining the status of the logical blocks - should be the physical device." Change Suggestion= "Should be: 0h - The physical device is incapable . . . 1h - The physical device is capable of . . . 2h - The physical device has determined . . . 3h - The physical device has determined . . . 4h - The physical device has determined . . . " ------- Comment Number: HPQ-309 Page Number: 205 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.8 Comment= "Device Server -> Physical Device Table 136 references the device server for determining the status of the logical blocks - should be the physical device." Change Suggestion= "Should be: 0h - The physical device is incapable . . . 1h - The physical device is capable of . . . 2h - The physical device has determined . . . 3h - The physical device has determined . . . 4h - The physical device has determined . . . 5h - The physical device has determined . . . 6h - The physical device has determined . . . but the physical device is either not enabled . . . " ------- Comment Number: HPQ-310 Page Number: 206 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.9 Comment= "At 9.91 in. down and 1.19 in. from left ) s/b )," ------- Comment Number: HPQ-311 Page Number: 206 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.8 Comment= "Device Server -> Physical Device Fourth paragraph second sentence - ""The AUTHENTICATED field shall indicate the status of the authentication done by the device server . . . """ Change Suggestion= "Should be: ""The AUTHENTICATED field shall indicate the status of the authentication done by the physical device . . . """ ------- Comment Number: HPQ-312 Page Number: 206 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.2.8 Comment= "Device Server -> Physical Device 'Fifth paragraph second sentence - ""The AUTHENTICATED field shall indicate the status of the authentication done by the device server . . . """ Change Suggestion= "Should be: ""The AUTHENTICATED field shall indicate the status of the authentication done by the physical device . . . """ ------- Comment Number: HPQ-313 Page Number: 207 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.1 Comment= "At 2.31 in. down and 4.07 in. from left may be used by an application client to read s/b returns" ------- Comment Number: HPQ-314 Page Number: 207 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.10.1 Table 138 Comment= "At 5.55 in. down and 5.15 in. from left (n-9) s/b (n-13)" ------- Comment Number: HPQ-315 Page Number: 207 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.5.2.10.2 Comment= "At 5.88 in. down and 0.84 in. from left It would be better to add 2 reserved bytes before PUBLIC KEY LENGTH so the PUBLIC KEY field starts on byte 16 (dword aligned)" ------- Comment Number: HPQ-316 Page Number: 207 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.10.2 Comment= "At 9.68 in. down and 4.51 in. from left Bytes 14 through 269.. s/b The PUBLIC KEY field shall be set as follows: bytes 0 through 255 shall be set to the modulus n; and bytes 256 through 511 shall be set to the public exponent e." ------- Comment Number: HPQ-317 Page Number: 208 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.2.10.3 Comment= "At 2.14 in. down and 4.06 in. from left Bytes 14 through 146... s/b The PUBLIC KEY field shall be set to the ECC 521 public key..." ------- Comment Number: HPQ-318 Page Number: 208 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.3.1 Comment= "At 3.81 in. down and 4.76 in. from left Tape Data Encryption security protocol s/b 20h (i.e., Tape Data Encryption) (see SPC-4)" ------- Comment Number: HPQ-319 Page Number: 208 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.3.1 Comment= "Device Server -> Physical Device First paragraph first sentence - ""The SECURITY PROTOCOL OUT command specifying the Tape Data Encryption security protocol (i.e., 20h) is used to configure the data security methods in the device server and on the medium"" - data security methods are now in the physical device" Change Suggestion= "Change to "". . . is used to configure the data security methods in the physical device and on the medium""" ------- Comment Number: HPQ-320 Page Number: 209 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.5.3.2.1 Table 141 Comment= "At 6.69 in. down and 0.61 in. from left It may be better to start KEY on an 8-byte aligned boundary so any 8-byte fields contained within it (e.g. an ESP-SCSI payload) are naturally aligned." ------- Comment Number: HPQ-321 Page Number: 209 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.5.3.2.1 Table 141 Comment= "At 7.28 in. down and 0.51 in. from left Make same change as proposed in table 132 for how the descriptor list is described" ------- Comment Number: HPQ-322 Page Number: 210 PDF Comment Subtype: Underline PDF Comment Type: Underline Locator: 8.5.3.2.1 Comment= "At 1.82 in. down and 0.45 in. from left Second sentence on page, Replace: Support for scope values of PUBLIC and ALL I_T NEXUS are mandatory for device servers that support the Set Data Encryption page. with a column in table 142 showing Mandatory and Optional for each code" ------- Comment Number: HPQ-323 Page Number: 210 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.3.2.1 Table 142 Comment= "At 2.71 in. down and 4.06 in. from left scope s/b smallcaps" ------- Comment Number: HPQ-324 Page Number: 210 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.3.2.1 Comment= "At 4.93 in. down and 5.28 in. from left field.. delete extra ." ------- Comment Number: HPQ-325 Page Number: 210 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.3.2.1 Comment= "Device Server -> Physical Device Last paragraph on the page ""The raw decryption mode control (RDMC) field specifies if the device server shall mark each encrypted block""" Change Suggestion= "Should be "". . . if the physical device shall march each encrypted block""" ------- Comment Number: HPQ-326 Page Number: 211 PDF Comment Subtype: PDF Comment Type: Locator: "4th parag, 1st line, " Comment= I_T nexus change to I_T_L nexus again Change Suggestion= ------- Comment Number: HPQ-327 Page Number: 211 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.3.2.1 Comment= "Device Server -> Physical Device Table 144 - device server is marking encrypted blocks - should be physical device" Change Suggestion= "Should be: 00b - The physical device shall mark . . . 01b - Reserved 10b - The physical device shall mark . . . 11b - The physical device shall mark . . " ------- Comment Number: HPQ-328 Page Number: 211 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.3.2.1 Comment= "Device Server -> Physical Device Paragraph following a/b/c list "". . . the key sent in this page shall be added to the set of data encryption parameters used by the device server for the selected scope""" Change Suggestion= "Should be: "". . . the key sent in this page shall be added to the set of data encryption parameters used by the physical device for the selected scope""" ------- Comment Number: HPQ-329 Page Number: 212 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.5.3.2 Comment= "At 4.89 in. down and 0.24 in. from left Section 8.5.3.2 should include some references to 8.5.2.5 Data Encryption Management Capabilities, pointing out the relationship regarding the CKOD, CKORP, CKORL, LOCK, and the SCOPE fields and their _C counterparts." ------- Comment Number: HPQ-330 Page Number: 212 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.3.2.1 Comment= "Device Server -> Physical Device Table 145 - 2h should be updated to reflect data is encrypted in the physical device" Change Suggestion= "Should be: 2h - ENCRYPT - The physical device shall encrypt . . ." ------- Comment Number: HPQ-331 Page Number: 213 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.3.2.1 Comment= "Device Server -> Physical Device Table 146 - all fields have decryption occuring in the device server rather than the physical device" Change Suggestion= "Should be: 0h - DISABLE - Data decryption is disabled. If the physical device encounters . . . 1h - RAW - Data decryption is disabled. If the physical device encounters . . . 2h - DECRYPT - The physical device shall decrypt all data . . . 3h - MIXED - The physical device shall decrypt all data that is read from the medium that the physical device dtermines what encrypted . . . If the physical device encounters unencrypted data . . .""" ------- Comment Number: HPQ-332 Page Number: 214 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.3.2.1 Table 147 Comment= "At 3.21 in. down and 2.84 in. from left Make the descriptions in table 147 match the section header names 8.5.3.2.xx. the key to be used to encrypt or decrypt data. s/b a plain-text key a vendor-specific key reference. s/b a key reference. etc." ------- Comment Number: HPQ-333 Page Number: 214 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 8.5.3.2.1 item b) Comment= "At 8.41 in. down and 3.75 in. from left StrikeOut: ; - following and" ------- Comment Number: HPQ-334 Page Number: 214 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.3.2.1 Comment= "Device Server -> Physical Device Second paragraph following table 147 - ""If the ENCRYPTION MODE field is set to ENCRYPT then device server shall save . . .and associate them with every logical block that is encrypted with this key by the device server""" Change Suggestion= "Should be "". . . the physical device shall save . . .and associate them with every logical block that is encrypted with this key by the physical device""" ------- Comment Number: HPQ-335 Page Number: 214 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.3.2.1 Comment= "Device Server -> Physical Device Third paragraph following table 147 - ""If the ENCRYPTION MODE field is set to EXTERNAL the device server shall save . . .""" Change Suggestion= "Should be ""If the ENCRYPTION MODE field is set to EXTERNAL the physical device shall save . . .""" ------- Comment Number: HPQ-336 Page Number: 215 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 8.5.3.2.1 Comment= "At 8.48 in. down and 7.82 in. from left Item a) of last a/b/c list StrikeOut: , - following or" ------- Comment Number: HPQ-337 Page Number: 215 PDF Comment Subtype: PDF Comment Type: Locator: 8.5.3.2.1 Comment= "Device Server -> Physical Device Third paragraph ""if a nonce value descriptor (see 8.5.4.5) is included and the algorithm and the device server supports application client generated nonce values . . . and the encryption algorithm or the device server does not support . . . If the encryption algorithm or the device server request an application client generated nonce . . .""" Change Suggestion= "Should be ""if a nonce value descriptor (see 8.5.4.5) is included and the algorithm and the physical device supports application client generated nonce values . . . and the encryption algorithm or the physical device does not support . . . If the encryption algorithm or the physical device request an application client generated nonce . . .""" ------- Comment Number: HPQ-338 Page Number: 217 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.3.2.4.1 Table 150 Comment= "At 3.96 in. down and 4.29 in. from left LABEL LENGTH s/b LABEL LENGTH (n - 3)" ------- Comment Number: HPQ-339 Page Number: 217 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.5.3.2.4.1 Table 150 Comment= "At 4.81 in. down and 0.68 in. from left Could padding be included so the length fields are each aligned on 2 byte boundaries and so the key fields are each aligned on 4 byte boundaries?" ------- Comment Number: HPQ-340 Page Number: 217 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.3.2.4.1 Table 150 Comment= "At 4.90 in. down and 4.05 in. from left WRAPPED KEY LENGTH s/b WRAPPED KEY LENGTH (m - (n+2))" ------- Comment Number: HPQ-341 Page Number: 217 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.3.2.4.1 Table 150 Comment= "At 5.85 in. down and 4.14 in. from left SIGNATURE LENGTH s/b SIGNATURE LENGTH (z - (m+2))" ------- Comment Number: HPQ-342 Page Number: 218 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: 8.5.3.2.4.2 Comment= "At 5.65 in. down and 4.40 in. from left StrikeOut: (MGF) - in last sentence of first paragraph" ------- Comment Number: HPQ-343 Page Number: 218 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.3.2.4.2 Comment= "At 6.48 in. down and 0.94 in. from left LABEL s/b smallcaps" ------- Comment Number: HPQ-344 Page Number: 219 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.5.3.2.4.3 Table 152 Comment= "At 2.92 in. down and 0.85 in. from left Make table 152 wider so the 2nd column does not wrap" ------- Comment Number: HPQ-345 Page Number: 219 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.3.2.5 Comment= "At 9.38 in. down and 5.39 in. from left ESP-SCSI out w/o length descriptor should change to match the name used in SPC-4 (global)" ------- Comment Number: HPQ-346 Page Number: 220 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.5.3.3 Table 154 Comment= "At 5.47 in. down and 0.18 in. from left The ESP-SCSI out descriptor should start on a 4 or ideally 8 byte boundary so any fields contained within maintain their natural alignment." ------- Comment Number: HPQ-347 Page Number: 221 PDF Comment Subtype: Text PDF Comment Type: Note Locator: 8.5.4.2 Table 156 Comment= "At 6.08 in. down and 1.34 in. from left Add acronyms in table 156 U-KAD A-KAD M-KAD The use the acronyms in the 8.5.4.x section headers and text." ------- Comment Number: HPQ-348 Page Number: 221 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.4.2 Table 156 Comment= "At 6.59 in. down and 2.56 in. from left 04 s/b 04h" ------- Comment Number: HPQ-349 Page Number: 221 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.4.2 Table 157 Comment= "At 9.02 in. down and 5.11 in. from left authenticated s/b authentication" ------- Comment Number: HPQ-350 Page Number: 222 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: 8.5.4.5 Comment= "At 2.83 in. down and 1.77 in. from left descriptor s/b key descriptor" ------- Comment Number: HPQ-351 Page Number: 224 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: A.2 Table A.1 Comment= "At 9.86 in. down and 3.27 in. from left in footnote a) StrikeOut: in SCSI streaming devices" ------- Comment Number: HPQ-352 Page Number: 224 PDF Comment Subtype: StrikeOut PDF Comment Type: Cross-Out Locator: A.2 Table A.1 Comment= "At 10.02 in. down and 1.82 in. from left in footnote a) StrikeOut: to be used" ------- Comment Number: HPQ-353 Page Number: 230 PDF Comment Subtype: PDF Comment Type: Locator: "Annex B, B.1.1" Comment= "Meaning of ""they"" in 3rd sentence unclear" Change Suggestion= "replace ""that they use master data management servers"" with ""that master data management servers are used""" ------- Comment Number: HPQ-354 Page Number: 231 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: B.1.1 Comment= "At 1.64 in. down and 2.74 in. from left key manager s/b centralized key manager" ------- Comment Number: HPQ-355 Page Number: 231 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: B.1.1 Comment= "At 1.64 in. down and 3.60 in. from left master server s/b master data management server" ------- Comment Number: HPQ-356 Page Number: 231 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: B.1.1 item a) Comment= "At 2.48 in. down and 2.42 in. from left e.g. s/b e.g.," ------- Comment Number: HPQ-357 Page Number: 231 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: B.1.2 Table B.1 Comment= "At 6.30 in. down and 2.43 in. from left e.g. s/b e.g.," ------- Comment Number: HPQ-358 Page Number: 231 PDF Comment Subtype: Highlight PDF Comment Type: Highlight Locator: B.1.2 Table B.1 Comment= "At 7.03 in. down and 6.09 in. from left , s/b ;" ------- Comment Number: HPQ-359 Page Number: 233 PDF Comment Subtype: Text PDF Comment Type: Note Locator: C.1 Figure C.1 Comment= "At 9.96 in. down and 6.47 in. from left Delete extra lines in bottom right box in figure C.1" ************************************************************** Comments attached to No ballot from Kevin Butt of IBM Corp.: Comments on ssc3r04a.fdf IBM comment number 1 Page=2 Subtype=Highlight Author=kdbutt Comment= T10 Vice-Chair Change to Mark Evans IBM comment number 2 Page=4 Subtype=Highlight Author=Nakayama Comment= 06-453r0: It would be typo: '06-453r0', because '06-453r1' is available and the latest change is reflected to the r04a document. IBM comment number 3 Page=13 Subtype=Highlight Author=kdbutt Comment= DATA ENCRYPTION PARAMETERS FOR ENCRYPTION REQUEST POLICIES s/b Data encryption parameters for encryption request policies IBM comment number 4 Page=13 Subtype=Highlight Author=kdbutt Comment= DATA ENCRYPTION PARAMETERS FOR DECRYPTION REQUEST POLICIES s/b Data encryption parameters for decryption request policies IBM comment number 5 Page=13 Subtype=Highlight Author=kdbutt Comment= DATA ENCRYPTION PARAMETERS FOR ENCRYPTION REQUEST INDICATOR SETTINGS s/b Data encryption parameters for encryption request indicator settings IBM comment number 6 Page=13 Subtype=Highlight Author=kdbutt Comment= DATA ENCRYPTION PARAMETERS FOR DECRYPTION REQUEST INDICATOR SETTINGS s/b Data encryption parameters for decryption request indicator settings IBM comment number 7 Page=13 Subtype=Highlight Author=kdbutt Comment= DATA ENCRYPTION PERIOD TIMER EXPIRED INDICATOR s/b Data encryption period timer expired indicator IBM comment number 8 Page=13 Subtype=Highlight Author=kdbutt Comment= dest_type small caps IBM comment number 9 Page=14 Subtype=Highlight Author=kdbutt Comment= speed small caps IBM comment number 10 Page=14 Subtype=Highlight Author=kdbutt Comment= eod small caps IBM comment number 11 Page=14 Subtype=Highlight Author=kdbutt Comment= wtre small caps IBM comment number 12 Page=14 Subtype=Highlight Author=kdbutt Comment= rewind on reset small caps IBM comment number 13 Page=15 Subtype=Highlight Author=kdbutt Comment= worm mode label restrictions small caps IBM comment number 14 Page=15 Subtype=Highlight Author=kdbutt Comment= worm mode filemarks restrictions small caps IBM comment number 15 Page=15 Subtype=Highlight Author=kdbutt Comment= rdmc_c small caps IBM comment number 16 Page=15 Subtype=Highlight Author=kdbutt Comment= security protocol specific small caps IBM comment number 17 Page=24 Subtype=Highlight Author=kdbutt Comment= not coincide with s/b be different than IBM comment number 18 Page=24 Subtype=StrikeOut Author=kdbutt Comment= Not all parameters are accessible through the page IBM comment number 19 Page=24 Subtype=Highlight Author=kdbutt Comment= may be s/b is IBM comment number 20 Page=25 Subtype=Highlight Author=kdbutt Comment= not coincide with s/b be different than IBM comment number 21 Page=26 Subtype=Highlight Author=kdbutt Comment= 3.1.56 reservation loss: An event caused by the release of a reserve/release method reservation (see SPC-2) or by the transition within the device server from the state where a persistent reservation holder exists to the state where a persistent reservation holder does not exist (see SPC-4). Comment 1: add: A preempt of a reservation is not considered a reservation loss if a new reservation is created as part of that preempt. <, then " throughout instead of "if , as it appears here. The "then" helps set apart the action to take and make text consistent. (There are several instances throughout the standard missing the "then", so this comment will be the only mention of it). QTM-rbw-25 47 E 4.2.13.1 - Write protection of the medium prevents the alteration of logical objects on the medium and any change s/b ...medium, and any change... QTM-rbw-26 48 E If more than one condition exists, the device server shall either report the applicable condition in order of HARDWARE WRITE PROTECTED, PERMANENT WRITE PROTECT, PERSISTENT WRITE PROTECT, ASSOCIATED WRITE PROTECT, and LOGICAL UNIT SOFTWARE WRITE PROTECTED, or report the generic additional sense code of WRITE PROTECTED. Make this a numbered list. QTM-rbw-27 48 E a) the format on the current medium is read-only by the device server; s/b ...medium is maintained as read-only... QTM-rbw-28 48 c) the medium is an archive tape Definition or reference for 'archive tape'? QTM-rbw-29 49 E 4.2.13.3 - Software write protection for the device server controls write protection for the device server. (this statement seems circular; better wording?) QTM-rbw-30 49 E 4.2.13.3 - The state of each control bit shall be set to its default state after a logical unit reset. Where is the default state specified? QTM-rbw-31 50 E Table 7 ' Commands providing progress indication without changing ready state Needs (Continued) for split table QTM-rbw-32 51 f) an application client shall specify a Command Reference Number (see SAM-3) for each command in a tagged write sequence. Would suggest rewording in terms of the device server to avoid placing requirement on application client (e.g., device shall expect and check a CRN...) QTM-rbw-33 51 E When operating in implicit address mode, spacing operations and commands to read and write on s/b ...read from and write on... QTM-rbw-34 51 E When operating in explicit address mode, commands to read and write on the s/b ...read from and write on... QTM-rbw-35 52 E A common command containing a BAM bit Should this be "a generic command"? (two places) QTM-rbw-36 53 T So there's no way to return to A0 from F0, E0, or E1? QTM-rbw-37 55 f) an explicit command is enabled and the medium position is not at BOx. In this case the device server shall This doesn't seem like normal lettered list formatting, as it doesn't read like a single, semi-colon delimited sentence. The "In this case" statements break the pattern. (several) QTM-rbw-38 60 E Transition All:F0: This transition shall occur when a power-on, logical unit reset, ot I_T nexus loss s/b of I_T nexus QTM-rbw-39 61 E TapeAlert flags fall into three categories of default severity (see table 9). There are six categories shown in table 9. QTM-rbw-40 61 E The event that generated this device information may be retried. s/b The event that generated this information... QTM-rbw-41 61 E The systme may not s/b The system... QTM-rbw-42 61 E The condition should be logged and/or the operator informed (missing period at end) QTM-rbw-43 61 T Not all six severities are used in Table 10 QTM-rbw-44 62 E Table 10 specifies the 64 TapeAlert flags for a sequential-access device. See Annex A for additional information about each TapeAlert flag.l (trailing I after period) QTM-rbw-45 62 E Severity The single letters for severity are not defined in the table footer and need to be. QTM-rbw-46 64 T Should we add TA flags for data encryption/decryption errors? QTM-rbw-47 64 E establish an Informational s/b establish and informational QTM-rbw-48 64 E more TapeAlert flags; and s/b flags; or QTM-rbw-49 65 E (e.g. polled at a regular interval of 60 seconds). s/b (e.g., QTM-rbw-50 65 E a) priot to s/b prior QTM-rbw-51 65 E that an informational exception has occurred. s/b ...informational exception condition... QTM-rbw-52 65 E flags appears in the Information sense data descriptor s/b information sense QTM-rbw-53 66 E not wish to receive a unit attention condition (see 8.2.3) s/b (see 8.2.3); and QTM-rbw-54 66 E d) establishing a threshold value and a threshold met criteria (tmc) value for each TapeAlert log page parameter with the etc bit set to one s/b TMC (small caps); ETC (small caps) QTM-rbw-55 66 E de-activation. de-activation or deactivation? (consistency) QTM-rbw-56 66 E in the Information sense information sense QTM-rbw-57 66 E the PCR field set to one (is PCR a field or bit?) QTM-rbw-58 67 E NOTE 7 The device server deactivating TapeAlert flags on any basis other than per I_T nexus, if the TAPLSD bit is set to zero, violates backwards compatibility with previous versions of this standard. suggest: If the TAPLSD bit is set to zero, then if the device server deactivates TapeAlert flags on any basis other than per I_T nexus violates backwards compatibility with previous versions of this standard. QTM-rbw-59 67 T In addition to the deactivation conditions for all TapeAlert flags (see 4.2.17.3), the device server shall activate s/b ...shall deactivate... QTM-rbw-60 67 E execution of an autoload operation s/b b) execution (i.e., format as item b of list) QTM-rbw-61 67 E are not affected by port events s/b SCSI port events QTM-rbw-62 67 E requiring the application client to maintain at least one previously retrieved TapeAlert Response log page in order to detect differences. Suggest converting this to an "e.g.," since this is not the only way of accomplishing this (and doesn't place a requirement on the client). QTM-rbw-63 68 E A value of 0h specifies that s/b 0h indicates that QTM-rbw-64 68 E The use of specific vendor identification other than the one associated with the device is allowed. s/b A vendor identification other than the one associated with the device may be used. QTM-rbw-65 68 E (Flag 1 = MSB, Byte 1; Flag 64 = LSB, Byte 8). s/b (i.e., Flag 1 = MSB, byte 1; Flag 64 = LSB, byte 8). QTM-rbw-66 68 E The bits specify all the TapeAlert flags that were set during the previous load, (i.e., the bits are “sticky” for the load). s/b ...that were set to one during... (and) (i.e., the bits remain set to one for the duration of the load). QTM-rbw-67 69 E A value of 0h specifies s/b 0h indicates QTM-rbw-68 69 E when a registrants only or all registrants persistent s/b ...or an all... QTM-rbw-69 69 E Need table footer on first page too. QTM-rbw-70 70 E commands by the devices server. s/b device server QTM-rbw-71 71 E While in WORM mode, WRITE, WRITE FILEMARKS, ERASE, FORMAT MEDIUM, SET CAPACITY, and MODE SELECT commands need to expand to WRITE(6), WRITE(16), WRITE FILEMARKS(6)/(16), ERASE(6)/(16). QTM-rbw-72 71 E determine if medium s/b determine if a medium QTM-rbw-73 72 T 4.2.21.3, 4th para, 4th sentence: If the device server is capable of determining that the encryption s/b determining that the decryption QTM-rbw-74 72 E or MIXED, but all of the keys s/b MIXED, and all QTM-rbw-75 72 E encrypted block, shall cause s/b encrypted block shall cause QTM-rbw-76 72 E DECRYPT or MIXED but the data fails s/b MIXED and the QTM-rbw-77 73 E A device server that is capable of distinguishing encrypted blocks from unencrypted blocks and has been configured to decrypt the data should perform at least one of the following for each encrypted block that is decrypted: suggest: For each encrypted block that is decrypted, a device server that is capable of distinguishing encrypted blocks from unencrypted blocks and has been configured to decrypt the data should: QTM-rbw-78 73 T A device server that is capable of both determining if the encryption s/b For each encrypted block, a device server... QTM-rbw-79 73 T encryption algorithm being broken What does "being broken" mean? QTM-rbw-80 73 T This condition shall persist until the volume is demounted or a hard reset condition occurs. Comment: Someone that has enough control to be setting encryption parameters and sending keys to try certainly has the ability to demount/remount a volume or instigate a hard reset. As such, is this mechanism really providing much value? QTM-rbw-81 74 E DECRYPTION MODE field is set to RAW s/b field set to RAW QTM-rbw-82 74 E is set to 10b: s/b is set to 10b, then: QTM-rbw-83 75 E The physical device also may have limited resources for storage of keys. (strike this sentence, as it doesn't specify anything). QTM-rbw-84 75 E A device server that supports encryption s/b ...that supports data encryption... QTM-rbw-85 75 T The method by which keys and their associated vendor-specific key references are made available to the device server is outside the scope of this standard. (Isn't this the SPOUT command and Tape Data Encryption protocol?) QTM-rbw-86 75 E and the device server experiences a reservation loss what does it mean for a device server to "experience" a reservation loss? QTM-rbw-87 76 The first three pairs of lettered lists on this page should be numbered lists (i.e., release the resources before establishing) QTM-rbw-88 76 E key), at the physical device s/b and the physical device QTM-rbw-89 76 T After a vendor-specific event, doesn't the physical device still need to release resources? QTM-rbw-90 77 E If an I_T nexus data encryption scope is set to PUBLIC it indicates the physical device does not have a saved set of data encryption parameters that were established by that I_T nexus. Device servers that support encryption s/b An I_T nexus data encryption scope set to PUBLIC indicates that the physical device does not have a saved set of data encryption parameters that were established by that I_T nexus. Device servers that support data encryption QTM-rbw-91 78 E A physical device may have limited resources for storage of sets of data encryption parameters (i.e., it may not have enough resources to store a unique set of data encryption parameters for every I_T nexus that it is capable of managing). This sentence should be removed since it doesn't specify anything. However, if not removed, then the 'may' should be changed since it is not granting permission to have limited resources. QTM-rbw-92 78 E some values which may be changed s/b values that may be QTM-rbw-93 78 E d) other vendor-specific data encryption capabilities. (need to increase font size) QTM-rbw-94 79 E an application client which cause the physical s/b client that cause QTM-rbw-95 79 E The device server reports its capability with respect to nonce values s/b The device server reports its nonce value capability in... QTM-rbw-96 79 E additional data which is associated s/b data that is QTM-rbw-97 79 T plaintext, What is plaintext? QTM-rbw-98 79 E but which is not encrypted. s/b but that is not QTM-rbw-99 79 E It may be authenticated s/b to what is 'it' referring? QTM-rbw-100 80 E key-associated data to be protected s/b data to be authenticated QTM-rbw-101 80 E Some encryption algorithms allow or require the use of additional data which is associated s/b Some data encryption... ...data that is... QTM-rbw-102 80 E If a supported encryption algorithm has been disabled then: s/b ...has been disabled, then: QTM-rbw-103 81 T NOTE 13 The SECURITY PROTOCOL IN command specifying the Tape Data Encryption security protocol and the Data Encryption Status page may be used to determine whether external data encryption control has been used to provide a set of data encryption parameters. Limited to just provide, or includes establish, change, or control? (as in previous wording) QTM-rbw-104 81 T 4.2.22.3.1 - Numbered list should be lettered list. QTM-rbw-105 82 E if running in unbuffered, s/b in unbuffered mode, QTM-rbw-106 82 E when the operation will not be ('will' is not an allowed standards term) QTM-rbw-107 83 E encryptionparameters s/b encryption parameters QTM-rbw-108 83 E from a entity using s/b from an entity QTM-rbw-109 84 E shall be set to defaults on: a) a hard reset condition; b) a volume is demounted; c) a data encryption parameters request period timeout (see 4.2.22.3.4); or d) successfully processing s/b shall be set to defaults: a) on a... b) when a... c) after a... d) after a... QTM-rbw-110 84 E The data encryption parameters period settings shall contain a data encryption parameters period time, a data encryption period timer, and a data encryption parameters period expired indicator. (make into a lettered list) QTM-rbw-111 85 T then the device server shall respond to a SECURITY PROTOCOL IN command specifying the Tape Data Encryption security protocol and the Data Encryption Status page with the PARAMETERS CONTROL field set to 011b or 100b. Respond with what? QTM-rbw-112 86 E such as key wrapping and/or securing the channel used to transmit the key. s/b (e.g., key wrapping...). QTM-rbw-113 86 E While these public keys are not secret, the device server shall maintain the authorization white list in a way that will prevent an attacker from modifying a public key or even injecting his own (such operations will grant the attacker the ability to send wrapped keys to the device server). s/b While these public keys are not secret, the device server shall maintain the authorization white list in a way that prevents an attacker from modifying or adding a public key (e.g., such operations may grant the attacker the ability to send wrapped keys to the device server). QTM-rbw-114 86 E A volume contains no encrypted s/b A volume contains either no encrypted... QTM-rbw-115 87 E The logical position following the completion of a self-test is not specified by this standard. See SPC-4. s/b The logical position following the completion of a self-test (see SPC-4) is not specified by this standard. QTM-rbw-116 87 E CbCS is a credential-based system that manages access to a logical unit or a volume. See SPC-4. s/b CbCS (see SPC-4) is a credential-based system that manages access to a logical unit or a volume. QTM-rbw-117 87 E shalll s/b shall QTM-rbw-118 89 E The following command codes Should command codes be opcodes? (as in table 21). (same comment for 6.1) QTM-rbw-119 124 T The PREVENT ALLOW MEDIUM REMOVAL command (see table 44) requests that the logical unit enable or disable the removal of the medium. Wouldn't it be more accurate to say 'removal of the volume' since that is the physical carrier of the medium? Could add a sentence to say removal includes volume. QTM-rbw-120 124 E Medium removal shall be prohibited. s/b shall be prevented. QTM-rbw-121 124 T The prevention of medium removal shall begin when any application client issues a PREVENT ALLOW MEDIUM REMOVAL command with a PREVENT field of 01b (i.e., medium removal prevented). Suggest stating that it begins after device server successfully processing command QTM-rbw-122 124 T receipt of a PREVENT ALLOW MEDIUM REMOVAL command with a PREVENT field of 00b; Suggest rewording as device server successfully processing command. Also need an 'or' after this A) item (indented list) QTM-rbw-123 124 E B) an I_T nexus loss; or s/b B) an I_T nexis loss; QTM-rbw-124 124 E If possible, the device server shall perform an synchronize cache operation before terminating the prevention of medium removal. remove sentence QTM-rbw-125 124 E with the PREVENT field set to zero s/b set to 00b QTM-rbw-126 124 E for each the I_T nexuses s/b for each I_T nexus QTM-rbw-127 124 E function for an initiator port s/b for a SCSI initiator port QTM-rbw-128 124 E allow removal of the medium by an operator. s/b removal of the volume by an operator. QTM-rbw-129 129 E if the PEWS field (see 8.3.8) is set to zero. Global comment: The use of 'zero' and 'one' should be limited to bit values. Field values should have notation such as 00h or 0000h (field size dependent). QTM-rbw-130 129 E the PARTITION NUMBER field shall be set to zero. s/b 00h QTM-rbw-131 137 E A WRTOK bit spell out QTM-rbw-132 137 E A DUP bit spell out QTM-rbw-133 137 E A DEFLT bit spell out QTM-rbw-134 137 E If the Descriptor Length Valid (DLV) s/b If the descriptor length valid (DLV) QTM-rbw-135 139 E (MSB) Remove all MSB and LSB from the primary density codes field, as it has subfields. QTM-rbw-136 139 E Add MSB and LSB to the last three fields in table 57, since they do not have subfields. QTM-rbw-137 139 E shall contain zero. s/b 00h QTM-rbw-138 140 E any document that specifies a characteristics s/b that specifies characteristics QTM-rbw-139 147 T What is the parameter format for the log page specified in 8.2.2? Seems to be missing (e.g., what size are the parameters?) QTM-rbw-140 156 E The PRODUCT REVISION LEVEL field shall contains the s/b shall contain the QTM-rbw-141 156 E The OPERATION CODE field and SERVICE ACTION field if applicable contain s/b The OPERATION CODE field and SERVICE ACTION field, if applicable, contain QTM-rbw-142 156 E If medium was present at the time s/b If a medium... QTM-rbw-143 156 T 1) the BARCODE field... This should be a lettered list. QTM-rbw-144 157 E Flag Number s/b flag number QTM-rbw-145 157 E a Log Select command. s/b a LOG SELECT command. QTM-rbw-146 157 E the REPORT TIMESTAMP parameter s/b the REPORT TIMESTAMP command parameter QTM-rbw-147 159 E DEVICE SERVERITY s/b DEVICE SEVERITY QTM-rbw-148 159 T The DEVICE SEVERITY CODE field is specified in table 9. Table 9 specifies the TapeAlert flag severities; suggest dropping 'DEVICE' from this field name (as well as similar in table 82) to make common. QTM-rbw-149 160 E The DEVICE ELEMENT CODE TEXT (DECT) field s/b The device element code text (DECT) field QTM-rbw-150 160 E in prioritized order.. (remove extra period) QTM-rbw-151 160 E VOLUME SERVERITY s/b VOLUME SEVERITY QTM-rbw-152 161 T The VOLUME SEVERITY CODE field is specified (see previous comment on table 79) QTM-rbw-153 161 E The VOLUME INFORMATION CODE (VIC) field is specified in table 80. s/b table 83. QTM-rbw-154 161 E specified in table 84.. (remove extra period) QTM-rbw-155 161 T The VOLUME IDENTIFICATION LENGTH field specifies the length of the volume identification descriptors. The length of one descriptor or all of them? QTM-rbw-156 161 E If the volume information descriptor is returned s/b If a volume... QTM-rbw-157 161 T 1) a MAM attribute... This should be a lettered list. QTM-rbw-158 163 E server may set the rrqst bit to one (rrqst needs small caps) QTM-rbw-159 164 T If the INTXN bit in the VHF data descriptor of the DT Device Status log page (see ADC-2) is set to one, the parameter shall report only code 00h (i.e., Recovery not requested). This appears to be a problem, as this bit is controlled by another device server (i.e., ADC not SSC). How can one device server qualify the behavior f another? Need to move into physical device? QTM-rbw-160 164 E recovery requested, s/b Recovery requested QTM-rbw-161 164 T Table 89 ' Recovery procedures How do these recovery procedure requests interact with the ADC recovery requests? May not want the ADC and SSC requests to conflict or collide. Model clause needed? QTM-rbw-162 165 E Table 89 ' Recovery procedures need (Continued) on split table QTM-rbw-163 165 E a volume. contact s/b volume. Contact QTM-rbw-164 165 T and the RRQST bit in the VHF data descriptor of the DT Device Status log page (see ADC-2) is set to zero, Same as previous comment on inter-device server interaction. Two more places following also. QTM-rbw-165 165 E then the application client shall not issue a load or unload command Should reword so as to not place requirement on client, but on device server. QTM-rbw-166 165 E Issue UNLOAD command; Instruct s/b command. Instruct QTM-rbw-167 168 E Table 93 ' Sequential-access density codes need (Continued) on split table QTM-rbw-168 169 E Table 94 ' Mode page codes and subpage codes need (Continued) on split table QTM-rbw-169 175 E A REW bit of one specifies (combine with previous paragraph) QTM-rbw-170 184 E Table 71 defines the s/b Table 107 QTM-rbw-171 187 E A TapeAlert Prevent LOG SENSE Deactivation (TAPLSD) bit s/b A TapeAlert prevent LOG SENSE deactivation... QTM-rbw-172 187 E A TapeAlert Respect Page Control (TARPC) s/b A TapeAlert respect page control... QTM-rbw-173 188 E A TapeAlert Select Exception Reporting (TASER) bit s/b A TapeAlert select exception reporting... QTM-rbw-174 188 E A TapeAlert Respect Parameter Fields (TARPF) s/b A Tapealert respect parameter fields... QTM-rbw-175 188 E The Programmable Early Warning Size (PEWS) s/b The programmable early warning size... QTM-rbw-176 188 E (VCELBRE) bit is set set to s/b is set to QTM-rbw-177 188 E VCELBRE bit is set to zero then s/b is set to zero, then QTM-rbw-178 189 E If the Write Once Read Many (WORM) bit s/b the write once read many QTM-rbw-179 191 T via the Automation Device Serial Number subpage, see ADC-3), This is no longer a valid reference. QTM-rbw-180 195 E UKADF AKADF needs separator bar QTM-rbw-181 196 E Name capitalize the name first letter (i.e., No, Software, Hardware, Capable) QTM-rbw-182 196 E has no has data decryption s/b has no data QTM-rbw-183 197 E Name same comment as table 125 QTM-rbw-184 197 E device has no has data encryption s/b has no data QTM-rbw-185 197 E ecryption s/b encryption (two places) QTM-rbw-186 198 E Fixed s/b fixed (two places) QTM-rbw-187 199 E SECURITY ALGORITHM CODE field contains an security algorithm s/b contains a security algorithm QTM-rbw-188 202 T Table 133: 011b Data encryption parameters are not exclusively controlled by the automation/drive interface device server. 100b Data encryption parameters are not exclusively controlled by a management interface. These should both be "are exclusively controlled" QTM-rbw-189 208 E The SECURITY PROTOCOL (fix the font on 'The') QTM-rbw-190 213 E deevice s/b device QTM-rbw-191 215 E RAW; or, s/b RAW; or QTM-rbw-192 219 E w/o Is this correct? ************************************************************** Comments attached to Abs ballot from Michael Rogers of Samsung: Not materially affected by this proposal. ************************************************************** Comments attached to Abs ballot from Gerald Houlder of Seagate Technology: Seagate is not materially affected by this standard. ************************************************************** Comments attached to No ballot from Roger Cummings of Symantec: 1 (tech) Page: xviii Location: Foreword Problem Description: In the second paragraph, the name of the field and the structure containing it are incorrect, and the reference should be to the published SAM-3. Suggested Solution: This standard specifies the external behavior of a device server that defines itself as a sequential-access device in the PERIPHERAL DEVICE TYPE field of the standard INQUIRY data. This device type is known as a stream device. This standard conforms to ANSI INCITS 402-2005, SCSI Architecture Model - 3. 2 (tech) Page: xviii Location: Foreword Problem Description: The foreword contains a conformance statement that does not occur anywhere else in the text. Suggested Solution: Add a sentence to the first paragraph of 1 Scope that reads "The definitions in this standard conform to the requirements of SAM-3." 3 (tech) Page: 1 Location: Scope Problem Description: The reference to the Inquiry field in item a) of the list is incorrect. Suggested Solution: a) permit an application client to communicate over a SCSI service delivery subsystem, with a logical unit that declares itself to be a sequential-access device in the PERIPHERAL DEVICE TYPE field of the standard INQUIRY data (see SPC-3); 4 (edit) Page: 1 Location: Figure 1 Problem Description: Correct the label "Shared Command Set (for all device types)" to match the text used in other standards. Suggested Solution: Primary Command Set (for all device types) 5 (tech) Page: 3 Location: 2 Normative References Problem Description: Add ADC-2, PKCS #1, ANSI X9.63, ISO/IEC 18033-2 to the list of references (ADC is referenced in 4.2.3 & Table 2, PKCS in 8.5.2.10.2, ECC & ANSI X9.63 in 8.5.2.10.3, ISO/IEC 18033-2 in 8.5.3.2.4.3) Suggested Solution: Add references 6 (tech) Page: 5 Location: 3.1.3 Auxiliary memory Problem Description: Delete the definition of auxiliary memory. Wherever the term is used in the document its preceded by "medium" and there's already a definition for that. Suggested Solution: Delete the definition. 7 (tech) Page: 7 Location: 3.1.44 medium auxiliary memory (MAM) Problem Description: This definition should reference the definition in SPC-4. Suggested Solution: An auxiliary memory residing on a medium that is accessible to the device server (e.g., a tape cartridge). See SPC-4. 8 (tech) Page: 7 Location: 3.1.51 page Problem Description: The page definition should be the same as, and should reference, SPC-3. Suggested Solution: page: A regular parameter structure (or format) used by several commands. These pages are identified with a value known as a page code. (see SPC-4) 9 (edit) Page: 7 Location: 3.2 Acronyms Problem Description: Add the following acronyms Suggested Solution: ADC Automation Device Control, PEWZ , SDK, RSA, ECC 10 (edit) Page: 15 Location: Figure 3 Problem Description: Ther terms BOM & EOM (and BOP & EOP) are used throughout this section, but are never fully defined. Suggested Solution: Spell out acronym on first usage. 11 (edit) Page: 17 Location: 4.2.3 Physical Device Problem Description: The reference SSC & ADC in item a) is very cryptic and needs to be expanded. Suggested Solution: (e.g. where a physical device is associated with a auotmation device that can perform media movement, both a device server that implement the commands set defined in this standard and a device server that impements another command set such as ADC-2 may control the device); 12 (edit) Page: 18 Location: Figure 8 Problem Description: The names in three of the boxes have been cropped. Suggested Solution: Correct 13 (edit) Page: 20 Location: 4.2.5 Problem Description: Define PEWZ on first usage. Suggested Solution: 14 (edit) Page: 21 Location: 4.2.6 Partitions within a volume Problem Description: Use (n) for the partition number to avoid confusion with Box & EOx. Suggested Solution: Each partition (n) within a volume has a defined beginning-of-partition (BOP n), an early-warning position (EW n), and an end-of-partition (EOP n). 15 (edit) Page: 22 Location: 4.2.7.1 Logical objects within a partition Problem Description: Use (n) for the partition number to avoid confusion with Box & EOx. Suggested Solution: The area between BOP n and EOP n. 16 (edit) Page: 52 Location: 4.2.21.1 Data Encryption Problem Description: Change the red text in this section to black. Suggested Solution: 17 (edit) Page: 52 Location: 4.2.21.1 Data Encryption Problem Description: The first sentence of this section is prone to giving the erroneous impression that a device can decypt the contents of a logical block on the media and replace the block on the media with unencrypted information, and thus needs clarification. Suggested Solution: A device compliant with this standard may contain hardware or software that is capable of encrypting the data within logical blocks as those blocks are stored on the media, and decrypting the data within logical blocks as those blocks are read from the media, to provide security against unauthorized access to that data. 18 (edit) Page: 53 Location: 4.2.21.3 Reading encrypted blocks Problem Description: "shall be vendor specific" is oxymoronic Suggested Solution: "is vendor specific" 19 (tech) Page: 54 Location: 4.2.21.5 Keyless copy Problem Description: This section should identify: a) How an application client determines that a Logical Unit has the capability to act as a KCSLU or a KCDLU; b) How an application client enables or disables this capability; Suggested Solution: 20 (edit) Page: 57 Location: 4.2.21.7 Saved Information Problem Description: This section needs to be moved to the end of section 4.21 so that it occurs after concepts such as lock & key instance counter have been defined. Suggested Solution: Move section 21 (edit) Page: 58 Location: 4.2.21.8 Data encryption parameters Problem Description: This section needs to be moved to the end of section 4.21 so that it occurs after concepts such as KAD & Nonce have been defined. Suggested Solution: Move section 22 (edit) Page: 61 Location: 4.2.22 External data encryption control Problem Description: This section should identify how an application client determines that a physical device has the capability for external data encryption control BEFORE it happens. Suggested Solution: 23 (tech) Page: 61 Location: 4.2.22 External data encryption control Problem Description: The interaction between this feature and the encryption mode locking defined in 4.2.21.11 needs to be defined. Specifically, can a lock be placed when the data encryption paremeters are under external control? Suggested Solution: 24 (edit) Page: 66 Location: 4.2.22.5 External data encryption control error conditions Problem Description: Change reference to ADC-2 for consistency with the rest of the document. Suggested Solution: (see ADC-2) 25 (edit) Page: 175 Location: 8.5.2.4 Data Encryption capabilities page Problem Description: I don't believe that this page "requests that information." Us the same format as for the other pages. Suggested Solution: Table 121 specifies the format of the Data Encryption Capabilities page. The page reports information on the set of data encryption algorithms supported by this device server. If external data encryption control is supported, then the set of data encryption algorithms reported by the device server may not include all of the algorithms in the set of data encryption algorithms supported by the physical device. 26 (edit) Page: 176 Location: Table 124 Problem Description: There is a vertical divider missing between UKADF & AKADF Suggested Solution: Insert 27 (edit) Page: 178 Location: Table 127 Problem Description: Typo "ecryption" Suggested Solution: Correct 28 (edit) Page: 178 Location: Table 128 Problem Description: Show the code in this table using binary notation as per the other two tables on this page. Suggested Solution: Correct 29 (edit) Page: 191 Location: Table 142 Problem Description: Show the code in this table using binary notation as per the other two tables on this page. Suggested Solution: Correct 30 (edit) Page: 201 Location: 8.5.4.1 Problem Description: typo "Pages in used" Suggested Solution: Delete "in" ************************************************************** Comments attached to Abs ballot from Dan Gorenc of TycoElectronics: No objections, just doesn't affect connectors. ******************** End of Ballot Report ********************