
From johnl@iecc.com  Sun Mar  3 20:07:37 2013
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 617D621F87E4 for <asrg@ietfa.amsl.com>; Sun,  3 Mar 2013 20:07:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.001
X-Spam-Level: 
X-Spam-Status: No, score=-100.001 tagged_above=-999 required=5 tests=[NO_RELAYS=-0.001, 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 GdFg77DVHV0A for <asrg@ietfa.amsl.com>; Sun,  3 Mar 2013 20:07:31 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 9A26C21F8756 for <asrg@irtf.org>; Sun,  3 Mar 2013 20:07:28 -0800 (PST)
Received: (qmail 75299 invoked from network); 4 Mar 2013 04:07:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:vbr-info:user-agent:cleverness; s=12622.51341e00.k1303; bh=C1TTiMVurgDkF5hiTSGBBdPNQjKqUOngQ3lp0CsCXVU=; b=CVE4ZBNgtX0rx60fi0z+MXE7hfen7aMT0r+PgsTD7gqXNKXGOp79Z0pGFOlOER/kWe1/+BTvEmF2nLdbM3FIFnTr6V69AqMbHQ4SLvixwzVhFX8bdRgPcjO8pvFwHJbk+wTAR6imspaynqqyt5UKkTm8kDN5ZJYIrineGkluJaY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 4 Mar 2013 04:07:06 -0000
Date: 3 Mar 2013 23:07:27 -0500
Message-ID: <alpine.BSF.2.00.1303032304390.89952@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Anti Spam Research Group" <asrg@irtf.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-1851939189-1362370047=:89952"
Subject: [Asrg] The end of the ASRG
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 04:07:37 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-1851939189-1362370047=:89952
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII

I've been talking to the head of the Internet Research Task Force, and 
have reluctantly agreed that since the ASRG hasn't doing anything for 
about a year, and doesn't seem likely to do anything in the future, it's 
time to shut it down.  The IETF meets next week, and barring a surprise, 
we'll probably pull the plug then.

There's plenty of anti-spam research to do, and a fair amount being done, 
but it's not being done here.

The ASRG wiki is hosted on a machine I personally own, and I expect to 
leave it up indefinitely, in case anyone has further interest in using or 
(hint hint) updating and extending the taxonomy of anti-spam techniques.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly
--3825401791-1851939189-1362370047=:89952
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIIJwAYJKoZIhvcNAQcCoIIJsTCCCa0CAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBvEwggbtMIIF1aADAgECAgMElr8wDQYJKoZIhvcNAQELBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xMjA3MjYwMTI5NTNaFw0xMzA3MjcwODE4NTVaMDgxFzAV
BgNVBAMMDmpvaG5sQGllY2MuY29tMR0wGwYJKoZIhvcNAQkBFg5qb2hubEBp
ZWNjLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMFb8p7E
Amn6F6QRKCe3TS54cIt5/+qSF4wmlM5cfiZyDvr1H4ttCWDKjUS1N2QaH38J
G23LRAanlY+G/WKY/SCuEtNqIApqHrbF2QGlzDEYIHXg+5//vlSXZ/lNof8p
96XDqnZZZQrqhcvy2Vrx6YWeIzobO+HHSQTqOvAotXx6LRwLIrQ38jIN4FPr
kYescZlMWFG4dlrQLkgzn31heyqn0Mg0i+y2w+UaeHyLBKxzyIzaoQY5yJje
e+hihNtn+SBSwzR6JD88Jp1tet/oxsDfR6TWf6cnujXRR8kCgWryJ5DkiL8B
5SAL5WR7XvrLnhxMNZmDl0g2/0QoHiLdXv8CAwEAAaOCA6kwggOlMAkGA1Ud
EwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEF
BQcDBDAdBgNVHQ4EFgQUOjyDiYoWWJbXWPUtB8wSSe3G6qIwHwYDVR0jBBgw
FoAUU3Ltkpzg2ssBXHx+ljVO8tS4UYIwGQYDVR0RBBIwEIEOam9obmxAaWVj
Yy5jb20wggIhBgNVHSAEggIYMIICFDCCAhAGCysGAQQBgbU3AQICMIIB/zAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBk
ZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJt
ZWRpYXRlLnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlm
aWNhdGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2Fz
IGlzc3VlZCBhY2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiBy
ZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFu
Y2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29tcGxpYW5j
ZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wgZwGCCsGAQUF
BwICMIGPMCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMC
AQIaZExpYWJpbGl0eSBhbmQgd2FycmFudGllcyBhcmUgbGltaXRlZCEgU2Vl
IHNlY3Rpb24gIkxlZ2FsIGFuZCBMaW1pdGF0aW9ucyIgb2YgdGhlIFN0YXJ0
Q29tIENBIHBvbGljeS4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5z
dGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5
BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFz
czEvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3Ns
LmNvbS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBww
GoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBCwUAA4IB
AQAJApMkA1Q6kZOLmOfAqp9Cd/6crBHszmxKVg0rlIXR9eLtbjohunMDRm8l
is4y5XLr/oHuUrY42wPt6gbjSL7BTJJv//HjgZGQQ1pTUIB+MPD4WefCwTG/
+SSLGcGW/mcXTCK7XvD3e+PIudfK+HnqpyAr1lH/pkunWWnoSWf408QIxIIa
RVNFhQlyr75H1RKiYZllbJTwbMsQqbkHE+W08Dl2LMz9AWW+Qq0v1WGSOYr/
prkSmqpNyNN3yInNRM2ju1/EWLxaK0ViITL4pY7Ck/RKPz+7hufcLZmA51XY
tVY8nqITnFz5N6FJLGvCQ7tom5cHp5D8vtujPcMYKjJuMYIClzCCApMCAQEw
gZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgw
NgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRl
IENsaWVudCBDQQIDBJa/MAkGBSsOAwIaBQCggdgwGAYJKoZIhvcNAQkDMQsG
CSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwMzA0MDQwNzI3WjAjBgkq
hkiG9w0BCQQxFgQUX6RCCTxh93foEM6XrQiBNkFoecQweQYJKoZIhvcNAQkP
MWwwajALBglghkgBZQMEASowCwYJYIZIAWUDBAEWMAsGCWCGSAFlAwQBAjAK
BggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYF
Kw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAcIxVSV2h
ouvWQkiZ8/YnrxZ/xm6y0Wzt8/P7iOGSOkJkV9OzVlk8Hf/lxOjpBrRVGciX
PkE4AGvUSwrj+xSAF6MhFrhGRSGcVrB/+qteShLaZMJJkaThMfV7fu44fZJi
BDbUDH77u0OXkuIIuhRHKgbvRThxnkHbRwz2csGvFWprMezq7u8vfrqqQOhU
cf6GVV45+Vy3n5wI8Ce7BgRY8YQ4m5DQR30orMtH2AVhBea4kRt3Tjyuhi3s
djQMH1I5zhxfMqSSDm1CHjzmb+c58uiOFz9qq/rH4D2yL0mO6qq8t98sp6AM
voPJRCOVzh6IOOlBbvm89fNHdliENlQpSw==

--3825401791-1851939189-1362370047=:89952--

From darxus@chaosreigns.com  Sun Mar  3 21:08:04 2013
Return-Path: <darxus@chaosreigns.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ECC121F874C for <asrg@ietfa.amsl.com>; Sun,  3 Mar 2013 21:08:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.599
X-Spam-Level: 
X-Spam-Status: No, score=0.599 tagged_above=-999 required=5 tests=[J_CHICKENPOX_23=0.6, NO_RELAYS=-0.001]
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 YzU+eRK-xpK4 for <asrg@ietfa.amsl.com>; Sun,  3 Mar 2013 21:07:59 -0800 (PST)
Received: from panic.chaosreigns.com (panic.chaosreigns.com [IPv6:2600:3c01::f03c:91ff:fe96:340b]) by ietfa.amsl.com (Postfix) with ESMTP id 86AF621F8742 for <asrg@irtf.org>; Sun,  3 Mar 2013 21:07:59 -0800 (PST)
Received: by panic.chaosreigns.com (Postfix, from userid 1000) id EECC5CD348; Mon,  4 Mar 2013 00:07:58 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=chaosreigns.com; s=mail; t=1362373678; bh=nEWhcVVtQKpfhkC8O8PVVL1oPZgZC5YQDEgIrAsde/Y=; h=Date:From:To:Subject:References:In-Reply-To; b=IQTSFn3QhzoG8lvrPgJ9SBhgwH2r0EFNDmyVp4m2bOI/o+ZjXGpYPiS70/PrqZVX5 wU9bU715xBlAsM6YlmEKkykEa+LtLYJLic6o5g0dnjS7N2mmGgyFKFXjmMs8ZbKPUL dvquLe2Huk5tUtrsFJqC/Uv92U+GpmZce6tBLWeE=
Date: Mon, 4 Mar 2013 00:07:58 -0500
From: darxus@chaosreigns.com
To: asrg@irtf.org
Message-ID: <20130304050758.GQ26133@chaosreigns.com>
References: <alpine.BSF.2.00.1303032304390.89952@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1303032304390.89952@joyce.lan>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [Asrg] The end of the ASRG
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 05:08:04 -0000

On 03/03, John R. Levine wrote:
> There's plenty of anti-spam research to do, and a fair amount being
> done, but it's not being done here.

Where is it being done?

-- 
"The most elementary and valuable statement in science, the beginning
of wisdom is: 'I do not know'." - Data, ST:TNG 2x2 Where Silence Has Lease
http://www.ChaosReigns.com

From vesely@tana.it  Mon Mar  4 00:22:53 2013
Return-Path: <vesely@tana.it>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24C9121F8910 for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 00:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level: 
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
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 haXJp0salq9Z for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 00:22:52 -0800 (PST)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 4D94F21F88C7 for <asrg@irtf.org>; Mon,  4 Mar 2013 00:22:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1362385364; bh=ahtPDgRDiFxzCh2W5FJgfBj8lAG1TJnvRmdGiedjbE4=; l=360; h=Date:From:To:References:In-Reply-To; b=q79bSjF/uPY9GLYKmH1++DLndIm2V/Neg0BptRpC9eU4G3Cy4vZMo2kkmpiKlb7CM ontu2ZCiNmuAK1AXpvnZgy0Zzt3wcBun0yl81qawbAH3v6lNQz+p/Rq3YrjERiaix6 7r3GvBHhm0ZhhbC/OngIByOOgHtl5t39wBs7DAio=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Mon, 04 Mar 2013 09:22:43 +0100 id 00000000005DC039.00000000513459D3.00002CDC
Message-ID: <513459D3.4090603@tana.it>
Date: Mon, 04 Mar 2013 09:22:43 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: asrg@irtf.org
References: <alpine.BSF.2.00.1303032304390.89952@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1303032304390.89952@joyce.lan>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] The end of the ASRG
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 08:22:53 -0000

On Mon 04/Mar/2013 05:07:27 +0100 John R. Levine wrote:
> 
> The ASRG wiki is hosted on a machine I personally own, and I expect to
> leave it up indefinitely, in case anyone has further interest in using
> or (hint hint) updating and extending the taxonomy of anti-spam
> techniques.

I'd hope this mailing list is going to remain up indefinitely too.

From martijn.grooten@virusbtn.com  Mon Mar  4 03:30:03 2013
Return-Path: <martijn.grooten@virusbtn.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFC821F8A71 for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 03:30:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 WVqtLns3ZDKm for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 03:30:02 -0800 (PST)
Received: from mx5.sophos.com (mx5.sophos.com [195.171.192.175]) by ietfa.amsl.com (Postfix) with ESMTP id 5F4F621F8A5E for <asrg@irtf.org>; Mon,  4 Mar 2013 03:29:51 -0800 (PST)
Received: from mx5.sophos.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 1373A540ACF for <asrg@irtf.org>; Mon,  4 Mar 2013 11:29:21 +0000 (GMT)
Received: from ABN-EXCH1A.green.sophos (unknown [10.100.70.61]) by mx5.sophos.com (Postfix) with ESMTPS id DBEFE5406F7 for <asrg@irtf.org>; Mon,  4 Mar 2013 11:29:20 +0000 (GMT)
Received: from abn-exch1b.green.sophos ([fe80::dc96:facf:3d2c:c352]) by ABN-EXCH1A.green.sophos ([fe80::67:3150:dacd:910d%15]) with mapi id 14.02.0328.009; Mon, 4 Mar 2013 11:29:49 +0000
From: Martijn Grooten <martijn.grooten@virusbtn.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Thread-Topic: [Asrg] The end of the ASRG
Thread-Index: AQHOGI3I3zQtdNh1YE6b7/jM2ck54JiVMceAgAAykiM=
Date: Mon, 4 Mar 2013 11:29:48 +0000
Message-ID: <0D79787962F6AE4B84B2CC41FC957D0B20C048CD@abn-exch1b.green.sophos>
References: <alpine.BSF.2.00.1303032304390.89952@joyce.lan>, <513459D3.4090603@tana.it>
In-Reply-To: <513459D3.4090603@tana.it>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.100.64.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Asrg] The end of the ASRG
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 11:30:03 -0000

> I'd hope this mailing list is going to remain up indefinitely too.

+1

Though I can kind of see the IRTF's arguments for shutting it down. Perhaps=
 it could be run elsewhere?

In any case, thanks to John for having run the list all these years.

Martijn.

________________________________

Virus Bulletin Ltd, The Pentagon, Abingdon, OX14 3YP, England.
Company Reg No: 2388295. VAT Reg No: GB 532 5598 33.

From rsk@gsp.org  Mon Mar  4 05:29:27 2013
Return-Path: <rsk@gsp.org>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC2F121F89EF for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 05:29:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 PEmAenRuP-kK for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 05:29:27 -0800 (PST)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by ietfa.amsl.com (Postfix) with ESMTP id F19F021F89EE for <asrg@irtf.org>; Mon,  4 Mar 2013 05:29:26 -0800 (PST)
Received: from gsp.org (localhost.firemountain.net [127.0.0.1]) by taos.firemountain.net (8.14.6/8.14.6) with SMTP id r24DTO2k020476 for <asrg@irtf.org>; Mon, 4 Mar 2013 08:29:25 -0500 (EST)
Date: Mon, 4 Mar 2013 08:29:24 -0500
From: Rich Kulawiec <rsk@gsp.org>
To: asrg@irtf.org
Message-ID: <20130304132924.GA27928@gsp.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: [Asrg] Development of an object assessment format/protocol
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 13:29:27 -0000

I've been thinking about this for a long time, and would like to find
out what others have been doing in this area (if anything) and whether
this is a topic we can or should collectively pursue.

Here's the problem statement:

We've been using DNS to communicate information about the assessment
of certain objects -- IP addresses, host names, domain names -- and
while that has its advantages (notably that most of the software already
exists, is already installed, is reasonably well-understood, etc.) it
also limits the vocabulary we can use.  Moreover, there are objects
that we might want to talk about whose information isn't easily
communicated via DNS -- e.g., web pages, email addresses.  We use other
kinds of methods for communicating those, including downloadable files,
APIs, etc.

We need, I think, a mechanism via which we can ask more complex questions
and get more comprehensive answers.  We need a mechanism which isn't
a hack on top of DNS, but which has been developed from the ground up
specifically for this purpose.

At the moment, there are a number of ad hoc ways that this happens:
for example, Joe Wein maintains a rather large list of spammer/phisher
email addresses.  (And domains, too.)   The Malwaredomains folks have
lists of domains.  The Stopforumspam folks have lists of domains and
IP addresses.  There are DNSBLs and RHSBLs like the ones run by Spamhaus.
There are various projects to identify malicious web pages.  And so on.

And all of these are great, except: they all use different ways to
express information.  Some of them can be queried; some can't.  Some
of them carry metadata like "how did we decide this?" or 'when did
we decide this?" or "for further reference, see:" and some don't.
Some of them support methods for asking narrower/broader questions,
some of them don't.

What I'm suggesting, therefore, is that we need (a) a standardized
way to express these things and (b) a standardized protocol by which
we can ask questions and get answers.  For instance:

	Does the web page at http://example.com/foo.html contain malware?

	Is the address fred@example.net associated which phishing?

	What can you tell me about the domain example.com?

	Has the IP address 192.168.0.20 sent spam recently?

Certainly all of these things are possible today, by asking various
information sources in various ways.  But not in an integrated,
unified fashion which would yield results that could be compared
to each other or integrated with each other programatically.

(For example, I might wish to ask 5 different information sources
about 192.168.0.20 and weight their opinions.  Or I might want
to ask an open-ended question like "what do you know about example.com?")

In all these instances, opinions come with metadata: whose opinion
is this?  At what time was it rendered?  Is there are time at which
it should be considered no-longer-valid?  Is there a confidence
level associated with this opinion?  Is the answer specific to
the object that was asked about or does it apply more broadly?
(e.g., I asked about 192.168.0.20 but got back an opinion that
applies not only to that, but to all of 192.168.0.0/24.)

Where I'm going, probably predictably, is that the format for
both questions and answers may be XML-based in order to provide
sufficient expressive power.   (Yes, that's verbose.  Very much
the antithesis of the terse Q/A format we use with DNS.  I haven't
been able to decide if that's a good, bad or neutral thing,
other than noting that using XML has the advantage of making
information immediately palatable to a wide range of software.)

So let me see if I can phrase the questions this way:

1. Is such a format needed?
2. Is a query-response protocol needed to transmit it?
3. If so, does anything already exist which would lend itself
to (1) and (2) with minimal changes?  If so, is it desirable
to run that experiment?
4. If not, then is there sufficient utility in this approach
that it's worth pursuing?
5. If this exists, will it be used?  Is there sufficient reason
for changes from what already exists?

(I'm aware of draft-dskoll-reputation-reporting, but it doesn't
cover all kinds of objects I have in mind here.  I'll note in
passing though that it attempts to be as concise as possible,
which is a good thing and a fine thing, but does limit the
scope of both questions and answers.)

---rsk

From martijn.grooten@virusbtn.com  Mon Mar  4 07:46:17 2013
Return-Path: <martijn.grooten@virusbtn.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B428521F8BEF for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 07:46:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 uG-CNF7qnvkW for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 07:46:17 -0800 (PST)
Received: from mx4.sophos.com (mx4.sophos.com [216.47.234.213]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7CE21F8BE7 for <asrg@irtf.org>; Mon,  4 Mar 2013 07:46:17 -0800 (PST)
Received: from mx4.sophos.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 193964E0326 for <asrg@irtf.org>; Mon,  4 Mar 2013 15:46:16 +0000 (GMT)
Received: from ABN-EXCH1A.green.sophos (abn-exch1a.green.sophos [10.100.70.61]) by mx4.sophos.com (Postfix) with ESMTPS id BC9104E00FE for <asrg@irtf.org>; Mon,  4 Mar 2013 15:46:15 +0000 (GMT)
Received: from abn-exch1b.green.sophos ([fe80::dc96:facf:3d2c:c352]) by ABN-EXCH1A.green.sophos ([fe80::67:3150:dacd:910d%15]) with mapi id 14.02.0328.009; Mon, 4 Mar 2013 15:46:14 +0000
From: Martijn Grooten <martijn.grooten@virusbtn.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Thread-Topic: [Asrg] Development of an object assessment format/protocol
Thread-Index: AQHOGNxQAb9aIe4DYkedCXol+NqIjpiVkAvA
Date: Mon, 4 Mar 2013 15:46:14 +0000
Message-ID: <0D79787962F6AE4B84B2CC41FC957D0B20C05A58@abn-exch1b.green.sophos>
References: <20130304132924.GA27928@gsp.org>
In-Reply-To: <20130304132924.GA27928@gsp.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.100.110.133]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Asrg] Development of an object assessment format/protocol
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 15:46:17 -0000

Rich Kulawiec wrote:
> And all of these are great, except: they all use different ways to expres=
s
> information.  Some of them can be queried; some can't.  Some of them carr=
y
> metadata like "how did we decide this?" or 'when did we decide this?" or
> "for further reference, see:" and some don't.
> Some of them support methods for asking narrower/broader questions,
> some of them don't.

Is the reason different sources use different ways to express information t=
he fact that there is no suitable protocol? Or is it a mere consequence of =
the fact that sources have different things they are willing and able to sh=
are?

I think the idea is nice. Whether such a format is really needed I'm not su=
re. I can see how having more information available makes for better decisi=
ons, but I am worried the accuracy gained isn't worth the performance lost.

Perhaps you can come up with examples of where such a protocol would be use=
ful?

Martijn.


________________________________

Virus Bulletin Ltd, The Pentagon, Abingdon, OX14 3YP, England.
Company Reg No: 2388295. VAT Reg No: GB 532 5598 33.

From skull@bofhland.org  Mon Mar  4 08:59:56 2013
Return-Path: <skull@bofhland.org>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB78521F8C2A for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 08:59:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_52=0.6]
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 DafkCIiyVXEL for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 08:59:56 -0800 (PST)
Received: from mithrandir.bofhland.org (mithrandir.bofhland.org [IPv6:2a02:9a8:94::b]) by ietfa.amsl.com (Postfix) with ESMTP id 36B0921F8C20 for <asrg@irtf.org>; Mon,  4 Mar 2013 08:59:55 -0800 (PST)
Received: from enlil.local (baggins.skullkrusher.net [147.123.72.2]) by mithrandir.bofhland.org (Postfix) with ESMTPSA id C6BFD6C376 for <asrg@irtf.org>; Mon,  4 Mar 2013 17:59:51 +0100 (CET)
Message-ID: <5134D304.5040702@bofhland.org>
Date: Mon, 04 Mar 2013 17:59:48 +0100
From: "Emanuele Balla (aka Skull)" <skull@bofhland.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20130304132924.GA27928@gsp.org> <0D79787962F6AE4B84B2CC41FC957D0B20C05A58@abn-exch1b.green.sophos>
In-Reply-To: <0D79787962F6AE4B84B2CC41FC957D0B20C05A58@abn-exch1b.green.sophos>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Development of an object assessment format/protocol
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 16:59:56 -0000

On 3/4/13 4:46 PM, Martijn Grooten wrote:
e protocol? Or is it a
> mere consequence of the fact that sources have different things they
> are willing and able to share?
> 
> I think the idea is nice. Whether such a format is really needed I'm
> not sure. I can see how having more information available makes for
> better decisions, but I am worried the accuracy gained isn't worth
> the performance lost.


As someone who's been thinking and experimenting on this for maybe the
last 3 or 4 years: yes (IMHO) the protocol would be useful.

IMHO (read this post like I had filled it with "IMHO" all over the
place), the reason why a similar protocol won't be a big performance
loss is that probably DNS cache in DNSBL-like lookups is not as useful
as most people would expect...

The problem why it's not been built so far is that those who are mostly
interested in such a protocol being available (data providers, as they
have data they could provide through it) rarely have the resources to
create something like that.

Partly because creating protocols is not their main job.

Partly because they would have to provide both server and client
implementation, otherwise nobody will be able to use their data.

Partly because - to be as smart as DNS- the client needs to be as
"complex" as DNS: redundacy, load-balancing, lowest-latency server
selection, etc.: all the logic has to go in the client, not in the
servers layout (like in "let's run anycast and forget about the
client"), for several reasons

Partly because, if the rest of the industry doesn't follow their lead,
the service will be unusable for most users and will simply never get
traction.

Partly because there're lots of issues about providing/looking_up data
with extreme granularity (privacy, exposure, etc), so these data
providers are not sure the service would be so useful, after all, and
they prefer to just provide the data in a raw format to those who are
smart enough to figure out on their own how to use them.


> Perhaps you can come up with examples of where such a protocol would
> be useful?

Straight to the point: abusive URLs on legit domains
. There's no (easy/effective) way to encode an entire URL in a DNS request.
At least, that's the reason why I've been thinking about this topic for
the last 4 years... :-\


From dhc@dcrocker.net  Mon Mar  4 09:07:23 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C63121F85DF for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 09:07:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Gwuv2jB5feUH for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 09:07:17 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 203E221F8648 for <asrg@irtf.org>; Mon,  4 Mar 2013 09:07:17 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r24H6vnL018293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 4 Mar 2013 09:06:58 -0800
Message-ID: <5134D4AF.8060101@dcrocker.net>
Date: Mon, 04 Mar 2013 09:06:55 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20130304132924.GA27928@gsp.org>
In-Reply-To: <20130304132924.GA27928@gsp.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 04 Mar 2013 09:06:58 -0800 (PST)
Subject: Re: [Asrg] Development of an object assessment format/protocol
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net, Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 17:07:23 -0000

On 3/4/2013 5:29 AM, Rich Kulawiec wrote:
> We need, I think, a mechanism via which we can ask more complex questions
> and get more comprehensive answers.  We need a mechanism which isn't
> a hack on top of DNS, but which has been developed from the ground up
> specifically for this purpose.


By way of exploring a baseline, how does what you are asking for differ 
from the Repute work:


    http://datatracker.ietf.org/wg/repute/charter/

Can it be a value-add enhancement to it? If not, why?

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From rsk@gsp.org  Mon Mar  4 09:10:13 2013
Return-Path: <rsk@gsp.org>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C49BC21F8891 for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 09:10:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 BLomQp4+aO-f for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 09:10:13 -0800 (PST)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by ietfa.amsl.com (Postfix) with ESMTP id E705221F8629 for <asrg@irtf.org>; Mon,  4 Mar 2013 09:10:12 -0800 (PST)
Received: from gsp.org (localhost.firemountain.net [127.0.0.1]) by taos.firemountain.net (8.14.6/8.14.6) with SMTP id r24HABN7014631 for <asrg@irtf.org>; Mon, 4 Mar 2013 12:10:11 -0500 (EST)
Date: Mon, 4 Mar 2013 12:10:10 -0500
From: Rich Kulawiec <rsk@gsp.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <20130304171010.GA3191@gsp.org>
References: <20130304132924.GA27928@gsp.org> <0D79787962F6AE4B84B2CC41FC957D0B20C05A58@abn-exch1b.green.sophos>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0D79787962F6AE4B84B2CC41FC957D0B20C05A58@abn-exch1b.green.sophos>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [Asrg] Development of an object assessment format/protocol
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 17:10:13 -0000

On Mon, Mar 04, 2013 at 03:46:14PM +0000, Martijn Grooten wrote:
> Is the reason different sources use different ways to express
> information the fact that there is no suitable protocol? Or is it a
> mere consequence of the fact that sources have different things they
> are willing and able to share?

That's a pair of great questions, and I can see reasons to answer "yes"
to both.

On the one hand: there's no standardized way to do this (beyond DNSBLs
and RHSBLs, which we've piggybacked on DNS).  On the other hand, you're
right, different people are making different statements about different
entities -- IP addresses, domains, web pages, email addresses, etc. --
so *if* there existed some standardized way to express this, it would
have to let them say the same things they're saying now...because otherwise
they'd probably have no reason to use it.

So I dunno.

> Perhaps you can come up with examples of where such a protocol would be useful?

Sure.  Let me show these using some pseudocode, just to illustrate the
concept.  Let's presume that example.org is asking questions of example.com.

	Question:
		query-proto-version = 1.0
		query-to = blah.example.com
		query-time = Mon Mar  4 16:06:37 UTC 2013
		object type = ipv4
		object value = 192.168.0.3
		object query = spam source?
	Answer:
		answer-proto-version = 1.1
		answer-from = blah.example.com
		answer-time = Mon Mar  4 16:06:38 UTC 2013
		answer-valid-time = Fri Mar  1 13:05:00 UTC 2013
		answer-expiration-time = Fri Mar  8 13:05:00 UTC 2013
		answer = yes

This is the equivalent of a DNSBL check -- except that the answer
also contains two more items.   It includes an "answer-valid-time",
which could be "the time that we started giving out this answer",
and "answer-expiration-time", which could be the time that this
answer is scheduled to expire.  Thus the former could mean "we listed
this IP address at 1:05 PM last Friday, because that's when our sensors
told us to" and the latter could mean "unless we see a reason to
extend the listing, we're going to drop it at 1:05 PM this Friday".

	Question:
		query-proto-version = 1.0
		query-to = blah.example.com
		query-time = Mon Mar  4 16:06:37 UTC 2013
		object type = URL
		object value = http://example.net/some/page.html
		object query = infected with malware?
	Answer:
		answer-proto-version = 1.1
		answer-from = blah.example.com
		answer-time = Mon Mar  4 16:06:38 UTC 2013
		answer-valid-time = Fri Mar  1 14:05:00 UTC 2013
		answer-expiration-time = Fri Mar  8 14:05:00 UTC 2013
		answer = no

This is a very similar Q/A: in this case the answer is negative,
but it also has an expiration time. (Let's presume that example.com
is crawling sites at weekly intervals, thus there is no reason for
this answer to [possibly] change until the next crawl is done.
The requestor might be okay with this answer, or it might want
a more recent one -- in which case it will need to ask someone else.)

	Question:
		query-proto-version = 1.0
		query-to = blah.example.com
		query-time = Mon Mar  4 16:06:37 UTC 2013
		object type = ASN
		object value = 123456789
		object query = hijacked?
	Answer:
		answer-proto-version = 1.1
		answer-from = blah.example.com
		answer-time = Mon Mar  4 16:06:38 UTC 2013
		answer-valid-time = Fri Mar  1 14:10:00 UTC 2013
		answer-expiration-time = Fri Apr  5 14:10:00 UTC 2013
		answer = yes
		answer-additional: http://example.com/hijacks/123456789

Also very similar.  I posited a much longer expiration time because
this is probably not going to be a quickly-remediated problem.  I've
also shown an addition to the answer, which in this case is just a URL
where something consumable by humans might be found.

To expand on those just a little bit: "object type" could probably
encompass things like:

	IPv4/IPv6 addresses
	networks (by handle?) (by CIDR?)
	ASNs
	domains, subdomains, hosts
	URLs
	email addresses

"object query" could include the examples above, and much more obviously,
but should exclude those things that we already have ways to find out,
e.g., this should not be a way to query for a DNS A record, because
that's just kinda silly.

There are two (at least two) ways to go with this: one would be to
make it concise and use UDP.  Another would be to make it verbose
and use TCP. (Insert long discussion here about performance tradeoffs.)
I'm not sure that this is worth getting into unless the high-level
idea flies: if we don't actually need a standard format and a standard
protocol that uses it, then those tradeoffs don't matter.

---rsk


From martijn.grooten@virusbtn.com  Mon Mar  4 10:28:41 2013
Return-Path: <martijn.grooten@virusbtn.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F61D21F8DE5 for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 10:28:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 iVzKMoVfemPb for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 10:28:40 -0800 (PST)
Received: from mx4.sophos.com (mx4.sophos.com [216.47.234.213]) by ietfa.amsl.com (Postfix) with ESMTP id 9418E21F8E0C for <asrg@irtf.org>; Mon,  4 Mar 2013 10:28:40 -0800 (PST)
Received: from mx4.sophos.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id F134B4E034C for <asrg@irtf.org>; Mon,  4 Mar 2013 18:28:38 +0000 (GMT)
Received: from ABN-EXCH1A.green.sophos (abn-exch1a.green.sophos [10.100.70.61]) by mx4.sophos.com (Postfix) with ESMTPS id 7C29E4E0343 for <asrg@irtf.org>; Mon,  4 Mar 2013 18:28:38 +0000 (GMT)
Received: from abn-exch1b.green.sophos ([fe80::dc96:facf:3d2c:c352]) by ABN-EXCH1A.green.sophos ([fe80::67:3150:dacd:910d%15]) with mapi id 14.02.0328.009; Mon, 4 Mar 2013 18:28:37 +0000
From: Martijn Grooten <martijn.grooten@virusbtn.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Thread-Topic: [Asrg] Development of an object assessment format/protocol
Thread-Index: AQHOGNxQAb9aIe4DYkedCXol+NqIjpiVkAvAgAAxlwCAAAvtcA==
Date: Mon, 4 Mar 2013 18:28:36 +0000
Message-ID: <0D79787962F6AE4B84B2CC41FC957D0B20C05B52@abn-exch1b.green.sophos>
References: <20130304132924.GA27928@gsp.org> <0D79787962F6AE4B84B2CC41FC957D0B20C05A58@abn-exch1b.green.sophos> <5134D304.5040702@bofhland.org>
In-Reply-To: <5134D304.5040702@bofhland.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.100.110.133]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Asrg] Development of an object assessment format/protocol
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 18:28:41 -0000

Emanuele Balla (aka Skull) wrote:
> Straight to the point: abusive URLs on legit domains . There's no
> (easy/effective) way to encode an entire URL in a DNS request.
> At least, that's the reason why I've been thinking about this topic for t=
he last
> 4 years... :-\

Can't you just use HTTP for that? There is an easy and effective way to enc=
ode URLs in HTTP - and HTTP is pretty good at returning all sorts of respon=
ses: a single character (0=3Dgood, 1=3Dbad), some XML, some JSON, something=
 else. There is obviously some overhead from the TCP connection and the req=
uest and response headers, but I wonder if there are many cases in which:
- this overhead is a huge problem;
- the request can't easily be 'encoded' into DNS.

Rich's examples all seem pretty easy to encode into DNS, but more important=
ly, to me they shout for HTTP POST. When Rich's idea of asking for context =
(expiration time, range to which the answer applies) is used well, it could=
 actually save you a lot of further requests.

Note: some web proxies are already using HTTP to make requests about whethe=
r a particular URL is bad. In web proxies time really does matter (delaying=
 all web pages by a second seriously affects perceived performance).

Martijn.


________________________________

Virus Bulletin Ltd, The Pentagon, Abingdon, OX14 3YP, England.
Company Reg No: 2388295. VAT Reg No: GB 532 5598 33.

From prvs=077541D51C=paul@pscs.co.uk  Mon Mar  4 11:00:53 2013
Return-Path: <prvs=077541D51C=paul@pscs.co.uk>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78C2D21F89EF for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 11:00:53 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hkj1qwIelXTg for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 11:00:53 -0800 (PST)
Received: from mail.pscs.co.uk (mail.pscs.co.uk [188.65.177.237]) by ietfa.amsl.com (Postfix) with ESMTP id DC83121F8D44 for <asrg@irtf.org>; Mon,  4 Mar 2013 11:00:51 -0800 (PST)
Received: from lmail.pscs.co.uk ([82.68.5.206]) by mail.pscs.co.uk ([188.65.177.237] running VPOP3) with ESMTP for <asrg@irtf.org>; Mon, 4 Mar 2013 18:49:58 -0000
Received: from [192.168.57.43] ([92.27.146.145]) by lmail.pscs.co.uk ([192.168.66.70] running VPOP3) with ESMTP for <asrg@irtf.org>; Mon, 4 Mar 2013 18:43:47 -0000
Message-ID: <5134EB63.1020801@pscs.co.uk>
Date: Mon, 04 Mar 2013 18:43:47 +0000
From: Paul Smith <paul@pscs.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: asrg@irtf.org
References: <20130304132924.GA27928@gsp.org> <0D79787962F6AE4B84B2CC41FC957D0B20C05A58@abn-exch1b.green.sophos> <5134D304.5040702@bofhland.org> <0D79787962F6AE4B84B2CC41FC957D0B20C05B52@abn-exch1b.green.sophos>
In-Reply-To: <0D79787962F6AE4B84B2CC41FC957D0B20C05B52@abn-exch1b.green.sophos>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-Sender: paul
X-Server: VPOP3 Enterprise V6.0 - Registered
X-Organisation: Paul Smith Computer Services
Subject: Re: [Asrg] Development of an object assessment format/protocol
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 19:00:53 -0000

On 04/03/2013 18:28, Martijn Grooten wrote:
> Emanuele Balla (aka Skull) wrote:
>> Straight to the point: abusive URLs on legit domains . There's no
>> (easy/effective) way to encode an entire URL in a DNS request.
>> At least, that's the reason why I've been thinking about this topic for the last
>> 4 years... :-\
> Can't you just use HTTP for that?

Well, HTTP seems a bit 'heavyweight' for this to me. That's one of the 
advantages of DNS - it's UDP, so no packets to set up short-lived 
sessions. (Other advantages, AFAICS, are distributed caching, and 
widespread support)

I suppose you could keep a HTTP session open for a while, but, you'd 
need a beefy server to handle the zillions of sessions you'd have to 
have open at once. DNS doesn't have 'sessions' so you don't have this 
problem.

OTOH, a disadvantage of DNS is that it's UDP, so you have to handle 
retries etc yourself.

So, if you're looking at something like this, you need to first of all 
think UDP or TCP? UDP is easy & quick to have lots of packets flying 
around, but you have extra work to handle retries, and some of the 
benefit of UDP could be gained by just having long-lived sessions 
between reputation source and reputation checker. But, this may cause 
issues for servers and firewalls (could a typical server/firewall have 
hundreds of thousands of active TCP sessions? A NAT firewall would die 
quickly, but could a non-NAT firewall cope?)

If you decide UDP is the most efficient, then DNS is very attractive, 
because you already have distributed caching 'built-in' to the Internet 
infrastructure, but if we're willing to dump that capability, then I'm 
fairly sure we could come up with something with the suitable 
capabilities which would fit in a UDP packet size - once we can decide 
what the 'suitable capabilities' are...

If TCP is the way to go, then the world is your oyster, but I'd be 
concerned about speed and the server requirements. Anyone know how many 
queries someone like Spamhaus gets an hour?



-

Paul Smith Computer Services
Tel: 01484 855800
Vat No: GB 685 6987 53

From bzs@world.std.com  Mon Mar  4 11:59:10 2013
Return-Path: <bzs@world.std.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1601421F8D73 for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 11:59:10 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0-yMErw5IQ8N for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 11:59:09 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id 29E7321F8D59 for <asrg@irtf.org>; Mon,  4 Mar 2013 11:59:09 -0800 (PST)
Received: from world.std.com (root@world.std.com [192.74.137.5]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r24JwiOp012911; Mon, 4 Mar 2013 14:58:46 -0500
Received: (from bzs@localhost) by world.std.com (8.13.6/8.13.6) id r24JwiVD021423; Mon, 4 Mar 2013 14:58:44 -0500 (EST)
From: Barry Shein <bzs@world.std.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <20788.64756.472942.424801@world.std.com>
Date: Mon, 4 Mar 2013 14:58:44 -0500
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-Reply-To: <20130304132924.GA27928@gsp.org>
References: <20130304132924.GA27928@gsp.org>
X-Mailer: VM 7.07 under Emacs 21.2.2
Subject: Re: [Asrg] Development of an object assessment format/protocol
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 19:59:10 -0000

My only thought is how much the coming era of 1,000+ new top-level
domains, internationalization of the DNS space, and IPv6 will motivate
new thinking vis a vis spam and related.

I'm sometimes quoted, from back around 1990, as joking that I
remembered the good old days when you could read all the Usenet
newsgroup topics in one day as they breached 100,000 groups -- an echo
of an older comment by someone else that they remembered when you
could read all the content every day.

Soon, "I remember the good old days when you could recognize all the
TLDs, including the ccTLDs, and had all the gTLDs memorized and could
even say why the were each created!" (other than perhaps .COOP :-)?

So, for example, if your (Joe or Jane End-User) risk assessment of a
.COM or a recognizable string in .COM is lower than some others like
maybe random-noise.country-i-never-heard-of what does it mean when
that spreads to 1,000 or more, possibly closer to 2,000, TLDs alone
let alone internationalization? How can filters even be kept up
without automation? etc. What will they make of punycode domains? etc.

Same question for 128-bit addressing which if nothing else may let
miscreants be much more highly motile.

And I'll toss in the progress of smart phone technology for free, who
thought even a few years ago I could carry around so much spam in my
pants pocket! Now, 64GB is de rigeur. And how go the smartphone
botnets? shudder.

Maybe it's just the calm before the storm?

-- 
        -Barry Shein

The World              | bzs@TheWorld.com           | http://www.TheWorld.com
Purveyors to the Trade | Voice: 800-THE-WRLD        | Dial-Up: US, PR, Canada
Software Tool & Die    | Public Access Internet     | SINCE 1989     *oo*

From skull@bofhland.org  Mon Mar  4 12:42:04 2013
Return-Path: <skull@bofhland.org>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17F4E21F9000 for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 12:42:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599]
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 Y+NEHF79rVwd for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 12:42:03 -0800 (PST)
Received: from mithrandir.bofhland.org (mithrandir.bofhland.org [IPv6:2a02:9a8:94::b]) by ietfa.amsl.com (Postfix) with ESMTP id 5AC1821F8FDF for <asrg@irtf.org>; Mon,  4 Mar 2013 12:41:40 -0800 (PST)
Received: from enlil.local (baggins.skullkrusher.net [147.123.72.2]) by mithrandir.bofhland.org (Postfix) with ESMTPSA id E364A6C376 for <asrg@irtf.org>; Mon,  4 Mar 2013 21:41:37 +0100 (CET)
Message-ID: <513506FF.9050205@bofhland.org>
Date: Mon, 04 Mar 2013 21:41:35 +0100
From: "Emanuele Balla (aka Skull)" <skull@bofhland.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20130304132924.GA27928@gsp.org> <0D79787962F6AE4B84B2CC41FC957D0B20C05A58@abn-exch1b.green.sophos> <5134D304.5040702@bofhland.org> <0D79787962F6AE4B84B2CC41FC957D0B20C05B52@abn-exch1b.green.sophos>
In-Reply-To: <0D79787962F6AE4B84B2CC41FC957D0B20C05B52@abn-exch1b.green.sophos>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Development of an object assessment format/protocol
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 20:42:04 -0000

On 3/4/13 7:28 PM, Martijn Grooten wrote:
>> Straight to the point: abusive URLs on legit domains . There's no
>> (easy/effective) way to encode an entire URL in a DNS request.
>> At least, that's the reason why I've been thinking about this topic for the last
>> 4 years... :-\
> 
> Can't you just use HTTP for that?

You could, for sure.
But you won't have redundancy/loaf_balancing/best_peer_selection in the
client: you'd need to wrap something around it (through SRV records for
the client, and clustering, anycast, geoDNS to direct the client to the
best server, etc).
This will increase the requirements for running such services significantly.

Also you'll move the entire thing to TCP, requiring sessions/sockets,
much more expensive to scale properly, and also much more susceptible to
DDoS than UDP-based protocols.

Then take into account the amount of queries major DNSBLs satisfy at the
moment (on DNS, where there's at least some caching in place): >100Kqps.

All in all, I'm quite confident there are not many entities wanting to
provide service to the internet at large over a similar infrastructure...




From johnl@iecc.com  Mon Mar  4 12:53:01 2013
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D294521F8D6E for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 12:53:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.6
X-Spam-Level: 
X-Spam-Status: No, score=-105.6 tagged_above=-999 required=5 tests=[AWL=5.599,  BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, 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 5PpgcNW-yHda for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 12:53:01 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id DB99B21F8D42 for <asrg@irtf.org>; Mon,  4 Mar 2013 12:53:00 -0800 (PST)
Received: (qmail 3614 invoked from network); 4 Mar 2013 20:52:57 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 4 Mar 2013 20:52:57 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=513509a9.xn--9vv.k1303; i=johnl@user.iecc.com; bh=BOGiraB3GxujkIFBLJtNUvs5j5Go3Tnhc+W6gKWvGzc=; b=Jg5yU3ohKccUu3aR2n8MoxLH3UFAWwIesRpnS72IelYkMGrwjkdelpwt98xVAs0t4c6rh9eVjsl9Hzbks9kRQ5T4A9jVsQuybyMENkbJglGI0IU+wLhY3mJOQnKPncUzyMmP0eLyOBO6OWoGATrfHoagP87k0TqHe0lYktrOh1A=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=513509a9.xn--9vv.k1303; olt=johnl@user.iecc.com; bh=BOGiraB3GxujkIFBLJtNUvs5j5Go3Tnhc+W6gKWvGzc=; b=QPqtEn+9hrIrmHjRMOcHUwZD/VzEav4yzxLX4zGeqY0ZuvfQOTuz2W7xhNkPjaBr4ctRMDL3KTgMBjsdopZlcUQhAoi6welzXrQ7/e7YhZ8X+eBBdKds1Dal/i1XbvJMvsT8zYxF/lwKI6EQ+IfqkkxCWpX7I3+oRiO9PCcs8gE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 4 Mar 2013 20:52:35 -0000
Message-ID: <20130304205235.99260.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <20130304050758.GQ26133@chaosreigns.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] The end of the ASRG
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 20:53:01 -0000

>> There's plenty of anti-spam research to do, and a fair amount being
>> done, but it's not being done here.
>
>Where is it being done?

A lot of universities.  Papers show up all over the place.


From johnl@iecc.com  Mon Mar  4 12:53:42 2013
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D979821F8DFF for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 12:53:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.4
X-Spam-Level: 
X-Spam-Status: No, score=-108.4 tagged_above=-999 required=5 tests=[AWL=2.800,  BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, 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 9zAyI584Bs4z for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 12:53:41 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 20E1021F8DFC for <asrg@irtf.org>; Mon,  4 Mar 2013 12:53:41 -0800 (PST)
Received: (qmail 3824 invoked from network); 4 Mar 2013 20:53:41 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 4 Mar 2013 20:53:41 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=513509d4.xn--30v786c.k1303; i=johnl@user.iecc.com; bh=ekParL6rVqBhGiFu5BO/zxTacwAJMXamceL1NXgiDLU=; b=aeH/YELvWJXmtN9ERuD+tOOGfB1Moy0diIRqiR52WiaTalCQ2z0T7B9sAVJeKJTsfYsFc7N4RZfBiN+Y8l8yJdNQPRS157Q4dH+2GPLhy0vwM7NDSFuWa8ThWX3I2C0rsKMSO3wlnb1NZIFXGuZmWPcgPP4qsE9K/GhwF52hWEc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=513509d4.xn--30v786c.k1303; olt=johnl@user.iecc.com; bh=ekParL6rVqBhGiFu5BO/zxTacwAJMXamceL1NXgiDLU=; b=BRPaxu2Rn942v2e9DVkjEBDFjdBL0BmafTFnqkfOkURR5wQj6nkuo8Cc8gveD1B9zB3ygv6pS5WUhw2xXdPR+mV6AcPJVAHUnUECzeeMwRw+o0GjbXHaALHww+jU8Fb7f4z18OZ2t41Ed9VtHxMpkktRX9/d3wbxgwx9HFLcRrA=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 4 Mar 2013 20:53:18 -0000
Message-ID: <20130304205318.99282.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <513459D3.4090603@tana.it>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] The end of the ASRG
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2013 20:53:42 -0000

>I'd hope this mailing list is going to remain up indefinitely too.

I'll ask.  If not, it's easy enough for me to move it to the list manager
where I already have about 100 lists.

R's,
John

From johnl@iecc.com  Mon Mar  4 17:29:03 2013
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94B6621F8621 for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 17:29:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.333
X-Spam-Level: 
X-Spam-Status: No, score=-109.333 tagged_above=-999 required=5 tests=[AWL=1.866, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, 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 Yh1RwLAgdAHP for <asrg@ietfa.amsl.com>; Mon,  4 Mar 2013 17:29:02 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id A0D8B21F85D9 for <asrg@irtf.org>; Mon,  4 Mar 2013 17:29:02 -0800 (PST)
Received: (qmail 66988 invoked from network); 5 Mar 2013 01:29:02 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 5 Mar 2013 01:29:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=51354a5d.xn--btvx9d.k1303; i=johnl@user.iecc.com; bh=urlclwBe9siSZcEh4GRUQKdMTNaxQz4sQ2/x/bYwKq4=; b=kHya0/KqZvL5rrNm+bKAr0adx5qfMo36iC8btfFQ/DZLRxXw6Qi+OT0bRNcd/YZiQiOVQRqNK5dSaS7BFB9GIjNmK0KYselI8NQSB0eZ5o1LfyZz7of0IqyITRIhqwYDPmrHS47rgRIm+ynEE2eV6s91Tsv+Gf4k/1QifQOP0As=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=51354a5d.xn--btvx9d.k1303; olt=johnl@user.iecc.com; bh=urlclwBe9siSZcEh4GRUQKdMTNaxQz4sQ2/x/bYwKq4=; b=IhE6TLDDBtcPjQ408XgLJB5psBxLhQCr0uolYXCIueXrJjII9cau6k72xp6/K8G4C+XY4UkigAToIMwAQkynJzHSO+L9LG5trY3igQWwYBintSIcYfOvO1ElUWN/vd7K9G9iDLCo5bZoasL2NFnxe47ebC/NcxndbE5CYDEK5g0=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 5 Mar 2013 01:28:39 -0000
Message-ID: <20130305012839.160.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <20130304132924.GA27928@gsp.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] Development of an object assessment format/protocol
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Mar 2013 01:29:03 -0000

In article <20130304132924.GA27928@gsp.org> you write:
>I've been thinking about this for a long time, and would like to find
>out what others have been doing in this area (if anything) and whether
>this is a topic we can or should collectively pursue.

Have you followed what the REPUTE working group did?  Its goal was to
come up with a way to publish reputation information more general than
the handful of bits you can get from a DNSBL.  There were some
interesting ideas but it's run out of gas and is about to be wound up.

draft-ietf-repute-considerations-00.txt
draft-ietf-repute-email-identifiers-06.txt
draft-ietf-repute-model-03.txt
draft-ietf-repute-media-type-05.txt
draft-ietf-repute-query-http-04.txt

If people had stuff they wanted to do, I expect it could be spun up
again.  If they were sufficiently researchy and people had concrete
plans, I could probably persuade Lars to let the ASRG continue until
they were done.



From johnl@iecc.com  Sat Mar 16 14:44:29 2013
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E77821F8539 for <asrg@ietfa.amsl.com>; Sat, 16 Mar 2013 14:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 gfTslOqyhCvl for <asrg@ietfa.amsl.com>; Sat, 16 Mar 2013 14:44:29 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id AE16C21F8512 for <asrg@irtf.org>; Sat, 16 Mar 2013 14:44:28 -0700 (PDT)
Received: (qmail 11133 invoked from network); 16 Mar 2013 21:44:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:vbr-info:user-agent:cleverness; s=2b7c.5144e7bc.k1303; bh=R6JPnX/SS99Hi8JMYs5W5ISddVP8I+EZnnwrxIQDRUk=; b=PTGZuFfYwrHo4TwNTJzk3vVOi11vR3anTIyH7dK14qdiuzwmq6e+Bf5LqKv3NR73jQmPToR0lhGXyPBtgNdQDXsu9O55RQ3ZjZKj8fahtLQg7VxZCZxtY69YZDHDZ3EmYCUiqZkx/BGYBkhh1WDu0eGi4wd2y4YoeWbrvV1qEys=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 16 Mar 2013 21:44:06 -0000
Date: 16 Mar 2013 17:44:27 -0400
Message-ID: <alpine.BSF.2.00.1303161741110.311@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Anti Spam Research Group" <asrg@irtf.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Subject: [Asrg] ASRG shut down and list move
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Mar 2013 21:44:29 -0000

As I said last week, the IRTF ASRG is closing due to lack of research 
activity.

People have expressed interest in continuing the mailing list, so I'm 
moving it to a server I run.  The new list name is asrg@lists.gurus.org, 
so asrg presumably will now be Anti Spam Research Gurus.

You will shortly receive a welcome message from the new list.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From lars@netapp.com  Mon Mar 18 06:23:44 2013
Return-Path: <lars@netapp.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3032921F8651; Mon, 18 Mar 2013 06:23:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.524
X-Spam-Level: 
X-Spam-Status: No, score=-10.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 l+l+EGxwDREK; Mon, 18 Mar 2013 06:23:43 -0700 (PDT)
Received: from mx1.netapp.com (mx1.netapp.com [216.240.18.38]) by ietfa.amsl.com (Postfix) with ESMTP id 86A7521F8951; Mon, 18 Mar 2013 06:23:43 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.84,865,1355126400"; d="scan'208";a="247407288"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx1-out.netapp.com with ESMTP; 18 Mar 2013 06:23:43 -0700
Received: from vmwexceht05-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.77.35]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r2IDNgWc019805; Mon, 18 Mar 2013 06:23:43 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.218]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0342.003; Mon, 18 Mar 2013 06:23:42 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "asrg@irtf.org" <asrg@irtf.org>
Thread-Topic: Closing the Anti Spam Research Group (ASRG)
Thread-Index: AQHOI9vP1dBd0m/s+UydUc97c/qT0A==
Date: Mon, 18 Mar 2013 13:23:42 +0000
Message-ID: <4B4BF234-5708-480A-8E4C-FC3F19890F8D@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3A3309327595184A99BF64B04F516FC3@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "irtf-announce@irtf.org" <irtf-announce@irtf.org>
Subject: [Asrg] Closing the Anti Spam Research Group (ASRG)
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "irtf-chair@irtf.org" <irtf-chair@irtf.org>, Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2013 13:23:44 -0000

Hi,

as announced by the chair, the Anti Spam Research Group (ASRG) has conclude=
d their work and will be closed. The IRTF mailing list will close along wit=
h the group, but the former chair has created a new list at asrg@lists.guru=
s.org for folks to continue the discussion.

I would like to thank all participants, and especially the RG chairs, for a=
ll their efforts over the years.

Lars Eggert
IRTF Chair=
