RFC 3980: T11 Network Address Authority (NAA) Naming Format for iSCSI Node Names
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7143.
Current document in this lineage: RFC 7143 — Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)
In plain English — editorial summary, not part of the RFC
Internet Small Computer Systems Interface (iSCSI) is a SCSI transport protocol that maps the SCSI family of protocols onto TCP/IP. This document defines an additional iSCSI node name type format to enable use of the "Network Address Authority" (NAA) worldwide naming format defined by the InterNational Committee for Information Technology Standards (INCITS) T11 - Fibre Channel (FC) protocols and used by Serial Attached SCSI (SAS). This document updates RFC 3720. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3980
- Published
- February 2005
- Authors
- M. Krueger; M. Chadalapaka; R. Elliott
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 8
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
Read the full history of Internet Small Computer System Interface (iSCSI) Protocol (Consolidated) →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3783Small Computer Systems Interface (SCSI) Command Ordering Considerations with iSCSICurrent
May 2004
- RFC 3722String Profile for Internet Small Computer Systems Interface (iSCSI) NamesCurrent
April 2004
- RFC 5047DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI)Updated
October 2007
- RFC 3989Middlebox Communications (MIDCOM) Protocol SemanticsObsoleted
February 2005
- RFC 4008Definitions of Managed Objects for Network Address Translators (NAT)Obsoleted
March 2005
- RFC 4018Finding Internet Small Computer Systems Interface (iSCSI) Targets and Name Servers by Using Service Location Protocol version 2 (SLPv2)Updated
May 2005
- RFC 4019RObust Header Compression (ROHC): Profiles for User Datagram Protocol (UDP) LiteUpdated
April 2005
- RFC 3941Negative-Acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Building BlocksObsoleted
November 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?