DRN and TID Label Issues -- Issue #3
"Brian F. G. Bidulock" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Organization | http://www.openss7.org/ |
| Message-ID | <[email protected]> |
Lincoln, RFC 3868 says: 4.1.1. Receipt of Primitives from SCCP ... When there is no Routing Key match, or only a partial match, for an incoming SS7 message, a default treatment MAY be specified. Possible solutions are to provide a default Application Server at the SGP that directs all unallocated traffic to a (set of) default ASP(s), or to drop the message and provide a notification to Layer Management in an M-ERROR indication primitive. The treatment of unallocated traffic is implementation dependent. 4.7.3.1. TCAP traffic ... If an ASP is not available, the SG may generate (X)UDTS "routing failure", if the return option is used. 4.7.3.2. SCCP Connection Oriented traffic ... If an ASP is not available, the SG discards the message. The application of DRN/TID label is inconsistent with the concept of a "default ASP" and the principle that the SG implementation is in the best position to decide the treatment of unallocated traffic. --brian -- Brian F. G. Bidulock [email protected] http://www.openss7.org/