Date: Thu, 23 Apr 1998 13:07:42 +0200 From: Vered Nimrod <nim@tadirantele.com> Subject: VoIP Numbering Plan Vs. Domain names. IPNP
Is there any work being done on the above subject ?
IETF has a working group dealing with IP Telephony, but I'm not sure whether they are dealing with the mentioned problem, or not.
There is a need for a universal IPNP (IP Numbering Plan) system. So that every equipment that will be connected to the Internet will have a unique DN (Directory Number).
The solution should rather be sought in the domain name system. And there is already a possible solution to the problem, outlined in the RFC 1530 (Principles of Operation of the TPC.INT Subdomain). This is, of course, my personal view of the matter and just one more idea on the solution to the problem. * A user calling from a "net phone" would use a host name in the form 7.9.3.3.6.2.9.3.2.7.9.tpc.int to call the phone number +972-3-9263397 belonging to a "regular" PSTN (i.e. domain name is the reversed phone number, much like IN-ADDR.ARPA system). In the DNS, there should be an "MX" record pointing to the PSTN/Internet gateway, e.g.: *.*.*.*.*.*.3.2.7.9.tpc.int. IN MX 10 pstn-gw.domain.com. The client application should consult the MX records, find out the name of the gateway and then connect to the gateway - the same way mail clients do. * A user calling from a PSTN should probably use an access code to reach a local PSTN/Internet gateway - which is exactly the way you described. That access code should be assigned by a national telecom authority. Best regards, Beri .-------. | --+-- | Berislav Todorovic, B.Sc.E.E. | E-mail: BERI@etf.bg.ac.yu | /|\ Hostmaster of the YU TLD | |-(-+-)-| School of Electrical Engineering | Phone: (+381-11) 3221-419 | \|/ Bulevar Revolucije 73 | 3370-106 | --+-- | 11000 Belgrade SERBIA, YUGOSLAVIA | Fax: (+381-11) 3248-681 `-------' --------------------------------------------------------------------