Re: [Speermint] Re: [Enum] How to correctly set up the request URI?

["Stastny Richard" <Richard.Stastny at oefeg.at>]

Tony,
 
I do not fully understand what the CALEA issue has to do with the question which
URI is put in ENUM. This may be a signalling requirement in SPEERMINT
 
I have complete different concerns regarding CALEA, in principle I do 
not understand why the service providers are bothered with this at all,
because the NSA is getting all data from Penn anyway ;-)
 
http://news.com.com/AT38T+leaks+sensitive+info+in+NSA+suit/2100-1028_3-6077353.html?tag=nefd.lede
 
http://www.wired.com/news/technology/0,70944-0.html
 
-sta

________________________________

Von: Tony Rutkowski [mailto:trutkowski at verisign.com]
Gesendet: Fr 02.06.2006 23:13
An: Pfautz, Penn L, GBLAM; James McEachern; speermint at ietf.org; enum at ietf.org
Betreff: RE: [Speermint] Re: [Enum] How to correctly set up the request URI?



Hi Penn,

>I see no privacy issue with a carrier URI like the one you show below as
>long as it points to a carrier network element rather than directly to
>say, the user's terminal adapter. If the pointer is direct to CPE I'd
>have some concerns, which is not to say a provider can be forbidden
>(except by regulators) to do so.

The concerns primarily relate to network integrity as
well as support of law enforcement (CALEA/LI requirements)
in determining authoritative bindings of user/provider
information to identifiers.  In Europe and many countries,
this binding information is also subject to data retention
directives.

--tony


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




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