[MMUSIC] Adding multihomed fairness to the ICE dualstack fairness draft

"Pal Martinsen (palmarti)" <palmarti@cisco.com> Mon, 09 February 2015 10:19 UTC

Return-Path: <palmarti@cisco.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 337071A01AA for <mmusic@ietfa.amsl.com>; Mon, 9 Feb 2015 02:19:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 IaWyPgDw0_My for <mmusic@ietfa.amsl.com>; Mon, 9 Feb 2015 02:19:42 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 012741A01A9 for <mmusic@ietf.org>; Mon, 9 Feb 2015 02:19:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12704; q=dns/txt; s=iport; t=1423477182; x=1424686782; h=from:to:subject:date:message-id:references:mime-version; bh=Qdg8NqZ27ObdeI1aIxR2frSDj//y+6Y0QM5CVlRdbuY=; b=bua2qMxGICiqOJ46EVzxA7MfwWOub8gLLvoPCxZL++DavHiGgQI3h+m5 XIwwawPGoE0dHf3fDqt1XHRyVdYCFX4mw3D/1q7tdLM6xSLMNyIrqUQzi 4/bAGNDzQ+Y8XsJMYsVERf9a45lb9B4Ws+2mvQOO3ZxWIwHHarAng/cBx U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkoIAJqI2FStJV2a/2dsb2JhbABcgwZSWgSCfr4LgWyFbwIceEMBAQEBAQF8hAwBAQEEI2YCARkDAQIoAwICAjAUCQgCBBMJiCQNsEuWBgEBAQEBAQQBAQEBAQEBAQEBARePdAoHgmIugRQFjxuDUIVcgRg2gk2OVSKDbm8BgUN+AQEB
X-IronPort-AV: E=Sophos;i="5.09,543,1418083200"; d="scan'208,217";a="394568454"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-3.cisco.com with ESMTP; 09 Feb 2015 10:19:41 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t19AJftW024297 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mmusic@ietf.org>; Mon, 9 Feb 2015 10:19:41 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.15]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Mon, 9 Feb 2015 04:19:40 -0600
From: "Pal Martinsen (palmarti)" <palmarti@cisco.com>
To: mmusic <mmusic@ietf.org>
Thread-Topic: Adding multihomed fairness to the ICE dualstack fairness draft
Thread-Index: AQHQRFHqLYK2sT+uHUisecUWXBQdQQ==
Date: Mon, 09 Feb 2015 10:19:40 +0000
Message-ID: <87B0413F-78F4-408A-872F-D446B917C172@cisco.com>
References: <20150209100203.12891.61110.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.55.154.76]
Content-Type: multipart/alternative; boundary="_000_87B0413F78F4408A872FD446B917C172ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/_UEbXtQu7STDHu6ZNa_FV5cGwSQ>
Subject: [MMUSIC] Adding multihomed fairness to the ICE dualstack fairness draft
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: Mon, 09 Feb 2015 10:19:45 -0000

Hi again,

The lack of supporting multihomed (as used in ICE context) support in the draft seems to be the last remaining issue to solve. This make sense as IPv4/IPv6 dualstack really is a special case of the more general multihomed scenario. So we decided to have a go at it.

The approach is fairly simple. The different interfaces an agent can use are divided into two categories, based on either static or dynamic agent knowledge. An interface can be known to the agent to provide either stable or unstable connectivity. Details are in the draft.

.-.
Pål-Erik




Begin forwarded message:

From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
To: Prashanth Patil <praspati@cisco.com<mailto:praspati@cisco.com>>, Tirumaleswar Reddy <tireddy@cisco.com<mailto:tireddy@cisco.com>>, Prashanth Patil <praspati@cisco.com<mailto:praspati@cisco.com>>, "Paal-Erik Martinsen" <palmarti@cisco.com<mailto:palmarti@cisco.com>>, Tirumaleswar Reddy <tireddy@cisco.com<mailto:tireddy@cisco.com>>, Paal-Erik Martinsen <palmarti@cisco.com<mailto:palmarti@cisco.com>>
Subject: New Version Notification for draft-martinsen-mmusic-ice-dualstack-fairness-02.txt
Date: 9 Feb 2015 11:02:03 CET


A new version of I-D, draft-martinsen-mmusic-ice-dualstack-fairness-02.txt
has been successfully submitted by Paal-Erik Martinsen and posted to the
IETF repository.

Name: draft-martinsen-mmusic-ice-dualstack-fairness
Revision: 02
Title: ICE IPv4/IPv6 Dual Stack Fairness
Document date: 2015-02-09
Group: Individual Submission
Pages: 9
URL:            http://www.ietf.org/internet-drafts/draft-martinsen-mmusic-ice-dualstack-fairness-02.txt
Status:         https://datatracker.ietf.org/doc/draft-martinsen-mmusic-ice-dualstack-fairness/
Htmlized:       http://tools.ietf.org/html/draft-martinsen-mmusic-ice-dualstack-fairness-02
Diff:           http://www.ietf.org/rfcdiff?url2=draft-martinsen-mmusic-ice-dualstack-fairness-02

Abstract:
  This document provides guidelines on how to make Interactive
  Connectivity Establishment (ICE) conclude faster in multihomed and
  IPv4/IPv6 dual-stack scenarios where broken paths exist.  The
  provided guidelines are backwards compatible with the original ICE
  specification.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

The IETF Secretariat