Subject: Re: [drinks] Use Case: Selecting egress points

From: "Cartwright, Ken" <[email-masked]>
Date: Mon, 7 Jun 2010 17:09:36 -0400

With respect to my action item related to the inactive/active concept of a PI that we all agreed needed to be in the protocol...

I think the current use case UC LOOKUP #6 speaks to this concept under its portion "c)".  So I suggest that we change the last sentence of this use case to say... "The choice is dependent on the policies of the implementer of the protocol".  The alternative of adding in another use case that specifically speaks to section "c)" is probably not a good idea.

Ken

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] On Behalf Of Sumanth Channabasappa
Sent: Thursday, May 27, 2010 1:49 PM
To: DRINKS WG
Subject: [drinks] Use Case: Selecting egress points

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.
_______________________________________________
drinks mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/drinks

This e-mail message is for the sole use of the intended recipient(s)and may
contain confidential and privileged information of Transaction Network Services.
Any unauthorised review, use, disclosure or distribution is prohibited. If you
are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.