1 / 7

Motivation for the I-D

IETF 63 – ENUM WG IANA Registration for an Enumservice Containing Number Portability and PSTN Signaling Information < draft-livingood-shockey-enum-npd-00> 5 August 2005 Co-Authors: Jason Livingood Richard Shockey. Motivation for the I-D.

becca
Télécharger la présentation

Motivation for the I-D

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. IETF 63 – ENUM WGIANA Registration for an Enumservice Containing Number Portability and PSTN Signaling Information<draft-livingood-shockey-enum-npd-00>5 August 2005Co-Authors:Jason LivingoodRichard Shockey

  2. Motivation for the I-D • This Enumservice could enable carriers, as well as other service providers and users, to place ported, pooled, and blocks of numbers and their associated PSTN contact information, into ENUM databases, using standardized, non-proprietary methods. • This, in turn, could enable such parties to consolidate all telephone number lookups in their networks into a single ENUM lookup, thereby simplifying call routing and network operations, which would then result in either an on-net, or IP-based response, or off-net, or PSTN-based response. • It is conceivable that being able to query for this information in ENUM could significantly reduce or eliminate the need for these parties to maintain traditional, SS7/TCAP/SIGTRAN-based query gateways, applications, and protocols in their networks.

  3. Motivation for the I-D • Call routing lookup consolidation. • No need for separate database of pooled, ported (LNP), and block number data. • One DNS lookup gives BOTH on-net and off-net results to VoIP network element. • Leverages investment in ENUM data management now underway. • Uses standardized, DNS interfaces. • Enables determines location of the destination as close to point of call origination as possible. • Reduces complexity in a VoIP network; reduced need for legacy PSTN signaling and databases. • No per dip fees; flat-rate DNS infrastructure.

  4. Example #1, Ported TN $ORIGIN 3.1.8.7.1.8.9.5.1.2.1.e164.arpa. NAPTR 10 100 "u" "E2U+npd:tel" "!^.*$!tel:+1-215-981-7813;rn=+1-215-981-7600;npdi!" In this example, a Routing Number (rn) and a Number Portability Dip Indicator (npdi) are used as shown in draft-ietf-iptel-tel-np-06.txt. The ‘npdi’ field is included in order to prevent subsequent lookups in legacy-style PSTN databases.

  5. Example #2, Non-Ported TN $ORIGIN 3.1.8.7.1.8.9.5.1.2.1.e164.arpa. NAPTR 10 100 "u" "E2U+npd:tel" "!^.*$!tel:+1-215-981-7813;npdi!“ In this example, a Number Portability Dip Indicator (npdi) is used. The ‘npdi’ field is included in order to prevent subsequent lookups in legacy-style PSTN databases.

  6. Next Steps • Minor editorial changes recommended on the list. • Update document references (Yu draft iteration). • Add more examples if possible.

  7. Thank you!

More Related