Correction: RFC 5047 NOT moved to Historic -- Re: Moved to Historic: RFC 5047 on DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI)

RFC Editor <rfc-editor@rfc-editor.org> Thu, 26 March 2020 03:46 UTC

Return-Path: <rfc-ed@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DB383A0DB4 for <ietf-announce@ietfa.amsl.com>; Wed, 25 Mar 2020 20:46:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 bR_92A_EAGtm for <ietf-announce@ietfa.amsl.com>; Wed, 25 Mar 2020 20:46:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB8E73A0DAF for <ietf-announce@ietf.org>; Wed, 25 Mar 2020 20:46:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 6000) id D72ECF406F7; Wed, 25 Mar 2020 20:46:36 -0700 (PDT)
Date: Wed, 25 Mar 2020 20:46:36 -0700
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Cc: RFC Editor <rfc-editor@rfc-editor.org>
Subject: Correction: RFC 5047 NOT moved to Historic -- Re: Moved to Historic: RFC 5047 on DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI)
Message-ID: <20200326034636.GA5356@rfc-editor.org>
References: <20200326014151.F4127F40716@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200326014151.F4127F40716@rfc-editor.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/QszuzyEiO_6XuTPbzsOfTJmsqqc>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2020 03:46:50 -0000

Greetings all,

Please disregard this message - this document has not been moved to
Historic.  

Apoloiges for any confusion.

RFC Editor/sg

On Wed, Mar 25, 2020 at 06:41:51PM -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
>