Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.

Philipp Hancke <> Mon, 22 July 2013 18:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4E21C21F9477 for <>; Mon, 22 Jul 2013 11:27:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.082
X-Spam-Status: No, score=-1.082 tagged_above=-999 required=5 tests=[AWL=1.517, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id W7EcMIlgEHYn for <>; Mon, 22 Jul 2013 11:27:48 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 7427A21F93F3 for <>; Mon, 22 Jul 2013 11:27:43 -0700 (PDT)
Received: from [] ( []) (authenticated bits=0) by (8.14.3/8.14.3/Debian-9.4) with ESMTP id r6MIRdcK015026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Jul 2013 20:27:40 +0200
Message-ID: <>
Date: Mon, 22 Jul 2013 20:27:33 +0200
From: Philipp Hancke <>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Roman Shpount <>
References: <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: XMPP Jingle <>,,
Subject: Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 22 Jul 2013 18:27:53 -0000

Am 22.07.2013 19:45, schrieb Roman Shpount:
>> It's hard work and there are some points where this is PITA, I have
>> discovered numerous bugs in chrome (and the jingle spec) along the way, but
>> it's certainly not unfeasible.
> Out of curiosity, does the same code work with Firefox?

Yes, feel free to fork it at and 
try the example. The core mapping has been relatively stable since I 
showed the first public version at the xmpp summit in Brussels six 
months ago.

Things like chrome suddenly (in canary) requiring a mapping of a=rtcp-fb 
weren't helpful and required extra work, but I do not expect this to 
happen too often once the SDP requirements are agreed upon.

It even sends to and receives rtp from Jitsi, even though no side is 
playing out anything yet; that can hopefully be resolved in Berlin.