Fibre Channel Over TCP/IP (FCIP)
RFC 3821

Document Type RFC - Proposed Standard (July 2004; No errata)
Updated by RFC 7146
Last updated 2015-10-14
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3821 (Proposed Standard)
Consensus Unknown
Telechat date
Responsible AD Allison Mankin
Send notices to <ElizabethRodriguez@ieee.org>
Network Working Group                                       M. Rajagopal
Request for Comments: 3821                                  E. Rodriguez
Category: Standards Track                                       R. Weber
                                                              July 2004

                    Fibre Channel Over TCP/IP (FCIP)

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   Fibre Channel Over TCP/IP (FCIP) describes mechanisms that allow the
   interconnection of islands of Fibre Channel storage area networks
   over IP-based networks to form a unified storage area network in a
   single Fibre Channel fabric.  FCIP relies on IP-based network
   services to provide the connectivity between the storage area network
   islands over local area networks, metropolitan area networks, or wide
   area networks.

Table Of Contents

   1.  Purpose, Motivation, and Objectives. . . . . . . . . . . . . .  3
   2.  Relationship to Fibre Channel Standards. . . . . . . . . . . .  4
       2.1.  Relevant Fibre Channel Standards . . . . . . . . . . . .  4
       2.2.  This Specification and Fibre Channel Standards . . . . .  5
   3.  Terminology. . . . . . . . . . . . . . . . . . . . . . . . . .  5
   4.  Protocol Summary . . . . . . . . . . . . . . . . . . . . . . .  7
   5.  The FCIP Model . . . . . . . . . . . . . . . . . . . . . . . .  9
       5.1.  FCIP Protocol Model. . . . . . . . . . . . . . . . . . .  9
       5.2.  FCIP Link. . . . . . . . . . . . . . . . . . . . . . . . 10
       5.3.  FC Entity. . . . . . . . . . . . . . . . . . . . . . . . 11
       5.4.  FCIP Entity. . . . . . . . . . . . . . . . . . . . . . . 12
       5.5.  FCIP Link Endpoint (FCIP_LEP). . . . . . . . . . . . . . 13
       5.6.  FCIP Data Engine (FCIP_DE) . . . . . . . . . . . . . . . 14
             5.6.1.  FCIP Encapsulation of FC Frames. . . . . . . . . 16
             5.6.2.  FCIP Data Engine Error Detection and Recovery. . 19
   6.  Checking FC Frame Transit Times in the IP Network. . . . . . . 22

Rajagopal, et al.           Standards Track                     [Page 1]
RFC 3821                          FCIP                         July 2004

   7.  The FCIP Special Frame (FSF) . . . . . . . . . . . . . . . . . 23
       7.1.  FCIP Special Frame Format. . . . . . . . . . . . . . . . 23
       7.2.  Overview of FSF Usage in Connection Establishment. . . . 26
   8.  TCP Connection Management. . . . . . . . . . . . . . . . . . . 28
       8.1.  TCP Connection Establishment . . . . . . . . . . . . . . 28
             8.1.1.  Connection Establishment Model . . . . . . . . . 28
             8.1.2.  Creating New TCP Connections . . . . . . . . . . 29
             8.1.3.  Processing Incoming TCP Connect Requests . . . . 32
             8.1.4.  Simultaneous Connection Establishment. . . . . . 36
       8.2.  Closing TCP Connections. . . . . . . . . . . . . . . . . 36
       8.3.  TCP Connection Parameters. . . . . . . . . . . . . . . . 36
             8.3.1.  TCP Selective Acknowledgement Option . . . . . . 36
             8.3.2.  TCP Window Scale Option. . . . . . . . . . . . . 36
             8.3.3.  Protection Against Sequence Number Wrap. . . . . 37
             8.3.4.  TCP_NODELAY Option . . . . . . . . . . . . . . . 37
       8.4.  TCP Connection Considerations. . . . . . . . . . . . . . 37
       8.5.  Flow Control Mapping between TCP and FC. . . . . . . . . 37
   9.  Security . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
       9.1.  Threat Models. . . . . . . . . . . . . . . . . . . . . . 38
       9.2.  FC Fabric and IP Network Deployment Models . . . . . . . 40
       9.3.  FCIP Security Components . . . . . . . . . . . . . . . . 40
             9.3.1.  IPsec ESP Authentication and Confidentiality . . 40
             9.3.2.  Key Management . . . . . . . . . . . . . . . . . 41
             9.3.3.  ESP Replay Protection and Rekeying Issues. . . . 43
       9.4.  Secure FCIP Link Operation . . . . . . . . . . . . . . . 44
             9.4.1.  FCIP Link Initialization Steps . . . . . . . . . 44
             9.4.2.  TCP Connection Security Associations (SAs) . . . 44
             9.4.3.  Handling Data Integrity and Confidentiality
                     Violations . . . . . . . . . . . . . . . . . . . 45
   10. Performance. . . . . . . . . . . . . . . . . . . . . . . . . . 45
       10.1. Performance Considerations . . . . . . . . . . . . . . . 45
       10.2. IP Quality of Service (QoS) Support. . . . . . . . . . . 46
Show full document text