RE: [lemonade] Gen-ART review of draft-ietf-lemonade-convert-17.txt

Black_David@emc.com Thu, 17 April 2008 15:10 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CCAB528C564; Thu, 17 Apr 2008 08:10:57 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82CDA3A68D7; Wed, 16 Apr 2008 12:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.608
X-Spam-Level:
X-Spam-Status: No, score=-4.608 tagged_above=-999 required=5 tests=[AWL=1.991, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KhA5Yx9imEva; Wed, 16 Apr 2008 12:07:01 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id CB1E03A6C9D; Wed, 16 Apr 2008 12:07:00 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id m3GJ7ZGw016152; Wed, 16 Apr 2008 15:07:35 -0400 (EDT)
Received: from mailhub.lss.emc.com (uraeus.lss.emc.com [10.254.144.14]) by hop04-l1d11-si01.isus.emc.com (Tablus Interceptor); Wed, 16 Apr 2008 15:07:35 -0400
Received: from corpussmtp4.corp.emc.com (corpussmtp4.corp.emc.com [10.254.64.54]) by mailhub.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id m3GJ7Qt7013448; Wed, 16 Apr 2008 15:07:32 -0400 (EDT)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.11]) by corpussmtp4.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 Apr 2008 15:07:27 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [lemonade] Gen-ART review of draft-ietf-lemonade-convert-17.txt
Date: Wed, 16 Apr 2008 15:07:27 -0400
Message-ID: <8CC6CEAB44F131478D3A7B429ECACD91016F5FEB@CORPUSMX20A.corp.emc.com>
In-Reply-To: <4806484B.6080602@isode.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [lemonade] Gen-ART review of draft-ietf-lemonade-convert-17.txt
Thread-Index: Acif8YyhMIyNrfyYQBWey6m7HEQU9wAAmQvg
References: <8CC6CEAB44F131478D3A7B429ECACD91016F5FB0@CORPUSMX20A.corp.emc.com> <4806484B.6080602@isode.com>
To: alexey.melnikov@isode.com
X-OriginalArrivalTime: 16 Apr 2008 19:07:27.0964 (UTC) FILETIME=[1CD5D9C0:01C89FF5]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.8.30.51425
X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -3, NO_REAL_NAME 0, __C230066_P5 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Tablus-Inspected: yes
X-Tablus-Classifications: public
X-Tablus-Action: allow
X-Mailman-Approved-At: Thu, 17 Apr 2008 08:10:56 -0700
Cc: ietf@ietf.org, lemonade@ietf.org, peter.coates@Sun.COM, Black_David@emc.com, chris.newman@Sun.COM, gen-art@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Alexey,

Thank you for your prompt response.

Keeping the To: and Subject: lines in the IANA registration
in Section 11.1 is fine since they are in RFC 2506, and
RFC 2506 is noted in that section as having established
the registry.  Please consider adding an informative
reference to RFC 2506, but this is not essential.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
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
----------------------------------------------------

> Black_David@emc.com wrote:
> 
> >I have been selected as the General Area Review Team (Gen-ART) 
> >reviewer for this draft (for background on Gen-ART, please see 
> >http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
> >
> >Please resolve these comments along with any other Last Call comments

> >you may receive. 
> >
> >Document: draft-ietf-lemonade-convert-17.txt
> >Reviewer: David L. Black
> >Review Date: 15 April 2008
> >IETF LC End Date: 16 April 2008
> >  
> >
> Hi David,
> Thank you for your review.
> 
> >Summary: 
> >This draft is basically ready for publication, but has nits that
> >should be fixed before publication.
> >
> >Comments:
> >This is a generally well-written draft on the CONVERT extension
> >to IMAP.  All of these comments are minor nits.
> >
> >In Section 2, please remove this convention:
> >   [[anchor3: Editorial comments and questions are marked like
this.]]
> >
> Done.
> 
> >p.10 contains a couple of example email addresses.  Please use
> >example.com, example.net or example.org as the domain.
> >
> Somebody else complained about this earlier, so I've already fixed
this 
> in my copy.
> 
> >In Section 11.1 are the To: and Subject: lines needed as part of
> >the IANA registration?  If not, please remove them.
> >  
> >
> They are a part of the IANA template in RFC 2506, so I would rather
keep 
> them
> 
> >In the IANA registration in Section 11.1, please ask IANA to
> >replace RFC XXXX by the RFC number assigned to this draft.
> >  
> >
> Ok.
> 
> >idnits 2.08.05 got confused by the square brackets used in IMAP
> >syntax and reported a number of potential reference problems -
> >there are no actual problems.
> >  
> >
> Indeed.
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf