Barry Greene (bgreene) wrote:
E) There isn't any perceived new revenue to the network generated from
turning on sources address policing.
"E" is the #1 reason I've run into with SPs for not deploying source
address policing.
Agreed. In fact, if there was some way to make the application of source
address policing in some way a /sine qua non/ for any ISP with end
customer connections, then I think we would be most, if not all of the
way there. Indeed one of the goals of SAVA would be to significantly
increase the incentive to apply source address filtering.
Comment on the draft - L3 source validation we OK 10 years ago - but not
today. It has to be a L2/L3 source check today. This is why there are
more ports configured with DHCP Lease Query and IP Source Verify (both
L2/L3 source checks) then with uRPF Strict.
Agreed. In fact in the expanded framework that is being worked on, L2/L3
source checks in access networks is part of the picture.
_______________________________________________
routing-discussion mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/routing-discussion
--
"Product roadmap and/or product discussion in this email set forth
Juniper Networks' current intention and is subject to change at any
time without notice. No purchases are contingent upon Juniper
Networks delivering any feature or functionality expressed or implied
in this roadmap or product discussion."
-----------------------------------------------------------------
Mark Williams Juniper Networks
Liaison Beijing Office
Academic Networking Sector Tel: +86 10 6528 8800 x16032
Asia Pacific FAX: +61 7 3251 0155
[EMAIL PROTECTED] Cell: +86 1370-111-4749
_______________________________________________
Int-area mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/int-area
