[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
some comments on I-D Action:draft-takacs-ccamp-revertive-ps-00.txt
Attila,
I have planned respond to this for same time, but did not really
had time to get around to it.
Attila Takacs wrote:
Hi Loa,
I assume a part of your comment/question relates to problems with
reversion if LSP setup and holding priorities are mismatched.
that would be one case, but not really what i was thinking of
In this
case the worker may be already deleted before the reversion would take
place. This is certainly an interesting question...
sure
...at a first thought an explicit revertive bit may be used to override
the priorities for LSPs with revertive protection.
I've two questions:
1. If revertiveness is the normal procedure, wouldn't it be better to
let indicate LSPs that *shouldn't* revert?
2. What I really thought about was, how does revertiveness work with
traffic placement policies?
Assume that you have a policy that that says you want to optimize the
chances to successfully set up an LSP that make a maximum share of some
constraints. It could be any constraints, but thinking of it as bw
wouldn't wrong.
Assume also that you have three different routes form A to B, through
C, D and E respectively.
Assume that each of the nodes C, D and E has interfaces with constraint
of 100. This is of course a very simplified model just to illustrate my
point.
In order the follow your policy you place traffic on C and E, and leave
D free, if there is a request for an LSP that requires 100. So the
situation could be:
C = 40 occupied, 60 free
D = 100 free
E = 40 occupied, 60 free
now if C fails it makes sense to move the traffic to E:
C = failed
D = 100 free
E = 80 occupied, 20 free
If the failure takes some time to repair, there might be a request
for a LSP that requires 60, the only possibility is to place on D:
C = failed
D = 60 occupied, 40 free
E = 80 occupied, 20 free
Now C comes back up:
C = 100 free
D = 60 occupied, 40 free
E = 80 occupied, 20 free
This situation is in accordance with your policy, but if you
revert you loose the ability to place any LSPs which requires
more than 60
C = 40 occupied, 60 free
D = 60 occupied, 40 free
E = 40 occupied, 60 free
Why would you want to revert in this case?
Now there might be some optimization program working in the background,
that might move traffic from any of nodes to any of the other, possibly
from C to E.
I seems to me that running an optimization program is more efficient.
/Loa
Best regards,
Attila
--
Loa Andersson
Principal Networking Architect
Acreo AB phone: +46 8 632 77 14
Isafjordsgatan 22 mobile: +46 739 81 21 64
Kista, Sweden email: loa.andersson@acreo.se
loa@pi.nu