Re: [Asrg] IP responsibility --slightly out of scope

Alessandro Vesely <vesely@tana.it> Mon, 31 March 2008 01:01 UTC

Return-Path: <asrg-bounces@ietf.org>
X-Original-To: asrg-archive@optimus.ietf.org
Delivered-To: ietfarch-asrg-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 448763A6A02; Sun, 30 Mar 2008 18:01:29 -0700 (PDT)
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 AB8C03A6A02 for <asrg@core3.amsl.com>; Sun, 30 Mar 2008 18:01:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level:
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 4dj4u8M8Yg4l for <asrg@core3.amsl.com>; Sun, 30 Mar 2008 18:01:27 -0700 (PDT)
Received: from north.tana.it (north.tana.it [194.243.254.162]) by core3.amsl.com (Postfix) with ESMTP id BD98E3A6899 for <asrg@ietf.org>; Sun, 30 Mar 2008 18:01:26 -0700 (PDT)
Received: from [194.243.254.190] (ip190.tana.it [194.243.254.190]) by north.tana.it (8.11.7p1+Sun/8.8.5) with ESMTP id m2UJEhu06313 for <asrg@ietf.org>; Sun, 30 Mar 2008 21:14:43 +0200 (CEST)
Message-ID: <47EFE6A2.7000001@tana.it>
Date: Sun, 30 Mar 2008 21:14:42 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@ietf.org>
References: <20080325160757.22934.qmail@simone.iecc.com> <47EAFBAB.2060000@tana.it> <fsg978$7dg$1@ger.gmane.org>
In-Reply-To: <fsg978$7dg$1@ger.gmane.org>
X-Enigmail-Version: 0.95.6
Subject: Re: [Asrg] IP responsibility --slightly out of scope
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@ietf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

Frank Ellermann wrote:
>> I think those concepts should be clarified, referencing the
>> relevant RFC where apropriate
> 
> Post numbers, please.  I'd know where to find the MTAMARK draft,
> unfortunately that never made it.  The reverse lookup draft is
> just in WGLC and should be available if needed as reference.

I guess you mean draft-ietf-dnsop-reverse-mapping-considerations-06.
It has a number of interesting consideration w.r.t. DNSBLs, as it also 
considers anti-spam as a topic. Specifically, in-addr.arpa could be 
considered a DNSWL in its own right.

The other relevant topic is [r]whois maintenance. I'm not an RFC 
connoisseur, and I'm quite lost here. The specs, e.g. rfc1714 or 
rfc3912, limit themselves with protocol specification, even if they 
suggest that tracking IP assignment is the intended usage. Rfc2050 
mentions a database that is maintained by adding reassignment 
information, but doesn't say if and how it is published. Perhaps, 
there is room enough in the DNSBL BCP to informally suggest that 
published information about IP assignments _is_ available, and that 
the point of contact mentioned there is responsible for referring to 
the final user of a given number. Policies and obligations for 
actually providing such reference obviously vary.
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www.ietf.org/mailman/listinfo/asrg