IETF Logo Mail Archive

Re: [Ice] Peter's review of ICEbis - Much of the spec is much more complicated than it otherwise would be because a media stream has more than one component.

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 29 May 2017 06:44 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ice@ietfa.amsl.com
Delivered-To: ice@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85520126BF0 for <ice@ietfa.amsl.com>; Sun, 28 May 2017 23:44:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 lYtZmWNzq9iP for <ice@ietfa.amsl.com>; Sun, 28 May 2017 23:44:33 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B4F41200B9 for <ice@ietf.org>; Sun, 28 May 2017 23:44:33 -0700 (PDT)
X-AuditID: c1b4fb30-039ff700000007db-e0-592bc34c20fa
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 03.D1.02011.C43CB295; Mon, 29 May 2017 08:44:31 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.30]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0339.000; Mon, 29 May 2017 08:44:29 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Peter Thatcher <pthatcher@google.com>, "ice@ietf.org" <ice@ietf.org>
Thread-Topic: [Ice] Peter's review of ICEbis - Much of the spec is much more complicated than it otherwise would be because a media stream has more than one component.
Thread-Index: AQHS2EcFiI1CctLCKk6poKZrQK4FhA==
Date: Mon, 29 May 2017 06:44:29 +0000
Message-ID: <D5519E2D.1D3AD%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.4.170508
x-originating-ip: [153.88.183.19]
Content-Type: multipart/alternative; boundary="_000_D5519E2D1D3ADchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42KZGbFdV9f/sHakwZJJ2hbfLtRaXFv+mtWB yWPBplKPJUt+MgUwRXHZpKTmZJalFunbJXBlPJ71lrXgj1DFxU9zWBsYn/N3MXJySAiYSBw7 OZW5i5GLQ0jgCKPE3AOPmSCcxYwSkzdvAspwcLAJWEh0/9MGaRAR8JDY/GY5G0iNsMAqRokd U0+DdYsIrGaUeH/5KitElZ7Ex4PPwWwWAVWJa9M3sYIM4hWwlriwJwokzCggJvH91BomEJtZ QFzi1pP5TBAXCUgs2XOeGcIWlXj5+B9YqyjQyHf7PSHCihLtTxsYIVoTJPb82g5m8woISpyc +YRlAqPQLCRTZyEpm4WkDCJuIPH+3HxmCFtbYtnC11C2vsTGL2cZIWxriVcn7jMhq1nAyLGK UbQ4tTgpN93ISC+1KDO5uDg/Ty8vtWQTIzB2Dm75bbCD8eVzx0OMAhyMSjy8HOu1I4VYE8uK K3MPMUpwMCuJ8E4tBwrxpiRWVqUW5ccXleakFh9ilOZgURLnddx3IUJIID2xJDU7NbUgtQgm y8TBKdXAuKP4SOJFf6WCiHRls6cGU33FN/Q03/pjXNG6TrFY8mH+Ob/DUc9tmllaijYubDgY KajI4PkghsNy6zkj+Y2RPPwPV5z8uiKnQUn5UIJPqNqRJUw+Nik33Bct9dr2rtlWRfPFEUmJ 2f/0f/x6/82UR9nCPU4wqLW/vOuweIhno/s6RT9TPnUlluKMREMt5qLiRAATdh2emQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ice/X6Pq7fIVCjxi-BWbu3SxEoi-3lQ>
Subject: Re: [Ice] Peter's review of ICEbis - Much of the spec is much more complicated than it otherwise would be because a media stream has more than one component.
X-BeenThere: ice@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Interactive Connectivity Establishment \(ICE\)" <ice.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ice>, <mailto:ice-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ice/>
List-Post: <mailto:ice@ietf.org>
List-Help: <mailto:ice-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ice>, <mailto:ice-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 May 2017 06:44:34 -0000

Hi,

> - Much of the spec is much more complicated than it otherwise would be because a media stream has more than one component.  Would it make sense
> to define a check list as representing a single component of a single media stream rather than multiple components?  That would make the rules and states around check lists much more simple.

I have been thinking the same thing :)

However, in that case I think we need to talk about certain media streams being “dependent" on each other, and that checks for both streams (e.g., one RTP stream and one RTCP stream) must succeed in order to the streams to be used (unless BUNDLE is used, of course).

Regards,

Christer

v2.23.0 | Report a Bug | By Email