Re: [Simple] Internal WG Review: Recharter of SIP for Instant Messaging and Presence Leveraging Extensions (simple)
Paul Kyzivat <pkyzivat@cisco.com> Wed, 31 January 2007 04:15 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HC6sT-0008RX-AW; Tue, 30 Jan 2007 23:15:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HC6sS-0008RS-4a for simple@ietf.org; Tue, 30 Jan 2007 23:15:20 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HC6sQ-0005Q5-LC for simple@ietf.org; Tue, 30 Jan 2007 23:15:20 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 30 Jan 2007 23:15:19 -0500
X-IronPort-AV: i="4.13,259,1167627600"; d="scan'208"; a="112804151:sNHT60988652"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l0V4FIKO004635; Tue, 30 Jan 2007 23:15:18 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l0V4FIOA015886; Tue, 30 Jan 2007 23:15:18 -0500 (EST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 30 Jan 2007 23:15:18 -0500
Received: from [10.86.243.83] ([10.86.243.83]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 30 Jan 2007 23:15:17 -0500
Message-ID: <45C017D4.2030709@cisco.com>
Date: Tue, 30 Jan 2007 23:15:16 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
Subject: Re: [Simple] Internal WG Review: Recharter of SIP for Instant Messaging and Presence Leveraging Extensions (simple)
References: <E1HC0bx-0006P1-FG@ietf.org> <45BFC36C.4060304@cisco.com> <B35D3E34-63D5-49B2-A739-27F04C35026A@nostrum.com> <66cd252f0701301743ycc944cfhbee8817f21aa506b@mail.gmail.com> <1E3C1F6F-1497-4C1E-9336-934665BD9F87@nostrum.com>
In-Reply-To: <1E3C1F6F-1497-4C1E-9336-934665BD9F87@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Jan 2007 04:15:17.0489 (UTC) FILETIME=[6A03D610:01C744EE]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8907; t=1170216918; x=1171080918; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[Simple]=20Internal=20WG=20Review=3A=20Recharter=20of =20SIP=20for=20Instant=20Messaging=0A=20and=20Presence=20Leveraging=20Exte nsions=20(simple) |Sender:=20 |To:=20Ben=20Campbell=20<ben@nostrum.com>; bh=9eN+OcxdyxBdOuJnktxN7DPlDmjPR+jrGIpiM6jFqXs=; b=XnhdRi4tBNsKvenpGd0ZuzfnCTVzaZXl/v9aUTRaPiQQCdUVeYAntKvL0T62Ts8hVV17vHVM Yqejspmmyrd8cm7Hbou6PGCnOp6SRUqMDs65QjSKl248sOceI6ufuX8R;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.5 (/)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
Cc: 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>
Errors-To: simple-bounces@ietf.org
Ben Campbell wrote: > No, the June milestone is fine with me. I just wanted to make sure we > didn't forget it. I did not originally make the connection, but it makes > sense on a re-read. I also don't care much whether there is an explicit milestone. I was just trying to understand if that is still on the table. Thanks, Paul > On Jan 30, 2007, at 7:43 PM, Hisham Khartabil wrote: > >> I believe this was to be put into the June milestone. But I guess Ben >> and Paul want to see it as one of the primary milestones listed. >> >> Regards, >> Hisham >> >> On 31/01/07, Ben Campbell <ben@nostrum.com> wrote: >>> I also remember that being brought up, and also don't remember the >>> outcome ;-) >>> >>> On Jan 30, 2007, at 4:15 PM, Paul Kyzivat wrote: >>> >>> > Wasn't there some talk of a need to specify how to choose between >>> > MESSAGE and MSRP, and/or to transition between them in support of a >>> > single conversation? >>> > >>> > E.g. send a MESSAGE because there may never be a conversation, but >>> > then INVITE with an MSRP session to continue the conversation. The >>> > need here would be for a way to tie these things together so it is >>> > clear that they are part of the same conversation. There are >>> > obviously issues with involving the same pair of UAs in both. >>> > >>> > I seem to recall this was discussed at some point, but I'm not sure >>> > and if so I don't remember the outcome. >>> > >>> > Paul >>> > >>> > IESG Secretary wrote: >>> >> 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 >>> >>> >>> _______________________________________________ >>> 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
- [Simple] Internal WG Review: Recharter of SIP for… IESG Secretary
- Re: [Simple] Internal WG Review: Recharter of SIP… Paul Kyzivat
- Re: [Simple] Internal WG Review: Recharter of SIP… Ben Campbell
- Re: [Simple] Internal WG Review: Recharter of SIP… Hisham Khartabil
- Re: [Simple] Internal WG Review: Recharter of SIP… Ben Campbell
- Re: [Simple] Internal WG Review: Recharter of SIP… Paul Kyzivat
- RE: [Simple] Internal WG Review: Recharter of SIP… Markus.Isomaki
- RE: [Simple] Internal WG Review: Recharter of SIP… Stafford, Matthew
- RE: [Simple] Internal WG Review: Recharter of SIP… Salvatore Loreto (JO/LMF)
- Re: [Simple] Internal WG Review: Recharter of SIP… Jonathan Rosenberg
- Re: [Simple] Internal WG Review: Recharter of SIP… Jonathan Rosenberg
- RE: [Simple] Internal WG Review: Recharter of SIP… Drage, Keith (Keith)