Re: Query regarding re-registration procedure in m3ua.

[email protected]
Newsgroups gmane.ietf.sigtran
Message-ID <[email protected]>
Hi,
 
Is the below call flow right for re-registration procedure.
 
ASP                                                  SG
--------                                              ----------
   |                                                     

--- On Tue, 3/3/09, Brian F. G. Bidulock <[email protected]> wrote:


From: Brian F. G. Bidulock <[email protected]>
Subject: Re: Query regarding re-registration procedure in m3ua.
To: [email protected]
Cc: "sigtran" <[email protected]>, [email protected]
Date: Tuesday, March 3, 2009, 8:21 AM


-----Inline Attachment Follows-----


moharana_p,

It would be better if you read the specification.

See RFC 4666/4.4.1 Registration:

   ...

   An ASP MAY request modification of an existing Routing Key by
   including a Routing Context parameter in a Registration Request
   message.  Upon receipt of a Registration Request message containing a
   Routing Context, if the SGP determines that the Routing Context
   applies to an existing Routing Key, the SGP MAY adjust the existing
   Routing Key to match the new information provided in the Routing Key
   parameter.  A Registration Response "ERR Routing Key Change Refused"
   is returned if the SGP does not support this re-registration
   procedure or RC does not exist.  Otherwise, a Registration Response
   "Successfully Registered" is returned.

   ...

--brian

[email protected] wrote:              (Tue, 03 Mar 2009 04:47:28)
> 
>    Hi All,
> 
> 
>    I have some doubt regarding the RC parameter value in the REG REQ
>    message.
> 
> 
>     1. As per the RFC4666 the RC is an optional parameter in the REG REQ
>        message. Should REG REQ message contain RC parameter during
>        registering a RK first time or RC parameter is only needed during
>        re registration procedure?
>     2. In which scenario re registration of RK is required?
> 
> 
>    Br,
>    Padmalochan

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

_______________________________________________
Sigtran mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sigtran
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.