Re: [Sipping] comments on draft-wing-sipping-spam-score-00
Henning Schulzrinne <hgs@cs.columbia.edu> Tue, 04 December 2007 15:41 UTC
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzZuG-0007bJ-Oh; Tue, 04 Dec 2007 10:41:56 -0500
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1IzZuF-0007YS-Ae for sipping-confirm+ok@megatron.ietf.org; Tue, 04 Dec 2007 10:41:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzZuF-0007YB-0m for sipping@ietf.org; Tue, 04 Dec 2007 10:41:55 -0500
Received: from jalapeno.cc.columbia.edu ([128.59.29.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzZuE-0007cp-Jv for sipping@ietf.org; Tue, 04 Dec 2007 10:41:55 -0500
Received: from dhcp-3471.ietf70.org (dhcp-3471.ietf70.org [130.129.52.113]) (user=hgs10 mech=PLAIN bits=0) by jalapeno.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id lB4FfP4i025096 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 4 Dec 2007 10:41:26 -0500 (EST)
Message-Id: <BC2EF934-BE70-4476-9ACB-B96776B018B0@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: Jonathan Rosenberg <jdrosen@cisco.com>
In-Reply-To: <47556743.5050604@cisco.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [Sipping] comments on draft-wing-sipping-spam-score-00
Date: Tue, 04 Dec 2007 10:41:24 -0500
References: <47556743.5050604@cisco.com>
X-Mailer: Apple Mail (2.915)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5
X-Spam-Score: -1.0 (-)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: IETF Sipping List <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org
The mechanism proposed has reasonable precedent in email, with various X-Spam-Score style headers inserted by the local mailserver. The problem in email is that every spam filter seems to have picked some other X- convention or re-use the same header with different formats. I don't think that's an experience that we want to repeat. For example, your message arrived in my inbox with X-Spam-Score: -3 () CU_OK_LISTUNSUB RBL_DNSWL_127.0.9.3 On Dec 4, 2007, at 9:42 AM, Jonathan Rosenberg wrote: > I think a key part of this is that you need to have a trust > relationship with the sender of the score, otherwise its useless. As > with any trust relationship, it requires authentication to make sure > the guy you are talking to is the one you trust. This typically > implies mutual TLS authentication between domains. It also means > that you can't have more than one spam score at a time - just the > one from the previous hop domain. So how would you authenticate and > authorize the sources farther away, as this draft proposes? Clearly, authentication would work (e.g., in the SIP Connect style), but the simpler approach taken today by email also works: The inbound proxy deletes all such headers and the UA has a trust relationship with its proxy. This does not work if the originating domain computes the scores; there, you'd need a trust relationship. This seems pretty similar to PAI. The limitations of this approach need to be clearly documented in the draft. > > > It seems that, unless there is a standardized range and meaning of > values it will be hard to take any action based on this value. This isn't true today for email spam scores, but it is still useful, given that the tests performed by one's inbound proxy tend not to change a whole lot over time. Spam Assassin inserts similar tokens into inbound email and it is then up to the scripts in the email "UA" to decide whether, for example, Chinese characters are a sign of spam or not. Henning _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- [Sipping] comments on draft-wing-sipping-spam-sco… Jonathan Rosenberg
- RE: [Sipping] comments on draft-wing-sipping-spam… Saverio Niccolini
- Re: [Sipping] comments on draft-wing-sipping-spam… Henning Schulzrinne
- Re: [Sipping] comments on draft-wing-sipping-spam… Hannes Tschofenig
- RE: [Sipping] comments on draft-wing-sipping-spam… Dan Wing