[codec] #16: Multicast?

"codec issue tracker" <trac@tools.ietf.org> Wed, 21 April 2010 09:42 UTC

Return-Path: <trac@tools.ietf.org>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id B48093A6827 for <codec@core3.amsl.com>; Wed, 21 Apr 2010 02:42:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id XFB+D1cZoBqj for <codec@core3.amsl.com>; Wed, 21 Apr 2010 02:42:41 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 0C1843A67AB for <codec@ietf.org>; Wed, 21 Apr 2010 02:42:37 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1O4WRw-0007uC-4M; Wed, 21 Apr 2010 02:42:28 -0700
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.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: hoene@uni-tuebingen.de
X-Trac-Project: codec
Date: Wed, 21 Apr 2010 09:42:28 -0000
X-URL: http://tools.ietf.org/codec/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/codec/trac/ticket/16
Message-ID: <062.7439ee5d5fd36480e73548f37cb10207@tools.ietf.org>
X-Trac-Ticket-ID: 16
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: 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: [codec] #16: Multicast?
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Wed, 21 Apr 2010 09:42:41 -0000

#16: Multicast?
 Reporter:  hoene@…                 |       Owner:     
     Type:  enhancement             |      Status:  new
 Priority:  trivial                 |   Milestone:     
Component:  requirements            |     Version:     
 Severity:  Active WG Document      |    Keywords:     
 The question arrose whether the interactive CODEC MUST support multicast
 in addition to teleconferencing.

 On 04/13/2010 11:35 AM, Christian Hoene wrote:
 >>> P.S. On the same note, does anybody here cares about using this
 >>> CODEC with multicast? Is there a single commercial multicast voice
 >>> From what I've seen all multicast does is making IETF voice
 >>> standards harder to understand or implement.
 >> I think that would be a mistake to ignore multicast - not because of
 >> multicast itself, but because of Xcast (RFC 5058) which is a
 >> promising technology to replace centralized conference bridges.
 > Regarding multicast:
 > I think we shall start at user requirements and scenarios.
 > Teleconference (including mono or spatial audio) might be good
 > starting point. Virtual environments like second live would require
 multicast communication, too. If the requirements of these scenarios are
 well understand, we can start to talk about potential solutions like IP
 multicast, Xcast or conference bridges.

Ticket URL: <http://trac.tools.ietf.org/wg/codec/trac/ticket/16>
codec <http://tools.ietf.org/codec/>