RE: Further IESG feedback on draft-crispin-imapv-17.txt

ned.freed@mrochek.com Fri, 20 September 2002 21:26 UTC

Received: by above.proper.com (8.11.6/8.11.3) id g8KLQ5n08951 for ietf-imapext-bks; Fri, 20 Sep 2002 14:26:05 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [209.55.107.55]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g8KLQ4k08943 for <ietf-imapext@imc.org>; Fri, 20 Sep 2002 14:26:04 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01KMP5PUHPY800628S@mauve.mrochek.com> for ietf-imapext@imc.org; Fri, 20 Sep 2002 14:26:03 -0700 (PDT)
Date: Fri, 20 Sep 2002 14:20:58 -0700
From: ned.freed@mrochek.com
Subject: RE: Further IESG feedback on draft-crispin-imapv-17.txt
In-reply-to: "Your message dated Fri, 20 Sep 2002 13:59:01 -0700" <72C5FDA4D9CC3045B80EA1B76DB86A99ED2CC0@DF-BOWWOW.platinum.corp.microsoft.com>
To: Larry Osterman <larryo@exchange.MICROSOFT.com>
Cc: Mark Crispin <MRC@cac.washington.edu>, ned.freed@mrochek.com, IMAP Mailing List <imap@u.washington.edu>, IMAP Extensions WG <ietf-imapext@imc.org>, paf@cisco.com, jis@mit.edu
Message-id: <01KMQ6IRCEVA00628S@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Content-transfer-encoding: 7bit
References: <72C5FDA4D9CC3045B80EA1B76DB86A99ED2CC0@DF-BOWWOW.platinum.corp.microsoft.com>
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>

> What's the standards track status on IMAP-TLS?

RFC 2595 is currently a proposed standard.

>  Won't citing it as a
> reference tie the base standard to a subsidiary standard?

I'm not sure what you mean by "subsidiary". If you mean does it create a
normative reference to RFC 2595 and from there to TLS and so on, the answer is
yes it does. Such references are to be expected and certainly aren't a problem
per se.

Normative references do become an issue should a specification want to advance
to draft. In this case we'd have to advance both the base IMAP specification
and RFC 2595 at the same time. And that cannot happen until TLS itself
advances. But again, this is an expected and normal part of the standards
process.

> Other than that nit, I personally like the wording.

Good.

				Ned