[MEXT] Processing of BRI (Binding Revocation) by MAG
"Magesh Shanmugam" <mshanmugam@intellinet-india.com> Mon, 19 January 2009 12:25 UTC
Return-Path: <mext-bounces@ietf.org>
X-Original-To: nemo-archive@megatron.ietf.org
Delivered-To: ietfarch-nemo-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D2A303A6911; Mon, 19 Jan 2009 04:25:08 -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 C8D833A695B; Mon, 19 Jan 2009 04:25:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.085
X-Spam-Level: **
X-Spam-Status: No, score=2.085 tagged_above=-999 required=5 tests=[AWL=-0.079, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
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 P75R+hzWI9Vg; Mon, 19 Jan 2009 04:25:05 -0800 (PST)
Received: from ricky.india.internal.net (unknown [59.145.147.70]) by core3.amsl.com (Postfix) with ESMTP id 273F33A6821; Mon, 19 Jan 2009 04:25:03 -0800 (PST)
Received: from Magesh (magesh.india.internal.net.16.172.in-addr.arpa [172.16.8.41] (may be forged)) by ricky.india.internal.net (8.12.10/8.12.10) with ESMTP id n0JCCdxA016217; Mon, 19 Jan 2009 17:42:39 +0530
Message-Id: <200901191212.n0JCCdxA016217@ricky.india.internal.net>
From: Magesh Shanmugam <mshanmugam@intellinet-india.com>
To: 'Ahmad Muhanna' <amuhanna@nortel.com>
Date: Mon, 19 Jan 2009 18:00:27 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: Acl6MbWiLAZ2wPBbRNyWgrShkUmdqQ==
X-Cyberoam-Version: 9.5.4.86
X-Cyberoam-smtpxy-version: 0.0.4.2
X-Cyberoam-AV-Status: Clean
X-Cyberoam-Proto: SMTP
X-Cyberoam-AV-Policy: None
X-Cyberoam-AS-Policy: Global Spam Policy
Cc: netlmm@ietf.org, mext@ietf.org
Subject: [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="===============1312599354=="
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? Thanks S Magesh
_______________________________________________ MEXT mailing list MEXT@ietf.org https://www.ietf.org/mailman/listinfo/mext
- [MEXT] Processing of BRI (Binding Revocation) by … Magesh Shanmugam
- Re: [MEXT] Processing of BRI (Binding Revocation)… Ahmad Muhanna
- Re: [MEXT] Processing of BRI (Binding Revocation)… Magesh Shanmugam
- Re: [MEXT] Processing of BRI (Binding Revocation)… Ahmad Muhanna