Re: M3UA and SUA recommendations
Siu Chai Tho <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <[email protected]> |
Stanislav, Stanislav Ivanovich <[email protected]> wrote: You should not understand all the parts of any RFC paper as normative ones if they do not affect behavior on the external protocol. [Siu Chai Tho] No layer will ever be visible externally, it is essentially an abstract definition concept. This is not unique for SIGTRAN but goes for all protocol layers (such as defined in RFC 1122 or ITU-T SS7 specifications). Layering is a architectural design pattern and thus only applicable to implementations. Nevertheless it's an important architectural choice to choose layers. [...] [Stanislav Ivanovich] Why then different process types??? Read terminology sections of both SUA and M3UA: "IP Server Process (IPSP) - A process instance of an IP-based application. An IPSP is essentially the same as an ASP, except that it uses SUA in a peer-to-peer fashion." "Signalling Gateway Process (SGP) - A process instance of a Signalling Gateway. It serves as an ac! tive, load-sharing or broadcast process of a Signalling Gateway." Don't you need IPSP and ASP to serve the interface to the MTP/SCCPuser and the SGP to serve the interface to MTP/SCCP ? That in itself is a difference. The difference between ASP and IPSP is as you quoted above, an IPSP can talk to other IPSPs serving MTP/SCCP users. Thank you, Joe Send instant messages to your online friends http://au.messenger.yahoo.com _______________________________________________ Sigtran mailing list [email protected] https://www1.ietf.org/mailman/listinfo/sigtran