1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
|
<pre>Internet Engineering Task Force (IETF) F. Knight
Request for Comments: 7144 NetApp
Category: Standards Track M. Chadalapaka
ISSN: 2070-1721 Microsoft
April 2014
<span class="h1">Internet Small Computer System Interface (iSCSI)</span>
<span class="h1">SCSI Features Update</span>
Abstract
Internet Small Computer System Interface (iSCSI) is a SCSI
transport protocol that maps the SCSI family of protocols onto
TCP/IP. The iSCSI protocol as specified in <a href="./rfc7143">RFC 7143</a> (and as
previously specified by the combination of <a href="./rfc3720">RFC 3720</a> and <a href="./rfc5048">RFC</a>
<a href="./rfc5048">5048</a>) is based on the SAM-2 (SCSI Architecture Model - 2)
version of the SCSI family of protocols. This document
defines enhancements to the iSCSI protocol to support certain
additional features of the SCSI protocol that were defined in
SAM-3, SAM-4, and SAM-5.
This document is a companion document to <a href="./rfc7143">RFC 7143</a>.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by
the Internet Engineering Steering Group (IESG). Further
information on Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of
RFC 5741</a>.
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7144">http://www.rfc-editor.org/info/rfc7144</a>.
<span class="grey">Knight & Chadalapaka Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Knight & Chadalapaka Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a>
<a href="#section-2">2</a>. Definitions, Acronyms, and Document Summary .....................<a href="#page-4">4</a>
<a href="#section-2.1">2.1</a>. Definitions ................................................<a href="#page-4">4</a>
<a href="#section-2.2">2.2</a>. Acronyms ...................................................<a href="#page-4">4</a>
<a href="#section-2.3">2.3</a>. New Semantics ..............................................<a href="#page-4">4</a>
<a href="#section-3">3</a>. Terminology Mapping .............................................<a href="#page-5">5</a>
<a href="#section-4">4</a>. New Feature Use .................................................<a href="#page-7">7</a>
<a href="#section-4.1">4.1</a>. Negotiation of New Feature Use .............................<a href="#page-7">7</a>
4.2. Impact on Standard INQUIRY Data - iSCSI Version
Descriptors ................................................<a href="#page-8">8</a>
<a href="#section-5">5</a>. SCSI Commands ...................................................<a href="#page-9">9</a>
<a href="#section-5.1">5.1</a>. SCSI Command Additions .....................................<a href="#page-9">9</a>
<a href="#section-5.1.1">5.1.1</a>. Command Priority (Byte 2) ..........................<a href="#page-10">10</a>
<a href="#section-5.2">5.2</a>. SCSI Response Additions ...................................<a href="#page-11">11</a>
<a href="#section-5.2.1">5.2.1</a>. Status Qualifier ...................................<a href="#page-12">12</a>
<a href="#section-5.2.2">5.2.2</a>. Data Segment - Sense and Response Data Segment .....<a href="#page-12">12</a>
<a href="#section-6">6</a>. Task Management Functions ......................................<a href="#page-13">13</a>
<a href="#section-6.1">6.1</a>. Task Management Function Request PDU ......................<a href="#page-13">13</a>
<a href="#section-6.2">6.2</a>. Existing Task Management Functions ........................<a href="#page-14">14</a>
<a href="#section-6.3">6.3</a>. Task Management Function Additions ........................<a href="#page-14">14</a>
<a href="#section-6.3.1">6.3.1</a>. LUN Field ..........................................<a href="#page-15">15</a>
<a href="#section-6.3.2">6.3.2</a>. Referenced Task Tag ................................<a href="#page-16">16</a>
<a href="#section-6.3.3">6.3.3</a>. RefCmdSN ...........................................<a href="#page-16">16</a>
<a href="#section-6.4">6.4</a>. Task Management Function Responses ........................<a href="#page-17">17</a>
<a href="#section-6.4.1">6.4.1</a>. Task Management Function Response PDU ..............<a href="#page-17">17</a>
<a href="#section-6.4.2">6.4.2</a>. Task Management Function Response Additions ........<a href="#page-18">18</a>
<a href="#section-6.5">6.5</a>. Task Management Requests Affecting Multiple Tasks .........<a href="#page-19">19</a>
<a href="#section-7">7</a>. Login/Text Operational Text Keys ...............................<a href="#page-19">19</a>
<a href="#section-7.1">7.1</a>. New Operational Text Keys .................................<a href="#page-19">19</a>
<a href="#section-7.1.1">7.1.1</a>. iSCSIProtocolLevel .................................<a href="#page-19">19</a>
<a href="#section-8">8</a>. Security Considerations ........................................<a href="#page-20">20</a>
<a href="#section-9">9</a>. IANA Considerations ............................................<a href="#page-21">21</a>
<a href="#section-10">10</a>. References ....................................................<a href="#page-24">24</a>
<a href="#section-10.1">10.1</a>. Normative References .....................................<a href="#page-24">24</a>
<a href="#section-10.2">10.2</a>. Informative References ...................................<a href="#page-24">24</a>
<a href="#section-11">11</a>. Acknowledgements ..............................................<a href="#page-24">24</a>
<span class="grey">Knight & Chadalapaka Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The original iSCSI protocol [<a href="./rfc3720" title=""Internet Small Computer Systems Interface (iSCSI)"">RFC3720</a>] was built based on the [<a href="#ref-SAM2" title=""SCSI Architecture Model - 2 (SAM-2)"">SAM2</a>]
model for SCSI. Several new features and capabilities have been
added to the SCSI Architecture Model in the intervening years (at the
time of publication of this document, SAM-5 was the current version
of the SCSI Architecture Model). This document is not a complete
revision of [<a href="./rfc3720" title=""Internet Small Computer Systems Interface (iSCSI)"">RFC3720</a>]. Instead, this document is intended as a
companion document to <a href="./rfc7143">RFC 7143</a>; this document may also be used as a
companion document to the combination of [<a href="./rfc3720" title=""Internet Small Computer Systems Interface (iSCSI)"">RFC3720</a>] and [<a href="./rfc5048" title=""Internet Small Computer System Interface (iSCSI) Corrections and Clarifications"">RFC5048</a>],
although both of those RFCs have been obsoleted by [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>].
For more information on the SCSI Architecture Model and SCSI Primary
Commands - 4, contact the INCITS T10 Technical Committee for SCSI
Storage Interfaces at <<a href="http://www.t10.org">http://www.t10.org</a>>.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Definitions, Acronyms, and Document Summary</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Definitions</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Acronyms</span>
ACA Auto Contingent Allegiance
AHS Additional Header Segment
ISID Initiator Session Identifier
LU Logical Unit
PDU Protocol Data Unit
SAM-5 SCSI Architecture Model - 5 (see [<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>])
TSIH Target Session Identifying Handle
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. New Semantics</span>
This document specifies new iSCSI semantics. This section summarizes
the contents of the document.
<a href="#section-3">Section 3</a>: The mapping of iSCSI objects to SAM-5 objects
The iSCSI node may contain both initiator and target
capabilities.
<a href="#section-4">Section 4</a>: New feature use
New features need negotiation for use. The
negotiation may have an impact on standard INQUIRY
data.
<span class="grey">Knight & Chadalapaka Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
<a href="#section-5">Section 5</a>: New command operations
The PRI field for SCSI command priority has been added
to the SCSI Command PDU (see <a href="#section-5.1.1">Section 5.1.1</a>). The
Status Qualifier field has been added to the SCSI
Response PDU (see <a href="#section-5.2.1">Section 5.2.1</a>). Sense data may be
returned (via Autosense) for any SCSI status, not just
CHECK CONDITION (see <a href="#section-5.2.2">Section 5.2.2</a>).
<a href="#section-6">Section 6</a>: New task management functions
Four new task management functions (QUERY TASK, QUERY
TASK SET, I_T NEXUS RESET, and QUERY ASYNCHRONOUS
EVENT) have been added (see <a href="#section-6.3">Section 6.3</a>). A new
"Function succeeded" response has been added (see
<a href="#section-6.4.2">Section 6.4.2</a>).
<a href="#section-7">Section 7</a>: New negotiation key
A new negotiation key has been added to enable the use
of the new features in Sections <a href="#section-5">5</a> and <a href="#section-6">6</a>.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Terminology Mapping</span>
The iSCSI model (defined in [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>]) uses different terminology
than the SCSI Architecture Model. In some cases, iSCSI uses multiple
terms to describe what in the SCSI Architecture Model is described
with a single term. The iSCSI terms and SAM-5 terms are not
necessarily equivalent, but rather, the iSCSI terms represent
examples of the objects or classes described in SAM-5 as follows:
<span class="grey">Knight & Chadalapaka Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
Terminology in <a href="./rfc7143">RFC 7143</a> | Terminology in SAM-5
+-----------------------------+---------------------------+
| Network Entity | none |
+-----------------------------+---------------------------+
| iSCSI Node | SCSI Device |
+-----------------------------+---------------------------+
| iSCSI Name | SCSI Device Name |
+-----------------------------+---------------------------+
| iSCSI Node Name | SCSI Device Name |
+-----------------------------+---------------------------+
| iSCSI Initiator Node | SCSI Initiator Device |
+-----------------------------+---------------------------+
| iSCSI Initiator Name | SCSI Device Name |
+-----------------------------+---------------------------+
| iSCSI Initiator Port | SCSI Initiator Port |
| Identifier; (i.e., iSCSI | Identifier |
| Node Name + ,,,i, + ISID)** | |
+-----------------------------+---------------------------+
| iSCSI Initiator Port Name; | SCSI Initiator Port Name |
| (i.e., iSCSI Node Name + | |
| ,,,i, + ISID)** | |
+-----------------------------+---------------------------+
| iSCSI Target Node | SCSI Target Device |
+-----------------------------+---------------------------+
| iSCSI Target Name | SCSI Device Name |
+-----------------------------+---------------------------+
| iSCSI Target Port | SCSI Target Port |
| Identifier; (i.e., iSCSI | Identifier |
| Node Name + ,,,t, + | |
| Target Portal Group Tag)** | |
+-----------------------------+---------------------------+
| iSCSI Target Port Name; | SCSI Target Port Name |
| (i.e., iSCSI Node Name + | |
| ,,,t, + Target Portal | |
| Group Tag)** | |
+-----------------------------+---------------------------+
| iSCSI Target Portal Group | SCSI Target Port |
+-----------------------------+---------------------------+
| iSCSI Initiator Name + | I_T Nexus Identifier |
| ',i,' + ISID + iSCSI | |
| Target Name + ',t,' + | |
| Target Portal Group Tag | |
+-----------------------------+---------------------------+
| Target Portal Group Tag | Relative Port ID |
+-----------------------------+---------------------------+
** The text encoding of the ISID value and the Target Portal Group
Tag value includes an initial ,,0X or ,,0x (see [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>]).
<span class="grey">Knight & Chadalapaka Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
The following diagram shows an example of a combination target device
and initiator device. Such a configuration may exist in a target
device that implements a SCSI Copy Manager. This example shows how a
session that shares Network Portals within a Portal Group may be
established (see Target Portal Group 1). In addition, this example
shows the initiator using a different portal group than the target
portal group, but the initiator portal group sharing Network Portal A
with the target portal group.
----------------------------IP Network---------------------
| | |
+----|---------------|-------+ +----|------------+
| +----------+ +----------+ | | +----------+ |
| | Network | | Network | | | | Network | |
| | Portal A | | Portal B | | | | Portal A | |
| +----------+ +----------+ | | +----------+ |
| | Target | | | | Initiator |
| | Portal | | | | Portal |
| | Group 1 | | | | Group 2 |
+----|---------------|-------+ +----|------------+
| | |
+----------|---------------|--------------------|--------------------+
| +--------|---------------|----+ +-------------|------------------+ |
| |+-------|---------------|---+| |+------------|-----------------+| |
| ||iSCSI Session (Target side)|| ||iSCSI Session (Initiator side)|| |
| || || || || |
| || (TSIH = 56) || || (SSID = 48) || |
| |+---------------------------+| |+------------------------------+| |
| | | | | |
| | iSCSI Target Node | | iSCSI Initiator Node | |
| +-----------------------------+ +--------------------------------+ |
| iSCSI Node |
| (within Network Entity, not shown) |
+--------------------------------------------------------------------+
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. New Feature Use</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Negotiation of New Feature Use</span>
The iSCSIProtocolLevel operational text key (see <a href="#section-7.1.1">Section 7.1.1</a>)
containing a value of "2" MUST be negotiated to enable the use of
features described in this RFC.
This is an iSCSI negotiation mechanism that enabled iSCSI support for
corresponding SCSI capabilities (see [<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>] and [<a href="#ref-SPC4" title=""SCSI Primary Commands - 4"">SPC4</a>]). For this
reason, negotiation of this key to a value of "2" is necessary but
not sufficient for use of the SCSI capabilities enabled by the iSCSI
features in this RFC.
<span class="grey">Knight & Chadalapaka Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
For example, an iSCSI implementation may negotiate this new key to
"2" but respond to the new task management functions (see <a href="#section-6.3">Section</a>
<a href="#section-6.3">6.3</a>) with "Task management function not supported" (which indicates a
SCSI error that prevents the function from being performed). In
contrast, if the key is negotiated to "2", an iSCSI implementation
MUST NOT reject a Task Management Function Request PDU that requests
one of the new task management functions (as such a reject would
report an iSCSI protocol error).
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Impact on Standard INQUIRY Data - iSCSI Version Descriptors</span>
The negotiated value of the iSCSIProtocolLevel key is an increment
from the base iSCSI version descriptor value (0960h); see [<a href="#ref-SPC4" title=""SCSI Primary Commands - 4"">SPC4</a>]. If
the SCSI device server returns an iSCSI version descriptor in the
standard INQUIRY data, then the value returned in that iSCSI version
descriptor MUST be set to the sum of the base value (0960h) plus the
negotiated value of the iSCSIProtocolLevel key. (For example, if the
negotiated iSCSIProtocolLevel=2, then if an iSCSI version descriptor
is returned in the standard INQUIRY data, it is set to 0962h.)
In support of this functionality, INCITS Technical Committee T10,
which is responsible for SCSI standards, has assigned SCSI version
descriptor codes 0961h-097Fh to <a href="./rfc7144">RFC 7144</a> for IANA to manage via the
values 1-31 of the iSCSIProtocolLevel key; see <a href="#section-9">Section 9</a>. The "No
version claimed" description for the value 0 of the
iSCSIProtocolLevel key corresponds to the existing T10 assignment of
the 0960h SCSI version descriptor code to "iSCSI (no version
claimed)" -- for this reason, the assignment of the value 0 in the
IANA registry for the iSCSIProtocolLevel key must not be changed.
<span class="grey">Knight & Chadalapaka Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. SCSI Commands</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. SCSI Command Additions</span>
The format of the SCSI Command PDU is:
Byte/ 0 | 1 | 2 | 3 |
/ | | | |
|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|
+---------------+---------------+---------------+---------------+
0|.|I| 0x01 |F|R|W|. .|ATTR | PRI | Reserved |
+---------------+---------------+---------------+---------------+
4|TotalAHSLength | DataSegmentLength |
+---------------+---------------+---------------+---------------+
8| Logical Unit Number (LUN) |
+ +
12| |
+---------------+---------------+---------------+---------------+
16| Initiator Task Tag |
+---------------+---------------+---------------+---------------+
20| Expected Data Transfer Length |
+---------------+---------------+---------------+---------------+
24| CmdSN |
+---------------+---------------+---------------+---------------+
28| ExpStatSN |
+---------------+---------------+---------------+---------------+
32/ SCSI Command Descriptor Block (CDB) /
+/ /
+---------------+---------------+---------------+---------------+
48/ AHS (Optional) /
+---------------+---------------+---------------+---------------+
x/ Header Digest (Optional) /
+---------------+---------------+---------------+---------------+
y/ (DataSegment, Command Data) (Optional) /
+/ /
+---------------+---------------+---------------+---------------+
z/ Data Digest (Optional) /
+---------------+---------------+---------------+---------------+
The SCSI Command PDU above is duplicated from [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>] for reference
to show the PRI field. For any field other than the PRI field, the
text in [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>] supersedes the text in <a href="#section-5.1">Section 5.1</a> of this document
in the event the two documents conflict.
<span class="grey">Knight & Chadalapaka Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
<span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>. Command Priority (Byte 2)</span>
The Command Priority (PRI) is a four-bit field that specifies the
relative scheduling importance of this command in relation to other
commands already in the task set with SIMPLE task attributes (see
[<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>]).
<a href="#section-11">Section 11</a> ("iSCSI PDU Formats") of [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>] requires that senders
set this field to zero. A sender MUST NOT set this field to a value
other than zero unless the iSCSIProtocolLevel text key defined in
<a href="#section-7.1.1">Section 7.1.1</a> has been negotiated on the session with a value of "2".
This field MUST be ignored by iSCSI targets unless the
iSCSIProtocolLevel text key with a value of "2" as defined in <a href="#section-7.1.1">Section</a>
<a href="#section-7.1.1">7.1.1</a> was negotiated on the session.
See [<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>] for additional considerations on the use of the Command
Priority field.
<span class="grey">Knight & Chadalapaka Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. SCSI Response Additions</span>
The format of the SCSI Response PDU is:
Byte/ 0 | 1 | 2 | 3 |
/ | | | |
|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|
+---------------+---------------+---------------+---------------+
0|.|.| 0x21 |1|. .|o|u|O|U|.| Response | Status |
+---------------+---------------+---------------+---------------+
4|TotalAHSLength | DataSegmentLength |
+---------------+---------------+---------------+---------------+
8| Status Qualifier | Reserved |
+---------------+---------------+---------------+---------------+
12| Reserved |
+---------------+---------------+---------------+---------------+
16| Initiator Task Tag |
+---------------+---------------+---------------+---------------+
20| SNACK Tag or Reserved |
+---------------+---------------+---------------+---------------+
24| StatSN |
+---------------+---------------+---------------+---------------+
28| ExpCmdSN |
+---------------+---------------+---------------+---------------+
32| MaxCmdSN |
+---------------+---------------+---------------+---------------+
36| ExpDataSN or Reserved |
+---------------+---------------+---------------+---------------+
40| Bidirectional Read Residual Count or Reserved |
+---------------+---------------+---------------+---------------+
44| Residual Count or Reserved |
+---------------+---------------+---------------+---------------+
48| Header-Digest (Optional) |
+---------------+---------------+---------------+---------------+
/ Data Segment (Optional) /
+/ /
+---------------+---------------+---------------+---------------+
| Data-Digest (Optional) |
+---------------+---------------+---------------+---------------+
The SCSI Response PDU above is duplicated from [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>] for
reference to show the Status Qualifier field. For any field other
than the Status field, the Status Qualifier field, and the Data
Segment - Sense and Response Data Segment field, the text in
[<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>] supersedes the text in <a href="#section-5.2">Section 5.2</a> of this document in the
event the two documents conflict.
<span class="grey">Knight & Chadalapaka Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. Status Qualifier</span>
The Status Qualifier provides additional status information (see
[<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>]).
As defined in <a href="#section-11">Section 11</a> ("iSCSI PDU Formats") of [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>],
compliant senders already set this field to zero. Compliant senders
MUST NOT set this field to a value other than zero unless the
iSCSIProtocolLevel text key with a value of "2" as defined in <a href="#section-7.1.1">Section</a>
<a href="#section-7.1.1">7.1.1</a> was negotiated on the session.
This field MUST be ignored by receivers unless the iSCSIProtocolLevel
text key with a value of "2" as defined in <a href="#section-7.1.1">Section 7.1.1</a> was
negotiated on the session.
<span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>. Data Segment - Sense and Response Data Segment</span>
<a href="./rfc7143#section-11.4.7">Section 11.4.7 of [RFC7143]</a> specifies that iSCSI targets MUST support
and enable Autosense. If Status is CHECK CONDITION (0x02), then the
Data Segment MUST contain sense data for the failed command. While
[<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>] does not make any statements about the state of the Data
Segment when the Status is not CHECK CONDITION (0x02) (i.e., the Data
Segment is not prohibited from containing sense data when the Status
is not CHECK CONDITION), negotiation of the iSCSIProtocolLevel text
key with a value of "2" as defined in <a href="#section-7.1.1">Section 7.1.1</a> explicitly
indicates that the Data Segment MAY contain sense data at any time,
no matter what value is set in the Status field.
<span class="grey">Knight & Chadalapaka Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Task Management Functions</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Task Management Function Request PDU</span>
Byte/ 0 | 1 | 2 | 3 |
/ | | | |
|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|
+---------------+---------------+---------------+---------------+
0|.|I| 0x02 |1| Function | Reserved |
+---------------+---------------+---------------+---------------+
4|TotalAHSLength | DataSegmentLength |
+---------------+---------------+---------------+---------------+
8| Logical Unit Number (LUN) |
+ +
12| |
+---------------+---------------+---------------+---------------+
16| Initiator Task Tag |
+---------------+---------------+---------------+---------------+
20| Referenced Task Tag or 0xffffffff |
+---------------+---------------+---------------+---------------+
24| CmdSN |
+---------------+---------------+---------------+---------------+
28| ExpStatSN |
+---------------+---------------+---------------+---------------+
32| RefCmdSN or Reserved |
+---------------+---------------+---------------+---------------+
36| ExpDataSN or Reserved |
+---------------+---------------+---------------+---------------+
40| Reserved /
+/ /
+---------------+---------------+---------------+---------------+
48| Header-Digest (Optional) |
+---------------+---------------+---------------+---------------+
The Task Management Function Request PDU above is duplicated from
[<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>] for reference only. [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>] supersedes the text in
Sections <a href="#section-6.1">6.1</a> and <a href="#section-6.2">6.2</a> of this document in the event the two documents
conflict.
<span class="grey">Knight & Chadalapaka Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Existing Task Management Functions</span>
<a href="./rfc7143#section-11.5">Section 11.5 of [RFC7143]</a> defines the semantics used to request that
SCSI task management functions be performed. The following task
management functions are defined:
1 - ABORT TASK
2 - ABORT TASK SET
3 - CLEAR ACA
4 - CLEAR TASK SET
5 - LOGICAL UNIT RESET
6 - TARGET WARM RESET
7 - TARGET COLD RESET
8 - TASK REASSIGN
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Task Management Function Additions</span>
Additional task management function codes are listed below. For a
more detailed description of SCSI task management, see [<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>].
9 - QUERY TASK - determine if the command identified by the
Referenced Task Tag field is present in the task set.
10 - QUERY TASK SET - determine if any command is present in the
task set for the I_T_L Nexus on which the task management
function was received.
11 - I_T NEXUS RESET - perform an I_T nexus loss function (see
[<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>]) for the I_T nexus on which the task management function
was received.
12 - QUERY ASYNCHRONOUS EVENT - determine if there is a unit
attention condition or a deferred error pending for the I_T_L
nexus on which the task management function was received.
These task management function requests MUST NOT be sent unless the
iSCSIProtocolLevel text key with a value of "2" as defined in <a href="#section-7.1.1">Section</a>
<a href="#section-7.1.1">7.1.1</a> was negotiated on the session.
Any compliant initiator that sends any of the new task management
functions defined in this section MUST also support all new task
management function responses (as specified in <a href="#section-6.4.2">Section 6.4.2</a>).
For all of the task management functions detailed in this section,
the Task Management Function Response MUST be returned as detailed in
<a href="#section-6.4">Section 6.4</a>.
<span class="grey">Knight & Chadalapaka Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
The iSCSI target MUST ensure that no responses for the commands
covered by a task management function are sent to the iSCSI initiator
port after the Task Management response except for commands covered
by a TASK REASSIGN, QUERY TASK, or QUERY TASK SET.
If a QUERY TASK is issued for a task created by an immediate command,
then RefCmdSN MUST be that of the Task Management request itself
(i.e., CmdSN and RefCmdSN are equal); otherwise, RefCmdSN MUST be set
to the CmdSN of the task to be queried (lower than CmdSN).
If the connection is still active (it is not undergoing an implicit
or explicit logout), QUERY TASK MUST be issued on the same connection
to which the task to be queried is allegiant at the time the Task
Management request is issued. If the connection is implicitly or
explicitly logged out (i.e., no other request will be issued on the
failing connection and no other response will be received on the
failing connection), then a QUERY TASK function request may be issued
on another connection. This Task Management request will then
establish a new allegiance for the command being queried.
At the target, a QUERY TASK function MUST NOT be executed on a Task
Management request; such a request MUST result in Task Management
response of "Function rejected".
For the I_T NEXUS RESET function, the target device MUST respond to
the function as defined in [<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>]. Each logical unit accessible via
the receiving I_T NEXUS MUST behave as dictated by the I_T nexus loss
function in [<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>] for the I_T nexus on which the task management
function was received. The target device MUST drop all connections
in the session over which this function is received. Independent of
the DefaultTime2Wait and DefaultTime2Retain values applicable to the
session over which this function is received, the target device MUST
consider each participating connection in the session to have
immediately timed out, leading to FREE state. The resulting timeouts
cause the session timeout event defined in [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>], which in turn
triggers the I_T nexus loss notification to the SCSI layer as
described in [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>].
<span class="h4"><a class="selflink" id="section-6.3.1" href="#section-6.3.1">6.3.1</a>. LUN Field</span>
This field is required for functions that address a specific LU
(i.e., ABORT TASK, CLEAR TASK SET, ABORT TASK SET, CLEAR ACA, LOGICAL
UNIT RESET, QUERY TASK, QUERY TASK SET, and QUERY ASYNCHRONOUS EVENT)
and is reserved in all others.
<span class="grey">Knight & Chadalapaka Standards Track [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
<span class="h4"><a class="selflink" id="section-6.3.2" href="#section-6.3.2">6.3.2</a>. Referenced Task Tag</span>
The Reference Task Tag is the Initiator Task Tag of the task to be
aborted for the ABORT TASK function, reassigned for the TASK REASSIGN
function, or queried for the QUERY TASK function. For all other
functions, this field MUST be set to the reserved value 0xffffffff.
<span class="h4"><a class="selflink" id="section-6.3.3" href="#section-6.3.3">6.3.3</a>. RefCmdSN</span>
If a QUERY TASK is issued for a task created by an immediate command
then RefCmdSN MUST be that of the Task Management request itself
(i.e., CmdSN and RefCmdSN are equal).
For a QUERY TASK of a task created by non-immediate command RefCmdSN
MUST be set to the CmdSN of the task identified by the Referenced
Task Tag field. Targets must use this field as described in <a href="./rfc7143#section-11.6.1">section</a>
<a href="./rfc7143#section-11.6.1">11.6.1 of [RFC7143]</a> when the task identified by the Referenced Task
Tag field is not in the task set.
<span class="grey">Knight & Chadalapaka Standards Track [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Task Management Function Responses</span>
<span class="h4"><a class="selflink" id="section-6.4.1" href="#section-6.4.1">6.4.1</a>. Task Management Function Response PDU</span>
Byte/ 0 | 1 | 2 | 3 |
/ | | | |
|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|0 1 2 3 4 5 6 7|
+---------------+---------------+---------------+---------------+
0|.|.| 0x22 |1| Reserved | Response | Reserved |
+---------------+---------------+---------------+---------------+
4|TotalAHSLength | DataSegmentLength |
+-----------------------------------------------+---------------+
8| Additional Response Information | Reserved |
+-----------------------------------------------+---------------+
12| Reserved |
+---------------+---------------+---------------+---------------+
16| Initiator Task Tag |
+---------------+---------------+---------------+---------------+
20| Reserved |
+---------------+---------------+---------------+---------------+
24| StatSN |
+---------------+---------------+---------------+---------------+
28| ExpCmdSN |
+---------------+---------------+---------------+---------------+
32| MaxCmdSN |
+---------------+---------------+---------------+---------------+
36/ Reserved /
+/ /
+---------------+---------------+---------------+---------------+
48| Header-Digest (Optional) |
+---------------+---------------+---------------+---------------+
<a href="./rfc7143#section-11.6">Section 11.6 of [RFC7143]</a> defines the semantics used for responses to
SCSI task management functions. The following responses are defined
in [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>]:
0 - Function Complete
1 - Task does not exist
2 - LUN does not exist
3 - Task still allegiant
4 - Task allegiance reassignment not supported
5 - Task management function not supported
6 - Function authorization failed
255 - Function rejected
<span class="grey">Knight & Chadalapaka Standards Track [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
The Task Management Function Response PDU above and the list of task
management function responses above are duplicated from [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>] for
reference only. [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>] supersedes the text in <a href="#section-6.4.1">section 6.4.1</a> of
this document in the event the two documents conflict.
Responses to new task management functions (see <a href="#section-6.4.2">Section 6.4.2</a>) are
listed below. In addition, a new task Management response is listed
below. For a more detailed description of SCSI task management
responses, see [<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>].
For the functions QUERY TASK, QUERY TASK SET, I_T NEXUS RESET, and
QUERY ASYNCHRONOUS EVENT, the target performs the requested Task
Management function and sends a Task Management response back to the
initiator.
<span class="h4"><a class="selflink" id="section-6.4.2" href="#section-6.4.2">6.4.2</a>. Task Management Function Response Additions</span>
The new response is listed below:
7 - Function succeeded
In symbolic terms Response value 7 maps to the SCSI service response
of FUNCTION SUCCEEDED in [<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>].
The Task Management Function Response of "Function succeeded" MUST be
supported by an initiator that sends any of the new task management
functions (see <a href="#section-6.3">Section 6.3</a>).
For the QUERY TASK function, if the specified task is in the task
set, then the logical unit returns a Response value of "Function
succeeded", and additional response information is returned as
specified in [<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>]. If the specified task is not in the task set,
then the logical unit returns a Response value of "Function
complete".
For the QUERY TASK SET function, if there is any command present in
the task set from the specified I_T_L nexus, then the logical unit
returns a Response value of "Function succeeded". If there are no
commands present in the task set from the specified I_T_L nexus, then
the logical unit returns a Response value of "Function complete".
For the I_T NEXUS RESET function, after completion of the events
described in <a href="#section-6.3">Section 6.3</a> for this function, the logical unit returns
a Response value of "Function complete". However, because the target
drops all connections, the Service Response (defined by [<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>]) for
this SCSI task management function may not be reliably delivered to
the issuing initiator port.
<span class="grey">Knight & Chadalapaka Standards Track [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
For the QUERY ASYNCHRONOUS EVENT, if there is a unit attention
condition or deferred error pending for the specified I_T_L nexus,
then the logical unit returns a Response value of "Function
succeeded", and additional response information is returned as
specified in [<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>]. If there is no unit attention or deferred error
pending for the specified I_T_L nexus, then the logical unit returns
a Response value of "Function complete".
<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Task Management Requests Affecting Multiple Tasks</span>
<a href="./rfc5048#section-4.1">Section 4.1 of [RFC5048]</a> defines the notion of "affected tasks" in
multi-task abort scenarios. This section adds to the list included
in that section by defining the tasks affected by the I_T NEXUS RESET
function.
I_T NEXUS RESET: All outstanding tasks received on the I_T nexus
on which the function request was received for all logical
units accessible to the I_T nexus.
Sections <a href="#section-4.1.2">4.1.2</a> and <a href="#section-4.1.3">4.1.3</a> of [<a href="./rfc5048" title=""Internet Small Computer System Interface (iSCSI) Corrections and Clarifications"">RFC5048</a>] identify semantics for task
management functions that involve multi-task abort operations. If an
iSCSI implementation supports the I_T NEXUS RESET function, it MUST
also support the protocol behavior as defined in those sections and
follow the sequence of actions as described in those sections when
processing the I_T NEXUS RESET function.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Login/Text Operational Text Keys</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. New Operational Text Keys</span>
<span class="h4"><a class="selflink" id="section-7.1.1" href="#section-7.1.1">7.1.1</a>. iSCSIProtocolLevel</span>
Use: LO, IO
Irrelevant when: SessionType = Discovery
Senders: Initiator and Target
Scope: SW
iSCSIProtocolLevel=<numerical-value-from-0-to-31>
Default is 1.
Result function is Minimum.
This key is used to negotiate the use of iSCSI features that require
different levels of protocol support (e.g., PDU formats, end-node
semantics) for proper operation.
<span class="grey">Knight & Chadalapaka Standards Track [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
Negotiation of the iSCSIProtocolLevel key to a value corresponding to
an RFC indicates that both negotiating parties are compliant to the
RFC in question and agree to support the corresponding PDU formats
and semantics on that iSCSI session. Features using this key are
expected to be cumulative.
An iSCSIProtocolLevel key negotiated to "0" indicates that the
implementation does not claim a specific iSCSI protocol level.
An iSCSIProtocolLevel key negotiated to "1" indicates that the
implementation claims compliance with [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>].
An iSCSIProtocolLevel key negotiated to "2" is required to enable use
of features defined in this RFC.
If the negotiation answer is ignored by the acceptor, or the answer
from the remote iSCSI end point is key=NotUnderstood, then the
features defined in this RFC, and the features defined in any RFC
requiring a key value greater than "2", MUST NOT be used.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
Command priorities are relative values, not absolute values (see
[<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>], and affect collections of commands, not necessarily
individual commands (see [<a href="#ref-SAM5" title=""SCSI Architecture Model - 5 (SAM-5)"">SAM5</a>]). If command priority is supported,
it should be implemented in a fashion that avoids unwanted reduction
or denial of service.
All the iSCSI-related security text in [<a href="./rfc3723" title=""Securing Block Storage Protocols over IP"">RFC3723</a>] is directly
applicable to this document. The security text in [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>] is
directly applicable as well.
<span class="grey">Knight & Chadalapaka Standards Track [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. IANA Considerations</span>
This document modifies or creates a number of iSCSI-related
registries.
The following iSCSI-related registries are modified.
1. iSCSI Task Management Functions Codes
Name of the existing registry: "iSCSI Task Management Function
Codes"
The following entries have been added:
9 - QUERY TASK, <a href="./rfc7144">RFC 7144</a>
10 - QUERY TASK SET, <a href="./rfc7144">RFC 7144</a>
11 - I_T NEXUS RESET, <a href="./rfc7144">RFC 7144</a>
12 - QUERY ASYNCHRONOUS EVENT, <a href="./rfc7144">RFC 7144</a>
13-127 - Unassigned
2. iSCSI Login/Text Keys
Name of the existing registry: "iSCSI Login/Text Keys"
Fields to record in the registry: Assigned value and its
associated RFC reference.
The following entry has been added:
iSCSIProtocolLevel, <a href="./rfc7144">RFC 7144</a>
IANA has created the following iSCSI-related registries.
3. iSCSI Protocol Level
Name of new registry: "iSCSI Protocol Level"
Namespace details: Numerical values from 0 to 31
Information that must be provided to assign a new value: An IESG-
approved Standards Track specification defining the semantics and
interoperability requirements of the proposed new value and the
fields to be recorded in the registry.
<span class="grey">Knight & Chadalapaka Standards Track [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
Assignment policy:
The assignments of these values must be coordinated with the
INCITS T10 committee; therefore, review by an expert that
maintains an association with that committee is required prior to
IESG approval of the associated specification. After creation of
the registry, values are to be assigned sequentially (for example,
any value greater than 4 will not be assigned until after the
value 4 has been assigned).
Special care must be taken in the assignment of new values in this
registry. Compatibility and interoperability will be adversely
impacted if proper care is not exercised. Features using this key
are expected to be cumulative. For example, since this document
explicitly lists only value 2 for the features listed in this
document, it is expected that a new RFC assigning value 3 will
also have the features listed in this RFC, and therefore such an
RFC is expected to either revise or replace this RFC. Assignments
that do not follow this policy should be reviewed and approved by
the INCITS T10 committee.
3-31: range available to IANA for assignment in this registry.
Fields to record in the registry: Assigned value, description, and
its associated RFC reference.
The following entries have been added:
Value Description Reference
0 No version claimed <a href="./rfc7144">RFC 7144</a>
1 <a href="./rfc7143">RFC 7143</a> [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>]
2 <a href="./rfc7144">RFC 7144</a> <a href="./rfc7144">RFC 7144</a>
3-31 Unassigned
Allocation Policy: Expert Review and Standards Action [<a href="./rfc5226" title="">RFC5226</a>]
4. iSCSI Task Management Function Response Codes
Name of new registry: "iSCSI Task Management Function Response
Codes"
Namespace details: Numerical values that can fit in 8 bits.
<span class="grey">Knight & Chadalapaka Standards Track [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
Information that must be provided to assign a new value: An IESG-
approved specification defining the semantics and interoperability
requirements of the proposed new value and the fields to be
recorded in the registry.
Assignment policy:
If the requested value is not already assigned, it may be assigned
to the requester.
8-254: Range available to IANA for assignment in this registry.
Fields to record in the registry: Assigned value, Operation Name,
and its associated RFC reference.
The following entries have been added:
0 - Function complete, [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>]
1 - Task does not exist, [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>]
2 - LUN does not exist, [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>]
3 - Task still allegiant, [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>]
4 - Task allegiance reassignment not supported, [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>]
5 - Task management function not supported, [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>]
6 - Function authorization failed, [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>]
7 - Function succeeded, <a href="./rfc7144">RFC 7144</a>
8-254 - Unassigned
255 - Function rejected, [<a href="./rfc7143" title=""Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)"">RFC7143</a>]
Allocation Policy: Standards Action [<a href="./rfc5226" title="">RFC5226</a>]
<span class="grey">Knight & Chadalapaka Standards Track [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC3723">RFC3723</a>] Aboba, B., Tseng, J., Walker, J., Rangan, V., and F.
Travostino, "Securing Block Storage Protocols over IP",
<a href="./rfc3723">RFC 3723</a>, April 2004.
[<a id="ref-RFC5048">RFC5048</a>] Chadalapaka, M., Ed., "Internet Small Computer System
Interface (iSCSI) Corrections and Clarifications", <a href="./rfc5048">RFC</a>
<a href="./rfc5048">5048</a>, October 2007.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
May 2008.
[<a id="ref-RFC7143">RFC7143</a>] Chadalapaka, M., Satran, J., Meth, K., and D. Black,
"Internet Small Computer System Interface (iSCSI) Protocol
(Consolidated)", <a href="./rfc7143">RFC 7143</a>, April 2014.
[<a id="ref-SAM2">SAM2</a>] INCITS Technical Committee T10, "SCSI Architecture Model -
2 (SAM-2)", ANSI INCITS 366-2003, ISO/IEC 14776-412, 2003.
[<a id="ref-SAM5">SAM5</a>] INCITS Technical Committee T10, "SCSI Architecture Model -
5 (SAM-5)", T10/BSR INCITS 515 rev 04, Committee Draft.
[<a id="ref-SPC4">SPC4</a>] INCITS Technical Committee T10, "SCSI Primary Commands -
4", ANSI INCITS 513-201x.
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
[<a id="ref-RFC3720">RFC3720</a>] Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka, M.,
and E. Zeidner, "Internet Small Computer Systems Interface
(iSCSI)", <a href="./rfc3720">RFC 3720</a>, April 2004.
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Acknowledgements</span>
The Storage Maintenance (STORM) Working Group in the Transport Area
of the IETF has been responsible for defining these additions to the
iSCSI protocol (apart from other relevant IP Storage protocols). The
authors acknowledge the contributions of the entire working group and
other IETF reviewers.
<span class="grey">Knight & Chadalapaka Standards Track [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc7144">RFC 7144</a> iSCSI SCSI Features Update April 2014</span>
The following individuals directly contributed to identifying issues
and/or suggesting resolutions to the issues clarified in this
document: David Black, Rob Elliott. This document benefited from all
of these contributions.
Authors' Addresses
Frederick Knight
7301 Kit Creek Road
P.O. Box 13917
Research Triangle Park, NC 27709
USA
Phone: +1-919-476-5362
EMail: knight@netapp.com
Mallikarjun Chadalapaka
Microsoft
One Microsoft Way
Redmond, WA 98052
USA
EMail: cbm@chadalapaka.com
Knight & Chadalapaka Standards Track [Page 25]
</pre>
|
