Re: Recommendation for SUA modifications

Tolga,

Tolga Asveren wrote:                             (Wed, 12 Oct 2005 14:34:27)
> > That would be sending messages with RC 1 in them before receiving
> > ASP Active
> > Ack for RC 1.  That passage does not speak to the addressing of
> > the messages.
> > Other passages do.  The SG provides uniform connectivity to all
> > ASPs in an AS
> > and can route any messagew within a Network Appearance.
> [TOLGA]Here I still think different, i.e. I consider AS state to be honored
> in both directions of message flow based on the above passage-.

That is true enough for MTP/M3UA, but for SCCP/SUA the
responding address (in a connection response) is not necessarily
the address to which the connection request was sent.  SUA has
the ability for relay internal to the ASP or over the IP
network, that we precluded in the M3UA RFC.

Following your stricter interprentation would require, for
connection oriented operation, when the responding address
differs from the address of the request, of responsding to a
connection request using an RC differennt from that upon which
the connection request arrived.

Nevertheless, Lincoln seems to be avoiding this question,
perhaps you can venture an answer: "How does the SG know what
address to place in the OPC of the message if it receives an SUA
message (SCON or otherwise) from the ASP that does not include a
corresponding point code in the message?"

Remember that Lincoln says that his ASPs register only using GT
(or maybe SSN) with no point code, therefore there is no point
code in the routing key associated with the routing context and
that, if I interpret him correctly, that it is too difficult a
provisioning task for his ASP to provide one at registration.

For arguments sake, assume that the SG supports mutliple point
codes (otherwise the task is trivial).

--brian

-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/