[MMUSIC] ICE tiebreaker - session-level or media-level?
Justin Uberti <juberti@google.com> Fri, 12 October 2012 06:25 UTC
Return-Path: <juberti@google.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9C5421F84EC for <mmusic@ietfa.amsl.com>; Thu, 11 Oct 2012 23:25:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.837
X-Spam-Level:
X-Spam-Status: No, score=-102.837 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ecNp8vGQ12a for <mmusic@ietfa.amsl.com>; Thu, 11 Oct 2012 23:25:57 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1E78621F84EA for <mmusic@ietf.org>; Thu, 11 Oct 2012 23:25:56 -0700 (PDT)
Received: by mail-qc0-f172.google.com with SMTP id s14so2320550qcg.31 for <mmusic@ietf.org>; Thu, 11 Oct 2012 23:25:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :x-system-of-record; bh=DtsxKiQVSEDPYq0B6ZKFhR8Hes5P2WP8cTv+0tmv8Y0=; b=WMNA8COxN78YWp2MNjzDk7iAmVBv5WO0qPw9sg8/4N1+dvXDF/Vuo5sEgrbeUz8RVk 8fiXNyRyZruCy13kjfDbaB8u6Xr9SP0bH0v/bn0BnMFvLDJo0KB2pNKDnPNC2oR8cz+f ODbVz2q9slOS35dnicMhKQT47qwfT20DwQARd5jZgm8kTWKu9QcM/7s+SEtgyJWk8vHV F1JTZZuk2hm0j0lrgeA20l8yTg9wm9VS87GHGHiTWFKhOAOhLRVcumoAjN6wgYeyDcG1 VMgKzFV67H7AFon3pykR3obKmWotBw9q/e0y4WK9F1AkbvnWT8f2tFCvp0u1BRcCl1xg l/lw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :x-system-of-record:x-gm-message-state; bh=DtsxKiQVSEDPYq0B6ZKFhR8Hes5P2WP8cTv+0tmv8Y0=; b=cbc8tXyZ/W0586KyLkvDmHRJylP/kEnp02jir2DpBqBz8vi1u9BckICAcI+zcfmaKS H+x/PrfE2uNnTyPFT6XlhPkUWtgUK2lCipMUIlO4gwuN1zTI5ilrzrI8XiF0UlGXobat oo3JaDBPt2/biZiN5W4HRyYpyZ/ab2P9F5pIa1gFEwaRbx6zyAc7hK9lpllcjCHpqAkT Pqwh2e01gjvbWz+uRNfW8zTny4g8VxVnWPLepU1Htnd5NRyQoLksR9AMPwafglnEADep W4g2fb+Vnnpe9DqRpg/senqK2qssaoh097VHjX2e4L1nFb1XuFBGy0K1awzb5ldU2IWV VJkg==
Received: by 10.224.213.10 with SMTP id gu10mr5884471qab.10.1350023156436; Thu, 11 Oct 2012 23:25:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.216.194 with HTTP; Thu, 11 Oct 2012 23:25:36 -0700 (PDT)
From: Justin Uberti <juberti@google.com>
Date: Thu, 11 Oct 2012 23:25:36 -0700
Message-ID: <CAOJ7v-3P7ym=ASXn-_we6BwBsj3KthzbgY5Vu=+9o-2xSBpuFQ@mail.gmail.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="20cf300fae13ad8d1204cbd6c2b7"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQkQbcoTioy8Ig/MrDKL+m1scJjQ+iL2/Dz+RoEvXzM+0sZboFDgFWQ5DqxUNkdDKxBKUlgbxgtlJBYd7HS490yBFXM96X+IPwMC4LX3Gu2GEDZygWt6r/bA0tEgvgsibL2CK+7EkQgiJ7gYs0FNKCUMZQhWCC2qlZC/DXzJZZc+dMwvPhlYqrM/sSnT403zqk4F9zdv
Subject: [MMUSIC] ICE tiebreaker - session-level or media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Oct 2012 06:25:57 -0000
Reviewing the handling of role conflicts, a question came up: in the event
different systems handle different media in a session, do they have to
share the same ICE tiebreaker?
Section 5.2 of RFC 5245 indicates that the ICE Agent chooses the
tiebreaker, indicating that this is a session-level value.
To resolve this, each agent MUST select a random number, called
the tie-breaker, uniformly distributed between 0 and (2**64) - 1
(that is, a 64-bit positive integer). This number is used in
connectivity checks to detect and repair this case, as described
in Section 7.1.2.2 <http://tools.ietf.org/html/rfc5245#section-7.1.2.2>.
Or am I misreading, and each m= line corresponds to its own ICE Agent,
with its own tiebreaker value?
Thanks,
--justin
- [MMUSIC] ICE tiebreaker - session-level or media-… Justin Uberti
- Re: [MMUSIC] ICE tiebreaker - session-level or me… Marc Petit-Huguenin
- Re: [MMUSIC] ICE tiebreaker - session-level or me… Martin Thomson