Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC

"J.D. Falk" <jdfalk-lists@cybernothing.org> Fri, 14 October 2011 16:03 UTC

Return-Path: <jdfalk-lists@cybernothing.org>
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 E00DF21F84C9 for <ietf@ietfa.amsl.com>; Fri, 14 Oct 2011 09:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cwgUiWn-PXs1 for <ietf@ietfa.amsl.com>; Fri, 14 Oct 2011 09:03:12 -0700 (PDT)
Received: from ocelope.disgruntled.net (ocelope.disgruntled.net [97.107.131.76]) by ietfa.amsl.com (Postfix) with ESMTP id 000F221F8BA0 for <ietf@ietf.org>; Fri, 14 Oct 2011 09:03:11 -0700 (PDT)
Received: from [192.168.11.37] (c-76-126-154-212.hsd1.ca.comcast.net [76.126.154.212]) (authenticated bits=0) by ocelope.disgruntled.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p9EG35pr002660 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 14 Oct 2011 09:03:08 -0700
Subject: Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: "J.D. Falk" <jdfalk-lists@cybernothing.org>
In-Reply-To: <CALaySJJhshwKu9U6GWPR30+sSmk-QPuuQADqmWjD5sx08KJxQA@mail.gmail.com>
Date: Fri, 14 Oct 2011 09:03:05 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A2CD2D78-BBA1-4DB9-8E01-2B2B0AE0D22C@cybernothing.org>
References: <20110922134311.28658.88510.idtracker@ietfa.amsl.com> <6.2.5.6.2.20111003005127.09464a50@resistor.net> <F5833273385BB34F99288B3648C4F06F19C45D9E13@EXCH-C2.corp.cloudmark.com> <CAC4RtVAyyPKjxPqKQKnc5qeFh-88KOT7NL0846gRTMOb9zL0rg@mail.gmail.com> <3266F4FF-761B-4A12-8F68-7F7F8EBC3090@cybernothing.org> <CALaySJJGwGparJZVxnTZUWZfU+RyVUcVfg13GPmdvr+4VAzZ5A@mail.gmail.com> <4E97D434.8030402@qualcomm.com> <CALaySJJhshwKu9U6GWPR30+sSmk-QPuuQADqmWjD5sx08KJxQA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1084)
Cc: Pete Resnick <presnick@qualcomm.com>, "ietf@ietf.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: Fri, 14 Oct 2011 16:03:13 -0000

On Oct 14, 2011, at 6:14 AM, Barry Leiba wrote:

>>>>> He's not talking about the filename; the short title is what's printed
>>>>> at the top of every page.  It comes from the "abbrev" parameter in the
>>>>> "title" element in the XML.  It can be changed with an RFC Editor
>>>>> note.
>> 
>> The sponsoring AD would like to know what is desired in the RFC Editor note:
>> What would you like the short title to be? "CFBL Recommendations"?
> 
> Yes, that's consistent with the main title.

Agreed.

> I think those are reasonable compromises, but, of course, I can't
> speak for J.D.  I suggest moving the second paragraph of the Abstract
> into a new "Introduction" section that comes first in the body (new
> Section 1).  Put the footnote [1] to MAAWG there, and then put the
> "about MAAWG" text in the footnote.  Everyone understand that?  Makes
> sense?  I think that works better than putting it in the Acks.

I'm okay with either, with a slight preference for including it in the Acknowledgements section.  MAAWG understands that this kind of boilerplate is unusual for IETF documents.

Should I submit a new draft with these changes?

--
J.D. Falk
the leading purveyor of industry counter-rhetoric solutions