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

Harald Alvestrand <harald@alvestrand.no> Thu, 08 March 2012 16:07 UTC

Return-Path: <harald@alvestrand.no>
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 3E38821F8724 for <payload@ietfa.amsl.com>; Thu, 8 Mar 2012 08:07:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.513
X-Spam-Level:
X-Spam-Status: No, score=-110.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 rwGfhV6SPIG7 for <payload@ietfa.amsl.com>; Thu, 8 Mar 2012 08:07:32 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 3C55621F870A for <payload@ietf.org>; Thu, 8 Mar 2012 08:07:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 7F95B39E27B; Thu, 8 Mar 2012 17:07:31 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QE0WJm80y534; Thu, 8 Mar 2012 17:07:31 +0100 (CET)
Received: from hta-dell.lul.corp.google.com (unknown [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 09FDD39E149; Thu, 8 Mar 2012 17:07:31 +0100 (CET)
Message-ID: <4F58D942.3060603@alvestrand.no>
Date: Thu, 08 Mar 2012 17:07:30 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.27) Gecko/20120216 Thunderbird/3.1.19
MIME-Version: 1.0
To: "Kevin P. Fleming" <kpfleming@digium.com>
References: <C15918F2FCDA0243A7C919DA7C4BE9940B549C@xmb-rcd-x01-p.cisco.com> <4F4F59B7.907@alvestrand.no> <4F4FA94D.4090508@digium.com>
In-Reply-To: <4F4FA94D.4090508@digium.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: payload@ietf.org
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, 08 Mar 2012 16:07:33 -0000

I've queried within Google, and we're going to resurrect the draft.
It'll be a while still until we manage to get the information about 32 
kHz sample rate added, sorry.

                 Harald

On 03/01/2012 05:52 PM, Kevin P. Fleming wrote:
> 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.
>