<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)">
<style><!--
/* Font Definitions */
@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:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Reading between the lines this network’s current lack of diverse providers is consistent with a geographic/monopoly disadvantage. I do agree that your transit provider is in bad form to pad your routes, but it does happen. A phone call
or email to understand their limitations may be helpful. Trying to fit all of your traffic into an upstream’s own uplink that is far to small does not provide the best user experience. It could be an bug in the route-map. Speaking of bugs, trying to use
communities can cause you to observe bugs in other network’s route-maps (with great power comes great…).
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Padding much past three usually has little affect. Splitting your advertisement into say four smaller announcements and starting to advertise them one at a time through your preferred provider is a good place to start. Traffic will prefer
the more specific route. With luck that was done last night <span style="font-family:"Segoe UI Emoji",sans-serif">
😊</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Once you have balanced this out somewhat, you have bought yourself time. Next fun thing is to understand how this works when one provider fails or similar. Traffic can prefer the oldest route, so a small bump down the road can cause unanticipated
traffic changes the next nightly peak. Or to put it another way, this is how the sausage is made.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">P.S. Both of us top posting is also bad form.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt">Kevin Burke<o:p></o:p></span></p>
<p class="MsoNormal">802-540-0979<o:p></o:p></p>
<p class="MsoNormal">Burlington Telecom<o:p></o:p></p>
<p class="MsoNormal">200 Church St, Burlington, VT<o:p></o:p></p>
</div>
<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+kburke=burlingtontelecom.com@nanog.org>
<b>On Behalf Of </b>Douglas Fischer<br>
<b>Sent:</b> Thursday, October 20, 2022 8:51 AM<br>
<b>To:</b> Pirawat WATANAPONGSE <pirawat.w@ku.th><br>
<b>Cc:</b> nanog@nanog.org<br>
<b>Subject:</b> Re: Newbies Question: Do I really need to sacrifice Prefix-aggregation to do BGP Load-sharing?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td width="10" style="width:7.5pt;border:solid black 1.0pt;border-right:none;background:#F00000;padding:.75pt .75pt .75pt .75pt">
</td>
<td style="border:solid black 1.0pt;border-left:none;background:#FFD11C;padding:3.0pt 3.0pt 3.0pt 3.0pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">WARNING!! This message originated from an
<strong><span style="font-family:"Calibri",sans-serif">External Source</span></strong>. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">If your Upstream(Transit provider) prepends your routes without you asking or authorizing it to do so, you should SERIOUSLY consider switching providers!<br>
<br>
In the other email I talked about traffic engineering BGP communities.<br>
If those prepends were made from some community you were applying... OK, that's great!<br>
Even better if you could apply a community that did something like "apply 2 prepends for south america only".<br>
<br>
But a Transit Provider changing the AS-PATH (in addition to the mandatory hop) arbitrarily without your consent is not for good people.<br>
<br>
<br>
P.S. Your email replies are breaking threads in email readers. I suggest you review the email client tool.<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Em qui., 20 de out. de 2022 às 09:16, Pirawat WATANAPONGSE via NANOG <<a href="mailto:nanog@nanog.org">nanog@nanog.org</a>> escreveu:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">Dear all,<br>
<br>
<br>
Before all else:<br>
thank you all for the lightning-fast responses (even taking the time zone advantage into account).<br>
I really, really, really appreciate all your recommendations.<br>
<br>
Virtually all of you recommend prepending as the first choice.<br>
I also get the feeling that you guys consider de-aggregation “distasteful” (at the least) but sometimes unavoidable.<br>
<br>
I have considered the prepending myself, but dare not implement it yet<br>
for the fear that BGP (Human) Community will burn me alive, witch-hunt style,<br>
because of the following reasons:<br>
1. I can see from looking glass(es) that my upstreams already practice prepending (some paths) at their level (at least 3 more hops [x4]), supposedly to “balance” their bandwidth.<br>
2. Should I start prepending mine, I might upset their balance, causing them to prepend more, thus starting a “prepend war”. [I imagine that x20+ prepending starts out this way]<br>
<br>
The way I see it, prepending (or maybe even the whole BGP-Path thing) is a local-optimization problem: it’s only best for someone, not globally.<br>
And the Higher-Tiers (Lower Tier-Numbers) will always “engineer” me in the end.<br>
<br>
Worse yet, I might be out-voted by de-aggregation insider “cultists” anyway.<br>
<br>
Which forces me to proactively ask you guys questions about ROV-Overlapping and ROV “Hijack Gap” soon, in another posting with separate “Subject:”.<br>
<br>
Again, Thank you.<br>
<br>
<br>
Cheers,<br>
<br>
Pirawat.<br>
<br>
<br>
P.S. [Off-Topic] Any comment on the “SCION” System?<br>
Any good (I will even take "academically")?<br>
[Reference: <a href="https://scion-architecture.net/" target="_blank">https://scion-architecture.net/</a>]<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">Douglas Fernando Fischer<br>
Engº de Controle e Automação<o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>