Re: M3UA notify message
"Brian F. G. Bidulock" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Organization | http://www.openss7.org/ |
| Message-ID | <[email protected]> |
Tolga,
Tolga Asveren wrote: (Thu, 23 Feb 2006 14:34:22)
> Brian,
>
> Yes, obviously there is no issue for the single SGP case.
>
> I still think relying on the the private AS state of SGP for the traffic
> mode operation is a more elegant solution. It allows the ASPTM/ASPSM logic
> of SGPs run independently in a simplex way and requires some coordination
> only to generate SPMC, which is a MTP3 construct anyhow. I really interprete
> Greg's e-mail a bit different than you as well. To me, it seems that global
> AS-state issue was more to accomodate my complain about NTFYs, and to be
> honest I think he made the wrong decision. I think it is a better idea to
> keep ASP/SGP interface totally clean, where the concept of SG is not visible
> unless it is really required, i.e. for SSNM related issues, where SG is a
> single entity. This basically means to run ASPSM/ASPTM procedures
> independently on each SGP. Afterall, the concept of AS is a M3UA construct,
> and there we have the freedom to decide for its scope.
Then there would be no difference (other then SSNM) between an SG and an
SGP. We agreed years ago that there was a difference between an SG and
an SGP. An SG coordinates SPMC and AS/ASP state across all the SGP
serving an AS.
> I believe passages similar to below are describing use of the indpendent AS
> state for traffic mode related procedures: -from 4.3.4.3 ASP Active
> Procedures-
> In the case of an Override mode AS, reception of an ASP Active
> message at an SGP causes the (re)direction of all traffic for the AS
> to the ASP that sent the ASP Active message. Any previously active
> ASP in the AS is now considered to be in state ASP-INACTIVE and
> SHOULD no longer receive traffic from the SGP within the AS. The SGP
> or IPSP then MUST send a Notify message ("Alternate ASP_Active") to
> the previously active ASP in the AS, and SHOULD stop traffic to/from
> that ASP. The ASP receiving this Notify MUST consider itself now in
> the ASP-INACTIVE state, if it is not already aware of this via
> inter-ASP communication with the Overriding ASP.
No, no, no. See Ken's note on override mode from the old mail thread.
Ken describes the following scenario (his is more complicated):
ASP1/AS1 ASP2/AS1 SGP1/SG1 SGP2/SG1
| | | |
|----ASPUP----------------------->| |
|<---ASPUP Ack--------------------| |
|<---NTFY(AS Inactive)(AS1)-------| |
|<---NTFY(Insuff ASPs)(AS1)-------| |
| | | |
| |----ASPUP---------------------->|
| |<---ASPUP Ack-------------------|
| |<---NTFY(AS Inactive)(AS1)------|
| |<---NTFY(Insuff ASPs)(AS1)------|
| | | |
|----ASPAC-(AS1)----------------->| |
|<---ASPAC Ack-(AS1)--------------| |
|<---NTFY(AS Active)(AS1)---------| |
|<---NTFY(Alt ASP Act)(AS1)(ASP1)-| |
| |<--NTFY(AS Active)(AS1)---------|
| |<--NFTY(Alt ASP Act)(AS1)(ASP1)-|
| | | |
|<---DATA-------------------------| |
|<---DATA-------------------------|<--DATA---------|
|<---DATA-------------------------| |
|<---DATA-------------------------|<--DATA---------|
| | | |
| |---ASPAC (AS1)----------------->|
| |<--ASPAC Ack (AS1)--------------|
| |<--NTFY(Alt ASP Act)(AS1)(ASP2)-|
|<---NTFY(Alt ASP Act)(AS1)(ASP2)-| |
| | | |
| | |---DATA--------\|
| |<--DATA-------------------------|
| | |---DATA--------\|
| |<--DATA-------------------------|
| | |---DATA--------\|
| |<--DATA-------------------------|
| | | |
| | | |
Above, SGP2 follows the text in 4.3.4.3 to the letter; however, AS/ASP
state is coordinated across the SGPs serving the AS in accordance with
1.4.1.
When SGP2 receives the ASP Active it redirects traffic to ASP2. Note
that it must also redirect traffic from SGP1. ASP1 is now considered
ASP-INACTIVE in the AS. This is also true on SGP1.
Ken mentioned that the way to resolve problems with override mode was
to act only on the last ASP Active received by the SG. Which means
that the procedures are executed by the SGP with knowledge of the
overall (SG-wide) state of an ASP within an AS.
> Now, before we start exchanging thousands of e-mails, let me tell that I
> don't think any of the choices is "wrong". Both of them will work as long as
> both ASP and SGP have the same interpretation. Obviously the first priority
> is to document the consensus clearly in the RFC/IG. I don't think the text
> is clear enough. My and other peoples confusion is a good evidence for that.
> My personal opinion is that there is contradicting stataments in the RFC/IG
> and I don't necessarily aggree with you that everything is put there
> actually with a unified view of how things are supposed to work.
There are not contradicting statements.
> I think the two options are clearly explained in this thread in terms of how
> they are supposed to work. My personal choice is to have all ASPSM/ASPTM
> independent on SGPs, without using any global AS state for that purpose.
Cannot work. And is contrary to the existing RFC and the design
approach agreed by concensus leading to wide ranging changes between
M3UA Draft 7 and M3UA Draft 8.
> AFAICS, you are in the opinion that using global-AS state on SGPs for
> certain ASPTM procedures is a better idea. I think Barry and Lincoln think
> similar to you(?). For other people, I don't have a clear guesstimate. I
> also would think that it would be useful to have opinions from more people.
> In any case, let's decide what needs to be done and do it.
Nothing needs to be done, except a few examples. If you have another
proposal, please, craft some text and propose it.
--brian
--
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/