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

"Yaakov Stein" <yaakov_s@rad.com> Thu, 22 September 2005 15:04 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EISd2-0000bJ-Oq; Thu, 22 Sep 2005 11:04:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIScz-0000a0-U8 for ietf@megatron.ietf.org; Thu, 22 Sep 2005 11:04: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 LAA05624 for <ietf@ietf.org>; Thu, 22 Sep 2005 11:04:45 -0400 (EDT)
Received: from radmail1.rad.co.il ([62.0.23.193] helo=antivir1.rad.co.il) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EISjB-0003Uq-MK for ietf@ietf.org; Thu, 22 Sep 2005 11:11:15 -0400
Received: from antivir1.rad.co.il (localhost [127.0.0.1]) by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j8MF1hYL006286 for <ietf@ietf.org>; Thu, 22 Sep 2005 18:01:43 +0300 (IDT)
Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112]) by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id j8MF1hLx006283; Thu, 22 Sep 2005 18:01:43 +0300 (IDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 22 Sep 2005 18:06:12 +0200
Message-ID: <27A0F290348F8E45AEF79889DDE65A5205555251@exrad2.ad.rad.co.il>
Thread-Topic: Possible new Real-Time Applications and Infrastucture (RAI) Area
Thread-Index: AcW/jDmGaIh88Wy0QqW/1y6aVBthyAAAnTjg
From: Yaakov Stein <yaakov_s@rad.com>
To: IETF list <ietf@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: quoted-printable
Cc:
Subject: RE: Possible new Real-Time Applications and Infrastucture (RAI) Area
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

 
> 	Hmmmm.  Someone told me once that real-time means on a 
> time scale such that no measurable time elapses between event 
> occurrences and their recognition. 

There are technically 2 different types of real-time.

Hard real-time means that all processing required is always performed
before the next buffer arrives.  Soft (or statistical) real-time
means that on the average processing finishes before the
next buffer arrives, but additional memory will be needed
to ensure that data is not lost.

So there is no absolute cap on the time-scale for RT delays,
it depends on the rate of the data being processed.

<snip>
> 	Admittedly, in a networking context, real time is being 
> measured over shorter and shorter time intervals. But the 
> Area being proposed is not really about networking, is it?

I hope it is. As I mentioned in my first email on this subject.
separation of the processing from the networking
results in suboptimality of the combination.

Y(J)S


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