Re: last call for 'MDN profile for IMAP (BCP)'

Tony Hansen <tony@att.com> Wed, 27 November 2002 19:14 UTC

Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id gARJER909328 for ietf-imapext-bks; Wed, 27 Nov 2002 11:14:27 -0800 (PST)
Received: from kcmso2.proxy.att.com (kcmso2.att.com [192.128.134.71]) by above.proper.com (8.11.6/8.11.3) with ESMTP id gARJEPg09324 for <ietf-imapext@imc.org>; Wed, 27 Nov 2002 11:14:25 -0800 (PST)
Received: from maillennium.att.com ([135.25.114.99]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id gARJEIA8000587 for <ietf-imapext@imc.org>; Wed, 27 Nov 2002 13:14:19 -0600 (CST)
Received: from att.com (<unknown.domain>[135.210.32.31]) by maillennium.att.com (mailgw1) with SMTP id <20021127191352gw1006aljte> (Authid: tony); Wed, 27 Nov 2002 19:13:52 +0000
Message-ID: <3DE51917.2030401@att.com>
Date: Wed, 27 Nov 2002 14:12:23 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: imap-ext IETF <ietf-imapext@imc.org>
Subject: Re: last call for 'MDN profile for IMAP (BCP)'
References: <A018F79E-0218-11D7-B05E-0003934A5A7E@inet.it> <01KPCV4MFESQ004VR6@mauve.mrochek.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

As for the issue raised there in section 0, I'd be happy with changing 
the MUST NOT to a SHOULD NOT.

	Tony

ned+imapext@INNOSOFT.COM wrote:
> 
>> While reading the draft draft-melnikov-imap-mdn-04.txt I wondered
>> about the section '0. To do list and open issues'.
>> There is still 1 item and how can this document then
>> be in last call??
> 
> It is common for such sections to appear in documents that are last called.
> They are always removed prior to publication. I already have an RFC Editor
> note that says to do this along with several other things.
> 
>> What would this todo item cause as changes in the document??
> 
> The presumption is that the issue, such as it is, will be left unresolved.
> When I reviewed this I didn't think the issue was substantive. If it is
> seen as substantive by someone, well, that's what last calls are for...
> 
>                 Ned