[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sigtran] [M3UA] SE Override
Evgenij,
Yes the sequence you portray is correct, assuming that
Node13 operation is intended to be in M3UA traffic
Override mode, either by external shared "knowledge",
or by specification of the traffic mode in the ASP-Active
and ASP-Active-Ack messages.
As a result of the first exchange, IPSP2 is instructed
to transmit data to Node13 by way of IPSP1 only.
Some time later, IPSP3 took action to activate itself.
As this is in override mode, IPSP3's activation overrides
IPSP1's previous activation. IPSP1 becomes INACTIVE on
receipt of the Notify Alt ASP Active.
As a result of the later exchange, IPSP2 is instructed
to transmit data to Node13 by way of IPSP3 only.
I have assumed that the first exchange ASP-Active-Ack
(and first Notify AS Active) travelled from IPSP2 to
IPSP1, and were not somehow bidirectional.
With thanks, from Chris Benson.
On Tue, 3 Nov 2009, Evgenij wrote:
>> Date: Tue, 3 Nov 2009 11:54:25 +0300
>> From: Evgenij <evgenij.fokin at gmail.com>
>> To: <bidulock at openss7.org>, <evgenij.fokin at gmail.com>, <sigtran at ietf.org>
>> Subject: Re: [Sigtran] [M3UA] SE Override
>>
>> Sorry in previous sequense was mistake. Notify AltAspActive had wrong direction.
>>
>> Configuration:
>>
>> IPSP1
>> / \
>> User---Node2---IPSP2 Node13---User
>> \ /
>> IPSP3
>>
>> IPSP1------------------------IPSP2------------------------IPSP3
>> | | |
>> 1 | -> Asp Activate -> | |
>> 2 | <- Asp Activate Ack -> | |
>> 3 | <- Notify As Active -> | |
>> 4 | | -> Notify As Active |
>>
>> Some time later
>>
>> 5 | | -> Asp Activate |
>> 6 | | <- Asp Activate Ack |
>> 7 | <- Notify AltAspActive<- | |
>>
>>
>> ---
>>
>> Regards
>>
>> Evgenij
>>