Re: [MMUSIC] ICE PRIORITY with multiple TURN servers

"Stach, Thomas" <thomas.stach@unify.com> Fri, 06 June 2014 07:12 UTC

Return-Path: <thomas.stach@unify.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2342A1A010A for <mmusic@ietfa.amsl.com>; Fri, 6 Jun 2014 00:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level:
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RP_MATCHES_RCVD=-0.651] 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 PiNgmwgvfJQq for <mmusic@ietfa.amsl.com>; Fri, 6 Jun 2014 00:12:06 -0700 (PDT)
Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 31B521A00C5 for <mmusic@ietf.org>; Fri, 6 Jun 2014 00:12:06 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx12.unify.com (Server) with ESMTP id 2A59A23F0574; Fri, 6 Jun 2014 09:11:59 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.222]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0174.001; Fri, 6 Jun 2014 09:11:58 +0200
From: "Stach, Thomas" <thomas.stach@unify.com>
To: Justin Uberti <juberti@google.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Mallinath Bareddy <mallinath@google.com>, Jiayang Liu <jiayl@google.com>, Eric Rescorla <ekr@rtfm.com>
Thread-Topic: [MMUSIC] ICE PRIORITY with multiple TURN servers
Thread-Index: AQHPgSPtCa0N0iwsfU2FCZjPJ+UUq5tjqW9A
Date: Fri, 06 Jun 2014 07:11:58 +0000
Message-ID: <F81CEE99482EFE438DAE2A652361EE1217AAEB31@MCHP04MSX.global-ad.net>
References: <CAOJ7v-3osr-hMpTgVg7EwCJtBPdeaeUQ9ObPPZq-TqDnrjs+Kg@mail.gmail.com>
In-Reply-To: <CAOJ7v-3osr-hMpTgVg7EwCJtBPdeaeUQ9ObPPZq-TqDnrjs+Kg@mail.gmail.com>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.29.42.225]
Content-Type: multipart/alternative; boundary="_000_F81CEE99482EFE438DAE2A652361EE1217AAEB31MCHP04MSXglobal_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/2U6kKBuEvGnj1KKPI_qYFl3kZ2c
Subject: Re: [MMUSIC] ICE PRIORITY with multiple TURN servers
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jun 2014 07:12:08 -0000

Justin,

From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Justin Uberti
Sent: Freitag, 6. Juni 2014 03:09
To: mmusic@ietf.org; Mallinath Bareddy; Jiayang Liu; Eric Rescorla
Subject: [MMUSIC] ICE PRIORITY with multiple TURN servers

Consider the case where a single endpoint has 2 TURN servers, and allocates a relay candidate from both, from the same local IP. What should their PRIORITY values be?

Quoth 5245, S 4.1.2:
   Each candidate for a media stream MUST have a unique
   priority that MUST be a positive integer between 1 and (2**31 - 1).

OK, so they have to have different priorities, i.e. either their type preference or local preference must be different. But then, looking at S 4.1.2.1<http://4.1.2.1>:
   The type preference MUST be identical for all
   candidates of the same type and MUST be different for candidates of
   different types.

Hmm, this means their local_preference must be different. But later in S 4.1.2.1<http://4.1.2.1>:
   The local preference MUST be an integer from 0 to 65535 inclusive.
   It represents a preference for the particular IP address from which
   the candidate was obtained, in cases where an agent is multihomed.

Obviously, if they come from the same local IP, this cannot be satisfied. What to do?
[TS] Well, that paragraph continues:

  When there is only a single IP address, this value SHOULD be set to
   65535.  More generally, if there are multiple candidates for a
   particular component for a particular media stream that have the same
   type, the local preference MUST be unique for each one.

So the case of two TURN servers is covered.
What you propose below is OK, but if desired you could  also rank A1, A2, B1, B2. It’s your freedom of choice.
Regards
Thomas

It seems like the easiest solution would be to use some of the local preference to represent the ordering, so that both IP preference and server preference and represented, and therefore relay candidates from IPs 1 and 2 and Turn Servers A and B would stack rank as
A1
B1
A2
B2