IETF Logo Mail Archive

RE: [Notifications] Statement of interest, and comments on scope

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 09 August 2007 07:23 UTC

Return-path: <notifications-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IJ2Mr-0001D0-Ud; Thu, 09 Aug 2007 03:23:37 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IJ2Mq-0001Cr-M9 for notifications-confirm+ok@megatron.ietf.org; Thu, 09 Aug 2007 03:23:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IJ2Mq-0001Ci-BE for notifications@ietf.org; Thu, 09 Aug 2007 03:23:36 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100] helo=co300216-co-outbound.avaya.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IJ2Mq-000375-0s for notifications@ietf.org; Thu, 09 Aug 2007 03:23:36 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-outbound.avaya.com with ESMTP; 09 Aug 2007 03:23:35 -0400
X-IronPort-AV: i="4.19,239,1183348800"; d="scan'208"; a="51630389:sNHT8022426"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Notifications] Statement of interest, and comments on scope
Date: Thu, 09 Aug 2007 09:22:54 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04309DA8@307622ANEX5.global.avaya.com>
In-Reply-To: <E933815BB76213A6E0205106@[10.1.110.5]>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Notifications] Statement of interest, and comments on scope
Thread-Index: AcfZ+Nm4ty6IrxpYRNe5JnWqrkmEfgAXGz8A
References: <46B853C5.1040807@ninebynine.org> <46B98D7F.6090403@it.su.se> <E933815BB76213A6E0205106@[10.1.110.5]>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Chris Newman <Chris.Newman@Sun.COM>, Leif Johansson <leifj@it.su.se>, Graham Klyne <GK@ninebynine.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: notifications@ietf.org
X-BeenThere: notifications@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Message Notifications interest group discussion list <notifications.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/notifications>
List-Post: <mailto:notifications@ietf.org>
List-Help: <mailto:notifications-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=subscribe>
Errors-To: notifications-bounces@ietf.org

Yes. 

We have been paying marginal attention from the perspective of the OPS
area, as long as the scope of the work that is discussed stays within
the realm of mail, as defined in the BOF scope. If we want to discuss
about a more general applicability that is covering real-time
applications and has operational implications beyond mail services, the
discussions need to happen in a different context and involve a broader
community. 

And yes, duplication of functionality already present in other areas is
a concern. 

Dan


 
 

> -----Original Message-----
> From: Chris Newman [mailto:Chris.Newman@Sun.COM] 
> Sent: Wednesday, August 08, 2007 11:15 PM
> To: Leif Johansson; Graham Klyne
> Cc: notifications@ietf.org
> Subject: Re: [Notifications] Statement of interest, and 
> comments on scope
> 
> Speaking as sponsoring area director, I would not support a 
> proposed charter that included work on functionality already 
> present in SIP and/or XMPP.  I suspect other area directors 
> would also have problems with such a charter.
> 
>                 - Chris Newman
> 


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

v2.23.0 | Report a Bug | By Email