IETF Logo Mail Archive

Re: Possible new Real-Time Applications and Infrastucture (RAI) Area

Scott Michel <scooter.phd@gmail.com> Sat, 24 September 2005 07:27 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EJ4Rt-0004hs-KB; Sat, 24 Sep 2005 03:27:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EJ4Rq-0004hk-DV for ietf@megatron.ietf.org; Sat, 24 Sep 2005 03:27:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22450 for <ietf@ietf.org>; Sat, 24 Sep 2005 03:27:48 -0400 (EDT)
Received: from zproxy.gmail.com ([64.233.162.202]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EJ4YQ-0007V4-Jz for ietf@ietf.org; Sat, 24 Sep 2005 03:34:39 -0400
Received: by zproxy.gmail.com with SMTP id l1so873711nzf for <ietf@ietf.org>; Sat, 24 Sep 2005 00:27:40 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=p2hiSD5rEgoyNXx4Y7IfsCa0998Gbf2o6SHvVIfWMnVOyn75ERMQbucQLpOEfrz5NcyzaPiQ+f7IRFqaxbDqopI42fgNzpOvoG4LnkQGpocKat/pWGhiPq57b4ooNT9lz8/bG3Z3nd5tQ5dyNwkLlj9VHCWVdGev7ewqUssvcZQ=
Received: by 10.36.75.8 with SMTP id x8mr583476nza; Sat, 24 Sep 2005 00:27:40 -0700 (PDT)
Received: by 10.36.56.19 with HTTP; Sat, 24 Sep 2005 00:27:40 -0700 (PDT)
Message-ID: <258cd3200509240027313565bd@mail.gmail.com>
Date: Sat, 24 Sep 2005 00:27:40 -0700
From: Scott Michel <scooter.phd@gmail.com>
To: Melinda Shore <mshore@cisco.com>
In-Reply-To: <BF581557.AA8%mshore@cisco.com>
MIME-Version: 1.0
References: <43323DAD.3050004@dcrocker.net> <BF581557.AA8%mshore@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: dcrocker@bbiw.net, IETF list <ietf@ietf.org>
Subject: Re: Possible new Real-Time Applications and Infrastucture (RAI) Area
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Scott Michel <scooter.phd@gmail.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1897072625=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On 9/22/05, Melinda Shore <mshore@cisco.com> wrote:
>
> On 9/22/05 1:14 AM, "Dave Crocker" <dhc2@dcrocker.net> wrote:
> > The term
> > "real-time" tends to mean sub-second, and often much faster than that.
>
> That seems to be the vernacular use, but strictly speaking "real-time"
> is about robust assurances of delivery within a constrained time period,
> whether that time period is millisecond or multi-minute. In other
> words, the focus is on the guarantees, not on really-really-fast.


Let me play Devil's Advocate for a second: What wasn't addressed by the
previous work done in RSVP and Diffserv that this new area has to be
urgently addressed? Are not packet schedulers enough?

Or are we going to watch a whole new infrastructure get developed that will
be now better than the previous work, with less complexity, and more hope of
being deployed outside of DoD programs? Because, frankly, that's the only
place I've seen an explicit need for advanced QoS techniques (besides VoIP,
and that gets to be really debatable too.)


-scooter

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email