<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>RPKI and IRR should be part of the prefix-list generation process, from there setup rpf-check with a fail-filter pointing to an ACL that allows source traffic matching the prefix-list and drops the rest. Although at that point you can just apply said ACL to the L3 interfaces supplying the BGP handoff.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Ryan<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> NANOG <nanog-bounces+ryan=rkhtech.org@nanog.org> <b>On Behalf Of </b>Mike Hammett<br><b>Sent:</b> Monday, November 7, 2022 3:17 PM<br><b>To:</b> Charles Rumford <charlesr@deft.com><br><b>Cc:</b> nanog@nanog.org<br><b>Subject:</b> Re: BCP38 For BGP Customers<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>This may not exist yet, but what about a uRPF-like feature that uses RPKI, IRR, etc. instead of current BGP feed?<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br><a href="http://www.ics-il.com">http://www.ics-il.com</a><br><br>Midwest-IX<br><a href="http://www.midwest-ix.com">http://www.midwest-ix.com</a><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><hr size=2 width="100%" align=center id=zwchr></span></div><div><p class=MsoNormal><b><span style='font-size:12.0pt;font-family:"Helvetica",sans-serif;color:black'>From: </span></b><span style='font-size:12.0pt;font-family:"Helvetica",sans-serif;color:black'>"Charles Rumford via NANOG" <<a href="mailto:nanog@nanog.org">nanog@nanog.org</a>><br><b>To: </b><a href="mailto:nanog@nanog.org">nanog@nanog.org</a><br><b>Sent: </b>Monday, November 7, 2022 10:47:54 AM<br><b>Subject: </b>BCP38 For BGP Customers<br><br>Hello -<br><br>I'm are currently working on getting BCP38 filtering in place for our BGP <br>customers. My current plan is to use the Juniper uRPF feature to filter out <br>spoofed traffic based on the routing table. The mentality would be: "If you <br>don't send us the prefix, then we don't accept the traffic". This has raised <br>some issues amongst our network engineers regarding multi-homed customers.<br><br>One of the issues raised was if a multi-homed BGP customer revoked a prefix from <br>one of their peerings, but continued sending us traffic on the link then we <br>would drop the traffic.<br><br>I would like to hear what others are doing for BCP38 deployments for BGP <br>customers. Are you taking the stance of "if you don't send us the prefix, then <br>we don't accept the traffic"? Are you putting in some kind of fall back filter <br>in based on something like IRR data?<br><br>Thanks!<br><br>-- <br>Charles Rumford (he/his/him)<br>Network Engineer | Deft<br>1-312-268-9342 | <a href="mailto:charlesr@deft.com">charlesr@deft.com</a><br>deft.com<o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p></div></div></div></body></html>