Re: Informational RFC to be: <draft-irtf-asrg-bcp-blacklists-10.txt>

The IESG <iesg-secretary@ietf.org> Tue, 27 September 2011 14:45 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3E8121F8DED; Tue, 27 Sep 2011 07:45:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.136
X-Spam-Level:
X-Spam-Status: No, score=-102.136 tagged_above=-999 required=5 tests=[AWL=-0.336, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
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 C9P-EmFOlnQL; Tue, 27 Sep 2011 07:45:02 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FA5721F8D44; Tue, 27 Sep 2011 07:45:02 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: irsg@irtf.org
Subject: Re: Informational RFC to be: <draft-irtf-asrg-bcp-blacklists-10.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.60
Message-ID: <20110927144502.3443.46236.idtracker@ietfa.amsl.com>
Date: Tue, 27 Sep 2011 07:45:02 -0700
Cc: johnl@iecc.com, iana@iana.org, The IESG <iesg@ietf.org>, ietf-announce@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Sep 2011 14:45:03 -0000

The IESG has no problem with the publication of 'Overview of Email DNSBL
Best Practise' <draft-irtf-asrg-bcp-blacklists-10.txt> as an
Informational RFC.

The IESG wants to make the IRSG aware of its concern that there is
a potential for confusion between the IETF "Best Current Practice" (BCP)
series and the use of the term "Best Practise" in the title and the abstract
as well as the use of the acronym "BCP" in the page header of each
page and in sections 1.2 and 3.6. Anything that the IRSG can do to
avoid this confusion would be appreciated.

The IESG would also like the IRSG to review the comments in
the datatracker
(http://datatracker.ietf.org/doc/draft-irtf-asrg-bcp-blacklists/) related
to this document and determine whether or not they merit incorporation
into the document. Comments may exist in both the ballot and the comment
log.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-irtf-asrg-bcp-blacklists/

The process for such documents is described at
http://www.rfc-editor.org/indsubs.html

Thank you,

The IESG Secretary




Technical Summary

   The rise of spam and other anti-social behavior on the Internet has
   led to the creation of shared DNS-based lists ("DNSBLs") of IP
   addresses or domain names intended to help guide email filtering.
   This memo summarizes guidelines of accepted best practise for the
   management of public DNSBLs by their operators as well as for the
   proper use of such lists by mail server administrators (DNSBL users),
   and it provides useful background for both parties.  It is not
   intended to advise on the utility or efficacy of particular DNSBLs or
   the DNSBL concept in general, nor to assist end users with questions
   about spam.

Working Group Summary

   This document is a product of the Anti-Spam Research Group and
   represents the consensus of that group.

Document Quality

   This document is a research publication of the IRTF.

Personnel

   Pete Resnick <presnick@qualcomm.com> is the responsible Area Director.

IESG Note

   The IESG has concluded that this work is related to IETF work done
   in the MARF WG and the as-yet-unchartered REPUTE BOF, but this relationship
   does not prevent publishing.