RE: [Simple] (Performance) Internal WG Review: Recharter of SIP forInstant Messaging and Presence Leveraging Extensions (simple)

"Drage, Keith \(Keith\)" <drage@alcatel-lucent.com> Wed, 31 January 2007 14:36 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCGZD-0000IK-VH; Wed, 31 Jan 2007 09:36:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCGZD-0000IE-DP for simple@ietf.org; Wed, 31 Jan 2007 09:36:07 -0500
Received: from ihemail1.lucent.com ([135.245.0.33]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCGZA-0002JG-Hl for simple@ietf.org; Wed, 31 Jan 2007 09:36:07 -0500
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l0VEZqHt015486; Wed, 31 Jan 2007 08:35:59 -0600 (CST)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 31 Jan 2007 08:35:50 -0600
Received: from DEEXC1U01.de.lucent.com ([135.248.187.28]) by DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 31 Jan 2007 15:35:47 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Simple] (Performance) Internal WG Review: Recharter of SIP forInstant Messaging and Presence Leveraging Extensions (simple)
Date: Wed, 31 Jan 2007 15:35:48 +0100
Message-ID: <5D1A7985295922448D5550C94DE29180BD3CA0@DEEXC1U01.de.lucent.com>
In-Reply-To: <OF14F26051.D73E07FC-ONC2257274.004D6F48-C2257274.004D851B@il.ibm.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Simple] (Performance) Internal WG Review: Recharter of SIP forInstant Messaging and Presence Leveraging Extensions (simple)
Thread-Index: AcdFQ8WDajjkp0QFS9qZ2WW3g+LxtgAAEjWQ
References: <OF14F26051.D73E07FC-ONC2257274.004D6F48-C2257274.004D851B@il.ibm.com>
From: "Drage, Keith (Keith)" <drage@alcatel-lucent.com>
To: Avshalom Houri <AVSHALOM@il.ibm.com>, simple@ietf.org
X-OriginalArrivalTime: 31 Jan 2007 14:35:47.0504 (UTC) FILETIME=[18D54B00:01C74545]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 0d6b5666eba887052ef5e87a9de0d3b8
Cc:
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="===============1659745722=="
Errors-To: simple-bounces@ietf.org

If it updates RFC 3265 then the SIP WG needs to do it. There is a well
understood mechanism of providing requirements to the SIP WG to do this.
 
If it is an extension (i.e. extending RFC 3265 rather than updating it
with corrections), then RFC 3427 applies. In general this also means
that the SIP WG will do it, but if for example it is just a
uri-parameter or some such, then other groups could well do it. Again
there is a well understood mechanism of providing requirements to the
SIP WG to do this.
 
 
 
Keith


________________________________

	From: Avshalom Houri [mailto:AVSHALOM@il.ibm.com] 
	Sent: 31 January 2007 14:05
	To: simple@ietf.org
	Subject: Re: [Simple] (Performance) Internal WG Review:
Recharter of SIP forInstant Messaging and Presence Leveraging Extensions
(simple)
	
	

	Regarding: 
	
	Mar 2007 Submission of a performance and scalability analysis of
the
	SIMPLE presence mechanisms to the IESG for publication as
Informational 
	
	Assuming that we will find things that need to be improved in
e.g. 3265 
	what will be the mechanism for the improvements? Via SIP WG? 
	
	--Avshalom
	
	
	
	
IESG Secretary <iesg-secretary@ietf.org> 

30/01/2007 23:33 

To
iesg@ietf.org, iab@iab.org, simple@ietf.org, Robert Sparks
<RjS@estacado.net>, Hisham Khartabil <hisham.khartabil@gmail.com> 
cc
Subject
[Simple] Internal WG Review: Recharter of SIP for Instant Messaging and
Presence Leveraging Extensions (simple)

	




	A new charter for the SIP for Instant Messaging and Presence
Leveraging
	Extensions (simple) working group in the Real-time Applications
and
	Infrastructure Area of the IETF is being considered. The draft
charter 
	is provided below for your review and comment.
	
	Review time is one week.
	
	The IETF Secretariat
	
	+++
	
	SIP for Instant Messaging and Presence Leveraging Extensions
(simple)
	
======================================================================
	
	Last Modified: 2007-1-24
	
	Current Status: Active Working Group
	
	Chair(s):
	Robert Sparks <RjS@estacado.net>
	Hisham Khartabil <hisham.khartabil@gmail.com>
	
	
	Real-time Applications and Infrastructure Area Director(s):
	Jon Peterson <jon.peterson@neustar.biz>
	Cullen Jennings <fluffy@cisco.com>
	
	Real-time Applications and Infrastructure Area Advisor:
	Jon Peterson <jon.peterson@neustar.biz>
	
	Technical Advisor(s):
	Jon Peterson <jon.peterson@neustar.biz>
	
	Mailing Lists:
	General Discussion: simple@ietf.org
	To Subscribe: simple-request@ietf.org
	In Body: subscribe
	Archive: http://www.ietf.org/mail-archive/web/simple/index.html
	
	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. A mechanism for initiating and managing Instant Message group
chat.
	
	5. 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.
	
	Any mechanisms created for managing Instant Message group chat
are
	intended to provide a bridge to the conferencing protocols that
will 
	be defined in XCON. They will be limited in scope to address
only 
	simple Instant Message chat with nicknames and will not attempt
	to address complex conferencing concepts such as sidebars. Their

	design must anticipate operating in conjunction with the
conferencing 
	protocols XCON is working towards.
	
	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
	Feb 2007 Submission of an Instant Message Disposition
Notification
	mechanism to the IESG for publication as a Proposed Standard
	Feb 2007 Submission of XCAP event package to IESG or appropriate
working group targeting publication as Proposed Standard
	Feb 2007 Submission of proposed mechanisms meeting the advanced
messaging requirements to the IESG or appropriate working group
	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
	Aug 2007 Submission of proposed mechanisms for initiating and
managing
	Instant Message group chat to the IESG for publication as
Proposed
	Standard
	Aug 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