Re: [payload] Interest in raft-ietf-avt-rtp-isac

"Kevin P. Fleming" <kpfleming@digium.com> Thu, 01 March 2012 16:54 UTC

Return-Path: <kpfleming@digium.com>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04E6721E830D for <payload@ietfa.amsl.com>; Thu, 1 Mar 2012 08:54:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.546
X-Spam-Level:
X-Spam-Status: No, score=-106.546 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 2Vlv5SQGv5SD for <payload@ietfa.amsl.com>; Thu, 1 Mar 2012 08:54:45 -0800 (PST)
Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by ietfa.amsl.com (Postfix) with ESMTP id B422721E82C2 for <payload@ietf.org>; Thu, 1 Mar 2012 08:52:31 -0800 (PST)
Received: from [10.24.55.203] (helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from <kpfleming@digium.com>) id 1S39F0-0006yh-I6 for payload@ietf.org; Thu, 01 Mar 2012 10:52:30 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id 85FE6D8007 for <payload@ietf.org>; Thu, 1 Mar 2012 10:52:30 -0600 (CST)
Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Es2NUslpSZRG for <payload@ietf.org>; Thu, 1 Mar 2012 10:52:30 -0600 (CST)
Received: from [10.24.250.46] (unknown [10.24.250.46]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id 060E8D8005 for <payload@ietf.org>; Thu, 1 Mar 2012 10:52:29 -0600 (CST)
Message-ID: <4F4FA94D.4090508@digium.com>
Date: Thu, 01 Mar 2012 10:52:29 -0600
From: "Kevin P. Fleming" <kpfleming@digium.com>
Organization: Digium, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: payload@ietf.org
References: <C15918F2FCDA0243A7C919DA7C4BE9940B549C@xmb-rcd-x01-p.cisco.com> <4F4F59B7.907@alvestrand.no>
In-Reply-To: <4F4F59B7.907@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [payload] Interest in raft-ietf-avt-rtp-isac
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/payload>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 16:54:47 -0000

On 03/01/2012 05:12 AM, Harald Alvestrand wrote:
> On 02/27/2012 09:09 PM, Ali C. Begen (abegen) wrote:
>> WG,
>>
>> We have a milestone for this draft and we passed the target date some
>> time ago. AFAICT, the current draft has expired and there was no
>> continued work on this draft. I wonder whether the WG still has
>> interest in finishing this work. Please reply to this email (cc'ing
>> the payload list) if you have an interest/desire in seeing this
>> document finished.
>>
>> https://datatracker.ietf.org/doc/draft-ietf-avt-rtp-isac/
> I have checked with the relevant ex-Gips team (now Google), and it seems
> that we don't have any particular reason to make this a high priority at
> the moment. It's stable code.
>
> Do other participants see a benefit in having this spec published as an
> RFC?

At the request of a community member, I've just started working on 
adding support for iSAC passthrough in Asterisk, and while investigating 
it I learned that Chrome can currently generate/accept offers with iSAC 
at 32kHz sample rate, which is not included in this draft.

If Google is going to continue to distribute iSAC support in products 
(and others are as well), I'd be happy to see this draft updated to 
match the current state of deployments and get pushed towards publication.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming@digium.com | SIP: kpfleming@digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org