Re: [Rucus] Actions coming out of informal RUCUS meeting at IETF 73
Henning Schulzrinne <hgs@cs.columbia.edu> Thu, 03 September 2009 01:09 UTC
Return-Path: <hgs@cs.columbia.edu>
X-Original-To: rucus@core3.amsl.com
Delivered-To: rucus@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B46E428C10C for <rucus@core3.amsl.com>; Wed, 2 Sep 2009 18:09:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.258
X-Spam-Level:
X-Spam-Status: No, score=-5.258 tagged_above=-999 required=5 tests=[AWL=1.341, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 RAekoprF5aMe for <rucus@core3.amsl.com>; Wed, 2 Sep 2009 18:09:05 -0700 (PDT)
Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by core3.amsl.com (Postfix) with ESMTP id 72D0528C124 for <rucus@ietf.org>; Wed, 2 Sep 2009 18:09:05 -0700 (PDT)
Received: from ice.cs.columbia.edu (ice.cs.columbia.edu [128.59.18.177]) (user=hgs10 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id n82LbHOr001123 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 2 Sep 2009 17:37:20 -0400 (EDT)
Message-Id: <A5391C94-9A1F-4B62-8707-0A3DFCE1C335@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: Dan York <dyork@voxeo.com>
In-Reply-To: <323263D6-B104-4C13-8EC5-1FC4CFC3112C@voxeo.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 02 Sep 2009 17:37:16 -0400
References: <323263D6-B104-4C13-8EC5-1FC4CFC3112C@voxeo.com>
X-Mailer: Apple Mail (2.936)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.65 on 128.59.29.8
Cc: "rucus@ietf.org BoF" <rucus@ietf.org>
Subject: Re: [Rucus] Actions coming out of informal RUCUS meeting at IETF 73
X-BeenThere: rucus@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Reducing Unwanted Communication Using SIP \(RUCUS\)" <rucus.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rucus>, <mailto:rucus-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rucus>
List-Post: <mailto:rucus@ietf.org>
List-Help: <mailto:rucus-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rucus>, <mailto:rucus-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2009 01:09:06 -0000
Digging through some old mail. Has any of this occurred? Henning On Dec 1, 2008, at 12:07 PM, Dan York wrote: > Folks, > > At the informal RUCUS meeting at IETF 73 (see minutes here: http://www.ietf.org/mail-archive/web/rucus/current/msg00347.html > ), part of the discussion was that while the charter for the RUCUS > EG pointed at RFC 5039, that RFC alone does not provide the whole > picture of the issues around SPIT/spam. It was also pointed out > that while many of us may be aware of various different situations > related to SPIT, much of that information has not been captured in > any formal written documents but exists more in email threads or > informal conversations. > > To that end, it was agreed that several people would write Internet- > Drafts that document what is in fact going on out in actual > deployments with regard to voice spam/SPIT and also spam in other > areas. > > The list I have of who said they would submit a document is the > following: > > - David Schwartz about email spam and lessons from there. > - David Schwartz about the XConnect / Kayote experience thus far > with SPIT. > - Hannes Tschofenig about XMPP spam (and Hannes indicated he would > contact Peter St. Andre) > - Hendrik Scholz about the recent German SPIT attack (Jan Seedorf > offered to help) > - Juergen Quitteck/Jan Seedorf about some of the cases they have > seen in their NEC incident database > - Jan Seedorf about the differences between DKIM and SIP Identity > (Jan agreed but indicated he would need the assistance of others in > the room) > > It was agreed that these documents do NOT have to be long. They > could be just a page or two if that is all it takes to summarize the > incident/event/situation. The main point is to provide some written > background information for our continued discussions about SPIT and > what the IETF can or cannot do (which would then lead to the brief > mechanism-focused Internet-Drafts that are discussed in the RUCUS > charter). > > We also agreed that these documents would be submitted as Internet- > Drafts because they then fit within the IETF workflow and are a > standard format that others involved with the IETF (but not > necessarily RUCUS) can find and understand. > > We did not set a deadline at the meeting, but I would suggest that > if we could perhaps aim to have these brief documents put together > by the end of this month (Dec 2008) or by, say, January 15th, that > would help. I realize with holidays that may be tough, but as soon > as possible would be great. I'd like to make the case to the ADs > that RUCUS should have a formal time slot at IETF 74, but for that > to occur we need to have some forward momentum. If we could have > these summary documents in by mid-January, that gives us some time > to pull together some mechanism-related drafts before the March > meeting in SF that could then warrant some real face-to-face > discussion. > > Thanks to everyone who volunteered to write a document - and if > there are others on this list who want to contribute a short > document about experiences you have seen related to spam in general > or specifically SPIT, please *do*! > > Thanks, > Dan > > -- > Dan York, CISSP, Director of Emerging Communication Technology > Office of the CTO Voxeo Corporation dyork@voxeo.com > Phone: +1-407-455-5859 Skype: danyork http://www.voxeo.com > Blogs: http://blogs.voxeo.com http://www.disruptivetelephony.com > > Build voice applications based on open standards. > Find out how at http://www.voxeo.com/free > > > > > > _______________________________________________ > Rucus mailing list > Rucus@ietf.org > https://www.ietf.org/mailman/listinfo/rucus >
- [Rucus] Actions coming out of informal RUCUS meet… Dan York
- Re: [Rucus] Actions coming out of informal RUCUS … Peter Saint-Andre
- Re: [Rucus] Actions coming out of informal RUCUS … Victor Pascual Ávila
- Re: [Rucus] Actions coming out of informal RUCUS … Hendrik Scholz
- Re: [Rucus] Actions coming out of informal RUCUS … Hendrik Scholz
- Re: [Rucus] Actions coming out of informal RUCUS … Dan York
- Re: [Rucus] Actions coming out of informal RUCUS … Henning Schulzrinne