Re: SUA: CLDT: RC Parameter

Tolga,

There is absolutely no reason to do so.

--brian

Tolga Asveren wrote:                                                 (Fri, 02 Jun 2006 09:33:37)
> Hi Ilie,
> 
> Oh O.K., I see your point. Yes, the clarification added in M3UA-IG should be
> there in SUA-IG as well. SE-IPSP model is a peer-to-peer signaling
> relationship where the peers are the IPSP on each side, hence it should be
> identified by declaring the traffic range used for this relationship for
> both AS.
> 
>     Thanks,
>      Tolga
> 
> > -----Original Message-----
> > From: Ilie Glib [mailto:[email protected]]
> > Sent: Thursday, June 01, 2006 4:05 AM
> > To: Tolga Asveren
> > Cc: sigtran
> > Subject: Re: [Sigtran] SUA: CLDT: RC Parameter
> >
> >
> > Hello Tolga,
> >
> > my assumption was that each AS in the picture below is defined by its
> > destination address only, and there is no source address in the RK
> > definition. For instance, I have AS1=SSN1, AS2=SSN2 on one side, and
> > AS3=SSN3, AS4=SSN4 on the other side. This is possible according to
> > SUA RFC, and it shall work in single exchange mode (M3UA RFCbis does
> > not allow this configuration for SE mode, and mandates that RK defines
> > both source and destination addresses when SE is in use), unless we
> > explicitly prohibit this configuration in SUA implementers' guide,
> > that is, make source and destination addresses mandatory parts of SUA
> > RK definition in SE as M3UA does.
> >
> > Thank you
> >
> > Ilie
> >

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