Anti-Spam Working Group Draft Agenda
| When: |
Thursday, 5 October - 14:00 -15:30 |
| Where: |
St Johns II |
| Working Group Co-Chairs: |
Rodney Tillotson |
| Working Group Home Page |
A. Administrative Matters - Rodney Tillotson
Download the Presentation - Update RIPE-206 (69 KB)
Priority Items
B . Updates
- Developments in E-mail Abuse; Social Engineering, GIF, Bayes Blinding
- Review of ISP Spam Measures - Pascal Manzano (ENISA)
- Other Developments in Anti-Abuse; Litigation, SPF/SID
- Legislation
- Products
- Recent Working Group Mailing List Discussions
C. Technical Measures
D. Interactions
- Database Working Group, IRT object
- Marketers
- Other ISPs
- Bulk Mailers
- RIRs
- IETF
E. Advice
X. AOB
Y. Future Tasks
Z. Agenda for RIPE 54 and Plenary Presentations
Review of ISP Spam Measures
Presenter: Pascal Manzano (ENISA)
Significant findings from a survey of provisions made by
ESPs in Europe:
Increasing Transparency
- Reporting of security breaches
- Becoming aware of a security or spam problem
Defining Appropriate Security
- State of the art and cost of implementations
- Email security versus privacy
Setting Standards
- Technical and Organisational Security Measures
- Measures to fight spam
Download the Presentation (69 KB)
Title: DKIM and e-mail abuse
Presenter: Eliot Lear (Cisco)
The core DKIM specification is now slated to become a
Proposed Standard, having successfully completed Last Call
and been approved by the Internet Engineering Steering Group
(IESG). It specifies a method for authorities within a
domain to sign a message in such a way that the signature is
verifiable through DNS.
On its own DKIM should be able to reduce the number of bogus
Mail Delivery Notifications (MDNs). Combined with other
mechanisms DKIM provides a necessary set of tools to fight
spam and phishing.
There are unfinished components to DKIM. One in particular
is what is currently known as the Sender Signing Protocol
(SSP). For instance, does a domain sign all of its mail or
just some, and who does it allow to sign its mail? We are
currently reviewing requirements for such a protocol and
will discuss them at the San Diego IETF meeting in November.
Download the Presentation (45 KB)
This agenda was last updated on 29 September 2006. |