Re: drums2?

Pete Resnick <presnick@qualcomm.com> Fri, 16 August 2002 16:52 UTC

Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g7GGqnf28706 for ietf-822-bks; Fri, 16 Aug 2002 09:52:49 -0700 (PDT)
Received: from episteme-software.com (champdsl-25-66.mcleodusa.net [216.43.25.66]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7GGqlw28698 for <ietf-822@imc.org>; Fri, 16 Aug 2002 09:52:48 -0700 (PDT)
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with ESMTP (Eudora Internet Mail Server 3.1.3); Fri, 16 Aug 2002 11:52:43 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <a05200629b982dc0dd554@[216.43.25.67]>
In-Reply-To: <H0xp09.MLF@clw.cs.man.ac.uk>
References: <3D5AB95C.3020103@att.com> <01KLAG31RZ4A0001B1@mauve.mrochek.com> <5.1.1.2.2.20020815083718.07a296b0@jay.songbird.com> <H0xp09.MLF@clw.cs.man.ac.uk>
X-Mailer: Eudora [Macintosh version 5.2a3]
Date: Fri, 16 Aug 2002 11:51:43 -0500
To: Charles Lindsey <chl@clw.cs.man.ac.uk>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: drums2?
Cc: ietf-822@imc.org
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>

On 8/16/02 at 11:24 AM +0000, Charles Lindsey wrote:

>Well reclassifying a few items into or out of the obsolete category is not
>necessarily "new technical work" is it? Surely that is just tidying up.

Nope, that's new technical work. A Draft Standards documents existing 
practice. It doesn't say how things should be.

>OTOH, if a major change in email is shortly going to happen, namely hte
>internationalization of addr-specs, then it does not seem to be the right
>time to be bringing out a new standard that merely re-establishes the old
>system.

Two things:

1. This is the way the IETF works. We add on to the old system with 
new Proposed Standards, we document the old system with Draft and 
Full Standards. It seems perfectly "right". Other standards bodies 
might operate differently.

2. If there is a major change in e-mail, it better happen in a way 
that doesn't invalidate the old system. That was what was great about 
MIME: Every MIME message is a perfectly valid 822 message, only it 
was interpreted differently. Documenting the old system (and it's not 
a "new standard") is *exactly* what needs to happen if there is going 
to be a major change: It should be perfectly clear for the proposed 
change what will conform to the current system.

This is "IETF 101" stuff. Moving to Draft Standard *removes* stuff 
from the spec that doesn't correspond to reality. It *never* adds or 
changes stuff. Perhaps your message is a good indicator that we 
haven't been moving things to Draft Standard nearly enough lately.

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102