metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 4850: Declarative Public Extension Key for Internet Small Computer Systems Interface (iSCSI) Node Architecture

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

The Internet Small Computer Systems Interface (iSCSI) protocol, described in RFC 3720, allows for extension items to the protocol in the form of Private or Public Extension Keys. This document describes a Public Extension Key for the purpose of enhancing iSCSI supportability. The key accomplishes this objective by allowing iSCSI nodes to communicate architecture details during the iSCSI login sequence. The receiving node can then use this information for enhanced logging and support. This document updates RFC 3720 to allow iSCSI extension items to be defined by standards track RFCs and experimental RFCs in addition to informational RFCs. [STANDARDS-TRACK]

Document record

Document ID
RFC4850
Published
April 2007
Authors
D. Wysochanski
Status
PROPOSED STANDARD
Stream
IETF
Area
tsv
Pages
9
Also known as
—
Obsoleted by:
RFC 7143
Updates:
RFC 3720

Topics

Standards lineage

This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.

  1. RFC 3720 (2004)
  2. RFC 3980 (2005)
  3. RFC 4850 (2007)
  4. RFC 5048 (2007)
  5. RFC 7143 (2014) ✓

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.

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?

canonical URL: /rfc/4850-declarative-public-extension-key-for-internet-small-computer-systems-interface-i