Re: [multimob] Fast Handover Solutions

Behcet Sarikaya <sarikaya2012@gmail.com> Tue, 27 November 2012 17:24 UTC

Return-Path: <sarikaya2012@gmail.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 9CC5A21F87E0 for <multimob@ietfa.amsl.com>; Tue, 27 Nov 2012 09:24:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 D4qoTPGmkYBN for <multimob@ietfa.amsl.com>; Tue, 27 Nov 2012 09:24:34 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 606F921F8711 for <multimob@ietf.org>; Tue, 27 Nov 2012 09:24:34 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id j26so9954433iaf.31 for <multimob@ietf.org>; Tue, 27 Nov 2012 09:24:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=vN03/vEcSY69uk3ibwKc+RPmn9oLSur24bUWuT5WacE=; b=01JaodSvQYzy9B1I8Fo7Evr2ook5DENbsPSpDzkTWD3pOfFy7yfsY5TH5EPw+XwCAZ WZ9YuKRSlQcBxNotCZGHvpNvsVqAfI8BXpjdwfqi7SytXhycJk/s9+xuMjd0S2+JkPjY rd5UG/vp/HIEaj4hbZsGHVAy8c3Yu+Cm7XWT8+QQ2DF+Kj9Tzx2MvQbXjmnCbZ9jm0nr 0ZpW2lOSVide13tBhiwo09uHb7/VLcgnsK05B46ZypCSrXhT+caT6Pnk7P+/Qm9Hl0DC cayS5bHHXtBVMpUAGNKAqqfR014kk4B/JTl3IJqDOFVB+hbOvPywpnVJ0ikrdIy92dLG 923Q==
MIME-Version: 1.0
Received: by 10.50.5.205 with SMTP id u13mr16502362igu.37.1354037073990; Tue, 27 Nov 2012 09:24:33 -0800 (PST)
Received: by 10.231.10.204 with HTTP; Tue, 27 Nov 2012 09:24:33 -0800 (PST)
In-Reply-To: <7C52FDEBC843C44DBAF2CA6A30662C6D0D2927@xmb-aln-x04.cisco.com>
References: <CAC8QAcfaFSJxSSM4geFbWSV-fLkrM6Ry93PjXmfgv94A0rksoQ@mail.gmail.com> <7C52FDEBC843C44DBAF2CA6A30662C6D0D2927@xmb-aln-x04.cisco.com>
Date: Tue, 27 Nov 2012 11:24:33 -0600
Message-ID: <CAC8QAcf9WZPZrUopghQW6r8BOuBBpeUuRB0c_A8uj_6XhKSkDA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "Rajeev Koodli (rkoodli)" <rkoodli@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "multimob@ietf.org" <multimob@ietf.org>, "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
Subject: Re: [multimob] Fast Handover Solutions
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
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 17:24:35 -0000

Hi Rajeev,

I checked again.
The charter item is about PMIPv6 handover optimizations, not on fast handover.

The draft name should have been handover-optimizations not fast-handover.

Sorry about that because I had suggested this draft name.

Without realizing that it would cause so much trouble.

I repeat here again, the draft title did not change and the draft
content is reflected in the title. This is the most important thing.


Regards,

Behcet

On Mon, Nov 26, 2012 at 6:07 PM, Rajeev Koodli (rkoodli)
<rkoodli@cisco.com> wrote:
>
>
> 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
>