Re: [RAM] The mapping problem: rendezvous points?

Marshall Eubanks <tme@multicasttech.com> Tue, 08 May 2007 20:42 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlWVu-00076v-Fc; Tue, 08 May 2007 16:42:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlWVt-00076d-5Y for ram@iab.org; Tue, 08 May 2007 16:42:25 -0400
Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlWVq-0002xD-UO for ram@iab.org; Tue, 08 May 2007 16:42:25 -0400
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 6580427; Tue, 08 May 2007 16:42:20 -0400
In-Reply-To: <9C228355-9425-4C66-A9A7-47498490E3B1@virtualized.org>
References: <8F47F550-6224-4AFF-8359-CBA98D3F2FAB@muada.com> <271CF87FD652F34DBF877CB0CB5D16FC054EA470@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com> <9C228355-9425-4C66-A9A7-47498490E3B1@virtualized.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <CF3684B9-ED4E-43CF-A347-30FEA9FC2642@multicasttech.com>
Content-Transfer-Encoding: 7bit
From: Marshall Eubanks <tme@multicasttech.com>
Subject: Re: [RAM] The mapping problem: rendezvous points?
Date: Tue, 08 May 2007 16:42:16 -0400
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: ram@iab.org
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

Dear David;

On May 8, 2007, at 4:16 PM, David Conrad wrote:

> Hi,
>
> On May 8, 2007, at 11:18 AM, Dave Thaler wrote:
>> I disagree with the word "everything".  The two high level choices  
>> are:
>>
>> PULL: work on-demand (which results in deterministic loss and hence
>> adversely affects applications) and cache the result for some time
>
> What applications are adversely affected by a delay in transmitting  
> the first packet?  How do such applications work in today's "best  
> effort" Internet?

If delays are as much as several seconds, that will start to bring  
serious complaints from webhosts,
but the needs of video are more stringent.

In IPTV / Internet Broadcasting / Video Conferencing, there is a  
desire to

- start / change channels & broadcasts in 100's of milliseconds and
- not lose basically any packets

and that is why much of this traffic now goes over L2VPNs or L3VPNs.  
FEC will help with the
second, not the first.

Regards
Marshall

>
> Thanks,
> -drc
>
>
>
>
> _______________________________________________
> RAM mailing list
> RAM@iab.org
> https://www1.ietf.org/mailman/listinfo/ram


_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram