[Gen-art] RE: Gen-ART review of draft-ietf-ips-iscsi-nodearch-key-03

Black_David@emc.com Thu, 07 December 2006 23:34 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsSlF-00077E-Gz; Thu, 07 Dec 2006 18:34:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsSlD-000779-Tk for gen-art@ietf.org; Thu, 07 Dec 2006 18:34:39 -0500
Received: from mexforward.lss.emc.com ([128.222.32.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsSlA-00047b-Gk for gen-art@ietf.org; Thu, 07 Dec 2006 18:34:39 -0500
Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.11]) by mexforward.lss.emc.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id kB7NYWKi006178; Thu, 7 Dec 2006 18:34:32 -0500 (EST)
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id kB7NYEHW021520; Thu, 7 Dec 2006 18:34:30 -0500 (EST)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.13]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 7 Dec 2006 18:34:16 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 07 Dec 2006 18:33:25 -0500
Message-ID: <F222151D3323874393F83102D614E055068B89A0@CORPUSMX20A.corp.emc.com>
In-Reply-To: <4577E323.9040802@alvestrand.no>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Gen-ART review of draft-ietf-ips-iscsi-nodearch-key-03
Thread-Index: AccZ5Li+okFjw25TQTa2T/ZGpULjGQAcjxpQ
To: harald@alvestrand.no, gen-art@ietf.org, wysochanski@pobox.com, lars.eggert@netlab.nec.de
X-OriginalArrivalTime: 07 Dec 2006 23:34:16.0987 (UTC) FILETIME=[3610E6B0:01C71A58]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2006.12.7.151432
X-PerlMx-Spam: Gauge=, SPAM=2%, Reason='EMC_FROM_0+ -2, NO_REAL_NAME 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: Black_David@emc.com
Subject: [Gen-art] RE: Gen-ART review of draft-ietf-ips-iscsi-nodearch-key-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Errors-To: gen-art-bounces@ietf.org

Harald,

Many thanks for reviewing this draft.

> This document does 2 things:
> 
> - Register an extension to pass implementation identities around
> - Change the registration requirement for extensions to allow 
> Experimental extensions to be registered

It also instructs IANA to correct some registry problems.

> 1) I read RFC 3720 section 13.5.2 as saying that publication 
> of extensions as standards-track is allowed, even though the 
> wording is quite convoluted. So the implication of the 
> language in section 5 that it was previously restricted to 
> informational only seems unwarranted.

The WG and the editor of the draft that became RFC 3270 do not
share your view of the convoluted wording, and regard this draft
as making a change to the process requirements in RFC 3270.
At a minimum, this draft unambiguously states what is allowed.

> 2) It would be good if section 5 of this draft pointed 
> specifically at section 13.5.2 of RFC 3720 as the section to 
> be updated, and provided specific language to be read as 
> "this section is now replaced by". I *think* the text only 
> means that the words "as an informational RFC" are changed to 
> "as an informational or experimental RFC, as appropriate", 
> but it would be nice to be 100% certain that this is the 
> intended effect, and that no other section of RFC 3720 needs 
> changing (my scan of 3720 might have overlooked something).

I believe your thinking is correct, and I will supply the Area
Director (Lars) with an appropriate RFC Editor Note.

Many thanks to the Gen-ART process and the people who make it
happen, as this draft would have been far less likely to receive
this caliber of IETF Last Call review in Gen-ART's absence.

Thanks,
--David (ips WG chair & shepherd for this draft)

> -----Original Message-----
> From: Harald Alvestrand [mailto:harald@alvestrand.no] 
> Sent: Thursday, December 07, 2006 4:47 AM
> To: gen-art@ietf.org; wysochanski@pobox.com; Lars Eggert; Black, David
> Subject: Gen-ART review of draft-ietf-ips-iscsi-nodearch-key-03
> 
> Document: draft-ietf-ips-iscsi-nodearch-key-03
> Reviewer: Harald Tveit Alvestrand
> Review Date: 2006-12-07
> IETF LC End Date: 2006-12-11
> IESG Telechat date: (if known)
> 
> Summary: Ready to go. Small grumbles.
> 
> Comments:
> 
> This document does 2 things:
> 
> - Register an extension to pass implementation identities around
> - Change the registration requirement for extensions to allow 
> Experimental extensions to be registered
> 
> The first point is adequately described, with more than 
> enough caveats about what to do and not to do.
> 
> The last one seems quite reasonable, given that Informational 
> registration was already allowed. I'm not completely happy 
> about the lumping of that one into this document, but that's 
> the call of the WG and AD.
> 
> Two points, which may be addressed if the document is 
> revisited for other reasons:
> 
> 1) I read RFC 3720 section 13.5.2 as saying that publication 
> of extensions as standards-track is allowed, even though the 
> wording is quite convoluted. So the implication of the 
> language in section 5 that it was previously restricted to 
> informational only seems unwarranted.
> 
> 2) It would be good if section 5 of this draft pointed 
> specifically at section 13.5.2 of RFC 3720 as the section to 
> be updated, and provided specific language to be read as 
> "this section is now replaced by". I *think* the text only 
> means that the words "as an informational RFC" are changed to 
> "as an informational or experimental RFC, as appropriate", 
> but it would be nice to be 100% certain that this is the 
> intended effect, and that no other section of RFC 3720 needs 
> changing (my scan of 3720 might have overlooked something).
> 
> http://tools.ietf.org/wg/ips/draft-ietf-ips-iscsi-nodearch-key
/ claims that there are no nits. Good.
> 
> 
> 

_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www1.ietf.org/mailman/listinfo/gen-art