Re: [MEXT] Processing of BRI (Binding Revocation) by MAG

"Ahmad Muhanna" <amuhanna@nortel.com> Mon, 19 January 2009 14:11 UTC

Return-Path: <mext-bounces@ietf.org>
X-Original-To: mip6-archive@megatron.ietf.org
Delivered-To: ietfarch-mip6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FB883A6B54; Mon, 19 Jan 2009 06:11:03 -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 321F428C113; Mon, 19 Jan 2009 06:11:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.452
X-Spam-Level:
X-Spam-Status: No, score=-6.452 tagged_above=-999 required=5 tests=[AWL=0.146, 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 MaJthwaI0Atc; Mon, 19 Jan 2009 06:11:00 -0800 (PST)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id DFF253A67E5; Mon, 19 Jan 2009 06:10:59 -0800 (PST)
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 n0JE6p907463; Mon, 19 Jan 2009 14:06:51 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 19 Jan 2009 08:10:27 -0600
Message-ID: <C5A96676FCD00745B64AE42D5FCC9B6E1CA92CFF@zrc2hxm0.corp.nortel.com>
In-Reply-To: <200901191212.n0JCCdxA016217@ricky.india.internal.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Processing of BRI (Binding Revocation) by MAG
Thread-Index: Acl6MbWiLAZ2wPBbRNyWgrShkUmdqQADGOwA
References: <200901191212.n0JCCdxA016217@ricky.india.internal.net>
From: Ahmad Muhanna <amuhanna@nortel.com>
To: Magesh Shanmugam <mshanmugam@intellinet-india.com>
Cc: netlmm@ietf.org, mext@ietf.org
Subject: Re: [MEXT] Processing of BRI (Binding Revocation) by MAG
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: multipart/mixed; boundary="===============1684729884=="
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org

 

	Ahmad
	 
	I have a query regarding the handling of Binding Revocation by
MAG for individual binding session.  
	Following is the scenario:
	 
	Scenario:
	 
	1. Proxy Mobile Initial Registration, MAG sends PBU to LMA with
HNP option set to ALL_ZERO for MN 1.
	2. LMA in turn sends back PBA with 3 HNP(s) assigned to MN 1 and
updates Binding Cache Entry.
	3. MAG updates Binding Update List entry and sends Router
Advertisement to the MN with all the 
	    prefixes and prefix lifetime. 
	    Note: MAG considers the prefix lifetime as binding lifetime
and starts Binding Lifetime timer.
	4. Bi-directional tunnel is established between MAG and LMA.  
	5. Prefix Route(s) are created for all the prefixes at MAG.
	6. MN 1 gets one IP Address from the alloted 3 HNP(s).
	7. LMA sends BRI message with one HNP (out of the alloted 3
HNPs) with revoke trigger as 
	   "ADMINISTRATIVE REASON".
	 
	After step 7, when MAG receives BRI message with only one HNP
and MN-ID:
	 
	Queries:
	 
	1. Will MAG stop the binding lifetime timer (started after
binding session establishment), due to the
	    received BRI message?
	2. Will MAG delete the complete Binding Update List maintained
for the MN (MN 1) or will it delete
	    only the corresponding HNP entry from the BUL and send RA
message to MN 1 (eventhough
	    the IP Address used by MN is not from the HNP received in
BRI message)?  If it deletes only the
	    corresponding HNP entry, what will happen to the Binding
Lifetime timer? 
	 
	[Ahmad]
	If the LMA assigned 3 HNP for MN1, then if the LMA would like to
revoke all of the HNPs, the LMA have one of the following options:
	 
	1. Send BRI with MN-ID option ONLY. This means that all HNPs are
revoked, or
	2. Send a BRI with MN-ID and all HNPs.
	 
	Although, the draft recommend Number 1 BUT does not prevent No.
2.
	 
	On the other hand, if the LMA sends a BRI with MN-ID and a
single HNP, then the MAG MUST consider the revocation of that single HNP
and MUST NOT remove the MN1 from the BUL.
	 
	Hope this help.
	 
	Regards,
	Ahmad 
	 
	Thanks
	S Magesh

_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www.ietf.org/mailman/listinfo/mext