[Ips] RFC 4850 on Declarative Public Extension Key for Internet Small Computer Systems Interface (iSCSI) Node Architecture
rfc-editor@rfc-editor.org Tue, 17 April 2007 21:10 UTC
Return-path: <ips-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hduwr-0001O4-VW; Tue, 17 Apr 2007 17:10:49 -0400
Received: from ips by megatron.ietf.org with local (Exim 4.43) id 1Hduwq-0001Nw-9H for ips-confirm+ok@megatron.ietf.org; Tue, 17 Apr 2007 17:10:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hduwp-0001No-Vv; Tue, 17 Apr 2007 17:10:47 -0400
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hduwp-0003PT-KC; Tue, 17 Apr 2007 17:10:47 -0400
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l3HLAl0h007712; Tue, 17 Apr 2007 14:10:47 -0700
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l3HLAl1o007711; Tue, 17 Apr 2007 14:10:47 -0700
Date: Tue, 17 Apr 2007 14:10:47 -0700
Message-Id: <200704172110.l3HLAl1o007711@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: ips@ietf.org, rfc-editor@rfc-editor.org
Subject: [Ips] RFC 4850 on Declarative Public Extension Key for Internet Small Computer Systems Interface (iSCSI) Node Architecture
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=subscribe>
Errors-To: ips-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 4850
Title: Declarative Public Extension Key for
Internet Small Computer Systems Interface (iSCSI)
Node Architecture
Author: D. Wysochanski
Status: Standards Track
Date: April 2007
Mailbox: wysochanski@pobox.com
Pages: 9
Characters: 16430
Updates: RFC3720
See-Also:
I-D Tag: draft-ietf-ips-iscsi-nodearch-key-03.txt
URL: http://www.rfc-editor.org/rfc/rfc4850.txt
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]
This document is a product of the IP Storage
Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: 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.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
Ips mailing list
Ips@ietf.org
https://www1.ietf.org/mailman/listinfo/ips