IETF Logo Mail Archive

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

Simon Perreault <sperreault@jive.com> Mon, 08 June 2015 14:57 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 BB9C61B2E70 for <rtcweb@ietfa.amsl.com>; Mon, 8 Jun 2015 07:57: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 v4WCpt9_4y96 for <rtcweb@ietfa.amsl.com>; Mon, 8 Jun 2015 07:57:36 -0700 (PDT)
Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) (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 3EB351B2E73 for <rtcweb@ietf.org>; Mon, 8 Jun 2015 07:57:36 -0700 (PDT)
Received: by obbgp2 with SMTP id gp2so77776480obb.2 for <rtcweb@ietf.org>; Mon, 08 Jun 2015 07:57:35 -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=xBGkc4lPSYaze8jMbHeCFP64guUlH0T2DNCXz9lVu1c=; b=ht/SZUnOQ3zVfe1d6yeI9PlmarSyJz1cd9u0R1TmUWG4gUruYRh3ws4Bb/LL/rIE02 UKzf4saePvJxrETc9uTp5f/R2zyaeLxie0uL0/YLI4ntCAQtwBMu+L5UCDI/Ccpm6wqm 1Bwq57bmU6M6LFANF4EyunSBnXjFw1Ylm+lz1LEu5KJLe6R6msKlqnw/ZJ4TmmP98D3n nzyZiTK0ONFm6u/0XboQBsU5FUikP+ZsYa6L1wxshIy3P7fh/ZewPrvHc5DwpXfzimgG mNI3KIztmCoB0N3zC8H1zm5SpXRnqBn6fP9tRBcH+fmpZEUnTok/bOOkML7fwSg2cWcM LYoQ==
X-Gm-Message-State: ALoCoQlEaRrDHSjChd4ErIcwuS06rbJCSmydN8R3z3AnV3R4GdvypTWsepCYZm7VBOvTxWx2+F1H
X-Received: by 10.182.230.75 with SMTP id sw11mr14230897obc.60.1433775455736; Mon, 08 Jun 2015 07:57:35 -0700 (PDT)
Received: from jivecommunications.com ([199.87.120.129]) by mx.google.com with ESMTPSA id fy4sm1881082oeb.12.2015.06.08.07.57.34 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Jun 2015 07:57:35 -0700 (PDT)
Message-ID: <5575AD5D.5070001@jive.com>
Date: Mon, 08 Jun 2015 08:57:33 -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: Magnus Westerlund <magnus.westerlund@ericsson.com>, Harald Alvestrand <harald@alvestrand.no>, 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>
In-Reply-To: <5575A9F9.5030504@ericsson.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/M0J9mWkNsi2XO_YCz5zbnaua8Qs>
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 14:57:37 -0000

Le 2015-06-08 08:43, Magnus Westerlund a écrit :
>>>> Are there legacy gateways that will NOT fall over on a clock rate +
>>>> SSRC
>>>> switch?
>>>
>>> Good Question!
>>
>> Depends what you mean by "legacy". My gateway will not fall over.
>>
> 
> I think this is an import aspect. The gateway is not legacy, as it is an
> WebRTC gateway. It is the endpoint on the other side of the gateway that
> is "legacy".

My modus operandi with endpoints is: if you haven't tested it and seen
it working, then you must assume it will fail. It's a sad state of
affairs. Implementers should be whipped and forced to attend SIPit. ;)

In any case, that's why we have SBCs.

Personally, having the WebRTC clients do the right thing makes my life
easier. Focusing too much on compatibility with legacy makes my life
harder. I can make the gateway do the fixup easily. But as WebRTC
inevitably grows and SIP diminishes, my life becomes gradually happier. :D

Simon

v2.23.0 | Report a Bug | By Email