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

Dave Crocker <dhc2@dcrocker.net> Fri, 23 September 2005 23:00 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIwWS-0002d6-Vu; Fri, 23 Sep 2005 19:00:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIwWR-0002cU-5i for ietf@megatron.ietf.org; Fri, 23 Sep 2005 19:00:03 -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 TAA20931 for <ietf@ietf.org>; Fri, 23 Sep 2005 19:00:00 -0400 (EDT)
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIwcw-0005vP-L3 for ietf@ietf.org; Fri, 23 Sep 2005 19:06:48 -0400
Received: from [192.168.0.3] (adsl-71-131-47-236.dsl.sntc01.pacbell.net [71.131.47.236]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id j8NN0Gac023704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Sep 2005 16:00:17 -0700
Message-ID: <433488D3.2000100@dcrocker.net>
Date: Fri, 23 Sep 2005 15:59:31 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 1.4 (Windows/20050908)
MIME-Version: 1.0
To: Melinda Shore <mshore@cisco.com>
References: <BF59F240.C0B%mshore@cisco.com>
In-Reply-To: <BF59F240.C0B%mshore@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Found to be clean
X-Songbird-From: dhc2@dcrocker.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
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: dcrocker@bbiw.net
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

Melinda, thanks for pursuing this.

 >  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.

well, what I was in fact trying to get at was the need for characterizing the 
technical work, unless this really is merely splitting off a piece of apps 
work according to an interest group.  If there are distinguishing technical 
characteristics to the work being done, then its nature needs to be clear.

So far, references have been made to time-sensitive and to signalling, yet it 
is not clear how this applies to the work that is being defined as seeding the 
area.  Since SIP is really a signalling protocol, yes, that part is clear. 
But where is the time-sensitive technology component to the work in the area?

And if it is "multi-media" then what does that really mean?  Note that email 
and the web are multi-media... big time.

d/
-- 

  Dave Crocker
  Brandenburg InternetWorking
  +1.408.246.8253
  dcrocker  a t ...
  WE'VE MOVED to:  www.bbiw.net

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