[enum-wg] insert meaningless and irrelevant Subject header

-----Original Message-----
From: enum-wg-bounces at ripe.net [mailto:enum-wg-bounces at ripe.net] On Behalf
Of Nikolay Shopik
Sent: Wednesday, November 13, 2013 2:33 PM
To: Richard Shockey
Cc: 'RIPE ENUM WG'
Subject: Re: [enum-wg] insert meaningless and irrelevant Subject header

On 13.11.2013 22:47, Richard Shockey wrote:
> BTW the focus in the US now is on using closed ENUM systems it for all 
> IP [SIP/IMS] interconnection data among carriers since everyone 
> including the mobile operators want to junk their TDM/SS7 gear and 
> Public Key Infrastructure for signing the inbound E.164 number in the 
> INVITE to validate the origin call and combat Call Spoofing etc.

We are lagging behind, for like 5-7 years. MNP only apply to mobile
operators, local operators will still using TDM/SS7 and nowhere plan to junk
their stuff. That's probably because our FSB didn't come up with new
wiretapping technology for SIP/IMS yet. So they still need TDM to wiretap
calls.

[RS> ]  Oh there are lots of US and Israeli firms that would be happy to
help the FSB !   They have a lot of experience are really good at analyzing
Call Details Records as well.  :-) 


SIP/IMS and public key, can you point me to draft/rfc?

[RS> ]  The SIP/IMS interconnection issue is part of the regulators push for
a PSTN Transition to all IP infrastructure.  The big carriers want it as
well... well get out from under the regulator first but there is a real
issue in that the old TDM gear needs to be replaced and is simply too
expensive to continue to operate and the SIP gear is cheaper.

http://www.telecompetitor.com/pstn-phase-out-debate-continues-at-fcc/

http://www.fiercewireless.com/tech/story/t-wants-fccs-blessing-shut-down-pst
n/2010-01-03

The problem is that the half transition is now causing huge leakage in the
system that is creating huge criminal fraud.  

https://datatracker.ietf.org/wg/stir/charter/

The consensus opinion  is the adapt DKIM to phone numbers. 

http://tools.ietf.org/html/rfc6376

In any event all of this requires restructuring the numbering databases and
that eventually ends up with ENUM somewhere in the picture.

http://apps.fcc.gov/ecfs/document/view?id=7520931878