Re: [Enum] a suggestion re: using flags to distinguish post-ENUM signaling f lows

>The second one is (essentially) number portability. My SIP URI can change from sip:mstafford@provider-A.net to >sip:mstafford@provider-B.biz. As long as my phone number stays the same, it can be used to obtain my current SIP URI.

What I want to have is SIP URI portability too, or in other words: I want to have my sip URI sip:richard@stastny.com
hosted by one provider and the possibility to port this to another.

Especially if I am a company.

For more information see the ECMA christmas wish-list presented today at ETSI TISPAN:
Technical Report TR/91
Enterprise Communication in Next Generation Corporate Networks (NGCN) involving Public Next Generation Networks (NGN)
(December 2005)
http://www.ecma-international.org/publications/files/ECMA-TR/TR-091.pdf

and also
Technical Report TR/92
Corporate Telecommunication Networks - Mobility for Enterprise Communications
(December 2005)
http://www.ecma-international.org/publications/files/ECMA-TR/TR-092.pdf

The scenarios and requirements described in these two documents will not
be really easy to implement with NGNs ;-)
Of course they want to have best of both sides: peering with each other in all variants
AND in addition to be connected to an NGN, just to be on the safe side.
One could also say: the overflow traffic is for the telcos (say max 20%)

Richard

________________________________

Von: enum-bounces@ietf.org im Auftrag von Stafford, Matthew
Gesendet: Di 07.02.2006 19:20
An: Tony Rutkowski
Cc: enum@ietf.org; speermint@ietf.org
Betreff: RE: [Enum] a suggestion re: using flags to distinguish post-ENUM signaling f lows

Tony- The E.164 space is a many-encumbered thing. No argument there. 

All the same, I see two benefits of E.164 numbers: although *some* mobile devices have QWERTY keyboards, many of them still don't. IMO a telephone number is far and away the easiest thing to punch into a cellphone keypad. That's the first one. The second one is (essentially) number portability. My SIP URI can change from sip:mstafford@provider-A.net to sip:mstafford@provider-B.biz. As long as my phone number stays the same, it can be used to obtain my current SIP URI.

Best, 
Matt 

-----Original Message----- 
From: Tony Rutkowski [mailto:trutkowski@verisign.com] 
Sent: Sunday, February 05, 2006 10:42 AM 
To: lconroy; Stafford, Matthew; Otmar Lendl 
Cc: enum@ietf.org; speermint@ietf.org 
Subject: Re: [Enum] a suggestion re: using flags to distinguish post-ENUM signaling f lows 

Hi Lawrence, 

>The first is the process issue - what group (if any) coordinates 
>between the different DDDS applications and their uses; this topic 
... 
>3761bis. It seems that your proposal is purely for Carrier/ Infrastructure/ 
>Private ENUM; in this case, changing 3761 has unintended consequences 
>for Public/User ENUM applications. 

These are great understatements.  The use of 
E.164 identifiers, internationally and 
domestically, is subject to more statutory, 
regulatory, national security, and industry 
practice requirements than any identifier 
space in existence - not to mention well 
established institutional jurisdiction. 

The following list is a current tabulation 
of E.164 resolver-directory capability 
requirements, parsed into three categories, 
currently in play in various industry NGN 
forums.  The recently enacted EC Data 
Retention Directive, and the U.S. Prevent 
Cyberstalking law, add further complexity 
to the mix. ;-) 

best, 
--tony 

>basic resolver capability 
> 
>supplementary capability 
>         Number Portability 
>         Priority Access 
>         Roaming 
>         Quality of Service 
>         Directory Assistance 
>         CallerID 
>         Disability Assistance 
>         Language preference 
>         Personal emergency (E112/911) 
>         Public emergency alerts 
>         Law enforcement assistance 
>         DoNotCall 
>         Payment Methods 
>         Intercarrier Compensation 
>         Profile Management 
>         Presence 
>         Availability 
>         Location 
>         Push Management 
>         Digital Rights Management 
>         Device Management 
>         Authentication Credentials 
>         Information verification level 
> 
>protocol feature 
>         Authentication 
>         Auditing 
>         Multiple Syntax Support 
>         Mutiple Language Support 
>         Extensibility and Localisation Mechanisms 

_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum