Re: [MEXT] Home-Agent-Switch-Message andBinding-Revocation-Indication-Message
"Vijay Devarapalli" <vijay@wichorus.com> Tue, 23 December 2008 23:02 UTC
Return-Path: <mext-bounces@ietf.org>
X-Original-To: monami6-archive@megatron.ietf.org
Delivered-To: ietfarch-monami6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 259A33A6B31;
Tue, 23 Dec 2008 15:02:02 -0800 (PST)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id EFB843A6B31
for <mext@core3.amsl.com>; Tue, 23 Dec 2008 15:02:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
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 ak6Bi9oEIDmr for <mext@core3.amsl.com>;
Tue, 23 Dec 2008 15:02:00 -0800 (PST)
Received: from outbound.mse15.exchange.ms (outbound.mse15.exchange.ms
[216.52.164.185])
by core3.amsl.com (Postfix) with ESMTP id 20FF43A69D8
for <mext@ietf.org>; Tue, 23 Dec 2008 15:01:59 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 23 Dec 2008 18:01:46 -0500
Message-ID: <DE33046582DF324092F2A982824D6B03050058C7@mse15be2.mse15.exchange.ms>
In-Reply-To: <D3CFEF84287B46408A7F0405EE7C5457019E82AF@corvette.eu.tieto.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MEXT] Home-Agent-Switch-Message
andBinding-Revocation-Indication-Message
Thread-Index: AcllBQ4e4S/LZRz7RCOTXd8Ui3ClCgATU7tg
From: "Vijay Devarapalli" <vijay@wichorus.com>
To: <Christian.Kaas-Petersen@tieto.com>,
<mext@ietf.org>
Subject: Re: [MEXT] Home-Agent-Switch-Message
andBinding-Revocation-Indication-Message
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>,
<mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>,
<mailto:mext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org
Hi, > -----Original Message----- > From: mext-bounces@ietf.org [mailto:mext-bounces@ietf.org] On > Behalf Of Christian.Kaas-Petersen@tieto.com > Sent: Tuesday, December 23, 2008 5:48 AM > To: mext@ietf.org > Subject: [MEXT] Home-Agent-Switch-Message > andBinding-Revocation-Indication-Message > > Is there a difference to a mobile node receiving an RFC 5142 specified > > Home Agent Switch Message > # of addresses = 0 > > and receiving a draft-ietf-mext-binding-revocation specified > > Binding Revocation Indication Message > > The packets are different and the responses will be > different, but isn't it true the net result in both cases is > the same: the home agent will no longer support the mobile > node so the mobile node is left alone in the world? Yes, there is no difference. Vijay _______________________________________________ MEXT mailing list MEXT@ietf.org https://www.ietf.org/mailman/listinfo/mext
- [MEXT] Home-Agent-Switch-Message and Binding-Revo… Christian.Kaas-Petersen
- Re: [MEXT] Home-Agent-Switch-Message andBinding-R… Vijay Devarapalli