Re: [Simple] Internal WG Review: Recharter of SIP for Instant Messaging and Presence Leveraging Extensions (simple)

"Hisham Khartabil" <hisham.khartabil@gmail.com> Wed, 31 January 2007 01:43 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HC4VR-0000Cq-NL; Tue, 30 Jan 2007 20:43:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HC4VQ-0000Ck-FS for simple@ietf.org; Tue, 30 Jan 2007 20:43:24 -0500
Received: from ug-out-1314.google.com ([66.249.92.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HC4VP-0004Hx-T8 for simple@ietf.org; Tue, 30 Jan 2007 20:43:24 -0500
Received: by ug-out-1314.google.com with SMTP id 72so42553ugd for <simple@ietf.org>; Tue, 30 Jan 2007 17:43:23 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=op03hU/rvNWUs4EldgjYWV2Jygn5qMlwIZIes6LX88QFSsiY1aKpEFl2S4jeueW5InaUdXrFXfjcbxiYwjWvNOynfjYcQZWTekyEwxwgHmyH6j2o/Yx5OWl9WGQvWWP+y55XTIAQokC4LQOjXywxvX+bWZqazvVdwbjTajTReD8=
Received: by 10.82.111.8 with SMTP id j8mr41633buc.1170207802892; Tue, 30 Jan 2007 17:43:22 -0800 (PST)
Received: by 10.82.112.7 with HTTP; Tue, 30 Jan 2007 17:43:20 -0800 (PST)
Message-ID: <66cd252f0701301743ycc944cfhbee8817f21aa506b@mail.gmail.com>
Date: Wed, 31 Jan 2007 12:43:20 +1100
From: Hisham Khartabil <hisham.khartabil@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Subject: Re: [Simple] Internal WG Review: Recharter of SIP for Instant Messaging and Presence Leveraging Extensions (simple)
In-Reply-To: <B35D3E34-63D5-49B2-A739-27F04C35026A@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <E1HC0bx-0006P1-FG@ietf.org> <45BFC36C.4060304@cisco.com> <B35D3E34-63D5-49B2-A739-27F04C35026A@nostrum.com>
X-Spam-Score: 0.6 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5
Cc: Paul Kyzivat <pkyzivat@cisco.com>, 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

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