<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On 6 Mar 2015, at 5:55 pm, <a href="mailto:daniel@glovine.com.au" class="">daniel@glovine.com.au</a> wrote:<br class=""><div><blockquote type="cite" class=""><span style="font-family: Calibri, sans-serif; font-size: 11pt;" class="">He was interested to know if he can peer with a separate ASN to what he uses for transit, AKA</span><br class=""><div class=""><div class="WordSection1" style="page: WordSection1; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">Transit ASN 1001</span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Peering ASN 1002<o:p class=""></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">And then setting up BGP between the 2</span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">Would this work correctly using internal IP’s between the 2 BGP sides?</span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">By my knowledge I believe this could work, But want to make sure</span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></div></div></div></blockquote><br class=""></div><div>It isn’t a question of whether it <i style="font-weight: bold;" class="">could</i> work, it’s a question of what possible reason you’d have to do it that way.</div><div><br class=""></div><div>Why not transit and peering on the same ASN, just like virtually every other network operator on the planet? What is driving your customer to invent a unique deployment with side-effects they (and you) aren’t equipped to debug, when there are tens of thousands of networks out there doing exactly the same thing in a standard, well-understood way?</div><div><br class=""></div><div>Sounds like complexity for complexity’s sake.</div><div><br class=""></div><div> - mark</div><div><br class=""></div><div><br class=""></div><br class=""></body></html>