Message Context for Internet Mail Eric Burger Emily Candell - - PowerPoint PPT Presentation

▶

Nov 03, 2022 683 likes •804 views

Message Context for Internet Mail Eric Burger Emily Candell Charles Eliot Graham Klyne 49 th IETF VPIM WG draft-ietf-vpim-hint-01.txt 1 Background: Anyone Not Read draft-ietf-vpim-hint? T Context of Message Important to Many User Agents

SLIDE 1

draft-ietf-vpim-hint-01.txt 1

Message Context for Internet Mail

Eric Burger Emily Candell Charles Eliot Graham Klyne 49 th IETF VPIM WG

SLIDE 2

December 2000 draft-ietf-vpim-hint-01.txt 2

Background: Anyone Not Read draft-ietf-vpim-hint?

T Context of Message Important to Many User

Agents (UA)

T Context Can Give Hint to Mail Transfer Agent

(MTA) How to Handle Delivery

T Context Can Give Hint to User Agent (UA) For

User Indication of Message Type (e.g., Icon, Sorting of Inbox, etc.)

T Context Can Give Hint to UA for Presentation

SLIDE 3

December 2000 draft-ietf-vpim-hint-01.txt 3

Approach

T Create Top-Level, RFC 822 Message Attribute,

Message-Context

T Use of Attribute is Local to UA or MTA

S Presentation / Icons S Viewer to Use S Reply Composition Tool S etc.

T Only a Hint: OK if Wrong

S Otherwise Allows Mail Bomb Attack By Sending

Messages With Wrong Message Context

SLIDE 4

December 2000 draft-ietf-vpim-hint-01.txt 4

Message-Context

T Register Message-Context Types With IANA T Envisioned Initial Types

S voice-message S fax-message S video-message S sms-message S mail-message S none S X-mumble

SLIDE 5

December 2000 draft-ietf-vpim-hint-01.txt 5

Normative Changes from –00

T Changed Attribute name from Content-Hint to Message-Context T Enumerated mail-message Context T Added IANA rules

SLIDE 6

December 2000 draft-ietf-vpim-hint-01.txt 6

Informative Changes from -00

T Tidied-up Confusing Language T Moved Detailed Motivation Section to an

Appendix

T Explicitly Stated Sender’s and Receiver’s

Obligations

SLIDE 7

December 2000 draft-ietf-vpim-hint-01.txt 7

Security Considerations

T Consider Header Spoofing T Don’t Willy-Nilly Accept Message-Context: Application!

S Spoofing Message Type to Interpret Binary

Data

SLIDE 8

December 2000 draft-ietf-vpim-hint-01.txt 8

Issues from the VPIM, FAX, and RFC 822 Lists

T Eerily Silent

SLIDE 9

December 2000 draft-ietf-vpim-hint-01.txt 9

Next Steps

T A few editorial changes

S ABNF error (one, not one-or-more) S Rephrase Security Issue S Tightened Language; S.6-> S.7

T Submit –02 draft, Should Be Ready for

WG Last-Call

T Set-up IANA registrations and list

Message Context for Internet Mail

Eric Burger Emily Candell Charles Eliot Graham Klyne 49 th IETF VPIM WG

Background: Anyone Not Read draft-ietf-vpim-hint?

T Context of Message Important to Many User

Agents (UA)

T Context Can Give Hint to Mail Transfer Agent

(MTA) How to Handle Delivery

T Context Can Give Hint to User Agent (UA) For

User Indication of Message Type (e.g., Icon, Sorting of Inbox, etc.)

T Context Can Give Hint to UA for Presentation

Approach

T Create Top-Level, RFC 822 Message Attribute,

Message-Context

T Use of Attribute is Local to UA or MTA

S Presentation / Icons S Viewer to Use S Reply Composition Tool S etc.

T Only a Hint: OK if Wrong

S Otherwise Allows Mail Bomb Attack By Sending

Messages With Wrong Message Context

Message-Context

T Register Message-Context Types With IANA T Envisioned Initial Types

S voice-message S fax-message S video-message S sms-message S mail-message S none S X-mumble

Normative Changes from –00

T Changed Attribute name from Content-Hint to Message-Context T Enumerated mail-message Context T Added IANA rules

Informative Changes from -00

T Tidied-up Confusing Language T Moved Detailed Motivation Section to an

Appendix

T Explicitly Stated Sender’s and Receiver’s

Obligations

Security Considerations

T Consider Header Spoofing T Don’t Willy-Nilly Accept Message-Context: Application!

S Spoofing Message Type to Interpret Binary

Data

Issues from the VPIM, FAX, and RFC 822 Lists

T Eerily Silent

Next Steps

T A few editorial changes

S ABNF error (one, not one-or-more) S Rephrase Security Issue S Tightened Language; S.6-> S.7

T Submit –02 draft, Should Be Ready for

WG Last-Call

T Set-up IANA registrations and list

Thanks!

More Discussion?

Correspondence: e.burger@ ieee.org