I added the bar-sav document to the wg individual documents list.
", "time": "2022-11-11T09:36:04Z"}, {"author": "Kotikalapudi Sriram", "text": "@Roland: Can you please share some pointers for the measurements showing reductions in successful DDoS attacks?
", "time": "2022-11-11T10:21:31Z"}, {"author": "Roland Dobbins", "text": "@Kotikalapuni \u2014\u00a0http://www.netscout.com/threatreport
", "time": "2022-11-11T10:35:24Z"}, {"author": "Mingqing Huang", "text": "@ Sriram, yes indeed, if EFP-uRPF is widely deployed anywhere, it will work well for reflective attacks. the problems is that we can not asume that, we may need consider problem based on partial deployment/ collaboration
", "time": "2022-11-11T10:44:42Z"}, {"author": "Kotikalapudi Sriram", "text": "@Roland: Thank you. I go by Sriram
", "time": "2022-11-11T10:45:25Z"}, {"author": "Roland Dobbins", "text": "@Sriram \u2014 right, I just saw that the name-order was backwards, apologies. ;>
", "time": "2022-11-11T10:45:49Z"}, {"author": "Kotikalapudi Sriram", "text": "@Mingqing Not widely. Just AS1 in slide 7 can deploy it on the customer side on the other side where the attack is originating from.
", "time": "2022-11-11T10:50:59Z"}, {"author": "Roland Dobbins", "text": "We're hearing audio from the room, but not from the presenter.
", "time": "2022-11-11T10:56:28Z"}, {"author": "Roland Dobbins", "text": "We remote folks can't hear the presenter, who is presumably remote, as well.
", "time": "2022-11-11T10:56:59Z"}, {"author": "Roland Dobbins", "text": "Now we can. ;>
", "time": "2022-11-11T10:57:10Z"}, {"author": "Roland Dobbins", "text": "https://datatracker.ietf.org/doc/html/draft-baker-sava-cisco-ip-source-guard-00
", "time": "2022-11-11T11:10:53Z"}, {"author": "Tony Li", "text": "Volume is too low.
", "time": "2022-11-11T11:14:00Z"}, {"author": "Roland Dobbins", "text": "https://www.cisco.com/c/en/us/support/docs/broadband-cable/cable-security/20691-source-verify.html
", "time": "2022-11-11T11:14:03Z"}, {"author": "Tony Li", "text": "Better, thank you.
", "time": "2022-11-11T11:14:29Z"}, {"author": "Kotikalapudi Sriram", "text": "@Mingqing Also, if you are comparing with the existing solutions like EFP-uRPF, perhaps BAR-SAV should be included, especially since it is a significant improvement over EFP-uRPF. I realize it is still under discussion in IETF. But it is fairly well documented.
", "time": "2022-11-11T11:28:23Z"}, {"author": "Aijun Wang", "text": "If you have any question, please send it to the mail
", "time": "2022-11-11T11:28:26Z"}, {"author": "Aijun Wang", "text": "we are overtime now. 3 more minutes for the entire session
", "time": "2022-11-11T11:29:45Z"}, {"author": "Roland Dobbins", "text": "Where can we see the source code for the implementation of this SAV mechanism?
", "time": "2022-11-11T11:31:21Z"}, {"author": "Doug Montgomery", "text": "What device was the DUT in these tests?
", "time": "2022-11-11T11:31:26Z"}, {"author": "Mingqing Huang", "text": "@ Sriram, sure. BAR-SAV is a good proprosal to address the limitation of algorithm A of current RFC. however , in general, the goal is still focus on the spoofed traffic going outside the CC
", "time": "2022-11-11T11:33:08Z"}, {"author": "Darren Dukes", "text": "A few observations from a quick read of the drafts:
", "time": "2022-11-11T11:35:29Z"}]