It took a bit to find it, but there was a Last Call:
https://mailarchive.ietf.org/arch/msg/ietf-announce/lijeNVjkekVJNawP_QfoOJAxqrU
It would probably be useful to put RFC numbers in the Subject: of the
Last Call instead of just the document title.
pr
On 25 Mar 2020, at 21:27, John C Klensin wrote:
I am not questioning the decision to move this document to
Historic, but I don't remember seeing a Last Call announcement
and there does not appear to be anything in the datatracker
about this RFC since its approval and publication in 2007.
My understanding has been that the RFC Editor stopped moving
IETF Stream documents to Historic on its own initiative many
years ago. Was there a Last Call? If this was done as an IESG
executive decision, where is the decision and the motivation for
doing it with this document at this time, documented?
thanks,
john
--On Wednesday, March 25, 2020 18:41 -0700
rfc-editor@xxxxxxxxxxxxxx wrote:
RFC 5047 has been reclassified as Historic.
RFC 5047
Title: DA: Datamover Architecture for the
Internet Small Computer System Interface
(iSCSI) Author: M. Chadalapaka,
J. Hufferd,
J. Satran,
H. Shah
Status: Historic
Stream: IETF
Date: October 2007
Pages: 49
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ips-iwarp-da-05.txt
URL: https://www.rfc-editor.org/info/rfc5047
DOI: 10.17487/RFC5047
The Internet Small Computer System Interface (iSCSI) is a SCSI
transport protocol that maps the SCSI family
of application protocols onto TCP/IP. Datamover Architecture
for iSCSI (DA) defines an abstract model in which the
movement of data between iSCSI end nodes is logically
separated from the rest of the iSCSI protocol in order to
allow iSCSI to adapt to innovations available in new IP
transports. While DA defines the architectural functions
required of the class of Datamover protocols, it does not
define any specific Datamover protocols. Each such Datamover
protocol, defined in a separate document, provides a
reliable transport for all iSCSI PDUs, but actually moves the
data required for certain iSCSI PDUs without involving the
remote iSCSI layer itself. This document begins with an
introduction of a few new abstractions, defines a layered
architecture for iSCSI and Datamover protocols, and then
models the interactions within an iSCSI end node between the
iSCSI layer and the Datamover layer that happen in order to
transparently perform remote data movement within an IP
fabric. It is intended that this definition will help map
iSCSI to generic Remote Direct Memory Access (RDMA)-capable IP
fabrics in the future comprising TCP, the Stream Control
Transmission Protocol (SCTP), and possibly other underlying
network transport layers, such as InfiniBand.
This document is a product of the IP Storage Working Group of
the IETF.
HISTORIC: This memo defines a Historic Document for the
Internet community. It does not specify an Internet standard
of any kind. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist
lists. To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see
https://www.rfc-editor.org/search For downloading RFCs, see
https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to
either the author of the RFC in question, or to
rfc-editor@xxxxxxxxxxxxxx. Unless specifically noted
otherwise on the RFC itself, all RFCs are for unlimited
distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
IETF-Announce mailing list
IETF-Announce@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf-announce
