Re: [codec] #13: reference use-cases and topologies!
stephen botzko <stephen.botzko@gmail.com> Sat, 01 May 2010 10:06 UTC
Return-Path: <stephen.botzko@gmail.com>
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 47B543A6802 for <codec@core3.amsl.com>; Sat, 1 May 2010 03:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.049
X-Spam-Level:
X-Spam-Status: No, score=-1.049 tagged_above=-999 required=5 tests=[AWL=-0.540, BAYES_05=-1.11, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6]
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 IovpCyVIrCXl for <codec@core3.amsl.com>; Sat, 1 May 2010 03:05:58 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 00EC03A67D3 for <codec@ietf.org>; Sat, 1 May 2010 03:05:57 -0700 (PDT)
Received: by wyb35 with SMTP id 35so732760wyb.31 for <codec@ietf.org>; Sat, 01 May 2010 03:05:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=hkCISWz4xvzZcwHh60s+esrNXEbOwgwxwNm+87+uUwY=; b=OYYM5Qe6MP11+HTah8kyZtq9knlbbHBMnhX3R/XCqYaUhjXv/x+TIU4/7Ypvwj7uVL 1/gccZmbjatjU0LPeeZdvO9zRY4YHdBXPko+7Vw3WELepgyKY3Z8nHspGDBOR9uIpvAC X2dp7iu2DF5Z03rtMIdk4psE9oUhQGxWPuA1w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=siBzaM2QuJI6hdyjR/AkGGOLdpdcrSh95x35wUsptwj1+keh3OngmB+nC62RfeYdT6 4UPkkc7+ksadS55zwYxQ3CN3iTR/59S71otkBT4RpfxLMwh98LTMQbogrXA1BANM+os/ JWfr1Pv+Tb44PNIgsfT97eQz6oEYOHRSt6xzQ=
MIME-Version: 1.0
Received: by 10.216.90.4 with SMTP id d4mr3707264wef.135.1272708339978; Sat, 01 May 2010 03:05:39 -0700 (PDT)
Received: by 10.216.28.139 with HTTP; Sat, 1 May 2010 03:05:39 -0700 (PDT)
In-Reply-To: <071.791205ca9a47bcee1ebf5d2f98d94214@tools.ietf.org>
References: <062.407382d901e5e6b8dea15d6e3ae1a2c8@tools.ietf.org> <071.791205ca9a47bcee1ebf5d2f98d94214@tools.ietf.org>
Date: Sat, 01 May 2010 06:05:39 -0400
Message-ID: <o2g6e9223711005010305p27ac6f7agf7f5bfc3f83359df@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: codec@ietf.org
Content-Type: multipart/alternative; boundary="0016e6d6481581d17b04858580e8"
Subject: Re: [codec] #13: reference use-cases and topologies!
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: Sat, 01 May 2010 10:06:03 -0000
Surely centralized conferencing is an important use case. Stephen Botzko On Sat, May 1, 2010 at 5:47 AM, codec issue tracker <trac@tools.ietf.org>wrote: > #13: reference use-cases and topologies! > > ------------------------------------+--------------------------------------- > Reporter: hoene@… | Owner: > Type: defect | Status: new > Priority: critical | Milestone: > Component: requirements | Version: > Severity: Active WG Document | Keywords: > > ------------------------------------+--------------------------------------- > > Comment(by hoene@…): > > [Christian]: > At least use usages were mentioned previously: > a) removing the need for echo cancelation because of ultra-low delay, when > echoes are called side tones... > b) Push-to-talk > > With are the topologies under study? > a) IPend-to-IPend? > b) IPend-to-transcoding_gateway-to-PSTNend? > c) n to n (decentralized conferencing) > e) IPend-to-legal_interception-to-X > [Slava]: Henry, e2e (or p2p) is cool but what about Legal interception for > example in this case, which every cellco has to implemenet? > [Benjamin]: Whether or not we want to encourage it, interception of VoIP > traffic does not require a re-encode. The encoded packets can just be > copied to the additional receiver. > [Cullen]: RFC 2804 [legal interception is out of scope] > > -- > Ticket URL: <http://trac.tools.ietf.org/wg/codec/trac/ticket/13#comment:2> > codec <http://tools.ietf.org/codec/> > > _______________________________________________ > codec mailing list > codec@ietf.org > https://www.ietf.org/mailman/listinfo/codec >
- [codec] #13: reference use-cases and topologies! codec issue tracker
- Re: [codec] #13: reference use-cases and topologi… codec issue tracker
- Re: [codec] #13: reference use-cases and topologi… Christian Hoene
- Re: [codec] #13: reference use-cases and topologi… Colin Perkins
- Re: [codec] #13: reference use-cases and topologi… Peter Saint-Andre
- Re: [codec] #13: reference use-cases and topologi… Cullen Jennings
- Re: [codec] #13: reference use-cases and topologi… codec issue tracker
- Re: [codec] #13: reference use-cases and topologi… stephen botzko
- Re: [codec] #13: reference use-cases and topologi… codec issue tracker
- Re: [codec] requirements #13 (new): reference use… codec issue tracker
- Re: [codec] #13: reference use-cases and topologi… codec issue tracker