RE: RFC 4666 M3UA - Reg Request Message

Jitin,

There were some concerns about how to handle ISUP group messages, e.g. how
to generate a unique answer in the SG etc..., and so CIC-range support in
dynamic registration was dropped. SSN had a similar fate.

One could argue that generating a unique answer for group messages in the SG
is an implementation dependent feature and does not require support from
on-the-wire protocol (and I am aware of some products which do exactly
this), no CIC support in dynamic registration is the current official
approach.

    Thanks,
    Tolga

> -----Original Message-----
> From: Bhandari, Jitin (Jitin) [mailto:[email protected]]
> Sent: Wednesday, November 01, 2006 2:42 PM
> To: '[email protected]'
> Subject: [Sigtran] RFC 4666 M3UA - Reg Request Message
>
>
>
> Hello,
>
> We looked into the RFC-4666 and now we have serious concerns
> regarding the routing key parameter for Registration Request Message.
>
> Can anyone please provide us an explanation/background as why did
> we drop "Circuit Range List" parameter from the Routing Key
> Parameter description for RFC-4666?
>
> Please refer Section 3.6.1 (RFC-3332) where this parameter was
> present and Section 3.6.1 for RFC-4666 where this parameter is removed.
>
> CIC Resources are allocated dynamically in SS7 networks and
> provisioning of CIC resources changes quite often. Dynamic
> Registration procedure at M3UA is facilitating this flow through
> provisioning changes between MGC & SG.
>
> With the omission of this parameter from the Routing Key
> Definition in RFC-4666, we have limited the scope of Dynamic
> registration procedure and rather made it un-usable. The current
> parameters for Routing Key at Registration Request message can
> very well be defined via Static routing methods (via LM). CIC
> Range was a key parameter to this message.
>
> Please explain the thoughts behind getting rid of this key
> parameter from "Routing Key" definition.
>
> Also, we acknowledge that the Dynamic registration procedure for
> RFC-3332 had its own limitation but getting rid of CIC Range
> parameter is only going to make Dynamic registration procedure un-usable.
>
> Please comment.
>
> -Jitin
>
>
> _______________________________________________
> Sigtran mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/sigtran