RE: Possible new Real-Time Applications and Infrastucture (RAI) Area
sbrim@cisco.com Sun, 25 September 2005 11:01 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EJUFk-000075-NK; Sun, 25 Sep 2005 07:01:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EJUFi-000060-4x for ietf@megatron.ietf.org; Sun, 25 Sep 2005 07:01:02 -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 HAA04827 for <ietf@ietf.org>; Sun, 25 Sep 2005 07:00:59 -0400 (EDT)
From: sbrim@cisco.com
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EJUMW-0002Tb-Rb for ietf@ietf.org; Sun, 25 Sep 2005 07:08:06 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-2.cisco.com with ESMTP; 25 Sep 2005 04:00:52 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j8PB0n4V011067; Sun, 25 Sep 2005 04:00:49 -0700 (PDT)
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 25 Sep 2005 07:00:48 -0400
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: Sun, 25 Sep 2005 07:00:46 -0400
Message-ID: <CA8EB93B28BD0F4C88392699600BD655A81F13@xmb-rtp-211.amer.cisco.com>
Thread-Topic: Possible new Real-Time Applications and Infrastucture (RAI) Area
Thread-Index: AcXBwGHdK9ykXZXlRWm2qJiQlZGB3A==
To: Pete Resnick <presnick@qualcomm.com>
X-OriginalArrivalTime: 25 Sep 2005 11:00:48.0642 (UTC) FILETIME=[62DC6620:01C5C1C0]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: quoted-printable
Cc: 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 Saturday, September 24, 2005 17:02 PM, Pete Resnick allegedly wrote: > On 9/24/05 at 4:41 PM -0400, Scott W Brim wrote: > >> On Sat, Sep 24, 2005 11:15:51AM -0500, Pete Resnick allegedly wrote: >>> Signalling Applications and Infrastructure Area > > Actually, I screwed up: It's "Signalled Applications and > Infrastructure". > >> Some relationships are established or tailored through signaling >> that have nothing to do with interactiveness or delay tolerance (or >> SIP). > > True, but which "Signalled Applications" are you thinking of that > wouldn't fit into this area? Further, I can think of all sorts of > interactive and delay intolerant things that do not belong in this > area. *Signalled* applications (and the infrastructure to support > them) seems *exactly to describe the things that I want grouped > together. The problem I have is that just about every application is "signaled", in the sense that there is a control plane exchange to align state and establish paths and parameters before data is exchanged. HTTP includes both, but how about FTP, where the control port and data ports are distinct, and signaling is path-decoupled? Also consider Grids, in which there can be quite a significant setup phase during which signaling takes place. I now understand that "signaled" is just as important as "interactive" to you, so I won't suggest taking it out of the name, but "signaled" is not enough of a differentiator all by itself. I don't mind ambiguous names but I do get concerned about names that are confusing or misleading. swb _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- RE: Possible new Real-Time Applications and Infra… john.loughney
- Re: Possible new Real-Time Applications and Infra… Pekka Savola
- Re: Possible new Real-Time Applications and Infra… grenville armitage
- RE: Possible new Real-Time Applications and Infra… Yaakov Stein
- FW: Possible new Real-Time Applications and Infra… Markus.Isomaki
- TAWNNY! (Re: FW: Possible new Real-Time Applicati… Harald Tveit Alvestrand
- Re: TAWNNY! (Re: FW: Possible new Real-Time Appli… C Wegrzyn
- Re: TAWNNY! (Re: FW: Possible new Real-Time Appli… bill
- Re: TAWNNY! (Re: FW: Possible new Real-Time Appli… Bill Fenner
- RE: Possible new Real-Time Applications and Infra… Bill Sommerfeld
- Re: Possible new Real-Time Applications and Infra… Dave Crocker
- Re: Possible new Real-Time Applications and Infra… Dave Crocker
- Re: TAWNNY! (Re: FW: Possible new Real-Time Appli… Brian E Carpenter
- Re: Possible new Real-Time Applications and Infra… Melinda Shore
- Shifting sands [Re: Possible new Real-Time Applic… Brian E Carpenter
- RE: Possible new Real-Time Applications and Infra… Yaakov Stein
- Re: Possible new Real-Time Applications and Infra… Dave Crocker
- Re: Possible new Real-Time Applications and Infra… Melinda Shore
- Re: Possible new Real-Time Applications and Infra… Dave Crocker
- Re: Possible new Real-Time Applications and Infra… Scott Michel
- Re: Possible new Real-Time Applications and Infra… Pete Resnick
- Re: Possible new Real-Time Applications and Infra… Scott W Brim
- Re: Possible new Real-Time Applications and Infra… Pete Resnick
- RE: Possible new Real-Time Applications and Infra… Yaakov Stein
- RE: Possible new Real-Time Applications and Infra… sbrim
- Re: Possible new Real-Time Applications and Infra… Adam Roach
- Re: Possible new Real-Time Applications and Infra… Richard Shockey