From Alvin.Cox at seagate.com Wed Dec 2 07:46:53 2009 From: Alvin.Cox at seagate.com (Alvin.Cox at seagate.com) Date: Wed, 2 Dec 2009 09:46:53 -0600 Subject: Reminder: SAS PHY teleconference 12/3/09, 10:00 am CST Message-ID: Formatted message: HTML-formatted message Toll Free Dial in Number: (877)810-9442 International Access/Caller Paid Dial In Number: (636)651-3190 PARTICIPANT CODE: 3243413 Webex information: https://seagate.webex.com Topic: SAS-2.1 PHY WG Date: Thursday, Dec 3, 2009 Time: 10:00 am, Central Standard Time Meeting number: 826 515 680 Password: newsas Agenda: SAS 2.1 Upgrade the Touchstone reference to version 2.0 (Modify the .s4p files included with the standard to comply with version 2.0.) [Fromm] Tbd???s for microSAS [Cox] Mini SAS HD numbering and lane location [Cox/Molex] Section 5.6.6.3. The SCD11 and SCD22 limits SCDxx Limit Proposal for Active Cables in SAS-2.1 (10-001r0) [Oganessyan] Reference Transmitter Device Termination (TxRefTerm.s4p) and the Reference Receiver Device Termination (RxRefTerm.s4p) to be used in the SAS-2.1 Annex C StatEye code. But it is not. [Newman, Witt] New LB comment discussion items [Cox] SAS 3 Recommend 64/66 encoding for SAS 3.0 (09-407) [Felton] Alvin Cox Seagate Technology, LLC Office 405-392-3738 Cell 405-206-4809 E-Mail alvin.cox at seagate.com From keiji_katata at post.pioneer.co.jp Wed Dec 2 23:26:43 2009 From: keiji_katata at post.pioneer.co.jp (keiji_katata at post.pioneer.co.jp) Date: Thu, 3 Dec 2009 16:26:43 +0900 Subject: Reminder: Fuji reflector/ftp suspend notice Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * keiji_katata at post.pioneer.co.jp * Here are two items. 1st item: Fuji reflector will stop from 12/3 to 12/15. 2nd item: Sorry I did not work for ODD Zero Power Effort description in Fuji. Anyway I did not receive proposal or comment. So after recovery of Fuji reflector, I would like to send chair's proposal to all. Best regards, Keiji Katata PIONEER CORP. keiji_katata at post.pioneer.co.jp@avc-pioneer.com on 2009/11/06 11:36:40 mtfuji5 at avc-pioneer.com$B$KJV?.$7$F$/$@$5$$(B $BAw?.(B: [MtFuji] Fuji reflector/ftp suspend notice Hello all, Fuji servers and I will move office at 12/3 (Japan time). Therefore two weeks from 12/3 to 12/15, Fuji reflector and ftp will be suspended. Best regards, Keiji Katata PIONEER CORP. * * For T10 Reflector information, send a message with * 'info t10' (no quotes) in the message body to majordomo at t10.org From Alvin.Cox at seagate.com Thu Dec 3 14:09:55 2009 From: Alvin.Cox at seagate.com (Alvin.Cox at seagate.com) Date: Thu, 3 Dec 2009 16:09:55 -0600 Subject: PHY teleconference minutes posted Message-ID: Formatted message: HTML-formatted message Today's call minutes posted at: http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-003r0.pdf Alvin Cox Seagate Technology, LLC Office 405-392-3738 Cell 405-206-4809 From Barry.Olawsky at hp.com Fri Dec 4 13:53:38 2009 From: Barry.Olawsky at hp.com (Olawsky, Barry) Date: Fri, 4 Dec 2009 21:53:38 +0000 Subject: SFF-8449, SFF-8636 Conference Call Minutes, December 1, 2009 Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * "Olawsky, Barry" * Minutes of SFF-8636, SFF-8449 conference call December 1, 2009 Attendance: Mr. Mickey Felton EMC Mr. Doug Wagner FCI Ms. Katharine Schmidtke Finisar Corporation Mr. Barry Olawsky Hewlett Packard Mr. Gourgen Oganessyan Intersil Mr. Harvey Newman LSI Corp. Mr. Chris Fore NetApp Mr. Alvin Cox Seagate Technology Mr. Mike Fitzpatrick Toshiba Mr. Joel Meyers Tyco Electronics Mr. Scott Shuey Tyco Electronics Mr. Atul Sharma Volex, Inc. Mr. Toney Chew Volex, Inc. Mr. Michael Koffman Western Digital Technology Mr. Matt Davis Zarlink Semiconductor 15 in attendance Agenda: Discuss proposed content for SFF-8636 (Common Management Interface) and SFF-8449 (Mini Multilane Series Management Interface). SFF-8436 (QSFP+ Copper and Optical Transceiver) is to be used as a basis for SFF-8636. Discussion: Barry Olawsky (hp) presented a draft of the lower page 00 memory map including new parameters for SAS. One participant noted that version 3.4 of SFF8636 had assigned locations 8, 19-21, 30-33, 66-81 and 105-106 to vendor specific from reserved. Barry took an action item to investigate the change. Call schedule: Upcoming conference calls: December 10, 2009 Toll Free Dial in Number: (877)810-9442 International Access/Caller Paid Dial In Number: (636)651-3190 PARTICIPANT CODE: 3243413 Webex information: https://seagate.webex.com/seagate Topic: SAS-2.1 PHY WG Date: Thursday, December 10 2009 Time: 10:00 am, Central Daylight Time (GMT -05:00, Chicago) Meeting Number: 826 515 680 Meeting Password: newsas (Note: When logging onto WEBEX, please include your company following your name. This will help the person recording attendance.) * * For T10 Reflector information, send a message with * 'info t10' (no quotes) in the message body to majordomo at t10.org From lohmeyer at t10.org Sat Dec 5 23:00:51 2009 From: lohmeyer at t10.org (T10 Document Administrator) Date: Sun, 6 Dec 2009 00:00:51 -0700 Subject: Recent T10 documents uploaded since 2009/11/29 Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * T10 Document Administrator * Proposals --------- Minutes of ADI WG November 2009 (by: Noud Snelder) T10/09-389r1 Uploaded: 2009/12/01 44995 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-389r1.pdf Recommend 64/66 encoding for SAS 3.0 (by: Mickey Felton) T10/09-407r1 Uploaded: 2009/12/03 34633 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-407r1.pdf Minutes of SAS PHY Working Group conference call December 3, 2009 (by: Alvin Cox) T10/10-003r0 Uploaded: 2009/12/03 197928 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-003r0.pdf Molex mini SAS 10-meter cable assembly near-end isolation (by: Galen Fromm) T10/10-004r0 Uploaded: 2009/12/04 1119424 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-004r0.pdf Molex mini SAS 10-meter cable assembly near-end isolation (by: Galen Fromm) T10/10-004r0 Uploaded: 2009/12/04 1040324 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-004r0.s4p Working Drafts -------------- (Report generated on 2009/12/06 at 00:00:51) * * For T10 Reflector information, send a message with * 'info t10' (no quotes) in the message body to majordomo at t10.org From George.Penokie at lsi.com Mon Dec 7 08:29:49 2009 From: George.Penokie at lsi.com (Penokie, George) Date: Mon, 7 Dec 2009 09:29:49 -0700 Subject: Error in SPL-r04 MT_IP (transport Layer for SMP initiator port) State Machine? Message-ID: Formatted message: HTML-formatted message On investigation it was discovered that in proposal 05-305r0 the following was deleted: If the SMP Frame Receive Timeout timer expires before a Received SMP Function Complete confirmation is received, this state shall send an SMP Frame Receive Timeout confirmation to the management application layer and send an SMP Transmit Break request to the port layer. This is the only reference to the SMP Frame Receive Timeout confirmation and as a result of the above deleted statements the MT_IP3:Receive state in the MT_IP state machine figure should have also been deleted. As a result the SMP Frame Receive Timeout confirmation has been deleted from the MT_IP state machine figure. Bye for now, George Penokie LSI Corporation 3033 41st St. NW Suite 100 Rochester, MN 55901 507-328-9017 george.penokie at lsi.com From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Alan Westbury Sent: Saturday, November 14, 2009 5:46 AM To: t10 at t10.org Subject: Error in SPL-r04 MT_IP (transport Layer for SMP initiator port) State Machine? Hi T10, SPL Figure 146 shows message "SMP Frame Receive Timeout" in state MT_IP3:Receive. This message is not covered by the clause describing this state (8.4.5.2.4.1). Looking back at SAS 1.1, there used to be a vendor specific "SMP Frame Receive Timeout timer". On expiry of this timer, MT_IP informed the management application, and sent a Break request to the Port Layer. This would appear to account for the message shown in Fig 146. In SAS 2 / SPL the timing requirement has shifted to the MT_TP state machine, but it's now unclear what the MT_IP response should be in the event of a timeout. Regards, Alan --- Alan Westbury Product Architect Xyratex Storage Systems, Langstone Road, Havant, PO9 1SA United Kingdom Tel +44 - (0)23 - 9249 6722 (direct) Tel +44 - (0)23 - 9249 6000 (switch board) Fax +44 - (0)23 - 9249 2284 Email: alan_westbury at xyratex.com http://www.xyratex.c ______________________________________________________________________ This email may contain privileged or confidential information, which should only be used for the purpose for which it was sent by Xyratex. No further rights or licenses are granted to use such information. If you are not the intended recipient of this message, please notify the sender by return and delete it. You may not use, copy, disclose or rely on the information contained in it. Internet email is susceptible to data corruption, interception and unauthorised amendment for which Xyratex does not accept liability. While we have taken reasonable precautions to ensure that this email is free of viruses, Xyratex does not accept liability for the presence of any computer viruses in this email, nor for any losses caused as a result of viruses. Xyratex Technology Limited (03134912), Registered in England & Wales, Registered Office, Langstone Road, Havant, Hampshire, PO9 1SA. The Xyratex group of companies also includes, Xyratex Ltd, registered in Bermuda, Xyratex International Inc, registered in California, Xyratex (Malaysia) Sdn Bhd registered in Malaysia, Xyratex Technology (Wuxi) Co Ltd registered in The People's Republic of China and Xyratex Japan Limited registered in Japan. ______________________________________________________________________ From kdbutt at us.ibm.com Wed Dec 9 12:19:58 2009 From: kdbutt at us.ibm.com (Kevin D Butt) Date: Wed, 9 Dec 2009 13:19:58 -0700 Subject: SAS2 6G Connectors Message-ID: Formatted message: HTML-formatted message In looking at SAS-2 it appears that all external connectors that support 6G are supposed to have slot 3 on the connector. Likewise the cables are supposed to have key 3 if they are for 6G (i..e, too long for 3G). Yet when searching for cables and HBA's on the web, we do not see any cables or HBA's that have key/slot 3. Am I missing an understanding here? Thanks, Kevin D. Butt SCSI & Fibre Channel Architect, Tape Firmware MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744 Tel: 520-799-5280 Fax: 520-799-2723 (T/L:321) Email address: kdbutt at us.ibm.com From Barry.Olawsky at hp.com Wed Dec 9 12:37:19 2009 From: Barry.Olawsky at hp.com (Olawsky, Barry) Date: Wed, 9 Dec 2009 20:37:19 +0000 Subject: SFF-8449, SFF-8636 Conference Call Reminder, December 10, 2009 Message-ID: Formatted message: HTML-formatted message Agenda: Discuss proposed content for SFF-8636 (Common Management Interface) and SFF-8449 (Mini Multilane Series Management Interface). SFF-8436 (QSFP+ Copper and Optical Transceiver) is to be used as a basis for SFF-8636. Call schedule: Upcoming conference calls: December 10, 2009 Toll Free Dial in Number: (877)810-9442 International Access/Caller Paid Dial In Number: (636)651-3190 PARTICIPANT CODE: 3243413 Webex information: https://seagate.webex.com/seagate Topic: SAS-2.1 PHY WG Date: Tuesday, December 10 2009 Time: 10:00 am, Central Daylight Time (GMT -05:00, Chicago) Meeting Number: 826 515 680 Meeting Password: newsas (Note: When logging onto WEBEX, please include your company following your name. This will help the person recording attendance.) From Felton_Mickey at emc.com Wed Dec 9 12:49:17 2009 From: Felton_Mickey at emc.com (Felton_Mickey at emc.com) Date: Wed, 9 Dec 2009 15:49:17 -0500 Subject: SAS2 6G Connectors Message-ID: Formatted message: HTML-formatted message Kevin- Actually the wording in the spec is actually even more confusing than what you stated. It actually states Trained cables will have the key and untrained cables will not. How do you market a cable as "Trained"? See table 14, page 57 of the spec, page 74 of the PDF. -Mick From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Kevin D Butt Sent: Wednesday, December 09, 2009 3:20 PM To: t10 at t10.org Subject: SAS2 6G Connectors In looking at SAS-2 it appears that all external connectors that support 6G are supposed to have slot 3 on the connector. Likewise the cables are supposed to have key 3 if they are for 6G (i..e, too long for 3G). Yet when searching for cables and HBA's on the web, we do not see any cables or HBA's that have key/slot 3. Am I missing an understanding here? Thanks, Kevin D. Butt SCSI & Fibre Channel Architect, Tape Firmware MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744 Tel: 520-799-5280 Fax: 520-799-2723 (T/L:321) Email address: kdbutt at us.ibm.com http://www-03.ibm.com/servers/storage/ Formatted message: HTML-formatted message Only receptacles that support 6 Gbps over a 10 m cable are support to have that key slot. If the phy's ability to support 10 m cables at that rate is questionable, then not including that key slot is safer. A 10 m cable without that key leaves itself open to being plugged into receptacles where it won't work reliably. From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Kevin D Butt Sent: Wednesday, December 09, 2009 2:20 PM To: t10 at t10.org Subject: SAS2 6G Connectors In looking at SAS-2 it appears that all external connectors that support 6G are supposed to have slot 3 on the connector. Likewise the cables are supposed to have key 3 if they are for 6G (i..e, too long for 3G). Yet when searching for cables and HBA's on the web, we do not see any cables or HBA's that have key/slot 3. Am I missing an understanding here? Thanks, Kevin D. Butt SCSI & Fibre Channel Architect, Tape Firmware MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744 Tel: 520-799-5280 Fax: 520-799-2723 (T/L:321) Email address: kdbutt at us.ibm.com http://www-03.ibm.com/servers/storage/ From lohmeyer at t10.org Wed Dec 9 14:39:30 2009 From: lohmeyer at t10.org (John Lohmeyer) Date: Wed, 09 Dec 2009 15:39:30 -0700 Subject: Fwd: IMPORTANT: INCITS 2010 Invoicing Schedule and Information Message-ID: Formatted message: HTML-formatted message If you are a T10 principal or alternate member, you should have received the below email directly from Lynn Barra. Please note the billing schedule for the 2010 membership invoices. John >From: "Barra, Lynn" >To: All Members >Sender: "active_committee_members at standards.incits.org" > >Date: Wed, 9 Dec 2009 14:41:43 -0700 >Subject: IMPORTANT: INCITS 2010 Invoicing Schedule and Information > >INCITS Community ? > >This overview of the INCITS 2010 participation payment schedule is being sent to all participants as additional reminder. Please review and if you have any questions, let me know. > > >From: Barra, Lynn [mailto:lbarra at itic.org] >Sent: Tuesday, October 06, 2009 9:08 PM >To: chairs at standards.incits.org >Cc: Deutsch, Donald; Hughes, Jim; Wennblom, Philip; Wright, Don >Subject: [Chairs] IMPORTANT: INCITS 2010 Invoicing Schedule and Information >Importance: High > >To INCITS TC and TG Chairs ? > >It?s that time of year again and the INCITS Secretariat has started the process for generating invoices for 2010 participation. Note that the membership cycle begins on December 1, 2009 and ends November 30, 2010. > >In August, TC and TG Chairs were emailed a membership report of organizations and representatives on record for their committee. The Secretariat has received some updated information from you and/or directly |from members. When invoices are issued, the principal contact that INCITS has on record is the individual who will receive the invoices (unless an organization has requested a separate designed billing point of contact). > >Beginning with the 2010 membership cycle, the automated features of the billing system will be used to issue invoices, reminder notices, final notices and sadly termination notices. The schedule is as follows: > >1. October 29: The billing system will take a snapshot of each committee to generate invoices with existing information. >2. November 1: The 2010 invoices are emailed to the Principal representative (or to the designed billing contact). > >3. December 1: A 30-day reminder notice to unpaid organizations is emailed to the Principal representative (or to the designed billing contact). >4. January 1: Final notices to unpaid organizations are emailed to the Principal representative (or to the designed billing contact). A summary of organizations that received a final notice will be emailed to TC/TG Chairs on January 4. >5. February 1: Memberships are deactivated if unpaid and cancellation notices are emailed to the Principal representative (or to the designed billing contact). If deactivated, organizations are welcome to re-establish participation in accordance with the INCITS/RD-2 and should contact the INCITS Secretariat. A summary of deactivated organizations will be emailed to TC/TG Chairs on February 2. > >Principal representatives should be reminded that if they do not receive an invoice, they should contact the Secretariat immediately. Maintaining membership is the responsibility of the member organization (Principal and Alternates). Purchase orders, contracts and agreements must be fully executed and received at the INCITS Secretariat before the February 1, 2010 deadline to ensure uninterrupted service. For purchase orders, contracts and agreements received after January 1, 2010, payment in full must be received within 60 days to avoid deactivation. >Note to Chairs: >Please ensure both Principal and Alternate members are aware of the above schedule of invoicing activities. Membership data can be provided upon request and changes can be submitted via email. > >- Committees already transitioned to ICMS - Chairs can log into ICMS and download their rosters for review and members can view and update their own participation or submit changes via email. >- Committees not transitioned to ICMS - Chairs should contact the Secretariat for ICMS access to their rosters; membership changes can be submitted via email. > >Please contact the Secretariat any questions. > > >Lynn Barra (lbarra at itic.org, 202-626-5739) >Barbara Bennett (bbennett at itic.org, 202-626-5743) >Serena Patrick (spatrick at itic.org, 202-626-5741) >Debbie Spittle (dspittle at itic.org, 202-626-5746) > > > -- John Lohmeyer Email: lohmeyer at t10.org LSI Corp. Voice: +1-719-533-7560 4420 ArrowsWest Dr. Cell: +1-719-338-1642 Colo Spgs, CO 80907 From Felton_Mickey at emc.com Thu Dec 10 08:29:11 2009 From: Felton_Mickey at emc.com (Felton_Mickey at emc.com) Date: Thu, 10 Dec 2009 11:29:11 -0500 Subject: SAS2 6G Connectors Message-ID: Formatted message: HTML-formatted message Rob- Did you mean 10m or 6m for key slot 3? From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Elliott, Robert (Server Storage) Sent: Wednesday, December 09, 2009 4:12 PM To: Kevin D Butt; t10 at t10.org Subject: RE: SAS2 6G Connectors Only receptacles that support 6 Gbps over a 10 m cable are support to have that key slot. If the phy's ability to support 10 m cables at that rate is questionable, then not including that key slot is safer. A 10 m cable without that key leaves itself open to being plugged into receptacles where it won't work reliably. From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Kevin D Butt Sent: Wednesday, December 09, 2009 2:20 PM To: t10 at t10.org Subject: SAS2 6G Connectors In looking at SAS-2 it appears that all external connectors that support 6G are supposed to have slot 3 on the connector. Likewise the cables are supposed to have key 3 if they are for 6G (i..e, too long for 3G). Yet when searching for cables and HBA's on the web, we do not see any cables or HBA's that have key/slot 3. Am I missing an understanding here? Thanks, Kevin D. Butt SCSI & Fibre Channel Architect, Tape Firmware MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744 Tel: 520-799-5280 Fax: 520-799-2723 (T/L:321) Email address: kdbutt at us.ibm.com http://www-03.ibm.com/servers/storage/ Formatted message: HTML-formatted message This is a reminder that the cut-off date for making reservations is 28-Dec-2009. I know it is getting to be Christmas and New Years, so don't let this get lost in the shuffle. ------------------------------------------------- Curtis E. Stevens Sr. Staff Engr - Standards & Features Technology 20511 Lake Forest Drive #A 113-F Lake Forest, California 92630 Phone: 949-672-7933 Cell: 949-307-5050 E-Mail: Curtis.Stevens at WDC.com From Elliott at hp.com Thu Dec 10 12:22:44 2009 From: Elliott at hp.com (Elliott, Robert (Server Storage)) Date: Thu, 10 Dec 2009 20:22:44 +0000 Subject: SAS2 6G Connectors Message-ID: Formatted message: HTML-formatted message Cables are divided into two categories: a) up to 6 m; these cables do not include key 3. - All SAS-1 and SAS-2 phys are expected to work with these short cables. b) 6 m to 10 m; these cables include key 3. - SAS-1 phys are not expected to work with these long cables. - SAS-2 phys are expected to work with these long cables. SAS-1 receptacles do not include key slot 3. This prevents long cables from being attached; only short cables fit. SAS-2 receptacles include key slot 3. This allows both short and long cables to be attached. Possible reasons that a SAS-2 phy might use the SAS-1 receptacle include: - the key/key slot definition arrived too late in SAS-2 to make it into the product release. - the phy was not validated with enough other phys for the vendor to be confident about including the key slot in the product release. There was a one-year gap between STA plugfests. - the phy is not completely compliant with SAS-2. The transmitter or receiver might have issues that aren't a problem with 6 m or less. - the vendor uses cables and receptacles without keys & key slots, letting the user plug in combinations that don't work. From: Felton_Mickey at emc.com [mailto:Felton_Mickey at emc.com] Sent: Thursday, December 10, 2009 10:29 AM To: Elliott, Robert (Server Storage); kdbutt at us.ibm.com; t10 at t10.org Subject: RE: SAS2 6G Connectors Rob- Did you mean 10m or 6m for key slot 3? From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Elliott, Robert (Server Storage) Sent: Wednesday, December 09, 2009 4:12 PM To: Kevin D Butt; t10 at t10.org Subject: RE: SAS2 6G Connectors Only receptacles that support 6 Gbps over a 10 m cable are support to have that key slot. If the phy's ability to support 10 m cables at that rate is questionable, then not including that key slot is safer. A 10 m cable without that key leaves itself open to being plugged into receptacles where it won't work reliably. From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Kevin D Butt Sent: Wednesday, December 09, 2009 2:20 PM To: t10 at t10.org Subject: SAS2 6G Connectors In looking at SAS-2 it appears that all external connectors that support 6G are supposed to have slot 3 on the connector. Likewise the cables are supposed to have key 3 if they are for 6G (i..e, too long for 3G). Yet when searching for cables and HBA's on the web, we do not see any cables or HBA's that have key/slot 3. Am I missing an understanding here? Thanks, Kevin D. Butt SCSI & Fibre Channel Architect, Tape Firmware MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744 Tel: 520-799-5280 Fax: 520-799-2723 (T/L:321) Email address: kdbutt at us.ibm.com http://www-03.ibm.com/servers/storage/ From Kevin_Marks at Dell.com Thu Dec 10 13:58:45 2009 From: Kevin_Marks at Dell.com (Kevin_Marks at Dell.com) Date: Thu, 10 Dec 2009 15:58:45 -0600 Subject: Updated SCSI Power Proposals posted (SPC-4/SBC-3/SPL) Message-ID: Formatted message: HTML-formatted message SPC-4/SBC-3 - http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-085r7.pdf SPL - http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-354r0.pdf These incorporate everyone's feedback to date. Thanks Kevin Kevin Marks Technologist, Storage Architecture | Office of the CTO Dell, Inc. 512.723.9173 | voice 512.963.8178 | mobile kevin_marks at dell.com From j.osterlund at sisa.samsung.com Fri Dec 11 11:10:50 2009 From: j.osterlund at sisa.samsung.com (John Osterlund) Date: Fri, 11 Dec 2009 11:10:50 -0800 Subject: next T10 Meeting announcement has a typo( year sb 2010 ) Message-ID: Formatted message: HTML-formatted message Note to all, The T10 meeting announcement has typo (actually created an issue for me for my travel authorization process): Meeting Announcement T10 Technical Committee (and friends) January 11-14, 2009 HOSTED BY: Western Digital Technologies, Inc. Should be 2010. -John Osterlund From bberg at bswd.com Fri Dec 11 11:44:14 2009 From: bberg at bswd.com (Brian A. Berg) Date: Fri, 11 Dec 2009 19:44:14 +0000 (GMT) Subject: EE Times story re: the Standards Process Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * "Brian A. Berg" * Of some interest. Demystifying the standards development process http://www.eetimes.com/showArticle.jhtml;jsessionid=P44IQFVSDPDLRQE1GHPSKHWAT MY32JVN?articleID=222001705&pgno=2 The process of creating a standard is only one piece of a larger life cycle that spans from prestandardization investigation and planning through post-publication activities, including testing, promotion, education and maintenance. ___________________________________________________________________ Brian A. Berg bberg at bswd.com Voice: +1.408.741.5010 Berg Software Design FAX: +1.408.741.5234 14500 Big Basin Way, Suite F Consulting: USB/Flash/SCSI/SAN Saratoga, CA 95070 USA Cell: +1.408.568.2505 visit the Storage Cornucopia at www.bswd.com * * For T10 Reflector information, send a message with * 'info t10' (no quotes) in the message body to majordomo at t10.org From lohmeyer at t10.org Fri Dec 11 15:17:47 2009 From: lohmeyer at t10.org (John Lohmeyer) Date: Fri, 11 Dec 2009 16:17:47 -0700 Subject: next T10 Meeting announcement has a typo( year sb 2010 ) Message-ID: Formatted message: HTML-formatted message John, It is corrected. Sorry about the hassle. John At 12/11/2009 12:10 PM, John Osterlund wrote: >Note to all, > >The T10 meeting announcement has typo (actually created an issue for me for my travel authorization process): > >Meeting Announcement >T10 Technical Committee (and friends) >January 11-14, 2009 >HOSTED BY: Western Digital Technologies, Inc. > > >Should be 2010. > >-John Osterlund -- John Lohmeyer Email: lohmeyer at t10.org LSI Corp. Voice: +1-719-533-7560 4420 ArrowsWest Dr. Cell: +1-719-338-1642 Colo Spgs, CO 80907 From lohmeyer at t10.org Sat Dec 12 23:00:46 2009 From: lohmeyer at t10.org (T10 Document Administrator) Date: Sun, 13 Dec 2009 00:00:46 -0700 Subject: Recent T10 documents uploaded since 2009/12/06 Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * T10 Document Administrator * Proposals --------- Minutes of T10 Plenary Meeting #88 - November 6, 2008 (by: Weber & Lohmeyer) T10/08-430r1 Uploaded: 2009/12/07 135317 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-430r1.htm Minutes of T10 Plenary Meeting #88 - November 6, 2008 (by: Weber & Lohmeyer) T10/08-430r1 Uploaded: 2009/12/07 324116 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-430r1.pdf SPC-4/SBC-3: Power conditions transition modifications (by: Kevin Marks) T10/09-085r7 Uploaded: 2009/12/10 209247 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-085r7.pdf UAS Letter Ballot Comment Resolutions (by: Curtis Stevens) T10/09-163r4 Uploaded: 2009/12/10 1573464 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-163r4.fdf UAS Letter Ballot Comment Resolutions (by: Curtis Stevens) T10/09-163r4 Uploaded: 2009/12/10 2659099 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-163r4.pdf UAS Letter Ballot Comment Resolutions (by: Curtis Stevens) T10/09-163r5 Uploaded: 2009/12/12 2680157 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-163r5.pdf SBC-3: SPC-4; SAM-5; SCSI Referrals (by: George Penokie) T10/09-241r5 Uploaded: 2009/12/09 291360 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-241r5.pdf SPL Only: Power condition transition modifications and cleanup (by: Kevin Marks) T10/09-354r0 Uploaded: 2009/12/10 119439 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-354r0.pdf ICR Analysis of Channels for SAS-3 (by: Kevin Witt) T10/09-395r1 Uploaded: 2009/12/12 399124 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-395r1.pdf SPC-4 SBC-3 Add Disable PI Check on xxPROTECT=0 feature (by: Gerald Houlder) T10/10-005r0 Uploaded: 2009/12/07 407140 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-005r0.pdf Working Drafts -------------- MultiMedia Command Set - 6 (MMC-6) (Editor: Bill McFerrin) Rev: 02g Uploaded: 2009/12/11 4577888 bytes http://www.t10.org/cgi-bin/ac.pl?t=f&f=mmc6r02g.pdf SAS Protocol Layer (SPL) (Editor: George Penokie) Rev: 05 Uploaded: 2009/12/07 8223611 bytes http://www.t10.org/cgi-bin/ac.pl?t=f&f=spl-r05.pdf (Report generated on 2009/12/13 at 00:00:46) * * For T10 Reflector information, send a message with * 'info t10' (no quotes) in the message body to majordomo at t10.org From kdbutt at us.ibm.com Wed Dec 16 06:58:21 2009 From: kdbutt at us.ibm.com (Kevin D Butt) Date: Wed, 16 Dec 2009 07:58:21 -0700 Subject: Reminder: SMC-3 Web Conference Today (Dec 16) Message-ID: Formatted message: HTML-formatted message Kevin D. Butt SCSI & Fibre Channel Architect, Tape Firmware MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744 Tel: 520-799-5280 Fax: 520-799-2723 (T/L:321) Email address: kdbutt at us.ibm.com http://www-03.ibm.com/servers/storage/ ----- Forwarded by Kevin D Butt/Tucson/IBM on 12/16/2009 07:57 AM ----- From: Kevin D Butt/Tucson/IBM at IBMUS To: t10 at t10.org Date: 11/20/2009 09:56 AM Subject: SMC-3 Web Conference Details (Dec 16) Sent by: owner-t10 at t10.org The SMC-3 Working Group is holding a web conference on Dec 16 from 8:00 AM - 11:00 AM PST The following two proposals will be discussed 6.3 SMC-3 Report Volume Information (08-215r7) [Ballard] 6.7 SMC-3: Volume Replication Visibility (09-308r3) [Cummings] The audio conference numbers are also available at the web conference login. US Toll Free: 1-866-907-1016 US Toll: 1-719-387-8316 Participant Passcode: 240180 Conference Access Numbers: Location Local Access (Preferred) Toll Free Netherlands, Amsterdam +31 (0) 20 262 0120 Netherlands 0 800 022 3061 UK, London +44 (0) 20 8150 0610 UK 0 808 101 5336 Please contact kdbutt at us.ibm.com if you need a number for a country not listed. Conference Shortcuts ? Press *1 to hear a help menu. ? Press *0 to reach an operator. ? Press *6 to mute or "un-mute" line. ? Press *4 to increase conference volume. ? Press *7 to decrease conference volume. ? Press *5 to increase your voice volume. ? Press *8 to decrease your voice volume. =================================================== JOIN THE WEB CONFERENCE 1) Join the conference up to 20 minutes prior to 9:00 AM at 12/16/2009 2) Direct your web browser to the following URL: http://www.ibm.com/collaboration/webconferences/center/meetingdetails.jsp?mee tingId=1AA8485D0D9118F8E00F9F5E153923E9 3) When prompted, enter the web conference password: SMC-3call WEB CONFERENCE DETAILS: Conference URL: http://www.ibm.com/collaboration/webconferences/center/meetingdetails.jsp?mee tingId=1AA8485D0D9118F8E00F9F5E153923E9 Password: SMC-3call Conference name: SMC-3 Standards Start time: 12/16/2009 9:00 AM Duration: 03 hours 10 minutes Meeting creator: Kevin D. Butt Moderator: Kevin D. Butt WHITEBOARD ATTACHMENTS: No attachments PREPARE FOR THE WEB CONFERENCE - Meeting participants + A userid and password is not required to enter the meeting. + A meeting password is required. + Browsers supported Internet Explorer 6.0 on Windows XP Professional Mozilla 1.7.12 on Windows XP Professional Mozilla 1.7.6 on RedHat Enterprise Linux 4.0 or Novell Linux Desktop 9.0 Firefox 1.5 on Windows XP Professional, RedHat Enterprise Linux 4.0, and Novell Linux Desktop 9.0 + Java JDK/JRE supported IBM or Sun JDK/JRE 1.4.2 or later - Internet Explorer 6.0 on Windows XP Professional IBM or Sun JRE 1.4.2 or later - RedHat Enterprise Linux 4.0 and Novell Linux Desktop 9.0 - To determine whether you have Java installed, and what version you have, for Microsoft (R) Internet Explorer, for example, click Tools - Internet Options, and then click Advanced. For other Microsoft(R) Windows(R)-based browsers, check the Java Control panel. IBM users can Download the latest version of Java from ISSI. External customers can Download the latest version of Java from Sun Microsystems Web site at http://www.java.sun.com - Additional Browser setting Help can be found at : http://www.ibm.com/collaboration/webconferences/center/stmtghelp/en/H_MAKING_ YOUR_BROWSER_WORK_WITH_SAMETIME_3308_OVER.html + If this is your first IBM Web Conference, attend the special "test" meeting to make sure that you can join easily. Please visit http://www.ibm.com/collaboration/webconferences/center/meetingwizard.jsp and click "Attend a test meeting" + Help is available at http://www.ibm.com/collaboration/webconference/help/index.html + Leave the meeting or close your browser at the end of the meeting. IBM Web Conferences is powered by the IBM Lotus Sametime product. For more information on IBM's internal deployment of Sametime Web conferencing: http://www.ibm.com/collaboration/webconference/help/what_features_functions_e nabled_IBM_wc_offering.html For more information on the Lotus Sametime product: http://www.ibm.com/lotus/sametime To make a suggestion or ask questions, visit http://ibmforums.ibm.com/forums/forum.jspa?forumID=889 Thanks Kevin D. Butt SCSI & Fibre Channel Architect, Tape Firmware MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744 Tel: 520-799-5280 Fax: 520-799-2723 (T/L:321) Email address: kdbutt at us.ibm.com http://www-03.ibm.com/servers/storage/ From Alvin.Cox at seagate.com Wed Dec 16 13:56:30 2009 From: Alvin.Cox at seagate.com (Alvin.Cox at seagate.com) Date: Wed, 16 Dec 2009 15:56:30 -0600 Subject: Reminder: SAS PHY teleconference 12/17/09, 10:00 am CST Message-ID: Formatted message: HTML-formatted message Toll Free Dial in Number: (877)810-9442 International Access/Caller Paid Dial In Number: (636)651-3190 PARTICIPANT CODE: 3243413 Webex information: https://seagate.webex.com Topic: SAS-2.1 PHY WG Date: Thursday, Dec 17, 2009 Time: 10:00 am, Central Standard Time Meeting number: 826 515 680 Password: newsas Agenda: SAS 2.1 Upgrade the Touchstone reference to version 2.0 (Modify the .s4p files included with the standard to comply with version 2.0.) [Fromm] Tbd???s for microSAS [Cox] Mini SAS HD numbering and lane location [Cox/Molex] Section 5.6.6.3. The SCD11 and SCD22 limits Summary of cable analysis [Olawsky] SCDxx Limit Proposal for Active Cables in SAS-2.1 (10-001) [Oganessyan] Reference Transmitter Device Termination (TxRefTerm.s4p) and the Reference Receiver Device Termination (RxRefTerm.s4p) to be used in the SAS-2.1 Annex C StatEye code. But it is not. [Newman, Witt] SAS-2.1 StatEye ReadMe File (10-007) [Newman] New LB comment discussion items [Cox] SAS 3 Recommend 64/66 encoding for SAS 3.0 (09-407) [Felton] Updates to channel analysis Alvin Cox Seagate Technology, LLC Office 405-392-3738 Cell 405-206-4809 E-Mail alvin.cox at seagate.com From goganess at intersil.com Wed Dec 16 12:01:35 2009 From: goganess at intersil.com (Oganessyan, Gourgen) Date: Wed, 16 Dec 2009 15:01:35 -0500 Subject: Revised Active cable SCDxx proposal uploaded Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * "Oganessyan, Gourgen" * Presentation 10-001r1 has been uploaded for review. Gourgen Oganessyan Staff Product Marketing Engineer Intersil Corp. Phone: (408)-890-1700 (630)-802-0574 (cell) Fax: (630)-364-5724 e-mail: goganess at intersil.com * * For T10 Reflector information, send a message with * 'info t10' (no quotes) in the message body to majordomo at t10.org From lohmeyer at t10.org Thu Dec 17 09:06:06 2009 From: lohmeyer at t10.org (John Lohmeyer) Date: Thu, 17 Dec 2009 10:06:06 -0700 Subject: T10 Reflector clean up Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * John Lohmeyer * # # # # # # # # # # It is time again to clean up the T10 Reflector. The following addresses have bounced consistently since the last clean up and are being removed: kiranmai.vedanabhatla at jdsu.com Daniele.Gardellini at infineon.com arvind at amphenolcanada.com jaremyf at atlconnect.com nathana at atlconnect.com These people may re-subscribe (hopefully, with a better address) by using the following URL: http://www.t10.org/t10r.htm -- John Lohmeyer Email: lohmeyer at t10.org LSI Corp. Voice: +1-719-533-7560 4420 ArrowsWest Dr. Cell: +1-719-338-1642 Colo Spgs, CO 80907 * * For T10 Reflector information, send a message with * 'info t10' (no quotes) in the message body to majordomo at t10.org From curtis.ballard at hp.com Thu Dec 17 16:01:34 2009 From: curtis.ballard at hp.com (Ballard, Curtis C (StorageWorks)) Date: Fri, 18 Dec 2009 00:01:34 +0000 Subject: REPORT VOLUME INFORMATION command as approved by SMC-3 posted Message-ID: Formatted message: HTML-formatted message I have posted the final revision of a new command for SMC-3, REPORT VOLUME INFORMATION, as accepted by the SMC-3 working group yesterday during a telephone conference. This command allows an application client to query detailed information about the volume in an element by element address and also introduces a variable length CDB that allows sending a volume "handle" such as a serial number or barcode to request information. If you have interesting in reading volume information from media changers or processing variable length CDBs you might want to take a look at this proposal. http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-010r1.pdf Curtis Ballard Hewlett Packard StorageWorks Platforms Tape Fort Collins, CO (970) 898-3013 From lohmeyer at t10.org Sat Dec 19 23:00:50 2009 From: lohmeyer at t10.org (T10 Document Administrator) Date: Sun, 20 Dec 2009 00:00:50 -0700 Subject: Recent T10 documents uploaded since 2009/12/13 Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * T10 Document Administrator * Proposals --------- MMC-6 Letter Ballot Comment Resolution (by: William McFerrin) T10/09-283r2 Uploaded: 2009/12/14 90369 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-283r2.pdf SCDxx Limit Proposal for Active Cables in SAS-2.1 (by: Gourgen Oganessyan) T10/10-001r1 Uploaded: 2009/12/16 106038 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-001r1.pdf SAS-2.1 StatEye ReadMe File (by: Harvey Newman) T10/10-007r0 Uploaded: 2009/12/15 152179 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-007r0.pdf SAS-2.1 StatEye ReadMe File (by: Harvey Newman) T10/10-007r0 Uploaded: 2009/12/15 280856 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-007r0.zip SAS-2.1 StatEye ReadMe File (by: Harvey Newman) T10/10-007r1 Uploaded: 2009/12/17 152249 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-007r1.pdf SAS-2.1: SCD21 Limit Proposal for Passive Cables (by: Michael Rost) T10/10-008r0 Uploaded: 2009/12/16 256675 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-008r0.pdf T11 Liaison Report, December 2009 (by: Steven Wilson) T10/10-009r0 Uploaded: 2009/12/14 24974 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-009r0.pdf SMC-3 Report Volume Information (by: Curtis Ballard) T10/10-010r0 Uploaded: 2009/12/15 248162 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-010r0.pdf SMC-3 Report Volume Information (by: Curtis Ballard) T10/10-010r1 Uploaded: 2009/12/17 241052 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-010r1.pdf Minutes SMC-3 16 December 2009 (by: Kevin Butt) T10/10-011r0 Uploaded: 2009/12/16 40775 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-011r0.pdf SPL: Prohibiting deletable primitives during Train-SNW (by: George Penokie) T10/10-012r0 Uploaded: 2009/12/17 62536 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-012r0.pdf SPL: Prohibiting deletable primitives during Train-SNW (by: George Penokie) T10/10-012r1 Uploaded: 2009/12/17 68532 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-012r1.pdf Minutes of SAS PHY Working Group conference call December 17, 2009 (by: Alvin Cox) T10/10-013r0 Uploaded: 2009/12/17 38286 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-013r0.pdf SAT-3: Work items and open issues list (by: Mark Overby) T10/10-014r0 Uploaded: 2009/12/17 32735 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-014r0.pdf SAS 2.1 letter ballot comment fdf file (by: Alvin Cox) T10/10-015r0 Uploaded: 2009/12/18 788345 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-015r0.fdf SAS 2.1 letter ballot comment fdf file (by: Alvin Cox) T10/10-015r0 Uploaded: 2009/12/18 4802 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-015r0.pdf Working Drafts -------------- (Report generated on 2009/12/20 at 00:00:50) * * For T10 Reflector information, send a message with * 'info t10' (no quotes) in the message body to majordomo at t10.org From Frederick.Knight at netapp.com Wed Dec 23 14:23:35 2009 From: Frederick.Knight at netapp.com (Knight, Frederick) Date: Wed, 23 Dec 2009 17:23:35 -0500 Subject: 09-100 & 09-363 Updates posted Message-ID: Formatted message: HTML-formatted message I've posted updates to two proposals we'll be looking at in January in Santa Ana: For the Atomic COMPARE AND WRITE: http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-100r3.pdf There is now only 1 protection related field (for the write). There is no protection validation during the verify operation (because, we're already doing a full verify of every byte of the data anyway). For the XCOPY with NLID capability: http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-363r2.pdf I've updated some wording based on feedback from the November meeting (particularly around the count/limits fields for the two types of XCOPY commands - w/NLID and without/NLID). Fred Knight From lohmeyer at t10.org Sat Dec 26 23:00:50 2009 From: lohmeyer at t10.org (T10 Document Administrator) Date: Sun, 27 Dec 2009 00:00:50 -0700 Subject: Recent T10 documents uploaded since 2009/12/20 Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * T10 Document Administrator * Proposals --------- SBC-3 - Atomic COMPARE AND WRITE command (by: Frederick Knight) T10/09-100r3 Uploaded: 2009/12/23 84990 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-100r3.pdf SBC-3 - Thin Provisioning: Anchored (by: David L. Black) T10/09-272r2 Uploaded: 2009/12/21 287451 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-272r2.pdf SBC-3 - Thin Provisioning: Anchored (by: David L. Black) T10/09-272r3 Uploaded: 2009/12/23 288166 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-272r3.pdf SPC-4 XCOPY with no LIST IDENTIFIER (by: Frederick Knight) T10/09-363r2 Uploaded: 2009/12/23 187131 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-363r2.pdf SPC-4: Persistent Reservations Clarification (by: David Black) T10/10-016r0 Uploaded: 2009/12/21 30220 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=10-016r0.pdf Working Drafts -------------- (Report generated on 2009/12/27 at 00:00:50) * * For T10 Reflector information, send a message with * 'info t10' (no quotes) in the message body to majordomo at t10.org From keiji_katata at post.pioneer.co.jp Sun Dec 27 17:48:39 2009 From: keiji_katata at post.pioneer.co.jp (keiji_katata at post.pioneer.co.jp) Date: Mon, 28 Dec 2009 10:48:39 +0900 Subject: Fuji reflector/ftp recovery notice Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * keiji_katata at post.pioneer.co.jp * Hello all, Fuji server has moved to new office and has started again. I will send you chair's proposal for ODD Zero Power Effort description in the next January. I believe that you greet the good new year. Best regards, Keiji Katata PIONEER CORP. * * For T10 Reflector information, send a message with * 'info t10' (no quotes) in the message body to majordomo at t10.org From lohmeyer at t10.org Mon Dec 28 01:00:00 2009 From: lohmeyer at t10.org (T10 List Manager) Date: Mon, 28 Dec 2009 02:00:00 -0700 Subject: T10 Reflector Monthly Reminder Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * T10 List Manager * This is an automatic monthly posting to the T10 Reflector. If you receive this message, it means that you are subscribed to the T10 Reflector email list. The T10 Reflector is provided by the SCSI Trade Association and maintained by LSI Corp. This reflector exists to discuss INCITS T10 Technical Committee issues and to disseminate T10-related information (minutes, meeting notices, etc.). --------------------------------------------------------------------------- You do not need to be an INCITS T10 Technical Committee member to use this reflector, however you must agree to: * read the INCITS Patent Policy and the INCITS Antitrust Guidelines * acknowledge that the activities of the T10 Technical Committee are governed by the INCITS policies and procedures as specified in the reference documents RD-1 and RD-2 * acknowledge that draft documents may change at any time, without notice. The INCITS Patent Policy, the INCITS Antitrust Guidelines, the RD-1, and the RD-2 are all available on the www.incits.org web site. If you do not agree to the above conditions, then you must unsubscribe to this reflector. --------------------------------------------------------------------------- T10 Reflector is not intended to carry commercial traffic. People who post advertisements, job offers, etc. will be removed from the reflector. Please visit http://www.t10.org/t10r.htm for instructions on subscribing, unsubscribing, or searching the T10 Reflector archives. * * For T10 Reflector information, send a message with * 'info t10' (no quotes) in the message body to majordomo at t10.org From jgeldman at lexar.com Mon Dec 28 11:24:41 2009 From: jgeldman at lexar.com (jgeldman at lexar.com) Date: Mon, 28 Dec 2009 11:24:41 -0800 Subject: Format Unit (Sanitize) homework on FMTDATA=0 & "parameter list" Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * * In the November CAB meeting, while going over 09-331r1 (modifications of FORMAT UNIT to include T13's Sanitize capability), it was noted that in the FORMAT UNIT command, the non-zero DEFECT_LIST_FORMAT with FMTDATA=0 intent was not clear. Please be ready to discuss this in Santa Ana. The behavior of FMTDATA=0 and DEFECT_LIST_FORMAT != 000b is unspecified. Question 1) Should this be reserved? Or should any behavior be documented? Should it be documented as vendor specific? FMTDATA=0 specifies, "that no parameter list be transferred from the data-out buffer" (written on spec-like-a pirate day?). Table 17 specifies that with FMTDATA=0 and DEFECT_LIST_FORMAT=000b, the device has mandatory support for the comment "defect information is vendor specific". The phrase "no parameter list be transferred" is a bit arcane. As the phrase "parameter list" is used 99 times in multiple contexts in SBC3r20, it may mean specifically the "FORMAT UNIT parameter list" or it might mean any parameter list. Question 2) Should the FMTDATA=0 specification be changed to say "that the data-out buffer contents, if any, contain vendor specific data"? Or that nothing will used from the data-out buffer? Other requirements when FMTDATA=0: LONGLIST and CMPLIST shall be ignored; FMTPINFO shall be valid; and DEFECT_LIST_FORMAT shall be 000b (pending resolution of question 1) Happy Holidays, John Geldman Director of Industry Standards Lexar Media 47300 Bayside Parkway Fremont, CA 94538 P: 510 580-8715 C: 510 449-3597 * * For T10 Reflector information, send a message with * 'info t10' (no quotes) in the message body to majordomo at t10.org