[Sipping] RE: [Sip] Proposed work items for MIG

"Samir Srivastava" <samirsr@nortel.com> Tue, 26 September 2006 21:01 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GSK3w-0002bH-1E; Tue, 26 Sep 2006 17:01:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GSK3t-0002bB-UH for sipping@ietf.org; Tue, 26 Sep 2006 17:01:53 -0400
Received: from zrtps0kp.nortel.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSK3o-0004bO-Cl for sipping@ietf.org; Tue, 26 Sep 2006 17:01:53 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com [47.103.123.73]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id k8QL1Mh07893; Tue, 26 Sep 2006 17:01:23 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 26 Sep 2006 16:01:21 -0500
Message-ID: <62B9B0847CC47543B6B3B5E26BD268E60EB04647@zrc2hxm2.corp.nortel.com>
In-Reply-To: <28F05913385EAC43AF019413F674A017101B6E07@OCCLUST04EVS1.ugd.att.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Proposed work items for MIG
Thread-index: AcbOEqhoXRg/AvAoTTuhvqVw36sfDATmUpmg
From: Samir Srivastava <samirsr@nortel.com>
To: "Dolly, Martin C, ALABS" <mdolly@att.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d094b18a574860cb9e2fe5fedfbcc179
Cc: sipping@ietf.org
Subject: [Sipping] RE: [Sip] Proposed work items for MIG
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1604726472=="
Errors-To: sipping-bounces@ietf.org

Hi,

 

Why draft draft-niccolini-sipping-feedback-spit is moved to MIG ? SPIT
is applicable to VoIP. As per my understanding, MIG is for migrating
traditional telephony services to IP. Am I missing something?

 

If IETF wants to take this work, then I want this work to progress at
the higher priority. If bandwidth is the problem in SIPPING/SIP, then I
am okay.

 

Thx

Samir

 

 

________________________________

From: Dolly, Martin C, ALABS [mailto:mdolly@att.com] 
Sent: Friday, September 01, 2006 3:05 PM
To: session-bounces@sip-voip.org
Cc: SIP List; sipping@ietf.org
Subject: [Sip] Proposed work items for MIG

 

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

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