1 / 10

Bounce Address Tag Validation (BATV) “Was use of the bounce address authorized?”

D. Crocker Brandenburg InternetWorking mipassoc.org/batv 03/08/05 13:13. MIPA. Bounce Address Tag Validation (BATV) “Was use of the bounce address authorized?”. Who. Specified in. Originator (author). Content – From/Resent-From. Submitter into transfer service.

osborn
Download Presentation

Bounce Address Tag Validation (BATV) “Was use of the bounce address authorized?”

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. D. Crocker Brandenburg InternetWorking mipassoc.org/batv 03/08/05 13:13 MIPA Bounce Address Tag Validation (BATV)“Was use of the bounce address authorized?”

  2. Who Specified in Originator (author) Content– From/Resent-From Submitter into transfer service Content –Sender/Resent-Sender Return address (bounces) Envelope –Mail-FromContent –Return-Path Sending Relay Envelope –HELO/EHLO Content –Received header Receiving Relay Content –Received header Basic Email Roles

  3. Bounce Addresses Abuse • Redirecting flood of bounces • Spam sends to many invalid addresses, thereby causing masses of bounces. • Spammers specify stray bounce addresses – like yours -- just to get the traffic off the sending service • Backdoor trojan • Bounce message, itself, might contain dangerous content • Denial of service • The flood of messages can cripple the bounce receiving site

  4. Bounce Generation IntermediateRelay Bounce Generation MSA MDA MTA MTA MTA MDA MTA Bounce Receipt Evaluation Venues SignMailFrom

  5. Bounce Address Validation Goals • Bounce recipient delivery agent • Should I deliver this bounce? • Bounce originator • Should I create this bounce? • And by the way… • If the bounce address is invalid, the entire message is probably invalid • If we can detect forged mail, we do not need to worry about its bounce address

  6. BATV • Sign envelope Mail-From address • Protect against simple bounce address forgery • Possibly protect against unauthorized re-use of signature • Submission Agent adds sig to bounce address MAIL FROM mailbox@domain MAIL FROM sig-scheme=mailbox/sig-data@domain • Multiple signature schemes Symmetric – can only be validated by signer’s admin Public – can be validated by relays on original path

  7. A Symmetric BATV Signature • Originating site uses any signing scheme • BATV spec provides a simple version joe-user@example.com prvs=joe-user/tag-val@example.com tag-val = Encryption of(day address will expire,original mailbox@domain)

  8. Public BATV Signature • Same style as for symmetric key approach • Except that originating site uses symmetric key and the evaluating site must obtain the public key • Public key distribution is the core difficulty • Therefore, piggyback the effort on an existing message encryption effort, like DomainKeys and Identified Internet Mail • Unfortunately, no existing public key-based message signing effort has widespread support… yet

  9. Status • Several rounds of specification and open comment • Now recruiting field experience • Plan to pursue IETF standardization

  10. To follow-up… • Mailing list http://mipassoc.org/mailman/listinfo/ietf-clear • BATV specification http://ietf.org/internet-drafts/… • Bounce Address Tag Validation (BATV) draft-levine-mass-batv-00.txt • Internet mail architecture http://bbiw.net/current.html#email • draft-crocker-email-arch-03.txt

More Related