Re: Doubt regarding Dynamic registration and DE model

Hi Brian,

Thanks a lot for your quick help, your mail has cleared lot of doubts.

I have one more doubt now.


Consider two AS communicating  where the RK1=(OPC=2-200, DPC=2-100) is
different from RK2=(OPC=2-100,
DPC=2-200). Each RK defines its own AS, in this case AS1, which
corresponds to RK1, sits in 2-200 signalling point and AS2, which
corresponds to RK2, is in 2-100, and each AS has its own RK.
 Then Routing Context RC1 corresponding to RK1
 is assigned in AS2 and Routing Context RC2 corresponding to RK2 is
 assigned in AS1.

 Then will the messages going from AS1 to AS2 use RC2 and messages going
from AS2 to AS1 use RC1,
 or it is the other way round. ?

 Please clarify




On 6/28/07, Brian F. G. Bidulock <[email protected]> wrote:
>
> Mohammad,
>
> Mohammad Arif wrote:                               (Wed, 27 Jun 2007
> 17:56:04)
> >
> >    Hi ,
> >
> >
> >
> >    IF  one M3UA peer supports SE model and another supports DE
> model,then
> >    how will they communicate.?
>
> Both must support SE.  See RFC 4666/4.3:
>
> 4.3.  AS and ASP/IPSP State Maintenance
>
>   ...
>
>   In order to ensure interoperability, an M3UA implementation
>   supporting IPSP communication MUST support the IPSP SE model and MAY
>   implement the IPSP DE model.
>
> >
> >    How  will  local M3UA endpoint knows that the remote end is
> supporting
> >    the same model( SE or DE)?
>
> Well, if it supports IPSP at all, it MUST support SE and only MAY support
> DE.
> Therefore, for DE mode operation, both ends will have to be configured for
> DE
> operation.
>
> >    My Second doubt is,
> >
> >    Can  Routing  Key  be  a  static configurable  data ( to be entered
> by
> >    user)? Or it is always generated from OPC,DPC,SLS. ?
>
> Any data can be used.  See RFC 4666/1.4.2.1:
>
>   ...
>
>   Possible SS7 address/routing information that comprise a Routing Key
>   entry includes, for example, the OPC, DPC, and SIO found in the MTP3
>   routing label.  Some example Routing Keys are: the DPC alone, the
>   DPC/OPC combination, or the DPC/OPC/SI combination.  The particular
>   information used to define an M3UA Routing Key is application and
>   network dependent, and none of the above examples are mandated.
>
> >    Does the static configuring of routing key depend on SE or DE model?
>
> No. See RFC 4666/1.4.2.3:
>
>   There are two ways to provision a Routing Key at an SGP.  A Routing
>   Key may be configured statically using an implementation dependent
>   management interface, or dynamically using the M3UA Routing Key
>   registration procedure.
>
> >    I have an understanding that DE model supports dynamic registration
> so
> >    routing key is  not configurable , it is generated.
>
> No. See RFC 4666/1.4.2.3:
>
>   There are two ways to provision a Routing Key at an SGP.  A Routing
>   Key may be configured statically using an implementation dependent
>   management interface, or dynamically using the M3UA Routing Key
>   registration procedure.
>
> --brian
>
> --
> Brian F. G. Bidulock
> [email protected]
> http://www.openss7.org/
>



-- 
Regards
Mohammad Arif

_______________________________________________
Sigtran mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/sigtran