Subject: [drinks] Use Case: Selecting egress points

From: Sumanth Channabasappa <[email-masked]>
Date: Thu, 27 May 2010 11:49:11 -0600

Folks,

Ken reminded me of a use case that inadvertently got dropped off in an earlier revision of the use cases I-D. I am enclosing the use case here. Please provide your comments. And if there are no objections, I will include it in the next rev.

Thanks!
- S

Selecting egress points

An SSP has a peering relationship with a peer, and when sending messages to that peer's point of interconnection, the originating SSP wishes to use one or more points of egress.  These points of egress may vary for any given peer.  This capability is supported by allowing an originating SSP to provision SED for identities terminating to other SSPs where the originating SSP is itself the data recipient.  The provisioning SSP may make use of multiple data recipient identities if it requires different sets of egress points be used for calls originating from different parts of its network.  Routing from egress points to ingress points of the terminating SSP may be accomplished by static routing from the egress points or by the egress points using data provisioned to the Registry by the terminating SSP.