1 / 6

Edmon Chung, Afilias edmon@afilias

draft-ietf-eai-mailinglist-00.txt Mailing Lists and Internationalized Email Addresses IETF66 Montreal – July 11, 2006. Edmon Chung, Afilias edmon@afilias.info. Overview. http://www.ietf.org/internet-drafts/draft-ietf-eai-mailinglist-00.txt Expanding from Scenarios Doc

sheryl
Download Presentation

Edmon Chung, Afilias edmon@afilias

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. draft-ietf-eai-mailinglist-00.txtMailing Lists and Internationalized Email AddressesIETF66 Montreal – July 11, 2006 Edmon Chung, Afilias edmon@afilias.info

  2. Overview • http://www.ietf.org/internet-drafts/draft-ietf-eai-mailinglist-00.txt • Expanding from Scenarios Doc • Mailing-List Header Fields • Mailing-lists should not introduce additional protocol requirements for EAI • Operational policies of managing mailing-lists (should always obtain alt-address or atomic information of subscriber) • Highlights issue for obtaining alt-address / atomic info

  3. Scenarios • Pure Case (only members involved) • Member  Mailing-List • Mailing-List  Member • Scenario 2.1 -- Two i18nmail users • Scenario 2.4 -- One i18nmail user sends to one ASCII user • Mixed Case (non-members involved) • Non-Member  Mailing-List • Non-Member cc-ed • Member replying to list and cc-ing Non-Member • Scenario 2.2 -- Three i18nmail users • Scenario 2.5 -- An i18mail user sends to one ascii user and one i18nmail user

  4. Mailing List Header Fields • List-Id: List Header Mailing List <list-header.nisto.com> • List-Help: <mailto:list@host.com?subject=help> (List Instructions) • List-Unsubscribe: <mailto:list@host.com?subject=unsubscribe> • List-Subscribe: <mailto:list@host.com?subject=subscribe> • List-Post: <mailto:list@host.com> • List-Owner: <mailto:listmom@host.com> (Contact Person for Help) • List-Archive: <mailto:archive@host.com?subject=index%20list> • Generally follows EAIHeaders and IRI documents • May wish to extend mailto IRI to allow for presentation of alt-address / atomic info?

  5. Issues for Further Discussion • Obtaining Downgrade Information • EAI-aware  EAI-aware mailing-list, alt-address or atomic information is not required • Downgrade maybe called for when “exploding” to members • Reject incoming mail if alt-address / atomic info not provided? • Mechanism, such as an additional SMTP command, for the receiving MTA (in this case the mailing-list) to request for alt-address or atomic information from sender? • May be useful in other scenarios (especially those concerning multiple recipients) • Downgrading Considerations for mailto URLs • Including Alt-Address / Atomic info in mailto URLs? • Operational policy of requiring Alt-Address / Atomic info • Hard requirement / suggestion?

  6. Thank You • Edmon Chung • edmon@afilias.info

More Related