Re: [Gen-art] Gen-ART LC Review of draft-ietf-eai-simpledowngrade-07

Barry Leiba <barryleiba@computer.org> Thu, 20 September 2012 18:30 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 914AB21F8733; Thu, 20 Sep 2012 11:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.956
X-Spam-Level:
X-Spam-Status: No, score=-102.956 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 fqz7OqaYc62d; Thu, 20 Sep 2012 11:30:50 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id B827A21F8731; Thu, 20 Sep 2012 11:30:48 -0700 (PDT)
Received: by lboj14 with SMTP id j14so2540473lbo.31 for <multiple recipients>; Thu, 20 Sep 2012 11:30:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=CoTQaCIPSvH3MZ5oITbHk654TiQQr5hSzf1AomJGV2I=; b=aAru/g6jdGzCd2LP/17vvDA643K9+PyZfkVnrgwjWNeaAYsu7xGJ2KfZrw/8toEsPO kLO5unteyrWEvk3EhiBLzhxREgJhucGtFzId8MKQbq4Udn9LOIoKnCF+cYuGeMRijV8I 7nChUA4pJ2eRDDRxo7/FuPUecC0f9mFSPFJLpF1OYd3bbVCHwGEM5ORkFMa+YQufRPSH viTVisrz7JRHcrRgHHLBpcLQdLIo3rPSqrPDyTxXtlJVQWx6InYBgw5pbTCQcMRe2oXQ /JRw1WjJx4jyou2tO7CsTQrq4dVTBLXtCXbtGRYrTRA/dKsCDMvuRY1q6DUphDszw55Q 29aA==
MIME-Version: 1.0
Received: by 10.152.123.103 with SMTP id lz7mr2244122lab.21.1348165847663; Thu, 20 Sep 2012 11:30:47 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.91.33 with HTTP; Thu, 20 Sep 2012 11:30:47 -0700 (PDT)
In-Reply-To: <5059E240.8040702@gulbrandsen.priv.no>
References: <74115521-D2B3-419B-9571-660D16F06BB1@nostrum.com> <5059E240.8040702@gulbrandsen.priv.no>
Date: Thu, 20 Sep 2012 14:30:47 -0400
X-Google-Sender-Auth: ume0gzkK2nKDUxmbVSu9wryrjYc
Message-ID: <CAC4RtVCqB5GDXmyi1TDE-B+dBbJaN7veM15GfGD+eNk+VNyAUQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Ben Campbell <ben@nostrum.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-eai-simpledowngrade.all@tools.ietf.org, "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-eai-simpledowngrade-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Sep 2012 18:30:50 -0000

>> -- Abstract should mention that this updates 3501
>
> Really? A detail of this document updates a minor detail of that document,
> that's hardly what I would expect to see in a single-paragraph summary.
>
> I know someone who likes to repeat the Subject in the first line of the
> email body text. Just in case I didn't see it the first time, I suppose.

There's no need to be flippant; this is called out by the idnits
program, and Ben is highlighting it.  It's not a big deal, but there
are reasons for it:

1. The "updates" (and "obsoletes") information is not in the text of
the published RFC, but is part of the RFC's metadata.  Not everyone
who will look at the RFC will see the metadata.  Some will see only
Title and Abstract.  And so on.  It's not just frivolity to put
something in the Abstract.

2. We also like to have an *explanation* in the Introduction, saying
why a document updates another.  For that part, it's not just "This
document updates RFC 3501," but "This document updates RFC 3501
because it adds [this] and changes [that]."

Barry