RE: [Seamoby] Revised Section 4 of CAR issues draft
"Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se> Wed, 16 January 2002 15:49 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11903 for <seamoby-archive@odin.ietf.org>; Wed, 16 Jan 2002 10:49:25 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA05776; Wed, 16 Jan 2002 10:34:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA05743 for <seamoby@optimus.ietf.org>; Wed, 16 Jan 2002 10:34:02 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11362 for <seamoby@ietf.org>; Wed, 16 Jan 2002 10:33:43 -0500 (EST)
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32]) by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0GFXhJ28688 for <seamoby@ietf.org>; Wed, 16 Jan 2002 16:33:43 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Wed Jan 16 16:33:26 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19) id <Z1HXK58Y>; Wed, 16 Jan 2002 16:33:42 +0100
Message-ID: <4DA6EA82906FD511BE2F00508BCF053801C4C20D@Esealnt861.al.sw.ericsson.se>
From: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>
To: 'Hemant Chaskar' <hchaskar@hotmail.com>, seamoby@ietf.org
Subject: RE: [Seamoby] Revised Section 4 of CAR issues draft
Date: Wed, 16 Jan 2002 16:33:21 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
I'm happy with the new modifications. Hesham > -----Original Message----- > From: Hemant Chaskar [mailto:hchaskar@hotmail.com] > Sent: Wednesday, January 16, 2002 3:57 AM > To: seamoby@ietf.org > Subject: [Seamoby] Revised Section 4 of CAR issues draft > > > Hi, > > Here is the revised text for Section 4 of CAR discovery > issues draft. The > text has been finetuned. I hope that it is now clear > enough. If there are no > more concerns on Section 4, we can submit the problem > statement draft with > this text for Section 4, to IESG. > > Hemant > > -------------------------------snip------------------------- > --------- > > 4. APPROACHES TO CANDIDATE ACCESS ROUTER DISCOVERY > > In this section, we describe three approaches to CAR discovery, > namely the Anticipated CAR Discovery (discovery prior to > handoff), Dynamic > CAR > Discovery (discovery at the time of handoff) and Hybrid CAR > Discovery. > > 4.1 Anticipated CAR Discovery > > In Anticpated CAR Discovery, CAR discovery is performed at some > point prior to the MN performing a handoff. This can be performed in > a number of ways and with various entities particpating in > the process. > One illustrative method for Anticipated CAR Discovery is > given below. > > In this method, an AR currently serving an MN can identify > a set of CARs for > the MN's handoff, at some point prior to handoff. This > information is then > available at the time of handoff as input to the TAR > Selection Algorithm. > Another > input to the TAR Selection Algorithm may be the preferences > expressed by the > MN > prior to the handoff, or preferences enforced by the > administrative control. > At > the time of handoff, it may only be required to provide > input to the TAR > Selection > Algorithm about the reachability of neighboring ARs from > the MN. This > reachability > information is usually in the form of the identity of the > AP to which the MN > can listen to, and the current AR has to resolve this AP > identity to the > GAAR's IP address. > > The advantage of Anticipated CAR Discovery is that the > handoff can be > executed > quickly because much of the information needed by the TAR Selection > Algorithm > is collected in advance of handoff. > > Anticipated CAR Discovery is depicted in Figure 1. > > > > ----------------------------------------------------------------- > | All routers > | > | | Discovery of ARs whose > coverage | > | | areas overlap (GAARs) with > that of | > | v the current AR > | > | Local map of GAARs at current AR > | > | | > | > | | Capability identification > | > | v > | > | CARs for MN's handoff identified at current AR > | > | | > | > > --------------------------|-------------------------------------- > | > | Predefined preferences of the MN > AR Reachability | and administrative preferences > for the MN | > | | | > v v v > TAR Selection Algorithm executed at the time of > handoff to determine unique TAR for MN's handoff > > Figure 1: Anticipated CAR Discovery > > > 4.2 Dynamic CAR Discovery > > In Dyanmic CAR discovery, CAR discovery is performed at the > time the MN is > about to undergo handoff. Again, this can be performed in a > number of ways > and with various entities particpating in the process. One > illustrative > method > for Dynamic CAR Discovery is given below. > > According to this method, an MN dynamically obtains > information about the > available > ARs for handoff, along with their capabilities. This is > done after the > handoff trigger > is generated. When the MN detects an AR that has > capabilities matching its > preferences, > the MN may notify the currently serving AR to perform a > handoff to this AR > using one or > more of the seamless handoff protocols. The advantage of > this method is that > the MN > has fine-grained control over the TAR selection. However, > this method > generates more > radio traffic during the CAR discovery step. This is > because capability > information is > sent to the MN over the air. Also, it is required that the > MN can receive > IP-level > capability information from the GAARs and negotiate > requirements with the > GAARs, while > still being connected to the current AR. > > > Dynamic CAR Discovery is shown in Figure 2. > > > > -------------------------------------------------------------- > | > | > | GAARs identified at handoff time > | > | | > | > | | Capability > identification | > | | > | > | v > | > | CARs for MN's handoff identified > | > | | > | > > ---------------------------|---------------------------------- > | > | TAR selection at the > | time of handoff > v > Unique TAR identity > > Figure 2: Dynamic CAR Discovery > > > 4.3 Hybrid CAR Discovery > > In practice, a hybrid of the Anticipated and Dynamic CAR discovery > approaches > may be used. For example, in the hybrid approach, the GAAR > discovery and > much > of the capability identification may be performed prior to > handover, while > the > remaining capability identification may happen during the > handover process. > But, > there are other alternatives too. > > _________________________________________________________________ > Chat with friends online, try MSN Messenger: http://messenger.msn.com _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby
- [Seamoby] Revised Section 4 of CAR issues draft Hemant Chaskar
- RE: [Seamoby] Revised Section 4 of CAR issues dra… Hesham Soliman (ERA)
- RE: [Seamoby] Revised Section 4 of CAR issues dra… Govind Krishnamurthi