Enum Next Generation

743 views

Published on

Patrik Fältström

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
743
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Enum Next Generation

  1. 1. ENUM Next Generation Patrik Fältström (With ideas from Olaf Kolkman) ENUM RIPE-53 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 1
  2. 2. Do you feel lost? Do you know how to contact your friends? ENUM is (supposed to be) the solution to that problem Patrik Fältström +46 8 685 9131 ENUM RIPE-53 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 2
  3. 3. It does not really solve the problem… QuickTime™ and a TIFF (Uncompressed) decompressor are needed to see this picture. Source: ISC, where you can buy this sh ENUM RIPE-53 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 3
  4. 4. Delegation on CC l Administrative model ITU-T TSB RIPE NCC Service Admin operator DNS operator DNS operator Verification agency Holder ENUM of E.164 registrar Delegation on Customer level ENUM RIPE-53 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 4
  5. 5. ENUM for infrastructure Convergence of telcos to ENUM Infrastructure information in the public DNS Publish routing information ENUM was always intended for the public 0.5.6.0.2.2.2.0(…) NAPTR <point to SIP service for user> 0.5.6.0.2.2.2.0(…) NAPTR <point to SIP service for infrastructure> Two owners of the same record in the same zone? ENUM RIPE-53 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 5
  6. 6. Problems Different ASPs for services, but only one delegation Do you want your mms:mailto record to be maintained by your cell phone operator? Do the cell phone operator let you maintain your mms:mailto record? ENUM RIPE-53 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 6
  7. 7. Current idea… $ORIGIN 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. NAPTR 10 100 "u" "E2U+sip" "!^.*$!sip:info@example.com!” . NAPTR 10 100 "d" "E2U+sip" "" 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. NAPTR 10 102 "u" "E2U+msg" "!^.*$!mailto:info@example.com!" . NAPTR 10 102 "d" "E2U+msg" "" 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. $ORIGIN 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. _sip._e2u URI 10 10 "sip:info@example.com" _sip._e2u URI 10 10 "sip:info@example2.net" _h323._e2u URI 10 10 "h323:info@example.com" _msg._e2u URI 10 10 "mailto:info@example.com" ENUM RIPE-53 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 7
  8. 8. Delegation structure . arpa. e164.arpa. 4.4.e164.arpa. 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. NAPTR 10 100 "u" "E2U+sip" "!^.*$!sip:info@example.com!" . NAPTR 10 101 "u" "E2U+h323" "!^.*$!h323:info@example.com!" . NAPTR 10 102 "u" "E2U+msg" "!^.*$!mailto:info@example.com!" . _e2u.3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. _infra.3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. _msg._e2u.3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. _sip._e2u.3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. URI 10 10 "sip:info@example.com" URI 10 10 "sip:info@example2.net" ENUM RIPE-53 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 8
  9. 9. ENUM Next Generation Today, query for NAPTR and get back every URI “connected” to the domain Should we separate between What services exists for this domain? What URI should I use for this service? Will this at the same time make delegation possible of separate URI specifications to different organisations? Backward compatibility? ENUM RIPE-53 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 9
  10. 10. Documents draft-ietf-enum-uri-00.txt Me, Olaf Kolkman and Niall O’Reilly draft-ietf-enum-3761bis-00.txt Me, … ENUM RIPE-53 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 10
  11. 11. Q and A ENUM RIPE-53 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 11
  12. 12. ENUM RIPE-53 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 12

×