IETF Logo Mail Archive

[siprec] Proposal for follow-on siprec work

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 16 May 2013 19:55 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB13811E80AE for <siprec@ietfa.amsl.com>; Thu, 16 May 2013 12:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.275
X-Spam-Level:
X-Spam-Status: No, score=-0.275 tagged_above=-999 required=5 tests=[AWL=0.163, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KjGMqtdaKAqX for <siprec@ietfa.amsl.com>; Thu, 16 May 2013 12:55:50 -0700 (PDT)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:96]) by ietfa.amsl.com (Postfix) with ESMTP id DD7E611E80A5 for <siprec@ietf.org>; Thu, 16 May 2013 12:55:49 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta09.westchester.pa.mail.comcast.net with comcast id cffu1l0071ei1Bg59jvoVB; Thu, 16 May 2013 19:55:48 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta24.westchester.pa.mail.comcast.net with comcast id cjvo1l0053ZTu2S3kjvouf; Thu, 16 May 2013 19:55:48 +0000
Message-ID: <519539C2.4010005@alum.mit.edu>
Date: Thu, 16 May 2013 15:55:46 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "siprec@ietf.org" <siprec@ietf.org>
References: <20130516194128.15788.68159.idtracker@ietfa.amsl.com>
In-Reply-To: <20130516194128.15788.68159.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20130516194128.15788.68159.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1368734148; bh=Jt0MvmyYsNyBy/7rj05dlVel2ByHvVKSCCCp9GY4OEo=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=DacfY8f9Z3ts+RO0N9ffpzG4FlKGp87GEV/qKbDTDGYQOCMsxrzsfhkZ0LdK9lI2T e94kFrGUMJ8sqJwevpnBbPXGr8TK6g2OovD+Di0kPdvl79ztsGaxwIRs4HMHMN2Yte NXMh5IyKiAP8OcHgfkU6Wf/iUjYa9g+MefQ2h7tSTNoh+NOV29noA3Uo0nkgpo6VZ0 kTQnFvyjHhahN18ThNWQDJ+WkGdNmIAgFti1pw8ii/3Hs0b6SKTL7uc22hQdvsRF5V qcwbKpVInzWTtSEVIU+ZGOQK1ntjemUArKsEWzOndvt6se0jPfTngFFC6VU25Zt0Y8 vUaKhaBPSezqA==
Subject: [siprec] Proposal for follow-on siprec work
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 19:55:54 -0000

siprec'ers:

I hope I'm not getting ahead of myself, but I *think* we are almost done 
with the current round of siprec work. While we need to finish it, I 
also think we need to be thinking about "what next".

Michael Yan and I have just posted a new draft proposing some new siprec 
functionality that we would like to see. We are looking to assess the 
interest in this.

The draft is intentionally somewhat vague, reflecting its preliminary 
status. We want to refine it based on interest from the community. I can 
imagine refining it in two ways:

- deepening it with more detail about the functionality mentioned
- broadening it with additional functionality that others feel is
   currently lacking from siprec.

I'm posting this message to siprec, where I know there is a built-in 
community of interest. But IIUC the actual process for adopting new work 
of this sort will be to go back through dispatch. So I'll probably also 
be posting a similar message to the dispatch mailing list.

Please, we want to hear from you!

	Thanks,
	Paul


-------- Original Message --------
Subject: New Version Notification for 
draft-kyzivat-siprec-webconf-use-case-00.txt
Date: Thu, 16 May 2013 12:41:28 -0700
From: internet-drafts@ietf.org
To: Paul H. Kyzivat <pkyzivat@alum.mit.edu>,        Michael Yan 
<michael.yan@huawei.com>,        Paul Kyzivat <pkyzivat@alum.mit.edu>


A new version of I-D, draft-kyzivat-siprec-webconf-use-case-00.txt
has been successfully submitted by Paul H. Kyzivat and posted to the
IETF repository.

Filename:	 draft-kyzivat-siprec-webconf-use-case
Revision:	 00
Title:		 Web Conference Recording Use Case
Creation date:	 2013-05-16
Group:		 Individual Submission
Number of pages: 6
URL: 
http://www.ietf.org/internet-drafts/draft-kyzivat-siprec-webconf-use-case-00.txt
Status: 
http://datatracker.ietf.org/doc/draft-kyzivat-siprec-webconf-use-case
Htmlized: 
http://tools.ietf.org/html/draft-kyzivat-siprec-webconf-use-case-00


Abstract:
    The current work of SIPREC will soon finish.  As its charter defined,
    SIPREC has covered industries like financial trading floors, contact
    center and emergency service bureaus.  But when talking about
    products or solutions like data or web conferencing, SIPREC is
    insufficient to record all aspects of calls with different
    interactive media channels.  This draft tries to show a use case for
    web conference recording and show how it can work well under SIPREC
    mechanism.


 



The IETF Secretariat

v2.23.0 | Report a Bug | By Email