[MMUSIC] ICE Multihomed lingo

"Pal Martinsen (palmarti)" <palmarti@cisco.com> Wed, 03 June 2015 12:57 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 E94461A0381 for <mmusic@ietfa.amsl.com>; Wed, 3 Jun 2015 05:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 jv34gPDwb3CL for <mmusic@ietfa.amsl.com>; Wed, 3 Jun 2015 05:57:07 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D3A41A0217 for <mmusic@ietf.org>; Wed, 3 Jun 2015 05:57:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1664; q=dns/txt; s=iport; t=1433336227; x=1434545827; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=pq7CUER8UIgy0Ykh5ouv7eAKtDA5/I3IE0/pXSyjnac=; b=dzw2i4/YpX3wg6s743xab9lx1gE7k5Snk5QECG+O0oB32nerKB/yGC+W SZoQmpLILS6WgYwQSA/B2AcjEop5bj8FDKb1sfZkXd5luLIc3ePND0j9U C8NsnUmOn6/nqghEmIt5GhxY2tsLP/TBZiOUavs/L1etdBiOYjYmsqbgR 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CFBQD/+G5V/5tdJa1bgxCBOIMYu0KHb4EsOhIBAQEBAQEBgQqEKSMRVwEiAiYCBDAVEgSIQKcmj1+jfgEBAQEBBQEBAQEBAQEbgSGSFy+BFgWTEosel0QjYYEpHIFSgjWBAQEBAQ
X-IronPort-AV: E=Sophos;i="5.13,547,1427760000"; d="scan'208";a="155843671"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-3.cisco.com with ESMTP; 03 Jun 2015 12:57:06 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t53Cv6Ih022518 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mmusic@ietf.org>; Wed, 3 Jun 2015 12:57:06 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.183]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Wed, 3 Jun 2015 07:57:06 -0500
From: "Pal Martinsen (palmarti)" <palmarti@cisco.com>
To: mmusic <mmusic@ietf.org>
Thread-Topic: ICE Multihomed lingo
Thread-Index: AQHQnfzLrCvFrpDBSE6hNIw5oa6Adw==
Date: Wed, 03 Jun 2015 12:57:06 +0000
Message-ID: <39C2F662-2261-4ACA-A7F6-CF99F81CC5DE@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.104.212]
Content-Type: text/plain; charset="utf-8"
Content-ID: <74E9428D23F3C742A9B8AFC82E985AFD@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/iI-hRC_197hMvEkSGqZxorPzGT0>
Subject: [MMUSIC] ICE Multihomed lingo
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: Wed, 03 Jun 2015 12:57:10 -0000

Hi,

After asking for review of draft-ietf-mmusic-ice-dualstack-fairness by an IPv6 guy (not on the MMUSIC list) he pointed out that he was a bit confused regarding the term multihomed agent. Apparently there are several variations of multihoming; multi-interface multihoming, multi-prefixing multihoming, site multihoming and so on.

Not sure if this is confusing or needs a better definition in the various ICE specs. Any thoughts?

The current and slightly updated text in the fainess drafts says:

A multihomed ICE agent can potentially send and receive connectivity
checks on all available interfaces and IP addresses.  It is possible
for an interface to have several IP addresses associated with it.  To
avoid unnecessary delay when performing connectivity checks it would
be beneficial to prioritize interfaces and IP addresses known by the
agent to provide stable connectivity.  If the agent have access to
information about the physical network it is connected to (Like SSID
in a WiFi Network) this can be used as information regarding how that
network interface should be prioritized at this point in time.


Does the text above need a stricter multihomed definition?

.-.
Pål-Erik