Re: ASP Capabilities value 0x2 of interworking field
"Brian F. G. Bidulock" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Organization | http://www.openss7.org/ |
| Message-ID | <[email protected]> |
Tolga, Tolga Asveren wrote: (Tue, 20 Dec 2005 08:46:56) > > > [TOLGA]SGPs. > > Placing GTT at the edge of the network is not practical. > [TOLGA]At least we agree that SUA SG can act as relay. I disagree with you > that you consider SG at the edge of the network. This is not mandatory by > protocol. You can have them whereever you want and with relaying support > they perform what you want to achieve: allowing easier management of the > network. That is the idea why there is relaying support defined for SGs. Interconnect is not done at the core of the network. GTT is. No self respecting SS7 network operator would connect your SUA junk to their primary STPs any day soon. Lot's o' luck. > > > [TOLGA]A SGP does not need to have SS7 interface. You put it > > there, if you > > > need to acces conventional SS7 network. > > So in M3UA what is an SGP with no SS7 interface? An IPSP that supports > > relaying? > [TOLGA]No, still an SG. IPSP is a direct, peer-to-peer relationship between > two applications. SG-SG is a peer-to-peer relationship between two relaying > agents. Whether they relay to a node in conventional SS7 network, to another > IP entity or to a local application is conceptually not important. SUA already has this concept. Any element can be a relay within the IP or SS7 domains. Only M3UA needs the SG-SG concept because currently only an SG can relay, and now only within the SS7 domain. For M3UA, however, providing relay within the IP domain is pointless. Each originator knows the address of the final destination and might as well form an association with and send it there directly. M3UA relays accomplish nothing more than an IP router already aptly acheives. --brian -- Brian F. G. Bidulock [email protected] http://www.openss7.org/