70 likes | 86 Views
Intradomain gateway discovery requirements. Henning Schulzrinne Columbia University. Organizational assumptions. Possibly “mutual aid” e.g., gateway calls to local calling area without billing Loosely affiliated, with different administrators different university campuses
E N D
Intradomain gateway discovery requirements Henning Schulzrinne Columbia University
Organizational assumptions • Possibly “mutual aid” • e.g., gateway calls to local calling area without billing • Loosely affiliated, with different administrators • different university campuses • different branches of enterprise 52st IETF
G G G G P P P P Example 212 415 Columbia U. ? UCB 52st IETF
Dynamic configuration • New gateways or gateway capacity capacity changes • For university networks (e.g., I2), potentially several hundred participants • Policy changes • new area codes adds additional calling areas • policy changes (time of day, …) 52st IETF
Coordination • May have loose central administrator • avoid manual updates and configuration • reflect changes rapidly (minutes) 52st IETF
Status updates • Want to have reasonably accurate picture • But occasional failure + retry acceptable • SIP INVITE fails, proxy retries • also, may allow grace period (change policy, allow calls for old policy for an hour) • Charging not an issue • may use a “brownie point” system 52st IETF
Additional considerations • Multicast may be available • Not competitors – if anything, GWs are happy not to get a call… 52st IETF