Re: [Simple] splitting of partial notify draft

Alex Audu <alex.audu@alcatel.com> Fri, 02 January 2004 22:26 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27060 for <simple-archive@ietf.org>; Fri, 2 Jan 2004 17:26:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AcXkM-0000lC-00 for simple-archive@ietf.org; Fri, 02 Jan 2004 17:26:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AcXic-0000ZN-00 for simple-archive@ietf.org; Fri, 02 Jan 2004 17:24:34 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AcXfa-0000JU-00; Fri, 02 Jan 2004 17:21:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcXfB-0000mw-Uc; Fri, 02 Jan 2004 17:21:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcXeL-0000mF-4W for simple@optimus.ietf.org; Fri, 02 Jan 2004 17:20:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26735 for <simple@ietf.org>; Fri, 2 Jan 2004 17:20:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AcXe8-0000Gh-00 for simple@ietf.org; Fri, 02 Jan 2004 17:19:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AcXa4-000084-00 for simple@ietf.org; Fri, 02 Jan 2004 17:15:44 -0500
Received: from auds952.usa.alcatel.com ([143.209.238.7]) by ietf-mx with esmtp (Exim 4.12) id 1AcXV4-0007fJ-00 for simple@ietf.org; Fri, 02 Jan 2004 17:10:34 -0500
Received: from alcatel.com (localhost [127.0.0.1]) by auds952.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id i02M9ZOf023660; Fri, 2 Jan 2004 16:09:35 -0600 (CST)
Message-ID: <3FF5EC1F.33E38A71@alcatel.com>
From: Alex Audu <alex.audu@alcatel.com>
Reply-To: alex.audu@alcatel.com
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mikko.lonnfors@nokia.com
CC: simple@ietf.org
Subject: Re: [Simple] splitting of partial notify draft
References: <0C1353ABB1DEB74DB067ADFF749C4EEF01D1727C@esebe004.ntc.nokia.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: simple-admin@ietf.org
Errors-To: simple-admin@ietf.org
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/mail-archive/working-groups/simple/>
Date: Fri, 02 Jan 2004 16:09:35 -0600
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Hi Mikko,

I guess re-usability would be a good-enough motivation to split the
dopcument.

Thanks,
Alex.


mikko.lonnfors@nokia.com wrote:

> Hi,
>
> Main motivation to slip the current document is to improve reusability
> of the MIME type ('application/pidf-partial+xml'). There are other
> places than presence event package where this content format may be
> used. If there wouldn't be any other usages for this then keeping
> document in its current form would make sense. But if somebody writes a
> new draft which utilized 'application/pidf-partial+xml' MIME type then
> it is much more convenient if there is a standalone definition for that.
>
> - Mikko
>
> -----Original Message-----
> From: ext Alex Audu [mailto:alex.audu@alcatel.com]
> Sent: Wednesday, December 24, 2003 12:00 AM
> To: Lonnfors Mikko (NRC/Helsinki)
> Cc: simple@ietf.org
> Subject: Re: [Simple] splitting of partial notify draft
>
> Hi,
> I think I like the document in its current form. Is there a technical or
> ligistic reason for
> splitting it? The current form is compact and keeping everything in one
> place aids
> readability.
> Cheers,
> Alex.
>
> mikko.lonnfors@nokia.com wrote:
> Hi folks,
> Current partial notify draft (draft-ietf-simple-partial-notify) contains
> new MIME type definition and specifies how SUBSCRIBE/NOTIFY in presence
> event package is used with that particular MIME type. One think which
> could be done is to slip the current draft into two. One part would
> contain MIME type definition and other would cover how that particular
> MIME type is used with presence event package. This way it would
> probably be much easier to reuse partial PIDF MIME type. Similar
> approach has been taken in winfo.
> So, I would like to know how people feel about this. Please vote for:
> 1)
> Split the document
> 2)
> Keep it as it is
> - Mikko


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