From alvin.cox at seagate.com  Tue May  1 14:15:13 2012
From: alvin.cox at seagate.com (Alvin Cox)
Date: Tue, 1 May 2012 16:15:13 -0500
Subject: No SAS PHY call this week (5/3/12)
Message-ID: <mailman.118.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205010_f.htm">HTML-formatted message</a>

No call this week. Watch for updated and new proposals.  Face-to-face
meeting next Tuesday.
-- 
Alvin Cox
Seagate Technology, LLC
Cell 405-206-4809
Office 405-392-3738
E-Mail	alvin.cox at seagate.com


From roweber at ieee.org  Wed May  2 15:38:12 2012
From: roweber at ieee.org (Ralph Weber)
Date: Wed, 2 May 2012 17:38:12 -0500
Subject: SPC-4 Letter Ballot plans
Message-ID: <mailman.119.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* Ralph Weber <roweber at ieee.org>
*
The tentative thinking is that the long-awaited SPC-4
Letter Ballot will be held May 11 to June 29.
Item 5.1.9 on the CAP agenda provides an opportunity to
discuss this prior to the T10 Plenary.
All the best,
.Ralph
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From Raj.Divecha at dothill.com  Fri May  4 10:29:04 2012
From: Raj.Divecha at dothill.com (Raj Divecha)
Date: Fri, 4 May 2012 11:29:04 -0600
Subject: SES: Seeking clarification on Threshold Out/In diagnostic pages
Message-ID: <mailman.120.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205040_f.htm">HTML-formatted message</a>

Hi,
I searched the T10 emails for this but didn't found anything.
The SES spec is a bit ambiguous regarding which element types should be
included in the Threshold Out/In diagnostic page. A clarification would be
helpful.
The following are the excerpts from the 2r20 spec. Below each excerpt is my
comment. The questions are at the end of the email.
6.1.8 Threshold Out diagnostic page
The Threshold Out diagnostic page is transmitted to the enclosure services
process to establish threshold values for those elements that have limited
sensing capability (e.g., temperature sensors, uninterruptible power
supplies, voltage sensors, and current sensors).
My comment: this statement "possibly" suggests that this page includes only
those element types that support threshold.
The threshold control descriptor list contains a threshold control descriptor
for each type descriptor header in the Configuration diagnostic page (see
6.1.2).
My comment: this statement "strongly" suggests that this page includes all
element types, whether or not they support thresholds.
7.1 Element definitions overview, Table 60
My comment: shows which element type support thresholds and which not.
7.2.4 Threshold control element format
All fields in the threshold control element are advisory. The enclosure
services process shall ignore the contents of the threshold control element
for those elements that have no value to be compared with a threshold and for
those elements that do not implement the threshold function.
My comment: this statement suggests that threshold descriptors for even those
element types, that do not support threshold, are included in the Threshold
Out/In diagnostic page, however, the application client and the enclosure
services process (ESP) are supposed to ignore them.
7.3 Field definitions for all element types
My comments: this section does not describe the threshold descriptors for
element types that do not support threshold. Not even a generic descriptor
with 4 reserved bytes is defined.
If the readers are to assume that the threshold descriptors for even those
element types that do not support threshold are to be included in the
Threshold Out/In diagnostic pages, then they are also supposed to assume a
generic 4-byte threshold descriptors with all bytes as reserved as they are
supposed to be ignored by both the application client and the ESP.
If the readers are to assume that the Threshold Out/In pages should include
only those element types that support threshold then there is no question of
assuming a generic 4-bytes reserved descriptor and no question of ignoring
them.
Based on the above there are many "strong" points that indicate that the
Threshold Out/In pages include even those element types that do not support
thresholds and there are some "weak" points that indicate that they don't
include those element types.
Did the spec authors intended to include additional descriptors in the page
that will never be used?
Or were the Threshold Out/In diagnostic pages meant to be similar to the
Additional Element Status diagnostic page where in only a selected subset of
element types appear in these pages?
In my opinion the spec authors did not intend to include additional
descriptors in the page that will never be used and thus the Threshold Out/In
diagnostic page is similar to the Additional Element Status diagnostic page
where only a limited subset of element types appear in these pages. However,
I could be wrong, thus please clarify.
Thanks,
Raj


From Matthew_Jacobs at Dell.com  Fri May  4 12:41:30 2012
From: Matthew_Jacobs at Dell.com (Matthew_Jacobs at Dell.com)
Date: Fri, 4 May 2012 14:41:30 -0500
Subject: Seeking clarification on Threshold Out/In diagnostic pages
Message-ID: <mailman.121.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205041_f.htm">HTML-formatted message</a>

Raj,
The descriptions of the threshold control descriptor list and the threshold
status descriptor list in sections 6.1.8 and 6.1.9 state that the list
contains a control/status "descriptor for each type descriptor header in the
Configuration diagnostic page".  From that, I believe all individual elements
defined in the Configuration diagnostic page have a threshold element in the
Threshold in/Out diagnostic page even if it is just a placeholder/reserved
threshold element.
Matt
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Raj Divecha
Sent: Friday, May 04, 2012 12:29 PM
To: t10 at t10.org
Subject: SES: Seeking clarification on Threshold Out/In diagnostic pages
Hi,
I searched the T10 emails for this but didn't found anything.
The SES spec is a bit ambiguous regarding which element types should be
included in the Threshold Out/In diagnostic page. A clarification would be
helpful.
The following are the excerpts from the 2r20 spec. Below each excerpt is my
comment. The questions are at the end of the email.
6.1.8 Threshold Out diagnostic page
The Threshold Out diagnostic page is transmitted to the enclosure services
process to establish threshold values for those elements that have limited
sensing capability (e.g., temperature sensors, uninterruptible power
supplies, voltage sensors, and current sensors).
My comment: this statement "possibly" suggests that this page includes only
those element types that support threshold.
The threshold control descriptor list contains a threshold control descriptor
for each type descriptor header in the Configuration diagnostic page (see
6.1.2).
My comment: this statement "strongly" suggests that this page includes all
element types, whether or not they support thresholds.
7.1 Element definitions overview, Table 60
My comment: shows which element type support thresholds and which not.
7.2.4 Threshold control element format
All fields in the threshold control element are advisory. The enclosure
services process shall ignore the contents of the threshold control element
for those elements that have no value to be compared with a threshold and for
those elements that do not implement the threshold function.
My comment: this statement suggests that threshold descriptors for even those
element types, that do not support threshold, are included in the Threshold
Out/In diagnostic page, however, the application client and the enclosure
services process (ESP) are supposed to ignore them.
7.3 Field definitions for all element types
My comments: this section does not describe the threshold descriptors for
element types that do not support threshold. Not even a generic descriptor
with 4 reserved bytes is defined.
If the readers are to assume that the threshold descriptors for even those
element types that do not support threshold are to be included in the
Threshold Out/In diagnostic pages, then they are also supposed to assume a
generic 4-byte threshold descriptors with all bytes as reserved as they are
supposed to be ignored by both the application client and the ESP.
If the readers are to assume that the Threshold Out/In pages should include
only those element types that support threshold then there is no question of
assuming a generic 4-bytes reserved descriptor and no question of ignoring
them.
Based on the above there are many "strong" points that indicate that the
Threshold Out/In pages include even those element types that do not support
thresholds and there are some "weak" points that indicate that they don't
include those element types.
Did the spec authors intended to include additional descriptors in the page
that will never be used?
Or were the Threshold Out/In diagnostic pages meant to be similar to the
Additional Element Status diagnostic page where in only a selected subset of
element types appear in these pages?
In my opinion the spec authors did not intend to include additional
descriptors in the page that will never be used and thus the Threshold Out/In
diagnostic page is similar to the Additional Element Status diagnostic page
where only a limited subset of element types appear in these pages. However,
I could be wrong, thus please clarify.
Thanks,
Raj


From Raj.Divecha at dothill.com  Fri May  4 13:36:42 2012
From: Raj.Divecha at dothill.com (Raj Divecha)
Date: Fri, 4 May 2012 14:36:42 -0600
Subject: Seeking clarification on Threshold Out/In diagnostic pages
Message-ID: <mailman.122.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205042_f.htm">HTML-formatted message</a>

Matt,
Yeah that's a strong indicator indeed, I too acknowledge that in my email.
However, those placeholder/reserved threshold elements are a huge wastage and
amounts to unnecessary data being transferred. Thus I believe that the
authors of the SES spec wouldn't have intended the same and is a thing that
does not clearly come out of the spec.
Consider the below given configuration of an imaginary enclosure. In this we
are talking about sending/receiving 352 bytes of useless data, that is
approximately 80% wastage. The number of useless bytes would almost multiply
as you add subenclosures.
24
Array Device Slot elements
2
Power Supply elements
6
Cooling elements
4
Temperature Sensor elements
1
Door Lock element
1
Audible Alarm element
2
Enclosure Services Controller Electronics elements
1
Invalid Operation Reason element
1
UPS element
1
Display element
1
Enclosure element
6
Voltage Sensor elements
4
Current Sensor elements
2
SAS Expander elements
30
SAS Connector elements
2
VS element 1
4
VS element 2
As the authors limited the number of element types appearing in the
Additional Element Status diagnostic page, it is probable that they intended
the same for the Threshold Out/In diagnostic page but unfortunately it didn't
came out that way in the spec.
Raj
From: Matthew_Jacobs at Dell.com [mailto:Matthew_Jacobs at Dell.com]
Sent: Friday, May 04, 2012 1:42 PM
To: Raj Divecha; t10 at t10.org
Subject: RE: Seeking clarification on Threshold Out/In diagnostic pages
Raj,
The descriptions of the threshold control descriptor list and the threshold
status descriptor list in sections 6.1.8 and 6.1.9 state that the list
contains a control/status "descriptor for each type descriptor header in the
Configuration diagnostic page".  From that, I believe all individual elements
defined in the Configuration diagnostic page have a threshold element in the
Threshold in/Out diagnostic page even if it is just a placeholder/reserved
threshold element.
Matt
From: owner-t10 at t10.org<mailto:owner-t10 at t10.org>
[mailto:owner-t10 at t10.org]<mailto:[mailto:owner-t10 at t10.org]> On Behalf Of
Raj Divecha
Sent: Friday, May 04, 2012 12:29 PM
To: t10 at t10.org<mailto:t10 at t10.org>
Subject: SES: Seeking clarification on Threshold Out/In diagnostic pages
Hi,
I searched the T10 emails for this but didn't found anything.
The SES spec is a bit ambiguous regarding which element types should be
included in the Threshold Out/In diagnostic page. A clarification would be
helpful.
The following are the excerpts from the 2r20 spec. Below each excerpt is my
comment. The questions are at the end of the email.
6.1.8 Threshold Out diagnostic page
The Threshold Out diagnostic page is transmitted to the enclosure services
process to establish threshold values for those elements that have limited
sensing capability (e.g., temperature sensors, uninterruptible power
supplies, voltage sensors, and current sensors).
My comment: this statement "possibly" suggests that this page includes only
those element types that support threshold.
The threshold control descriptor list contains a threshold control descriptor
for each type descriptor header in the Configuration diagnostic page (see
6.1.2).
My comment: this statement "strongly" suggests that this page includes all
element types, whether or not they support thresholds.
7.1 Element definitions overview, Table 60
My comment: shows which element type support thresholds and which not.
7.2.4 Threshold control element format
All fields in the threshold control element are advisory. The enclosure
services process shall ignore the contents of the threshold control element
for those elements that have no value to be compared with a threshold and for
those elements that do not implement the threshold function.
My comment: this statement suggests that threshold descriptors for even those
element types, that do not support threshold, are included in the Threshold
Out/In diagnostic page, however, the application client and the enclosure
services process (ESP) are supposed to ignore them.
7.3 Field definitions for all element types
My comments: this section does not describe the threshold descriptors for
element types that do not support threshold. Not even a generic descriptor
with 4 reserved bytes is defined.
If the readers are to assume that the threshold descriptors for even those
element types that do not support threshold are to be included in the
Threshold Out/In diagnostic pages, then they are also supposed to assume a
generic 4-byte threshold descriptors with all bytes as reserved as they are
supposed to be ignored by both the application client and the ESP.
If the readers are to assume that the Threshold Out/In pages should include
only those element types that support threshold then there is no question of
assuming a generic 4-bytes reserved descriptor and no question of ignoring
them.
Based on the above there are many "strong" points that indicate that the
Threshold Out/In pages include even those element types that do not support
thresholds and there are some "weak" points that indicate that they don't
include those element types.
Did the spec authors intended to include additional descriptors in the page
that will never be used?
Or were the Threshold Out/In diagnostic pages meant to be similar to the
Additional Element Status diagnostic page where in only a selected subset of
element types appear in these pages?
In my opinion the spec authors did not intend to include additional
descriptors in the page that will never be used and thus the Threshold Out/In
diagnostic page is similar to the Additional Element Status diagnostic page
where only a limited subset of element types appear in these pages. However,
I could be wrong, thus please clarify.
Thanks,
Raj


From lohmeyer at t10.org  Sat May  5 23:01:12 2012
From: lohmeyer at t10.org (T10 Document Administrator)
Date: Sun, 6 May 2012 00:01:12 -0600
Subject: Recent T10 documents uploaded since 2012/04/29
Message-ID: <mailman.123.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* T10 Document Administrator <lohmeyer at t10.org>
*
Proposals
---------
SBC-4 SPC-5 Atomic writes and reads
(by: Rob Elliott and Ashish Batwara)
T10/11-229r4   Uploaded: 2012/05/01   276590 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-229r4.pdf
SPC-4: Device Internal Status Dump
(by: Frederick Knight)
T10/11-322r1   Uploaded: 2012/05/04   205010 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-322r1.pdf
SOP Asynchronous Events
(by: Steve Johnson and Rob Elliott)
T10/11-391r1   Uploaded: 2012/04/30   145719 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-391r1.pdf
SBC-4 SPC-5 Scattered writes, optionally atomic
(by: Rob Elliott and Ashish Batwara)
T10/12-086r2   Uploaded: 2012/05/01   175800 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-086r2.pdf
SBC-4 SPC-5 Gathered reads, optionally atomic
(by: Rob Elliott and Ashish Batwara)
T10/12-087r2   Uploaded: 2012/05/01   175625 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-087r2.pdf
SSC-4 More TapeAlert flag activation conditions
(by: Curtis Ballard)
T10/12-109r2   Uploaded: 2012/05/04   183243 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-109r2.pdf
SAM-5/SPC-4: REPORT LUNS new select report types
(by: Frederick Knight)
T10/12-124r0   Uploaded: 2012/05/04   284720 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-124r0.pdf
SBC-3: Definitions for read, write, verify, and unmap operations
(by: Mark Evans)
T10/12-139r2   Uploaded: 2012/05/04   93090 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-139r2.pdf
SOP Request identifier model
(by: Rob Elliott)
T10/12-148r2   Uploaded: 2012/05/04   348367 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-148r2.pdf
SSC-4 Resolve letter ballot #HPQ-76
(by: Curtis Ballard)
T10/12-162r0   Uploaded: 2012/05/04   134008 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-162r0.pdf
SOP Bridge error responses
(by: Rob Elliott)
T10/12-193r2   Uploaded: 2012/04/30   249698 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-193r2.pdf
SOP Bridge error responses
(by: Rob Elliott)
T10/12-193r3   Uploaded: 2012/04/30   249582 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-193r3.pdf
PQI Device Status register and Error Data register
(by: Ie-Wei Njoo)
T10/12-194r5   Uploaded: 2012/05/04   369917 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-194r5.pdf
PQI - SGL type support for PQI IUs and other IUs
(by: Ie-Wei Njoo)
T10/12-202r1   Uploaded: 2012/05/04   145948 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-202r1.pdf
SOP: Annex A.x - SGL Types for SOP
(by: Ie-Wei Njoo)
T10/12-204r1   Uploaded: 2012/05/04   96097 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-204r1.pdf
SPC-4, SBC-3: Sanitize operation definition clarification and
expansion
(by: Mark Evans)
T10/12-220r1   Uploaded: 2012/05/02   28601 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-220r1.pdf
Rewording of partitioning type in 12-127r1
(by: Kevin Butt)
T10/12-234r0   Uploaded: 2012/04/30   48973 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-234r0.pdf
SOP TBD cleanups
(by: Rob Elliott)
T10/12-235r0   Uploaded: 2012/05/01   147744 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-235r0.pdf
SOP merge IQ ERROR IU into EVENT IU
(by: Rob Elliott)
T10/12-240r0   Uploaded: 2012/05/02   188659 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-240r0.pdf
T11 Liaison Report April 2012
(by: Steven Wilson)
T10/12-241r0   Uploaded: 2012/05/04   25770 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-241r0.pdf
SSC-4: Informational Exceptions Control mode page
(by: Curtis Ballard)
T10/12-245r0   Uploaded: 2012/05/04   96008 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-245r0.pdf
SBC-3: VERIFY SAME command
(by: Frederick Knight)
T10/12-246r0   Uploaded: 2012/05/04   167880 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-246r0.pdf
Working Drafts
--------------
SCSI Primary Commands - 4 (SPC-4)
(Editor: Ralph Weber)
 Rev: 35d      Uploaded: 2012/04/30   4258142 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc4r35d.pdf
SCSI Primary Commands - 4 (SPC-4)
(Editor: Ralph Weber)
 Rev: 35e      Uploaded: 2012/05/04   4268629 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc4r35e.pdf
SCSI Primary Commands - 4 (SPC-4)
(Editor: Ralph Weber)
 Rev: 35f      Uploaded: 2012/05/05   4273780 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc4r35f.pdf
(Report generated on 2012/05/06 at 00:01:12)
*
* 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 May  7 10:53:58 2012
From: lohmeyer at t10.org (John Lohmeyer)
Date: Mon, 7 May 2012 11:53:58 -0600
Subject: SAT Minutes posted
Message-ID: <mailman.124.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* John Lohmeyer <lohmeyer at t10.org>
*
The draft minutes of the 5/7/12 SAT working group meeting are available at:
   http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-236r0.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.stevens at wdc.com  Tue May  8 11:33:16 2012
From: curtis.stevens at wdc.com (Curtis Stevens)
Date: Tue, 8 May 2012 18:33:16 +0000
Subject: SOPQI June WG Meeting Arrangements
Message-ID: <mailman.125.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205080_f.htm">HTML-formatted message</a>
Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205080_ann-sopwg_120614.pdf">ann-sopwg_120614.pdf</a>

Attached is the meeting announcement for the SOPQI WG meeting scheduled for
June 13-15.  This meeting is scheduled to start at 9am on Wednesday 13-June. 
The reservation link for the meeting is now active.  If you have questions
please respond Curtis.Stevens at wdc.com
-------------------------------------------------
Curtis E. Stevens
Director, Standards & Features Technology
3355 Michelson Dr. #100
Office: 1-1041
Irvine, Ca. 92612
Phone: 949-672-7933
Cell: 949-307-5050
E-Mail: Curtis.Stevens at WDC.com
Remember, you may only be blamed for something if you are actually doing
something.


From lohmeyer at t10.org  Wed May  9 11:14:17 2012
From: lohmeyer at t10.org (John Lohmeyer)
Date: Wed, 9 May 2012 12:14:17 -0600
Subject: CAP Minutes posted
Message-ID: <mailman.126.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* John Lohmeyer <lohmeyer at t10.org>
*
The draft minutes of the 5/7-8/12 CAP working group meeting are available at:
   http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-237r0.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 alvin.cox at seagate.com  Wed May  9 16:19:06 2012
From: alvin.cox at seagate.com (Alvin Cox)
Date: Wed, 9 May 2012 18:19:06 -0500
Subject: Reminder: SAS PHY Teleconference Thursday, May 17, 2012 10:00am CDT
Message-ID: <mailman.127.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205091_f.htm">HTML-formatted message</a>

Agenda:
Connector related items
Electrical
SAS-3 Receiver device compliance (12-244) [Gagnon]
SAS-3 TxRx connection compliance (12-243) [Gagnon]
SAS PHY: End-to-End Compliance Methodology and Specification (11-416)
[Gagnon]
Next call:
Thursday, May 17, 2012, 10:00 am CDT
Toll Free Dial in Number: (877)810-9442
International Access/Caller Paid Dial In Number: (636)651-3190
PARTICIPANT CODE: 3243413
Webex information: **
Topic: SAS-3
Date: Thursday, May 17, 2012
Time: 10:00 am, Central Daylight Time (Chicago, GMT-05:00)
Meeting Number: 827 988 093
Meeting Password: sas12gbps
-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&R
T=MiM3
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: sas12gbps
4. Click "Join".
To view in other time zones or languages, please click the link:
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&O
RT=MiM3
-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://seagate.webex.com/seagate/mc
2. On the left navigation bar, click "Support".
To update this meeting to your calendar program (for example Microsoft
Outlook), click this link:
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&ICS=MRS2&LD=1&RD=2
&ST=1&SHA2=pEI2tL0j5oE58s9ytOQWHuV98SACdVZgiFnrG-CNDds=&RT=MiM3
WebEx will automatically setup Meeting Manager for Windows the first time
you join a meeting. To save time, you can setup prior to the meeting by
clicking this link:
https://seagate.webex.com/seagate/meetingcenter/mcsetup.php
The playback of UCF (Universal Communications Format) rich media files
requires appropriate players. To view this type of rich media files in the
meeting, please check whether you have the players installed on your
computer by going to https://seagate.webex.com/seagate/systemdiagnosis.php.
-- 
Alvin Cox
Seagate Technology, LLC
Cell 405-206-4809
Office 405-392-3738
E-Mail	alvin.cox at seagate.com


From lohmeyer at t10.org  Thu May 10 11:07:33 2012
From: lohmeyer at t10.org (John Lohmeyer)
Date: Thu, 10 May 2012 12:07:33 -0600
Subject: SAS Protocol WG Minutes posted
Message-ID: <mailman.128.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* John Lohmeyer <lohmeyer at t10.org>
*
The draft minutes of the 5/9/12 SAS Protocol working group meeting are
available at:
   http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-238r0.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 scsi.bbs at lsi.com  Thu May 10 17:07:25 2012
From: scsi.bbs at lsi.com (T10 Voting Administrator)
Date: Thu, 10 May 2012 18:07:25 -0600
Subject: SPC-4: T10 Letter Ballot T10LBVOTE 12-267r0
Message-ID: <mailman.129.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* T10 Voting Administrator <scsi.bbs at lsi.com>
*
 2012/05/10 18:05:46
A T10 letter ballot (T10/12-267r0) has just been issued.
The topic of this letter ballot is:
  Forwarding SPC-4 to First Public Review
This ballot closes 2012/06/29 at 12:00 noon MT.
If you are a T10 voting member, you should receive a separate
email with details of how to vote.
If you do not receive this email, it is likely that a spam
filter blocked its delivery. You can also find voting
instructions in the Members section of the T10 committee
web site.
Please do NOT reply to this automated email.
*
* 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 May 11 09:39:22 2012
From: lohmeyer at t10.org (John Lohmeyer)
Date: Fri, 11 May 2012 10:39:22 -0600
Subject: T10 minutes posted
Message-ID: <mailman.130.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* John Lohmeyer <lohmeyer at t10.org>
*
The draft minutes of T10 Plenary meeting #109 (5/10/2012) are available at:
   http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-239r0.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 lohmeyer at t10.org  Fri May 11 13:49:40 2012
From: lohmeyer at t10.org (John Lohmeyer)
Date: Fri, 11 May 2012 14:49:40 -0600
Subject: T10 Reflector clean up
Message-ID: <mailman.131.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* John Lohmeyer <lohmeyer at t10.org>
*
#
#
#
#
#
#
#
#
#
#
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:
  william_lin at goCyberlink.com
  cnadams at tycoelectronics.com
  jeyaram_g at hcl.in
  mark.hornacek at central.sun.com
  simon.poon at sun.com
  mark.carlson at sun.com
  greg.price at sun.com
  anand.jain at sun.com
  peter.teng at am.necel.com
  Seow.Tan at am.necel.com
  rajiv at ti.com
  mmoeller at email.cinch.com
  jmcgrath at email.cinch.com
  michael_herz at agilent.com
  hsangha at link-a-media.com
  jaydiep at us.ibm.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.stevens at wdc.com  Fri May 11 15:07:50 2012
From: curtis.stevens at wdc.com (Curtis Stevens)
Date: Fri, 11 May 2012 22:07:50 +0000
Subject: SOPQI
Message-ID: <mailman.132.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205112_f.htm">HTML-formatted message</a>
Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205112_nameless-3696-3.txt">nameless-3696-3.txt</a>

CURTIS STEVENS invites you to an online meeting using WebEx.
Meeting Number: 745 241 979
Meeting Password: This meeting does not require a password.
-------------------------------------------------------
To join this meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://premconf.webex.com/premconf/j.php?J=745241979
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: This meeting does
not require a password.
4. Click "Join".
5. Follow the instructions that appear on your screen.
-------------------------------------------------------
Teleconference information
-------------------------------------------------------
Call-in toll-free number (Premiere): 1-866-546-3377  (US)
Call-in number (Premiere): 1-719-234-7872  (US)
Attendee access code: 982 762 9443
http://www.webex.com
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and
any documents and other materials exchanged or viewed during the session to
be recorded. By joining this session, you automatically consent to such
recordings. If you do not consent to the recording, discuss your concerns
with the meeting host prior to the start of the recording or do not join the
session. Please note that any such recordings may be subject to discovery in
the event of litigation.


From lohmeyer at t10.org  Sat May 12 23:01:17 2012
From: lohmeyer at t10.org (T10 Document Administrator)
Date: Sun, 13 May 2012 00:01:17 -0600
Subject: Recent T10 documents uploaded since 2012/05/06
Message-ID: <mailman.133.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* T10 Document Administrator <lohmeyer at t10.org>
*
Proposals
---------
SOP PQI SPC-4 overflow and underflow handling
(by: Rob Elliott)
T10/11-169r4   Uploaded: 2012/05/11   435734 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-169r4.pdf
Proposed PCI class code assignment for SOP
(by: Rob Elliott)
T10/11-173r3   Uploaded: 2012/05/11   128724 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-173r3.pdf
SBC-3 Add rebuild assist feature
(by: Gerald Houlder)
T10/11-298r6   Uploaded: 2012/05/08   100677 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-298r6.pdf
SBC-3 Add rebuild assist feature
(by: Gerald Houlder)
T10/11-298r7   Uploaded: 2012/05/08   97052 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-298r7.pdf
SOP Asynchronous Events
(by: Steve Johnson and Rob Elliott)
T10/11-391r2   Uploaded: 2012/05/11   146162 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-391r2.pdf
SOP - Annex B
(by: Kevin Marks)
T10/11-404r1   Uploaded: 2012/05/11   31748 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-404r1.pdf
SAS PHY: End-to-End Compliance Methodology and Specification
(by: Mathieu Gagnon)
T10/11-416r7   Uploaded: 2012/05/07   262782 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-416r7.pdf
SBC-3: LBA Access Hints
(by: Frederick Knight)
T10/11-436r6   Uploaded: 2012/05/07   423030 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-436r6.pdf
PQI Worklist
(by: Ie Wei Njoo and Tim Symons)
T10/11-451r7   Uploaded: 2012/05/09   32112 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-451r7.pdf
PQI Worklist
(by: Ie Wei Njoo and Tim Symons)
T10/11-451r7   Uploaded: 2012/05/09   43520 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-451r7.xls
SSC-4: Letter Ballot Comment Database
(by: David Peterson)
T10/11-478r4   Uploaded: 2012/05/09   3000348 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-478r4.pdf
SAM-5 SCSI port identifiers for UAS
(by: Rob Elliott)
T10/11-517r3   Uploaded: 2012/05/10   252393 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-517r3.pdf
SPL-2 Letter Ballot Comments Resolution
(by: George Penokie)
T10/12-049r4   Uploaded: 2012/05/10   6194828 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-049r4.fdf
SPL-2 Letter Ballot Comments Resolution
(by: George Penokie)
T10/12-049r4   Uploaded: 2012/05/10   8689503 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-049r4.pdf
SSC-4 LB comment #QTM-31, Ready State Usage
(by: Paul Suhler)
T10/12-068r1   Uploaded: 2012/05/07   24551 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-068r1.docx
SSC-4 LB comment #QTM-31, Ready State Usage
(by: Paul Suhler)
T10/12-068r1   Uploaded: 2012/05/07   22794 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-068r1.fdf
SSC-4 LB comment #QTM-31, Ready State Usage
(by: Paul Suhler)
T10/12-068r1   Uploaded: 2012/05/07   4281033 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-068r1.pdf
SSC-4 LB comment #QTM-31, Ready State Usage
(by: Paul Suhler)
T10/12-068r2   Uploaded: 2012/05/09   24226 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-068r2.fdf
SSC-4 LB comment #QTM-31, Ready State Usage
(by: Paul Suhler)
T10/12-068r2   Uploaded: 2012/05/09   4281050 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-068r2.pdf
T13 Liaison Report to T10
(by: Dan Colegrove)
T10/12-077r2   Uploaded: 2012/05/09   32262 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-077r2.pdf
PQI Reset register
(by: Ie-Wei Njoo)
T10/12-088r3   Uploaded: 2012/05/07   302899 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-088r3.pdf
PQI Reset register
(by: Ie-Wei Njoo)
T10/12-088r4   Uploaded: 2012/05/09   323581 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-088r4.pdf
SOP PCIe specific IU parameters
(by: Satish Vasudeva)
T10/12-090r5   Uploaded: 2012/05/10   129349 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-090r5.pdf
SPL-2: Managing dual coefficient adjustment requests
(by: George Penokie, Bill Voorhees)
T10/12-091r7   Uploaded: 2012/05/10   230649 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-091r7.pdf
#IBM-Late-31Jan12: LBP table clean-up
(by: Kevin Butt)
T10/12-101r2   Uploaded: 2012/05/09   69408 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-101r2.pdf
SSC-4: Encryption TapeAlert
(by: Kevin Butt)
T10/12-113r1   Uploaded: 2012/05/09   21776 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-113r1.pdf
SPC-4: Lost PR state
(by: Frederick Knight)
T10/12-125r2   Uploaded: 2012/05/08   205756 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-125r2.pdf
SPC-4: Lost PR state
(by: Frederick Knight)
T10/12-125r3   Uploaded: 2012/05/08   206039 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-125r3.pdf
SOP Request identifier model
(by: Rob Elliott)
T10/12-148r3   Uploaded: 2012/05/11   348393 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-148r3.pdf
SPC-4 / SBC-3: Third Party Copy Additions
(by: Frederick Knight)
T10/12-166r1   Uploaded: 2012/05/07   211129 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-166r1.pdf
Minutes SSC-4 March 06, 2012
(by: Kevin Butt)
T10/12-167r1   Uploaded: 2012/05/09   51899 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-167r1.pdf
editorial changes to SOP Rev 2
(by: Curtis Stevens)
T10/12-185r0   Uploaded: 2012/05/10   1324680 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-185r0.pdf
SBC-3 task set clarifications
(by: Rob Elliott)
T10/12-186r1   Uploaded: 2012/05/08   96829 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-186r1.pdf
SBC-3 Advise migrating from XDWRITE and XDREAD to XDWRITEREAD
(by: Rob Elliott)
T10/12-191r1   Uploaded: 2012/05/08   85204 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-191r1.pdf
SOP Bridge error responses
(by: Rob Elliott)
T10/12-193r4   Uploaded: 2012/05/11   252360 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-193r4.pdf
PQI Device Status register and Error Data register
(by: Ie-Wei Njoo)
T10/12-194r6   Uploaded: 2012/05/08   374505 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-194r6.pdf
PQI sleep, shutdown, and reboot notification
(by: Rob Elliott)
T10/12-195r2   Uploaded: 2012/05/11   208944 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-195r2.pdf
Minutes of SAS PHY Working Group conference call March 29, 2012
(by: Alvin Cox)
T10/12-201r0   Uploaded: 2012/05/10   19017 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-201r0.pdf
Style Guide: Lists
(by: Mark Evans)
T10/12-221r1   Uploaded: 2012/05/09   27301 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-221r1.pdf
SPC-4: RTPG Clarification
(by: Frederick Knight)
T10/12-222r1   Uploaded: 2012/05/07   159122 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-222r1.pdf
SOP: Data transfer model
(by: Mark Evans)
T10/12-223r1   Uploaded: 2012/05/11   19989 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-223r1.pdf
Electrical Modeling & Simulation Summary, SFF-8639 Rcpt to Dual Port
Plug
(by: Scott Shuey)
T10/12-232r0   Uploaded: 2012/05/08   445803 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-232r0.pdf
Rewording of partitioning type in 12-127r1
(by: Kevin Butt)
T10/12-234r1   Uploaded: 2012/05/09   49242 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-234r1.pdf
SOP TBD cleanups
(by: Rob Elliott)
T10/12-235r1   Uploaded: 2012/05/11   147147 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-235r1.pdf
Minutes of SAT Working Group - May 7, 2012
(by: Weber & Lohmeyer)
T10/12-236r0   Uploaded: 2012/05/07   28621 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-236r0.htm
Minutes of SAT Working Group - May 7, 2012
(by: Weber & Lohmeyer)
T10/12-236r0   Uploaded: 2012/05/07   86278 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-236r0.pdf
Minutes of CAP Working Group - May 7-8, 2012
(by: Weber & Lohmeyer)
T10/12-237r0   Uploaded: 2012/05/09   67804 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-237r0.htm
Minutes of CAP Working Group - May 7-8, 2012
(by: Weber & Lohmeyer)
T10/12-237r0   Uploaded: 2012/05/09   156225 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-237r0.pdf
Minutes of SAS Protocol Working Group - May 9, 2012
(by: Weber & Lohmeyer)
T10/12-238r0   Uploaded: 2012/05/10   34720 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-238r0.htm
Minutes of SAS Protocol Working Group - May 9, 2012
(by: Weber & Lohmeyer)
T10/12-238r0   Uploaded: 2012/05/10   97552 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-238r0.pdf
Minutes of T10 Plenary Meeting #109 - May 10, 2012
(by: Weber & Lohmeyer)
T10/12-239r0   Uploaded: 2012/05/11   144087 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-239r0.htm
Minutes of T10 Plenary Meeting #109 - May 10, 2012
(by: Weber & Lohmeyer)
T10/12-239r0   Uploaded: 2012/05/11   301494 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-239r0.pdf
SOP merge IQ ERROR IU into EVENT IU
(by: Rob Elliott)
T10/12-240r1   Uploaded: 2012/05/11   188927 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-240r1.pdf
SAS-3 Transmitter device compliance
(by: Mathieu Gagnon)
T10/12-242r0   Uploaded: 2012/05/07   160661 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-242r0.pdf
SAS-3 TxRx connection compliance
(by: Mathieu Gagnon)
T10/12-243r0   Uploaded: 2012/05/07   269664 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-243r0.pdf
SAS-3 Receiver device compliance
(by: Mathieu Gagnon)
T10/12-244r0   Uploaded: 2012/05/07   127894 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-244r0.pdf
A SAM-5 hierarchy of logical unit numbers (or Plan 9 From Outer Space)
(by: Ralph Weber)
T10/12-247r0   Uploaded: 2012/05/07   108671 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-247r0.pdf
SAT-3: VERIFY SAME Translation
(by: Frederick Knight)
T10/12-248r0   Uploaded: 2012/05/07   128076 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-248r0.pdf
SAS-3 Transmitter coefficient ranges
(by: Mathieu Gagnon)
T10/12-249r0   Uploaded: 2012/05/07   446140 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-249r0.pdf
SAS-3 Transmitter coefficient ranges
(by: Mathieu Gagnon)
T10/12-249r1   Uploaded: 2012/05/08   493932 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-249r1.pdf
SAS-3 Transmitter coefficient ranges
(by: Mathieu Gagnon)
T10/12-249r2   Uploaded: 2012/05/08   496160 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-249r2.pdf
SAS-3 TE Mini SAS HD 6m
(by: Harvey Newman)
T10/12-250r0   Uploaded: 2012/05/07   423373 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-250r0.pdf
SAS-3 TE Mini SAS HD 6m
(by: Harvey Newman)
T10/12-250r0   Uploaded: 2012/05/07   22228329 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-250r0.zip
SPL-3 Persistent Connection
(by: George Penokie)
T10/12-251r0   Uploaded: 2012/05/08   599566 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-251r0.pdf
SAS-3 Compliance and measurement points
(by: Mathieu Gagnon)
T10/12-252r0   Uploaded: 2012/05/08   79569 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-252r0.pdf
SAS-3 Compliance and measurement points
(by: Mathieu Gagnon)
T10/12-252r1   Uploaded: 2012/05/08   99228 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-252r1.pdf
SAS-3 Reference transmitter
(by: Mathieu Gagnon)
T10/12-253r0   Uploaded: 2012/05/08   105105 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-253r0.pdf
SAS-3 Reference transmitter
(by: Mathieu Gagnon)
T10/12-253r1   Uploaded: 2012/05/08   141157 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-253r1.pdf
PQI Queue ID field offset fix
(by: Ie-Wei Njoo)
T10/12-254r0   Uploaded: 2012/05/08   187445 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-254r0.pdf
SOP Meeting Announcement - June 13-15, 2012
(by: Curtis Stevens)
T10/12-255r0   Uploaded: 2012/05/08   9152 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-255r0.pdf
SAM-5:	Annex corrections for ADT
(by: Paul Suhler)
T10/12-256r0   Uploaded: 2012/05/08   31877 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-256r0.pdf
SAM-5:	Annex corrections for ADT
(by: Paul Suhler)
T10/12-256r1   Uploaded: 2012/05/08   32097 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-256r1.pdf
Features for ADT-3
(by: Paul Suhler)
T10/12-257r0   Uploaded: 2012/05/10   29889 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-257r0.pdf
Minutes SSC-4 May 09, 2012
(by: Kevin Butt)
T10/12-258r0   Uploaded: 2012/05/09   56960 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-258r0.pdf
Minutes of SAS Phy working group meeting May 8, 2012
(by: Alvin Cox and Bill Voorhees)
T10/12-259r0   Uploaded: 2012/05/10   47375 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-259r0.pdf
STA - T10 Liaison Report May 10, 2012
(by: Marty Czekalski)
T10/12-261r0   Uploaded: 2012/05/10   381727 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-261r0.pdf
Minutes of SOP-PQI Working Group - 10-11 May 2012
(by: Rob Elliott)
T10/12-262r0   Uploaded: 2012/05/11   155770 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-262r0.pdf
Agenda for T10 Meeting #110 July 19, 2012
(by: John Lohmeyer)
T10/12-263r0   Uploaded: 2012/05/10   15173 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-263r0.pdf
T10 Project Summary - May 2012
(by: John Lohmeyer)
T10/12-264r0   Uploaded: 2012/05/10   30004 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-264r0.pdf
Jeopardy Letter for May 2012 meeting
(by: John Lohmeyer)
T10/12-265r0   Uploaded: 2012/05/10   31915 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-265r0.pdf
Instructions for SPC-4 Letter Ballot reviewers
(by: Ralph Weber)
T10/12-266r0   Uploaded: 2012/05/10   32288 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-266r0.pdf
Letter Ballot on forwarding SPC-4 to First Public Review
(by: John Lohmeyer)
T10/12-267r0   Uploaded: 2012/05/10   34665 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-267r0.pdf
Working Drafts
--------------
SCSI over PCIe(r) architecture (SOP)
(Editor: Curtis Stevens)
 Rev: 03       Uploaded: 2012/05/10   1677930 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=sop-r03.pdf
SCSI Primary Commands - 4 (SPC-4)
(Editor: Ralph Weber)
 Rev: 36       Uploaded: 2012/05/10   4527805 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc4r36.pdf
SCSI Primary Commands - 4 (SPC-4)
(Editor: Ralph Weber)
 Rev: 36a      Uploaded: 2012/05/10   4564136 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc4r36a.pdf
SAS Protocol Layer - 2 (SPL-2)
(Editor: George Penokie)
 Rev: 04e      Uploaded: 2012/05/10   9247783 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spl2r04e.pdf
SAS Protocol Layer - 2 (SPL-2)
(Editor: George Penokie)
 Rev: 05       Uploaded: 2012/05/10   9024006 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spl2r05.pdf
(Report generated on 2012/05/13 at 00:01:17)
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From curtis.stevens at wdc.com  Mon May 14 09:41:45 2012
From: curtis.stevens at wdc.com (Curtis Stevens)
Date: Mon, 14 May 2012 16:41:45 +0000
Subject: SOPQI WG Meeting
Message-ID: <mailman.134.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205140_f.htm">HTML-formatted message</a>
Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205140_nameless-3584-3.txt">nameless-3584-3.txt</a>

CURTIS STEVENS invites you to an online meeting using WebEx.
Meeting Number: 749 063 819
Meeting Password: This meeting does not require a password.
-------------------------------------------------------
To join this meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://premconf.webex.com/premconf/j.php?J=749063819
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: This meeting does
not require a password.
4. Click "Join".
5. Follow the instructions that appear on your screen.
-------------------------------------------------------
Teleconference information
-------------------------------------------------------
Call-in toll-free number (Premiere): 1-866-546-3377  (US)
Call-in number (Premiere): 1-719-234-7872  (US)
Attendee access code: 982 762 9443
http://www.webex.com
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and
any documents and other materials exchanged or viewed during the session to
be recorded. By joining this session, you automatically consent to such
recordings. If you do not consent to the recording, discuss your concerns
with the meeting host prior to the start of the recording or do not join the
session. Please note that any such recordings may be subject to discovery in
the event of litigation.


From curtis.stevens at wdc.com  Mon May 14 09:46:46 2012
From: curtis.stevens at wdc.com (Curtis Stevens)
Date: Mon, 14 May 2012 16:46:46 +0000
Subject: SOPQI WG Meeting
Message-ID: <mailman.135.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205141_f.htm">HTML-formatted message</a>
Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205141_nameless-3584-6.txt">nameless-3584-6.txt</a>

CURTIS STEVENS invites you to an online meeting using WebEx.
Meeting Number: 747 607 157
Meeting Password: This meeting does not require a password.
-------------------------------------------------------
To join this meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://premconf.webex.com/premconf/j.php?J=747607157
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: This meeting does
not require a password.
4. Click "Join".
5. Follow the instructions that appear on your screen.
-------------------------------------------------------
Teleconference information
-------------------------------------------------------
Call-in toll-free number (Premiere): 1-866-546-3377  (US)
Call-in number (Premiere): 1-719-234-7872  (US)
Attendee access code: 982 762 9443
http://www.webex.com
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and
any documents and other materials exchanged or viewed during the session to
be recorded. By joining this session, you automatically consent to such
recordings. If you do not consent to the recording, discuss your concerns
with the meeting host prior to the start of the recording or do not join the
session. Please note that any such recordings may be subject to discovery in
the event of litigation.


From curtis.stevens at wdc.com  Mon May 14 09:43:29 2012
From: curtis.stevens at wdc.com (Curtis Stevens)
Date: Mon, 14 May 2012 16:43:29 +0000
Subject: SOPQI WG Meeting
Message-ID: <mailman.136.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205142_f.htm">HTML-formatted message</a>
Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205142_nameless-3584-9.txt">nameless-3584-9.txt</a>

CURTIS STEVENS invites you to an online meeting using WebEx.
Meeting Number: 746 675 960
Meeting Password: This meeting does not require a password.
-------------------------------------------------------
To join this meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://premconf.webex.com/premconf/j.php?J=746675960
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: This meeting does
not require a password.
4. Click "Join".
5. Follow the instructions that appear on your screen.
-------------------------------------------------------
Teleconference information
-------------------------------------------------------
Call-in toll-free number (Premiere): 1-866-546-3377  (US)
Call-in number (Premiere): 1-719-234-7872  (US)
Attendee access code: 982 762 9443
http://www.webex.com
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and
any documents and other materials exchanged or viewed during the session to
be recorded. By joining this session, you automatically consent to such
recordings. If you do not consent to the recording, discuss your concerns
with the meeting host prior to the start of the recording or do not join the
session. Please note that any such recordings may be subject to discovery in
the event of litigation.


From curtis.stevens at wdc.com  Mon May 14 09:50:26 2012
From: curtis.stevens at wdc.com (Curtis Stevens)
Date: Mon, 14 May 2012 16:50:26 +0000
Subject: SOPQI WG Meeting
Message-ID: <mailman.137.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205143_f.htm">HTML-formatted message</a>
Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205143_nameless-3676-3.txt">nameless-3676-3.txt</a>

CURTIS STEVENS invites you to an online meeting using WebEx.
Meeting Number: 744 206 788
Meeting Password: This meeting does not require a password.
-------------------------------------------------------
To join this meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://premconf.webex.com/premconf/j.php?J=744206788
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: This meeting does
not require a password.
4. Click "Join".
5. Follow the instructions that appear on your screen.
-------------------------------------------------------
Teleconference information
-------------------------------------------------------
Call-in toll-free number (Premiere): 1-866-546-3377  (US)
Call-in number (Premiere): 1-719-234-7872  (US)
Attendee access code: 982 762 9443
http://www.webex.com
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and
any documents and other materials exchanged or viewed during the session to
be recorded. By joining this session, you automatically consent to such
recordings. If you do not consent to the recording, discuss your concerns
with the meeting host prior to the start of the recording or do not join the
session. Please note that any such recordings may be subject to discovery in
the event of litigation.


From curtis.stevens at wdc.com  Mon May 14 09:54:57 2012
From: curtis.stevens at wdc.com (Curtis Stevens)
Date: Mon, 14 May 2012 16:54:57 +0000
Subject: SOPQI WG Meeting
Message-ID: <mailman.138.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205144_f.htm">HTML-formatted message</a>
Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205144_nameless-3916-3.txt">nameless-3916-3.txt</a>

CURTIS STEVENS invites you to an online meeting using WebEx.
Meeting Number: 742 509 186
Meeting Password: This meeting does not require a password.
-------------------------------------------------------
To join this meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://premconf.webex.com/premconf/j.php?J=742509186
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: This meeting does
not require a password.
4. Click "Join".
5. Follow the instructions that appear on your screen.
-------------------------------------------------------
Teleconference information
-------------------------------------------------------
Call-in toll-free number (Premiere): 1-866-546-3377  (US)
Call-in number (Premiere): 1-719-234-7872  (US)
Attendee access code: 982 762 9443
http://www.webex.com
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and
any documents and other materials exchanged or viewed during the session to
be recorded. By joining this session, you automatically consent to such
recordings. If you do not consent to the recording, discuss your concerns
with the meeting host prior to the start of the recording or do not join the
session. Please note that any such recordings may be subject to discovery in
the event of litigation.


From curtis.stevens at wdc.com  Mon May 14 15:55:58 2012
From: curtis.stevens at wdc.com (Curtis Stevens)
Date: Mon, 14 May 2012 22:55:58 +0000
Subject: SOP/PQI Telecons
Message-ID: <mailman.139.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205145_f.htm">HTML-formatted message</a>

I have posted the meeting calls for SOP/PQI meeting through the end of July. 
I have called these SOPQI to provide an easy to find key in writing E-Mail
rules to do sorting.  Unless there is an objection I will continue to use
this term to make the meetings easy to recognize.
-------------------------------------------------
Curtis E. Stevens
Director, Standards & Features Technology
3355 Michelson Dr. #100
Office: 1-1041
Irvine, Ca. 92612
Phone: 949-672-7933
Cell: 949-307-5050
E-Mail: Curtis.Stevens at WDC.com
Remember, you may only be blamed for something if you are actually doing
something.


From alvin.cox at seagate.com  Wed May 16 13:29:30 2012
From: alvin.cox at seagate.com (Alvin Cox)
Date: Wed, 16 May 2012 15:29:30 -0500
Subject: Reminder: SAS PHY Teleconference Thursday, May 17, 2012 10:00am CDT
Message-ID: <mailman.140.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205160_f.htm">HTML-formatted message</a>

Agenda:
Connector related items
Electrical
SAS-3 Receiver device compliance (12-244) [Gagnon]
SAS-3 TxRx connection compliance (12-243) [Gagnon]
SAS PHY: End-to-End Compliance Methodology and Specification (11-416)
[Gagnon]
We may want to have additional discussion on the common mode measurement
for 12Gbps transmitter devices
Next call: Thursday, May 17, 2012, 10:00 am CDT
Toll Free Dial in Number: (877)810-9442
International Access/Caller Paid Dial In Number: (636)651-3190
PARTICIPANT CODE: 3243413
Webex information:
Next call:
Thursday, May 17, 2012, 10:00 am CDT
Toll Free Dial in Number: (877)810-9442
International Access/Caller Paid Dial In Number: (636)651-3190
PARTICIPANT CODE: 3243413
Webex information: **
Topic: SAS-3
Date: Thursday, May 17, 2012
Time: 10:00 am, Central Daylight Time (Chicago, GMT-05:00)
Meeting Number: 827 988 093
Meeting Password: sas12gbps
-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&R
T=MiM3
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: sas12gbps
4. Click "Join".
To view in other time zones or languages, please click the link:
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&O
RT=MiM3
-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://seagate.webex.com/seagate/mc
2. On the left navigation bar, click "Support".
To update this meeting to your calendar program (for example Microsoft
Outlook), click this link:
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&ICS=MRS2&LD=1&RD=2
&ST=1&SHA2=pEI2tL0j5oE58s9ytOQWHuV98SACdVZgiFnrG-CNDds=&RT=MiM3
WebEx will automatically setup Meeting Manager for Windows the first time
you join a meeting. To save time, you can setup prior to the meeting by
clicking this link:
https://seagate.webex.com/seagate/meetingcenter/mcsetup.php
The playback of UCF (Universal Communications Format) rich media files
requires appropriate players. To view this type of rich media files in the
meeting, please check whether you have the players installed on your
computer by going to https://seagate.webex.com/seagate/systemdiagnosis.php.
-- 
Alvin Cox
Seagate Technology, LLC
Cell 405-206-4809
Office 405-392-3738
E-Mail	alvin.cox at seagate.com


From Elliott at hp.com  Wed May 16 15:30:49 2012
From: Elliott at hp.com (Elliott, Robert (Server Storage))
Date: Wed, 16 May 2012 22:30:49 +0000
Subject: T10 SAM-5 12-029 teleconference
Message-ID: <mailman.141.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205161_f.htm">HTML-formatted message</a>
Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205161_nameless-436-3.txt">nameless-436-3.txt</a>

T10 is holding a teleconference on 22 May 2012 at 1pm Central Time to go over
this SAM-5 proposal:
	12-029r2 SAM-5 Command and Task Management Function architecture
model proposal.
Event number	16505464
Event name	T10 SAM-5 12-029 discussion
Event date and time	5/22/2012 1:00 PM Central Time
Duration	120 minutes
Phone and pass code	877-675-4345 or 281-964-1607,
participant code 5185037
Event Keys
Participant key 	EPU4LZTEKV     
https://www.rooms.hp.com/attend/default.aspx?key=EPU4LZTEKV


From lohmeyer at t10.org  Sat May 19 23:01:17 2012
From: lohmeyer at t10.org (T10 Document Administrator)
Date: Sun, 20 May 2012 00:01:17 -0600
Subject: Recent T10 documents uploaded since 2012/05/13
Message-ID: <mailman.142.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* T10 Document Administrator <lohmeyer at t10.org>
*
Proposals
---------
SAS PHY: End-to-End Compliance Methodology and Specification
(by: Mathieu Gagnon)
T10/11-416r8   Uploaded: 2012/05/19   219569 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=11-416r8.pdf
PQI interrupt coalescing
(by: David Geddes)
T10/12-038r3   Uploaded: 2012/05/13   37004 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-038r3.pdf
PQI Reset register
(by: Ie-Wei Njoo)
T10/12-088r5   Uploaded: 2012/05/14   326363 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-088r5.pdf
PQI Reset register
(by: Ie-Wei Njoo)
T10/12-088r6   Uploaded: 2012/05/19   318671 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-088r6.pdf
SPC-4 SBC-3 Add progress indication description to SYNCHRONIZE CACHE
commands
(by: Gerald Houlder)
T10/12-104r3   Uploaded: 2012/05/15   45715 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-104r3.pdf
SSC-4 resolve LB review comment #HPQ-12
(by: Curtis Ballard)
T10/12-115r1   Uploaded: 2012/05/16   151296 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-115r1.pdf
SSC-4 Resolve letter ballot #HPQ-76
(by: Curtis Ballard)
T10/12-162r1   Uploaded: 2012/05/16   134695 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-162r1.pdf
SAM-5 ABORT TASK with overlapped commands
(by: Rob Elliott)
T10/12-189r1   Uploaded: 2012/05/18   253275 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-189r1.pdf
PQI - SGL type support for PQI IUs and other IUs
(by: Ie-Wei Njoo)
T10/12-202r2   Uploaded: 2012/05/14   144087 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-202r2.pdf
SOP: Annex A.x - SGL Types for SOP
(by: Ie-Wei Njoo)
T10/12-204r2   Uploaded: 2012/05/14   80212 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-204r2.pdf
PQI Memory Alignments
(by: Brad Besmer)
T10/12-212r2   Uploaded: 2012/05/14   146353 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-212r2.pdf
PQI Memory Alignments
(by: Brad Besmer)
T10/12-212r3   Uploaded: 2012/05/16   149870 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-212r3.pdf
SPC-4, SBC-3: Sanitize operation definition clarification and
expansion
(by: Mark Evans)
T10/12-220r2   Uploaded: 2012/05/15   33521 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-220r2.pdf
Minutes of T10 Plenary Meeting #109 - May 10, 2012
(by: Weber & Lohmeyer)
T10/12-239r0   Uploaded: 2012/05/15   146834 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-239r0.htm
Minutes of T10 Plenary Meeting #109 - May 10, 2012
(by: Weber & Lohmeyer)
T10/12-239r1   Uploaded: 2012/05/16   146933 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-239r1.htm
Minutes of T10 Plenary Meeting #109 - May 10, 2012
(by: Weber & Lohmeyer)
T10/12-239r1   Uploaded: 2012/05/16   307360 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-239r1.pdf
SAS-3 Transmitter device compliance
(by: Mathieu Gagnon)
T10/12-242r1   Uploaded: 2012/05/19   121309 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-242r1.pdf
SAS-3 TxRx connection compliance
(by: Mathieu Gagnon)
T10/12-243r1   Uploaded: 2012/05/19   270960 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-243r1.pdf
SAS-3 Receiver device compliance
(by: Mathieu Gagnon)
T10/12-244r1   Uploaded: 2012/05/19   216811 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-244r1.pdf
SPL-3 Persistent Connection
(by: George Penokie)
T10/12-251r1   Uploaded: 2012/05/16   553274 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-251r1.pdf
T10 Style Guide 3rd Edition
(by: George Penokie)
T10/12-269r0   Uploaded: 2012/05/15   868378 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-269r0.pdf
PQI administrator function error handling
(by: Rob Elliott)
T10/12-271r0   Uploaded: 2012/05/18   356532 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-271r0.pdf
Working Drafts
--------------
PCIe(r) architecture Queuing Interface (PQI)
(Editor: Ie-Wei Njoo)
 Rev: 05       Uploaded: 2012/05/14   1508880 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=pqi-r05.pdf
SCSI Architecture Model - 5 (SAM-5)
(Editor: George Penokie)
 Rev: 11       Uploaded: 2012/05/15   1229273 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=sam5r11.pdf
(Report generated on 2012/05/20 at 00:01:17)
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From mickey.felton at emc.com  Mon May 21 10:34:46 2012
From: mickey.felton at emc.com (mickey.felton at emc.com)
Date: Mon, 21 May 2012 13:34:46 -0400
Subject: September T10.
Message-ID: <mailman.143.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205210_f.htm">HTML-formatted message</a>

Its almost that time again to head back to Boston and try to finish a SAS
specification!
There were a number of good ideas and areas of change that were presented to
me last time we had the meeting at the Double tree.
If anyone has any other feedbacks other than what's below let me know and I
will get them addressed
1.	 Fix the wireless internet in conference rooms - We are setting up a
few more wire portals to address this concern
2.	 Fix the TV channels received -the hotel said the cable provider has
more channels than last year.
3.	 Change the lunch options - No one liked the pick your own sandwich
stlye so I'm proposing:
a.	 Pizza buffet
b.	Build your own sandwich with selection of meats
c.	 Italian buffet
d.	Fish / Chowder buffet.
4.	 Fix the Double beds vs  King rooms, more King bed rooms are
available, as usual first come first serve.
-Thanks
Mick Felton


From gerry.houlder at seagate.com  Wed May 23 08:45:51 2012
From: gerry.houlder at seagate.com (Gerry Houlder)
Date: Wed, 23 May 2012 10:45:51 -0500
Subject: Telecon information for MDC project discussion May 31, 2012
Message-ID: <mailman.144.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205230_f.htm">HTML-formatted message</a>

Agenda:
Discuss 12-034r2 updates since last telecon
Decide if this is enough of a start to approve the project in July.
-------------------------------------------------------
Meeting information
-------------------------------------------------------
Topic: MDC project discussion
Date: Thursday, May 31, 2012
Time: 4:00 pm, Central Daylight Time (Chicago, GMT-05:00)
Meeting Number: 828 394 185
Meeting Password: T10banded
-------------------------------------------------------
To start or join the online meeting
-------------------------------------------------------
Go to
https://seagate.webex.com/seagate/j.php?ED=167000587&UID=478887201&PW=NYWEwOD
Y5YjE4&RT=MiM3
-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
1. Please call one of the following numbers:
United States: 1-952-230-1270
US Toll-Free: 1-855-856-8765
2. Follow the instructions that you hear on the phone.
Your Cisco Unified MeetingPlace meeting ID: 828394185
-------------------------------------------------------
For general WebEx assistance
-------------------------------------------------------
1. Go to https://seagate.webex.com/seagate/mc
2. On the left navigation bar, click "Support".
To add this meeting to your calendar program (for example Microsoft
Outlook), click this link:
https://seagate.webex.com/seagate/j.php?ED=167000587&UID=478887201&ICS=MS&LD=
1&RD=2&ST=1&SHA2=6ga3TOOO-BXaiWW7b1ynH5LBoDgIseNkEbeetN3Leqg=
To check whether you have the appropriate players installed for UCF
(Universal Communications Format) rich media files, go to
https://seagate.webex.com/seagate/systemdiagnosis.php.


From curtis.stevens at wdc.com  Wed May 23 12:13:00 2012
From: curtis.stevens at wdc.com (Curtis Stevens)
Date: Wed, 23 May 2012 19:13:00 +0000
Subject: SOPQI WG Meeting
Message-ID: <mailman.145.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205231_f.htm">HTML-formatted message</a>
Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205231_nameless-2772-3.txt">nameless-2772-3.txt</a>

CURTIS STEVENS invites you to an online meeting using WebEx.
Meeting Number: 743 685 662
Meeting Password: This meeting does not require a password.
-------------------------------------------------------
To join this meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://premconf.webex.com/premconf/j.php?J=743685662
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: This meeting does
not require a password.
4. Click "Join".
5. Follow the instructions that appear on your screen.
-------------------------------------------------------
Teleconference information
-------------------------------------------------------
Call-in toll-free number (Premiere): 1-866-546-3377  (US)
Call-in number (Premiere): 1-719-234-7872  (US)
Attendee access code: 982 762 9443
http://www.webex.com
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and
any documents and other materials exchanged or viewed during the session to
be recorded. By joining this session, you automatically consent to such
recordings. If you do not consent to the recording, discuss your concerns
with the meeting host prior to the start of the recording or do not join the
session. Please note that any such recordings may be subject to discovery in
the event of litigation.


From alvin.cox at seagate.com  Wed May 23 12:47:37 2012
From: alvin.cox at seagate.com (Alvin Cox)
Date: Wed, 23 May 2012 14:47:37 -0500
Subject: Reminder: SAS PHY Teleconference Thursday, May 24, 2012 10:00am CDT
Message-ID: <mailman.146.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205232_f.htm">HTML-formatted message</a>

Next call: Thursday, May 24, 2012, 10:00 am CDT
Agenda:
Connector related
Call schedule
Electrical
12G Tx common mode
SAS-3 Receiver device compliance (12-244) [Gagnon]
SAS-3 TxRx connection compliance (12-243) [Gagnon]
SAS PHY: End-to-End Compliance Methodology and Specification (11-416)
[Gagnon]
New items
Toll Free Dial in Number: (877)810-9442
International Access/Caller Paid Dial In Number: (636)651-3190
PARTICIPANT CODE: 3243413
Webex information:
Topic: SAS-3
Date: Thursday, May 24, 2012
Time: 10:00 am, Central Daylight Time (Chicago, GMT-05:00)
Meeting Number: 827 988 093
Meeting Password: sas12gbps
-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&R
T=MiM3
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: sas12gbps
4. Click "Join".
To view in other time zones or languages, please click the link:
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&O
RT=MiM3
-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://seagate.webex.com/seagate/mc
2. On the left navigation bar, click "Support".
To update this meeting to your calendar program (for example Microsoft
Outlook), click this link:
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&ICS=MRS2&LD=1&RD=2
&ST=1&SHA2=pEI2tL0j5oE58s9ytOQWHuV98SACdVZgiFnrG-CNDds=&RT=MiM3
WebEx will automatically setup Meeting Manager for Windows the first time
you join a meeting. To save time, you can setup prior to the meeting by
clicking this link:
https://seagate.webex.com/seagate/meetingcenter/mcsetup.php
The playback of UCF (Universal Communications Format) rich media files
requires appropriate players. To view this type of rich media files in the
meeting, please check whether you have the players installed on your
computer by going to https://seagate.webex.com/seagate/systemdiagnosis.php.
-- 
Alvin Cox
Seagate Technology, LLC
Cell 405-206-4809
Office 405-392-3738
E-Mail	alvin.cox at seagate.com


From joe at lingua-data.com  Thu May 24 10:12:12 2012
From: joe at lingua-data.com (Joe Breher)
Date: Thu, 24 May 2012 11:12:12 -0600
Subject: SOP: use of 'assumed' - standardese?
Message-ID: <mailman.147.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* Joe Breher <joe at lingua-data.com>
*
I have run across some interesting language in SOP.
In the 6.4.x section of sop-r03 (SCSI transport protocol services), several
tables contain the note "Each Device Queuing Layer object is assumed to be
associated with one Host Queuing Layer object, and each SOP target port is
assumed to be associated with one SOP initiator port through that pair of
Queuing Layer objects".
What does 'assumed' mean in standardese? This term is not defined in the
document. Does this note need to be elevated to a normative 'shall' in some
other section of the document?
Joe Breher
President,
lingua data (a dba of q music inc)
(478) 2-Breher
(478) 227-3437
*
* 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 May 26 23:01:17 2012
From: lohmeyer at t10.org (T10 Document Administrator)
Date: Sun, 27 May 2012 00:01:17 -0600
Subject: Recent T10 documents uploaded since 2012/05/20
Message-ID: <mailman.148.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* T10 Document Administrator <lohmeyer at t10.org>
*
Proposals
---------
Multi-characteristic Device Commands for SCSI
(by: Gerald Houlder)
T10/12-034r2   Uploaded: 2012/05/25   349543 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-034r2.pdf
PQI Reset register
(by: Ie-Wei Njoo)
T10/12-088r7   Uploaded: 2012/05/25   320225 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-088r7.pdf
SOP Device server error handling
(by: Dan Colegrove)
T10/12-093r1   Uploaded: 2012/05/21   23813 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-093r1.pdf
SOP Device server error handling
(by: Dan Colegrove)
T10/12-093r2   Uploaded: 2012/05/21   40623 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-093r2.pdf
SAS-3 12 Gbps transmitter requirement updates
(by: Alvin Cox)
T10/12-226r1   Uploaded: 2012/05/24   332752 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-226r1.pdf
Minutes of SAT Working Group - May 7, 2012
(by: Weber & Lohmeyer)
T10/12-236r1   Uploaded: 2012/05/22   28929 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-236r1.htm
Minutes of SAT Working Group - May 7, 2012
(by: Weber & Lohmeyer)
T10/12-236r1   Uploaded: 2012/05/22   87772 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-236r1.pdf
Minutes of SAS Protocol Working Group - May 9, 2012
(by: Weber & Lohmeyer)
T10/12-238r1   Uploaded: 2012/05/21   35297 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-238r1.htm
Minutes of SAS Protocol Working Group - May 9, 2012
(by: Weber & Lohmeyer)
T10/12-238r1   Uploaded: 2012/05/21   99239 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-238r1.pdf
Minutes of SOP-PQI Working Group - 10-11 May 2012
(by: Rob Elliott)
T10/12-262r1   Uploaded: 2012/05/21   155729 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-262r1.pdf
Working Drafts
--------------
PCIe(r) architecture Queuing Interface (PQI)
(Editor: Ie-Wei Njoo)
 Rev: 05a      Uploaded: 2012/05/23   1608008 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=pqi-r05a.pdf
SCSI Block Commands - 3 (SBC-3)
(Editor: Mark Evans)
 Rev: 31       Uploaded: 2012/05/25   2313068 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=sbc3r31.pdf
(Report generated on 2012/05/27 at 00:01:17)
*
* 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 May 28 01:00:00 2012
From: lohmeyer at t10.org (T10 List Manager)
Date: Mon, 28 May 2012 02:00:00 -0600
Subject: T10 Reflector Monthly Reminder
Message-ID: <mailman.149.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* T10 List Manager <lohmeyer at t10.org>
*
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 alvin.cox at seagate.com  Tue May 29 09:52:33 2012
From: alvin.cox at seagate.com (Alvin Cox)
Date: Tue, 29 May 2012 11:52:33 -0500
Subject: Reminder: SAS PHY Teleconference Thursday, May 31, 2012 10:00am CDT
Message-ID: <mailman.150.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205290_f.htm">HTML-formatted message</a>

Next call: Thursday, May 31, 2012, 10:00 am CDT
Agenda:
Connector related
Electrical
12G Tx common mode discussion - frequency requirement changes?
SAS-3 Receiver device compliance (12-244) [Gagnon]
SAS-3 TxRx connection compliance (12-243) [Gagnon]
SAS PHY: End-to-End Compliance Methodology and Specification (11-416)
[Gagnon]
New items
Toll Free Dial in Number: (877)810-9442
International Access/Caller Paid Dial In Number: (636)651-3190
PARTICIPANT CODE: 3243413
Webex information:
Topic: SAS-3
Date: Thursday, May 31, 2012
Time: 10:00 am, Central Daylight Time (Chicago, GMT-05:00)
Meeting Number: 827 988 093
Meeting Password: sas12gbps
-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&R
T=MiM3
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: sas12gbps
4. Click "Join".
To view in other time zones or languages, please click the link:
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&O
RT=MiM3
-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://seagate.webex.com/seagate/mc
2. On the left navigation bar, click "Support".
To update this meeting to your calendar program (for example Microsoft
Outlook), click this link:
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&ICS=MRS2&LD=1&RD=2
&ST=1&SHA2=pEI2tL0j5oE58s9ytOQWHuV98SACdVZgiFnrG-CNDds=&RT=MiM3
WebEx will automatically setup Meeting Manager for Windows the first time
you join a meeting. To save time, you can setup prior to the meeting by
clicking this link:
https://seagate.webex.com/seagate/meetingcenter/mcsetup.php
The playback of UCF (Universal Communications Format) rich media files
requires appropriate players. To view this type of rich media files in the
meeting, please check whether you have the players installed on your
computer by going to https://seagate.webex.com/seagate/systemdiagnosis.php.
-- 
Alvin Cox
Seagate Technology, LLC
Cell 405-206-4809
Office 405-392-3738
E-Mail	alvin.cox at seagate.com


From gerry.houlder at seagate.com  Wed May 30 11:14:38 2012
From: gerry.houlder at seagate.com (Gerry Houlder)
Date: Wed, 30 May 2012 13:14:38 -0500
Subject: Reminder: Multi-characteristic Device Commands telecon - Thursday May
 31 2:00 pm PDT
Message-ID: <mailman.151.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205300_f.htm">HTML-formatted message</a>

Agenda:
Discuss 12-034r2 updates since last telecon
Decide if this is enough of a start to approve the project in July.
-------------------------------------------------------
Meeting information
-------------------------------------------------------
Topic: MDC project discussion
Date: Thursday, May 31, 2012
Time: 4:00 pm, Central Daylight Time (Chicago, GMT-05:00)
Meeting Number: 828 394 185
Meeting Password: T10banded
-------------------------------------------------------
To start or join the online meeting
-------------------------------------------------------
Go
tohttps://seagate.webex.com/seagate/j.php?ED=167000587&UID=478887201&PW=NYWEw
OD
Y5YjE4&RT=MiM3
-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
1. Please call one of the following numbers:
United States: 1-952-230-1270
US Toll-Free: 1-855-856-8765
2. Follow the instructions that you hear on the phone.
Your Cisco Unified MeetingPlace meeting ID: 828394185
-------------------------------------------------------
For general WebEx assistance
-------------------------------------------------------
1. Go to https://seagate.webex.com/seagate/mc
2. On the left navigation bar, click "Support".
To add this meeting to your calendar program (for example Microsoft
Outlook), click this
link:https://seagate.webex.com/seagate/j.php?ED=167000587&UID=478887201&ICS=M
S&LD=
1&RD=2&ST=1&SHA2=6ga3TOOO-BXaiWW7b1ynH5LBoDgIseNkEbeetN3Leqg=
To check whether you have the appropriate players installed for UCF
(Universal Communications Format) rich media files, go
tohttps://seagate.webex.com/seagate/systemdiagnosis.php.


From lohmeyer at t10.org  Thu May 31 09:22:33 2012
From: lohmeyer at t10.org (John Lohmeyer)
Date: Thu, 31 May 2012 10:22:33 -0600
Subject: Two weeks until July T10 hotel cutoff date
Message-ID: <mailman.152.1441607378.22528.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* John Lohmeyer <lohmeyer at t10.org>
*
Procrastinators:
It is time to make your July T10 reservations. The cutoff date is June 14th,
just two weeks away.
You can find the meeting announcement at: 
  http://www.t10.org/ftp/t10/announce/ann-m110.pdf
It includes the Hilton web reservations link at:
http://www.hilton.com/en/hi/groups/personalized/C/COSCSHF-LSI712-20120714/ind
ex.jhtml?WT.mc_id=POG
Please remember that if your spouse is sharing your room, say you have only
one person to receive the correct room rate. The double occupancy rate is
only intended for cases where two meeting attendees are sharing a room --
pretty rare.
Also, please join us at the LSI reception on Tuesday evening, which is again
being held at the Phantom Canyon Brewing Co. across the street from the
Antler's Hotel. You can bring your spouse and/or adult children, but they
must be over 21 years of age.
If you have any trouble making your room reservations, please let me know
ASAP. I can help you get into the T10 room block.
See you in July!
John
--
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 mickey.felton at emc.com  Thu May 31 10:26:39 2012
From: mickey.felton at emc.com (mickey.felton at emc.com)
Date: Thu, 31 May 2012 13:26:39 -0400
Subject: Reminder: SAS PHY Teleconference Thursday, June 7, 2012 10:00am
 CDT
Message-ID: <mailman.153.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205311_f.htm">HTML-formatted message</a>

Next call: Thursday, June 7, 2012, 10:00 am CDT
Agenda:
Connector related
Electrical
12G Tx common mode discussion - frequency requirement changes?
SAS PHY: End-to-End Compliance Methodology and Specification (11-416)
[Gagnon]
SAS-3 Transmitter device compliance (12-242) [Gagnon]
New items
Toll Free Dial in Number: (877)810-9442
International Access/Caller Paid Dial In Number: (636)651-3190
PARTICIPANT CODE: 3243413
Webex information:
Topic: SAS-3
Date: Thursday, June 7, 2012
Time: 10:00 am, Central Daylight Time (Chicago, GMT-05:00)
Meeting Number: 827 988 093
Meeting Password: sas12gbps
-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&R
T=MiM3
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: sas12gbps
4. Click "Join".
To view in other time zones or languages, please click the link:
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&O
RT=MiM3
-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://seagate.webex.com/seagate/mc
2. On the left navigation bar, click "Support".
To update this meeting to your calendar program (for example Microsoft
Outlook), click this link:
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&ICS=MRS2&LD=1&RD=2
&ST=1&SHA2=pEI2tL0j5oE58s9ytOQWHuV98SACdVZgiFnrG-CNDds=&RT=MiM3
WebEx will automatically setup Meeting Manager for Windows the first time you
join a meeting. To save time, you can setup prior to the meeting by clicking
this link:
https://seagate.webex.com/seagate/meetingcenter/mcsetup.php
The playback of UCF (Universal Communications Format) rich media files
requires appropriate players. To view this type of rich media files in the
meeting, please check whether you have the players installed on your computer
by going to https://seagate.webex.com/seagate/systemdiagnosis.php.
--
Alvin Cox
Seagate Technology, LLC
Cell 405-206-4809
Office 405-392-3738
E-Mail	alvin.cox at seagate.com


From mickey.felton at emc.com  Thu May 31 10:59:13 2012
From: mickey.felton at emc.com (mickey.felton at emc.com)
Date: Thu, 31 May 2012 13:59:13 -0400
Subject: Amended: Reminder: SAS PHY Teleconference Thursday, June 7, 2012
 10:00am CDT
Message-ID: <mailman.154.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205312_f.htm">HTML-formatted message</a>

Sorry everyone for the repeat, I didn't realize the WEB EX info changes week
to week, below is the new information:
Agenda:
Connector related
Electrical
12G Tx common mode discussion - frequency requirement changes?
SAS PHY: End-to-End Compliance Methodology and Specification (11-416)
[Gagnon]
SAS-3 Transmitter device compliance (12-242) [Gagnon]
New items
Toll Free Dial in Number: (877)810-9442
International Access/Caller Paid Dial In Number: (636)651-3190
PARTICIPANT CODE: 3243413
Webex information:
Topic: SAS-3
Date: Thursday, June 7, 2012
Time: 10:00 am, Central Daylight Time (Chicago, GMT-05:00)
Meeting Number: 827 988 093
Meeting Password: sas12gbps
-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&R
T=MiM3
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: sas12gbps
4. Click "Join".
To view in other time zones or languages, please click the link:
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&O
RT=MiM3
-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://seagate.webex.com/seagate/mc
2. On the left navigation bar, click "Support".
To update this meeting to your calendar program (for example Microsoft
Outlook), click this link:
https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&ICS=MRS2&LD=1&RD=2
&ST=1&SHA2=pEI2tL0j5oE58s9ytOQWHuV98SACdVZgiFnrG-CNDds=&RT=MiM3
WebEx will automatically setup Meeting Manager for Windows the first time you
join a meeting. To save time, you can setup prior to the meeting by clicking
this link:
https://seagate.webex.com/seagate/meetingcenter/mcsetup.php
The playback of UCF (Universal Communications Format) rich media files
requires appropriate players. To view this type of rich media files in the
meeting, please check whether you have the players installed on your computer
by going to https://seagate.webex.com/seagate/systemdiagnosis.php.


From Elliott at hp.com  Thu May 31 12:02:50 2012
From: Elliott at hp.com (Elliott, Robert (Server Storage))
Date: Thu, 31 May 2012 19:02:50 +0000
Subject: Seeking clarification on Threshold Out/In diagnostic pages
Message-ID: <mailman.155.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205313_f.htm">HTML-formatted message</a>

The Threshold Out/In diagnostic pages are old, and just report 4 bytes per
element type plus 4 bytes per individual element; the Additional Element
Status diagnostic page is relatively new and is designed to return a lot more
data per element (but not all elements need to report extra data).  So, don't
be surprised by differences.
These are all the same size:
- control descriptor list (Enclosure Control diagnostic page)
- status descriptor list (Enclosure Status diagnostic page)
- threshold control descriptor list (Threshold Out diagnostic page)
- threshold status descriptor list (Threshold In diagnostic page)
In ses3r04a, table 65 and table 66 (PDF page 85-86) define the generic
formats for the threshold elements.  I agree there should be a statement
somewhere that:
a) all the fields in the threshold control elements are ignored; and
b) all the fields in the threshold status elements are reserved,
for the elements listed in table 60 (PDF page 82) as having a threshold of
"none".
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Raj Divecha
Sent: Friday, 04 May, 2012 3:37 PM
To: Matthew_Jacobs at Dell.com
Cc: t10 at t10.org
Subject: RE: Seeking clarification on Threshold Out/In diagnostic pages
Matt,
Yeah that's a strong indicator indeed, I too acknowledge that in my email.
However, those placeholder/reserved threshold elements are a huge wastage and
amounts to unnecessary data being transferred. Thus I believe that the
authors of the SES spec wouldn't have intended the same and is a thing that
does not clearly come out of the spec.
Consider the below given configuration of an imaginary enclosure. In this we
are talking about sending/receiving 352 bytes of useless data, that is
approximately 80% wastage. The number of useless bytes would almost multiply
as you add subenclosures.
24
Array Device Slot elements
2
Power Supply elements
6
Cooling elements
4
Temperature Sensor elements
1
Door Lock element
1
Audible Alarm element
2
Enclosure Services Controller Electronics elements
1
Invalid Operation Reason element
1
UPS element
1
Display element
1
Enclosure element
6
Voltage Sensor elements
4
Current Sensor elements
2
SAS Expander elements
30
SAS Connector elements
2
VS element 1
4
VS element 2
As the authors limited the number of element types appearing in the
Additional Element Status diagnostic page, it is probable that they intended
the same for the Threshold Out/In diagnostic page but unfortunately it didn't
came out that way in the spec.
Raj
From: Matthew_Jacobs at Dell.com<mailto:Matthew_Jacobs at Dell.com>
[mailto:Matthew_Jacobs at Dell.com]<mailto:[mailto:Matthew_Jacobs at Dell.com]>
Sent: Friday, May 04, 2012 1:42 PM
To: Raj Divecha; t10 at t10.org<mailto:t10 at t10.org>
Subject: RE: Seeking clarification on Threshold Out/In diagnostic pages
Raj,
The descriptions of the threshold control descriptor list and the threshold
status descriptor list in sections 6.1.8 and 6.1.9 state that the list
contains a control/status "descriptor for each type descriptor header in the
Configuration diagnostic page".  From that, I believe all individual elements
defined in the Configuration diagnostic page have a threshold element in the
Threshold in/Out diagnostic page even if it is just a placeholder/reserved
threshold element.
Matt
From: owner-t10 at t10.org<mailto:owner-t10 at t10.org>
[mailto:owner-t10 at t10.org]<mailto:[mailto:owner-t10 at t10.org]> On Behalf Of
Raj Divecha
Sent: Friday, May 04, 2012 12:29 PM
To: t10 at t10.org<mailto:t10 at t10.org>
Subject: SES: Seeking clarification on Threshold Out/In diagnostic pages
Hi,
I searched the T10 emails for this but didn't found anything.
The SES spec is a bit ambiguous regarding which element types should be
included in the Threshold Out/In diagnostic page. A clarification would be
helpful.
The following are the excerpts from the 2r20 spec. Below each excerpt is my
comment. The questions are at the end of the email.
6.1.8 Threshold Out diagnostic page
The Threshold Out diagnostic page is transmitted to the enclosure services
process to establish threshold values for those elements that have limited
sensing capability (e.g., temperature sensors, uninterruptible power
supplies, voltage sensors, and current sensors).
My comment: this statement "possibly" suggests that this page includes only
those element types that support threshold.
The threshold control descriptor list contains a threshold control descriptor
for each type descriptor header in the Configuration diagnostic page (see
6.1.2).
My comment: this statement "strongly" suggests that this page includes all
element types, whether or not they support thresholds.
7.1 Element definitions overview, Table 60
My comment: shows which element type support thresholds and which not.
7.2.4 Threshold control element format
All fields in the threshold control element are advisory. The enclosure
services process shall ignore the contents of the threshold control element
for those elements that have no value to be compared with a threshold and for
those elements that do not implement the threshold function.
My comment: this statement suggests that threshold descriptors for even those
element types, that do not support threshold, are included in the Threshold
Out/In diagnostic page, however, the application client and the enclosure
services process (ESP) are supposed to ignore them.
7.3 Field definitions for all element types
My comments: this section does not describe the threshold descriptors for
element types that do not support threshold. Not even a generic descriptor
with 4 reserved bytes is defined.
If the readers are to assume that the threshold descriptors for even those
element types that do not support threshold are to be included in the
Threshold Out/In diagnostic pages, then they are also supposed to assume a
generic 4-byte threshold descriptors with all bytes as reserved as they are
supposed to be ignored by both the application client and the ESP.
If the readers are to assume that the Threshold Out/In pages should include
only those element types that support threshold then there is no question of
assuming a generic 4-bytes reserved descriptor and no question of ignoring
them.
Based on the above there are many "strong" points that indicate that the
Threshold Out/In pages include even those element types that do not support
thresholds and there are some "weak" points that indicate that they don't
include those element types.
Did the spec authors intended to include additional descriptors in the page
that will never be used?
Or were the Threshold Out/In diagnostic pages meant to be similar to the
Additional Element Status diagnostic page where in only a selected subset of
element types appear in these pages?
In my opinion the spec authors did not intend to include additional
descriptors in the page that will never be used and thus the Threshold Out/In
diagnostic page is similar to the Additional Element Status diagnostic page
where only a limited subset of element types appear in these pages. However,
I could be wrong, thus please clarify.
Thanks,
Raj


From gerry.houlder at seagate.com  Thu May 31 15:43:19 2012
From: gerry.houlder at seagate.com (Gerry Houlder)
Date: Thu, 31 May 2012 17:43:19 -0500
Subject: Minutes of MDC Telecon on May 31, 2012
Message-ID: <mailman.156.1441607378.22528.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1205314_f.htm">HTML-formatted message</a>

The MDC Telecon was held at 4:00pm CDT on May 31, 2012. The agenda was to
discuss progress on
the 12-034 rev 2 - Multi-characteristic Device Commands proposal.
Attendees:
Jack Harwood (EMC)
Dan Colgrove (HGST)
Chris Williams (HP)
Curtis Ballard (HP)
John Lohmeyer (LSI)
Gerry Houlder (Seagate)
Joel Schipper (Seagate)
Jim Hatfield (Seagate)
Mike Fitzpatrick (Toshiba)
Paul Suler (Quantum)
Rev. 2 of 12-034 was discussed, there weren't any significant changes
requested.
Study group goal is to define a document that is firm enough so that host
end and target end implementations are possible. This means getting a
Peripheral Device Qualifier (in standard INQUIRY) assignment, four command
opcode/ service action assignments, and a VPD page assignment in addition
to the detail in 12-034r2. John Lohmeyer suggested that this should be done
within the context of an approved project, not just a study group proposal.
The group suggested the need for more justification for the project, with
explanation of areal density improvement that might be possible and other
justifications. This information should be made available for The CAP
meeting in July, under the agenda item for 12-010 (the project proposal for
MDC).
The telecon ended at 5:20 pm.