On Sat, Apr 27, 2013 at 10:57 PM, Paul Hoffman <[email protected]>wrote:
> These requirements might be useful to add in the next draft, but they need > to be refined. > > On Apr 26, 2013, at 8:10 PM, Toby Mao <[email protected]> wrote: > > > The ADVPN solution SHOULD be able to implement Quality of Service (QoS) > to regulate the traffic in the ADVPN topology. > > Why is this statement needed? Do you see situations where an ADVPN > solution would be *prevented* from implementing some sort of QoS because it > was an ADVPN? > [Toby]: There is no situation that ADVPN solution could be prevented from implementing Qos. Actually, Qos is crucial on ADVPN, such as sharing network bandwidth, meeting the application latency requirement. Especially in the Hub, for each spoke, the Qos policy should be implemented individually , because different spoke has different link speed and data processing capability. Thus, in the ADVPN solution, the small spoke can not be overrun by hub by sending too much traffic, also the spoke which has large bandwidth cannot hog the hub's resources and starve other spokes. In addition, a unique Qos policy for each spoke in the hub could be cumbersome for administrator, some improvement could be implemented, such as the spokes with the same bandwidth can belong to the same group, the Qos policy can be implemented on a basis of group. > > > ADVPN peer SHOULD NOT send excessive traffic to the other members of > ADVPN. > > How would you define "excessive"? Where would that measurement be done? [Toby] The traffic to the ADVPN peer exceeding the actual peer bandwidth can be defined as "excessive". To solve this problem, the other ADVPN peer should apply Qos policy for this ADVPN peer. > The traffic for each ADVPN peer CAN be measured individually for shaping > and policing. > > Why is this statement needed? Do you see situations where an ADVPN > solution would be *prevented* from measuring individually? [Toby] The reason is explained in the first answer. > > --Paul Hoffman
_______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
