<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Oct 4, 2014 at 10:19 PM, Antonio Prado <span dir="ltr"><<a href="mailto:aprado@topnet.it" target="_blank">aprado@topnet.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">On 04/10/14 15:00, Sanjeev Gupta wrote:<br>
> When we setup peering with our upstreams, they usually ask us for IRR or<br>
> RIS, or in some cases, a Letter of Authority, to demonstrate that we own<br>
> the address space we announce.  How do I handle the <a href="http://192.175.48.0/24" target="_blank">192.175.48.0/24</a><br>
</span><span class="">> as it transits through AS 37989 upstream?<br>
<br>
</span>hi,<br>
<br>
being included in the list <a href="https://www.as112.net/ops-listing.html" target="_blank">https://www.as112.net/ops-listing.html</a> and<br>
pointing peers (or upstreams) to it should suffice<br>
</blockquote></div><br></div><div class="gmail_extra">Thank you, Antonio.  I am cc:ing 112 -at- <a href="http://root-servers.org">root-servers.org</a>, to be added to that page<br><br><table border="1" cellpadding="3"><thead><tr><th>Who
    </th><th>Where
    </th><th>Unicast<br>Addresses
    </th><th>Transit AS
    </th><th>Statistics
</th></tr></thead><tbody>
<tr><td>DCS1 Pte Ltd<br></td><td>SG<br></td><td>203.123.48.17<br>2405:fc00::112<br></td><td>37989
    </td><td>
<br></td></tr></tbody></table><br></div><div class="gmail_extra"><br><br clear="all"><div>-- <br>Sanjeev Gupta<br>+65 98551208   <a href="http://sg.linkedin.com/in/ghane" target="_blank">http://sg.linkedin.com/in/ghane</a><br></div>
</div></div>