RE: [Ips] AD review of draft-ietf-ips-iscsi-nodearch-key-02

Julian Satran <Julian_Satran@il.ibm.com> Mon, 16 October 2006 15:19 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZUFb-0000Al-9Z; Mon, 16 Oct 2006 11:19:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZUFa-0000Ag-Qs for ips@ietf.org; Mon, 16 Oct 2006 11:19:34 -0400
Received: from mtagate5.de.ibm.com ([195.212.29.154]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZUFV-0001WQ-Su for ips@ietf.org; Mon, 16 Oct 2006 11:19:34 -0400
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate5.de.ibm.com (8.13.8/8.13.8) with ESMTP id k9GFJSHe055228 for <ips@ietf.org>; Mon, 16 Oct 2006 15:19:28 GMT
Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228]) by d12nrmr1607.megacenter.de.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id k9GFLva92883596 for <ips@ietf.org>; Mon, 16 Oct 2006 17:21:57 +0200
Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k9GFJSm9008457 for <ips@ietf.org>; Mon, 16 Oct 2006 17:19:28 +0200
Received: from d12mc102.megacenter.de.ibm.com (d12mc102.megacenter.de.ibm.com [9.149.167.114]) by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k9GFJSCW008454; Mon, 16 Oct 2006 17:19:28 +0200
In-Reply-To: <F222151D3323874393F83102D614E05502B67549@CORPUSMX20A.corp.emc.com>
To: Black_David@emc.com
MIME-Version: 1.0
Subject: RE: [Ips] AD review of draft-ietf-ips-iscsi-nodearch-key-02
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
From: Julian Satran <Julian_Satran@il.ibm.com>
Message-ID: <OF1723ED7D.95189F00-ONC2257209.00542357-C2257209.00542D8C@il.ibm.com>
Date: Mon, 16 Oct 2006 17:21:55 +0200
X-MIMETrack: Serialize by Router on D12MC102/12/M/IBM(Release 7.0.1HF269 | June 22, 2006) at 16/10/2006 17:21:57, Serialize complete at 16/10/2006 17:21:57
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4c358d334afcd91b425d436ca5722f22
Cc: lars.eggert@netlab.nec.de, ips@ietf.org
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>
Content-Type: multipart/mixed; boundary="===============1205924481=="
Errors-To: ips-bounces@ietf.org

works for me - julo



Black_David@emc.com 
16/10/06 16:45

To
Julian Satran/Haifa/IBM@IBMIL, <lars.eggert@netlab.nec.de>
cc
<ips@ietf.org>
Subject
RE: [Ips] AD review of draft-ietf-ips-iscsi-nodearch-key-02






Julian and Lars,
 
We could get clever here.  The crucial language in RFC 3720 says:
 
                 For IANA registered keys the string following X# must be
registered
                 with IANA and the use of the key MUST be described by an
informational RFC.

and there's similar language for Y# digest formats and Z# authentication
methods.

Given the level of review this draft has received (not only on the list,
but also in Montreal, I put crucial pieces of this draft's text on the
projector for word-by-word review), I don't think there would be any
problem with this draft becoming a proposed standard RFC, and it could
then update RFC 3720 to change "informational RFC" to "informational,
experimental or standards track RFC" in all three places.

I would want to issue a WG Last Call on these changes (publish
nodearch-key as proposed, standard, update RFC 3720 to allow
experimental
and standards-track RFCs for X# keys, Y# digests, and Z# authentication
methods), so that there is an adequate opportunity for anyone to object.

Comments?

Thanks,
--David (ips WG chair)
----------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------


________________________________

                 From: Julian Satran [mailto:Julian_Satran@il.ibm.com] 
                 Sent: Monday, October 16, 2006 4:04 AM
                 To: Lars Eggert
                 Cc: ips@ietf.org
                 Subject: Re: [Ips] AD review of
draft-ietf-ips-iscsi-nodearch-key-02
 
 

                 Lars, 
 
                 Yes we wanted new keys to be publicly documented without
requiring authors to go to a strict review (that might be hard to get in
several years). 
                 In retrospect we should have said "at least 
informational"
although there is (at least in theory) an ordering between RFC
"classes". 
 
                 Julo 
 
 
 
                 Lars Eggert <lars.eggert@netlab.nec.de> 

                 16/10/06 03:40 

 
                                 To
                                 ips@ietf.org 
                                 cc
 
                                 Subject
                                 Re: [Ips] AD review of
draft-ietf-ips-iscsi-nodearch-key-02

 




                 On Oct 16, 2006, at 10:28, Lars Eggert wrote:
                 >   Finally - why is this going for Informational and not 
PS? PS
seems
                 >   appropriate.
 
                 To be precise, I saw David's note on this from the 
document
writeup 
                 ("This document is being published as Informational 
because RFC
3720 
                 indicates that this class of key specification should be
published as 
                 informational.")
 
                 It's unfortunate that 3720 doesn't also allow publication 
at 
                 Standards Track; I wonder what the rationale for this 
was. 
                 Intuitively, this should be OK, because Standards Track
publication 
                 has a higher bar.
 
                 If the WG decides to go for Informational because of 
3720, I'm
OK 
                 with it. It may make sense to add a short note to the
introduction 
                 explaining this.
 
                 Lars
                 -- 
                 Lars Eggert                                     NEC 
Network
Laboratories
 
 
                 _______________________________________________
                 Ips mailing list
                 Ips@ietf.org
                 https://www1.ietf.org/mailman/listinfo/ips
 
 


_______________________________________________
Ips mailing list
Ips@ietf.org
https://www1.ietf.org/mailman/listinfo/ips