IETF Logo Mail Archive

Re: draft-irtf-asrg-bcp-blacklists

John Levine <johnl@iecc.com> Sun, 09 November 2008 00:10 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED5D53A68DE; Sat, 8 Nov 2008 16:10:04 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E67963A68DE for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 16:10:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.145
X-Spam-Level:
X-Spam-Status: No, score=-10.145 tagged_above=-999 required=5 tests=[AWL=-0.045, BAYES_00=-2.599, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0JARym-wIFhB for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 16:10:02 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 8559E3A68BF for <ietf@ietf.org>; Sat, 8 Nov 2008 16:10:02 -0800 (PST)
Received: (qmail 33419 invoked from network); 9 Nov 2008 00:09:59 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 9 Nov 2008 00:09:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=t1108; i=johnl@user.iecc.com; bh=YRjCWuDFVf7Hptz3WVSC9fHzvOLPBwn9z4uLvTZsbdY=; b=VJ/1HWrZlKLVfQBZBvGnf9YFmiCswcBSo5AnFUcX1/W37uQm/MoYfta9pHwef3ELCiI3/OGVo5x4OypL6SJ2hSMTHJu8Fw/aX/2mp+IQSnw4+PCMJkPTQ8hx7M9C5iz2
Date: Sun, 09 Nov 2008 00:09:58 -0000
Message-ID: <20081109000958.6074.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: draft-irtf-asrg-bcp-blacklists
In-Reply-To: <6.2.5.6.2.20081108144825.040b1720@resistor.net>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Cc: sm@resistor.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

>Standard Track and BCP RFCs are part of the IETF document 
>stream.  The proposed IRTF document stream (draft-irtf-rfcs) doesn't 
>create a new class of documents called IRTF BCPs.

Quite right.  That's why we're having the argument here about
draft-irtf-asrg-dnsbl-08.

>Shouldn't the headings of the two documents coming out of the ASRG be 
>"Network Working Group" instead of "Anti-Spam Research Group" as the 
>intended category is part of the IETF stream?

The boilerplate in the drafts is all generated by xml2rfc.  I presume
that the RFC Editor can adjust it appropriately.

R's,
John
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email