[bdNOG] How does Google select their Cache Engine IP nearest to the request sender?

Aniruddha Barua aniruddha.barua at colbd.com
Sat Feb 8 13:42:08 BDT 2014


Dear Simon bhai,

Thanks for your email.

I am only interested in the networking part of these CDNs, not the content caching & serving part.

As a Networking Professional, Enthusiast and a Member of bdNOG Community, I'd be happy to see any one or two (or if possible all) of them in bdNOG1, :-). But Google/YouTube one consumes(ISP Point of view)/saves(IIG Point of view) the lion's share of bandwidth as I have seen. Let's put the proposal before the Program Committee. If I remember correctly, Roman bhai had told me that there will be someone from Google in bdNOG1.

With thanks and best regards,

ANIRUDDHA BARUA 
Email: aniruddha.barua at colbd.com, cto at colbd.com

---------- Original Message -----------
From: "Simon Sohel Baroi / IIG-ITC / Sr.Manager / 01678618243 /" <simon.baroi at fiberathome.net> 
To: Muhammad Moinur Rahman <5u623l20 at gmail.com> 
Cc: Aniruddha Barua <aniruddha.barua at colbd.com>, "nog at bdnog.org" <nog at bdnog.org> 
Sent: Sat, 8 Feb 2014 12:42:56 +0600 
Subject: Re: [bdNOG] How does Google select their Cache Engine IP nearest to the request sender?

> Dear Barua da,
> 
> Lets do one thing. I can talk with Google/Akamai/Limelight, that if they have any good slides for their Cache working principle.
> 
> As we are having our 1st bdNOG Conference, may be they will be interested to give us a presentation ( conference/tutorial ) about how its working. There are some proprietary thing in the cache, which Google, Akamai, Limielight and all the CDN operators can tell or show us. But without that all the principles are same. I found google one is very interesting. 
> 
> Please let me know what do you thing. Should we include them in the bdNOG Conference ?
> 
> Let us know your thoughts.
> 
> - SIMON 
> 
> On Wed, Feb 5, 2014 at 4:24 PM, Muhammad Moinur Rahman <5u623l20 at gmail.com> wrote:
> 
> 
> Hi Aniruddha Da,
> 
> Yeap that's a problem. At first I planned to do it using NO_EXPORT. But the problem is we have to peer with the node using a different ASN rather than our own. So it doesn't work. However for your case with us ping me outside the list. I will send you my BGP communities. Which will help you a bit.
> 
> BR,
> Moin
> 
> On Tue, Feb 4, 2014 at 10:00 PM, Aniruddha Barua <aniruddha.barua at colbd.com> wrote:
> 
> Dear Moin bhai,
> 
> Thanks for your reply. I understand the NDA part. I don't want anyone to disclose anything.
> 
> 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? ;-)
> 
> Best regards to all,
> 
> ANIRUDDHA BARUA 
> Email: aniruddha.barua at colbd.com, cto at colbd.com 
> 
> ---------- Original Message -----------
> From: Muhammad Moinur Rahman <5u623l20 at gmail.com> 
> To: Aniruddha Barua <aniruddha.barua at colbd.com> 
> Cc: "nog at bdnog.org" <nog at bdnog.org> 
> Sent: Tue, 4 Feb 2014 18:32:03 +0600 
> Subject: Re: [bdNOG] How does Google select their Cache Engine IP nearest to the request sender? 
> 
> > Hi Aniruddha Da,
> > 
> > Due to NDA I cannot disclose much. But so far my work they emphasize on advertising the prefix of your resolver. 
> > 
> > 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.
> > 
> > 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,
> > Moin
> > 
> > On Tue, Feb 4, 2014 at 5:17 PM, Aniruddha Barua <aniruddha.barua at colbd.com> wrote:
> > Hello Everyone,
> > 
> > I have a question to the bdNOG community. I believe someone knows the answer.
> > 
> > Question is "How does Google select their Cache Engine IP nearest to the request sender?"
> > 
> > No doubt, they look at BGP tables for ASN of request sender but I want to know more specifics like,
> > do they look at BGP attributes, if yes then what BGP attributes, any algorithm other than BGP etc.
> > Thanks in advance.
> > 
> > Regards,
> > 
> > ANIRUDDHA BARUA
> > Email: aniruddha.barua at colbd.com, cto at colbd.com
> > 
> > _______________________________________________
> > nog mailing list
> > nog at bdnog.org
> > http://mailman.bdnog.org/mailman/listinfo/nog
> > 
> ------- End of Original Message -------
> 
> 
> _______________________________________________
> nog mailing list
> nog at bdnog.org
> http://mailman.bdnog.org/mailman/listinfo/nog
> 
> 
> 
> -- 
> Simon Sohel Baroi  |  Sr. Manager, Technology  |  PICO  |   ITC - IIG  |
> Cell : +880-1678-618243, +880-181-7022207  |  Desk : +880-9666776677 Ext-1031  |  
> Mail : simon.baroi at pico.net.bd  |  Skype : tx.fttx  |
> 
> 
> 
> Reduce. Reuse. Recycle. Respect. It's the little things that really can make a difference.
> 
------- End of Original Message -------
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bdnog.org/pipermail/nog/attachments/20140208/92c90fee/attachment-0001.html>


More information about the nog mailing list