Re: Moved to Historic: RFC 5047 on DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI)
Pete Resnick <resnick@episteme.net> Thu, 26 March 2020 02:50 UTC
Return-Path: <resnick@episteme.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A072E3A0816 for <ietf@ietfa.amsl.com>; Wed, 25 Mar 2020 19:50:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pSm1Ka9geXCJ for <ietf@ietfa.amsl.com>; Wed, 25 Mar 2020 19:50:58 -0700 (PDT)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35CF03A0140 for <ietf@ietf.org>; Wed, 25 Mar 2020 19:50:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id 3C39CA52FF62; Wed, 25 Mar 2020 21:50:54 -0500 (CDT)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1M6_u6ZUCkSG; Wed, 25 Mar 2020 21:50:52 -0500 (CDT)
Received: from [172.16.1.18] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id 8C5FDA52FF5B; Wed, 25 Mar 2020 21:50:52 -0500 (CDT)
From: Pete Resnick <resnick@episteme.net>
To: John C Klensin <john-ietf@jck.com>
Cc: rfc-editor@rfc-editor.org, ietf@ietf.org
Subject: Re: Moved to Historic: RFC 5047 on DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI)
Date: Wed, 25 Mar 2020 21:50:52 -0500
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <F078EAE9-109E-4FE9-A4A2-054D716EA2A6@episteme.net>
In-Reply-To: <658B282586A1D51694DB1AA0@PSB>
References: <20200326014151.F4127F40716@rfc-editor.org> <658B282586A1D51694DB1AA0@PSB>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bF48BuSZSLErD7IIYnBaQjrgb4g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2020 02:51:00 -0000
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@rfc-editor.org 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@rfc-editor.org. 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@ietf.org >> https://www.ietf.org/mailman/listinfo/ietf-announce
- Re: Moved to Historic: RFC 5047 on DA: Datamover … John C Klensin
- Re: Moved to Historic: RFC 5047 on DA: Datamover … Pete Resnick
- Re: Moved to Historic: RFC 5047 on DA: Datamover … Brian E Carpenter
- Re: Moved to Historic: RFC 5047 on DA: Datamover … Pete Resnick
- Re: Moved to Historic: RFC 5047 on DA: Datamover … John C Klensin
- Re: Moved to Historic: RFC 5047 on DA: Datamover … S Moonesamy