Re: [Sipping] IETF Standardization related to SPIT

Juergen Quittek <quittek@netlab.nec.de> Mon, 15 January 2007 22:39 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6aU9-0003qJ-9W; Mon, 15 Jan 2007 17:39:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6aU8-0003p7-36 for sipping@ietf.org; Mon, 15 Jan 2007 17:39:24 -0500
Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6aU6-0008RX-NP for sipping@ietf.org; Mon, 15 Jan 2007 17:39:24 -0500
Received: from [192.168.1.128] (unknown [91.89.53.224]) by kyoto.netlab.nec.de (Postfix) with ESMTP id A31A113CF82; Mon, 15 Jan 2007 23:46:32 +0100 (CET)
Date: Mon, 15 Jan 2007 23:39:20 +0100
From: Juergen Quittek <quittek@netlab.nec.de>
To: Dale.Worley@comcast.net, sipping@ietf.org
Subject: Re: [Sipping] IETF Standardization related to SPIT
Message-ID: <D8D16346B3FE9482EC7F582C@juergen-quitteks-computer.local>
In-Reply-To: <200701152059.l0FKx2nc024065@dragon.ariadne.com>
References: <113091BD57179D4491C19DA7E10CD696983EC5@mx1.office> <200701152059.l0FKx2nc024065@dragon.ariadne.com>
X-Mailer: Mulberry/4.0.5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc:
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

Hi Dale,

--On 15.01.07 21:59 +0100 Dale.Worley@comcast.net wrote:

>
>    From: "Saverio Niccolini" <Saverio.Niccolini@netlab.nec.de>
>
>    In order to start a discussion on the question if there is a need for IETF
>    standards related to SPIT prevention, we have submitted an Internet draft
>    that tries to identify the need for standards on a very high level. Please
>    find it at:
>
>    http://www.ietf.org/internet-drafts/draft-niccolini-sipping-spitstop-00.txt
>
>    We hope to refine this work and elaborate requirements for SPIT-related
>    standards in the next months and we would like to do it together with you.
>
> It seems like this I-D presupposes a particular model of how SPIT
> prevention will be implemented, but it does not make explicit what
> that model is.  Given that SPIT prevention has not yet been
> implemented anywhere, shouldn't we first be discussing the model and
> whether it suffices for SPIT prevention before attempting to
> standardize the details of how the components implied by the model
> will communicate?

We have a running system that we use for testing purposes in our office
and demonstrated at ITU Telecom 06 in Hong Kong.

Of course we had this system in the back of our heads when writing the draft.
But we do not think that our way is the only way to build a SPIT prevention
system.  We tried to be rather generic in the draft and start this discussion
in order to also include other views and alternative systems - maybe better
ones than ours ;-)

Thanks,

    Juergen

> Dale
>
> _______________________________________________
> 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 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