[enum-wg] Why is there no "SMS center is here" ENUM record?
Lawrence Conroy lwc at roke.co.uk
Wed May 16 15:52:44 CEST 2012
On 16 May 2012, at 13:08, Jim Reid wrote: > On 16 May 2012, at 12:23, Rick van Rein wrote: > >> As far as I can tell, there is no ENUM record that says >> "please deliver SMS for this number at the SMS Centre >> at IP address 123:456::789" -- is there a reason for that? > > NAPTRs can point at just about anything that has a URI scheme. So does RFC5724 "URI Scheme for Global System for Mobile Communications (GSM) Short Message Service (SMS) not meet your need? Admittedly, this talks about delivery to phone numbers rather than IP addresses. To which I add: You seem to be describing any set of telephone numbers from the perspective of the SMSC. So ... 1. OK -- as Jim says, with a NAPTR one has a URI -- let's say that has an IP address in that URI. So, there's something listening at a given IP address. You'll also need to specify the port (relatively easy, and the NEW spec may even spell out a default port). But ... What protocol? You would need to spell out the protocol for a start, in detail. ++ 2. Who controls provisioning records into the particular ENUM domains associated with devices served by the SMSC? 3. Is a carrier running an SMSC really going to provision thousands/millions of such records into the ENUM-domain-space associated with its customers' telephone numbers? all the best, Lawrence Conroy ++ As an unimportant aside... strictly the IETF sms NAPTR spec (rfc4355) would be updated, as it doesn't mention the sms: URI [or whatever URI scheme you're going to define for entities that handle your SMSC protocol]. IIUC, that's just a case of writing an sms:sms template (as shown in rfc6117/rfc6118) and dropping that into the IETF system (where, I believe, Bernie will check it and then nudge IANA to publish it). Biggest pain would be spec'ing the URI scheme for entities handling the SMSC protocol (and making sure that was specified correctly).
[ enum-wg Archives ]