Re: How to share Routing info. in IPSPs communication at M3UA level

[email protected]
Newsgroups gmane.ietf.sigtran
Message-ID <OFD399B2FA.A09ECD35-ON65257281.0031759A-88257281.007DB9EF@relianceada.com>
Thanks for instant response , it means after receiving ASPUP-ACK message 
by IPSP-A , IPSP-A should be send REGREQ to IPSP-B to register itself. 
Like this...
                          IPSP-A                           IPSP-B
                     |                                |
                     |-------------ASP Up------------>|
                     |<----------ASP Up Ack-----------|
                           |                                |
                     |----------- REG REQ (RKa)------>|(?)
                     |<---------- REG RSP (RCb)-------|
                           |                                |
                     |<------- ASP Active(RCb)--------|  RC: Routing 
Context
                     |-----ASP Active Ack (RCb)------>|      (optional)
                     |                                |
                     |                                |
                     |<=========  DATA (RCb) ========>|
                     |                                |
                     |<-----ASP Inactive (RCb)--------|  RC: Routing 
Context
                     |----ASP Inactive Ack (RCb)----->|      (optional)
                     |                                |
                     |<-----------ASP Down------------|
                     |---------ASP Down Ack---------->|
                     |                                |

Now my question is this, How will IPSP-B generate Routing Context(RCb) 
from Routing Key(RKa) of IPSP-A? Is there any algorithm to do this? thanks 
in advance...


With Regards,
Dheeraj 




"Brian F. G. Bidulock" <[email protected]> 
02/13/2007 12:24 AM
Please respond to
[email protected]


To
[email protected]
cc
[email protected]
Subject
Re: [Sigtran] How to share Routing info. in IPSPs communication at M3UA 
level






Dheeraj.Dubey,

The RC can be provisioned at either or both sides.  A side not 
provisioning
the RC may register a routing key with the other.  The exchange is the 
same
as for AS-SGP registration where the IPSP registering behaves like the AS
and the IPSP providing registration behaves like the SGP.

--brian

[email protected] wrote:            (Mon, 12 Feb 2007 
23:41:45)
> 
>    Dear
>    According  to  rfc   4666,  This is the call flow for  Single 
Exchange
>    IPSPs  Communication  at  M3UA level, I can't be able to know how 
they
>    exchange  their  Routing  Keys  and  how  to create respective 
Routing
>    Context(RCb). thanks in advance...
>                      IPSP-A                           IPSP-B
>                     |                                |
>                     |-------------ASP Up------------>|
>                     |<----------ASP Up Ack-----------|
>                     |                                |
>                           |<------- ASP Active(RCb)--------|  RC: 
Routing
>    Context
>                     |-----ASP Active Ack (RCb)------>|      (optional)
>                     |                                |
>                     |                                |
>                     |<=========  DATA (RCb) ========>|
>                     |                                |
>                           |<-----ASP Inactive (RCb)--------|  RC: 
Routing
>    Context
>                     |----ASP Inactive Ack (RCb)----->|      (optional)
>                     |                                |
>                     |<-----------ASP Down------------|
>                     |---------ASP Down Ack---------->|
>                     |                                |
>    With Regards,
>    Dheeraj

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


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

_______________________________________________
Sigtran mailing list
[email protected]
https://www1.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.