Re: [rtcweb] JSEP: Issues with a=ssrc and RTP payload type switching

Simon Perreault <sperreault@jive.com> Mon, 08 June 2015 15:16 UTC

Return-Path: <sperreault@jive.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A5FD1B2ED9 for <rtcweb@ietfa.amsl.com>; Mon, 8 Jun 2015 08:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tyNk0ngD3fPj for <rtcweb@ietfa.amsl.com>; Mon, 8 Jun 2015 08:16:36 -0700 (PDT)
Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com [209.85.214.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6B691B2F19 for <rtcweb@ietf.org>; Mon, 8 Jun 2015 08:15:07 -0700 (PDT)
Received: by obbgp2 with SMTP id gp2so78216550obb.2 for <rtcweb@ietf.org>; Mon, 08 Jun 2015 08:15:07 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=HHa3GBlVNj3JS2SZm0rTXTTbfQK91+1vrFUA1pEkF/g=; b=Ub2zE56FwyLHfL1YDFxL6Orr34ACEs8Fsd4qrSE6tbSm3mfMURyT4BFwt5x3csL2JR /LjZwG6+ojOYk9h8wTRnFoE3wbVYmR56pBhR+s500+e0iHMptGoCjvQpz7gf3ABcWEDS ZSYmT56bx/khiFb6pu+rYyGdYiQjbTFHneGfEbSpNDNwOKvoZVJ2hIhCIf/P1dQP87xr nS2jYpkmsyqi6A/ioA9ESwQVgVhujVE164swC/OpwZKanvj81k5NER2WF1UT/eCmCtxs /HGI2tUdMraMU0TflNtdWpMwXrXU0hFmgbd6JikLEJnNFBctb+Q6pSKCdKwCiFFxWOrs Kgfg==
X-Gm-Message-State: ALoCoQkG+Qf4AgwkiwObd6R5OUQK2w67Ej8D8GMPV2H5/oOFVAyP3GyS76Zh3HaZr+GM6DkIIWr3
X-Received: by 10.182.87.36 with SMTP id u4mr14948951obz.50.1433776507111; Mon, 08 Jun 2015 08:15:07 -0700 (PDT)
Received: from jivecommunications.com ([199.87.120.129]) by mx.google.com with ESMTPSA id yr6sm1936262obc.23.2015.06.08.08.15.05 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Jun 2015 08:15:06 -0700 (PDT)
Message-ID: <5575B178.1040309@jive.com>
Date: Mon, 08 Jun 2015 09:15:04 -0600
From: Simon Perreault <sperreault@jive.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>, Magnus Westerlund <magnus.westerlund@ericsson.com>, Roman Shpount <roman@telurix.com>
References: <556EF4F9.1060700@ericsson.com> <556F5E5C.5080600@alvestrand.no> <CAD5OKxs4_hVc-7haF7vik7+PNU33Ox9Jin35tzrPhiaekENLvQ@mail.gmail.com> <557556ED.8050206@ericsson.com> <55755E12.8020201@alvestrand.no> <55756237.6060206@ericsson.com> <5575A364.7060900@jive.com> <5575A9F9.5030504@ericsson.com> <5575B013.3030701@alvestrand.no>
In-Reply-To: <5575B013.3030701@alvestrand.no>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/tkwVu3kMcEQCt_7Vby_P3muDvc4>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] JSEP: Issues with a=ssrc and RTP payload type switching
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 08 Jun 2015 15:16:37 -0000

Le 2015-06-08 09:09, Harald Alvestrand a écrit :
> This has another implication:
> 
> When doing PT switching for comfort noise, you MUST have a CN with the
> same clock rate as your normal audio codec.
> 
> CN is exactly the type of PT-switching that, if it occurs at all, occurs
> very frequently.

I'm not following. We're discussing generating a new SSRC on clock
rate-switching, not on PT-switching. For the CN example, you would
typically include in your SDP one CN payload type per possible clock
type so that you can switch payload types without switching the clock rate.

Simon