Re: Behaviour in DE-IPSP model when ASPAC does not haveany RC.

Brain,

Can we also interpret your bellow statement like this --> In IPSP double exchange mode ASPACT from both sides MUST include the Routing context of its local AS. 

If that is correct then why in the RFC section 5.6.2 its mentioned that Routing Context is optional in ASPAC message.

Thanks
Suresh.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of ext Brian F. G. Bidulock
Sent: Wednesday, March 24, 2010 9:11 PM
To: Anand N Ilkal
Cc: [email protected]
Subject: Re: [Sigtran] Behaviour in DE-IPSP model when ASPAC does not haveany RC.

Anand,

For each full duplex flow, DE requires one RC at one peer and another at the
other peer.  This requires a double-ended exchange to activate using RC.
Where the IPSP has a conifgured AS (see 4.3.4.3 second paragraph), no RC is
required in ASPAC, in which case, the AS at each end is known by both sides
and a single-ended exchage _could_ be possible.  That is all that it is saying.

--brian

Anand N Ilkal wrote:                                                                 (Wed, 24 Mar 2010 08:17:57)
> 
>    Hello,
>    In Double Exchange mode under IPSP-IPSP model. what should be the
>    behaviour in case Remote Peer sends ASPAC without any Routing Context?
>    Section 4.3.1 in RFC 4666 indicates the Single Exchange behaviour can
>    be followed -
>    extracts from RFC 4666 -
>    "ASPTM messages. When sending ASPTM messages to activate/deactivate
>    all the traffic independently of routing keys by not specifying any
>    RC, a single exchange could be sufficient."
>    Does it mean the local peer does not have to send ASPAC to the peer?
>    Or is it just talking about multiple AS's in the remote peer? By
>    sending only one ASPAC with no RC, it is updating the status for all
>    the AS's in the remote peer which are served by the same ASP?
>    --
>    with regards,
>    Anand kumar Ilkal

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


-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sigtran