[94135] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Network end users to pull down 2 gigabytes a day, continuously?

daemon@ATHENA.MIT.EDU (Gian Constantine)
Wed Jan 10 09:28:09 2007

In-Reply-To: <Pine.LNX.4.64.0701101138050.29447@uplift.swm.pp.se>
Cc: nanog@merit.edu
From: Gian Constantine <constantinegi@corp.earthlink.net>
Date: Wed, 10 Jan 2007 09:01:42 -0500
To: Mikael Abrahamsson <swmike@swm.pp.se>
Errors-To: owner-nanog@merit.edu



--Apple-Mail-6--995541920
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Sounds a little like low buffering and sparse I-frames, but I'm no  
MPEG expert. :-)

Gian Anthony Constantine
Senior Network Design Engineer
Earthlink, Inc.

On Jan 10, 2007, at 5:42 AM, Mikael Abrahamsson wrote:

>
> On Tue, 9 Jan 2007, Valdis.Kletnieks@vt.edu wrote:
>
>> between handling 30K unicast streams, and 30K multicast streams  
>> that each have only one or at most 2-3 viewers?
>
> My opinion on the downside of video multicast is that if you want  
> it realtime your SLA figures on acceptable packet loss goes down  
> from fractions of a percent into the thousands of a percent, at  
> least with current implementations of video.
>
> Imagine internet multicast and having customers complain about bad  
> video quality and trying to chase down that last 1/100000 packet  
> loss that makes peoples video pixelate every 20-30 minutes, and the  
> video stream doesn't even originate in your network?
>
> For multicast video to be easier to implement we need more robust  
> video codecs that can handle jitter and packet loss that are  
> currently present in networks and handled acceptably by TCP for  
> unicast.
>
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se


--Apple-Mail-6--995541920
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Sounds a little like low =
buffering and sparse I-frames, but I'm no MPEG expert. :-)<DIV><BR><DIV> =
<SPAN class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; 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; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><SPAN =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; 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; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><DIV>Gian Anthony =
Constantine</DIV><DIV>Senior Network Design =
Engineer</DIV><DIV>Earthlink, =
Inc.</DIV></SPAN></SPAN></DIV><BR><DIV><DIV>On Jan 10, 2007, at 5:42 AM, =
Mikael Abrahamsson wrote:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">On Tue, =
9 Jan 2007, <A =
href=3D"mailto:Valdis.Kletnieks@vt.edu">Valdis.Kletnieks@vt.edu</A> =
wrote:</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV> =
<BLOCKQUOTE type=3D"cite"><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">between handling 30K =
unicast streams, and 30K multicast streams that each have only one or at =
most 2-3 viewers?</DIV> </BLOCKQUOTE><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">My opinion on the downside of =
video multicast is that if you want it realtime your SLA figures on =
acceptable packet loss goes down from fractions of a percent into the =
thousands of a percent, at least with current implementations of =
video.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Imagine internet multicast and having customers =
complain about bad video quality and trying to chase down that last =
1/100000 packet loss that makes peoples video pixelate every 20-30 =
minutes, and the video stream doesn't even originate in your =
network?</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">For multicast video to be easier to implement we =
need more robust video codecs that can handle jitter and packet loss =
that are currently present in networks and handled acceptably by TCP for =
unicast.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">--<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Mikael =
Abrahamsson<SPAN class=3D"Apple-converted-space">=A0 =A0 </SPAN>email: =
<A href=3D"mailto:swmike@swm.pp.se">swmike@swm.pp.se</A></DIV> =
</BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-6--995541920--

home help back first fref pref prev next nref lref last post