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

Melinda Shore <mshore@cisco.com> Fri, 23 September 2005 21:56 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIvWz-0004Sq-Ia; Fri, 23 Sep 2005 17:56:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIvWx-0004Sl-P5 for ietf@megatron.ietf.org; Fri, 23 Sep 2005 17:56:31 -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 RAA17018 for <ietf@ietf.org>; Fri, 23 Sep 2005 17:56:29 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIvdS-0004ai-Vr for ietf@ietf.org; Fri, 23 Sep 2005 18:03:16 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 23 Sep 2005 17:56:22 -0400
X-IronPort-AV: i="3.97,141,1125892800"; d="scan'208"; a="71576394:sNHT31060156"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j8NLuHT8024516; Fri, 23 Sep 2005 17:56:20 -0400 (EDT)
Received: from xmb-rtp-205.amer.cisco.com ([64.102.31.59]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 23 Sep 2005 17:56:18 -0400
Received: from 10.21.97.17 ([10.21.97.17]) by xmb-rtp-205.amer.cisco.com ([64.102.31.59]) via Exchange Front-End Server email.cisco.com ([171.70.151.187]) with Microsoft Exchange Server HTTP-DAV ; Fri, 23 Sep 2005 21:56:17 +0000
User-Agent: Microsoft-Entourage/11.0.0.040405
Date: Fri, 23 Sep 2005 17:56:16 -0400
From: Melinda Shore <mshore@cisco.com>
To: dcrocker@bbiw.net
Message-ID: <BF59F240.C0B%mshore@cisco.com>
In-Reply-To: <433475BD.1040605@dcrocker.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 23 Sep 2005 21:56:18.0274 (UTC) FILETIME=[A0527C20:01C5C089]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Cc: 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
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

On 9/23/05 5:38 PM, "Dave Crocker" <dhc2@dcrocker.net> wrote:
> For the proposed area, that does not seem to explain the inclusion of  ENUM,
> instant messaging or presence.  (This area is going to take over xmpp, too?)

ENUM is ancillary to telephony and not really to much else.
But anyway, you'll note that I argued that "real-time" is
an unsuitable name because of what it actually means, not
that your definition of real-time was vernacular and we need
to focus on what's actually real-time.  I tend to prefer
naming it something around multimedia applications but as
long as whatever it is is reasonably descriptive and won't
lead to people thinking that it's a proper place to work
on things like storage device controllers, I'm good.

Melinda

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