<font size=2 face="sans-serif">Thanks Michael.</font><br><br><br><br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Michael Xing <xiaoxing@microsoft.com></font><br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Amir Dagan1/Israel/IBM@IBMIL,
Curtis Stevens <curtis.stevens@wdc.com></font><br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"T10, Reflector"
<T10@t10.org></font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">2016-04-15 19:29</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">RE: [T10] Determining
an SED Drive</font><br><hr noshade><br><br><br><font size=2 face="Calibri">Hi Amir,</font><br><font size=2 face="Calibri"> </font><br><font size=2 face="Calibri">You can report one of 1667 versions: 0xFFC0,
0xFFC1 or 0xFFC2 in “Version Descriptor” field of INQUIRY DATA.</font><br><font size=2 face="Calibri"> </font><br><font size=2 face="Calibri">Thanks,</font><br><font size=2 face="Calibri">Michael</font><br><font size=2 face="Calibri"> </font><br><font size=2 face="Calibri"><b>From:</b> t10-bounces@t10.org [</font><a href="mailto:t10-bounces@t10.org"><font size=2 face="Calibri">mailto:t10-bounces@t10.org</font></a><font size=2 face="Calibri">]
<b>On Behalf Of </b>Amir Dagan1<b><br>Sent:</b> Sunday, April 10, 2016 1:49 AM<b><br>To:</b> Curtis Stevens <curtis.stevens@wdc.com><b><br>Cc:</b> T10, Reflector <T10@t10.org><b><br>Subject:</b> Re: [T10] Determining an SED Drive</font><br><font size=3 face="Times New Roman"> </font><br><font size=2 face="Arial">Thanks - where do think that would be in
the extended INQUIRY (which field)? I'd like to relay on a generic structure
of INQUIRY - not necessarily vendor-specific. </font><font size=3 face="Times New Roman"><br><br><br></font><font size=1 color=#5f5f5f face="Arial"><br>From: </font><font size=1 face="Arial">Curtis
Stevens <</font><a href=mailto:curtis.stevens@wdc.com><font size=1 color=blue face="Arial"><u>curtis.stevens@wdc.com</u></font></a><font size=1 face="Arial">></font><font size=1 color=#5f5f5f face="Arial"><br>To: </font><font size=1 face="Arial">"John
Geldman (jgeldman)" <</font><a href=mailto:jgeldman@micron.com><font size=1 color=blue face="Arial"><u>jgeldman@micron.com</u></font></a><font size=1 face="Arial">>,
Amir Dagan1/Israel/IBM@IBMIL</font><font size=1 color=#5f5f5f face="Arial"><br>Cc: </font><font size=1 face="Arial">"T10,
Reflector" <</font><a href=mailto:T10@t10.org><font size=1 color=blue face="Arial"><u>T10@t10.org</u></font></a><font size=1 face="Arial">></font><font size=1 color=#5f5f5f face="Arial"><br>Date: </font><font size=1 face="Arial">2016-04-08
01:51</font><font size=1 color=#5f5f5f face="Arial"><br>Subject: </font><font size=1 face="Arial">RE:
[T10] Determining an SED Drive</font><div align=center><hr noshade></div><br><font size=3 face="Times New Roman"><br><br></font><font size=2 color=#004080 face="Calibri"><br>Agreed! Go 1667 </font><font size=2 color=#004080 face="Wingdings">J</font><font size=2 color=#004080 face="Calibri"><br> <br> </font><font size=2 color=#3f621f face="Arial"><br> <br> <br>-------------------------------------------------<br>Curtis E. Stevens<br>Director, Standards & Features Technology<br>3355 Michelson Dr. #100<br>Office: 1-1041<br>Irvine, Ca. 92612<br> <br>Phone: 949-672-7933<br>Cell: 949-307-5050<br>E-Mail: </font><a href=mailto:Curtis.Stevens@WDC.com><font size=2 color=#3f621f face="Arial"><u>Curtis.Stevens@WDC.com</u></font></a><font size=2 color=#3f621f face="Arial"><br> <br>Remember, you may only be blamed for something if you are actually doing
something.</font><font size=2 color=#004080 face="Calibri"><br> </font><font size=2 face="Calibri"><b><br>From:</b> John Geldman (jgeldman) [</font><a href=mailto:jgeldman@micron.com><font size=2 color=blue face="Calibri"><u>mailto:jgeldman@micron.com</u></font></a><font size=2 face="Calibri">]
<b><br>Sent:</b> Thursday, April 7, 2016 3:11 PM<b><br>To:</b> Amir Dagan1 <</font><a href=mailto:AMIRDA@il.ibm.com><font size=2 color=blue face="Calibri"><u>AMIRDA@il.ibm.com</u></font></a><font size=2 face="Calibri">>;
Curtis Stevens <</font><a href=mailto:curtis.stevens@wdc.com><font size=2 color=blue face="Calibri"><u>curtis.stevens@wdc.com</u></font></a><font size=2 face="Calibri">><b><br>Cc:</b> T10, Reflector <</font><a href=mailto:T10@t10.org><font size=2 color=blue face="Calibri"><u>T10@t10.org</u></font></a><font size=2 face="Calibri">><b><br>Subject:</b> RE: [T10] Determining an SED Drive</font><font size=3 face="Times New Roman"><br> </font><font size=2 color=#004080 face="Calibri"><br>One more bit of complexity. If you are working with a SED that was designed
to support Microsoft’s BitLocker, it would support IEEE 1667 to communicate
with the TCG functionality. <br> <br>IEEE 1667 support/version information and/or TCG support/version may show
up in extended INQUIRY responses. <br> <br>John<br> </font><font size=2 face="Calibri"><b><br>From:</b> </font><a href="mailto:t10-bounces@t10.org"><font size=2 color=blue face="Calibri"><u>t10-bounces@t10.org</u></font></a><font size=2 face="Calibri">[</font><a href="mailto:t10-bounces@t10.org"><font size=2 color=blue face="Calibri"><u>mailto:t10-bounces@t10.org</u></font></a><font size=2 face="Calibri">]
<b>On Behalf Of </b>Amir Dagan1<b><br>Sent:</b> Thursday, April 07, 2016 2:19 PM<b><br>To:</b> Curtis Stevens<b><br>Cc:</b> T10, Reflector<b><br>Subject:</b> Re: [T10] Determining an SED Drive</font><font size=3 face="Times New Roman"><br> </font><font size=2 face="Courier New"><br>(Adding John's final note to keep it single-threaded)<br><br>Thank you John, Curtis and Gerry for your useful notes.<br><br>I was looking after a method which will be as generic as possible - for
a "HW-agnostic" environment - where the type of drive and FW
is not known in advance (some enterprise drive spec do have a SED bit -
but I cannot trust that).<br><br>Combining all the comments I realise now that if the system SW is designed
to do TCG SED, then the right way would be to send a level 0 discovery
to all the devices and rule out those who do not allow to proceed with
the process.<br><br>I tend to agree with Curtis' bottom line...<br><br>Many thanks,<br>Amir<br><br>--</font><font size=2 color=#004080 face="Calibri"><br><br>Amir, <br><br>While there has been a fair amount of advice for you, I’m not sure it
is on target. <br>What did you mean by a SED device? Did you have a specific type in mind
(e.g., TCG implementations)? <br><br>Thank you,<br>John Geldman<br></font><font size=3 color=blue face="Times New Roman"><u><br><br></u></font><a href="https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.micron.com%2f&data=01%7c01%7cxiaoxing%40microsoft.com%7c8abfd7594ee34de358d708d3611dc6f7%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=gEhJwJN4sAc2kC0RAhMe7JBAuaA8dFBWTduriGqNEPA%3d"><img src=cid:_4_0DD585380DD7D48400290B51C2257F98 alt=cid:image001.png@01D123AF.225CEFA0 style="border:0px solid;"></a><font size=1 color=#808080 face="Segoe UI"><b><br>John Geldman</b><br>Director, Industry Standards, <br><br>Micron Technology, Inc.<b><br>Office</b> +1 (408) 822-0348 <b>Mobile</b> +1 (510) 449-3597</font><font size=3 color=blue face="Times New Roman"><u><br><br></u></font><a href=mailto:jgeldman@micron.com><font size=1 color=#808080 face="Segoe UI"><u>jgeldman@micron.com</u></font></a><font size=3 face="Times New Roman"><br><br></font><font size=1 color=#5f5f5f face="Arial"><br><br>From: </font><font size=1 face="Arial">Curtis
Stevens <</font><a href=mailto:curtis.stevens@wdc.com><font size=1 color=blue face="Arial"><u>curtis.stevens@wdc.com</u></font></a><font size=1 face="Arial">></font><font size=1 color=#5f5f5f face="Arial"><br>To: </font><font size=1 face="Arial">Gerry Houlder
<</font><a href=mailto:gerry.houlder@seagate.com><font size=1 color=blue face="Arial"><u>gerry.houlder@seagate.com</u></font></a><font size=1 face="Arial">>,
"Otte, Olga" <</font><a href=mailto:olga.otte@hpe.com><font size=1 color=blue face="Arial"><u>olga.otte@hpe.com</u></font></a><font size=1 face="Arial">></font><font size=1 color=#5f5f5f face="Arial"><br>Cc: </font><font size=1 face="Arial">"T10,
Reflector" <</font><a href=mailto:T10@t10.org><font size=1 color=blue face="Arial"><u>T10@t10.org</u></font></a><font size=1 face="Arial">></font><font size=1 color=#5f5f5f face="Arial"><br>Date: </font><font size=1 face="Arial">2016-04-07
20:31</font><font size=1 color=#5f5f5f face="Arial"><br>Subject: </font><font size=1 face="Arial">Re:
[T10] Determining an SED Drive</font><font size=1 color=#5f5f5f face="Arial"><br>Sent by: </font><a href="mailto:t10-bounces@t10.org"><font size=1 color=blue face="Arial"><u>t10-bounces@t10.org</u></font></a><div align=center><hr noshade></div><br><font size=3 face="Times New Roman"><br><br></font><font size=2 color=#004080 face="Calibri"><br><br>Actually, TCG is one way to do SED, there are others that do not use TCG.
Depending on a command to fail is really not a reliable we to determine
that some underlying functionality is available.<br><br>This was handled on the T13 side by adding a SED bit. The only use
case is for customers that get custom configurations and know what they
are getting in advance. Due to the nature of the problem, there is
no reliable/universal detection method. Whatever you define can be
spoofed. Including Model # and Manufacturer.</font><font size=2 color=#3f621f face="Arial"><br><br><br><br>-------------------------------------------------<br>Curtis E. Stevens<br>Director, Standards & Features Technology<br>3355 Michelson Dr. #100<br>Office: 1-1041<br>Irvine, Ca. 92612<br><br>Phone: 949-672-7933<br>Cell: 949-307-5050<br>E-Mail: </font><a href=mailto:Curtis.Stevens@WDC.com><font size=2 color=#3f621f face="Arial"><u>Curtis.Stevens@WDC.com</u></font></a><font size=2 color=#3f621f face="Arial"><br><br>Remember, you may only be blamed for something if you are actually doing
something.</font><font size=2 face="Calibri"><b><br><br>From:</b> </font><a href="mailto:t10-bounces@t10.org"><font size=2 color=blue face="Calibri"><u>t10-bounces@t10.org</u></font></a><font size=2 face="Calibri">[</font><a href="mailto:t10-bounces@t10.org"><font size=2 color=blue face="Calibri"><u>mailto:t10-bounces@t10.org</u></font></a><font size=2 face="Calibri">]
<b>On Behalf Of </b>Gerry Houlder<b><br>Sent:</b> Thursday, April 7, 2016 9:17 AM<b><br>To:</b> Otte, Olga <</font><a href=mailto:olga.otte@hpe.com><font size=2 color=blue face="Calibri"><u>olga.otte@hpe.com</u></font></a><font size=2 face="Calibri">><b><br>Cc:</b> T10, Reflector <</font><a href=mailto:T10@t10.org><font size=2 color=blue face="Calibri"><u>T10@t10.org</u></font></a><font size=2 face="Calibri">><b><br>Subject:</b> Re: [T10] Determining an SED Drive</font><font size=3 face="Times New Roman"><br><br>If you get drive not ready, then the drive is not spun up yet.<br>If you get invalid command, then the drive is not SED.<br>There may be exceptions where an SED uses vendor specific protocols (not
SECURITY PROTOCOL IN and SECURITY PROTOCOL OUT commands) that you can't
determine from this method.<br><br>On Thu, Apr 7, 2016 at 10:31 AM, Otte, Olga <</font><a href=mailto:olga.otte@hpe.com target=_blank><font size=3 color=blue face="Times New Roman"><u>olga.otte@hpe.com</u></font></a><font size=3 face="Times New Roman">>
wrote:</font><font size=2 color=#004080 face="Times New Roman"><br>Do we expect “drive not ready” or “Invalid command” check condition
if drive is not spin up yet? I think I am getting timing issue and not
sure what is expected behavior.<br><br>Olga Otte HPE</font><font size=2 face="Tahoma"><b><br><br>From:</b> </font><a href="mailto:t10-bounces@t10.org" target=_blank><font size=2 color=blue face="Tahoma"><u>t10-bounces@t10.org</u></font></a><font size=2 face="Tahoma">[mailto:</font><a href="mailto:t10-bounces@t10.org" target=_blank><font size=2 color=blue face="Tahoma"><u>t10-bounces@t10.org</u></font></a><font size=2 face="Tahoma">]
<b>On Behalf Of </b>Saha, Soumit<b><br>Sent:</b> Thursday, April 07, 2016 7:35 AM<b><br>To:</b> Amir Dagan1<b><br>Cc:</b> T10, Reflector<b><br>Subject:</b> Re: [T10] Determining an SED Drive</font><p><font size=3 face="Times New Roman">You have to send SPC trusted receive
(IF-RECV) SCSI primary command with discovery payload and handle illegal
requests if the drive is not an SED.</font><p><font size=3 face="Times New Roman">There are no vital data pages for
SED specific attributes.<br>On 7 Apr 2016 12:39, Amir Dagan1 <</font><a href=mailto:AMIRDA@il.ibm.com target=_blank><font size=3 color=blue face="Times New Roman"><u>AMIRDA@il.ibm.com</u></font></a><font size=3 face="Times New Roman">>
wrote:</font><font size=2 face="Arial"><br>Hello,<br><br>Is there a "SCSI" way (non vendor specific) to tell whether a
device is an SED one (Self Encrypting Drive)?<br>I do not mean by P/N etc., but a designated field in a logpage, inquiry,
etc.<br><br>Thanks,<br>Amir Dagan<br>IBM</font><font size=3 face="Times New Roman"><br><br>_______________________________________________<br>T10 mailing list</font><font size=3 color=blue face="Times New Roman"><u><br></u></font><a href=mailto:T10@t10.org><font size=3 color=blue face="Times New Roman"><u>T10@t10.org</u></font></a><font size=3 color=blue face="Times New Roman"><u><br></u></font><a href="https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.t10.org%2fmailman%2flistinfo%2ft10&data=01%7c01%7cxiaoxing%40microsoft.com%7c8abfd7594ee34de358d708d3611dc6f7%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=dS2o71nBt8NQhqDRqQTMmjAA76Z9zO0pBxzEMtkcG%2f8%3d" target=_blank><font size=3 color=blue face="Times New Roman"><u>http://www.t10.org/mailman/listinfo/t10</u></font></a><font size=2 face="Courier New"><br>_______________________________________________<br>T10 mailing list</font><font size=3 color=blue face="Times New Roman"><u><br></u></font><a href=mailto:T10@t10.org><font size=2 color=blue face="Courier New"><u>T10@t10.org</u></font></a><font size=3 color=blue face="Times New Roman"><u><br></u></font><a href="https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.t10.org%2fmailman%2flistinfo%2ft10&data=01%7c01%7cxiaoxing%40microsoft.com%7c8abfd7594ee34de358d708d3611dc6f7%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=dS2o71nBt8NQhqDRqQTMmjAA76Z9zO0pBxzEMtkcG%2f8%3d"><font size=2 color=blue face="Courier New"><u>http://www.t10.org/mailman/listinfo/t10</u></font></a><p><font size=3 face="Times New Roman"> </font><p><BR>