[100618] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: BGP Peering and Prefix filterin Question

daemon@ATHENA.MIT.EDU (Paul Stewart)
Mon Oct 29 14:40:07 2007

Date: Mon, 29 Oct 2007 14:37:59 -0400
In-Reply-To: <CCD4153D830F584982521DFC986BFF310DA3F6B4@tgainf06.TGASolutions.local>
From: "Paul Stewart" <pstewart@nexicomgroup.net>
To: "Jim McBurnett" <jim@tgasolutions.com>, <nanog@nanog.org>
Errors-To: owner-nanog@merit.edu


This is a multi-part message in MIME format.

------_=_NextPart_001_01C81A5A.D4D738B4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

hi there...
 
Who would have the time to monitor this if it was a manual process? ;)  
 
Personally, never heard of that but it may happen out there....
 
We use strict RADB filtering on 95% of our connections.  Once a day, we
run a copy of IRRPT against a list of peered AS's and update the
prefix-lists
 
For transit, we just sanitize the routes (drop private space, drop small
subnets etc.)
 
Take care,
 
Paul
 

________________________________

From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of
Jim McBurnett
Sent: Monday, October 29, 2007 2:15 PM
To: nanog@nanog.org
Subject: BGP Peering and Prefix filterin Question



Hello,

Recently I have been told that some ISP's are automatically or maybe
manually modifying their BGP inbound prefix listing after a network is
not advertised to them for a period of time.

 

So the questions I pose to the group:

1.       Is this normal?

2.       Can anyone share your policies?

3.       Who does it?

4.       How often?

5.       Is it automagic? Or the dirty work slaved off to the junior
engineer in the corner somewhere?

a.       I know you probably won't trust that junior engineer, but some
do....

 

Anyway just a little research after a small problem a customer recently
had.

 

 

Thanks,

Jim




 

-------------------------------------------------------------------------=
---

"The information transmitted is intended only for the person or entity to=
 which it is addressed and contains confidential and/or privileged material=
. If you received this in error, please contact the sender immediately and =
then destroy this transmission, including all attachments, without copying,=
 distributing or disclosing same. Thank you."
------_=_NextPart_001_01C81A5A.D4D738B4
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D 
"urn:schemas-microsoft-com:vml" xmlns:o =3D 
"urn:schemas-microsoft-com:office:office" xmlns:w =3D 
"urn:schemas-microsoft-com:office:word" xmlns:m =3D 
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"=
>
<META content=3D"MSHTML 6.00.6000.16544" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Calibri;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif=
"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif=
"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif=
"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans=
-serif"; mso-style-priority: 34
}
LI.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans=
-serif"; mso-style-priority: 34
}
DIV.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans=
-serif"; mso-style-priority: 34
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue><P>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007><FONT face=
=3DArial 
color=3D#0000ff size=3D2>hi there...</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007><FONT face=
=3DArial 
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007><FONT face=
=3DArial 
color=3D#0000ff size=3D2>Who would have the time to monitor this if it wa=
s a manual 
process? ;)&nbsp; </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007><FONT face=
=3DArial 
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007><FONT face=
=3DArial 
color=3D#0000ff size=3D2>Personally, never heard of that but it may happe=
n out 
there....</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007><FONT face=
=3DArial 
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007><FONT face=
=3DArial 
color=3D#0000ff size=3D2>We use strict RADB filtering on 95% of our 
connections.&nbsp; Once a day, we run a copy of IRRPT against a list of p=
eered 
AS's and update the prefix-lists</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007><FONT face=
=3DArial 
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007><FONT face=
=3DArial 
color=3D#0000ff size=3D2>For transit, we just sanitize the routes (drop p=
rivate 
space, drop small subnets etc.)</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007><FONT face=
=3DArial 
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007><FONT face=
=3DArial 
color=3D#0000ff size=3D2>Take care,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007><FONT face=
=3DArial 
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007><FONT face=
=3DArial 
color=3D#0000ff size=3D2>Paul</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971463118-29102007></SPAN>&nbsp=
;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> owner-nanog@merit.edu 
[mailto:owner-nanog@merit.edu] <B>On Behalf Of </B>Jim McBurnett<BR><B>Se=
nt:</B> 
Monday, October 29, 2007 2:15 PM<BR><B>To:</B> 
nanog@nanog.org<BR><B>Subject:</B> BGP Peering and Prefix filterin 
Question<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal>Hello,<o:p></o:p></P>
<P class=3DMsoNormal>Recently I have been told that some ISP&#8217;s are =
automatically 
or maybe manually modifying their BGP inbound prefix listing after a netw=
ork is 
not advertised to them for a period of time.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>So the questions I pose to the group:<o:p></o:p></P>
<P class=3DMsoListParagraph 
style=3D"TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"><![if !supportLi=
sts]><SPAN 
style=3D"mso-list: Ignore">1.<SPAN 
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; 
</SPAN></SPAN><![endif]>Is this normal?<o:p></o:p></P>
<P class=3DMsoListParagraph 
style=3D"TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"><![if !supportLi=
sts]><SPAN 
style=3D"mso-list: Ignore">2.<SPAN 
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; 
</SPAN></SPAN><![endif]>Can anyone share your policies?<o:p></o:p></P>
<P class=3DMsoListParagraph 
style=3D"TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"><![if !supportLi=
sts]><SPAN 
style=3D"mso-list: Ignore">3.<SPAN 
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; 
</SPAN></SPAN><![endif]>Who does it?<o:p></o:p></P>
<P class=3DMsoListParagraph 
style=3D"TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"><![if !supportLi=
sts]><SPAN 
style=3D"mso-list: Ignore">4.<SPAN 
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; 
</SPAN></SPAN><![endif]>How often?<o:p></o:p></P>
<P class=3DMsoListParagraph 
style=3D"TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"><![if !supportLi=
sts]><SPAN 
style=3D"mso-list: Ignore">5.<SPAN 
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; 
</SPAN></SPAN><![endif]>Is it automagic? Or the dirty work slaved off to =
the 
junior engineer in the corner somewhere?<o:p></o:p></P>
<P class=3DMsoListParagraph 
style=3D"MARGIN-LEFT: 1in; TEXT-INDENT: -0.25in; mso-list: l0 level2 lfo1=
"><![if !supportLists]><SPAN 
style=3D"mso-list: Ignore">a.<SPAN 
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; 
</SPAN></SPAN><![endif]>I know you probably won&#8217;t trust that junior=
 engineer, 
but some do&#8230;.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>Anyway just a little research after a small problem =
a 
customer recently had.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>Thanks,<o:p></o:p></P>
<P class=3DMsoNormal>Jim<o:p></o:p></P></DIV></P>
<P>&nbsp;</P>
<P>----------------------------------------------------------------------=
------</P>
<P><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><FONT 
face=3D"Times New Roman" size=3D3><SPAN 
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">"The information transmitte=
d is 
intended only for the person or entity to which it is addressed and conta=
ins 
confidential and/or privileged material. If you received this in error, p=
lease 
contact the sender immediately and then destroy this transmission, includ=
ing all 
attachments, without copying, distributing or disclosing same. Thank 
you."<BR></SPAN></FONT></SPAN></P></BODY></HTML>


------_=_NextPart_001_01C81A5A.D4D738B4--


home help back first fref pref prev next nref lref last post