RE: ENUM Privacy (was RE: [Enum] User ENUM vs Operator ENUM)

["Peter Williams" <home_pw at msn.com>]

> As Peter suggested using Application layer tunnelling to captivate user
> applications within these goldfish bowl domains I don't see why I shouldn't
> use similar to get through and around them should they become a reality!
>
>
>
> Christian

Dont get too upset at common practice. Privacy and control are orthognal 
axies of operational security. To get privacy, public ENUM providers (or 
their TTPs) wil have to cede some control. Security and Privacy via 
comparmentalization is a well understood practice.

IF we reason by analogy,PABXs have long had public number to private 
exchange number mappings, to save costs, and route the call across the 
preferred providers network (as selected by the PABX). Im not aware of the 
PSTN having collapsed because of a private zone was created to manage public 
E.164 names. Quite the opposite, US telcos started offering "VPN services" 
to manage those names way back in 1950!

Can the determined corporate user use a calling card, and use source routing 
via AT&T 1800CALLATT number to avoid the local poilicy? of course.




Im a security engineer; I dont get to trust provider or operator conformance 
to standards, or make assumptiosn that software works correctly



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