[Sip] Proposed work items for MIG

"Dolly, Martin C, ALABS" <mdolly@att.com> Fri, 01 September 2006 22:05 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GJH8L-00028q-H1; Fri, 01 Sep 2006 18:05:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GJH8J-00028c-MI; Fri, 01 Sep 2006 18:05:03 -0400
Received: from mail146.messagelabs.com ([216.82.245.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GJH8D-0006nd-9l; Fri, 01 Sep 2006 18:05:03 -0400
X-VirusChecked: Checked
X-Env-Sender: mdolly@att.com
X-Msg-Ref: server-13.tower-146.messagelabs.com!1157148182!2746612!15
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 10921 invoked from network); 1 Sep 2006 22:04:56 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4) by server-13.tower-146.messagelabs.com with SMTP; 1 Sep 2006 22:04:56 -0000
Received: from OCCLUST04EVS1.ugd.att.com (135.38.164.13) by attrh3i.attrh.att.com (7.2.052) id 44F1C304000ED3AA; Fri, 1 Sep 2006 18:04:56 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 01 Sep 2006 17:04:55 -0500
Message-ID: <28F05913385EAC43AF019413F674A017101B6E07@OCCLUST04EVS1.ugd.att.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Proposed work items for MIG
Thread-Index: AcbOEqhoXRg/AvAoTTuhvqVw36sfDA==
From: "Dolly, Martin C, ALABS" <mdolly@att.com>
To: session-bounces@sip-voip.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 223e3c753032a50d5dc4443c921c3fcd
Cc: SIP List <Sip@ietf.org>, sipping@ietf.org
Subject: [Sip] Proposed work items for MIG
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>
Content-Type: multipart/mixed; boundary="===============1991474171=="
Errors-To: sip-bounces@ietf.org

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).  

 

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