RE: IP-based reputation services vs. DNSBL (long)
<michael.dillon@bt.com> Tue, 11 November 2008 09:23 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 7DC9B28C14B; Tue, 11 Nov 2008 01:23:45 -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 5388928C12E for <ietf@core3.amsl.com>; Tue, 11 Nov 2008 01:23:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 e6lnaf5uNEO1 for <ietf@core3.amsl.com>; Tue, 11 Nov 2008 01:23:43 -0800 (PST)
Received: from smtp3.smtp.bt.com (smtp3.smtp.bt.com [217.32.164.138]) by core3.amsl.com (Postfix) with ESMTP id 6894528C141 for <ietf@ietf.org>; Tue, 11 Nov 2008 01:23:43 -0800 (PST)
Received: from E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.61]) by smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 11 Nov 2008 09:23:42 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: IP-based reputation services vs. DNSBL (long)
Date: Tue, 11 Nov 2008 09:22:41 -0000
Message-ID: <C0F2465B4F386241A58321C884AC7ECC0945239E@E03MVZ2-UKDY.domain1.systemhost.net>
In-Reply-To: <49193FA7.7070101@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
thread-topic: IP-based reputation services vs. DNSBL (long)
Thread-Index: AclD1hb2u+GljossTwu8GhINz9WMVgABzGvA
From: michael.dillon@bt.com
To: ietf@ietf.org
X-OriginalArrivalTime: 11 Nov 2008 09:23:42.0913 (UTC) FILETIME=[309CF310:01C943DF]
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
> Would refusing to publish as a standard stop > implementations or merely create potential interoperability > issues that could lead to more legitimate messages being dropped? How would refusing to publish a document that is already public, CREATE potential interoperability issues? The question is not whether this information should be made public, because it already has been and there is no reason to believe that an IETF refusal would in any way prevent future publication of the information. The heart of the question is whether or not this is work that belongs in the IETF. A big part of the issue is the fact that this draft glosses over the security considerations of DNSBLs. If the draft had taken more than three brief paragraphs to discuss these, then we would be having a different discussion. DNSBLs are a temporary band-aid solution for a badly broken Internet email architecture. They have provided the community with an education but that doesn't mean that they should be standardised by the IETF. --Michael Dillon _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- IP-based reputation services vs. DNSBL (long) Keith Moore
- Re: IP-based reputation services vs. DNSBL (long) John Leslie
- RE: IP-based reputation services vs. DNSBL (long) Lawrence Rosen
- Re: IP-based reputation services vs. DNSBL (long) John Levine
- RE: IP-based reputation services vs. DNSBL (long) Lawrence Rosen
- Re: IP-based reputation services vs. DNSBL (long) Eliot Lear
- RE: IP-based reputation services vs. DNSBL (long) michael.dillon
- Re: IP-based reputation services vs. DNSBL (long) Keith Moore
- Re: IP-based reputation services vs. DNSBL (long) Eliot Lear
- Re: IP-based reputation services vs. DNSBL (long) Keith Moore
- Re: IP-based reputation services vs. DNSBL (long) Dave CROCKER
- Re: IP-based reputation services vs. DNSBL (long) Dave CROCKER
- Re: IP-based reputation services vs. DNSBL (long) Dave CROCKER
- RE: IP-based reputation services vs. DNSBL (long) Hallam-Baker, Phillip
- Re: IP-based reputation services vs. DNSBL (long) Sam Hartman
- Re: IP-based reputation services vs. DNSBL (long) TS Glassey
- Re: IP-based reputation services vs. DNSBL (long) Tony Finch
- Re: IP-based reputation services vs. DNSBL (long) Keith Moore
- Re: IP-based reputation services vs. DNSBL (long) Keith Moore
- Re: IP-based reputation services vs. DNSBL (long) TS Glassey
- Re: IP-based reputation services vs. DNSBL (long) Matthias Leisi
- Re: IP-based reputation services vs. DNSBL (long) Matthias Leisi
- Re: IP-based reputation services vs. DNSBL (long) Eliot Lear
- Re: IP-based reputation services vs. DNSBL (long) TS Glassey
- Re: IP-based reputation services vs. DNSBL (long) Chris Lewis
- RE: IP-based reputation services vs. DNSBL (long) Hallam-Baker, Phillip
- Re: IP-based reputation services vs. DNSBL (long) Chris Lewis
- Re: not spoofing, was IP-based reputation serviceā¦ John Levine
- RE: IP-based reputation services vs. DNSBL (long) Hallam-Baker, Phillip
- Re: IP-based reputation services vs. DNSBL (long) Chris Lewis
- RE: IP-based reputation services vs. DNSBL (long) Hallam-Baker, Phillip