60 likes | 161 Views
E2MD (ENUM-to-Doctor). I see the problem… he’s infected by the IETF!. What we need. Calling-name Key = calling number SPID/SPN Key = called or calling number Send-N Key = called number (only?) Unused Key = either Source-based results
E N D
E2MD (ENUM-to-Doctor) I see the problem… he’s infected by the IETF!
What we need • Calling-name • Key = calling number • SPID/SPN • Key = called or calling number • Send-N • Key = called number (only?) • Unused • Key = either • Source-based results • Key = called number, but “filtered” by source data (or arguably key = called + source)
Requirements • Has to support variable-length/open numbering plans • Has to be in private database: all use-cases • Has to be in public database: all use-cases?
Source-URI • Today, source-uri is done in private contexts only • Used for VoIP routing • Example-1: NANP local vs. long-distance calls, in North America • Example-2: transit peering arrangements
Source-URI Problem • Call from A to C may need different path than from B to C, and different from A to D Database Proxy-1 Proxy-2 A B C D
A Horse of a different color What if we just say “fine, it’s not The DNS”, it’s ENUM 2.0