the RFC2125: The PPP Bandwidth Allocation Protocol (BAP) / The PPP Bandwidth
Allocation Control Protocol (BACP) describes some methods to dynamic Bandwidth
Allocation in Multilink PPP. But it only can add, remote a link dynamic, why not go
further for the ppp it self to allocate Bandwidth dynamically in the use of just only
one link, i mean negotiating how much bandwidth peer need and without any interrupt.
for example, in the pppoe scenario, if we have to implement QOS between the BAS
and pppoe client( note: no just bandwidth control or limit), what to do? extending
the ppp or extending the pppoe? which it the best? for the ppp is so pop in the
network access field, why not just extending the ppp it self?
i mean, extending the ppp, let the ppp(lcp or ncp for more accurate) can be use as
a signal protocol, just like rsvp, so all other protocols such as pppoe, l2tp can
benefit from it.
"PPP delivers the packet to IP, possibly with a QoS "label", and IP uses the QoS
to decide how to queue and schedule the packet"
yes, i can not agree u more. but it is the data panel not the control panel, how
a ppp end point know how much bandwidth the other ppp end point needs? traditionally,
it can be predefined by administrator. why not do this just more automatically, so the
peer can dynamically change QOS at any time?
thanks.
