draft-pfautz-lind-enum-carrier-00.txt

IETF 604 August 2004

Steven D. Lind

4 August 2004 draft-pfautz-lind-enum-carrier-00 2

Carrier ENUM

• Need to distinguish between private (intra-enterprise, intra-carrier, CUG) uses of ENUM technology versus public ENUM

• Private uses are legitimate but separate from the question of whether the public ENUM infrastructure can/should support carrier interconnection as well as end user reachability

4 August 2004 draft-pfautz-lind-enum-carrier-00 3

draft-pfautz-lind-enum-carrier-00.txtObjective

• Define mechanism to allow public ENUM tree (e164.arpa) to support both end user applications and carrier interconnection– Avoid provisioning and performance issues

associated with end user opt-in and control of Tier 2 for carrier registration while preserving user options and protections for end user registration

– Leverage existing work toward implementation of end user ENUM and carrier scale for greatest efficiency of both flavors of public ENUM

4 August 2004 draft-pfautz-lind-enum-carrier-00 4

A Delicate Balance

• End users want privacy to minimize unwanted communications

• Service providers want to maximize call completion– To/from their subscribers– Keep communication on the IP-plane– Single tree (or absolute minimal set of trees) to

find call completion information

4 August 2004 draft-pfautz-lind-enum-carrier-00 5

Opt-in• Each country will have its own unique privacy regulations

• Three types of “opt-in” (not all good; not for all situations)– User-initiated

– User-notified

– User-ignored

• What type of opt-in might be required for a translation from “+1 973 236 6787” to:– “sip:+19732366787@sip.foo.com”

– “sip:+19085617228@sip.bar.com”

– “mailto:+19732366787@email.foo.com”?

4 August 2004 draft-pfautz-lind-enum-carrier-00 6

Carrier Trees• Some infrastructure-related information (e.g.,

caller name) may properly reside in private DNS resources

• Basic communication completion information in private trees defeats basic value of ENUM

• Fewer trees lead to admission control problems– Who controls admission– What is criteria

• Many trees lead to call completion problems– How to maximize chance of success– Do not want to replicate E.164 resource problems

4 August 2004 draft-pfautz-lind-enum-carrier-00 7

draft-pfautz-lind-enum-carrier-00.txtProposal

• In Tier 1, replace single NS record with 2 non-terminal NAPTRs with different service fields (E2U – end user; E2C – carrier) that point to the respective Tier 2s

• Carrier record to be populated by PSTN carrier of record for the number

• Querying client decides which record(s) to make use of.