Re: [M3UA] Double Exchange procedures

Adnan Hasnain Alam <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <[email protected]>
Hi Brian, David,
IPSP SE mode confuses me. What is the RC value that should be sent in the
ASP Active message? And what should be the routing key that would be
associated with this RC value? Would routing key define traffic in both
directions (how do you do that!) or only in one direction.

In IPSP DE mode, I am clear that each node would send its local RC value in
the ASP Active. And the routing key associated with this local RC value
would only define the nature of incoming traffic at this node.

Therefore I prefer IPSP DE mode. IPSP SE mode cause a lot of problems in
networks where there are many M3UA nodes interconnected in RC value
provisioning.

All the best,

Adnan

On Fri, Jun 5, 2009 at 8:53 PM, David Laight <[email protected]>wrote:

> > > How to know whether the peer IPSP/ASP is working as per
> > > Single Exchange or Double exchange ?
> > > Is it purely based on config only ?
> >
> > Configuration only.  A useful policy might be to assume SE mode
> > (as recommended in the RFC) with an option to configure DE mode
> > if you really see a need to support DE mode at all.
>
> I guess the only reason for DE is that it is symmetric.
> With SE one end has to do the client M3UA procedures and the
> other the server ones.
>
> I couldn't decide when a DE system would be able to send data,
> nor things like which routing context be included,
> so only implemented SE.
>
>        David
>
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1
> 1PT, UK
> Registration No: 1397386 (Wales)
> P Please consider the environment and don't print this e-mail unless you
> really need to
> _______________________________________________
> Sigtran mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/sigtran
>

_______________________________________________
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.