1 / 7

ENUMservice "vCard"

ENUMservice "vCard". draft-mayrhofer-enum-vcard-00 Alexander Mayrhofer, enum.at GmbH mailto:alexander.mayrhofer@enum.at. Introduction. ENUM: we know about that vCard: "electronic business card" A contact data format Essentially Key/value pairs Transport independent

ajaxe
Download Presentation

ENUMservice "vCard"

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. ENUMservice "vCard" draft-mayrhofer-enum-vcard-00 Alexander Mayrhofer, enum.at GmbH mailto:alexander.mayrhofer@enum.at IETF64 - draft-mayrhofer-enum-vcard-00

  2. Introduction • ENUM: we know about that • vCard: "electronic business card" • A contact data format • Essentially Key/value pairs • Transport independent • Most often transported via email and http • Understood by most PIM applications • ENUMservice "vCard": refer from phone number to http(s) resource containing a vCard IETF64 - draft-mayrhofer-enum-vcard-00

  3. Motivation • Publish additional interopable contact information related to a E.164 number • Discover and use this contact information before / during / after VoIP calls (and other applications) • "end user controlled directory entries" • Provide an innovative end-to-end service using ENUM • still seeking the user ENUM killer application, this does at least fatten the list of candidates • Two Service providers asking us how to implement such a service using ENUM IETF64 - draft-mayrhofer-enum-vcard-00

  4. Usage scenario Query: +43 1 5056416 ? ENUM DNS Response: vcard, http://… SIP, sip:office@enum.at Internet enum.at IETF64 - draft-mayrhofer-enum-vcard-00

  5. ENUMservice registration details • ENUMservice name: "vCard" • ENUMservice type: "vcard" • Subtypes: none defined • URI schemes: "http", "https" • Example: $ORIGIN 4.3.6.1.4.6.5.0.5.1.3.4.e164.arpa. @ IN NAPTR 100 10 "u" "E2U+vcard" "!^.*$!http://www.enum.at/vcard-axelm.vcf!" . IETF64 - draft-mayrhofer-enum-vcard-00

  6. Feedback received • Very few (as usual…) :-/ • Subtypes considerations: • "vcard:http" / "vcard:https" instead of just "vcard" • Additional URI schemes? • ldap/ldaps? • Anything else? IETF64 - draft-mayrhofer-enum-vcard-00

  7. Conclusion & discussion • "vCard" refers from ENUM domain to contact info • We already have implementors for this • We think that this could be an innovative service fostering ENUM deployment • We're going to provide a prototype based on Asterisk • Call for feedback • How to proceed with this document? IETF64 - draft-mayrhofer-enum-vcard-00

More Related