Re: [multimob] Fast Handover Solutions

"Rajeev Koodli (rkoodli)" <rkoodli@cisco.com> Tue, 27 November 2012 00:07 UTC

Return-Path: <rkoodli@cisco.com>
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 2C23C21F84F1 for <multimob@ietfa.amsl.com>; Mon, 26 Nov 2012 16:07:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 3GjwilG7Yemw for <multimob@ietfa.amsl.com>; Mon, 26 Nov 2012 16:07:31 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 41AFE21F84F0 for <multimob@ietf.org>; Mon, 26 Nov 2012 16:07:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4486; q=dns/txt; s=iport; t=1353974851; x=1355184451; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=7SVB4netwq16Uqf3SuAOSe9NCfECup7D4eSw8aVfo9M=; b=jlLala3IW7d5wHfCPrAEPJ4yIl4iBMhQWdWqYX9se/csyflg+UAUONWt cwy0oZhquVKCqhToBT3QOIpaWLiMOoZzivNULV26bPtbYy3OHuP5oMyH9 pNwL9ZRozlbOmxtuskbNJ2AyUwidGlR/Wvrry3D1DGn/2uaqLZUTPpF4U 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EACYDtFCtJXG//2dsb2JhbABEFsAOgQmCHgEBAQQBAQFrCxIBCBgKRQYLJQIEAQkEBQgTh2ADDwywN4ZYDYlUi05pg2BhA4gpjAOCcYoYA4UNgm+CHQ
X-IronPort-AV: E=McAfee;i="5400,1158,6908"; a="146456930"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-4.cisco.com with ESMTP; 27 Nov 2012 00:07:30 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id qAR07UWP010220 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 Nov 2012 00:07:30 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.168]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.001; Mon, 26 Nov 2012 18:07:30 -0600
From: "Rajeev Koodli (rkoodli)" <rkoodli@cisco.com>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>, "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
Thread-Topic: [multimob] Fast Handover Solutions
Thread-Index: AQHNwSUhIilrHwuomkScmGZZlY53rpfyOBMAgAAV8ICACtNhAP//pgYA
Date: Tue, 27 Nov 2012 00:07:30 +0000
Message-ID: <7C52FDEBC843C44DBAF2CA6A30662C6D0D2927@xmb-aln-x04.cisco.com>
In-Reply-To: <CAC8QAcfaFSJxSSM4geFbWSV-fLkrM6Ry93PjXmfgv94A0rksoQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.1.120420
x-originating-ip: [10.21.82.220]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5317DB3322346B48BEB6D2BE4E9D0D61@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "multimob@ietf.org" <multimob@ietf.org>
Subject: Re: [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: Tue, 27 Nov 2012 00:07:32 -0000

Hi Behcet,

On 11/26/12 1:46 PM, "Behcet Sarikaya" <sarikaya2012@gmail.com> wrote:

>On Mon, Nov 19, 2012 at 6:27 PM, Thomas C. Schmidt
><schmidt@informatik.haw-hamburg.de> wrote:
>> Hi Behcet,
>>
>> these requirements are for a fast handover solution, i.e., a protocol
>>that
>> operates a *handover* in a *fast* manner.
>>
>> I agree that draft-ietf-multimob-fast-handover does not meet the
>> requirements, but had written earlier on the list that the name of this
>> draft is misleading in two ways: (i) draft-ietf-multimob-fast-handover
>>is
>> not a fast handover solution, and (ii) the name "fast handover" is tied
>>to
>> RFC5568/RFC5949-like schemes for good reasons.
>>
>
>The draft title contains ... handover optimization ... and it reflects
>its content.
>We asked for this WG draft name because of the charter item to which
>it corresponds.

Sorry, which charter item has "fast-handover"?
Could you clarify?

Thanks.

-Rajeev

 

>
>I think this clarifies your confusion.
>
>Regards,
>
>Behcet
>
>> Cheers,
>>
>> Thomas
>>
>>
>> On 20.11.2012 00:09, Behcet Sarikaya wrote:
>>>
>>> Hi Thomas,
>>>
>>> It seems that these requirements are for
>>>
>>> draft-schmidt-multimob-fmipv6-pfmipv6-multicast
>>>
>>> and not for
>>> draft-ietf-multimob-fast-handover.
>>>
>>> What do you think?
>>>
>>> Regards,
>>>
>>> Behcet
>>>
>>> On Mon, Nov 12, 2012 at 4:28 PM, Thomas C. Schmidt
>>> <schmidt@informatik.haw-hamburg.de> wrote:
>>>>
>>>> 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-multic
>>>>ast).
>>>>
>>>>   (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-multic
>>>>ast
>>>> 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-multi
>>>>cast
>>>> 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-multic
>>>>ast.
>>>>
>>>> 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
>>>> °
>>>> _______________________________________________
>>>> multimob mailing list
>>>> multimob@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/multimob
>>
>>
>> --
>>
>> 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 °
>_______________________________________________
>multimob mailing list
>multimob@ietf.org
>https://www.ietf.org/mailman/listinfo/multimob