<HTML>
<HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<font size="2">Dear Moin bhai,
<br />
<br />Thanks for your reply. I understand the NDA part. I don't want anyone to disclose anything.
<br />
<br />But many things have become clearer to me now. From an end ISP's point of view, to better utilize BGP partial or full routes or even to advertise larger prefixes for fail-over function, all our upstream IIGs should have Cache nodes directly connected to their ASes. Otherwise traffic becomes unbalanced for us, as far as Google/YouTube and other cache based services are concerned. Google cache nodes should look at BGP attributes too, at least AS_PATH lengths. Is there anyone from Google in this list? ;-)
<br />
<br />Best regards to all,
<br />
<br />ANIRUDDHA BARUA
<br />
Email: aniruddha.barua@colbd.com, cto@colbd.com
<br />
<br />
<br /><b>---------- Original Message
-----------</b>
<br />
From: Muhammad Moinur Rahman <5u623l20@gmail.com>
<br />
To: Aniruddha Barua <aniruddha.barua@colbd.com>
<br />
Cc: "nog@bdnog.org" <nog@bdnog.org>
<br />
Sent: Tue, 4 Feb 2014 18:32:03 +0600
<br />
Subject: Re: [bdNOG] How does Google select their Cache Engine IP nearest to the
request sender?
<br />
<br />> Hi Aniruddha Da,
<br />>
<br />> Due to NDA I cannot disclose much.
But so far my work they emphasize on advertising the prefix of your
resolver.�
<br />>
<br />> Let's say you are using a resolver A.B.C.D. This prefix or
a longer version is advertised to Cache Node. When you are querying for one of
their records they somehow check if your resolver is advertised towards any of
the Cache node's BGP feed. If it finds it in any of their Nodes they reply
with an IP address from that block otherwise they reply from their block. They
do not check any other BGP attributes just the availability of the
prefix.
<br />>
<br />> Hope this meets your thirst. If not let me know. Maybe next
week we can meet somewhere. I will be in CTG to deploy the same for you.
3:)
<br />>
<br />> BR,
<br />>
Moin
<br />>
<br />> On Tue, Feb 4, 2014 at 5:17 PM, Aniruddha Barua <span dir="ltr"><<a target="_blank" href="mailto:aniruddha.barua@colbd.com">aniruddha.barua@colbd.com</a>></span> wrote:
<br />>
<blockquote style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">Hello Everyone,
<br />>
<br />>
I have a question to the bdNOG community. I believe someone knows the
answer.
<br />>
<br />>
Question is "How does Google select their Cache Engine IP nearest to the
request sender?"
<br />>
<br />>
No doubt, they look at BGP tables for ASN of request sender but I want to know
more specifics like,
<br />>
do they look at BGP attributes, if yes then what BGP attributes, any algorithm
other than BGP etc.
<br />>
Thanks in advance.
<br />>
<br />>
Regards,
<br />>
<br />>
ANIRUDDHA BARUA
<br />>
Email: <a href="mailto:aniruddha.barua@colbd.com">aniruddha.barua@colbd.com</a>,
<a href="mailto:cto@colbd.com">cto@colbd.com</a>
<br />>
<br />>
_______________________________________________
<br />>
nog mailing list
<br />>
<a href="mailto:nog@bdnog.org">nog@bdnog.org</a>
<br />>
<a target="_blank" href="http://mailman.bdnog.org/mailman/listinfo/nog">http://mailman.bdnog.org/mailman/listinfo/nog</a>
<br />>
</blockquote>
<br /><b>------- End of Original Message
-------</b>
<br />
</font>
</BODY>
</HTML>