[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Alternative to draft-ash-mpls-diffserv-te-class-types-00.txt ?
That's an interesting statement. Do you mean that preemption should only be allowed for protection traffic preempting primary traffic of sufficiently low priority?
"Lai, Wai S (Waisum), ALSVC" <firstname.lastname@example.org> on 21/11/2001 22:53:44
cc: (bcc: Sven VAN DEN BOSCH/BE/ALCATEL)
Subject RE: Alternative to
Under normal conditions, a network should be properly dimensioned so that
preemption is not needed while ensuring that service objectives are met.
Preemption used under overload often leads to network instability. Hence,
preemption is not a remedy for lack of network capacity, or lack of proper
capacity planning and provisioning in the network dimensioning process.
Thanks, Wai Sum.
From: Balazs Szviatovszki [mailto:Balazs.Szviatovszki@eth.ericsson.se]
Sent: Wednesday, November 21, 2001 10:36 AM
To: Naidu, Venkata
Cc: Lai, Wai S (Waisum), ALSVC; email@example.com
Subject: Re: Alternative to
I suppose the idea behind higher priority for control traffic is to assure
proper link-state routing operation in sever overloads. Check out this
"Proposed Mechanisms for Congestion Control/Failure Recovery in OSPF & ISIS
Still, I would not dare to say that there should not be preemption among
other non-control traffic types. Recall, the draft of Jim, proposed that it
should be configurable which class-type could preempt which one
class voice use priority 2
class data use priority 4
[mpls preempt <yes|limited|map|no>]
----------> [preempt map voice over data]
[class mute <list>]
Previous idea was that higher priority can preempt any lower priority. I
think this is the concept actually coded in many MPLS implementations.
"Naidu, Venkata" wrote:
> Wai Sum:
> I didn't understand why control traffic is so different?
> Draft recommends, no preemption of LSPs and/or transport
> links across CTs, except for control-traffic CT. (Why?)
> * I mentioned my concern about CT6 because, control traffic is
> also *some data* in IP sense. For good example, I can send
> OSPF/RSVP Hellos in one particular CT and all other Control
> messages (updates etc) in other CTs. Don't you agree?