<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:"Segoe UI";
        panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
span.EmailStyle19
        {mso-style-type:personal-compose;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri",sans-serif;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">Amir,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">It will be in the extended INQUIRY version descriptors.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">IEEE 1667-2015 recommends using a version descriptor of FFC0h (IEEE 1667, no version reported):<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Check standard INQUIRY command data bytes 58..73 for the IEEE 1667 (version not reported) version descriptor. If the IEEE 1667 version descriptor is present, then IEEE 1667 is supported, proceed to step 4).</span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">John Geldman<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"> Amir Dagan1 [mailto:AMIRDA@il.ibm.com]
<br>
<b>Sent:</b> Sunday, April 10, 2016 1:49 AM<br>
<b>To:</b> Curtis Stevens<br>
<b>Cc:</b> John Geldman (jgeldman); T10, Reflector<br>
<b>Subject:</b> RE: [T10] Determining an SED Drive<o:p></o:p></span></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">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.
</span><br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:#5F5F5F">From: &nbsp; &nbsp; &nbsp; &nbsp;</span><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">Curtis Stevens &lt;<a href="mailto:curtis.stevens@wdc.com">curtis.stevens@wdc.com</a>&gt;</span><br>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:#5F5F5F">To: &nbsp; &nbsp; &nbsp; &nbsp;</span><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">&quot;John Geldman (jgeldman)&quot; &lt;<a href="mailto:jgeldman@micron.com">jgeldman@micron.com</a>&gt;, Amir Dagan1/Israel/IBM@IBMIL</span><br>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:#5F5F5F">Cc: &nbsp; &nbsp; &nbsp; &nbsp;</span><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">&quot;T10, Reflector&quot; &lt;<a href="mailto:T10@t10.org">T10@t10.org</a>&gt;</span><br>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:#5F5F5F">Date: &nbsp; &nbsp; &nbsp; &nbsp;</span><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">2016-04-08 01:51</span><br>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:#5F5F5F">Subject: &nbsp; &nbsp; &nbsp; &nbsp;</span><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">RE: [T10] Determining an SED Drive</span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#004080">Agreed! Go 1667
</span><span style="font-size:10.0pt;font-family:Wingdings;color:#004080">J</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#004080">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#004080">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">-------------------------------------------------</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">Curtis E. Stevens</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">Director, Standards &amp; Features Technology</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">3355 Michelson Dr. #100</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">Office: 1-1041</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">Irvine, Ca. 92612</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">Phone: 949-672-7933</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">Cell: 949-307-5050</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">E-Mail:
</span><a href="mailto:Curtis.Stevens@WDC.com"><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">Curtis.Stevens@WDC.com</span></a><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">Remember, you may only be blamed for something if you are actually doing something.</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#004080">&nbsp;</span><br>
<b><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif"> John Geldman (jgeldman) [</span><a href="mailto:jgeldman@micron.com"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">mailto:jgeldman@micron.com</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">]
<b><br>
Sent:</b> Thursday, April 7, 2016 3:11 PM<b><br>
To:</b> Amir Dagan1 &lt;<a href="mailto:AMIRDA@il.ibm.com">AMIRDA@il.ibm.com</a>&gt;; Curtis Stevens &lt;<a href="mailto:curtis.stevens@wdc.com">curtis.stevens@wdc.com</a>&gt;<b><br>
Cc:</b> T10, Reflector &lt;<a href="mailto:T10@t10.org">T10@t10.org</a>&gt;<b><br>
Subject:</b> RE: [T10] Determining an SED Drive</span><br>
&nbsp;<br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#004080">One more bit of complexity. If you are working with a SED that was designed to support Microsoft&#8217;s BitLocker, it would support IEEE 1667 to communicate with the TCG functionality.
</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#004080">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#004080">IEEE 1667 support/version information and/or TCG support/version may show up in extended INQUIRY responses.
</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#004080">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#004080">John</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#004080">&nbsp;</span><br>
<b><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">
</span><a href="mailto:t10-bounces@t10.org"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">t10-bounces@t10.org</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">[</span><a href="mailto:t10-bounces@t10.org"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">mailto:t10-bounces@t10.org</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">]
<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</span><br>
&nbsp;<br>
<span style="font-size:10.0pt;font-family:&quot;Courier New&quot;">(Adding John's final note to keep it single-threaded)</span><br>
<span style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
Thank you John, Curtis and Gerry for your useful notes.</span><br>
<span style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
I was looking after a method which will be as generic as possible - for a &quot;HW-agnostic&quot; 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).</span><br>
<span style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><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.</span><br>
<span style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
I tend to agree with Curtis' bottom line...</span><br>
<span style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
Many thanks,<br>
Amir</span><br>
<span style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
--</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#004080"><br>
Amir, <br>
<br>
While there has been a fair amount of advice for you, I&#8217;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>
<br>
</span><u><span style="color:blue"><br>
</span></u><a href="http://www.micron.com/"><span style="text-decoration:none"><img border="0" width="168" height="45" id="_x0000_i1026" src="cid:image001.png@01D193CE.83143260" alt="cid:image001.png@01D123AF.225CEFA0"></span></a><b><span style="font-size:7.5pt;font-family:&quot;Segoe UI&quot;,sans-serif;color:gray"><br>
John Geldman</span></b><span style="font-size:7.5pt;font-family:&quot;Segoe UI&quot;,sans-serif;color:gray"><br>
Director, Industry Standards, <br>
<br>
Micron Technology, Inc.<b><br>
Office</b> &#43;1 (408) 822-0348 &nbsp;<b>Mobile</b> &#43;1 (510) 449-3597</span><u><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#0082BF"><br>
</span><span style="color:blue"><br>
</span></u><a href="mailto:jgeldman@micron.com"><span style="font-size:7.5pt;font-family:&quot;Segoe UI&quot;,sans-serif;color:gray">jgeldman@micron.com</span></a><br>
<br>
<br>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:#5F5F5F"><br>
From: &nbsp; &nbsp; &nbsp; &nbsp;</span><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">Curtis Stevens &lt;</span><a href="mailto:curtis.stevens@wdc.com"><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">curtis.stevens@wdc.com</span></a><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">&gt;<span style="color:#5F5F5F"><br>
To: &nbsp; &nbsp; &nbsp; &nbsp;</span>Gerry Houlder &lt;</span><a href="mailto:gerry.houlder@seagate.com"><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">gerry.houlder@seagate.com</span></a><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">&gt;, &quot;Otte, Olga&quot;
 &lt;</span><a href="mailto:olga.otte@hpe.com"><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">olga.otte@hpe.com</span></a><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">&gt;<span style="color:#5F5F5F"><br>
Cc: &nbsp; &nbsp; &nbsp; &nbsp;</span>&quot;T10, Reflector&quot; &lt;</span><a href="mailto:T10@t10.org"><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">T10@t10.org</span></a><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">&gt;<span style="color:#5F5F5F"><br>
Date: &nbsp; &nbsp; &nbsp; &nbsp;</span>2016-04-07 20:31<span style="color:#5F5F5F"><br>
Subject: &nbsp; &nbsp; &nbsp; &nbsp;</span>Re: [T10] Determining an SED Drive<span style="color:#5F5F5F"><br>
Sent by: &nbsp; &nbsp; &nbsp; &nbsp;</span></span><a href="mailto:t10-bounces@t10.org"><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">t10-bounces@t10.org</span></a><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#004080"><br>
Actually, TCG is one way to do SED, there are others that do not use TCG. &nbsp;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. &nbsp;The only use case is for customers that get custom configurations and know what they are getting in advance. &nbsp;Due to the nature of the problem, there is no reliable/universal detection method. &nbsp;Whatever
 you define can be spoofed. &nbsp;Including Model # and Manufacturer.<br>
</span><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F"><br>
<br>
<br>
-------------------------------------------------<br>
Curtis E. Stevens<br>
Director, Standards &amp; 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: </span><a href="mailto:Curtis.Stevens@WDC.com"><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F">Curtis.Stevens@WDC.com</span></a><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#3F621F"><br>
<br>
Remember, you may only be blamed for something if you are actually doing something.</span><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#004080"><br>
</span><b><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif"><br>
From:</span></b><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif"> </span>
<a href="mailto:t10-bounces@t10.org"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">t10-bounces@t10.org</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">[</span><a href="mailto:t10-bounces@t10.org"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">mailto:t10-bounces@t10.org</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">]
<b>On Behalf Of </b>Gerry Houlder<b><br>
Sent:</b> Thursday, April 7, 2016 9:17 AM<b><br>
To:</b> Otte, Olga &lt;</span><a href="mailto:olga.otte@hpe.com"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">olga.otte@hpe.com</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&gt;<b><br>
Cc:</b> T10, Reflector &lt;</span><a href="mailto:T10@t10.org"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">T10@t10.org</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&gt;<b><br>
Subject:</b> Re: [T10] Determining an SED Drive</span><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 &lt;<a href="mailto:olga.otte@hpe.com" target="_blank">olga.otte@hpe.com</a>&gt; wrote:<span style="font-size:10.0pt;color:#004080"><br>
Do we expect &#8220;drive not ready&#8221; or &#8220;Invalid command&#8221; 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<br>
</span><b><span style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif"><br>
From:</span></b><span style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif"> </span>
<a href="mailto:t10-bounces@t10.org" target="_blank"><span style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif">t10-bounces@t10.org</span></a><span style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif">[mailto:</span><a href="mailto:t10-bounces@t10.org" target="_blank"><span style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif">t10-bounces@t10.org</span></a><span style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif">]
<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</span><o:p></o:p></p>
<p>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.<o:p></o:p></p>
<p>There are no vital data pages for SED specific attributes.<br>
On 7 Apr 2016 12:39, Amir Dagan1 &lt;<a href="mailto:AMIRDA@il.ibm.com" target="_blank">AMIRDA@il.ibm.com</a>&gt; wrote:<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif"><br>
Hello,<br>
<br>
Is there a &quot;SCSI&quot; 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</span><br>
<br>
_______________________________________________<br>
T10 mailing list<u><span style="color:blue"><br>
</span></u><a href="mailto:T10@t10.org">T10@t10.org</a><u><span style="color:blue"><br>
</span></u><a href="http://www.t10.org/mailman/listinfo/t10" target="_blank">http://www.t10.org/mailman/listinfo/t10</a><br>
<span style="font-size:10.0pt;font-family:&quot;Courier New&quot;">_______________________________________________<br>
T10 mailing list</span><u><span style="color:blue"><br>
</span></u><a href="mailto:T10@t10.org"><span style="font-size:10.0pt;font-family:&quot;Courier New&quot;">T10@t10.org</span></a><u><span style="color:blue"><br>
</span></u><a href="http://www.t10.org/mailman/listinfo/t10"><span style="font-size:10.0pt;font-family:&quot;Courier New&quot;">http://www.t10.org/mailman/listinfo/t10</span></a><o:p></o:p></p>
<p><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>