Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop-transient-bce-pmipv6
Marco Liebsch <marco.liebsch@neclab.eu> Tue, 14 September 2010 07:24 UTC
Return-Path: <Marco.Liebsch@neclab.eu>
X-Original-To: mipshop@core3.amsl.com
Delivered-To: mipshop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BCEBE3A68E0 for <mipshop@core3.amsl.com>; Tue, 14 Sep 2010 00:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=0.299, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yBbGvqegy49j for <mipshop@core3.amsl.com>; Tue, 14 Sep 2010 00:24:43 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id 28F293A68E7 for <mipshop@ietf.org>; Tue, 14 Sep 2010 00:24:43 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id C59EB2C0001B6; Tue, 14 Sep 2010 09:25:08 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office.hd)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TIhb6+pCfA-u; Tue, 14 Sep 2010 09:25:08 +0200 (CEST)
Received: from ENCELADUS.office.hd (Enceladus.office.hd [192.168.24.52]) by smtp0.neclab.eu (Postfix) with ESMTP id A87B22C0001B0; Tue, 14 Sep 2010 09:24:43 +0200 (CEST)
Received: from [10.1.6.32] (10.1.6.32) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.218.12; Tue, 14 Sep 2010 09:23:39 +0200
Message-ID: <4C8F22F3.4060005@neclab.eu>
Date: Tue, 14 Sep 2010 09:23:31 +0200
From: Marco Liebsch <marco.liebsch@neclab.eu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Vijay Devarapalli <dvijay@gmail.com>
References: <4C8927B2.1030000@gmail.com> <4C89EE49.4050004@neclab.eu> <4C8A0FA7.7060308@piuha.net> <4C8AAC0C.5020204@gmail.com> <4C8E2B36.7050308@neclab.eu> <4C8E9C38.2030408@gmail.com>
In-Reply-To: <4C8E9C38.2030408@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.6.32]
Cc: "Laganier, Julien" <julienl@qualcomm.com>, mipshop@ietf.org, "BLUME, Oliver" <Oliver.Blume@alcatel-lucent.de>
Subject: Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop-transient-bce-pmipv6
X-BeenThere: mipshop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <mipshop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mipshop>
List-Post: <mailto:mipshop@ietf.org>
List-Help: <mailto:mipshop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2010 07:24:47 -0000
Am 13.09.2010 23:48, schrieb Vijay Devarapalli: > On 9/13/10 6:46 AM, Marco Liebsch wrote: >> Hi Vijay, >> >> please find some text for a revived section 4.7 MN Operation below. >> Text in section 4.3.1 could then refer to this new section 4.7 to >> link context. >> >> 4.7. MN operation >> >> For single-radio handover, this specification does not require any >> extended mode of operation on the MN when compared to [RFC5213]. > > Replace the above with > > For a single-radio handover, this specification does not require > any additional functionality on the mobile node, when compared to > [RFC 5213]. ok > >> During dual-radio handover, the MN benefits most from the transient >> BCE extension to PMIPv6 when it is able to keep communication on the >> previous interface while it is setting up its handover target >> interface with the configuration context which has been received as a >> result of the new interface's attachment to the nMAG. Various >> techniques enable support for such operation, e.g. the use of a >> virtual interface on top of physical radio interfaces or >> implementation specific extensions to the MN's protocol stack. >> Details about how to enable such make-before-break support on the MN >> are out of scope of this document. > > Looks ok. BTW, I think its ok to include the reference to the NETEXT > draft for the virtual interface (see Julien's email). ok. Will post a version 8 then with that text and the reference. marco > > Vijay > >> >> >> marco >> >> >> Vijay Devarapalli wrote: >>> On 9/10/10 3:59 AM, Jari Arkko wrote: >>>> Is some document change needed? >>> >>> Yes, IMO. Section 4.3.1 talks about the nMAG creating a transient BCE >>> only if it knows the MN supports transient BCE. Two issues with this. >>> >>> 1. If its a single radio handover, nothing needs to be supported on >>> the MN. Just whatever is needed according to RFC 5213. >>> >>> 2. For a dual radio handover, to get the true benefit from transient >>> BCE, the MN needs to be able to receive packets on two interfaces at >>> the same time for a short while. If it does not do this, transient BCE >>> would still work, and the MN does benefit, but there will be some >>> packet loss. >>> >>> This is not really captured in the draft. >>> >>> For the actual text changes, it is going to be hard for me to suggest >>> text changes since its been a year since I read the draft. I have to >>> go through it again. Marco would probably be able to come up with text >>> changes much more quickly. >>> >>> Perhaps we should add a section on the mobile node support for >>> transient BCE and explain clearly what needs to be supported on the >>> mobile node. >>> >>> Vijay >> >
- [Mipshop] Section 4.3.1 of draft-ietf-mipshop-tra… Vijay Devarapalli
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Marco Liebsch
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Jari Arkko
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Vijay Devarapalli
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Laganier, Julien
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Vijay Devarapalli
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Laganier, Julien
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Marco Liebsch
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Marco Liebsch
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Laganier, Julien
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Marco Liebsch
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Marco Liebsch
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Laganier, Julien
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Marco Liebsch
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Laganier, Julien
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Vijay Devarapalli
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Jari Arkko
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Marco Liebsch
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Marco Liebsch
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Marco Liebsch
- Re: [Mipshop] Section 4.3.1 of draft-ietf-mipshop… Jari Arkko