RE: Routing Key for an Appllication Server and an IP server

Regarding this issue, 4.3 from 3332bis provides some information:


Two IPSP models are defined as follows:

   1- IPSP Single Exchange (SE) model. Only a single exchange of ASPTM
      and ASPSM messages are needed to change the IPSP states. This means
      that a set of request from one end and acknowledgement from the
      other will be enough. The RK must define both sides of the traffic
      flow. Each exchange of ASPTM or ASPSM messages can be initiated by
      either IPSP. For this exchange, the initiating IPSP follows the
      procedures described in section 4.3.1.

   2- IPSP Double Exchange (DE) model. A double exchange of ASPTM and
      ASPSM messages are normally needed (ASPSM single exchange is
      optional as a simplification). Each exchange of ASPTM or ASPSM
      messages can be initiated by either IPSP. The RKs define the
      traffic to be directed to the peer as in the AS-SG model. Therefore
      two different RKs are usually used, one installed on each peer.

It is questionable to me whether ASPSM single exchange for IPSP-SE is a
simplication or an obstacle and whether it should be allowed at all but this
is besides the point for this thread. Similarly I would think that IPSP-DE
will require four -not two- RKs, two installed on each peer.

     Thanks,
     Tolga

> -----Original Message-----
> From: Tolga Asveren [mailto:[email protected]]
> Sent: Wednesday, August 16, 2006 3:05 PM
> To: anjali gurmukhani; Bui, MyHanh; [email protected]
> Subject: RE: [Sigtran] Routing Key for an Appllication Server and an IP
> server
>
>
> Please see below for a small comment...
>
>    Thanks,
>    Tolga
>
> 1) An application server is uniquely identified by a Routing Key. Now this
> Routing key can be any combination of DPC/OPC/SI/CIC. This combination has
> to be unique across the Application servers added.
>
> What this means is that you can have two Application servers
> added such that
> one AS has a Routing key type as DPC only with DPC=X and another having
> Routing key type as DPC+OPC where DPC=X and OPC=Y.
>
> 2) In IPSP-IPSP scenario, the communication is between two M3UA endpoints
> and the traffic has not be carried over the remote end as in the case of
> ASP-SGP scenario where the traffic is originating from SS7 side and has to
> be carried over to ASP OR is originating from ASP side and may be is
> destined for some point code in SS7 cloud.
>
> So point-to-point means that between two end-points in IP
> domain/conceptually no services of SG being used..For ex, an MSC could be
> talking to an SG and IP resident HLR at the same time. So in this case ,
> MSC-HLR communication is IPSP-IPSP( point-to-point) and MSC-SG is ASP-SG.
>
> As far as Routing Key type is concerned, it does not necessarily be
> DPC-OPC.can be DPC only also.
> [TOLGA]Just to prevent a confusion, IPSP-SE mandates DPC+OPC as
> RK, because
> it relies on the assumption that RK will identify traffic at both ends.
> IPSP-DE won't require that but it is also questionable whether it
> is a true
> peer-to-peer model or two coupled client/server relationships.
> Actually for
> IPSP-DE you will need to define to RKs, one for each direction of the
> relationship, which combined would correspond to the single RK of IPSP-SE.
>
>
> _______________________________________________
> Sigtran mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/sigtran