互联网小型计算机系统接口(iSCSI)协议规范

需积分: 10 38 浏览量更新于2024-07-17 收藏 825KB PDF 举报

"rfc7143-iscsi-2014-Consolidated.pdf" 本文档描述了基于TCP的SCSI传输协议——互联网小型计算机系统接口（iSCSI）协议，旨在与标准化的SCSI架构模型（SAM-2）完全兼容。RFC 7143是该领域的标准文档，它综合了之前多个版本的RFC，包括RFC 3720、3721、3980和4850，并对这些规范进行了更新和澄清。 iSCSI是一种网络存储协议，它允许通过IP网络进行SCSI命令的传输，从而实现数据的存储和检索。这个协议的建立使得远程存储设备能够像本地直接连接的SCSI设备一样工作。RFC 3720首次定义了iSCSI协议，包括其基本框架、操作流程和安全性方面。 RFC 3721详细介绍了iSCSI的命名示例和发现技术，这对于设备的识别和连接至关重要。命名机制允许iSCSI目标（如存储设备）和发起器（如服务器）在网络中被寻址和发现。 RFC 3980扩展了iSCSI协议的命名格式，增加了更多的灵活性，使得设备可以使用不同的方式来标识自身。这种扩展提高了iSCSI在复杂网络环境中的适应性。 RFC 4850引入了一个新的公共扩展密钥到iSCSI协议中，这可能涉及到安全性和功能性的增强，使得协议能够支持更多元化的应用需求。 RFC 5048对原始iSCSI协议提供了进一步的澄清、改进和修正，确保协议的实施更加清晰和稳定。这可能包括错误修复、性能优化或对某些模糊概念的明确说明。 RFC 7143通过合并这些RFC，形成了一个综合的规范，同时对整合后的规范进行了必要的更新。此文档还更新了RFC 3721中的部分文本，以确保所有相关描述的一致性和准确性。 iSCSI协议是现代数据中心和云存储环境中不可或缺的一部分，它简化了存储网络的管理，促进了存储资源的共享和利用。通过持续的标准化过程，iSCSI得以不断优化和完善，以满足不断增长的存储需求和网络环境的复杂性。

RFC 7143

iSCSI (Consolidated) April 2014

- Network Portal: The Network Portal is a component of a Network

Entity that has a TCP/IP network address and that may be used by an

iSCSI node within that Network Entity for the connection(s) within

one of its iSCSI sessions. A Network Portal in an initiator is

identified by its IP address. A Network Portal in a target is

identified by its IP address and its listening TCP port.

- Originator: In a negotiation or exchange, the originator is the

party that initiates the negotiation or exchange.

- PDU (Protocol Data Unit): The initiator and target divide their

communications into messages. The term "iSCSI Protocol Data Unit"

(iSCSI PDU) is used for these messages.

- Portal Groups: iSCSI supports multiple connections within the same

session; some implementations will have the ability to combine

connections in a session across multiple Network Portals. A portal

group defines a set of Network Portals within an iSCSI Network

Entity that collectively supports the capability of coordinating a

session with connections spanning these portals. Not all Network

Portals within a portal group need participate in every session

connected through that portal group. One or more portal groups may

provide access to an iSCSI node. Each Network Portal, as utilized

by a given iSCSI node, belongs to exactly one portal group within

that node.

- Portal Group Tag: This 16-bit quantity identifies a portal group

within an iSCSI node. All Network Portals with the same Portal

Group Tag in the context of a given iSCSI node are in the same

portal group.

- Recovery R2T: A recovery R2T is an R2T generated by a target upon

detecting the loss of one or more Data-Out PDUs through one of the

following means: a digest error, a sequence error, or a sequence

reception timeout. A recovery R2T carries the next unused R2TSN

but requests all or part of the data burst that an earlier R2T

(with a lower R2TSN) had already requested.

- Responder: In a negotiation or exchange, the responder is the party

that responds to the originator of the negotiation or exchange.

- SAS: The Serial Attached SCSI (SAS) standard contains both a

physical layer compatible with Serial ATA, and protocols for

transporting SCSI commands to SAS devices and ATA commands to SATA

devices [

SAS] [SPL].

Chadalapaka, et al. Standards Track [Page 16]

RFC 7143

iSCSI (Consolidated) April 2014

- SCSI Device: This is the SAM-2 term for an entity that contains one

or more SCSI ports that are connected to a service delivery

subsystem and supports a SCSI application protocol. For example, a

SCSI initiator device contains one or more SCSI initiator ports and

zero or more application clients. A target device contains one or

more SCSI target ports and one or more device servers and

associated LUs. For iSCSI, the SCSI device is the component within

an iSCSI node that provides the SCSI functionality. As such, there

can be at most one SCSI device within a given iSCSI node. Access

to the SCSI device can only be achieved in an iSCSI Normal

operational session. The SCSI device name is defined to be the

iSCSI name of the node.

- SCSI Layer: This builds/receives SCSI CDBs (Command Descriptor

Blocks) and relays/receives them with the remaining Execute Command

[

SAM2] parameters to/from the iSCSI Layer.

- Session: The group of TCP connections that link an initiator with a

target form a session (loosely equivalent to a SCSI I_T nexus).

TCP connections can be added and removed from a session. Across

all connections within a session, an initiator sees one and the

same target.

- SCSI Port: This is the SAM-2 term for an entity in a SCSI device

that provides the SCSI functionality to interface with a service

delivery subsystem. For iSCSI, the definitions of the SCSI

initiator port and the SCSI target port are different.

- SCSI Initiator Port: This maps to the endpoint of an iSCSI Normal

operational session. An iSCSI Normal operational session is

negotiated through the login process between an iSCSI initiator

node and an iSCSI target node. At successful completion of this

process, a SCSI initiator port is created within the SCSI initiator

device. The SCSI initiator port name and SCSI initiator port

identifier are both defined to be the iSCSI Initiator Name together

with (a) a label that identifies it as an initiator port

name/identifier and (b) the ISID portion of the session identifier.

- SCSI Port Name: This is a name consisting of UTF-8 [

RFC3629]

encoding of Unicode [

UNICODE] characters and includes the iSCSI

name + ’i’ or ’t’ + ISID or Target Portal Group Tag.

- SCSI-Presented Data Transfer Length (SPDTL): SPDTL is the aggregate

data length of the data that the SCSI layer logically "presents" to

the iSCSI layer for a Data-In or Data-Out transfer in the context

of a SCSI task. For a bidirectional task, there are two SPDTL

values -- one for Data-In and one for Data-Out. Note that the

notion of "presenting" includes immediate data per the data

Chadalapaka, et al. Standards Track [Page 17]

RFC 7143

iSCSI (Consolidated) April 2014

transfer model in [

SAM2] and excludes overlapping data transfers,

if any, requested by the SCSI layer.

- SCSI Target Port: This maps to an iSCSI target portal group.

- SCSI Target Port Name and SCSI Target Port Identifier: These are

both defined to be the iSCSI Target Name together with (a) a label

that identifies it as a target port name/identifier and (b) the

Target Portal Group Tag.

- SSID (Session ID): A session between an iSCSI initiator and an

iSCSI target is defined by a session ID that is a tuple composed of

an initiator part (ISID) and a target part (Target Portal Group

Tag). The ISID is explicitly specified by the initiator at session

establishment. The Target Portal Group Tag is implied by the

initiator through the selection of the TCP endpoint at connection

establishment. The TargetPortalGroupTag key must also be returned

by the target as a confirmation during connection establishment.

- T10: T10 is a technical committee within INCITS that develops

standards and technical reports on I/O interfaces, particularly the

series of SCSI (Small Computer System Interface) standards. See

http://www.t10.org>.

- T11: T11 is a technical committee within INCITS responsible for

standards development in the areas of Intelligent Peripheral

Interface (IPI), High-Performance Parallel Interface (HIPPI), and

Fibre Channel (FC). See <

http://www.t11.org>.

- Target Portal Group Tag: This is a numerical identifier (16-bit)

for an iSCSI target portal group.

- Target Transfer Tag (TTT): The TTT is an iSCSI protocol field used

in a few iSCSI PDUs (e.g., R2T, NOP-In) that is always sent from

the target to the initiator first and then quoted as a reference in

initiator-sent PDUs back to the target relating to the same

task/exchange. Therefore, the TTT effectively acts as an opaque

handle to an existing task/exchange to help the target associate

the incoming PDUs from the initiator to the proper execution

context.

- Third-party: This term is used in this document as a qualifier to

nexus objects (I_T or I_T_L) and iSCSI sessions, to indicate that

these objects and sessions reap the side effects of actions that

take place in the context of a separate iSCSI session. One example

of a third-party session is an iSCSI session discovering that its

I_T_L nexus to a LU got reset due to a LU reset operation

orchestrated via a separate I_T nexus.

Chadalapaka, et al. Standards Track [Page 18]

剩余294页未读，继续阅读

starmlk

粉丝: 7
资源: 10

互联网小型计算机系统接口(iSCSI)协议规范

RFC 3544 - IP Header Compression over PPP.pdf

rfc3721-iscsi-2004-Naming and Discovery.pdf

keytool -export -rfc -keystore upload-keystore.jks -alias upload -file upload_certificate.pem

rfc1305-1992

rfc viewer

rfc全部文档离线下载rfc1-rfc8505

rfc3261中文版 pdf 下载

30[单选题]下列哪个是网络标准化组织?-|||-○ A.ISO-|||-○ B.IEEE-|||-○ C.IETF-|||-○ D.W3C

The valid characters are defined in RFC 7230 and RFC 3986

最新资源