draft-ietf-bmwg-sdn-controller-benchmark
"Ger, Javier" <[email protected]>
| Newsgroups | gmane.ietf.bmwg |
|---|---|
| Message-ID | <94E7360D59AAB64F852152C5579B5F22802FD308@HERMES-MBX2.corp.cablevision.com.ar> |
Hi Bhuvan, I was wondering if defining more precisely what DoS attacks mean makes sense. Although there are several DoS attack types, based in the document content I assume it is referring to volumetric attacks, so it could be useful to include this clarification in the "term" draft. Additionally, if my previous assumption is true, I was also wondering if having a clear baseline or values related to DoS attacks can help (basically would allow running different tests consistently and avoid misinterpretations). Since the increased amount of requests (packets/traffic/sessions/etc.) is the typical behavior of the volumetric DoS attacks, in the "meth" draft you could include some value in order to define when you are considering that a certain volume of these requests mean a volumetric DoS attack is ongoing. Probably giving just one fixed value can be difficult because it will vary from one controller to another (in fact depending of their performance). But perhaps a table including a list/group of them or even some relative values based in what you have already measured about the controller performance in the first part of the procedure can give some kind of curve or ramp about how each value of illegitimate requests affects performance until the controller goes off. Regards. Visite https://www.cablevisionfibertel.com.ar<br>__________________________________________<br> Este mensaje es confidencial. Puede contener informacion amparada por el secreto comercial.<br>Si usted ha recibido este e-mail por error, debera eliminarlo de su sistema.<br>No debera copiar el mensaje ni divulgar su contenido a ninguna persona.<br>Muchas gracias.<br>This message is confidential. It may also contain information that is privileged or not authorized to be disclosed. If you have received it by mistake, delete it from your system.<br>You should not copy the messsage nor disclose its contents to anyone.<br>Many thanks.<br>__________________________________________ _______________________________________________ bmwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/bmwg