[Seamoby] IP Paging ]Framework discussion

[Behcet Sarikaya <[e-mail]>]

Jim,
   I went thru the emails that I missed on the list during holiday 
period. You referred to our work several times, do I have right to rebuttal?
-James Kempf said in his mail to Yoshi:
--Something like the time-slotted
--paging support in draft-sarikaya is what is needed in
--the final protocol.
We have included a shortedned version of time-slotted paging in the 
LAHAP draft. You seem to ignore the LAHAP draft always, why? (I think 
the answer is implicit in your other mail, parts of it I am copying here)
-James Kempf said in his mail:
--There must be a TA per paging area, not per subnet. In the case of
--L2 paging areas, the TA is identified as the entity that is taking
--the L2 paging area update and coverting it into an L3 paging
--area update. So it plays an important role there.

The movement at IP level is based on the subnet so if we are going to 
track movement then TA functionality is needed in every subnet. If every 
subnet is a L3 paging area then this becomes what you said.

-James Kempf said in his mail:
--I view the Paging Agent as the entity that initiates the actual page
--directly
--to the MN. This may be an L2 page or it may be an L3 page. I view it 
--as similar to the last hop router.
The last hop router can take part in paging in communication with the 
Paging Agent. In case L3 paging area contains several IP subnets, then 
don't you need an upper level entity to take care of the paging process?



We have been discussing these issues with Hideaki from Fujitsu whom I 
never met, several months back, I am enclosing the email from Seamoby 
archive.

-------- Original Message --------
Subject: [seamoby] Re: [Fwd: questions on LAHAP draft]
Date: Wed, 07 Nov 2001 14:10:31 -0500
From: Behcet Sarikaya <[e-mail]>
To: [e-mail]
CC: seamoby <[e-mail]>
References: <[e-mail]>

Hi Hideaki,
      L2 paging areas are what we have now in public cellular networks.
Our
protocols (Lahap and mipv6hp) are designed to work with them and
therefore have
a minimum L3 paging protocol such as registration. In this case we do
not use L3
paging areas because there is no need.
      L3 paging areas need to be set up in a 4G type of network where
there are
no L2 paging areas. In this case our protocols define maximum L3 paging
protocol
operations because all IP paging need to be performed in Layer 3, except
on-link
paging.
     On-link paging such as paging channel on cellular networks is a nice
feature
to have from the point of view of L3 paging. If there is on-link paging
support,
then our protocols exploit it to the maximum advantage of L3 paging,
together
with L3 paging areas. If there is no onlink paging support then our
protocols
define time-slot based on-link paging operations.
      Regarding the triggers, the triggers are designed to be used with
L2 paging
areas.
In case of Layer 3 paging areas, the paging area ID is multicast in the
router
advertisements which are Layer 3 messages. So how the host or MN get
this info
in dormant mode depends on how on-link paging is supported. I guess we
need to
do more work on this, it was good you raised this issue. Thanks.

   See you in Salt Lake.


Hideaki Takusagawa wrote:

 > hi Behcet,
 >
 > thanks for the reply.
 > i did check for that mail on Oct 5 but it wasn't there,
 > there must have been some problems in redirecting mail
 > between my 2 accounts.... sorry about that.
 >
 > >   In the case when Layer 3 paging areas are supported,
 > > whenever MN changes paging area, TA in the new subnet is notified using
 > > layer 2 trigger. If the new TA is in the same layer 3 paging area, 
MN does
 > > not perform any registration.
 >
 > how does the MN know of the L3 paging area,
 > i was under the impression that the trigger was only
 > to inform of the L2 paging area.
 >
 > > Since the paging request sent by PA is multicast in the layer 3
 > > paging area, the new TA also receives the paging request.
 >
 > yep, i understand now, if MN has moved within a L3 paging area, IP paging
 > goes
 > DMA -> first TA in L3 paging area that MN was under -> DMA -> PA -> 
current
 > TA. -> Host
 >
 > but this requires DMA to map L2 paging area to a PA that handles
 > L3 paging area right?
 > (that didn't sound right to me before....)
 >
 > and what about the case when MN is still under that first TA in
 > in the L3 paging area, couldn't there be some shortcuts here?
 >
 > hideaki
 >
 >
 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 > Hideaki Takusagawa
 > Network Systems Laboratories     FUJITSU LABORATORIES LTD.
 > Phone: (Ext) 044-754-2786 (Int) 7112-6146 Fax: [phone]
 > Email: [e-mail]


-- 
Behcet


_______________________________________________
Seamoby mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/seamoby