[multimob] Fast Handover Solutions

"Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de> Mon, 12 November 2012 22:29 UTC

Return-Path: <prvs=6565d6a3d=schmidt@informatik.haw-hamburg.de>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3146D21F8773 for <multimob@ietfa.amsl.com>; Mon, 12 Nov 2012 14:29:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level:
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 uuvdgLm+pwI7 for <multimob@ietfa.amsl.com>; Mon, 12 Nov 2012 14:29:04 -0800 (PST)
Received: from mx6.haw-public.haw-hamburg.de (mx6.haw-public.haw-hamburg.de [141.22.6.3]) by ietfa.amsl.com (Postfix) with ESMTP id 1CD1121F874D for <multimob@ietf.org>; Mon, 12 Nov 2012 14:28:56 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmoIAHl3oVCNFh5K/2dsb2JhbABEFsNMgQEHglcBBUA9FhgDAgECAUsKAwgBAReHcweYQqEzkAOCXAOXGIRPhUqFDoJiDg
Received: from mailgate.informatik.haw-hamburg.de ([141.22.30.74]) by mail6.is.haw-hamburg.de with ESMTP/TLS/ADH-AES256-SHA; 12 Nov 2012 23:28:56 +0100
Received: from localhost (localhost [127.0.0.1]) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTP id F0504104DABC for <multimob@ietf.org>; Mon, 12 Nov 2012 23:28:55 +0100 (CET)
Received: from mailgate.informatik.haw-hamburg.de ([127.0.0.1]) by localhost (mailgate.informatik.haw-hamburg.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 31014-06 for <multimob@ietf.org>; Mon, 12 Nov 2012 23:28:55 +0100 (CET)
Received: from [192.168.178.36] (g231108188.adsl.alicedsl.de [92.231.108.188]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTPSA id 7AA22107B96A for <multimob@ietf.org>; Mon, 12 Nov 2012 23:28:55 +0100 (CET)
Message-ID: <50A17826.5070109@informatik.haw-hamburg.de>
Date: Mon, 12 Nov 2012 23:28:54 +0100
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "multimob@ietf.org" <multimob@ietf.org>
Content-Type: text/plain; charset="ISO-8859-15"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by amavisd-new at informatik.haw-hamburg.de
Subject: [multimob] Fast Handover Solutions
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2012 22:29:05 -0000

Hi all,

after the - somewhat uninformed discussion at IETF85 - chairs asked me 
to restate requirements of a "fast handover solution" for Multicast 
Mobility.

Here they are:

  (i) Handover should be fast (this is only true for a direct pMAG/AR to 
nMAG/AR solution such as 
http://tools.ietf.org/html/draft-schmidt-multimob-fmipv6-pfmipv6-multicast).

  (ii) Multicast handover should be fully synchronized with unicast 
handover (otherwise unicast and multicast states diverge as is a 
well-known issue for the RAMS-approach, i.e., 
https://tools.ietf.org/html/draft-ietf-multimob-fast-handover).

  (iii) Multicast handover solutions should tightly integrate with 
unicast handover (only 
http://tools.ietf.org/html/draft-schmidt-multimob-fmipv6-pfmipv6-multicast 
integrates with PFMIPv6 and FMIPv6).

  (iv) Handover management should reuse standard mobility and multicast 
protocol operations for easy implementation and deployment 
(http://tools.ietf.org/html/draft-schmidt-multimob-fmipv6-pfmipv6-multicast 
introduced the use of standard IGMP/MLD records for context description 
in transfer, which has been copied several times).

  (v) Multicast handover management should integrate ASM and SSM, as 
well as IPv4 (IGMP) and IPv6 (MLD), which is only provided by 
http://tools.ietf.org/html/draft-schmidt-multimob-fmipv6-pfmipv6-multicast.

Based on these facts, chairs and AD proclaimed to re-decide on future 
paths for Multimob fast handover solutions.

Cheers,

Thomas
-- 

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °