Re: [Simple] Please Comment: proposed SIMPLE charter

Avshalom Houri <AVSHALOM@il.ibm.com> Sun, 13 August 2006 13:25 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GCFyK-0003uB-KS; Sun, 13 Aug 2006 09:25:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GCFyI-0003u6-P8 for simple@ietf.org; Sun, 13 Aug 2006 09:25:42 -0400
Received: from mtagate1.de.ibm.com ([195.212.29.150]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GCFyG-00042O-SH for simple@ietf.org; Sun, 13 Aug 2006 09:25:42 -0400
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate1.de.ibm.com (8.13.7/8.13.7) with ESMTP id k7DDPeFh101062 for <simple@ietf.org>; Sun, 13 Aug 2006 13:25:40 GMT
Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com [9.149.165.229]) by d12nrmr1607.megacenter.de.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id k7DDTQNN153242 for <simple@ietf.org>; Sun, 13 Aug 2006 15:29:26 +0200
Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k7DDPdVr017377 for <simple@ietf.org>; Sun, 13 Aug 2006 15:25:39 +0200
Received: from d12mc102.megacenter.de.ibm.com (d12mc102.megacenter.de.ibm.com [9.149.167.114]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k7DDPd7h017374; Sun, 13 Aug 2006 15:25:39 +0200
In-Reply-To: <CA94E8B7-ACCC-42D4-82D7-2A26DD291B30@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [Simple] Please Comment: proposed SIMPLE charter
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0 HF144 February 01, 2006
From: Avshalom Houri <AVSHALOM@il.ibm.com>
Message-ID: <OFD70A87BC.20DE7998-ONC22571C9.00497E89-C22571C9.0049BB2E@il.ibm.com>
Date: Sun, 13 Aug 2006 16:29:23 +0300
X-MIMETrack: Serialize by Router on D12MC102/12/M/IBM(Release 7.0.1HF269 | June 22, 2006) at 13/08/2006 16:29:25, Serialize complete at 13/08/2006 16:29:25
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 563af5038a5e1dade28c8affc0fff375
Cc: simple-ads@tools.ietf.org, simple-chairs@tools.ietf.org, simple@ietf.org
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/simple>
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>
Content-Type: multipart/mixed; boundary="===============1436419111=="
Errors-To: simple-bounces@ietf.org

Regarding:

Mar 2007                 Submission of a performance and scalability 
analysis of the 
SIMPLE presence mechanisms to the IESG for publication as Informational

Does it mean that we stop at that analysis or we try and create some 
optimizations
to solve issues that are found in the analysis?

I think that we will need to go behind analysis only.

--Avshalom




Robert Sparks <rjsparks@nostrum.com> 
10/08/2006 18:41

To
simple@ietf.org
cc
simple-ads@tools.ietf.org, simple-chairs@tools.ietf.org
Subject
[Simple] Please Comment: proposed SIMPLE charter






All -

Based on the feedback at and since IETF66, we've updated the proposed 
new charter
and milestones for the SIMPLE working group.

You'll find the result below (it's also at http://www.nostrum.com/ 
~rjsparks/charter.txt)

Please read this over and comment. If there is no objection or 
substantive comment
by the next two weeks (Aug 24), we'll ask Jon to start the process of 
making it official.

Thanks,

RjS

-------

Description of Working Group:

This working group focuses on the application of the Session Initiation
Protocol (SIP, RFC 3261) to the suite of services collectively known 
as instant
messaging and presence (IMP). The IETF has committed to producing an
interoperable standard for these services compliant to the 
requirements for IM
outlined in RFC 2779 (including the security and privacy requirements 
there)
and in the Common Presence and Instant Messaging (CPIM) specification,
developed within the IMPP working group. As the most common services 
for which
SIP is used share quite a bit in common with IMP, the adaptation of 
SIP to IMP
seems a natural choice given the widespread support for (and relative 
maturity
of) the SIP standard.

This group has completed the majority of its primary goals and will 
focus
on the remaining tasks documented here and concluding. Any proposed new
work should be socialized with the chairs and AD early to determine if
this WG is an appropriate venue.

The primary remaining work of this group will be to complete:

1. The MSRP proposed standard mechanism for transporting sessions of 
messages
    initiated using the SIP, compliant to the requirments of RFC 
2779, CPIM
    and BCP 41.

2. The XCAP framework for representing and carrying configuration and 
policy
    information in SIMPLE systems.

3. A mechanism for representing partial changes (patches) to XML 
documents
    and extensions to the SIMPLE publication and notification 
mechanisms to
    convey these partial changes.

4. An annotated overview of the SIMPLE protocol definition documents.

Any SIP extensions proposed in the course of this development will, 
after a
last call process, be transferred to the SIP WG for consideration as 
formal SIP
extensions.

The working group will work within the framework for presence and IM 
described
in RFC 2778. The extensions it defines must also be compliant with 
the SIP
processes for extensions. The group cannot modify baseline SIP 
behavior or
define a new version of SIP for IM and presence. If the group 
determines that
any capabilities requiring an extension to SIP are needed, the group 
will seek
to define such extensions within the SIP working group, and then use 
them here.

Goals and Milestones:
Done                             Submission of event package for presence 
to IESG for 
publication as Proposed Standard
Done                             Submission of watcher information drafts 
to IESG for 
publication as Proposed Standards
Done                             Submission of proposed event list 
mechanism to the SIP 
working group
Done                             Submission of requirements for event 
publishing to the IESG 
for publication as Proposed Standard
Done                             Submission of proposed mechanism for 
event publishing to the 
SIP working group
Done                             Submission of SIMPLE PIDF profile to IESG 
for publication as 
Proposed Standard
Done                             Submission of base XCAP draft to IESG for 
publication as 
Proposed Standard
Done                             Submission of indication of instant 
message preparation using 
SIP to IESG for publication as a Proposed Standard
Done                             Submission of XCAP usage for manipulation 
of presence 
document content
Done                             Submission of XCAP usage for setting 
presence authorization 
to IESG for publication as Proposed Standard
Done                             Submission of Filtering mechanisms to 
IESG for publication as 
a Proposed Standard
Done                             Submission of instant messaging session 
draft to IESG for 
publication as a Proposed Standard
Done                             Submission of instant messaging session 
relay drafts to IESG 
for publication as Proposed Standards
Done                             Submission of Partial Notification 
mechanism to IESG for 
publication as a Proposed Standard
Sep 2006                 Submission of an Instant Message Disposition 
Status 
Notification mechanism to the IESG for publication as a Proposed 
Standard
Dec 2006                 Submission of proposed mechanisms meeting the 
advanced 
messaging requirements to the IESG or appropriate working group
Dec 2006                 Submission of XCAP event package to IESG or 
appropriate 
working group targeting publication as Proposed Standard
Mar 2007                 Submission of a performance and scalability 
analysis of the 
SIMPLE presence mechanisms to the IESG for publication as Informational
Jun 2007                 Submission of SIMPLE protocol annotated overview 
draft to 
IESG for publication as Informational
Jul 2007                                 Conclusion of SIMPLE


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

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