Re: [Asrg] I-D Action: draft-irtf-asrg-dnsbl-08.txt (fwd)

SM <sm@resistor.net> Wed, 19 November 2008 09:28 UTC

Return-Path: <asrg-bounces@irtf.org>
X-Original-To: asrg-archive@optimus.ietf.org
Delivered-To: ietfarch-asrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA9CD3A6B72; Wed, 19 Nov 2008 01:28:35 -0800 (PST)
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 447213A6B6C for <asrg@core3.amsl.com>; Wed, 19 Nov 2008 01:28:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.111
X-Spam-Level:
X-Spam-Status: No, score=-2.111 tagged_above=-999 required=5 tests=[AWL=-0.311, BAYES_00=-2.599, 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 m4S7TtBSOaKR for <asrg@core3.amsl.com>; Wed, 19 Nov 2008 01:28:33 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 7BB4D3A676A for <asrg@irtf.org>; Wed, 19 Nov 2008 01:28:33 -0800 (PST)
Received: from subman.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.3/8.14.3) with ESMTP id mAJ9SLJj020664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Wed, 19 Nov 2008 01:28:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1227086911; x=1227173311; bh=tlpyQxwdGMLOQaHIasskiclXdneVWb8znT0DCYwgosM=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=tzH832Iyv+DHKDu7q0McU6EiFWRHjyDa/IZy4mTcxUqmp/SuXBU5/LvgzQAUZczRT zCpNRM/MPxlB75WcXTfdwdzht4AR4dGYvYTH2LEXHkc6wbBOIOn/fw48KgDY9OcqP8 le1joCFlYxplMWC+QODdLP55Lu6qYj5+CYc837sE=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=JcbTDJ7NcFa0ivTUji5toutV5JZ2N6hhp51iLl982mQZLqJakRwwo9oQcwNguD92L 9PQNPiWQ6TH8A/IavNJotgBogj8tGts55E99nxhByRK4/tcbKXKQxTr3D1NXU879L9K 9Tn/YHrvUsm3QcRHY8c6S7mKZxC66R9ycVeovxA=
Message-Id: <6.2.5.6.2.20081119001219.02a77790@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 19 Nov 2008 00:53:53 -0800
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
From: SM <sm@resistor.net>
In-Reply-To: <4922E592.8050806@dcrocker.net>
References: <20081117224341.98303.qmail@simone.iecc.com> <4922E592.8050806@dcrocker.net>
Mime-Version: 1.0
Subject: Re: [Asrg] I-D Action: draft-irtf-asrg-dnsbl-08.txt (fwd)
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: asrg-bounces@irtf.org
Errors-To: asrg-bounces@irtf.org

At 07:56 18-11-2008, Dave CROCKER wrote:
>John Levine wrote:
>>>I don't recall seeing a group consensus process for determining
>>>whether to shift out of seeking standards track.
>>There wasn't any group consensus to move it onto the standards
>>track, either.
>
>which means that it really was an individual submission and should 
>not have been cast as coming from the ASRG...

There is a mention in this draft about it being a product of the 
Anti-Spam Research Group (ASRG), a group that falls under the IRTF ( 
www.irtf.org ).  The guidelines and procedures for IRTF Research 
Groups are described in RFC 2014.

Version 5 of this draft mentions that it represents the consensus of 
the ASRG and the intended status was "Informational".  The intended 
status of Version 6 of this draft was "Standards Track".  As such, it 
would require IETF consensus and be published as an "Individual 
Submission" which has gone through the IETF process.  Version 8 of 
this draft which was submitted after the Last Call has an intended 
status of "Informational".

Dave has a point.  If the drafts from the ASRG are said to be a 
product of the group and represented as the consensus of the group, 
it would be good to seek the group consensus for any changes.  That 
would avoid unneeded "issues".

Regards,
-sm 

_______________________________________________
Asrg mailing list
Asrg@irtf.org
https://www.irtf.org/mailman/listinfo/asrg