Lawrence,
I don't think what you and I are saying is that much at odds.
My comment about the 90% was that the general population (not the
technical saavy) will follow the conventions of their residential
service provider or employer company providing the access network, the
IP addresses, the SIP or H.323 addresses, and the database entries to
make it all work. This does not mean that there can not be other
configurations that also work as you point out. But, the majority of
people don't have the time, interest, or background to go figure it all
out.
I mentioned the access provider and the IP addresses only to complete
the picture. There is a series of things that must be in place before
the system works. If I put a private non-routable IP address from the
LAN in my house in an ENUM record, I won't get an incoming call.
As for whether a company is a service provider, if they give me a
network connection, an IP address, a SIP address, and route packets to
my laptop, and terminate calls to my VoIP phone ... there is a saying
on this side of the pond: If it waddles like a duck, swims like a duck,
quacks like a duck, and looks like a duck, it's a duck.
Mike
At 01:14 AM 7/9/2004 +0100, Conroy, Lawrence (SMTP) wrote:
Hi Mike, folks,
I'm slightly at a loss here. I fear that we will just have to
disagree on this one.
You seem to be asking if I have a E2U+sip entry. The answer to that is
"some of the time, yes".
You then ask what kind of access I have. The domain of the SIP address
is mine; I registered it.
As it happens, the domain of the domainpart of the SIP AoRs "at work"
was also registered by me.
The IP address range I have at home was assigned via my DSL Internet
Access Provider. My company's
IAP also arranged for the IP range used by my company. I have to ask,
"this is pertinent because...?".
I must disagree over your definition of an Enterprise as a Service
Provider.
An Enterprise can register ENUM domains for the E.164 numbers via
which it is
provided Communications Service by a 3rd party CSP.
It is the end user assignee for these E.164 numbers, and so a
->potential<- ENUM Registrant.
The CSP is not the end user, and so (on this side of the pond) cannot
register ENUM domains
for those E.164 numbers.
Once registered, if I (or my company) choose to put anything I/they
want into my/their ENUM
domains, then (as I/they are paying to have it published) that's
my/their choice.
Given that any reasonable DNS server handles "split horizon", what you
see may well not be
what I see. Again, that's my/their choice.
Whether or not my company allows IP calls from teleworkers or Extranet
partners is also our
choice. Other registrants can make different choices in their domains
- I'm not stopping them
and they're not stopping me.
Equally, if an Enterprise chooses not to register in ENUM, that's also
their choice.
Finally, if and when caller/callee prefs and the rest of the
infrastructure is standardised
and in place to give all of the UCI/PUA features, then one could have
a single entry in ENUM
pointing to that PUA. However, for some time, there will be SIP
systems (or H.323, just to be
non-denominational) that do not provide full PUA functionality, and
for the foreseeable future
(i.e. in the interim) just using ENUM (and standard DNS) alone works
for me.
I don't need anything more complex.
My point is just that I believe that it will work for more than 10% of
the Registrant population.
all the best,
Lawrence
On 8 Jul 2004, at 16:51, Mike Hammer wrote:
Lawrence,
Do I understand correctly that ENUM points to your sip: address, and
that the DNS holds records to go from sip address to IP address to
make the connection to your SIP proxy?
I would anticipate also the possibility that the domain name of your
SIP address could be provided by either a residential SP or your
company acting as SP. I assume that you are also getting the IP
address from your local ISP serving your home, although I'm a bit
fuzzy on what type of local access you might be using to connect to
the ISP (modem, DSL, cable?).
Note that I consider enterprises/companies as service providers,
though not publicly regulated ones. And while they could also make
use of ENUM, they might question the value versus risk of putting
their company directory into the public domain. I suspect that they
would want to keep that information internal and only selectively
release such information. However, the before-mentioned suggestion
to provide a SIP proxy domain such that SIP messages to
sip:<e.164number>@company.com that can use an internal database to
translate to user-specific sip address can be used.
When presence becomes more widely deployed, ENUM could point to the
presence address for subscriptions. Then presence information could
provide the remaining information that would otherwise be publicly
posted in ENUM.
Mike
At 11:27 PM 7/7/2004 +0100, Conroy, Lawrence (SMTP) wrote:
Hi Mike, folks,
Is this 90% valid?
<snip>
Thus, whilst you may be right on the total population of PSTN
telephone service subscribers, I'm not sure this is the case for the
population of "user" ENUM subscribers.
--
Visit our website at www.roke.co.uk
Roke Manor Research Ltd, Roke Manor, Romsey, Hampshire SO51 0ZN, UK.
The information contained in this e-mail and any attachments is
confidential to
Roke Manor Research Ltd and must not be passed to any third party without
permission. This communication is for information only and shall not
create or
change any contractual relationship.
_______________________________________________
enum mailing list
enum at ietf.org
https://www1.ietf.org/mailman/listinfo/enum