Re: [Perc] Consensus call: SSRCs are immutable

"Roni Even" <ron.even.tlv@gmail.com> Wed, 11 November 2015 22:34 UTC

Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: perc@ietfa.amsl.com
Delivered-To: perc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D34131B3B84 for <perc@ietfa.amsl.com>; Wed, 11 Nov 2015 14:34:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 W9qUXKNflnNd for <perc@ietfa.amsl.com>; Wed, 11 Nov 2015 14:34:56 -0800 (PST)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 44BA31B3B83 for <perc@ietf.org>; Wed, 11 Nov 2015 14:34:56 -0800 (PST)
Received: by wmec201 with SMTP id c201so66847368wme.1 for <perc@ietf.org>; Wed, 11 Nov 2015 14:34:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=EjZoNCo/cNivwylYzPtCd67OZMcCjg2bwBjPsTWVaeg=; b=HP5BwlFsSacnw+ZMP0OC87IR2MwvKsMsKzSJBhaDuZAuzxFS+QAvVos1h32qyfmQqy BfUchrkNktoKT481sRjLQv2lVOUwhJlKk8/xmb4ZPWAjK27hwidxddf77S4hasi7cmTw ddoiwHmmII5KLZqEnk/TNgmPUVcGrc2qp8yk59yMhaxhZzbNtTpDcMtYpgb8IAYDshLF wNhEG7ScFVaF/WczIL5rQoOdtAB+U8JdACKucVItjYz0X1Yiw3LdMSExP0dpi387EK6D Ky4drngmxJBuCAaTiRu9iuWPIWW8G//TodNGrVYDWiBHxFdYO3VN7W2Irj9h7nEN+fmV i44g==
X-Received: by 10.194.118.226 with SMTP id kp2mr12921425wjb.59.1447281294727; Wed, 11 Nov 2015 14:34:54 -0800 (PST)
Received: from RoniPC (bzq-79-176-26-37.red.bezeqint.net. [79.176.26.37]) by smtp.gmail.com with ESMTPSA id l186sm27443813wmg.19.2015.11.11.14.34.52 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 11 Nov 2015 14:34:53 -0800 (PST)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Jonathan Lennox' <jonathan@vidyo.com>, 'Richard Barnes' <rlb@ipv.sx>
References: <CAL02cgSn_wVYpiPGrnRM2=rJnwvjAuCnOC=+UitLN7zpo8h1hw@mail.gmail.com> <8E19B154-6072-4B10-84F7-2D2F674E491F@vidyo.com>
In-Reply-To: <8E19B154-6072-4B10-84F7-2D2F674E491F@vidyo.com>
Date: Thu, 12 Nov 2015 00:34:49 +0200
Message-ID: <014501d11cd1$2e539ff0$8afadfd0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGekG49E0tWe8momegCk7AZGLur1wFy1DnMnvDpGxA=
Content-Language: he
Archived-At: <http://mailarchive.ietf.org/arch/msg/perc/9LLPeMOCjuefJEDXpsglUG3V8pI>
Cc: perc@ietf.org
Subject: Re: [Perc] Consensus call: SSRCs are immutable
X-BeenThere: perc@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Privacy Enhanced RTP Conferencing <perc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perc>, <mailto:perc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perc/>
List-Post: <mailto:perc@ietf.org>
List-Help: <mailto:perc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perc>, <mailto:perc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2015 22:35:00 -0000

Hi,
Agree with Jonathan and want to add that collision detection when the endpoint assign SSRC should also work for the cascaded case as described in Magnus' draft and if the MDD assigns SSRCs it should not complicate using RFC5576 SSRC attribute.
Roni




-----Original Message-----
From: Perc [mailto:perc-bounces@ietf.org] On Behalf Of Jonathan Lennox
Sent: Wednesday, November 11, 2015 9:14 PM
To: Richard Barnes
Cc: perc@ietf.org
Subject: Re: [Perc] Consensus call: SSRCs are immutable


> On Nov 11, 2015, at 1:49 PM, Richard Barnes <rlb@ipv.sx> wrote:
> 
> tl;dr: Do we have consensus that PERC should regard SSRCs as something 
> that an MDD MUST NOT change?  Please reply by Nov. 25.
> 
> At the PERC meeting at IETF 94, there was a discussion of which 
> portions of an SRTP packet an MDD should be allowed to modify.  At the 
> end of this discussion, there was pretty much unanimous agreement in 
> the room that MDDs should *not* be allowed to modify SSRC.  The only 
> people who were not explicitly in agreement were a couple of folks who 
> said they wanted to think about it.
> 
> This email is a formal call to confirm the consensus in the room.  If 
> you have any objections to the conclusion reached at the meeting -- 
> especially if you were not at the meeting -- please reply to this 
> message no later than Wednesday, November 25.

I’d like to have a convincing story about how SSRC uniqueness is guaranteed before we make this decision.

Having the KDF hand out SSRC values would be one possibility, but it has architectural implications — there are parts of the RTP architecture that implicitly assume endpoints can self-assign SSRC values as needed, e.g. RFC 7160.

Alternately, the MDD could probably make collisions visible (even for sources that aren’t currently being routed) by forwarding/generating RTCP as necessary, but we need to make sure this scales for large conferences, and that it doesn’t open up the possibility for a malicious MDD to do anything too nasty.

_______________________________________________
Perc mailing list
Perc@ietf.org
https://www.ietf.org/mailman/listinfo/perc