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

S Moonesamy <sm+ietf@elandsys.com> Thu, 26 March 2020 06:00 UTC

Return-Path: <sm@elandsys.com>
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 D3F603A0986 for <ietf@ietfa.amsl.com>; Wed, 25 Mar 2020 23:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
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 mCkS7ZZb36QU for <ietf@ietfa.amsl.com>; Wed, 25 Mar 2020 23:00:34 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 5DB913A0941 for <ietf@ietf.org>; Wed, 25 Mar 2020 23:00:26 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.204.210]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 02Q60B7K002756 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 25 Mar 2020 23:00:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1585202425; x=1585288825; i=@elandsys.com; bh=/Dnca4P1xscLDCO/qBwxdxUEirDz2R/MbpvAjUOJrRE=; h=Date:To:From:Subject:In-Reply-To:References; b=49TuIqH+7U8ZTxLfZ/nm21f92IRKwC/m2QFJGXwRxSrMx/+3bE7vmcY/NrTBLNabU uIXdDxbzEA2KN4EZt4BwVynJ378dk1Arg6IwrZ6+0ihbg5/p1gfJ+XD+4KnunSlJHW BWSjA2av9fdDqOoz5JsrYZkNI1pUg9/BYGVqnnpo=
Message-Id: <6.2.5.6.2.20200325222516.0b614be0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 25 Mar 2020 22:55:47 -0700
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Moved to Historic: RFC 5047 on DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI)
In-Reply-To: <615BBDA9E3C49FF433657D7A@PSB>
References: <20200326014151.F4127F40716@rfc-editor.org> <658B282586A1D51694DB1AA0@PSB> <F078EAE9-109E-4FE9-A4A2-054D716EA2A6@episteme.net> <f0dea95c-6e64-fc1b-499a-7f1a3bfc5955@gmail.com> <615BBDA9E3C49FF433657D7A@PSB>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yqJvVUlG0eVkv7DTPsgIhXGJfEs>
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 06:00:41 -0000

Hi John,
At 09:08 PM 25-03-2020, John C Klensin wrote:
>I assume it is due to all of the trauma around xml2rfc v3, but,
>after reviewing the datatracker information, I'm a bit surprised
>that it took the RFC Editor between early November and today to
>post their announcement (if that announcement was needed at
>all).  Or perhaps the wrong announcement was sent out as well as
>the wrong RFC number and title and what really should have gone
>out was the RFC publication announcement for
>draft-ietf-dnsop-obsolete-dlv .

Yesterday, there were some comments about whether there was any 
announcement about retiring DNSSEC Lookaside Validation (DLV).  From 
what I remember, that topic was discussed some time ago.  I looked up 
the relevant RFCs and the datatracker to find out whether there was 
any information there.  The reclassification was not reflected in the 
RFC Editor records.  I posted a message to DNSOP about the matter and 
copied it to the RSE.  I assume that it explains the following: 
https://mailarchive.ietf.org/arch/msg/ietf-announce/v80rDtxfHBPu7nvCLvxl9ym5ITg/

The RFC Editor lists the date of the status change for RFC 5074 as 
September 2019.  However, the approval announcement was sent out in 
November 2019.

Regards,
S. Moonesamy