IETF Logo Mail Archive

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

Leif Johansson <leifj@it.su.se> Wed, 08 August 2007 20:39 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 1IIsJf-0002UV-Px; Wed, 08 Aug 2007 16:39:39 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IIsJe-0002U5-3S for notifications-confirm+ok@megatron.ietf.org; Wed, 08 Aug 2007 16:39:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIsJc-0002Tq-Nn for notifications@ietf.org; Wed, 08 Aug 2007 16:39:37 -0400
Received: from smtp3.su.se ([130.237.93.228]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IIsJb-000247-9p for notifications@ietf.org; Wed, 08 Aug 2007 16:39:36 -0400
Received: from localhost (localhost [127.0.0.1]) by smtp3.su.se (Postfix) with ESMTP id 5A58C3BF51; Wed, 8 Aug 2007 22:39:34 +0200 (CEST)
Received: from smtp3.su.se ([127.0.0.1]) by localhost (smtp3.su.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 18430-01-59; Wed, 8 Aug 2007 22:39:34 +0200 (CEST)
Received: from [10.0.0.11] (ua-83-227-179-169.cust.bredbandsbolaget.se [83.227.179.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.su.se (Postfix) with ESMTP id ED7123BE22; Wed, 8 Aug 2007 22:39:33 +0200 (CEST)
Message-ID: <46BA2A19.5090606@it.su.se>
Date: Wed, 08 Aug 2007 22:39:53 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Chris Newman <Chris.Newman@Sun.COM>
Subject: Re: [Notifications] Statement of interest, and comments on scope
References: <46B853C5.1040807@ninebynine.org> <46B98D7F.6090403@it.su.se> <E933815BB76213A6E0205106@[10.1.110.5]>
In-Reply-To: <E933815BB76213A6E0205106@[10.1.110.5]>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at smtp.su.se
X-Spam-Status: No, hits=-2.286 tagged_above=-99 required=7 tests=[AWL=0.026, BAYES_00=-2.312]
X-Spam-Level:
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: Graham Klyne <GK@ninebynine.org>, 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

Chris Newman wrote:
> 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
>
>
I'm not surprised nor do I disagree. Would you support a charter
which explicitly specifies profiling existing implementation(s) of
(say) a publish subscribe metaphor?

If so you'd have to address the issue of the email client growing
a sip stack (or an xmpp stack).

    Cheers Leif


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

v2.23.0 | Report a Bug | By Email