Hi, Mohana: I read your I-D about bitmap based PBU and would like to have some comments as follows: It seems to me the Bulk PBU using Bitmap is one robust header/packet compression mechanism. in other words, Bulk PBU can be further compressed or optimized using Bitmap which saves not only signaling but also packet size comparing with Bulk re-registration mechanism described in draft-premec-netlmm-bulk-re-registration-03. But what I am still difficult to understand is in which situation or scenario the Bitmap based Bulk PBU will be utitlized instead of Bulk re-registration ? As you said in the I-D, The PBU originating from the MAG can be of different types such as initial registration PBU, handoff PBU, re-registration PBU and de-registration PBU. If the PBU originating from the MAG is initial registraion PBU, how can you guarantee that MAG initializing Bulk PBU can be attached by several Mobile nodes at the same time during initial registration for all these mobile nodes? Without attachment by several mobile nodes simutanesouly, how does the MAG construct bitmap base Bulk PBU packet? I think the same applies to handoff PBU. If the PUB originating from the MAG is re-registraion PBU, I am afraid that the most efficient or optimized way is to only carry Bulk Set ID or grouped ID in the re-registration PBU, the other mobility options is not necessary to be included, because LMA has already maintained binding for all these mobile nodes pertained to Bulk Set ID or grouped ID. In this scenario, if we still choose to use bitmap based PBU, more packet size will be costed for bitmap option included. The same applies to de-registration PBU. Therefore the only two pratical scenarios occuring to me instead of using Bulk re-registration are a. Bitmap based Bulk PBU can be used when several MNs ask to be added into Bulk re-registration set. b. MAG sending a Bitmap based bulk PBU containing several Bulk Set IDs created during the Bulk re-registration and several other Individual mobile nodes who would like to be added to one specific bulk re-registration set. In these two scenarios, bitmap based PBU can be used to compress packet size of PBU that includes several MNs who ask to join several bulk re-registration sets by avoiding duplicate mobility options for different MNs. Am I right? Regards! -Qin ----- Original Message ----- From: "Mohana Jeyatharan" <Mohana.Jeyatharan at sg.panasonic.com> To: <netext at ietf.org> Sent: Friday, October 16, 2009 9:13 AM Subject: [netext] FW: I-DAction:draft-jeyatharan-netext-pmip-bulkpbu-bitmap-00.txt Hi all, This ID is highlighting a bulk PBU optimization approach using bit maps. This approach can be used to send multiple PBU signals of any type in a combined manner using bitmaps. This approach can work along with the MN group ID approach as well as highlighted in this draft. Please see. Comments are appreciated. Thanks. BR, Mohana -----Original Message----- From: i-d-announce-bounces at ietf.org [mailto:i-d-announce-bounces at ietf.org] On Behalf Of Internet-Drafts at ietf.org Sent: Friday, October 16, 2009 9:00 AM To: i-d-announce at ietf.org Subject: I-D Action:draft-jeyatharan-netext-pmip-bulkpbu-bitmap-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Bulk PBU using Bitmaps Author(s) : M. Jeyatharan, C. Ng Filename : draft-jeyatharan-netext-pmip-bulkpbu-bitmap-00.txt Pages : 8 Date : 2009-10-15 In Proxy Mobile Internet Protocol version 6 (PMIPv6), each mobile node attached to a mobile access gateway (MAG) requires separate signaling. This might result in excessive network signaling if there a large number of mobile nodes attached to a MAG. In this draft we outline a bulk PBU optimization approach based on bitmap, in order to reduce the signaling load tied to numerous PBUs originating at the same time. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-jeyatharan-netext-pmip-bulkpbu -bitmap-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. -------------------------------------------------------------------------------- > _______________________________________________ > netext mailing list > netext at ietf.org > https://www.ietf.org/mailman/listinfo/netext >
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.