Re: [codec] requirements #29 (closed): Packet loss concealment?

"codec issue tracker" <trac@tools.ietf.org> Mon, 24 January 2011 23:34 UTC

Return-Path: <trac@tools.ietf.org>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D1CE3A69B5 for <codec@core3.amsl.com>; Mon, 24 Jan 2011 15:34:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level:
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OiRt4SrcteIC for <codec@core3.amsl.com>; Mon, 24 Jan 2011 15:34:20 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 55A473A6995 for <codec@ietf.org>; Mon, 24 Jan 2011 15:34:20 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1PhVyG-0005sX-0r; Mon, 24 Jan 2011 15:37:16 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: codec issue tracker <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: gmaxwell@juniper.net, hoene@uni-tuebingen.de
X-Trac-Project: codec
Date: Mon, 24 Jan 2011 23:37:15 -0000
X-URL: http://tools.ietf.org/codec/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/codec/trac/ticket/29#comment:2
Message-ID: <071.6802305aa0f40534e45c23f0a36082f0@tools.ietf.org>
References: <062.7815381850dc9f0a504d2c451298e6bb@tools.ietf.org>
X-Trac-Ticket-ID: 29
In-Reply-To: <062.7815381850dc9f0a504d2c451298e6bb@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: gmaxwell@juniper.net, hoene@uni-tuebingen.de, codec@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: codec@ietf.org
Subject: Re: [codec] requirements #29 (closed): Packet loss concealment?
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: codec@ietf.org
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2011 23:34:21 -0000

#29: Packet loss concealment?

Changes (by gmaxwell@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 This is addressed in the guidelines:

 http://tools.ietf.org/html/draft-valin-codec-guidelines-08
 4.5: "To ensure freedom of implementation, decoder-side only error
 concealment does not need to be specified, although the reference
 implementation should include the same PLC algorithm as used in the
 testing phase.  Is it up to the working group to decide whether minimum
 requirements on PLC quality will be required for compliance with the
 specification.  Obviously, any information signaled in the bitstream
 intended to aid PLC needs to be specified."

 I don't believe the working group has expressed interest in PLC
 performance, and I know that there is at least some opposition to
 requiring specific that implementers provide a particular PLC or PLC
 performance (e.g. I'd be opposed to requiring a particular kind of PLC).
 As such, Jean-Marc is adding the following parallel language to section 3
 of the requirements document:

 "To ensure freedom of implementation, decoder-side only error concealment
 does not need to be specified, although a functional PLC algorithm is
 desirable as part of the codec reference implementation.  Obviously,
 any information signaled in the bitstream intended to aid PLC needs to be
 specified."
 (Available at http://jmvalin.ca/misc_stuff/draft-ietf-codec-
 requirements.txt)

-- 
------------------------------------+---------------------------------------
 Reporter:  hoene@…                 |        Owner:        
     Type:  defect                  |       Status:  closed
 Priority:  major                   |    Milestone:        
Component:  requirements            |      Version:        
 Severity:  -                       |   Resolution:  fixed 
 Keywords:                          |  
------------------------------------+---------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/codec/trac/ticket/29#comment:2>
codec <http://tools.ietf.org/codec/>