<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div><blockquote type="cite"><br></blockquote><blockquote type="cite">ie. how would I solve the /22 into transit, /24 more specifics via MLPA <br></blockquote><blockquote type="cite">any better in your model? What extra control and nerd knobs do I get?<br></blockquote><br>The model was that there were two or three routing clouds: An users<br>and services cloud, and transit network cloud. The goal is to have<br>the /22s are known in the transit cloud, the /24s are known in the<br>services cloud.</div></blockquote><div><br></div>I understand that's the goal, but the reality is - how does your model give me the actual ability to do that?</div><div>If I can conjure up a set of filters to do that in your model, then I can equally apply that same filter set to the current model. Why do I need three different clouds and tunnels to apply a set of filters that I can apply anyway?</div><div><br></div><div>ie. if I can come up with a filter that's smart enough not to propogate /24s from an IX when I have a /20 from a transit customer at the border between your "clouds" then why can't I just apply that same smart filter at the peering router where I connect to the peering exchange? What does the extra clouds buy me?</div><div><br><blockquote type="cite"><div><br>On the border between the transit cloud and the local internet<br>exchange, you do nothing because that border doesn't exist.</div></blockquote><div><br></div><div>You've lost me here. How do my transit customers get access to the resources at the internet exchanges I peer at? Why not just drop peering at MLPAs? </div><div><br></div><br><div>MMC</div></div><div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>-- <br>Matthew Moyle-Croft Internode/Agile Peering and Core Networks<br>Level 4, 150 Grenfell Street, Adelaide, SA 5000 Australia<br>Email: <a href="mailto:mmc@internode.com.au">mmc@internode.com.au</a> Web: <a href="http://www.on.net/">http://www.on.net</a><br>Direct: +61-8-8228-2909<span class="Apple-tab-span" style="white-space: pre; "> </span><span class="Apple-tab-span" style="white-space: pre; "> </span> Mobile: +61-419-900-366<br>Reception: +61-8-8228-2999 Fax: +61-8-8235-6909<br></div></div></span> </div><br></body></html>