Re: [Sip] Proposed work items for MIG

Paul Kyzivat <pkyzivat@cisco.com> Tue, 05 September 2006 13:32 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GKb24-0003fB-Bs; Tue, 05 Sep 2006 09:32:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GKb23-0003f0-6B; Tue, 05 Sep 2006 09:32:03 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKb1u-0003a2-PR; Tue, 05 Sep 2006 09:32:03 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 05 Sep 2006 09:31:55 -0400
X-IronPort-AV: i="4.08,214,1154923200"; d="scan'208"; a="100664231:sNHT36037620"
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.20060308/8.12.11) with ESMTP id k85DVsLv004250; Tue, 5 Sep 2006 09:31:54 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k85DVsuI024524; Tue, 5 Sep 2006 09:31:54 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 5 Sep 2006 09:31:54 -0400
Received: from [161.44.79.176] ([161.44.79.176]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 5 Sep 2006 09:31:54 -0400
Message-ID: <44FD7C49.3070207@cisco.com>
Date: Tue, 05 Sep 2006 09:31:53 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: "Dolly, Martin C, ALABS" <mdolly@att.com>
Subject: Re: [Sip] Proposed work items for MIG
References: <28F05913385EAC43AF019413F674A017101B6E07@OCCLUST04EVS1.ugd.att.com>
In-Reply-To: <28F05913385EAC43AF019413F674A017101B6E07@OCCLUST04EVS1.ugd.att.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Sep 2006 13:31:54.0040 (UTC) FILETIME=[A6C61B80:01C6D0EF]
DKIM-Signature: a=rsa-sha1; q=dns; l=2930; t=1157463114; x=1158327114; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:Re=3A=20[Sip]=20Proposed=20work=20items=20for=20MIG |To:=22Dolly,=20Martin=20C,=20ALABS=22=20<mdolly@att.com>; X=v=3Dcisco.com=3B=20h=3DYxGkrqaby3pLqt4mM+Fms8IKKG4=3D; b=jiMxr9xO2Je0V5I0Len/7Dl6HxxcIY818JpoTXXOUT6mRr2nLH1ziX7hP+DsUmel5qGradVy 1Ltz7bTVD5J4qN59DSVSy/QU0yDB+TvPXBTLNPL8/Rmm/I/JCq5RG+Je;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: SIP List <Sip@ietf.org>, sipping@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

As always, there remains the issue of "what is a service?" that may lead 
to disagreements about what is in scope for this group. I'm glad to see 
the charter calls for identifying the list of services that are in 
scope. Of the drafts proposed below for handling by the group, many do 
fit my own gut feeling of "service".

One draft that doesn't is draft-hasebe-sipping-race-examples. I think 
that one is still deeply tied to the details of the protocol itself 
rather than particular services and needs to remain with sipping.

	Paul

Dolly, Martin C, ALABS wrote:
> Hello all,
>  
> 
> As was announced in Montreal, a group of us are proposing to hold a BOF 
> in San Diego for a new working group MIG (once again the charter can be 
> found at:  www.sip-voip.org/charter.html 
> <outbind://23/www.sip-voip.org/charter.html> and the associated mail 
> list at www.sip-voip.org <http://www.sip-voip.org>). 
> 
>  
> 
> Part of the intention of MIG (Service Migration) is to off load some of 
> the work from sip/sipping, and in our presentation in Montreal we did 
> identify a couple of drafts that could be moved to the new group.  To 
> help facilitate discussions, below is an expanded list of drafts that 
> could be handled by the new group.  This list of drafts includes other 
> SDO requirements, PSTN interoperability drafts and other drafts that 
> include such topics, such as enterprise migration, that may fit the MIG 
> charter:
> 
>  
> 
> draft-sinha-sip-block
> 
> draft-andreasen-sipping-rfc3603bis
> 
> draft-anil-sipping-bla
> 
> draft-camarillo-sipping-sbc-funcs
> 
> draft-fries-sipping-identity-enterprise-scenario
> 
> draft-froment-sipping-spit-authz-policies
> 
> draft-haluska-sipping-directory-assistance
> 
> draft-hasebe-sipping-race-examples
> 
> draft-jennings-sipping-pay
> 
> draft-dolly-sipping-atis-ptsc
> 
> draft-jesske-sipping-tispan-requirements
> 
> draft-dcsgroup-sipping-arch
> 
> draft-niccolini-sipping-feedback-spit
> 
> draft-poetzl-sipping-call-completion
> 
> draft-rocky-sipping-calling-party-category
> 
> draft-schubert-sipping-saml-cpc
> 
> draft-shacham-sipping-session-mobility
> 
> draft-worley-sipping-pickup
> 
> draft-zhang-sipping-overlap
> 
>  
> 
> If anyone has any comments or opinions on any of these items, or if 
> anyone feels that they may have a draft that fits the MIG charter, 
> please feel free to comment on the MIG list.
> 
>  
> 
> Cheers,
> 
>  
> 
> Martin
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip