draft-jevans-phishing-xml (was Re: [feedback-report] [Fwd: RE: Usage Scenarios])

[J.D. Falk]

On 6/3/05 7:48 AM, Yakov Shafranovich forwarded:

>I'd be interested in a sanity check on overlap with the jevans/cain
>driven IODEF extensions for Phish reports
>http://www.ietf.org/internet-drafts/draft-jevans-phishing-xml-00.txt
>  
>
 [ . . . ]

>Does anyone has informed opinions/comment on the areas where the two
>overlap?
>  
>
Looking over draft-jevans-phishing-xml, I'd say the overlap in use cases 
is small.  We should probably call out that an abuse feedback report 
with a Feedback-Type of  "phishing" may in some circumstances serve the 
same purpose as a PhishingReport with a PhishType of "email", but the 
structure, requirements, and implied purpose of each format differ widely.

I could see the two standards working in concert in a scenario such as 
when a bunch of end users click "report phishing" button in their MUA, 
which causes abuse feedback reports to be generated and sent to the 
Message Sender's ISP; these individual reports are also aggregated into 
a PhishingReport that is distributed to all of the different groups 
which track phishing.

-- 
J.D. Falk, Anti-spam Product Manager, Yahoo! Mail
jdfalk at yahoo-inc.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mipassoc.org/pipermail/abuse-feedback-report/attachments/20050608/8b520ecf/attachment.html