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

Scott W Brim <sbrim@cisco.com> Sat, 24 September 2005 20:42 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EJGqS-0007Xf-C3; Sat, 24 Sep 2005 16:42:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EJGqQ-0007WX-8h for ietf@megatron.ietf.org; Sat, 24 Sep 2005 16:42: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 QAA21947 for <ietf@ietf.org>; Sat, 24 Sep 2005 16:41:59 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EJGx7-00077E-DC for ietf@ietf.org; Sat, 24 Sep 2005 16:48:58 -0400
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 24 Sep 2005 13:41:45 -0700
X-IronPort-AV: i="3.97,143,1125903600"; d="scan'208"; a="214656330:sNHT30147828"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j8OKfeVv019749; Sat, 24 Sep 2005 13:41:43 -0700 (PDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 24 Sep 2005 16:41:41 -0400
Received: from cisco.com ([10.86.240.127]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 24 Sep 2005 16:41:40 -0400
Date: Sat, 24 Sep 2005 16:41:22 -0400
From: Scott W Brim <sbrim@cisco.com>
To: Pete Resnick <presnick@qualcomm.com>
Message-ID: <20050924204122.GA5660@sbrim-wxp01>
Mail-Followup-To: Scott W Brim <sbrim@cisco.com>, Pete Resnick <presnick@qualcomm.com>, IETF list <ietf@ietf.org>
References: <BF59F240.C0B%mshore@cisco.com> <433488D3.2000100@dcrocker.net> <p07000c00bf5b2b5ec486@[216.43.25.67]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <p07000c00bf5b2b5ec486@[216.43.25.67]>
User-Agent: Mutt/1.4.2.1i
X-OriginalArrivalTime: 24 Sep 2005 20:41:40.0845 (UTC) FILETIME=[5DFAC9D0:01C5C148]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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 Sat, Sep 24, 2005 11:15:51AM -0500, Pete Resnick allegedly wrote:
> On 9/23/05 at 3:59 PM -0700, Dave Crocker wrote:
> 
> >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?
> 
> Dave,
> 
> I'm not entirely clear here: Do you have a problem with Ted's 
> reformulation of this potential new area as the Signalling 
> Applications and Infrastructure Area? That is, does his description 
> concretely define the new area well enough?
> 
> (If SAI is reasonable, and I think it is, let's use that 
> reformulation and be done with it.)

Hi.  I'm just catching up but I think "signaling" is not an essential
discriminator of what we're talking about, and thus this name is in
fact unreasonable.  Some relationships are established or tailored
through signaling that have nothing to do with interactiveness or
delay tolerance (or SIP).  Some are established through "management".  

"Delay-sensitive interpersonal communications" seems to be an
excellent description of the scope.  "Instant" messaging should be
included.  TDM should not, and one-way multimedia should only be
ancillary, even if SIP-based.  

I'm not sure what the name should be but please, putting "signaling"
in the name is worse than "real-time".

swb

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