Information technology — Fibre Channel — Part 331: Virtual Interface (FC-VI)

ISO/IEC 14165-331:2004 defines an upper-layer protocol within the domain of Fibre Channel that is designed to permit efficient peer-to-peer or client-server messaging between nodes, and to comply with the Virtual Interface (VI) Architecture. Vendors that wish to implement devices that connect to FC-VI may follow the requirements of this and other normatively referenced standards to manufacture an FC-VI compliant device. Fibre Channel is a high-speed serial interface using either optical or electrical connections (i.e. the physical layer) at data rates currently up to 2 Gbits/s with a growth path to 10 Gbits/s, and provides a general data transport vehicle for Upper Level Protocols (ULPs) such as Intelligent Peripheral Interface (IPI) and Small Computer System Interface (SCSI) command sets, the High-Performance Parallel Interface (HIPPI) data framing, IP (Internet Protocol), ANSI/IEEE 802.2 and others. The topologies supported by Fibre Channel include point-to-point, switched fabric and arbitrated loop.

Technologies de l'information — Canal de fibres — Partie 331: Interface virtuelle (FC-VI)

General Information

Status
Withdrawn
Current Stage
5098 - Project deleted
Completion Date
04-Sep-2006
Ref Project

Relations

Buy Standard

Draft
ISO/IEC FDIS 14165-331 - Information technology -- Fibre Channel
English language
89 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

FINAL
INTERNATIONAL ISO/IEC
DRAFT
STANDARD FDIS
14165-331
ISO/IEC JTC 1
Information technology — Fibre
Secretariat: ANSI
Channel —
Voting begins on:
2004-06-17
Part 331:
Virtual Interface (FC-VI)
Voting terminates on:
2004-08-17
Technologies de l'information — Canal de fibres —

Partie 331: Interface virtuelle (FC-VI)


Please see the administrative notes on page iii

RECIPIENTS OF THIS DRAFT ARE INVITED TO
SUBMIT, WITH THEIR COMMENTS, NOTIFICATION
OF ANY RELEVANT PATENT RIGHTS OF WHICH
THEY ARE AWARE AND TO PROVIDE SUPPORT-
ING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
Reference number
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO-
ISO/IEC FDIS 14165-331:2004(E)
LOGICAL, COMMERCIAL AND USER PURPOSES,
DRAFT INTERNATIONAL STANDARDS MAY ON
OCCASION HAVE TO BE CONSIDERED IN THE
LIGHT OF THEIR POTENTIAL TO BECOME STAN-
DARDS TO WHICH REFERENCE MAY BE MADE IN
©
NATIONAL REGULATIONS. ISO/IEC 2004

---------------------- Page: 1 ----------------------
ISO/IEC FDIS 14165-331:2004(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.


Copyright notice
This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as permitted
under the applicable laws of the user's country, neither this ISO draft nor any extract from it may be
reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic,
photocopying, recording or otherwise, without prior written permission being secured.
Requests for permission to reproduce should be addressed to either ISO at the address below or ISO's
member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
ii © ISO/IEC 2004 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC FDIS 14165-331:2004(E)
In accordance with the provisions of Council Resolution 21/1986, this document is circulated in the
English language only.


© ISO/IEC 2004 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC FDIS 14165-331
PATENT STATEMENT
CAUTION: The developers of this standard have requested that holders of patents that
may be required for the implementation of the standard, disclose such patents to the pub-
lisher. However, neither the developers nor the publisher have undertaken a patent
search in order to identify which, if any, patents may apply to this standard. As of the date
of publication of this standard, following calls for the identification of patents that may be
required for the implementation of the standard, no such claims have been made. No fur-
ther patent search is conducted by the developer or the publisher in respect to any stan-
dard it processes. No representation is made or implied that licenses are not required to
avoid infringement in the use of this standard.

---------------------- Page: 4 ----------------------
ISO/IEC FDIS 14165-331 iii 2004-04-06
Contents
Page
1 Scope and purpose .2
2 Normative references .2
2.1 Normative references overview .2
2.2 Approved references .2
2.3 References under development .2
2.4 Other references .2
2.4.1 VI Architecture 1.0 reference specifications .2
2.4.2 Miscellaneous .2
3 Definitions and abbreviations .3
3.1 FC-VI definitions .3
3.2 VI Definitions .4
3.3 Abbreviations .5
3.4 Editorial conventions .5
4 Structure and concepts .7
4.1 Fibre channel structure and concepts .7
4.2 FC-VI structure and concepts .7
5 FC-VI protocol overview .10
5.1 FC-VI information units .10
5.2 FC-VI message transfer operation .10
5.2.1 FC-VI message transfer .10
5.2.2 FC-VI send message transfer operation .11
5.2.3 FC-VI RDMA write message transfer operation .12
5.2.4 FC-VI RDMA read message transfer operation .14
5.2.5 IU reception at an FC-VI edpoint .15
5.3 FC-VI connection setup operation .16
5.3.1 FC-VI client-server and peer-peer connection setup .16
5.3.2 FC-VI client-server connection setup .17
5.3.3 FC-VI Peer-to-Peer Connection Establishment .18
5.3.4 FC_VI concurrent peer-to-peer connection setup .20
5.3.5 FC-VI Disconnect Operation .22
5.4 Exchange ID reuse .23
5.5 Sequence ID reuse .24
5.6 Frame synonym detection .24
5.7 VI message length .25
5.8 FC-FS header usage for FC-VI .25
5.8.1 FC-FS header usage .25
5.8.2 CS_CTL field .26
5.8.3 TYPE field .26
5.8.4 F_CTL field .26
5.8.5 DF_CTL field .26
5.8.6 SEQ_CNT field .26
5.8.7 Parameter field .26
5.9 FC-VI device_header .27
5.9.1 FC-VI device_header description .27
5.9.2 FCVI_HANDLE field .27
5.9.3 FCVI_OPCODE field .28
5.9.4 FCVI_FLAGS field .28
5.9.4.1 FCVI_FLAGS field description .28

---------------------- Page: 5 ----------------------
2004-04-06 iv ISO/IEC FDIS 141655-331
5.9.4.2 FCVI_FLAGS for message request IUs.28
5.9.4.3 FCVI_FLAGS for message response IUs .28
5.9.4.4 FCVI_FLAGS for connect request IUs.29
5.9.4.5 FCVI_FLAGS for connect response IUs .30
5.9.4.6 FCVI_FLAGS for disconnect IUs .31
5.9.5 Reserved fields .32
5.9.6 FCVI_MSG_ID field .32
5.9.7 FCVI_PARAMETER field .32
5.9.7.1 FCVI_PARAMETER field format.32
5.9.7.2 Connect response reason codes .34
5.9.7.2.1 Connect response non-error reason codes.34
5.9.7.2.2 Connect response error reason codes.34
5.9.7.3 Message response / disconnect reason codes.34
5.9.7.3.1 Descriptor error reason codes.34
5.9.7.3.2 Remote FC-VI port non-descriptor errors.35
5.9.7.3.3 Reserved for future expansion.35
5.9.7.3.4 Vendor unique reason codes .35
5.9.8 FCVI_RMT_VA field .35
5.9.9 FCVI_RMT_VA_HANDLE field .36
5.9.10 FCVI_TOT_LEN field / FCVI_CONNECTION_ID field .36
6 FC-VI Information Unit (IU) formats .37
6.1 FC-VI IU overview .37
6.2 FCVI_SEND_RQST IU .37
6.2.1 FCVI_SEND_RQST IU description .37
6.2.2 FCVI_SEND_RQST Device_Header information .37
6.3 FCVI_SEND_RESP IU .37
6.3.1 FCVI_SEND_RESP IU description .37
6.3.2 FCVI_SEND_RESP Device_Header information .37
6.4 FCVI_WRITE_RQST IU .38
6.4.1 FCVI_WRITE_RQST IU overview .38
6.4.2 FCVI_WRITE_RQST IU Device_Header information .38
6.5 FCVI_WRITE_RESP IU .38
6.5.1 FCVI_WRITE_RESP IU description .38
6.5.2 FCVI_WRITE_RESP IU Device_Header information .39
6.6 FCVI_READ_RQST IU .39
6.6.1 FCVI_READ_RQST IU description .39
6.6.2 FCVI_READ_RQST IU Device_Header information .39
6.7 FCVI_READ_RESP IU .40
6.7.1 FCVI_READ_RESP IU description .40
6.7.2 FCVI_READ_RESP IU Device_Header information .40
6.8 FCVI_CONNECT_RQST IU .40
6.8.1 FCVI_CONNECT_RQST IU description .40
6.8.2 FCVI_CONNECT_RQST Device_Header information .41
6.8.3 FCVI_CONNECT_RQST Payload Information .41
6.9 FCVI_CONNECT_RESP1 IU .42
6.9.1 FCVI_CONNECT_RESP1 IU description .42
6.9.2 FCVI_CONNECT_RESP1 Device_Header information .42
6.9.3 FCVI_CONNECT_RESP1 Payload Information .43
6.10 FCVI_CONNECT_RESP2 IU .44
6.10.1 FCVI_CONNECT_RESP2 IU description .44
6.10.2 FCVI_CONNECT_RESP2 Device_Header information .44
6.11 FCVI_CONNECT_RESP3 IU .44

---------------------- Page: 6 ----------------------
ISO/IEC FDIS 14165-331 v 2004-04-06
6.11.1 FCVI_CONNECT_RESP3 IU description .44
6.11.2 FCVI_CONNECT_RESP3 Device_Header information .44
6.12 FCVI_DISCONNECT_RQST IU .45
6.12.1 FCVI_DISCONNECT_RQST IU description .45
6.12.2 FCVI_DISCONNECT_RQST Device_Header information .45
6.13 FCVI_DISCONNECT_RESP IU .46
6.13.1 FCVI_DISCONNECT_RESP IU description .46
6.13.2 FCVI_DISCONNECT_RESP Device_Header information .46
7 FC-VI Addressing and naming .47
7.1 FC-VI Addressing and naming overview .47
7.2 FCVI_NET_ADDRESS format .47
7.3 FCVI_ATTRIBUTES format .48
7.4 FC-VI address resolution .50
7.5 FARP ELS .51
7.6 Name server queries .52
7.7 Validation of host address to N_Port identifier mappings .52
7.7.1 Address mapping overview .52
7.7.2 Point-to-point topology .52
7.7.3 Private loop topology .52
7.7.4 Public loop topology .53
7.7.5 Fabric topology .53
8 FC-VI Error detection and recovery .54
8.1 FC-VI error detection and recovery overview .54
8.2 FC-VI endpoint states .54
8.3 FCVI_ULP_TIMEOUT definition .54
8.4 Message transfer error detection and recovery rules .55
8.4.1 Message error detection .55
8.4.2 Message transfer error recovery .55
8.5 Connection setup error detection and recovery rules .56
8.5.1 Connection setup error handling overview .56
8.5.2 Connection setup error detection .56
8.5.3 Connection setup error recovery .56
8.5.4 Connection setup originator retry rules .57
8.6 Disconnect operation error detection and recovery rules .57
8.6.1 Disconnect operation error handling overview .57
8.6.2 Disconnect operation error detection .57
8.6.3 Disconnect operation error recovery rules .58
Annex A: (informative) Concurrent matching peer requests examples .59
A.1 Annex A overview.59
A.2 Case 1 .59
A.3 Case 2 .60
A.4 Case 3 .61
A.5 Case 4 .61
A.6 Case 5 .62
A.7 Case 8 .63
Annex B: (informative) FC-VI Message Transfer Error Handling Examples .64
B.1 Annex B Overview .64
B.2 Message Transfer Error Handling Operation.64
B.2.1 Message Transfer Error Handling Operation Overview .64
B.2.2 Message Transfer Error Definitions .64

---------------------- Page: 7 ----------------------
2004-04-06 vi ISO/IEC FDIS 141655-331
B.2.3 Error Detection and Recovery Rule Processing .65
B.2.4 Message Responder and Message Originator Error Recovery Actions .65
B.2.5 Message responder error detection actions .66
B.2.6 Message originator Class 2 error detection actions .68
B.2.6.1 Message originator Class 2 error detection overview.68
B.2.6.2 Message response timeout at message originator.69
B.3 Message transfer error detection and recovery examples.69
B.3.1 Error examples overview .69
B.3.2 Mrcv > Mexp error example .69
B.3.2.1 Mrcv > Mexp example description .69
B.3.2.2 Mrcv > Mexp: In-order fabric and unreliable .70
B.3.2.3 Mrcv > Mexp: In-order fabric and reliable delivery.70
B.3.2.4 Mrcv > Mexp: Out-of-order fabric.71
B.3.3 Mrcv = Mexp error example .71
B.3.3.1 Mrcv = Mexp example description .71
B.3.3.2 Mrcv = Mexp: In-order fabric and unreliable .72
B.3.3.3 Mrcv = Mexp: Out-of-order fabric.72
Annex C: (informative) Connection Setup Error Handling Examples .73
C.1 Annex C overview.73
C.2 Connection setup error handling definitions .73
C.3 Connect request originator and connect request responder rules.73
C.4 Connect request originator rules .73
C.5 Connect request responder rules .75
C.5.1 Connect request responder retry rules .76
C.6 Error detection and recovery examples for connection setup .77
C.6.1 Overview .77
C.6.2 FC-VI connection setup timers .78
C.6.3 VipConnectRequest completion .79
C.6.4 VipConnectAccept completion .79
C.6.5 Enabling message transmission and reception .79
C.6.6 Client timeout of VipConnectRequest .80
C.6.7 Lost FCVI_CONNECT_RQST IU .80
C.6.7.1 Lost FCVI_CONNECT_RQST IU example.80
C.6.7.2 Retried connection setup.81
C.6.8 Lost FCVI_CONNECT_RESP1 IU .82
C.6.9 Lost FCVI_CONNECT_RESP2 IU .83
C.6.9.1 Lost FCVI_CONNECT_RESP2 IU example.83
C.6.9.2 Server timing out connection setup .84
C.6.10 Lost FCVI_CONNECT_RESP3 IU .84
C.6.10.1 Lost FCVI_CONNECT_RESP3 IU example.84
Annex D: (informative) Disconnect operation error handling examples .86
D.1 Disconnect operation example description.86
D.2 FC-VI disconnect operation example .87
Annex E: (informative) Message streaming for reliable reception .89
Annex F: (informative) Enabling Message Transmission in the FC-VI NIC .90

---------------------- Page: 8 ----------------------
ISO/IEC FDIS 14165-331 vii 2004-04-06
Tables
Page
1 FC-VI Information unit summary.10
2 Peer B actions based on connect responses from peer A .23
3 16-byte FC-VI device_header.27
4 32-byte FC-VI device_header.27
5 FCVI_FLAGS Bit definitions for message request IUs.28
6 FCVI_FLAGS Bit definitions for message response IUs .29
7 FCVI_FLAGS Bit definitions for connect request IUs.29
8 FC-VI connection mode definition .30
9 FCVI_FLAGS Bit definitions for connect response IUs .30
10 FCVI_FLAGS Bit definitions for disconnect IUs .31
11 FCVI_PARAMETER field for connect response and disconnect IUs .32
12 Reason code for CONN_STS.33
13 FCVI_CONNECT_RQST IU payload format .41
14 FCVI_CONNECT_RESP1 IU Payload Format.43
15 FCVI_NET_ADDRESS Format .48
16 FCVI_ATTRIBUTES format.
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.