Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06

Dave Crocker <dcrocker@bbiw.net> Thu, 18 October 2012 13:51 UTC

Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68F5721F875A; Thu, 18 Oct 2012 06:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.413
X-Spam-Level:
X-Spam-Status: No, score=-6.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDBn-7Tg62ub; Thu, 18 Oct 2012 06:50:59 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 79E7721F8758; Thu, 18 Oct 2012 06:50:59 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9IDosbT008905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 18 Oct 2012 06:50:55 -0700
Message-ID: <5080093D.2050406@bbiw.net>
Date: Thu, 18 Oct 2012 06:50:53 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <01OLJ9JAK8SQ00008S@mauve.mrochek.com> <507F5249.2090507@dcrocker.net> <CALaySJKD+JbkOuZsC7wQtNNLHBP-4a_=DNfQ0XkQWoCq78-JGg@mail.gmail.com> <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com>
In-Reply-To: <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 18 Oct 2012 06:50:55 -0700 (PDT)
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, johnl@taugh.com, Barry Leiba <barryleiba@computer.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
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>
X-List-Received-Date: Thu, 18 Oct 2012 13:51:00 -0000

On 10/18/2012 6:45 AM, John C Klensin wrote:
> As I said earlier, I can live with almost anything if it is
> correct and allows us to move forward.  I am, however, getting
> more concerned about the consequences to the virtual 5322bis and
> its future instantiation if we go down these paths.  I would
> really not like to be the relevant AD (or Pete-bis) trying to
> defend leaving the explanation and reference out of 5322bis
> given that they were important enough to include in this
> document and, if the explanation and reference go into 5322bis,
> why a large series of other references and explanations should
> not be included.  I'd be a tad happier if this explanatory stuff
> when into an appendix rather than the text.


The job of the current draft is to be sufficient to its purpose.  Its 
purpose is to augment a base document with a specific revision.

An update segment document does not typically have the purpose of 
including extensive annotations for possible later use, attempting to 
anticipate or hypothesize later editing efforts, to revise the base 
document.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net