Re: [rtcweb] BTW where are we at with MTI codecs?
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sun, 23 September 2012 09:48 UTC
Return-Path: <dromasca@avaya.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8441F21F84CE for <rtcweb@ietfa.amsl.com>; Sun, 23 Sep 2012 02:48:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.857
X-Spam-Level:
X-Spam-Status: No, score=-102.857 tagged_above=-999 required=5 tests=[AWL=-0.259, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xbI3x7MpPzdj for <rtcweb@ietfa.amsl.com>; Sun, 23 Sep 2012 02:48:58 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id C116521F84C9 for <rtcweb@ietf.org>; Sun, 23 Sep 2012 02:48:57 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAPbZXlDGmAcF/2dsb2JhbABCA4JLu2KBCIIgAQEBAQMSChEDWQIBCA0EBAEBCwYMCwEGAUUJCAEBBAESCAEZh2MLm0CcGoscGoJrgkVgA4ghh2yCJ4RGhG6KIIJpgWE
X-IronPort-AV: E=Sophos; i="4.80,470,1344225600"; d="scan'208,217"; a="28207112"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 23 Sep 2012 05:42:33 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 Sep 2012 05:41:24 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD9970.A4408F51"
Date: Sun, 23 Sep 2012 11:48:52 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040812A573@307622ANEX5.global.avaya.com>
In-Reply-To: <004101cd98f7$37afbae0$a70f30a0$@us>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] BTW where are we at with MTI codecs?
Thread-Index: Ac2Y9zZzgDBH7SjBQ/eFTQIiU1hVugAeLhdA
References: <004101cd98f7$37afbae0$a70f30a0$@us>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Richard Shockey <richard@shockey.us>, rtcweb@ietf.org
Subject: Re: [rtcweb] BTW where are we at with MTI codecs?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Sep 2012 09:48:59 -0000
I believe that the answer to the question in the subject line was given in the message from the chairs at http://www.ietf.org/mail-archive/web/rtcweb/current/msg05267.html. So the question is rather - 'where we are with the non-MTI codecs?' (the SHOULD codecs)? The chairs wrote in the same message: Ø Based on the discussion to date, the chairs will run a consensus call on Ø whether the WG should recommend specific codecs which will not be Ø mandatory to implement (i.e. will the document contain SHOULDs as well Ø as MUSTs for codec implementation)". If the response to that consensus Ø call indicates consensus for non-mandatory to implement recommendations, Ø we will run consensus calls on those codecs to be included at that level. Ø I think that that consensus call was not run yet. Regards, Dan From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Richard Shockey Sent: Saturday, September 22, 2012 10:20 PM To: rtcweb@ietf.org Subject: [rtcweb] BTW where are we at with MTI codecs? I do want to make it clear that SHOULD's should be included. I really really believe 722 AMR WB needs to be included in order to properly interoperate with Public SIP Networks (the former PSTN) and soon to be deployed Voice over LTE. Richard Shockey Shockey Consulting Chairman of the Board of Directors SIP Forum PSTN Mobile: +1 703.593.2683 <mailto:richard(at)shockey.us> skype-linkedin-facebook: rshockey101 http//www.sipforum.org
- [rtcweb] BTW where are we at with MTI codecs? Richard Shockey
- Re: [rtcweb] BTW where are we at with MTI codecs? Romascanu, Dan (Dan)
- Re: [rtcweb] BTW where are we at with MTI codecs? Richard Shockey
- Re: [rtcweb] BTW where are we at with MTI codecs? Magnus Westerlund