IETF Logo Mail Archive

Re: [rtcweb] Media negeotiation and signalling archatecture

Cullen Jennings <fluffy@cisco.com> Thu, 07 July 2011 04:11 UTC

Return-Path: <fluffy@cisco.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 8544A21F8552 for <rtcweb@ietfa.amsl.com>; Wed, 6 Jul 2011 21:11:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.51
X-Spam-Level:
X-Spam-Status: No, score=-105.51 tagged_above=-999 required=5 tests=[AWL=-2.911, BAYES_00=-2.599, 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 JBnrpyiHEOkT for <rtcweb@ietfa.amsl.com>; Wed, 6 Jul 2011 21:11:37 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id D7AB721F893C for <rtcweb@ietf.org>; Wed, 6 Jul 2011 21:11:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=457; q=dns/txt; s=iport; t=1310011898; x=1311221498; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=g24lgDbOFqrKmF2cg11xrIzhtG9ZVTU3ylyhQjiJXw4=; b=IsbrU1T3V5BtdDoPNG0FOD/pKN1DWdARdDVCVu+RxYJOiSoyXMuljIrY +FlVqNrgQdW6pCX2sOSPFLQS2OnWSqXdQVuv0AFHRzigIzp8gxRVxe6pt 0Q4XOExNdRntB0GtXVUnmyKhh8oFjO1mKAmHDC5OcDca7D6hk2e0BNKdp M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAIwxFU6rRDoH/2dsb2JhbABTqBd3iHulC519hjcEh0mKfYR9i2M
X-IronPort-AV: E=Sophos;i="4.65,491,1304294400"; d="scan'208";a="522175"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by rcdn-iport-8.cisco.com with ESMTP; 07 Jul 2011 04:11:37 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p674Baq2030140; Thu, 7 Jul 2011 04:11:36 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <CAHzHjDNPZ4MVmV_XGDN-jdVV2zjruVFqhih5BstefaWo33pCag@mail.gmail.com>
Date: Wed, 06 Jul 2011 22:11:35 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <2AE62384-D2B0-4630-A27A-C89AB7A5B826@cisco.com>
References: <B6D678DA-DB26-4A7C-AA0C-6DB580C1E835@cisco.com> <CAHzHjDNPZ4MVmV_XGDN-jdVV2zjruVFqhih5BstefaWo33pCag@mail.gmail.com>
To: Niklas Enbom <niklase@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Media negeotiation and signalling archatecture
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: Thu, 07 Jul 2011 04:11:38 -0000

I'm confused about it. So how does the current implementation negotiate the codec information? 


On Jun 30, 2011, at 2:39 AM, Niklas Enbom wrote:

> Cullen, what is meant by "current Chrome implementation" in this doc? At least what we're implementing is not using the Jingle protocol on the net. We are using libJingle internally, but the API we're building is essentially the whatwg proposal with some tweaks.
> 
> Niklas
>

v2.23.0 | Report a Bug | By Email