Re: [MEXT] Draft binding-revocation-12 "mobile node operation"
"Ahmad Muhanna" <amuhanna@nortel.com> Thu, 17 September 2009 20:44 UTC
Return-Path: <AMUHANNA@nortel.com>
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 9BF6A3A6AF1 for <mext@core3.amsl.com>; Thu, 17 Sep 2009 13:44:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.623
X-Spam-Level:
X-Spam-Status: No, score=-6.623 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 ODJzu4m2cm-H for <mext@core3.amsl.com>; Thu, 17 Sep 2009 13:44:34 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id D0E883A67AE for <mext@ietf.org>; Thu, 17 Sep 2009 13:44:07 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n8HKiU520069; Thu, 17 Sep 2009 20:44:30 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA37D7.9868DA2F"
Date: Thu, 17 Sep 2009 15:44:03 -0500
Message-ID: <C5A96676FCD00745B64AE42D5FCC9B6E204B8880@zrc2hxm0.corp.nortel.com>
In-Reply-To: <C24C03AE7348E44FB76B34B5D4ED44F503AB2BE3@esealmw106.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Draft binding-revocation-12 "mobile node operation"
Thread-Index: Aco3q27g5BjFBbVvRY6nAeEmSxTcrQALAGiw
References: <C24C03AE7348E44FB76B34B5D4ED44F503AB2BE3@esealmw106.eemea.ericsson.se>
From: Ahmad Muhanna <amuhanna@nortel.com>
To: Yuri Ismailov <yuri.ismailov@ericsson.com>
Cc: mext@ietf.org
Subject: Re: [MEXT] Draft binding-revocation-12 "mobile node operation"
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 20:44:35 -0000
Yuri, What you are talking about is related to flow revocation and I believe the chairs mentioned earlier that need to be addressed later on . possibly as an extension to this specification. Regards, Ahmad ________________________________ From: Yuri Ismailov [mailto:yuri.ismailov@ericsson.com] Sent: Thursday, September 17, 2009 10:28 AM To: Muhanna, Ahmad (RICH1:2H10) Cc: mext@ietf.org Subject: Draft binding-revocation-12 "mobile node operation" Ahmad, I think that "mobile node operation" chapter in the draft requires some extension, which would explicitely state one or more possible actions of the MN after sending BRA. In the case if NOT all bindings were revoked an MN still has an option to transfer flows to the remaining, still "active" bindings, However, if all bindings were revoked, then, according to my understanding, after a BRA sent by an MN, the MN will end up in the state when it cannot send or recieve traffic due to the revoked bindings. Transition into this state is actually triggered by HA or LMA by sending BRI. What is the way out of this state? I did not find any hints about that in the document. I think that this is important to specify MN's actions when it ends up in such state. Does that sound reasonable? Regards Yuri
- [MEXT] Draft binding-revocation-12 "mobile node o… Yuri Ismailov
- Re: [MEXT] Draft binding-revocation-12 "mobile no… Ahmad Muhanna
- Re: [MEXT] Draft binding-revocation-12 "mobile no… Behcet Sarikaya