[98382] in North American Network Operators' Group
Re: Content Delivery Networks
daemon@ATHENA.MIT.EDU (Michal Krsek)
Tue Aug 7 04:19:29 2007
From: "Michal Krsek" <michal@krsek.cz>
To: "Rod Beck" <Rod.Beck@hiberniaatlantic.com>
Cc: <nanog@merit.edu>
Date: Tue, 7 Aug 2007 09:59:41 +0200
Errors-To: owner-nanog@merit.edu
This is a multi-part message in MIME format.
------=_NextPart_000_004D_01C7D8D9.AC6547D0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content Delivery NetworksRod,
I run a small CDN oriented to audio/video distribution in Central Europe =
region. You mentioned challenges that CDN are facing. There are several =
of these:
1) Geographic load distribution
- in example, you have to have enough capacity in each distribution area =
that is being potentionally served by your customers (media companies).
2) Computing power
- you have to have in each POP adequate computing power that allows you =
to use full bandwidth available in that POP
3) Network capacity in each POP
- self explaining
4) Content moving
- you have to optimise internal data flows between POPs
5) User redirection
- You have to implement a scalable mechanisms that redirects users to =
the closes POP. You can use application redirect (fast, but not so much =
scalable), DNS redirect (scalable, but not so fast) or anycasting (this =
needs cooperation with ISP).
6) Costs of the system
- Most CDNs are designed for peaking traffic, but load is more dynamic =
that in traditional networks.
7) Play alone
There is almost no way for handover traffic to other CDN. No standards, =
no kinf of interconnection agreement.
These points are only a rough overview, this ecosystem is developping =
and challenges also depend on the starting conditions and region where =
you are running you CDN.
Regards
Michal
----- Original Message -----=20
From: Rod Beck=20
To: Jason J. W. Williams ; Pekka Savola ; Robert Boyle=20
Cc: ALEJANDRO ESQUIVEL RODRIGUEZ ; nanog@merit.edu=20
Sent: Monday, August 06, 2007 23:10
Subject: Content Delivery Networks
Can anyone give a breakdown of the different kinds of content deliver =
networks? For example, we have Akamai, which appears to be a pure Layer =
3 network that is tailored to pushing relatively small files like web =
pages and we have Lime Light Networks, which is a mix of Layer 1 and =
Layer 3, that focuses on bigger files like video streams.
Any insights out there? And what are the major challenges in making =
scalable content delivery networks?
Roderick S. Beck
Director of EMEA Sales
Hibernia Atlantic
1, Passage du Chantier, 75012 Paris
http://www.hiberniaatlantic.com
Wireless: 1-212-444-8829.
Landline: 33-1-4346-3209
AOL Messenger: GlobalBandwidth
rod.beck@hiberniaatlantic.com
rodbeck@erols.com
``Unthinking respect for authority is the greatest enemy of truth.'' =
Albert Einstein.
------=_NextPart_000_004D_01C7D8D9.AC6547D0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Content Delivery Networks</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16481" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Rod,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I run a small CDN oriented =
to audio/video=20
distribution in Central Europe region. You mentioned challenges =
that CDN=20
are facing. There are several of these:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>1) Geographic load =
distribution</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- in example, you have to have enough =
capacity in=20
each distribution area that is being potentionally served by your =
customers=20
(media companies).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>2) Computing power</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- you have to have in each POP adequate =
computing=20
power that allows you to use full bandwidth available in that =
POP</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>3) Network capacity in each =
POP</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- self explaining</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>4) Content moving</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- you have to optimise internal data =
flows between=20
POPs</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>5) User redirection</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- You have to implement a scalable =
mechanisms that=20
redirects users to the closes POP. You can use application redirect =
(fast, but=20
not so much scalable), DNS redirect (scalable, but not so fast) or =
anycasting=20
(this needs cooperation with ISP).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>6) Costs of the system</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- Most CDNs are designed for peaking =
traffic, but=20
load is more dynamic that in traditional networks.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>7) Play alone</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>There is almost no way =
for handover traffic to=20
other CDN. No standards, no kinf of interconnection =
agreement.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>These points are only a rough overview, =
this=20
ecosystem is developping and challenges also depend on the starting =
conditions=20
and region where you are running you CDN.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> =20
Regards</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> =20
Michal</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3DRod.Beck@hiberniaatlantic.com=20
href=3D"mailto:Rod.Beck@hiberniaatlantic.com">Rod Beck</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dwilliamsjj@digitar.com=20
href=3D"mailto:williamsjj@digitar.com">Jason J. W. Williams</A> ; <A=20
title=3Dpekkas@netcore.fi href=3D"mailto:pekkas@netcore.fi">Pekka =
Savola</A> ; <A=20
title=3Drobert@tellurian.com =
href=3D"mailto:robert@tellurian.com">Robert Boyle</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A=20
title=3Dalejandro_esquivel@costarricense.cr=20
href=3D"mailto:alejandro_esquivel@costarricense.cr">ALEJANDRO ESQUIVEL =
RODRIGUEZ</A> ; <A title=3Dnanog@merit.edu=20
href=3D"mailto:nanog@merit.edu">nanog@merit.edu</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, August 06, 2007 =
23:10</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Content Delivery =
Networks</DIV>
<DIV><FONT face=3DArial size=3D2></FONT><BR></DIV><!-- Converted from =
text/plain format -->
<P><FONT size=3D2>Can anyone give a breakdown of the different kinds =
of content=20
deliver networks? For example, we have Akamai, which appears to be a =
pure=20
Layer 3 network that is tailored to pushing relatively small files =
like web=20
pages and we have Lime Light Networks, which is a mix of Layer 1 and =
Layer 3,=20
that focuses on bigger files like video streams.<BR><BR>Any insights =
out=20
there? And what are the major challenges in making scalable content =
delivery=20
networks?<BR><BR>Roderick S. Beck<BR>Director of EMEA =
Sales<BR>Hibernia=20
Atlantic<BR>1, Passage du Chantier, 75012 Paris<BR><A=20
=
href=3D"http://www.hiberniaatlantic.com">http://www.hiberniaatlantic.com<=
/A><BR>Wireless:=20
1-212-444-8829.<BR>Landline: 33-1-4346-3209<BR>AOL Messenger:=20
GlobalBandwidth<BR><A=20
=
href=3D"mailto:rod.beck@hiberniaatlantic.com">rod.beck@hiberniaatlantic.c=
om</A><BR>rodbeck@erols.com<BR>``Unthinking=20
respect for authority is the greatest enemy of truth.'' Albert=20
Einstein.<BR><BR><BR></FONT></P><FONT face=3DTahoma size=3D2><FONT =
color=3D#0000ff>
<P><FONT face=3DArial=20
color=3D#000000></FONT> </P></BLOCKQUOTE></FONT></FONT></BODY></HTML=
>
------=_NextPart_000_004D_01C7D8D9.AC6547D0--
