From owner-seamoby@diameter.org  Thu Mar  1 04:00:38 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA28474
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 04:00:37 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f218Qj319531
	for seamoby-list; Thu, 1 Mar 2001 00:26:45 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x3.nokia.com (mgw-x3.nokia.com [131.228.20.26])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f218Qgo19526
	for <seamoby@cdma-2000.org>; Thu, 1 Mar 2001 00:26:42 -0800
Received: from esvir07nok.ntc.nokia.com (esvir07nokt.ntc.nokia.com [172.21.143.39])
	by mgw-x3.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f217anu03691
	for <seamoby@cdma-2000.org>; Thu, 1 Mar 2001 09:36:49 +0200 (EET)
Received: from esebh12nok.ntc.nokia.com (unverified) by esvir07nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5205f6c1e8ac158f27d32@esvir07nok.ntc.nokia.com>;
 Thu, 1 Mar 2001 09:36:15 +0200
Received: by esebh12nok with Internet Mail Service (5.5.2652.78)
	id <FPD9L8AT>; Thu, 1 Mar 2001 09:36:15 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680AAE1@eseis04nok>
From: john.loughney@nokia.com
To: pcalhoun@nasnfs.eng.sun.com, john.loughney@nokia.com
Cc: seamoby@cdma-2000.org
Subject: RE: MM Draft v1 WAS: [seamoby] Context Transfer and Paging
Date: Thu, 1 Mar 2001 09:36:13 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Pat,

> Great idea. How about Wednesday lunch?

Works for me.  

John


From owner-seamoby@diameter.org  Thu Mar  1 04:01:35 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA28494
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 04:01:35 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f218VDQ19556
	for seamoby-list; Thu, 1 Mar 2001 00:31:13 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f218VAo19551
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 00:31:11 -0800
Received: from esvir08nok.nokia.com (esvir08nokt.ntc.nokia.com [172.21.143.40])
	by mgw-x4.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f217geR03071
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 09:42:40 +0200 (EET)
Received: from esebh12nok.ntc.nokia.com (unverified) by esvir08nok.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5205fad196ac158f28123@esvir08nok.nokia.com>;
 Thu, 1 Mar 2001 09:40:42 +0200
Received: by esebh12nok with Internet Mail Service (5.5.2652.78)
	id <FPD9L8NN>; Thu, 1 Mar 2001 09:40:42 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680AAE2@eseis04nok>
From: john.loughney@nokia.com
To: james.kempf@sun.com, seamoby@diameter.org
Subject: RE: [seamoby] Yet Another BOF?
Date: Thu, 1 Mar 2001 09:40:39 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi James,

> With all due respect to the MM design team and to John, the 
> draft editor, the draft did not present such a clear case (at 
> least, not the 00 draft, I  have yet to read the 01 draft), at 
> least not to me. 

Not a problem.  I think many were not convinced by the v00 draft.
v01 of the MM draft tries to clarify some issues, but I do 
think more is needed.  

> If the mobile IP proponents are making these statements, then it is 
> incumbent upon the MM proponents to say: "Oh yeah? Show me how!". 
> If they can't come up with a solution, and a sketch of an MM solution 
> is simpler, then MM is clearly the way to go. The solution doesn't have 
> to be complete, even a simple description is usually enough to see 
> whether the MIP solution would be more complex or compromise 
> particular requirements. However, if in the end, the mobile IP 
> solution is good enough, in the sense that it satisfies the 
> requirements, and the working group agrees, 
> then its no good going off in a huff and accusing the mobile 
> IP proponents  of stonewalling.

Agreed.  My impression is that the draft should now focus
on some requirents which any MM protocol should fufill.  This
is something that should go into the v02 draft.

br,
John


From owner-seamoby@diameter.org  Thu Mar  1 04:24:12 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA28672
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 04:24:11 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f218kwj19597
	for seamoby-list; Thu, 1 Mar 2001 00:46:58 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f218kto19592
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 00:46:55 -0800
Received: from esvir06nok.ntc.nokia.com (esvir06nokt.ntc.nokia.com [172.21.143.38])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f217uTf09985
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 09:56:29 +0200 (EET)
Received: from esebh03nok.ntc.nokia.com (unverified) by esvir06nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T52060934bbac158f26129@esvir06nok.ntc.nokia.com>;
 Thu, 1 Mar 2001 09:56:24 +0200
Received: by esebh03nok with Internet Mail Service (5.5.2652.78)
	id <FTL1R1TC>; Thu, 1 Mar 2001 09:56:24 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680AAE3@eseis04nok>
From: john.loughney@nokia.com
To: KAtwal@zucotto.com, seamoby@diameter.org
Subject: SeaMoby, MANET, MIP & the Universe! WAS: [seamoby] Yet Another BO
	F?
Date: Thu, 1 Mar 2001 09:56:20 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Kulwinder,

> Why 'MUST' SeaMoby be confined by MANET/MIP?  
> If SeaMoby does its job there will be no need for MANET in 
> local mobility.
> If SeaMoby does its job there will be no need for MIP in 
> local mobility.

The 'MUST' in the section you quoted stated: 	

   Therefore, SeaMoby MUST be able to co-exist gracefully 
   with any MANET solutions algorithm that does become standardized.

because I am not going to re-write all of MANET & all of MIP
for all of the Internet.  Part of SeaMoby is focused on 
MM and I do not want to expand that scope.  Also, I favor
reuse whenever possible - creating new protocols for the
sake of new protocols is not a good idea.  Of course, we
do need to examine existing solutions & if they are not
sufficient, then that would be a good reason to do something
new.

I still strongly feel that SeaMoby may apply certain parts
of MIP & MANET in a novel way to solve these problems.

> The title of the section says ,"Comparion", but states a mandatory
> requirement.
> By making MANET a 'MUST' requirement for Seamoby is a sure 
> way to see that Seamoby is never deployed.

Nope, MANET is not a MUST requirement, but stating if MANET
& SeaMoby overlap/interact, they MUST do so gracefully.

br,
John


From owner-seamoby@diameter.org  Thu Mar  1 08:42:26 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA03374
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 08:42:25 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21D0R120397
	for seamoby-list; Thu, 1 Mar 2001 05:00:27 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from c007.snv.cp.net (c007-h000.c007.snv.cp.net [209.228.33.206])
	by charizard.diameter.org (8.10.0/8.10.0) with SMTP id f21D0No20389
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 05:00:24 -0800
Received: (cpmta 1309 invoked from network); 1 Mar 2001 04:09:54 -0800
Received: from pc-11-126.corp.3com.com (HELO PhilsSony) (139.87.11.126)
  by smtp.telocity.com (209.228.33.206) with SMTP; 1 Mar 2001 04:09:54 -0800
X-Sent: 1 Mar 2001 12:09:54 GMT
Message-ID: <001a01c0a248$b92182a0$6601a8c0@mw.3com.com>
From: "Phillip Neumiller" <neumiller@telocity.com>
To: "Kulwinder Atwal" <KAtwal@zucotto.com>, <seamoby@diameter.org>
References: <6833D86F1B05CA4FBAB3C73DD98BD8B90D29DC@NEPTUNE.zucotto.com>
Subject: Re: [seamoby] Yet Another BOF?
Date: Thu, 1 Mar 2001 06:11:18 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I concur completely with Kulwinder's comments.

-Phil Neumiller
----- Original Message -----
From: "Kulwinder Atwal" <KAtwal@zucotto.com>
To: <seamoby@diameter.org>
Sent: Wednesday, February 28, 2001 9:01 PM
Subject: RE: [seamoby] Yet Another BOF?


> 3.2 MANET / Ad-Hoc Networking Comparison
>
>    The MANET WG in the IETF has an important charter to create a
>    protocol for mobiles arranged in arbitrary and highly dynamic
>    associations.  This work is striving for robust and highly scalable
>    routing solutions.  Currently, MANET is not considering fast or
>    seamless handover.
>
>    In many instances, for example small residential networks found in
>    the home, the network may be relatively small and has far less
>    dynamics.  The network may still have a requirement for fast and/or
>    seamless handovers. For this reason there may be some overlap
>    between SeaMoby and ad-hoc networking solutions.  Therefore, SeaMoby
>    MUST be able to co-exist gracefully with any MANET solutions
>    algorithm that does become standardized.
>
> > -----Original Message-----
> > From: Phil_Neumiller@3com.com [mailto:Phil_Neumiller@3com.com]
> > Sent: Tuesday, February 27, 2001 6:51 PM
> > To: seamoby@diameter.org
> > Subject: [seamoby] Yet Another BOF?
> >
> >
> >
> >
> >
> > After a brief history with mobility BOFs,  I am convinced
> > that they are of
> > limited use.  Perhaps an
> > informational RFC is a better approach (not my idea).  I am
> > convinced that many
> > of us (perhaps
> > Gary, (Andrew, James, John, Peter, and the other OBAST
> > disciples:-))) that
> > wanted to build true
> > all IP based, edge oriented, routers with wireless cards,
> > with a standardized
> > backhaul, some
> > how got muscled out of the IETF by the powerful forces of the
> > MIP and MANET
> > groups.
>
> In the Micro-mobility draft the following section appears:
>
> 3.2 MANET / Ad-Hoc Networking Comparison
>
>    The MANET WG in the IETF has an important charter to create a
>    protocol for mobiles arranged in arbitrary and highly dynamic
>    associations.  This work is striving for robust and highly scalable
>    routing solutions.  Currently, MANET is not considering fast or
>    seamless handover.
>
>    In many instances, for example small residential networks found in
>    the home, the network may be relatively small and has far less
>    dynamics.  The network may still have a requirement for fast and/or
>    seamless handovers. For this reason there may be some overlap
>    between SeaMoby and ad-hoc networking solutions.  Therefore, SeaMoby
>    MUST be able to co-exist gracefully with any MANET solutions
>    algorithm that does become standardized.
>
> Comments:
>
> Why 'MUST' SeaMoby be confined by MANET/MIP?
> If SeaMoby does its job there will be no need for MANET in local mobility.
> If SeaMoby does its job there will be no need for MIP in local mobility.
>
> Are we forgetting that devices in the home are low cost?
> Why would any vendor support MIP, MANET and Seamoby to do one thing:
moving?
> Why would any Bluetooth vendor support three protocols when the same
vendor
> can go to the Bluetooth SIG and use the work of a SIG WG to get one
> protocol?
>
> The title of the section says ,"Comparion", but states a mandatory
> requirement.
> By making MANET a 'MUST' requirement for Seamoby is a sure way to see that
> Seamoby is
> never deployed.
>
> I would like someone the justify the opening statement in section 3.2:
>
>    The MANET WG in the IETF has an important charter to create a
>    protocol for mobiles arranged in arbitrary and highly dynamic
>    associations.
>
> Is the MANET charter more important than the SeaMoby Charter?
>
> What is an "arbitary association" and how does it differ from mobility?
>
> What is the timescale for "highly dynamic associations"?
>
> - Kulwinder.
>



From owner-seamoby@diameter.org  Thu Mar  1 13:45:58 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA16485
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 13:45:57 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21IVA121233
	for seamoby-list; Thu, 1 Mar 2001 10:31:10 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21IV7o21228
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 10:31:07 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id CAA74944;
	Fri, 2 Mar 2001 02:32:03 +0900
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA18709;
 Thu, 1 Mar 2001 09:38:47 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA00081;
 Thu, 1 Mar 2001 09:38:28 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f21Hag316488
 for mobile-ip-dist; Thu, 1 Mar 2001 09:36:42 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f21HaXV16481
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 09:36:33 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA29691
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 09:36:32 -0800 (PST)
Received: from eagle.aud.alcatel.com (host60d9.alcatel.com [128.251.96.217])
 by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA00342
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 09:36:32 -0800 (PST)
Received: from mswitch.aud.alcatel.com by eagle.aud.alcatel.com (8.8.8+Sun/SMI-SVR4)
 id LAA18139; Thu, 1 Mar 2001 11:36:24 -0600 (CST)
Received: from usa.alcatel.com by mswitch.aud.alcatel.com (8.8.8+Sun/SMI-SVR4)
 id LAA14127; Thu, 1 Mar 2001 11:36:22 -0600 (CST)
Message-ID: <3A9E8895.DD789091@usa.alcatel.com>
Date: Thu, 01 Mar 2001 11:36:21 -0600
From: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: seamoby@diameter.org
Subject: Re: [seamoby] Arch discussions in IETF
References: <7B5C0390ACE7D211BC9C0008C7EABA2B0321356A@daeis07nok>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi Raj and Phil,

  I think the critical question for micromobility (mm) branch of the
Seamoby WG is
to be or not to be, i.e.
whether another routing protocol for mobility is required. Presently we
have the MIP and
the Manet routing approaches.
  The alternative seems to be per-host routes or host-based routing. I do
not think there
has been another breakthrough proposal significantly different. We all know
Cellular IP and
Hawaii proposals. Recently there is probably another one based on extending
OSPF with
host-based routes.
  Of course there are a lot of details but I think this is the crux of
Seamoby mm problem.

--
Behcet




From owner-seamoby@diameter.org  Thu Mar  1 13:48:29 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA16593
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 13:48:27 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21IA5a21142
	for seamoby-list; Thu, 1 Mar 2001 10:10:05 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zrtps06u.us.nortel.com (h52s48a140n47.user.nortelnetworks.com [47.140.48.52])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21IA2o21135
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 10:10:02 -0800
Received: from smtprch2.nortel.com (erchg0k.us.nortel.com [47.113.64.104])
	by zrtps06u.us.nortel.com (8.11.0/8.11.0) with ESMTP id f21HIXl29398
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 12:18:33 -0500 (EST)
Received: from zrchb200.us.nortel.com (actually zrchb200) 
          by smtprch2.nortel.com; Thu, 1 Mar 2001 10:23:59 -0600
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZ1PFTHC>; Thu, 1 Mar 2001 10:26:48 -0600
Message-ID: <85AA7486A2C1D411BCA20000F8073E4351C70C@crchy271.us.nortel.com>
From: "Glenn Morrow" <gmorrow@nortelnetworks.com>
To: "'Hesham Soliman (ERA)'" <Hesham.Soliman@era.ericsson.se>
Cc: "'Michael Thomas'" <mat@cisco.com>, seamoby@diameter.org
Subject: RE: [seamoby] I-D ACTION:draft-ietf-seamoby-mm-problem-00.txt
Date: Thu, 1 Mar 2001 10:25:41 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A26C.420CD9C0"
X-Orig: <gmorrow@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A26C.420CD9C0
Content-Type: text/plain;
	charset="iso-8859-1"

Hesham,

See below:


> Hello Glenn, 
> 
> A router is a device that forwards packets from one interface to
> another. That makes a NAT a router and so is a HA. 
> A router CAN definitely tunnel, I hope you agree with that.
[[gm]]  Sounds like a reasonable definition to me; however, I do suspect
that some routers can't tunnel and can't do NAT. I think we should say "some
routers can" and be done with this banter which has occured since the
original MIPv6 handoff discussion. 

> A NAT is a device that hides addresses on one side of the 
> network from the other side and the end nodes. Typically 
> because they are not routable. 
[[gm]]  You have limited your definition of NAT. A NAT is a device or
process that translates a source and or desination address to another. It
matters not whether the addresses are globally routable or not. One could
say that one application of network address translation is to hide internal
addresses from the external network.

> A HA _does_not_hide addresses from anyone. 
[[gm]]  Really - does a correspondent node know the MN's COA unless route
optmization is used?

> The end nodes 
> and the entire Internet can route a MN's Home address.
[[gm]]  I am extremely please by this. I am also pleased that the entire
Internet does not know the MN's COA. I am not please with the fact that in
order to provide route optimization, the entire Internet must know the COA.
I would suggest a solution that exposes the COA information to only routers
and not hosts.
>  
> NATs typically break end to end security and many peer to
> peer protocols. A HA doesn't.
[[gm]]  
If you apply network address translation at both sides (as route optmized
MIP does) then you have no problem with peer to peer protocols. One way of
avoiding the necessity of changing of supposedly un-mutable fields is to use
encapsulation. Do you see that in optimized MIP, the MN could use a tunnel
to the CN to deliver a packet instead of address translation. The packet is
delivered either way (i.e. same functionality - different mechanism).

> I'm a bit surprised by your analogy and definitions but 
> I dont really think we should spend our lives looking 
> for a definition that makes a HA look like a NAT. 
> Surely there are better reasons for justifying
> the mm problem and better things to do.
[[gm]]  begin
Surely the following:

- a list of true requirements for node mobility (macro, micro)
- an analysis of data-hiding ramifications of these requirments
- an analysis of the scaling ramifications of these requirments

are essential to any problem and solution set.

You are quite correct that I was not focusing merely on the micro-solution.
I was also addressing end to end security associations, scaling, etc.. that
are some of the "excuses" for micromobility solutions - not that I am
opposed to some solutions. I believe we need both solutions that can support
real-time handover. 

If you note, the HA correlation with NAT is only one aspect about what is
discussed below. Making an HA equivalent to a limited definition of a NAT
was not my goal. I am a bit perplexed as to why your response focuses so
much on such a minor analogy and adapt an attitude that I somehow do not
understand the difference. 

If you look, I believe you might find some more pertinent suggestions in
terms of requirements, ramifications and possible ways forward. I and I hope
others would see much more value for you to focus on these.

Regards,

Glenn


[[gm]]  end

> Regards,
> Hesham
> 
> > -----Original Message-----
> > From:	Glenn Morrow [SMTP:gmorrow@nortelnetworks.com]
> > Sent:	Thursday, 1 March 2001 7:16
> > To:	'Hesham Soliman (ERA)'; 'Michael Thomas'
> > Cc:	seamoby@diameter.org
> > Subject:	RE: [seamoby] I-D
> ACTION:draft-ietf-seamoby-mm-problem-00.txt
> > 
> > I don't mean to jump but IMHO here are some things to realize about MIP
> in relation to these NAT statements: 
> > 
> > Route Optimized MIP is essentially per-host routing with some signaling
> (BU) and a double NAT function built into the end-nodes (hosts if you
> prefer).
> > 
> > Functionally you could decompose a MIP MN or a CN into the NAT, per-host
> routing (binding cache) functions and the "pure" host (applications) which
> uses the home addresses.
> > 
> > You could also think of the HA as a part of this double NAT as well;
> albeit, it is using a tunnel to statelessly signal the address
> translation.
> > 
> > The reason I am trying to bring this up to people is to make them
> realize the following: 
> > 
> > - It is per-host routing. 
> > - It is double NAT (address translation at both ends) 
> > 
> > Because it is per-host routing the route tables of the hosts may indeed
> grow large. For example, one of the hosts may be a website which millions
> of mobile hosts communicate simultaneously. Imagine a media or even just
> an HTTP server with a million per-host route entries. 
> > 
> > Are there server companies and chip manufacturers working on hardware
> assisted look-up engines and code to do these lookups to meet the delay
> requirements?
> > 
> > Another approach we might take it to move the double NAT and fast
> (per-host routing) lookup functions to the (purpose built) subnet routers
> where they might have a chance of scaling. 
> > 
> > This might also serve to provide simultaneous route optimization with
> location privacy and allow the existing SA's between routers to be
> leveraged in order to avoid the necessity of setting up SA's every time a
> mobile node wishes to communicate with another node on the network.
> > 
> > I am also fairly convinced that there are solutions which do not
> compromise the connectionless (redundant) nature of IP, especially in the
> IPv6 case.
> > 
> > Indeed this would not be creating a new protocol to solve the node
> mobility problem - it would be changing IP, itself, to solve the node
> mobility problem - essentially making a new "pure" IP.
> > 
> > O.K. fire away  - at least we might get off the "what is a router"
> debate. 
> > 
> > Glenn 
> > 
> > 
> > 
> > 

------_=_NextPart_001_01C0A26C.420CD9C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: [seamoby] I-D =
ACTION:draft-ietf-seamoby-mm-problem-00.txt</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Hesham,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">See below:</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hello Glenn, </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">A router is a device that forwards =
packets from one interface to</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">another. That makes a NAT a router =
and so is a HA. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">A router CAN definitely tunnel, I =
hope you agree with that.</FONT>
<BR><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> Sounds like a reasonable =
definition to me; however, I do suspect that some routers can't tunnel =
and can't do NAT. I think we should say &quot;some routers can&quot; =
and be done with this banter which has occured since the original MIPv6 =
handoff discussion.</FONT> </P>

<P><FONT SIZE=3D2 FACE=3D"Arial">A NAT is a device that hides addresses =
on one side of the </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">network from the other side and the =
end nodes. Typically </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">because they are not routable. =
</FONT>
<BR><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> You have limited your =
definition of NAT. A NAT is a device or process that translates a =
source and or desination address to another. It matters not whether the =
addresses are globally routable or not. One could say that one =
application of network address translation is to hide internal =
addresses from the external network.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">A HA _does_not_hide addresses from =
anyone. </FONT>
<BR><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> Really - does a =
correspondent node know the MN's COA unless route optmization is =
used?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The end nodes </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">and the entire Internet can route a =
MN's Home address.</FONT>
<BR><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> I am extremely please by =
this. I am also pleased that the entire</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Internet does not =
know the MN's COA. I am not please with the fact that in order to =
provide route optimization, the entire Internet must know the =
COA.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I would suggest a =
solution that exposes the COA information to only routers and not =
hosts.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">NATs typically break end to end =
security and many peer to</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">peer protocols. A HA doesn't.</FONT>
<BR><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> </FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">If you apply =
network address translation at both sides (as route optmized MIP does) =
then you have no problem with peer to peer protocols. One way of =
avoiding the necessity of changing of supposedly un-mutable fields is =
to use encapsulation. Do you see that in optimized MIP, the MN could =
use a tunnel to the CN to deliver a packet instead of address =
translation. The packet is delivered either way (i.e. same =
functionality - different mechanism).</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I'm a bit surprised by your analogy =
and definitions but </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">I dont really think we should spend =
our lives looking </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">for a definition that makes a HA look =
like a NAT. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Surely there are better reasons for =
justifying</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">the mm problem and better things to =
do.</FONT>
<BR><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> begin</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Surely the =
following:</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">- a list of true =
requirements for node mobility (macro, micro)</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">- an analysis of =
data-hiding ramifications of these requirments</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">- an analysis of =
the scaling ramifications of these requirments</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">are essential to any =
problem and solution set.</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">You are quite =
correct that I was not focusing merely on the micro-solution. I was =
also addressing end to end security associations, scaling, etc.. that =
are some of the &quot;excuses&quot; for micromobility solutions - not =
that I am opposed to some solutions. I believe we need both solutions =
that can support real-time handover. </FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">If you note, the HA =
correlation with NAT is only one aspect about what is discussed below. =
Making an HA equivalent to a limited definition of a NAT was not my =
goal. I am a bit perplexed as to why your response focuses so much on =
such a minor analogy and adapt an attitude that I somehow do not =
understand the difference. </FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">If you look, I =
believe you might find some more pertinent suggestions in terms of =
requirements, ramifications and possible ways forward. I and I hope =
others would see much more value for you to focus on these.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Regards,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Glenn</FONT>
</P>
<BR>

<P><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> end</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Hesham</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; From: Glenn Morrow =
[SMTP:gmorrow@nortelnetworks.com]</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Sent: Thursday, 1 March 2001 =
7:16</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; To:&nbsp;&nbsp; 'Hesham Soliman =
(ERA)'; 'Michael Thomas'</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Cc:&nbsp;&nbsp; =
seamoby@diameter.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RE: [seamoby] I-D =
ACTION:draft-ietf-seamoby-mm-problem-00.txt</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; I don't mean to jump but IMHO =
here are some things to realize about MIP in relation to these NAT =
statements: </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Route Optimized MIP is =
essentially per-host routing with some signaling (BU) and a double NAT =
function built into the end-nodes (hosts if you prefer).</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Functionally you could decompose =
a MIP MN or a CN into the NAT, per-host routing (binding cache) =
functions and the &quot;pure&quot; host (applications) which uses the =
home addresses.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; You could also think of the HA =
as a part of this double NAT as well; albeit, it is using a tunnel to =
statelessly signal the address translation.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; The reason I am trying to bring =
this up to people is to make them realize the following: </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; - It is per-host routing. =
</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; - It is double NAT (address =
translation at both ends) </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Because it is per-host routing =
the route tables of the hosts may indeed grow large. For example, one =
of the hosts may be a website which millions of mobile hosts =
communicate simultaneously. Imagine a media or even just an HTTP server =
with a million per-host route entries. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Are there server companies and =
chip manufacturers working on hardware assisted look-up engines and =
code to do these lookups to meet the delay requirements?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Another approach we might take =
it to move the double NAT and fast (per-host routing) lookup functions =
to the (purpose built) subnet routers where they might have a chance of =
scaling. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; This might also serve to provide =
simultaneous route optimization with location privacy and allow the =
existing SA's between routers to be leveraged in order to avoid the =
necessity of setting up SA's every time a mobile node wishes to =
communicate with another node on the network.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; I am also fairly convinced that =
there are solutions which do not compromise the connectionless =
(redundant) nature of IP, especially in the IPv6 case.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Indeed this would not be =
creating a new protocol to solve the node mobility problem - it would =
be changing IP, itself, to solve the node mobility problem - =
essentially making a new &quot;pure&quot; IP.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; O.K. fire away&nbsp; - at least =
we might get off the &quot;what is a router&quot; debate. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Glenn </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A26C.420CD9C0--


From owner-seamoby@diameter.org  Thu Mar  1 14:11:12 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18381
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 14:11:11 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21IQuG21190
	for seamoby-list; Thu, 1 Mar 2001 10:26:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from eagle.aud.alcatel.com (host60d9.alcatel.com [128.251.96.217])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21IQro21185
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 10:26:53 -0800
Received: from mswitch.aud.alcatel.com by eagle.aud.alcatel.com (8.8.8+Sun/SMI-SVR4)
	id LAA18139; Thu, 1 Mar 2001 11:36:24 -0600 (CST)
Received: from usa.alcatel.com by mswitch.aud.alcatel.com (8.8.8+Sun/SMI-SVR4)
	id LAA14127; Thu, 1 Mar 2001 11:36:22 -0600 (CST)
Message-ID: <3A9E8895.DD789091@usa.alcatel.com>
Date: Thu, 01 Mar 2001 11:36:21 -0600
From: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: seamoby@diameter.org
Subject: Re: [seamoby] Arch discussions in IETF
References: <7B5C0390ACE7D211BC9C0008C7EABA2B0321356A@daeis07nok>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Raj and Phil,

  I think the critical question for micromobility (mm) branch of the
Seamoby WG is
to be or not to be, i.e.
whether another routing protocol for mobility is required. Presently we
have the MIP and
the Manet routing approaches.
  The alternative seems to be per-host routes or host-based routing. I do
not think there
has been another breakthrough proposal significantly different. We all know
Cellular IP and
Hawaii proposals. Recently there is probably another one based on extending
OSPF with
host-based routes.
  Of course there are a lot of details but I think this is the crux of
Seamoby mm problem.

--
Behcet



From owner-seamoby@diameter.org  Thu Mar  1 14:31:32 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19200
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 14:31:29 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21J26021331
	for seamoby-list; Thu, 1 Mar 2001 11:02:06 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21J23o21326
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 11:02:03 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id DAA155140;
	Fri, 2 Mar 2001 03:02:56 +0900
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
 by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA10965;
 Thu, 1 Mar 2001 10:10:30 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA09819;
 Thu, 1 Mar 2001 10:10:22 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f21I8f716960
 for mobile-ip-dist; Thu, 1 Mar 2001 10:08:41 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f21I8UV16953
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 10:08:31 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA23948
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 10:08:30 -0800 (PST)
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA10766
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 11:08:28 -0700 (MST)
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
 by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id CAA72324;
 Fri, 2 Mar 2001 02:59:44 +0900
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA03112;
 Thu, 1 Mar 2001 10:06:38 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA07381;
 Thu, 1 Mar 2001 10:05:06 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f21I3K816801
 for mobile-ip-dist; Thu, 1 Mar 2001 10:03:20 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f21I3AV16794
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 10:03:11 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA07495
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 10:03:10 -0800 (PST)
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA07392
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 11:03:09 -0700 (MST)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
 by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id KAA14049;
 Thu, 1 Mar 2001 10:03:01 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
 by mira-sjc5-7.cisco.com (Mirapoint)
 with ESMTP id ABV01622;
 Thu, 1 Mar 2001 10:02:55 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA28818; Thu, 1 Mar 2001 10:02:55 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Message-ID: <15006.36559.662301.41126@thomasm-u1.cisco.com>
Date: Thu, 1 Mar 2001 10:02:55 -0800 (PST)
To: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
Cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Subject: Re: [seamoby] Arch discussions in IETF
In-Reply-To: <3A9E8895.DD789091@usa.alcatel.com>
References: <7B5C0390ACE7D211BC9C0008C7EABA2B0321356A@daeis07nok>
 <3A9E8895.DD789091@usa.alcatel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

I don't think this quite captures the finesse on
the issue. I don't believe that the proper framing
of the question is whether a new routing protocol
needs to be invented or not: it may very well be
that there is nothing to be done on the _routing
protocol_ front to support injecting host routes
if that's the ultimate solution. There may be work
needed to support _signaling_ a router that it
needs to change how a subnet is reachable.

I know this is hair splitting, but I think it's
important to separate out that it's quite possible
that the heavy lifting can already be done by
current protocols, and that all we need is the
ability to trigger them to happen. You might call
that a "routing protocol" too, but it ought not
evoke the fear and loathing that postulating a
Routing Protocol should.

   MIke


Behcet Sarikaya writes:
 > Hi Raj and Phil,
 > 
 >   I think the critical question for micromobility (mm) branch of the
 > Seamoby WG is
 > to be or not to be, i.e.
 > whether another routing protocol for mobility is required. Presently we
 > have the MIP and
 > the Manet routing approaches.
 >   The alternative seems to be per-host routes or host-based routing. I do
 > not think there
 > has been another breakthrough proposal significantly different. We all know
 > Cellular IP and
 > Hawaii proposals. Recently there is probably another one based on extending
 > OSPF with
 > host-based routes.
 >   Of course there are a lot of details but I think this is the crux of
 > Seamoby mm problem.
 > 
 > --
 > Behcet
 > 




From owner-seamoby@diameter.org  Thu Mar  1 15:02:55 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA20623
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 15:02:54 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21IwuX21302
	for seamoby-list; Thu, 1 Mar 2001 10:58:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21Iwro21297
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 10:58:53 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id CAA72324;
	Fri, 2 Mar 2001 02:59:44 +0900
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA03112;
 Thu, 1 Mar 2001 10:06:38 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA07381;
 Thu, 1 Mar 2001 10:05:06 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f21I3K816801
 for mobile-ip-dist; Thu, 1 Mar 2001 10:03:20 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f21I3AV16794
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 10:03:11 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA07495
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 10:03:10 -0800 (PST)
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA07392
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 11:03:09 -0700 (MST)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
 by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id KAA14049;
 Thu, 1 Mar 2001 10:03:01 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
 by mira-sjc5-7.cisco.com (Mirapoint)
 with ESMTP id ABV01622;
 Thu, 1 Mar 2001 10:02:55 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA28818; Thu, 1 Mar 2001 10:02:55 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Message-ID: <15006.36559.662301.41126@thomasm-u1.cisco.com>
Date: Thu, 1 Mar 2001 10:02:55 -0800 (PST)
To: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
Cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Subject: Re: [seamoby] Arch discussions in IETF
In-Reply-To: <3A9E8895.DD789091@usa.alcatel.com>
References: <7B5C0390ACE7D211BC9C0008C7EABA2B0321356A@daeis07nok>
 <3A9E8895.DD789091@usa.alcatel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

I don't think this quite captures the finesse on
the issue. I don't believe that the proper framing
of the question is whether a new routing protocol
needs to be invented or not: it may very well be
that there is nothing to be done on the _routing
protocol_ front to support injecting host routes
if that's the ultimate solution. There may be work
needed to support _signaling_ a router that it
needs to change how a subnet is reachable.

I know this is hair splitting, but I think it's
important to separate out that it's quite possible
that the heavy lifting can already be done by
current protocols, and that all we need is the
ability to trigger them to happen. You might call
that a "routing protocol" too, but it ought not
evoke the fear and loathing that postulating a
Routing Protocol should.

   MIke


Behcet Sarikaya writes:
 > Hi Raj and Phil,
 > 
 >   I think the critical question for micromobility (mm) branch of the
 > Seamoby WG is
 > to be or not to be, i.e.
 > whether another routing protocol for mobility is required. Presently we
 > have the MIP and
 > the Manet routing approaches.
 >   The alternative seems to be per-host routes or host-based routing. I do
 > not think there
 > has been another breakthrough proposal significantly different. We all know
 > Cellular IP and
 > Hawaii proposals. Recently there is probably another one based on extending
 > OSPF with
 > host-based routes.
 >   Of course there are a lot of details but I think this is the crux of
 > Seamoby mm problem.
 > 
 > --
 > Behcet
 > 



From owner-seamoby@diameter.org  Thu Mar  1 15:04:44 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA20725
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 15:04:43 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21J3hO21349
	for seamoby-list; Thu, 1 Mar 2001 11:03:43 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from hotmail.com (f45.law7.hotmail.com [216.33.237.45])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21J3go21344
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 11:03:42 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 1 Mar 2001 10:13:14 -0800
Received: from 63.78.179.5 by lw7fd.law7.hotmail.msn.com with HTTP;	Thu, 01 Mar 2001 18:13:13 GMT
X-Originating-IP: [63.78.179.5]
From: "Hemant Chaskar" <hchaskar@hotmail.com>
To: Hesham.Soliman@era.ericsson.se, james.kempf@sun.com,
        mobile-ip@marvin.corpeast.baynetworks.com
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
Date: Thu, 01 Mar 2001 18:13:13 
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F45GbRaedfUmtue5tkF0001933d@hotmail.com>
X-OriginalArrivalTime: 01 Mar 2001 18:13:14.0144 (UTC) FILETIME=[48251200:01C0A27B]
Sender: owner-seamoby@diameter.org
Precedence: bulk

Regarding the issue of round-trip latency in programming QoS forwarding 
treatment along new path after change in CoA:

This is intrinsic drawback of OPWA model of resource reservation of RSVP. In 
the worst case, one round-trip time will include traversals of four wireless 
links. This happens when both CN and MN are mobile.

Note that this drawback is eliminated in the approach to QoS signaling based 
on including QoS Object in hop-by-hop options extension header along with 
binding messages (draft-chaskar-mobileip-qos-00.txt). This draft was 
presented in SD and revised version (01) will be submitted soon.

Hemant
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com



From owner-seamoby@diameter.org  Thu Mar  1 15:07:01 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA20799
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 15:07:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21JauG21476
	for seamoby-list; Thu, 1 Mar 2001 11:36:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21Jaso21471
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 11:36:54 -0800
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Thu, 1 Mar 2001 13:42:57 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZV98DPK>; Thu, 1 Mar 2001 13:42:45 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D1C@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Scott Bradner'" <sob@harvard.edu>, campbell@comet.columbia.edu,
        pcalhoun@nasnfs.eng.sun.com
Cc: james.kempf@sun.com, Phil_Neumiller@3Com.com, seamoby@diameter.org
Subject: RE: [seamoby] Yet Another BOF?
Date: Thu, 1 Mar 2001 13:42:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A27F.5FEC1E70"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A27F.5FEC1E70
Content-Type: text/plain;
	charset="iso-8859-1"

It's just my perception Scott, but it seems like the response to any
identified requirement is "well, we can make MIP do that"....

Gary

> -----Original Message-----
> From: Scott Bradner [mailto:sob@harvard.edu]
> Sent: Wednesday, February 28, 2001 4:03 PM
> To: campbell@comet.columbia.edu; Kenward, Gary [WDLN2:AN10:EXCH];
> pcalhoun@nasnfs.eng.sun.com
> Cc: james.kempf@sun.com; Phil_Neumiller@3Com.com; seamoby@diameter.org
> Subject: RE: [seamoby] Yet Another BOF?
> 
> 
> anything that includes the text "That excludes vanilla MIP as 
> a solution"
> does not look like a requirements discusison to me 
> 
> why is it so hard to discuss what the actual requirents are without
> talking about solutions?
> 
> Scott
> 
> 

------_=_NextPart_001_01C0A27F.5FEC1E70
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>RE: [seamoby] Yet Another BOF?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>It's just my perception Scott, but it seems like the response to any</FONT>
<BR><FONT SIZE=2>identified requirement is &quot;well, we can make MIP do that&quot;....</FONT>
</P>

<P><FONT SIZE=2>Gary</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: Scott Bradner [<A HREF="mailto:sob@harvard.edu">mailto:sob@harvard.edu</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Wednesday, February 28, 2001 4:03 PM</FONT>
<BR><FONT SIZE=2>&gt; To: campbell@comet.columbia.edu; Kenward, Gary [WDLN2:AN10:EXCH];</FONT>
<BR><FONT SIZE=2>&gt; pcalhoun@nasnfs.eng.sun.com</FONT>
<BR><FONT SIZE=2>&gt; Cc: james.kempf@sun.com; Phil_Neumiller@3Com.com; seamoby@diameter.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: RE: [seamoby] Yet Another BOF?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; anything that includes the text &quot;That excludes vanilla MIP as </FONT>
<BR><FONT SIZE=2>&gt; a solution&quot;</FONT>
<BR><FONT SIZE=2>&gt; does not look like a requirements discusison to me </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; why is it so hard to discuss what the actual requirents are without</FONT>
<BR><FONT SIZE=2>&gt; talking about solutions?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Scott</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A27F.5FEC1E70--


From owner-seamoby@diameter.org  Thu Mar  1 15:31:37 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA21741
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 15:31:35 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21JR8Q21423
	for seamoby-list; Thu, 1 Mar 2001 11:27:08 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21JQYo21418
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 11:26:34 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id KAA14060;
	Thu, 1 Mar 2001 10:35:11 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABV02412;
	Thu, 1 Mar 2001 10:32:37 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA28821; Thu, 1 Mar 2001 10:32:37 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15006.38341.180329.463348@thomasm-u1.cisco.com>
Date: Thu, 1 Mar 2001 10:32:37 -0800 (PST)
To: "Hemant Chaskar" <hchaskar@hotmail.com>
Cc: Hesham.Soliman@era.ericsson.se, james.kempf@sun.com,
        mobile-ip@marvin.corpeast.baynetworks.com, seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
In-Reply-To: <F45GbRaedfUmtue5tkF0001933d@hotmail.com>
References: <F45GbRaedfUmtue5tkF0001933d@hotmail.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I don't see how this fundamentally changes
anything that James brought up. It still has to go
end to end, and it's still touching every router
in between MN and CN. 

What I do see is a lot of reinvention of RSVP
Rspec and Tspec's for no known reason.  The only
thing I can see of possible value is the ability
to piggyback the QoS update with the BU, but even
if this is the sole goal -- and that it's a worthy
goal which is not at all apparent to me -- I
imagine that there are better ways of doing this
with out reinventing RSVP: like, maybe,
piggybacking the BU on the PATH, or some such.

	     Mike


Hemant Chaskar writes:
 > Regarding the issue of round-trip latency in programming QoS forwarding 
 > treatment along new path after change in CoA:
 > 
 > This is intrinsic drawback of OPWA model of resource reservation of RSVP. In 
 > the worst case, one round-trip time will include traversals of four wireless 
 > links. This happens when both CN and MN are mobile.
 > 
 > Note that this drawback is eliminated in the approach to QoS signaling based 
 > on including QoS Object in hop-by-hop options extension header along with 
 > binding messages (draft-chaskar-mobileip-qos-00.txt). This draft was 
 > presented in SD and revised version (01) will be submitted soon.
 > 
 > Hemant
 > _________________________________________________________________
 > Get your FREE download of MSN Explorer at http://explorer.msn.com
 > 


From owner-seamoby@diameter.org  Thu Mar  1 15:31:38 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA21742
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 15:31:36 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21IrYS21292
	for seamoby-list; Thu, 1 Mar 2001 10:53:34 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21IrVo21287
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 10:53:31 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id KAA14049;
	Thu, 1 Mar 2001 10:03:01 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABV01622;
	Thu, 1 Mar 2001 10:02:55 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA28818; Thu, 1 Mar 2001 10:02:55 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15006.36559.662301.41126@thomasm-u1.cisco.com>
Date: Thu, 1 Mar 2001 10:02:55 -0800 (PST)
To: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
Cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Subject: Re: [seamoby] Arch discussions in IETF
In-Reply-To: <3A9E8895.DD789091@usa.alcatel.com>
References: <7B5C0390ACE7D211BC9C0008C7EABA2B0321356A@daeis07nok>
	<3A9E8895.DD789091@usa.alcatel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I don't think this quite captures the finesse on
the issue. I don't believe that the proper framing
of the question is whether a new routing protocol
needs to be invented or not: it may very well be
that there is nothing to be done on the _routing
protocol_ front to support injecting host routes
if that's the ultimate solution. There may be work
needed to support _signaling_ a router that it
needs to change how a subnet is reachable.

I know this is hair splitting, but I think it's
important to separate out that it's quite possible
that the heavy lifting can already be done by
current protocols, and that all we need is the
ability to trigger them to happen. You might call
that a "routing protocol" too, but it ought not
evoke the fear and loathing that postulating a
Routing Protocol should.

		 MIke


Behcet Sarikaya writes:
 > Hi Raj and Phil,
 > 
 >   I think the critical question for micromobility (mm) branch of the
 > Seamoby WG is
 > to be or not to be, i.e.
 > whether another routing protocol for mobility is required. Presently we
 > have the MIP and
 > the Manet routing approaches.
 >   The alternative seems to be per-host routes or host-based routing. I do
 > not think there
 > has been another breakthrough proposal significantly different. We all know
 > Cellular IP and
 > Hawaii proposals. Recently there is probably another one based on extending
 > OSPF with
 > host-based routes.
 >   Of course there are a lot of details but I think this is the crux of
 > Seamoby mm problem.
 > 
 > --
 > Behcet
 > 


From owner-seamoby@diameter.org  Thu Mar  1 15:48:18 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22379
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 15:48:17 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21K3Jl21559
	for seamoby-list; Thu, 1 Mar 2001 12:03:19 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21K3Go21554
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 12:03:16 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Thu, 1 Mar 2001 14:08:13 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZV9813A>; Thu, 1 Mar 2001 14:08:15 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D22@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "Gary Kenward" <gkenward@nortelnetworks.com>,
        "'James Kempf'" <james.kempf@sun.com>, Phil_Neumiller@3Com.com,
        seamoby@diameter.org
Subject: RE: [seamoby] Yet Another BOF?
Date: Thu, 1 Mar 2001 14:08:09 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A282.F42F90A0"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A282.F42F90A0
Content-Type: text/plain;
	charset="iso-8859-1"

Er, This should have read:
 
"Sorry James, . . . "
 
I re-read Phil's posting after sending out this message, and I failed to
see any reference to paging...
 
Gary

-----Original Message-----
From: Kenward, Gary [WDLN2:AN10:EXCH] 
Sent: Wednesday, February 28, 2001 3:19 PM
To: 'James Kempf'; Phil_Neumiller@3Com.com; seamoby@diameter.org
Subject: RE: [seamoby] Yet Another BOF?



Sorry Phil, I guess I misunderstood. The email in the front of my 
mind from Phil didn't discuss paging, he was making a general argument. 

My apologies for being confused. 

Gary 


> -----Original Message----- 
> From: James Kempf [ mailto:james.kempf@sun.com
<mailto:james.kempf@sun.com> ] 
> Sent: Wednesday, February 28, 2001 3:08 PM 
> To: Kenward, Gary [WDLN2:AN10:EXCH]; Phil_Neumiller@3Com.com; 
> seamoby@diameter.org 
> Subject: RE: [seamoby] Yet Another BOF? 
> 
> 
> Hi Gary, 
> 
> I think you missed what I said about paging. 
> 
> If you read the paging problem statement draft carefully, you 
> will see that 
> practically 
> everything that a paging protocol would do could be done by MIP. The 
> problem is, 
> it would result in a considerable complexity increase, and 
> would compromise 
> the utility of dormant mode for the mobile. Thus the 
> conclusion, a paging 
> protocol for IP would be a benefit. 
> 
> If the MM folks can demonstrate the same w.r.t. to mobility, 
> particularly 
> for security and QoS, then I think a case can be made for an 
> MM protocol. 
> With all due respect to the MM design team and to John, the 
> draft editor, 
> the draft did not present such a clear case (at least, not 
> the 00 draft, I 
> have yet to read the 01 draft), at least not to me. 
> If the mobile IP proponents are making these statements, then it is 
> incumbent upon the MM proponents to say: "Oh yeah? Show me 
> how!". If they 
> can't come up with a solution, and a sketch of an MM solution 
> is simpler, 
> then MM is clearly the way to go. The solution doesn't have 
> to be complete, 
> even a simple description is usually enough to see whether 
> the MIP solution 
> would be more complex or compromise particular requirements. 
> However, if in 
> the end, the mobile IP solution is good enough, in the 
> sense that it satisfies the requirements, and the working 
> group agrees, 
> then its no good going off in a huff and accusing the mobile 
> IP proponents 
> of stonewalling. 
> 
> I have no problem with giving the MM design team more time, since the 
> problem is more complex (and I hope the IESG will agree), 
> but, in the end, 
> I expect to see a technically based analysis, including 
> requirments and how 
> mobile IP can't solve them. It's OK to dream, but the rubber 
> hits the road 
> when you have to explain to skeptical engineers why your 
> completely new 
> solution will replace the existing solution in which they've 
> invested much 
> design and perhaps even implementation effort. 
> 
>                  jak 
> 
> At 01:18 PM 2/28/01 -0500, Gary Kenward wrote: 
> 
> >James: 
> > 
> >   I think you miss Phil's point. It's all simply a matter of 
> >software, and no doubt, with enough extensions, modifications, 
> >and bit twiddling, we could turn ARP into some version of a 
> >mobility protocol (or any other protocol, heck, there are still 
> >people working on mobile wireless ATM). 
> > 
> >    The frustration comes because with each attempt at a 
> >problem statement, MIP proponents come forth and state: 
> >"oh, well sure, we can make MIP do that". No problem statement 
> >for MM will ever be sufficient if this is the nature of the game. 
> > 
> >With all due respect, 
> >Gary 
> 
> 


------_=_NextPart_001_01C0A282.F42F90A0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [seamoby] Yet Another BOF?</TITLE>

<META content="MSHTML 5.00.2314.1000" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face="Comic Sans MS"><SPAN class=270505218-01032001>Er, This should 
have read:</SPAN></FONT></DIV>
<DIV><FONT face="Comic Sans MS"><SPAN 
class=270505218-01032001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face="Comic Sans MS"><SPAN class=270505218-01032001>"Sorry James, . . 
. "</SPAN></FONT></DIV>
<DIV><FONT face="Comic Sans MS"><SPAN 
class=270505218-01032001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face="Comic Sans MS"><SPAN class=270505218-01032001>I re-read Phil's 
posting after sending out this message, and I failed to</SPAN></FONT></DIV>
<DIV><FONT face="Comic Sans MS"><SPAN class=270505218-01032001>see any reference 
to paging...</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face="Comic Sans MS"><SPAN 
class=270505218-01032001>Gary</SPAN></FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #000080 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Kenward, Gary 
  [WDLN2:AN10:EXCH] <BR><B>Sent:</B> Wednesday, February 28, 2001 3:19 
  PM<BR><B>To:</B> 'James Kempf'; Phil_Neumiller@3Com.com; 
  seamoby@diameter.org<BR><B>Subject:</B> RE: [seamoby] Yet Another 
  BOF?<BR><BR></DIV></FONT>
  <P><FONT size=2>Sorry Phil, I guess I misunderstood. The email in the front of 
  my</FONT> <BR><FONT size=2>mind from Phil didn't discuss paging, he was making 
  a general argument.</FONT> </P>
  <P><FONT size=2>My apologies for being confused.</FONT> </P>
  <P><FONT size=2>Gary</FONT> </P><BR>
  <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
  From: James Kempf [<A 
  href="mailto:james.kempf@sun.com">mailto:james.kempf@sun.com</A>]</FONT> 
  <BR><FONT size=2>&gt; Sent: Wednesday, February 28, 2001 3:08 PM</FONT> 
  <BR><FONT size=2>&gt; To: Kenward, Gary [WDLN2:AN10:EXCH]; 
  Phil_Neumiller@3Com.com;</FONT> <BR><FONT size=2>&gt; 
  seamoby@diameter.org</FONT> <BR><FONT size=2>&gt; Subject: RE: [seamoby] Yet 
  Another BOF?</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; Hi Gary,</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; I think you missed what I said about 
  paging.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; If you read 
  the paging problem statement draft carefully, you </FONT><BR><FONT size=2>&gt; 
  will see that </FONT><BR><FONT size=2>&gt; practically</FONT> <BR><FONT 
  size=2>&gt; everything that a paging protocol would do could be done by MIP. 
  The </FONT><BR><FONT size=2>&gt; problem is,</FONT> <BR><FONT size=2>&gt; it 
  would result in a considerable complexity increase, and </FONT><BR><FONT 
  size=2>&gt; would compromise</FONT> <BR><FONT size=2>&gt; the utility of 
  dormant mode for the mobile. Thus the </FONT><BR><FONT size=2>&gt; conclusion, 
  a paging </FONT><BR><FONT size=2>&gt; protocol for IP would be a 
  benefit.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; If the MM 
  folks can demonstrate the same w.r.t. to mobility, </FONT><BR><FONT 
  size=2>&gt; particularly </FONT><BR><FONT size=2>&gt; for security and QoS, 
  then I think a case can be made for an </FONT><BR><FONT size=2>&gt; MM 
  protocol. </FONT><BR><FONT size=2>&gt; With all due respect to the MM design 
  team and to John, the </FONT><BR><FONT size=2>&gt; draft editor, 
  </FONT><BR><FONT size=2>&gt; the draft did not present such a clear case (at 
  least, not </FONT><BR><FONT size=2>&gt; the 00 draft, I </FONT><BR><FONT 
  size=2>&gt; have yet to read the 01 draft), at least not to me.</FONT> 
  <BR><FONT size=2>&gt; If the mobile IP proponents are making these statements, 
  then it is </FONT><BR><FONT size=2>&gt; incumbent upon the MM proponents to 
  say: "Oh yeah? Show me </FONT><BR><FONT size=2>&gt; how!". If they 
  </FONT><BR><FONT size=2>&gt; can't come up with a solution, and a sketch of an 
  MM solution </FONT><BR><FONT size=2>&gt; is simpler, </FONT><BR><FONT 
  size=2>&gt; then MM is clearly the way to go. The solution doesn't have 
  </FONT><BR><FONT size=2>&gt; to be complete, </FONT><BR><FONT size=2>&gt; even 
  a simple description is usually enough to see whether </FONT><BR><FONT 
  size=2>&gt; the MIP solution </FONT><BR><FONT size=2>&gt; would be more 
  complex or compromise particular requirements. </FONT><BR><FONT size=2>&gt; 
  However, if in </FONT><BR><FONT size=2>&gt; the end, the mobile IP solution is 
  good enough, in the</FONT> <BR><FONT size=2>&gt; sense that it satisfies the 
  requirements, and the working </FONT><BR><FONT size=2>&gt; group agrees, 
  </FONT><BR><FONT size=2>&gt; then its no good going off in a huff and accusing 
  the mobile </FONT><BR><FONT size=2>&gt; IP proponents </FONT><BR><FONT 
  size=2>&gt; of stonewalling.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; I have no problem with giving the MM design team more time, since 
  the </FONT><BR><FONT size=2>&gt; problem is more complex (and I hope the IESG 
  will agree), </FONT><BR><FONT size=2>&gt; but, in the end, </FONT><BR><FONT 
  size=2>&gt; I expect to see a technically based analysis, including 
  </FONT><BR><FONT size=2>&gt; requirments and how </FONT><BR><FONT size=2>&gt; 
  mobile IP can't solve them. It's OK to dream, but the rubber </FONT><BR><FONT 
  size=2>&gt; hits the road </FONT><BR><FONT size=2>&gt; when you have to 
  explain to skeptical engineers why your </FONT><BR><FONT size=2>&gt; 
  completely new </FONT><BR><FONT size=2>&gt; solution will replace the existing 
  solution in which they've </FONT><BR><FONT size=2>&gt; invested much 
  </FONT><BR><FONT size=2>&gt; design and perhaps even implementation 
  effort.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  jak</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; At 01:18 PM 
  2/28/01 -0500, Gary Kenward wrote:</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; &gt;James:</FONT> <BR><FONT size=2>&gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt;&nbsp;&nbsp; I think you miss Phil's 
  point. It's all simply a matter of</FONT> <BR><FONT size=2>&gt; &gt;software, 
  and no doubt, with enough extensions, modifications,</FONT> <BR><FONT 
  size=2>&gt; &gt;and bit twiddling, we could turn ARP into some version of 
  a</FONT> <BR><FONT size=2>&gt; &gt;mobility protocol (or any other protocol, 
  heck, there are still</FONT> <BR><FONT size=2>&gt; &gt;people working on 
  mobile wireless ATM).</FONT> <BR><FONT size=2>&gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt;&nbsp;&nbsp;&nbsp; The frustration comes because with each 
  attempt at a</FONT> <BR><FONT size=2>&gt; &gt;problem statement, MIP 
  proponents come forth and state:</FONT> <BR><FONT size=2>&gt; &gt;"oh, well 
  sure, we can make MIP do that". No problem statement</FONT> <BR><FONT 
  size=2>&gt; &gt;for MM will ever be sufficient if this is the nature of the 
  game.</FONT> <BR><FONT size=2>&gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt;With 
  all due respect,</FONT> <BR><FONT size=2>&gt; &gt;Gary</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C0A282.F42F90A0--


From owner-seamoby@diameter.org  Thu Mar  1 15:59:10 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22761
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 15:59:09 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21K5nH21574
	for seamoby-list; Thu, 1 Mar 2001 12:05:49 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21K5lo21569
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 12:05:47 -0800
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Thu, 1 Mar 2001 14:13:50 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZV981VF>; Thu, 1 Mar 2001 14:13:52 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D24@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Hesham Soliman (ERA)'" <Hesham.Soliman@era.ericsson.se>
Cc: "'seamoby'" <seamoby@diameter.org>
Subject: RE: [seamoby] I-D ACTION:draft-ietf-seamoby-mm-problem-00.txt
Date: Thu, 1 Mar 2001 14:13:42 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

Sorry, but Glenn's observations made sense to me. He was not defining
the HA as a NAT, he was identifying that it performed Network Address
Translation, which it does. It then forwards the packets, which is what
most NAT gateways do.

Gary

> -----Original Message-----
> From: Hesham Soliman (ERA) [mailto:Hesham.Soliman@era.ericsson.se]
> Sent: Wednesday, February 28, 2001 5:04 PM
> To: Morrow, Glenn [RICH2:C330:EXCH]
> Cc: 'Michael Thomas'; seamoby@diameter.org
> Subject: RE: [seamoby] I-D ACTION:draft-ietf-seamoby-mm-problem-00.txt
> 
> 
> Hello Glenn, 
> 
> A router is a device that forwards packets from one interface to
> another. That makes a NAT a router and so is a HA. 
> A router CAN definitely tunnel, I hope you agree with that.
> 
> A NAT is a device that hides addresses on one side of the 
> network from the other side and the end nodes. Typically 
> because they are not routable. 
> A HA _does_not_hide addresses from anyone. The end nodes 
> and the entire Internet can route a MN's Home address. 
> NATs typically break end to end security and many peer to
> peer protocols. A HA doesn't.
> 
> I'm a bit surprised by your analogy and definitions but 
> I dont really think we should spend our lives looking 
> for a definition that makes a HA look like a NAT. 
> Surely there are better reasons for justifying
> the mm problem and better things to do.
> 
> Regards,
> Hesham
> 
> > -----Original Message-----
> > From:	Glenn Morrow [SMTP:gmorrow@nortelnetworks.com]
> > Sent:	Thursday, 1 March 2001 7:16
> > To:	'Hesham Soliman (ERA)'; 'Michael Thomas'
> > Cc:	seamoby@diameter.org
> > Subject:	RE: [seamoby] I-D 
> ACTION:draft-ietf-seamoby-mm-problem-00.txt
> > 
> > I don't mean to jump but IMHO here are some things to 
> realize about MIP in relation to these NAT statements: 
> > 
> > Route Optimized MIP is essentially per-host routing with 
> some signaling (BU) and a double NAT function built into the 
> end-nodes (hosts if you prefer).
> > 
> > Functionally you could decompose a MIP MN or a CN into the 
> NAT, per-host routing (binding cache) functions and the 
> "pure" host (applications) which uses the home addresses.
> > 
> > You could also think of the HA as a part of this double NAT 
> as well; albeit, it is using a tunnel to statelessly signal 
> the address translation.
> > 
> > The reason I am trying to bring this up to people is to 
> make them realize the following: 
> > 
> > - It is per-host routing. 
> > - It is double NAT (address translation at both ends) 
> > 
> > Because it is per-host routing the route tables of the 
> hosts may indeed grow large. For example, one of the hosts 
> may be a website which millions of mobile hosts communicate 
> simultaneously. Imagine a media or even just an HTTP server 
> with a million per-host route entries. 
> > 
> > Are there server companies and chip manufacturers working 
> on hardware assisted look-up engines and code to do these 
> lookups to meet the delay requirements?
> > 
> > Another approach we might take it to move the double NAT 
> and fast (per-host routing) lookup functions to the (purpose 
> built) subnet routers where they might have a chance of scaling. 
> > 
> > This might also serve to provide simultaneous route 
> optimization with location privacy and allow the existing 
> SA's between routers to be leveraged in order to avoid the 
> necessity of setting up SA's every time a mobile node wishes 
> to communicate with another node on the network.
> > 
> > I am also fairly convinced that there are solutions which 
> do not compromise the connectionless (redundant) nature of 
> IP, especially in the IPv6 case.
> > 
> > Indeed this would not be creating a new protocol to solve 
> the node mobility problem - it would be changing IP, itself, 
> to solve the node mobility problem - essentially making a new 
> "pure" IP.
> > 
> > O.K. fire away  - at least we might get off the "what is a 
> router" debate. 
> > 
> > Glenn 
> > 
> > 
> > 
> > 
> > -----Original Message----- 
> > From:   Hesham Soliman (ERA) [SMTP:Hesham.Soliman@era.ericsson.se] 
> > Sent:   Tuesday, February 27, 2001 11:25 AM 
> > To:     seamoby@cdma-2000.org 
> > Subject:        RE: [seamoby] I-D 
> ACTION:draft-ietf-seamoby-mm-problem-00.txt 
> > 
> > 
> > > >     means choosing the shortest path between two nodes 
> > > >     on the Internet. 
> > > 
> > > Can you define node ? 
> > > 
> >         => Host ? Terminal ? 
> > 
> > > >     I hope you don't mean that having a router in the 
> > > >     middle that encapsulates a packet and forwards it 
> > > >     to the right address is breaking the Internet 
> > > >     model. That _is_routing.>  
> > > 
> > > But that is not what a Home Agent does.  No user application like 
> > > email or web browsing on the internet addresses a router. 
>  The cNode 
> > > and MN in Mobile IP actually address the Home Agent which has no 
> > > user application executing on it. 
> > > 
> >         => No it doesn't address the HA, this not true at 
> all. The application 
> >         addresses the Home address of the MN. The HA receives the 
> >         packet because of its ND/ARP advertisements. I'm sure you 
> >         know that already. So I don't know why you say that. 
> > 
> > 
> > > tunnels the packet.  The inner portion of an IP tunnel is 
> the application 
> > > layer of the outer header.  So the Home Agent is in 
> effect an application 
> > > layer switch in the middle of the network which is not 
> too different than a NAT. 
> > > 
> >         => That is a gross misinterpretation of a HA. How 
> could it possibly be a NAT ? 
> >         Do I need to list all the protocols that do not 
> work through a NAT ? 
> >         A HA does not operate above L3. This is the whole 
> point behind MIP. 
> > 
> > > > 
> > > >> An 
> > > >> anchor point anywhere in the network is neither client nor 
> > > >> server nor peer and therefore 
> > > >> 
> > > >     => It's a router ! They are usually in the middle 
> > > >     and they're not clients or servers. 
> > > 
> > > See my point above.  The Home Agent is not a router.  
> > > 
> >         => Of course it's a router, define a router ? 
> >         your claims above abou it being a NAT are wrong. 
> >         The first few pages in the MIP spec tell you 
> >         that it's a router don't they ? 
> > 
> > > Non-mobile 
> > > clients, servers, and peers do not address routers.  IOW, the IP 
> > > destination address of a packet originiating from a fixed 
> client, server, or 
> > > peer on the internet is not the address of a router.  
> > > 
> >         => I think you need to reread MIP. The CN does not 
> >         address the HA. 
> > 
> > > >     => I agree, but there are ways of making it redundant 
> > > >     like any other router. 
> > > 
> > > The only way is stateful transfer which requires some state other 
> > > than IP routing to be transfered.  It's expensive an wasteful. 
> > > What about networks that want to be multihomed ? 
> > > 
> >         => I was talking about a transfer of the binding cache. 
> >         Multihoming is not an issues here is it ? 
> > 
> >         Regards, 
> >         Hesham 
> > 
> 


From owner-seamoby@diameter.org  Thu Mar  1 16:17:17 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA23584
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 16:17:16 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21KP2O21684
	for seamoby-list; Thu, 1 Mar 2001 12:25:02 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21KOxo21679
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 12:24:59 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id LAA04165;
	Thu, 1 Mar 2001 11:33:07 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABV04150;
	Thu, 1 Mar 2001 11:32:47 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA28863; Thu, 1 Mar 2001 11:32:46 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15006.41950.824600.9719@thomasm-u1.cisco.com>
Date: Thu, 1 Mar 2001 11:32:46 -0800 (PST)
To: "Gary Kenward" <gkenward@nortelnetworks.com>
Cc: "'Hesham Soliman (ERA)'" <Hesham.Soliman@era.ericsson.se>,
        "'seamoby'" <seamoby@diameter.org>
Subject: RE: [seamoby] I-D ACTION:draft-ietf-seamoby-mm-problem-00.txt
In-Reply-To: <13E2EF604DE5D111B2E50000F80824E8057A8D24@zwdld001.ca.nortel.com>
References: <13E2EF604DE5D111B2E50000F80824E8057A8D24@zwdld001.ca.nortel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


This is *really* out in the weeds, but getting
called "NAT-like" is something of a Scarlet Letter
(well, at least should be) and I think I come down
on Heshem's side on that account. Tunneling is not
the moral equivalent of NAT'ing because it:

1) Can just be thought of as an ordinary interface
   between the two routers which terminate the
   tunnel
2) Does not alter either the interior L3 headers
   and more importantly doesn't do stateful 
   inspection on the > L3 contents.

		 Mike

Gary Kenward writes:
 > Sorry, but Glenn's observations made sense to me. He was not defining
 > the HA as a NAT, he was identifying that it performed Network Address
 > Translation, which it does. It then forwards the packets, which is what
 > most NAT gateways do.
 > 
 > Gary
 > 
 > > -----Original Message-----
 > > From: Hesham Soliman (ERA) [mailto:Hesham.Soliman@era.ericsson.se]
 > > Sent: Wednesday, February 28, 2001 5:04 PM
 > > To: Morrow, Glenn [RICH2:C330:EXCH]
 > > Cc: 'Michael Thomas'; seamoby@diameter.org
 > > Subject: RE: [seamoby] I-D ACTION:draft-ietf-seamoby-mm-problem-00.txt
 > > 
 > > 
 > > Hello Glenn, 
 > > 
 > > A router is a device that forwards packets from one interface to
 > > another. That makes a NAT a router and so is a HA. 
 > > A router CAN definitely tunnel, I hope you agree with that.
 > > 
 > > A NAT is a device that hides addresses on one side of the 
 > > network from the other side and the end nodes. Typically 
 > > because they are not routable. 
 > > A HA _does_not_hide addresses from anyone. The end nodes 
 > > and the entire Internet can route a MN's Home address. 
 > > NATs typically break end to end security and many peer to
 > > peer protocols. A HA doesn't.
 > > 
 > > I'm a bit surprised by your analogy and definitions but 
 > > I dont really think we should spend our lives looking 
 > > for a definition that makes a HA look like a NAT. 
 > > Surely there are better reasons for justifying
 > > the mm problem and better things to do.
 > > 
 > > Regards,
 > > Hesham
 > > 
 > > > -----Original Message-----
 > > > From:	Glenn Morrow [SMTP:gmorrow@nortelnetworks.com]
 > > > Sent:	Thursday, 1 March 2001 7:16
 > > > To:	'Hesham Soliman (ERA)'; 'Michael Thomas'
 > > > Cc:	seamoby@diameter.org
 > > > Subject:	RE: [seamoby] I-D 
 > > ACTION:draft-ietf-seamoby-mm-problem-00.txt
 > > > 
 > > > I don't mean to jump but IMHO here are some things to 
 > > realize about MIP in relation to these NAT statements: 
 > > > 
 > > > Route Optimized MIP is essentially per-host routing with 
 > > some signaling (BU) and a double NAT function built into the 
 > > end-nodes (hosts if you prefer).
 > > > 
 > > > Functionally you could decompose a MIP MN or a CN into the 
 > > NAT, per-host routing (binding cache) functions and the 
 > > "pure" host (applications) which uses the home addresses.
 > > > 
 > > > You could also think of the HA as a part of this double NAT 
 > > as well; albeit, it is using a tunnel to statelessly signal 
 > > the address translation.
 > > > 
 > > > The reason I am trying to bring this up to people is to 
 > > make them realize the following: 
 > > > 
 > > > - It is per-host routing. 
 > > > - It is double NAT (address translation at both ends) 
 > > > 
 > > > Because it is per-host routing the route tables of the 
 > > hosts may indeed grow large. For example, one of the hosts 
 > > may be a website which millions of mobile hosts communicate 
 > > simultaneously. Imagine a media or even just an HTTP server 
 > > with a million per-host route entries. 
 > > > 
 > > > Are there server companies and chip manufacturers working 
 > > on hardware assisted look-up engines and code to do these 
 > > lookups to meet the delay requirements?
 > > > 
 > > > Another approach we might take it to move the double NAT 
 > > and fast (per-host routing) lookup functions to the (purpose 
 > > built) subnet routers where they might have a chance of scaling. 
 > > > 
 > > > This might also serve to provide simultaneous route 
 > > optimization with location privacy and allow the existing 
 > > SA's between routers to be leveraged in order to avoid the 
 > > necessity of setting up SA's every time a mobile node wishes 
 > > to communicate with another node on the network.
 > > > 
 > > > I am also fairly convinced that there are solutions which 
 > > do not compromise the connectionless (redundant) nature of 
 > > IP, especially in the IPv6 case.
 > > > 
 > > > Indeed this would not be creating a new protocol to solve 
 > > the node mobility problem - it would be changing IP, itself, 
 > > to solve the node mobility problem - essentially making a new 
 > > "pure" IP.
 > > > 
 > > > O.K. fire away  - at least we might get off the "what is a 
 > > router" debate. 
 > > > 
 > > > Glenn 
 > > > 
 > > > 
 > > > 
 > > > 
 > > > -----Original Message----- 
 > > > From:   Hesham Soliman (ERA) [SMTP:Hesham.Soliman@era.ericsson.se] 
 > > > Sent:   Tuesday, February 27, 2001 11:25 AM 
 > > > To:     seamoby@cdma-2000.org 
 > > > Subject:        RE: [seamoby] I-D 
 > > ACTION:draft-ietf-seamoby-mm-problem-00.txt 
 > > > 
 > > > 
 > > > > >     means choosing the shortest path between two nodes 
 > > > > >     on the Internet. 
 > > > > 
 > > > > Can you define node ? 
 > > > > 
 > > >         => Host ? Terminal ? 
 > > > 
 > > > > >     I hope you don't mean that having a router in the 
 > > > > >     middle that encapsulates a packet and forwards it 
 > > > > >     to the right address is breaking the Internet 
 > > > > >     model. That _is_routing.>  
 > > > > 
 > > > > But that is not what a Home Agent does.  No user application like 
 > > > > email or web browsing on the internet addresses a router. 
 > >  The cNode 
 > > > > and MN in Mobile IP actually address the Home Agent which has no 
 > > > > user application executing on it. 
 > > > > 
 > > >         => No it doesn't address the HA, this not true at 
 > > all. The application 
 > > >         addresses the Home address of the MN. The HA receives the 
 > > >         packet because of its ND/ARP advertisements. I'm sure you 
 > > >         know that already. So I don't know why you say that. 
 > > > 
 > > > 
 > > > > tunnels the packet.  The inner portion of an IP tunnel is 
 > > the application 
 > > > > layer of the outer header.  So the Home Agent is in 
 > > effect an application 
 > > > > layer switch in the middle of the network which is not 
 > > too different than a NAT. 
 > > > > 
 > > >         => That is a gross misinterpretation of a HA. How 
 > > could it possibly be a NAT ? 
 > > >         Do I need to list all the protocols that do not 
 > > work through a NAT ? 
 > > >         A HA does not operate above L3. This is the whole 
 > > point behind MIP. 
 > > > 
 > > > > > 
 > > > > >> An 
 > > > > >> anchor point anywhere in the network is neither client nor 
 > > > > >> server nor peer and therefore 
 > > > > >> 
 > > > > >     => It's a router ! They are usually in the middle 
 > > > > >     and they're not clients or servers. 
 > > > > 
 > > > > See my point above.  The Home Agent is not a router.  
 > > > > 
 > > >         => Of course it's a router, define a router ? 
 > > >         your claims above abou it being a NAT are wrong. 
 > > >         The first few pages in the MIP spec tell you 
 > > >         that it's a router don't they ? 
 > > > 
 > > > > Non-mobile 
 > > > > clients, servers, and peers do not address routers.  IOW, the IP 
 > > > > destination address of a packet originiating from a fixed 
 > > client, server, or 
 > > > > peer on the internet is not the address of a router.  
 > > > > 
 > > >         => I think you need to reread MIP. The CN does not 
 > > >         address the HA. 
 > > > 
 > > > > >     => I agree, but there are ways of making it redundant 
 > > > > >     like any other router. 
 > > > > 
 > > > > The only way is stateful transfer which requires some state other 
 > > > > than IP routing to be transfered.  It's expensive an wasteful. 
 > > > > What about networks that want to be multihomed ? 
 > > > > 
 > > >         => I was talking about a transfer of the binding cache. 
 > > >         Multihoming is not an issues here is it ? 
 > > > 
 > > >         Regards, 
 > > >         Hesham 
 > > > 
 > > 


From owner-seamoby@diameter.org  Thu Mar  1 16:45:58 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA24934
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 16:45:57 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21LMBB21986
	for seamoby-list; Thu, 1 Mar 2001 13:22:11 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21LM9o21981
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 13:22:09 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id MAA28335;
	Thu, 1 Mar 2001 12:31:37 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f21KVZB00356;
	Thu, 1 Mar 2001 12:31:35 -0800
X-mProtect:  Thu, 1 Mar 2001 12:31:35 -0800 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdruJ7PV; Thu, 01 Mar 2001 12:09:28 PST
Message-ID: <3A9EAC7A.639F41EC@iprg.nokia.com>
Date: Thu, 01 Mar 2001 12:09:30 -0800
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Gary Kenward <gkenward@nortelnetworks.com>
CC: seamoby@diameter.org
Subject: Re: [seamoby] Yet Another BOF?
References: <13E2EF604DE5D111B2E50000F80824E8057A8D1C@zwdld001.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello Gary,

That's an interesting statement.  You might apply it to
other protocols to figure out:

"well, we can make SIP do that"
"well, we can make RADIUS do that"
"well, we can make PPP do that"

Mobile IP is supposed to be pretty simple, all in all,
just a way to associate a routing address to an identifying
address as needed.  Now [seamoby-mm] is presumably going to
make some protocol that enables local routability with
better latency characteristics, in addition to the global
association managed by ("unadorned") Mobile IP.  Or,
perhaps instead of, but I don't see so much why the latter.

But, as the success of IP proves, network-layer addressing
is so powerful that it is easy to imagine ways to fiddle
with it and get a lot of cool results.

Thus, it is easy to understand
"well, we can make Mobile IP do that"...
And I don't think it's necessarily an
unfortunate thing that people are thinking
about such things.  But, on the other hand,
it's important to avoid protocol bloat and
unnecessary requirements.  To me that just
means that good engineering is required.

Regards,
Charlie P.




> Gary Kenward wrote:
> 
> It's just my perception Scott, but it seems like the response to any
> identified requirement is "well, we can make MIP do that"....
> 
> Gary
> 
> > -----Original Message-----
> > From: Scott Bradner [mailto:sob@harvard.edu]
> > Sent: Wednesday, February 28, 2001 4:03 PM
> > To: campbell@comet.columbia.edu; Kenward, Gary [WDLN2:AN10:EXCH];
> > pcalhoun@nasnfs.eng.sun.com
> > Cc: james.kempf@sun.com; Phil_Neumiller@3Com.com; seamoby@diameter.org
> > Subject: RE: [seamoby] Yet Another BOF?
> >
> >
> > anything that includes the text "That excludes vanilla MIP as
> > a solution"
> > does not look like a requirements discusison to me
> >
> > why is it so hard to discuss what the actual requirents are without
> > talking about solutions?
> >
> > Scott
> >
> >


From owner-seamoby@diameter.org  Thu Mar  1 18:40:14 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA28354
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 18:40:14 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21Mci922184
	for seamoby-list; Thu, 1 Mar 2001 14:38:44 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21McHo22179
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 14:38:17 -0800
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f21Llgg27907
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 15:47:42 -0600 (CST)
Received: from daebh02nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T52074a7258ac12f25715a@davir04nok.americas.nokia.com>;
 Thu, 1 Mar 2001 15:47:17 -0600
Received: by daebh02nok with Internet Mail Service (5.5.2652.78)
	id <GCTBSL6X>; Thu, 1 Mar 2001 15:47:17 -0600
Message-ID: <B9CFA6CE8FFDD211A1FB0008C7894E46027F445C@bseis01nok>
From: Hemant.Chaskar@nokia.com
To: mat@cisco.com, hchaskar@hotmail.com
Cc: Hesham.Soliman@era.ericsson.se, james.kempf@sun.com,
        mobile-ip@marvin.corpeast.baynetworks.com, seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
Date: Thu, 1 Mar 2001 15:47:15 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Yes, it goes end to end. But there is a basic difference illustrated 
by following example. If we look at the latency between time end nodes
are ready to use new CoA and the time QoS forwarding treatment is programmed

over the new path, it can be seen that RSVP takes one end-to-end round trip
time 
between these two events. On the other hand, including QoS object with
binding
messages performs QoS programming before the nodes release packets using
new CoA. This is shown by following illustration.

Suppose MN is currently at CoA1. Consider data traffic from the
CN towards the MN (downlink direction).

   o MN moves to CoA2.

   o MN sends BU from CoA2.

   ----[One way end-to-end delay]----

   o BU reaches CN. CN sends BA to MN at CoA2.

   In RSVP, CN sends PATH message to MN at CoA2.

   In our approach, QoS OBJECT OPTION for downlink packet stream(s)
   is included in HOP-by-HOP OPTIONS EXTENSION HEADER with the BA.

   o CN may start sending MN's packets to CoA2. These packets
   contain CoA2 as destination address. 

   **In RSVP approach, they are not identified by existing
   reservations for MN's sessions. This is because, RSVP session is
   primarily identified by destination address which now has changed
   from CoA1 to CoA2. Hence, these packets will get default
   forwarding treatment.**

   **In our approach, the packet carrying QoS information about these
   packets precedes these packets, and hence, they can get proper
   forwarding treatment.**

   ----[One way end-to-end delay]----

   o BA reaches MN at CoA2. In RSVP approach, PATH message reaches
   MN at CoA2.

   o In RSVP approach, MN sends RESV to CN.

   ----[One way end-to-end delay]----

   o In RSVP approach, RESV reaches CN. 

   **In RSVP approach, it is at this time that the proper QoS
   forwarding treatment is programmed at the intermediate network
   domains for packets destined to CoA2.**


Hemant

-----Original Message-----
From: Michael Thomas [mailto:mat@cisco.com]
Sent: 01. March 2001 13:33
To: Hemant Chaskar
Cc: Hesham.Soliman@era.ericsson.se; james.kempf@sun.com;
mobile-ip@marvin.corpeast.baynetworks.com; seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff



I don't see how this fundamentally changes
anything that James brought up. It still has to go
end to end, and it's still touching every router
in between MN and CN. 

What I do see is a lot of reinvention of RSVP
Rspec and Tspec's for no known reason.  The only
thing I can see of possible value is the ability
to piggyback the QoS update with the BU, but even
if this is the sole goal -- and that it's a worthy
goal which is not at all apparent to me -- I
imagine that there are better ways of doing this
with out reinventing RSVP: like, maybe,
piggybacking the BU on the PATH, or some such.

	     Mike


Hemant Chaskar writes:
 > Regarding the issue of round-trip latency in programming QoS forwarding 
 > treatment along new path after change in CoA:
 > 
 > This is intrinsic drawback of OPWA model of resource reservation of RSVP.
In 
 > the worst case, one round-trip time will include traversals of four
wireless 
 > links. This happens when both CN and MN are mobile.
 > 
 > Note that this drawback is eliminated in the approach to QoS signaling
based 
 > on including QoS Object in hop-by-hop options extension header along with

 > binding messages (draft-chaskar-mobileip-qos-00.txt). This draft was 
 > presented in SD and revised version (01) will be submitted soon.
 > 
 > Hemant
 > _________________________________________________________________
 > Get your FREE download of MSN Explorer at http://explorer.msn.com
 > 


From owner-seamoby@diameter.org  Thu Mar  1 18:40:19 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA28365
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 18:40:18 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21Mmit22230
	for seamoby-list; Thu, 1 Mar 2001 14:48:44 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21Mmgo22225
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 14:48:42 -0800
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate.mot.com (motgate 2.1) with ESMTP id OAA00558 for <seamoby@diameter.org>; Thu, 1 Mar 2001 14:58:19 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id OAA12760 for <seamoby@diameter.org>; Thu, 1 Mar 2001 14:58:19 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2651.58)
	id <FWT7B54Y>; Thu, 1 Mar 2001 15:58:19 -0600
Message-ID: <0DF9920C9AD8D211AB0C0008C7CF1C9A062EDE32@il27exm02.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Phil_Neumiller@3Com.com'" <Phil_Neumiller@3Com.com>,
        seamoby@diameter.org
Subject: RE: [seamoby] Yet Another BOF?
Date: Thu, 1 Mar 2001 15:58:17 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk

<foot in mouth>

I am sorry I still have another 40 email to read, so if there has been some revelation since Tuesday (Phil's email) I appologize.

I have to agree with Phil (N) here, coming back after a few days to my seamoby mail folder, I don't recognize the list. Am I still on Seamoby mailing list, or this is mobile IP all of sudden?

I thought I came here because the MIP fast handoff groups couldn't agree on a draft in San Diego. So why should I sit here on seamoby list and dodge all the HMIP, FMIP, X Y ZMIP bullets. I can read that on mobile IP mailing list, which I guess I have to resubscribe or something.

I really enjoyed the context transfer design team, because from the beginning, just like Phil said, we started from  a clean slate. Everybody was set to produce a single common draft, instead of the battle field of drafts. I learned a lot from the team and we added even different solution alternatives to indicate that making a choice between alternatives as part of the problem. Why can't the mm team do the same instead of bibliography of mobile IP?

</foot in mouth>

It is sad to see the pioneers of this group (like Phil N.) so disappointed.

In respond to Pat C., I'd say I am all for the design teams, let's continue the work. The design team were never closed, anybody can join, even somebody as dumb as me, they were just more focused on seamoby issues.



Madjid

-----Original Message-----
From: Phil_Neumiller@3Com.com [mailto:Phil_Neumiller@3Com.com]
Sent: Tuesday, February 27, 2001 5:51 PM
To: seamoby@diameter.org
Subject: [seamoby] Yet Another BOF?





After a brief history with mobility BOFs,  I am convinced that they are of
limited use.  Perhaps an
informational RFC is a better approach (not my idea).  I am convinced that many
of us (perhaps
Gary, (Andrew, James, John, Peter, and the other OBAST disciples:-))) that
wanted to build true
all IP based, edge oriented, routers with wireless cards, with a standardized
backhaul, some
how got muscled out of the IETF by the powerful forces of the MIP and MANET
groups.  We
played nice, let them hack up the charter into what is now a tenuous set of
problem statements
dangling on the edge of existence.

I for one find it difficult to contribute or create in this type of forum.  Its
completely stifling.  We need
to throw out all the assumptions and start from a clean slate.  We need to
consider the implications of
ultra-wideband, widespread deployment of MMDS/LMDS, OFDM, hybrid fiber wireless
schemes and
how they interact with mobility, and the failure of 3G.  I am tired of arguing
about the minutia of where
an FA lives or whether its macro or micro mobility.  They will all likely be
irrelevant in the forth coming
world of glass pipes everywhere (its easier to lay glass in Nebraska than in NYC
James :-)).

Some folks have approached me about another BOF.  I am convinced it would NOT be
a good thing.
An informational RFC COULD provide a way to articulate some ideas in a way that
at least gets them
documented and shared.  Some other folks have approached me about this concept.
I am in favor
of this.  How about a seamoby4g mail list?  Anybody interested in a 4g seamoby
list?  This would
get all the off charter dreamware chatter off the seamoby list.

As for the SeaMoby WG, at this point I don't know.  We have to see what happens.
It looks to me
like SeaMoby is becoming MIP's newborn cousin at this point.  Hopefully, late
term abortions aren't
allowed.

Thanks,

Phil Neumiller



From owner-seamoby@diameter.org  Thu Mar  1 18:43:30 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA28434
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 18:43:29 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21MgvA22215
	for seamoby-list; Thu, 1 Mar 2001 14:42:57 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21Mgto22210
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 14:42:55 -0800
Received: from zrchb200.us.nortel.com (actually zrchb200) 
          by smtprch1.nortel.com; Thu, 1 Mar 2001 15:30:52 -0600
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZ1PF0WZ>; Thu, 1 Mar 2001 15:30:00 -0600
Message-ID: <85AA7486A2C1D411BCA20000F8073E4351C70F@crchy271.us.nortel.com>
From: "Glenn Morrow" <gmorrow@nortelnetworks.com>
To: "'Michael Thomas'" <mat@cisco.com>, Hemant Chaskar <hchaskar@hotmail.com>
Cc: Hesham.Soliman@era.ericsson.se, james.kempf@sun.com,
        mobile-ip@marvin.corpeast.baynetworks.com, seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
Date: Thu, 1 Mar 2001 15:29:53 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A296.C11978C0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A296.C11978C0
Content-Type: text/plain

Sounds like a no-brainer to me. The handoff signaling was the question and
it looks like an ICMP solution has emerged? 

Where do you propose to put the objects there or have you not resigned
yourselves to accept the ICMP solution (i.e. do you still want to try to
push RSVP)?

I really care more about the function than the WG or the protocol choosen -
pick one.

One advantage (tenous as it may be) of putting the QoS objects in IP itself
is that it pretty much stops the argument about which protocol or WG to use
for what, when more than one function is needed. 

Extremely counter to this is the investment each party has made in existing
signaling solutions. 

With a start from scratch mentality I would put in an IP header as I feel
that it is a network layer function.


Regards,

Glenn

> -----Original Message-----
> From:	Michael Thomas [SMTP:mat@cisco.com]
> Sent:	Thursday, March 01, 2001 12:33 PM
> To:	Hemant Chaskar
> Cc:	Hesham.Soliman@era.ericsson.se; james.kempf@sun.com;
> mobile-ip@marvin.corpeast.baynetworks.com; seamoby@diameter.org
> Subject:	RE: [seamoby] Hierarchical MIP, QoS, and Handoff
> 
> 
> I don't see how this fundamentally changes
> anything that James brought up. It still has to go
> end to end, and it's still touching every router
> in between MN and CN. 
> 
> What I do see is a lot of reinvention of RSVP
> Rspec and Tspec's for no known reason.  The only
> thing I can see of possible value is the ability
> to piggyback the QoS update with the BU, but even
> if this is the sole goal -- and that it's a worthy
> goal which is not at all apparent to me -- I
> imagine that there are better ways of doing this
> with out reinventing RSVP: like, maybe,
> piggybacking the BU on the PATH, or some such.
> 
> 	     Mike
> 
> 
> Hemant Chaskar writes:
>  > Regarding the issue of round-trip latency in programming QoS forwarding
> 
>  > treatment along new path after change in CoA:
>  > 
>  > This is intrinsic drawback of OPWA model of resource reservation of
> RSVP. In 
>  > the worst case, one round-trip time will include traversals of four
> wireless 
>  > links. This happens when both CN and MN are mobile.
>  > 
>  > Note that this drawback is eliminated in the approach to QoS signaling
> based 
>  > on including QoS Object in hop-by-hop options extension header along
> with 
>  > binding messages (draft-chaskar-mobileip-qos-00.txt). This draft was 
>  > presented in SD and revised version (01) will be submitted soon.
>  > 
>  > Hemant
>  > _________________________________________________________________
>  > Get your FREE download of MSN Explorer at http://explorer.msn.com
>  > 

------_=_NextPart_001_01C0A296.C11978C0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: [seamoby] Hierarchical MIP, QoS, and Handoff</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Sounds like a =
no-brainer to me. The handoff signaling was the question and it looks =
like an ICMP solution has emerged? </FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Where do you propose =
to put the objects there or have you not resigned yourselves to accept =
the ICMP solution (i.e. do you still want to try to push =
RSVP)?</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I really care more =
about the function than the WG or the protocol choosen - pick =
one.</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">One advantage =
(tenous as it may be) of putting the QoS objects in IP itself is that =
it pretty much stops the argument about which protocol or WG to use for =
what, when more than one function is needed. </FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Extremely counter to =
this is the investment each party has made in existing signaling =
solutions. </FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">With a start from =
scratch mentality I would put in an IP header as I feel that it is a =
network layer function.</FONT>
</P>
<BR>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Regards,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Glenn</FONT>
</P>

<P><FONT SIZE=3D1 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">From:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Michael Thomas [SMTP:mat@cisco.com]</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Thursday, March 01, 2001 12:33 PM</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">Hemant Chaskar</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">Hesham.Soliman@era.ericsson.se; james.kempf@sun.com; =
mobile-ip@marvin.corpeast.baynetworks.com; =
seamoby@diameter.org</FONT></P>

<P><B><FONT SIZE=3D1 =
FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Arial">RE: [seamoby] Hierarchical MIP, QoS, =
and Handoff</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">I don't see how this fundamentally =
changes</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">anything that James brought up. It =
still has to go</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">end to end, and it's still touching =
every router</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">in between MN and CN. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">What I do see is a lot of reinvention =
of RSVP</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Rspec and Tspec's for no known =
reason.&nbsp; The only</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">thing I can see of possible value is =
the ability</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">to piggyback the QoS update with the =
BU, but even</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">if this is the sole goal -- and that =
it's a worthy</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">goal which is not at all apparent to =
me -- I</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">imagine that there are better ways of =
doing this</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">with out reinventing RSVP: like, =
maybe,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">piggybacking the BU on the PATH, or =
some such.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp; Mike</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hemant Chaskar writes:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Regarding the issue of =
round-trip latency in programming QoS forwarding </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; treatment along new path =
after change in CoA:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; This is intrinsic drawback =
of OPWA model of resource reservation of RSVP. In </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; the worst case, one =
round-trip time will include traversals of four wireless </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; links. This happens when =
both CN and MN are mobile.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Note that this drawback is =
eliminated in the approach to QoS signaling based </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; on including QoS Object in =
hop-by-hop options extension header along with </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; binding messages =
(draft-chaskar-mobileip-qos-00.txt). This draft was </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; presented in SD and =
revised version (01) will be submitted soon.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Hemant</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; =
_________________________________________________________________</FONT>=

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Get your FREE download of =
MSN Explorer at <A HREF=3D"http://explorer.msn.com" =
TARGET=3D"_blank">http://explorer.msn.com</A></FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A296.C11978C0--


From owner-seamoby@diameter.org  Thu Mar  1 18:50:00 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA28636
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 18:49:59 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21N9kF22316
	for seamoby-list; Thu, 1 Mar 2001 15:09:46 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21N9ho22311
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 15:09:43 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id OAA02681;
	Thu, 1 Mar 2001 14:19:32 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABV08482;
	Thu, 1 Mar 2001 14:19:13 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id OAA28891; Thu, 1 Mar 2001 14:19:13 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
Message-ID: <15006.51937.60735.267223@thomasm-u1.cisco.com>
Date: Thu, 1 Mar 2001 14:19:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Hemant.Chaskar@nokia.com
Cc: mat@cisco.com, hchaskar@hotmail.com, Hesham.Soliman@era.ericsson.se,
        james.kempf@sun.com, mobile-ip@sunroof.eng.sun.com,
        seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
In-Reply-To: <B9CFA6CE8FFDD211A1FB0008C7894E46027F445C@bseis01nok>
References: <B9CFA6CE8FFDD211A1FB0008C7894E46027F445C@bseis01nok>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I really don't even know where to begin. It seems
that your claim is that RSVP's receiver oriented
PATH/RESV is either flawed, or should have a mode
which allows a single pass. I believe this leads
to overbooking for multicast since you don't get
to do flow merging properly and a host of other
reasons that I don't purport to understand well.

What I really don't understand is why MIP would be
the right place to solve this problem. If it has
merit, the RSVP folks seems like a much more
appropriate set of people to entertain such a
proposal. I suspect that they'd be able to supply
a lot more reasons why they designed RSVP the way
they did. Suggesting that mobileip is a breed
apart that requires its own QoS mechanisms sounds
just as wrong headed as RSVP folks designing their
own mobility protocol.

		Mike

Hemant.Chaskar@nokia.com writes:
 > Yes, it goes end to end. But there is a basic difference illustrated 
 > by following example. If we look at the latency between time end nodes
 > are ready to use new CoA and the time QoS forwarding treatment is programmed
 > 
 > over the new path, it can be seen that RSVP takes one end-to-end round trip
 > time 
 > between these two events. On the other hand, including QoS object with
 > binding
 > messages performs QoS programming before the nodes release packets using
 > new CoA. This is shown by following illustration.
 > 
 > Suppose MN is currently at CoA1. Consider data traffic from the
 > CN towards the MN (downlink direction).
 > 
 >    o MN moves to CoA2.
 > 
 >    o MN sends BU from CoA2.
 > 
 >    ----[One way end-to-end delay]----
 > 
 >    o BU reaches CN. CN sends BA to MN at CoA2.
 > 
 >    In RSVP, CN sends PATH message to MN at CoA2.
 > 
 >    In our approach, QoS OBJECT OPTION for downlink packet stream(s)
 >    is included in HOP-by-HOP OPTIONS EXTENSION HEADER with the BA.
 > 
 >    o CN may start sending MN's packets to CoA2. These packets
 >    contain CoA2 as destination address. 
 > 
 >    **In RSVP approach, they are not identified by existing
 >    reservations for MN's sessions. This is because, RSVP session is
 >    primarily identified by destination address which now has changed
 >    from CoA1 to CoA2. Hence, these packets will get default
 >    forwarding treatment.**
 > 
 >    **In our approach, the packet carrying QoS information about these
 >    packets precedes these packets, and hence, they can get proper
 >    forwarding treatment.**
 > 
 >    ----[One way end-to-end delay]----
 > 
 >    o BA reaches MN at CoA2. In RSVP approach, PATH message reaches
 >    MN at CoA2.
 > 
 >    o In RSVP approach, MN sends RESV to CN.
 > 
 >    ----[One way end-to-end delay]----
 > 
 >    o In RSVP approach, RESV reaches CN. 
 > 
 >    **In RSVP approach, it is at this time that the proper QoS
 >    forwarding treatment is programmed at the intermediate network
 >    domains for packets destined to CoA2.**
 > 
 > 
 > Hemant
 > 
 > -----Original Message-----
 > From: Michael Thomas [mailto:mat@cisco.com]
 > Sent: 01. March 2001 13:33
 > To: Hemant Chaskar
 > Cc: Hesham.Soliman@era.ericsson.se; james.kempf@sun.com;
 > mobile-ip@marvin.corpeast.baynetworks.com; seamoby@diameter.org
 > Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
 > 
 > 
 > 
 > I don't see how this fundamentally changes
 > anything that James brought up. It still has to go
 > end to end, and it's still touching every router
 > in between MN and CN. 
 > 
 > What I do see is a lot of reinvention of RSVP
 > Rspec and Tspec's for no known reason.  The only
 > thing I can see of possible value is the ability
 > to piggyback the QoS update with the BU, but even
 > if this is the sole goal -- and that it's a worthy
 > goal which is not at all apparent to me -- I
 > imagine that there are better ways of doing this
 > with out reinventing RSVP: like, maybe,
 > piggybacking the BU on the PATH, or some such.
 > 
 > 	     Mike
 > 
 > 
 > Hemant Chaskar writes:
 >  > Regarding the issue of round-trip latency in programming QoS forwarding 
 >  > treatment along new path after change in CoA:
 >  > 
 >  > This is intrinsic drawback of OPWA model of resource reservation of RSVP.
 > In 
 >  > the worst case, one round-trip time will include traversals of four
 > wireless 
 >  > links. This happens when both CN and MN are mobile.
 >  > 
 >  > Note that this drawback is eliminated in the approach to QoS signaling
 > based 
 >  > on including QoS Object in hop-by-hop options extension header along with
 > 
 >  > binding messages (draft-chaskar-mobileip-qos-00.txt). This draft was 
 >  > presented in SD and revised version (01) will be submitted soon.
 >  > 
 >  > Hemant
 >  > _________________________________________________________________
 >  > Get your FREE download of MSN Explorer at http://explorer.msn.com
 >  > 


From owner-seamoby@diameter.org  Thu Mar  1 18:50:44 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA28664
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 18:50:44 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21NH6p22342
	for seamoby-list; Thu, 1 Mar 2001 15:17:06 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21NH2o22337
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 15:17:02 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA11717;
	Thu, 1 Mar 2001 14:26:31 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA18851;
	Thu, 1 Mar 2001 14:26:31 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id OAA27260;
	Thu, 1 Mar 2001 14:26:29 -0800 (PST)
Date: Thu, 1 Mar 2001 14:22:07 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: RE: [seamoby] Yet Another BOF?
To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
Cc: "'Phil_Neumiller@3Com.com'" <Phil_Neumiller@3Com.com>,
        seamoby@diameter.org
In-Reply-To: "Your message with ID" <0DF9920C9AD8D211AB0C0008C7CF1C9A062EDE32@il27exm02.cig.mot.com>
Message-ID: <Roam.SIMC.2.0.6.983485327.28264.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> I am sorry I still have another 40 email to read, so if there has been some
> revelation since Tuesday (Phil's email) I appologize.
> 
> I have to agree with Phil (N) here, coming back after a few days to my
> seamoby mail folder, I don't recognize the list. Am I still on Seamoby
> mailing list, or this is mobile IP all of sudden?

Well, Phil CC'ed the Mobile IP list, so yes you have been reading e-mail from
people on the Mobile IP list. As I have previously stated, this is a bad
idea... very bad idea. 

So, let's just forget about the past and focus on what's next, and keep it
within this list.

> I thought I came here because the MIP fast handoff groups couldn't agree on
> a draft in San Diego. So why should I sit here on seamoby list and dodge all
> the HMIP, FMIP, X Y ZMIP bullets. I can read that on mobile IP mailing list,
> which I guess I have to resubscribe or something.

Nope. Not at all. That is far from the reason why Seamoby was created. Fast
handoff within the MIP protocol has been on the Mobile IP charter for longer
than this WG has existed.

We were created to offload the Mobile IP WG with non-Mobile IP related issues,
such as CIP, Hawaii, etc. (this is in addition to paging and context transfer,
of course).

> 
> I really enjoyed the context transfer design team, because from the
> beginning, just like Phil said, we started from  a clean slate. Everybody
> was set to produce a single common draft, instead of the battle field of
> drafts. I learned a lot from the team and we added even different solution
> alternatives to indicate that making a choice between alternatives as part
> of the problem. Why can't the mm team do the same instead of bibliography of
> mobile IP?

hmmmm.....

As many of us have stated in the past (including the ADs), simply define the
problem space. Forget about the few that will constantly state that this is
possible within the MIP framework. Of course! It's software, so you can do
anything with it. The better question is whether it makes sense to change MIP
to do what we need.

Anyways, the MM team put together -01, and it is looking quite good, but does
require some additional work, and -02 will be forthcoming, I'm sure. I will be
sitting down with the ADs in Minn. to work out a plan.

> It is sad to see the pioneers of this group (like Phil N.) so disappointed.

well, if we could get past the few that will constantly state that it MIP can
be used as a kitchen sink grinder, floor wax and a desert topping, and focus
on work, perhaps Phil N will be happier...

> 
> In respond to Pat C., I'd say I am all for the design teams, let's continue
> the work. The design team were never closed, anybody can join, even somebody
> as dumb as me, they were just more focused on seamoby issues.

Good, that's the response I seem to get most often.

PatC



From owner-seamoby@diameter.org  Thu Mar  1 18:53:55 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA28739
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 18:53:53 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21NIMJ22351
	for seamoby-list; Thu, 1 Mar 2001 15:18:22 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21NIKo22346
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 15:18:20 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f21MQUo08495;
	Thu, 1 Mar 2001 14:26:30 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f21MRpX16576;
	Thu, 1 Mar 2001 14:27:51 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A02.007B8A35 ; Thu, 1 Mar 2001 14:29:23 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
cc: Gary Kenward <gkenward@nortelnetworks.com>, seamoby@diameter.org
Message-ID: <88256A02.007B6BCB.00@hqoutbound.ops.3com.com>
Date: Thu, 1 Mar 2001 16:25:31 -0600
Subject: Re: [seamoby] Yet Another BOF?
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk




Hi Charlie,

.begin  :-) :-O  <- (foot)  :-)

Many pundits state (maybe its in your new book :-)) that mobile hosts will soon
out number fixed hosts.  This makes me think its a good thing that MIP is
becoming the Swiss army knife of mobility.  My thoughts now are that mobility
should be completely embedded into IPvX itself.  Thus MIP should be selectively
absorbed into IP.  IPv6 took some steps in that direction.  Of course a process
such as this would take years.  Why should mobility be separate from the routing
fabric of the global Internet if most the hosts are mobile?

I think its interesting how a double standard has been applied to the rigour
used
when developing macro and micro techniques,  We have been told that qualitative
words like fast wont do yet the  MIP "fast" handoff work is littered with them.

Do you think IPv4 / IPv6 bi-furcated MIP with fast smooth and HMIP will still be
pretty simple when all is RFCd?

People have tried to solve all kinds of problems with SIP and PPP and RADIUS
in places where something else would have worked better.  So I don't understand
your point.  You know the old idiom, if your only  tool is a hammer, everything
looks
like a nail.  In the case of mobility problems, people come to the IETF and see
one mobility tool RFC 2002 (there are some screwdrivers and wrenches being
worked on).

You said un-adorned meaning no speed tricks right?  If not, then better latency
characteristics begs the question of what baseline?  Does the MIP WG expect the
SeaMoby WG to predict how "fast" fast is?   Even unadorned how would SeaMoby
determine a baseline considered fair by all?  Also, this work as James has
indicated would take analytical modelling, simulation, and possibly prototypes
and
or measurement.

Thank you,

Phil Neumiller




Sent by:  "Charles E. Perkins" <charliep@iprg.nokia.com>


To:   Gary Kenward <gkenward@nortelnetworks.com>
cc:   seamoby@diameter.org (Phil Neumiller/MW/US/3Com)
Subject:  Re: [seamoby] Yet Another BOF?




Hello Gary,

That's an interesting statement.  You might apply it to
other protocols to figure out:

"well, we can make SIP do that"
"well, we can make RADIUS do that"
"well, we can make PPP do that"

Mobile IP is supposed to be pretty simple, all in all,
just a way to associate a routing address to an identifying
address as needed.  Now [seamoby-mm] is presumably going to
make some protocol that enables local routability with
better latency characteristics, in addition to the global
association managed by ("unadorned") Mobile IP.  Or,
perhaps instead of, but I don't see so much why the latter.

But, as the success of IP proves, network-layer addressing
is so powerful that it is easy to imagine ways to fiddle
with it and get a lot of cool results.

Thus, it is easy to understand
"well, we can make Mobile IP do that"...
And I don't think it's necessarily an
unfortunate thing that people are thinking
about such things.  But, on the other hand,
it's important to avoid protocol bloat and
unnecessary requirements.  To me that just
means that good engineering is required.

Regards,
Charlie P.




> Gary Kenward wrote:
>
> It's just my perception Scott, but it seems like the response to any
> identified requirement is "well, we can make MIP do that"....
>
> Gary
>
> > -----Original Message-----
> > From: Scott Bradner [mailto:sob@harvard.edu]
> > Sent: Wednesday, February 28, 2001 4:03 PM
> > To: campbell@comet.columbia.edu; Kenward, Gary [WDLN2:AN10:EXCH];
> > pcalhoun@nasnfs.eng.sun.com
> > Cc: james.kempf@sun.com; Phil_Neumiller@3Com.com; seamoby@diameter.org
> > Subject: RE: [seamoby] Yet Another BOF?
> >
> >
> > anything that includes the text "That excludes vanilla MIP as
> > a solution"
> > does not look like a requirements discusison to me
> >
> > why is it so hard to discuss what the actual requirents are without
> > talking about solutions?
> >
> > Scott
> >
> >






From owner-seamoby@diameter.org  Thu Mar  1 19:17:36 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA29256
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 19:17:35 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21NoZt22434
	for seamoby-list; Thu, 1 Mar 2001 15:50:35 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21NoWo22429
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 15:50:32 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id HAA142334;
	Fri, 2 Mar 2001 07:50:06 +0900
Received: from zrchh190 by smtprch2.nortel.com; Thu, 1 Mar 2001 15:37:22 -0600
Received: from marvin.corpeast.baynetworks.com by zrchh190;
          Thu, 1 Mar 2001 15:40:20 -0600
Received: from zrchb200.us.nortel.com (zrchb200.us.nortel.com [47.100.129.29]) 
          by marvin.corpeast.baynetworks.com (8.8.8+Sun/8.8.8) with ESMTP 
          id QAA06248 for <mobile-ip@marvin.corpeast.baynetworks.com>;
          Thu, 1 Mar 2001 16:30:22 -0500 (EST)
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZ1PF0WZ>; Thu, 1 Mar 2001 15:30:00 -0600
Message-ID: <85AA7486A2C1D411BCA20000F8073E4351C70F@crchy271.us.nortel.com>
From: "Glenn Morrow" <gmorrow@nortelnetworks.com>
To: "'Michael Thomas'" <mat@cisco.com>, Hemant Chaskar <hchaskar@hotmail.com>
Cc: Hesham.Soliman@era.ericsson.se, james.kempf@sun.com,
        mobile-ip@marvin.corpeast.baynetworks.com, seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
Date: Thu, 1 Mar 2001 15:29:53 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A296.C11978C0"
X-Orig: <ronyoung@nortelnetworks.com>
X-Orig: <ronyoung@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A296.C11978C0
Content-Type: text/plain

Sounds like a no-brainer to me. The handoff signaling was the question and
it looks like an ICMP solution has emerged? 

Where do you propose to put the objects there or have you not resigned
yourselves to accept the ICMP solution (i.e. do you still want to try to
push RSVP)?

I really care more about the function than the WG or the protocol choosen -
pick one.

One advantage (tenous as it may be) of putting the QoS objects in IP itself
is that it pretty much stops the argument about which protocol or WG to use
for what, when more than one function is needed. 

Extremely counter to this is the investment each party has made in existing
signaling solutions. 

With a start from scratch mentality I would put in an IP header as I feel
that it is a network layer function.


Regards,

Glenn

> -----Original Message-----
> From: Michael Thomas [SMTP:mat@cisco.com]
> Sent: Thursday, March 01, 2001 12:33 PM
> To: Hemant Chaskar
> Cc: Hesham.Soliman@era.ericsson.se; james.kempf@sun.com;
> mobile-ip@marvin.corpeast.baynetworks.com; seamoby@diameter.org
> Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
> 
> 
> I don't see how this fundamentally changes
> anything that James brought up. It still has to go
> end to end, and it's still touching every router
> in between MN and CN. 
> 
> What I do see is a lot of reinvention of RSVP
> Rspec and Tspec's for no known reason.  The only
> thing I can see of possible value is the ability
> to piggyback the QoS update with the BU, but even
> if this is the sole goal -- and that it's a worthy
> goal which is not at all apparent to me -- I
> imagine that there are better ways of doing this
> with out reinventing RSVP: like, maybe,
> piggybacking the BU on the PATH, or some such.
> 
>       Mike
> 
> 
> Hemant Chaskar writes:
>  > Regarding the issue of round-trip latency in programming QoS forwarding
> 
>  > treatment along new path after change in CoA:
>  > 
>  > This is intrinsic drawback of OPWA model of resource reservation of
> RSVP. In 
>  > the worst case, one round-trip time will include traversals of four
> wireless 
>  > links. This happens when both CN and MN are mobile.
>  > 
>  > Note that this drawback is eliminated in the approach to QoS signaling
> based 
>  > on including QoS Object in hop-by-hop options extension header along
> with 
>  > binding messages (draft-chaskar-mobileip-qos-00.txt). This draft was 
>  > presented in SD and revised version (01) will be submitted soon.
>  > 
>  > Hemant
>  > _________________________________________________________________
>  > Get your FREE download of MSN Explorer at http://explorer.msn.com
>  > 

------_=_NextPart_001_01C0A296.C11978C0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: [seamoby] Hierarchical MIP, QoS, and Handoff</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Sounds like a =
no-brainer to me. The handoff signaling was the question and it looks =
like an ICMP solution has emerged? </FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Where do you propose =
to put the objects there or have you not resigned yourselves to accept =
the ICMP solution (i.e. do you still want to try to push =
RSVP)?</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I really care more =
about the function than the WG or the protocol choosen - pick =
one.</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">One advantage =
(tenous as it may be) of putting the QoS objects in IP itself is that =
it pretty much stops the argument about which protocol or WG to use for =
what, when more than one function is needed. </FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Extremely counter to =
this is the investment each party has made in existing signaling =
solutions. </FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">With a start from =
scratch mentality I would put in an IP header as I feel that it is a =
network layer function.</FONT>
</P>
<BR>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Regards,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Glenn</FONT>
</P>

<P><FONT SIZE=3D1 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">From:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Michael Thomas [SMTP:mat@cisco.com]</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Thursday, March 01, 2001 12:33 PM</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">Hemant Chaskar</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">Hesham.Soliman@era.ericsson.se; james.kempf@sun.com; =
mobile-ip@marvin.corpeast.baynetworks.com; =
seamoby@diameter.org</FONT></P>

<P><B><FONT SIZE=3D1 =
FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Arial">RE: [seamoby] Hierarchical MIP, QoS, =
and Handoff</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">I don't see how this fundamentally =
changes</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">anything that James brought up. It =
still has to go</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">end to end, and it's still touching =
every router</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">in between MN and CN. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">What I do see is a lot of reinvention =
of RSVP</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Rspec and Tspec's for no known =
reason.&nbsp; The only</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">thing I can see of possible value is =
the ability</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">to piggyback the QoS update with the =
BU, but even</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">if this is the sole goal -- and that =
it's a worthy</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">goal which is not at all apparent to =
me -- I</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">imagine that there are better ways of =
doing this</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">with out reinventing RSVP: like, =
maybe,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">piggybacking the BU on the PATH, or =
some such.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp; Mike</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hemant Chaskar writes:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Regarding the issue of =
round-trip latency in programming QoS forwarding </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; treatment along new path =
after change in CoA:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; This is intrinsic drawback =
of OPWA model of resource reservation of RSVP. In </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; the worst case, one =
round-trip time will include traversals of four wireless </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; links. This happens when =
both CN and MN are mobile.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Note that this drawback is =
eliminated in the approach to QoS signaling based </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; on including QoS Object in =
hop-by-hop options extension header along with </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; binding messages =
(draft-chaskar-mobileip-qos-00.txt). This draft was </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; presented in SD and =
revised version (01) will be submitted soon.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Hemant</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; =
_________________________________________________________________</FONT>=

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Get your FREE download of =
MSN Explorer at <A HREF=3D"http://explorer.msn.com" =
TARGET=3D"_blank">http://explorer.msn.com</A></FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A296.C11978C0--



From owner-seamoby@diameter.org  Thu Mar  1 19:20:05 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA29311
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 19:20:04 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21Nmws22410
	for seamoby-list; Thu, 1 Mar 2001 15:48:58 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21Nmso22405
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 15:48:55 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id HAA149286;
	Fri, 2 Mar 2001 07:48:07 +0900
Received: from zrchh190 by smtprch2.nortel.com; Thu, 1 Mar 2001 15:34:07 -0600
Received: from marvin.corpeast.baynetworks.com by zrchh190;
          Thu, 1 Mar 2001 15:38:19 -0600
Received: from zrchb200.us.nortel.com (zrchb200.us.nortel.com [47.100.129.29]) 
          by marvin.corpeast.baynetworks.com (8.8.8+Sun/8.8.8) with ESMTP 
          id QAA06248 for <mobile-ip@marvin.corpeast.baynetworks.com>;
          Thu, 1 Mar 2001 16:30:22 -0500 (EST)
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZ1PF0WZ>; Thu, 1 Mar 2001 15:30:00 -0600
Message-ID: <85AA7486A2C1D411BCA20000F8073E4351C70F@crchy271.us.nortel.com>
From: "Glenn Morrow" <gmorrow@nortelnetworks.com>
To: "'Michael Thomas'" <mat@cisco.com>, Hemant Chaskar <hchaskar@hotmail.com>
Cc: Hesham.Soliman@era.ericsson.se, james.kempf@sun.com,
        mobile-ip@marvin.corpeast.baynetworks.com, seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
Date: Thu, 1 Mar 2001 15:29:53 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A296.C11978C0"
X-Orig: <ronyoung@nortelnetworks.com>
X-Orig: <ronyoung@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A296.C11978C0
Content-Type: text/plain

Sounds like a no-brainer to me. The handoff signaling was the question and
it looks like an ICMP solution has emerged? 

Where do you propose to put the objects there or have you not resigned
yourselves to accept the ICMP solution (i.e. do you still want to try to
push RSVP)?

I really care more about the function than the WG or the protocol choosen -
pick one.

One advantage (tenous as it may be) of putting the QoS objects in IP itself
is that it pretty much stops the argument about which protocol or WG to use
for what, when more than one function is needed. 

Extremely counter to this is the investment each party has made in existing
signaling solutions. 

With a start from scratch mentality I would put in an IP header as I feel
that it is a network layer function.


Regards,

Glenn

> -----Original Message-----
> From: Michael Thomas [SMTP:mat@cisco.com]
> Sent: Thursday, March 01, 2001 12:33 PM
> To: Hemant Chaskar
> Cc: Hesham.Soliman@era.ericsson.se; james.kempf@sun.com;
> mobile-ip@marvin.corpeast.baynetworks.com; seamoby@diameter.org
> Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
> 
> 
> I don't see how this fundamentally changes
> anything that James brought up. It still has to go
> end to end, and it's still touching every router
> in between MN and CN. 
> 
> What I do see is a lot of reinvention of RSVP
> Rspec and Tspec's for no known reason.  The only
> thing I can see of possible value is the ability
> to piggyback the QoS update with the BU, but even
> if this is the sole goal -- and that it's a worthy
> goal which is not at all apparent to me -- I
> imagine that there are better ways of doing this
> with out reinventing RSVP: like, maybe,
> piggybacking the BU on the PATH, or some such.
> 
>       Mike
> 
> 
> Hemant Chaskar writes:
>  > Regarding the issue of round-trip latency in programming QoS forwarding
> 
>  > treatment along new path after change in CoA:
>  > 
>  > This is intrinsic drawback of OPWA model of resource reservation of
> RSVP. In 
>  > the worst case, one round-trip time will include traversals of four
> wireless 
>  > links. This happens when both CN and MN are mobile.
>  > 
>  > Note that this drawback is eliminated in the approach to QoS signaling
> based 
>  > on including QoS Object in hop-by-hop options extension header along
> with 
>  > binding messages (draft-chaskar-mobileip-qos-00.txt). This draft was 
>  > presented in SD and revised version (01) will be submitted soon.
>  > 
>  > Hemant
>  > _________________________________________________________________
>  > Get your FREE download of MSN Explorer at http://explorer.msn.com
>  > 

------_=_NextPart_001_01C0A296.C11978C0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: [seamoby] Hierarchical MIP, QoS, and Handoff</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Sounds like a =
no-brainer to me. The handoff signaling was the question and it looks =
like an ICMP solution has emerged? </FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Where do you propose =
to put the objects there or have you not resigned yourselves to accept =
the ICMP solution (i.e. do you still want to try to push =
RSVP)?</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I really care more =
about the function than the WG or the protocol choosen - pick =
one.</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">One advantage =
(tenous as it may be) of putting the QoS objects in IP itself is that =
it pretty much stops the argument about which protocol or WG to use for =
what, when more than one function is needed. </FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Extremely counter to =
this is the investment each party has made in existing signaling =
solutions. </FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">With a start from =
scratch mentality I would put in an IP header as I feel that it is a =
network layer function.</FONT>
</P>
<BR>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Regards,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Glenn</FONT>
</P>

<P><FONT SIZE=3D1 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">From:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Michael Thomas [SMTP:mat@cisco.com]</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Thursday, March 01, 2001 12:33 PM</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">Hemant Chaskar</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">Hesham.Soliman@era.ericsson.se; james.kempf@sun.com; =
mobile-ip@marvin.corpeast.baynetworks.com; =
seamoby@diameter.org</FONT></P>

<P><B><FONT SIZE=3D1 =
FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Arial">RE: [seamoby] Hierarchical MIP, QoS, =
and Handoff</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">I don't see how this fundamentally =
changes</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">anything that James brought up. It =
still has to go</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">end to end, and it's still touching =
every router</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">in between MN and CN. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">What I do see is a lot of reinvention =
of RSVP</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Rspec and Tspec's for no known =
reason.&nbsp; The only</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">thing I can see of possible value is =
the ability</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">to piggyback the QoS update with the =
BU, but even</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">if this is the sole goal -- and that =
it's a worthy</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">goal which is not at all apparent to =
me -- I</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">imagine that there are better ways of =
doing this</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">with out reinventing RSVP: like, =
maybe,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">piggybacking the BU on the PATH, or =
some such.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp; Mike</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hemant Chaskar writes:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Regarding the issue of =
round-trip latency in programming QoS forwarding </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; treatment along new path =
after change in CoA:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; This is intrinsic drawback =
of OPWA model of resource reservation of RSVP. In </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; the worst case, one =
round-trip time will include traversals of four wireless </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; links. This happens when =
both CN and MN are mobile.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Note that this drawback is =
eliminated in the approach to QoS signaling based </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; on including QoS Object in =
hop-by-hop options extension header along with </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; binding messages =
(draft-chaskar-mobileip-qos-00.txt). This draft was </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; presented in SD and =
revised version (01) will be submitted soon.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Hemant</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; =
_________________________________________________________________</FONT>=

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Get your FREE download of =
MSN Explorer at <A HREF=3D"http://explorer.msn.com" =
TARGET=3D"_blank">http://explorer.msn.com</A></FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A296.C11978C0--



From owner-seamoby@diameter.org  Thu Mar  1 19:29:05 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA29501
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 19:29:05 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f220FiZ22514
	for seamoby-list; Thu, 1 Mar 2001 16:15:44 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f220Ffo22509
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 16:15:41 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id PAA02769;
	Thu, 1 Mar 2001 15:25:30 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABV10214;
	Thu, 1 Mar 2001 15:25:11 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id PAA28908; Thu, 1 Mar 2001 15:25:11 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15006.55894.888121.239760@thomasm-u1.cisco.com>
Date: Thu, 1 Mar 2001 15:25:10 -0800 (PST)
To: "Glenn Morrow" <gmorrow@nortelnetworks.com>
Cc: "'Michael Thomas'" <mat@cisco.com>, Hemant Chaskar <hchaskar@hotmail.com>,
        Hesham.Soliman@era.ericsson.se, james.kempf@sun.com,
        mobile-ip@marvin.corpeast.baynetworks.com, seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
In-Reply-To: <85AA7486A2C1D411BCA20000F8073E4351C70F@crchy271.us.nortel.com>
References: <85AA7486A2C1D411BCA20000F8073E4351C70F@crchy271.us.nortel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Glenn Morrow writes:
 > Sounds like a no-brainer to me. The handoff signaling was the question and
 > it looks like an ICMP solution has emerged? 
 > 
 > Where do you propose to put the objects there or have you not resigned
 > yourselves to accept the ICMP solution (i.e. do you still want to try to
 > push RSVP)?

   It took me a while to grok what you were talking
   about. I'm still not certain I'm reading it
   correctly.

   The answer about RSVP is no. The RSVP thingy
   probably is still an interesting angle on the
   BURP BOF (though, mainly from a requirements
   angle at this point.)

   But I thought that the handoff signling
   supposedly emerging was the HI/HACK for fast
   handoffs which is orthogonal to what's being
   discussed here.

 > One advantage (tenous as it may be) of putting the QoS objects in IP itself
 > is that it pretty much stops the argument about which protocol or WG to use
 > for what, when more than one function is needed. 
 > 
 > Extremely counter to this is the investment each party has made in existing
 > signaling solutions. 

   I guess I'd like to keep some semblance of
   modularity where we can find it. I'm innately
   suspicious of the argument "protocol X is 
   can't possibly be used in situation Y because
   it (and it alone usually) is unique." IETF
   protocol are surprisingly resilient all in all.

		Mike
   


From owner-seamoby@diameter.org  Thu Mar  1 19:30:43 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA29569
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 19:30:42 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f220HMc22528
	for seamoby-list; Thu, 1 Mar 2001 16:17:22 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f220HKo22522
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 16:17:20 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f21NPVo19875;
	Thu, 1 Mar 2001 15:25:31 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f21NQqX06278;
	Thu, 1 Mar 2001 15:26:52 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A02.0080F11B ; Thu, 1 Mar 2001 15:28:23 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
cc: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        seamoby@diameter.org
Message-ID: <88256A02.0080EC8F.00@hqoutbound.ops.3com.com>
Date: Thu, 1 Mar 2001 17:25:20 -0600
Subject: RE: [seamoby] Yet Another BOF?
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk



A few corrections,  :-O <- (FOOT) :-)




Please respond to Pat Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>



> I am sorry I still have another 40 email to read, so if there has been some
> revelation since Tuesday (Phil's email) I appologize.
>
> I have to agree with Phil (N) here, coming back after a few days to my
> seamoby mail folder, I don't recognize the list. Am I still on Seamoby
> mailing list, or this is mobile IP all of sudden?

Well, Phil CC'ed the Mobile IP list, so yes you have been reading e-mail from
people on the Mobile IP list. As I have previously stated, this is a bad
idea... very bad idea.

pdn>That email was very MUCH intended for both groups.  Bad idea?  Maybe.
pdn>I thought it stimulated a fairly useful thread with a short life.
pdn>The answer I got from Raj may be of interest to the micmob des team.
pdn>If the COA changes (and there is no MIP) infrastructure, it is
pdn>considered micromobility!  I can site some examples to explain this.

So, let's just forget about the past and focus on what's next, and keep it
within this list.


> I thought I came here because the MIP fast handoff groups couldn't agree on
> a draft in San Diego. So why should I sit here on seamoby list and dodge all
> the HMIP, FMIP, X Y ZMIP bullets. I can read that I

Nope. Not at all. That is far from the reason why Seamoby was created. Fast
handoff within the MIP protocol has been on the Mobile IP charter for longer
than this WG has existed.

We were created to offload the Mobile IP WG with non-Mobile IP related issues,
such as CIP, Hawaii, etc. (this is in addition to paging and context transfer,
of course).

pdn>Yes, indeed SeaMoby currently has a completely mobile IP inspired charter.
pdn>You would think that the OBAST BOF never happened the CRAPS BOF never
pdn>happened since absolutely nothing from those BOFs made it to charter.
pdn>Those drafts, that work, is pretty much in limbo.  The only perceived
pdn>important thing for SeaMoby is to work on the stuff that Mobile IP wishes
pdn>to expel (at least this the way the IESG constructed the WG).

> It is sad to see the pioneers of this group (like Phil N.) so disappointed.

well, if we could get past the few that will constantly state that it MIP can
be used as a kitchen sink grinder, floor wax and a desert topping, and focus
on work, perhaps Phil N will be happier...

pdn>Phil N. might have been happier with a different charter!  Phil N.  may
pdn>never be happy!  Phil N. might be happier with a different chair!  JK Pat

Phil









From owner-seamoby@diameter.org  Thu Mar  1 19:50:45 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA00024
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 19:50:45 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f220BYV22503
	for seamoby-list; Thu, 1 Mar 2001 16:11:34 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f220BVo22498
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 16:11:31 -0800
Received: [from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate.mot.com (motgate 2.1) with ESMTP id QAA10350 for <seamoby@diameter.org>; Thu, 1 Mar 2001 16:21:08 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id QAA19835 for <seamoby@diameter.org>; Thu, 1 Mar 2001 16:21:08 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2651.58)
	id <13DS6BK9>; Thu, 1 Mar 2001 17:21:08 -0600
Message-ID: <0DF9920C9AD8D211AB0C0008C7CF1C9A062EDE37@il27exm02.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Phil_Neumiller@3Com.com'" <Phil_Neumiller@3Com.com>,
        seamoby@diameter.org
Cc: "'Pat Calhoun'" <pcalhoun@nasnfs.eng.sun.com>,
        Nakhjiri Madjid-MNAKHJI1
	 <Madjid.Nakhjiri@motorola.com>
Subject:  [seamoby] Yet Another BOF?
Date: Thu, 1 Mar 2001 17:21:06 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk


<snip>

Nope. Not at all. That is far from the reason why Seamoby was created. Fast
handoff within the MIP protocol has been on the Mobile IP charter for longer
than this WG has existed.

We were created to offload the Mobile IP WG with non-Mobile IP related
issues,
such as CIP, Hawaii, etc. (this is in addition to paging and context
transfer,
of course).

MN>>agree, sorry. There was too much sarcasm there. But It seems that the
same issues are drifting this way.
See your own comment below.

hmmmm.....

As many of us have stated in the past (including the ADs), simply define the
problem space. Forget about the few that will constantly state that this is
possible within the MIP framework. Of course! It's software, so you can do
anything with it. The better question is whether it makes sense to change
MIP
to do what we need.

MN>> agreed again.

Anyways, the MM team put together -01, and it is looking quite good, but
does
require some additional work, and -02 will be forthcoming, I'm sure. I will
be
sitting down with the ADs in Minn. to work out a plan.

MN>> No offense to the authors of the drafts, I did read the draft and I
think I can empathize to a certain degree with the authors about the way
they had to write it, but it seems like it has brought some of the old
flames back to this list. I for one, although liked the scenario
description, think there was too much weight on MIP, with a lot of
comparisons that could be perceived as subjective by some MIP proponents.
Relying on or interoperability with MIP, could be reduced just one issue
among all the issues in a micromobility problem statement draft. 
Don't get me wrong, I want to speak neither for nor against MIP. Judging
from the draft, I just think seamoby MM covers a larger problem area for
mobility, and that is good IMHO.

<snip>

> In respond to Pat C., I'd say I am all for the design teams, let's
continue
> the work. The design team were never closed, anybody can join, even
somebody
> as dumb as me, they were just more focused on seamoby issues.

Good, that's the response I seem to get most often.

PatC


MN>> glad to hear that.

Madjid


From owner-seamoby@diameter.org  Thu Mar  1 21:15:41 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA01661
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 21:15:40 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f220k7022586
	for seamoby-list; Thu, 1 Mar 2001 16:46:07 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f220k5o22581
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 16:46:05 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA01806;
	Thu, 1 Mar 2001 15:55:28 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA17621;
	Thu, 1 Mar 2001 15:55:07 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id PAA01039;
	Thu, 1 Mar 2001 15:55:05 -0800 (PST)
Date: Thu, 1 Mar 2001 15:50:42 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: RE: [seamoby] Yet Another BOF?
To: Phil_Neumiller@3Com.com
Cc: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>,
        Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        seamoby@diameter.org
In-Reply-To: "Your message with ID" <88256A02.0080EC8F.00@hqoutbound.ops.3com.com>
Message-ID: <Roam.SIMC.2.0.6.983490642.4391.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> pdn>That email was very MUCH intended for both groups.  Bad idea?  Maybe.
> pdn>I thought it stimulated a fairly useful thread with a short life.
> pdn>The answer I got from Raj may be of interest to the micmob des team.
> pdn>If the COA changes (and there is no MIP) infrastructure, it is
> pdn>considered micromobility!  I can site some examples to explain this.

ok, then you don't mind me responding when someone wonders why all the MIP
folks are all of a sudden on our list.

> pdn>Yes, indeed SeaMoby currently has a completely mobile IP inspired
> charter. pdn>You would think that the OBAST BOF never happened the CRAPS BOF
> never pdn>happened since absolutely nothing from those BOFs made it to
> charter. pdn>Those drafts, that work, is pretty much in limbo.  The only
> perceived pdn>important thing for SeaMoby is to work on the stuff that
> Mobile IP wishes pdn>to expel (at least this the way the IESG constructed
> the WG).

There is *nothing* stopping this WG from working on the MM portion of OBAST.
However, work in the IETF does need to be justified. Simply stating that it
cannot be MIP doesn't but it with management. We need to provide justification.
 I am really not sure why we are expending all of these resources arguing this
very point over and over instead of simply doing the work...

> pdn>Phil N. might have been happier with a different charter!  Phil N.  may
> pdn>never be happy!  Phil N. might be happier with a different chair!  JK Pat

You were at the meetings, you knew what was going on. Nothing has changed.
Justification is still required.

You are free to discuss any chair issues you may have with Allison. She is the
AD overseeing this WG.

Now if you don't mind. I'd really like to kill this thread, and let real work
continue.

PatC



From owner-seamoby@diameter.org  Thu Mar  1 23:39:04 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA06048
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 23:39:03 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222Uam23196
	for seamoby-list; Thu, 1 Mar 2001 18:30:36 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222UXo23191
	for <seamoby@cdma-2000.org>; Thu, 1 Mar 2001 18:30:33 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:26:12 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 01:25:48 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SGWSJ16003
	for seamoby-list; Wed, 28 Feb 2001 08:32:28 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from idcpa4.pa.interdigital.com (idcmail.interdigital.com [12.32.197.142])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SGVoo15998
	for <seamoby@cdma-2000.org>; Wed, 28 Feb 2001 08:31:51 -0800
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <DLAL414W>; Wed, 28 Feb 2001 10:39:42 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D01F1F741@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>
To: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: [seamoby] test
Date: Wed, 28 Feb 2001 10:39:41 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This is a test.


From owner-seamoby@diameter.org  Thu Mar  1 23:54:33 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA06351
	for <seamoby-archive@odin.ietf.org>; Thu, 1 Mar 2001 23:54:32 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f221XXM22741
	for seamoby-list; Thu, 1 Mar 2001 17:33:33 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f221XVo22736
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 17:33:31 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f220fgo03133;
	Thu, 1 Mar 2001 16:41:42 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f220h3X01328;
	Thu, 1 Mar 2001 16:43:03 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A03.0004133B ; Thu, 1 Mar 2001 16:44:30 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3com.com
To: Pat Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
cc: seamoby@diameter.org
Message-ID: <88256A03.00041298.00@hqoutbound.ops.3com.com>
Date: Thu, 1 Mar 2001 18:41:56 -0600
Subject: [seamoby] Killing the thread (I'm trying)
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk



If these issues were not of systemic importance to the future of SeaMoby the
thread would
have died long ago.  Some people try to ride dead horses, some people dig up
bones,
some people bury the hatchet.  This letter will do a bit of each.

1).  I no longer can nor do I advocate OBAST!  I agree with some of its high
level
      priciples. That technology is owned by Motorola, Inc. .  There are some
parts in
      the public domain of limited use.

2).  Micro-mobility was a tiny portion of OBAST, like an elephant's trunk.

3).  The SeaMoby charter is an IESG creation and has nothing
       to do with either OBAST or the CRAPS BOF.

4).  You will agree with me that the SeaMoby charter is composed of the work MIP
       no longer wanted or did not want to work on.

If we can agree to the above, I will be content that the truth is out about what
SeaMoby is "currently" woking on and what its IETF prospects are.   I will then
shut up (clap clap clap) bury all  hatchets and get to work.  BTW,  I find it
extremely
diffiticult to justify anything without architectural context.

Thanks,

Phil




From owner-seamoby@diameter.org  Fri Mar  2 00:21:34 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA06662
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 00:21:33 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223r9c01122
	for seamoby-list; Thu, 1 Mar 2001 19:53:09 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223r6t01117
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:53:06 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GCB6RHAV>; Thu, 1 Mar 2001 22:01:16 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D29EF@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <KAtwal@zucotto.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Cc: "'seamoby@diameter.org'" <seamoby@diameter.org>
Subject: FW: [seamoby] MANET Critique  ( was  Yet Another BOF?
Date: Thu, 1 Mar 2001 22:01:15 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This is a cross post in response to recent MANET suggestions by members of
the MIP list.

-----Original Message-----
From: Kulwinder Atwal 
Sent: Thursday, March 01, 2001 8:56 PM
To: 'Charles E. Perkins'
Cc: seamoby@diameter.org; Gary Kenward
Subject: RE: [seamoby] MANET Critique ( was Yet Another BOF?



> -----Original Message-----
> From: Charles E. Perkins [mailto:charliep@iprg.nokia.com]
> Sent: Thursday, March 01, 2001 3:10 PM
> To: Gary Kenward
> Cc: seamoby@diameter.org
> Subject: Re: [seamoby] Yet Another BOF?
> 
 
> Thus, it is easy to understand
> "well, we can make Mobile IP do that"...
> And I don't think it's necessarily an
> unfortunate thing that people are thinking
> about such things.


>  But, on the other hand,
> it's important to avoid protocol bloat and
> unnecessary requirements.  To me that just
> means that good engineering is required.

Using this thought let us take a closer look at your MANET ADOV draft
Introduction.

    AODV allows mobile nodes to respond
    quickly to link breakages and changes in network topology.  The
    operation of AODV is loop-free, and by avoiding the Bellman-Ford
    ``counting to infinity'' problem offers quick convergence when the
    ad hoc network topology changes (typically, when a node moves in the
    network).  When links break, AODV causes the affected set of nodes to
    be notified so that they are able to invalidate the routes using the
    broken link.


    One distinguishing feature of AODV is its use of a destination
    sequence number for each route entry.  The destination sequence
    number is created by the destination for any route information it
    sends to requesting nodes.  Using destination sequence numbers
    ensures loop freedom and is simple to program.  Given the choice
    between two routes to a destination, a requesting node always selects
    the one with the greatest sequence number.

From this I see that you are trying to solve two problems:

Loop-free:
Multiple-Paths:

Unfortunately, I cannot think of an AD HOC network where this is a problem.
Maybe, your intent is to suggest it as a solution for Bluetooth?

There are serveral problems with this:

1. You did not read the Spec before writing the draft.  I recall sending you
a private email in December providing you with a link and requesting that
you read the Spec before commenting further on MANET.  Obviously, you have
not bothered to read it.

2. Bluetooth is a Master-Slave Network.  Master-Slave Networks have been
around for at least twenty years and are well understood.  Take a look at
MODBUS (A General Motors Initiative).

In brief, a Master-Slave Network,

2.1.  All communication is between the Master and a Slave.  Either from the
Master to the Slave, or from the Slave to the Master.
2.2.  The Master MUST transmit first by addressing a particular Slave.
Followed immediately by the particular Slave, and only the particular Slave
responding.
2.3.  The Master may broadcast to the network.  In this special case the
Slaves MUST NOT respond to the broadcast.
2.2.  A Slave MUST NOT communicate directly to another Slave. 

Appling this to Bluetooth:

A.  If a single physical device is logical Slave1 on Piconet1 and logical
Slave2 on Piconet2, applying rule 2.2, it MUST NOT route between logical
Slave1 and logical Slave2. No more loops, or multiple paths.

B.  If a single physical device wishes route between two Piconets it MUST be
a Master in one AND a Slave in the other. 

Therefore, there will be no Loops, and no multiple-Paths.  And no need for
MANET.  MANET is solution is search of a problem.  It hasn't found one in
Bluetooth.

>  But, on the other hand,
> it's important to avoid protocol bloat and
> unnecessary requirements.  To me that just
> means that good engineering is required.

Well put, Charlie.  Lets dump MANET, and all references to it, once and for
all.

- Kulwinder.

> 
> Regards,
> Charlie P.
> 


From owner-seamoby@diameter.org  Fri Mar  2 00:24:06 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA06745
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 00:24:05 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f224BmU01209
	for seamoby-list; Thu, 1 Mar 2001 20:11:48 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f224Bkt01204
	for <seamoby@cdma-2000.org>; Thu, 1 Mar 2001 20:11:46 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA19063
	for <seamoby@cdma-2000.org>; Thu, 1 Mar 2001 18:39:37 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA16400
	for <seamoby@cdma-2000.org>; Thu, 1 Mar 2001 18:39:37 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id SAA23714
	for <seamoby@cdma-2000.org>; Thu, 1 Mar 2001 18:39:35 -0800 (PST)
Date: Thu, 1 Mar 2001 18:35:14 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] The list...
To: seamoby@cdma-2000.org
Message-ID: <Roam.SIMC.2.0.6.983500514.12512.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

Something seems to have happend somewhere and old messages, that are not even
queued on my box, are being re-sent.

I am trying to trace it down, and will take down service for an hour or so.

patC



From owner-seamoby@diameter.org  Fri Mar  2 00:34:09 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA07027
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 00:34:08 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f2246ND01186
	for seamoby-list; Thu, 1 Mar 2001 20:06:23 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f2246Kt01181
	for <seamoby@cdma-2000.org>; Thu, 1 Mar 2001 20:06:20 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id TAA08285
	for <seamoby@cdma-2000.org>; Thu, 1 Mar 2001 19:14:30 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id TAA25370;
	Thu, 1 Mar 2001 19:14:28 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id TAA29312;
	Thu, 1 Mar 2001 19:14:27 -0800 (PST)
Date: Thu, 1 Mar 2001 19:10:05 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] The list ... (it's not me!!!)
To: seamoby@cdma-2000.org
Cc: steven.glass@east.sun.com
Message-ID: <Roam.SIMC.2.0.6.983502605.32690.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

All,

From what I can tell, the problems are caused by the new MobileIP list. My
list is operating correctly, but the Mobile IP list is constantly re-sending
old e-mails :(

Your mail administrator,

PatC



From owner-seamoby@diameter.org  Fri Mar  2 00:36:41 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA07057
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 00:36:40 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222UQd23187
	for seamoby-list; Thu, 1 Mar 2001 18:30:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222UNo23181
	for <seamoby@cdma-2000.org>; Thu, 1 Mar 2001 18:30:23 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:26:06 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 00:15:24 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SFQWK15871
	for seamoby-list; Wed, 28 Feb 2001 07:26:32 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SFQTo15866
	for <seamoby@cdma-2000.org>; Wed, 28 Feb 2001 07:26:29 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA20645;
	Wed, 28 Feb 2001 06:35:59 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA03323;
	Wed, 28 Feb 2001 06:35:43 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id GAA21158;
	Wed, 28 Feb 2001 06:35:27 -0800 (PST)
Date: Wed, 28 Feb 2001 06:31:06 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: Re: MM Draft v1 WAS: [seamoby] Context Transfer and Paging
To: john.loughney@nokia.com
Cc: pcalhoun@nasnfs.eng.sun.com, seamoby@cdma-2000.org
In-Reply-To: "Your message with ID" <01D91AFB08B6D211BFD00008C7EABAE10680AAC3@eseis04nok>
Message-ID: <Roam.SIMC.2.0.6.983370666.4129.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> I did get confirmation that it was recieved.  However, I
> do think that the draft will need additional work.

ok

> As this 
> problem statement may need the most justification, perhaps
> it wouldn't be a bad idea to meet in Minneapolis with
> the relevant folks to discuss the best way to procede.

Great idea. How about Wednesday lunch?

PatC


From owner-seamoby@diameter.org  Fri Mar  2 00:40:34 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA07083
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 00:40:33 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222QGN23071
	for seamoby-list; Thu, 1 Mar 2001 18:26:16 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222Pro23046
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:25:55 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:21:37 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 03:18:01 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21IQuG21190
	for seamoby-list; Thu, 1 Mar 2001 10:26:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from eagle.aud.alcatel.com (host60d9.alcatel.com [128.251.96.217])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21IQro21185
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 10:26:53 -0800
Received: from mswitch.aud.alcatel.com by eagle.aud.alcatel.com (8.8.8+Sun/SMI-SVR4)
	id LAA18139; Thu, 1 Mar 2001 11:36:24 -0600 (CST)
Received: from usa.alcatel.com by mswitch.aud.alcatel.com (8.8.8+Sun/SMI-SVR4)
	id LAA14127; Thu, 1 Mar 2001 11:36:22 -0600 (CST)
Message-ID: <3A9E8895.DD789091@usa.alcatel.com>
Date: Thu, 01 Mar 2001 11:36:21 -0600
From: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: seamoby@diameter.org
Subject: Re: [seamoby] Arch discussions in IETF
References: <7B5C0390ACE7D211BC9C0008C7EABA2B0321356A@daeis07nok>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Raj and Phil,

  I think the critical question for micromobility (mm) branch of the
Seamoby WG is
to be or not to be, i.e.
whether another routing protocol for mobility is required. Presently we
have the MIP and
the Manet routing approaches.
  The alternative seems to be per-host routes or host-based routing. I do
not think there
has been another breakthrough proposal significantly different. We all know
Cellular IP and
Hawaii proposals. Recently there is probably another one based on extending
OSPF with
host-based routes.
  Of course there are a lot of details but I think this is the crux of
Seamoby mm problem.

--
Behcet


From owner-seamoby@diameter.org  Fri Mar  2 00:49:09 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA07150
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 00:49:08 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222IfQ22983
	for seamoby-list; Thu, 1 Mar 2001 18:18:41 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222HMo22978
	for <seamoby@cdma-2000.org>; Thu, 1 Mar 2001 18:17:22 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:18:09 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Wed, 28 Feb 2001 17:24:18 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1S8HBm14610
	for seamoby-list; Wed, 28 Feb 2001 00:17:11 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1S8H8o14605
	for <seamoby@cdma-2000.org>; Wed, 28 Feb 2001 00:17:08 -0800
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1S7Qb204099
	for <seamoby@cdma-2000.org>; Wed, 28 Feb 2001 09:26:37 +0200 (EET)
Received: from esebh11nok.ntc.nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5200c7891eac158f25063@esvir05nok.ntc.nokia.com>;
 Wed, 28 Feb 2001 09:26:35 +0200
Received: by esebh11nok with Internet Mail Service (5.5.2652.78)
	id <FPDY2PBB>; Wed, 28 Feb 2001 09:24:26 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680AAC3@eseis04nok>
From: john.loughney@nokia.com
To: pcalhoun@nasnfs.Eng.Sun.COM
Cc: seamoby@cdma-2000.org
Subject: MM Draft v1 WAS: [seamoby] Context Transfer and Paging
Date: Wed, 28 Feb 2001 09:24:23 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Pat,

> I wasn't sure that it actually *did* make the deadline. I 
> know that additional comments were sent since. The ADs and I 
> are sitting down at the IETF with some other folks to discuss this.

I did get confirmation that it was recieved.  However, I
do think that the draft will need additional work.  As this 
problem statement may need the most justification, perhaps
it wouldn't be a bad idea to meet in Minneapolis with
the relevant folks to discuss the best way to procede.

best regards,
John


From owner-seamoby@diameter.org  Fri Mar  2 01:23:09 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA09144
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 01:23:08 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f225Qtk01484
	for seamoby-list; Thu, 1 Mar 2001 21:26:55 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f225Qqt01479
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 21:26:52 -0800
Received: from centralmail1.Central.Sun.COM ([129.147.62.10])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA09089
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 20:35:02 -0800 (PST)
Received: from esun1as-mm. (esun1as-mm.Central.Sun.COM [129.147.34.144])
	by centralmail1.Central.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id VAA07814
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 21:35:02 -0700 (MST)
Received: from sunyata.sun.com by esun1as-mm. (SMI-8.6/SMI-SVR4)
	id VAA28326; Thu, 1 Mar 2001 21:35:48 -0700
Message-Id: <5.0.0.25.1.20010301202954.009fa390@localhost>
X-Sender: kempf@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Thu, 01 Mar 2001 20:31:28 -0800
To: seamoby@diameter.org
From: James Kempf <james.kempf@sun.com>
Subject: [seamoby] Paging Requirements Discussion
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-seamoby@diameter.org
Precedence: bulk

We have a couple of weeks until IETF, and Pat has included an agenda item to
discuss ongoing work. Could we get started discussing paging requirements
on seamoby-paging@diameter.org? Anybody who is not currently subscribed
and would like to join, please join.

		jak



From owner-seamoby@diameter.org  Fri Mar  2 01:32:34 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA10228
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 01:32:33 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222VKm23211
	for seamoby-list; Thu, 1 Mar 2001 18:31:20 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222VEo23202
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:31:15 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:26:30 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:11:33 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SMBfK17077
	for seamoby-list; Wed, 28 Feb 2001 14:11:41 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SMBbo17071
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 14:11:38 -0800
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f1SLLAC13929
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 22:21:10 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Wed Feb 28 22:21:10 2001 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2651.58)
	id <FV8XLSG9>; Wed, 28 Feb 2001 22:17:24 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBAD@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'Michael Thomas'" <mat@cisco.com>
Cc: James Kempf <james.kempf@sun.com>,
        "'Gopal Dommety'"
	 <gdommety@cisco.com>,
        Claude Castelluccia
	 <claude.castelluccia@inrialpes.fr>,
        seamoby@diameter.org
Subject: RE: [seamoby] Is Mobile IP too slow or is Routing Table UpdateTo 
	 o slow? (was....)
Date: Wed, 28 Feb 2001 22:21:09 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk

>  > Can you elaborate why you believe a design that accommodates multiple levels of
>  > hierarchy is a bad idea? The draft doesn't go into much detail on this point.
> 
>    Also: it doesn't seem to make sense given its claimed
>    ability to support mobile routers: why wouldn't a 
>    mobile router in turn want to hook up to a MAP and
>    so on and so forth.
> 
	=> As I said to James we do see that as the only case 
	where it is needed and I've clarified that in the new
	revision coming out tomorrow or so.
	So you're right, this scenario is recommended
	_only_ for the mobile router case.

	Hesham


From owner-seamoby@diameter.org  Fri Mar  2 01:46:56 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA11906
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 01:46:55 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222QHp23016
	for seamoby-list; Thu, 1 Mar 2001 18:26:17 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222Ovo23010
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:24:57 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:19:17 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Wed, 28 Feb 2001 18:17:12 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1S9O7W14745
	for seamoby-list; Wed, 28 Feb 2001 01:24:07 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1S9O0o14740
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 01:24:00 -0800
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1S8XU202075
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 10:33:30 +0200 (EET)
Received: from esebh01nok.ntc.nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T520104cfabac158f21081@esvir01nok.ntc.nokia.com>;
 Wed, 28 Feb 2001 10:33:30 +0200
Received: by esebh01nok.ntc.nokia.com with Internet Mail Service (5.5.2652.78)
	id <FYNSCL8L>; Wed, 28 Feb 2001 10:33:02 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680AACA@eseis04nok>
From: john.loughney@nokia.com
To: james.kempf@sun.com
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Is Mobile IP too slow or is Routing Table Update To
	 o  slow? (was....)
Date: Wed, 28 Feb 2001 10:33:01 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi James,

> I think 3GPP2 is making a strong effort to make their All-IP 
> network all IP. They even recently started an effort to rearchitect 
> their RAN to be all IP (whether it goes so far as to be connectable 
> to the Internet, we shall see, but they are trying).
> 
> 3GPP is another story. They have lots of lingering telephony 
> stuff around for various reasons.

As I'm somewhat involved with 3GPP & PP2, my feeling is that both 
networks will not be part of the Internet.  Vendors & operators
in both groups (hey, there is a heck of a lot of overlap in terms
of participants of these groups) are still trying for a walled-garden
business model. In the face of licensing fees, network costs & an 
possible economic downturn - operators & vendors both will be trying
to sell existing solutions.  

Helping to get correct IP networking solutions into these architectures
is not a bad idea, but is it the IETF's job?  I'd rather suggest that
any solution we find here in SeaMoby should scale, should be effective
and be a good 'citizen' of the Internet ...

my 2 cents ...
John


From owner-seamoby@diameter.org  Fri Mar  2 02:11:47 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA22173
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 02:11:47 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223FkW23587
	for seamoby-list; Thu, 1 Mar 2001 19:15:46 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223Feo23578
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:15:41 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:48 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:18 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 05:28:06 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SKZtu16745
	for seamoby-list; Wed, 28 Feb 2001 12:35:55 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from motgate4.mot.com (motgate4.mot.com [144.189.100.102])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SKZro16740
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 12:35:53 -0800
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate4.mot.com (motgate4 2.1) with ESMTP id MAA14917 for <seamoby@diameter.org>; Wed, 28 Feb 2001 12:45:26 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id MAA23642 for <seamoby@diameter.org>; Wed, 28 Feb 2001 12:45:19 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2651.58)
	id <FWT7AWSZ>; Wed, 28 Feb 2001 13:45:17 -0600
Message-ID: <DFF2EFB82ADBD311B4BB00508B6F0C5C02B1F43B@il27exm03.cig.mot.com>
From: Roberts Philip-qa3445 <phil.roberts@motorola.com>
To: "'Hesham Soliman  (ERA)'" <Hesham.Soliman@era.ericsson.se>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
Date: Wed, 28 Feb 2001 13:45:17 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk



> ----------
> From: 	Hesham Soliman  (ERA)
> Sent: 	Wednesday, February 28, 2001 1:42 PM
> To: 	'James Kempf'; 'mobile-ip@standards.nortelnetworks.com'
> Cc: 	seamoby@diameter.org
> Subject: 	RE: [seamoby] Hierarchical MIP, QoS, and Handoff
> 
> 
> > (Hoping this gets through the MIP mailing list problems...)
> > 
> 	=> It didn't. I think this is definitely a MIP issue so we should 
> 	discuss it on the MIP list. You need to send your mail to
> 	mobile-ip@standards.nortelnetworks.com
> 
> 
Actually, we're currently in the process of moving the MIP mailing list.  You should receive an email on it when it's up later today (hopefully).  Many thanks to Sun for hosting and administering the list going forwards.


From owner-seamoby@diameter.org  Fri Mar  2 02:15:53 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA22501
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 02:15:53 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222VNG23214
	for seamoby-list; Thu, 1 Mar 2001 18:31:23 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222VIo23208
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:31:18 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:26:41 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 08:29:48 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SNTv017427
	for seamoby-list; Wed, 28 Feb 2001 15:29:57 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SNToo17422
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 15:29:50 -0800
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f1SMdNC29486
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 23:39:23 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Wed Feb 28 23:39:06 2001 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2651.58)
	id <FV8XLT2A>; Wed, 28 Feb 2001 23:35:20 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBB0@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Arch discussions in IETF
Date: Wed, 28 Feb 2001 23:39:05 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk

> >Phil,
> >
> >I do not see anyone saying that Mobile IP is the only solution for all
> >scenarios that require mobility. I am sure there are many scenarios
> >that Mobile IP may or may not be the most optimal solution. If Mobile
> >IP is unable to work as well as anything else you may have in mind
> >for specific scenarios, then why deploy Mobile IP in such scenarios?
> 
> Then where might these other solutions be standardized in the IETF?
> Would this fall under the classification of micro-mobility even though
> the "so-called" COA or routing prefix does indeed change?  I guess what
> I am getting at is there may be cases of infra-structure-less mobility
> where the COA changes but there is no HA.  
> 
	=> There was a draft presented in San Diego about Homeless 
	MIPv6. Just an example and I'm not trying to force MIP.

	Regards,

	Hesham


From owner-seamoby@diameter.org  Fri Mar  2 02:16:31 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA22593
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 02:16:31 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f225x7701646
	for seamoby-list; Thu, 1 Mar 2001 21:59:07 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f225x4t01641
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 21:59:04 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id VAA14115
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 21:07:15 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA23982;
	Thu, 1 Mar 2001 21:07:14 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id VAA29960;
	Thu, 1 Mar 2001 21:07:11 -0800 (PST)
Date: Thu, 1 Mar 2001 21:02:48 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] Paging (and CT) Requirements Discussion
To: James Kempf <james.kempf@sun.com>
Cc: seamoby@diameter.org
In-Reply-To: "Your message with ID" <5.0.0.25.1.20010301202954.009fa390@localhost>
Message-ID: <Roam.SIMC.2.0.6.983509368.14265.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> We have a couple of weeks until IETF, and Pat has included an agenda item to
> discuss ongoing work. Could we get started discussing paging requirements
> on seamoby-paging@diameter.org? Anybody who is not currently subscribed
> and would like to join, please join.

If anyone needs information on subscribing, see www.diameter.org/seamoby.html.

Thanks for getting the activities kick-started. We need to get something
similar going for context transfer. The mailing list info for the CT design
team is on the same web page, and I recommend re-using that as well.

PatC



From owner-seamoby@diameter.org  Fri Mar  2 02:20:48 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA22661
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 02:20:48 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222Pmf23024
	for seamoby-list; Thu, 1 Mar 2001 18:25:48 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222PTo23019
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:25:29 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:19:34 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Wed, 28 Feb 2001 19:04:05 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1S9lnX14795
	for seamoby-list; Wed, 28 Feb 2001 01:47:49 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from ebene.inrialpes.fr (ebene.inrialpes.fr [194.199.18.70])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1S9lko14790
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 01:47:46 -0800
Received: from glandon.inrialpes.fr (glandon.inrialpes.fr [194.199.24.105])
	by ebene.inrialpes.fr (8.9.3/8.8.6) with ESMTP id JAA11820;
	Wed, 28 Feb 2001 09:57:17 +0100 (MET)
Received: from inrialpes.fr (localhost [127.0.0.1])
	by glandon.inrialpes.fr (8.8.7/8.8.5) with ESMTP id JAA12184;
	Wed, 28 Feb 2001 09:57:17 +0100 (MET)
Message-ID: <3A9CBD6B.219885EE@inrialpes.fr>
Date: Wed, 28 Feb 2001 09:57:17 +0100
From: Claude Castelluccia <claude.castelluccia@inrialpes.fr>
X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: "Dana L. Blair" <dblair@cisco.com>
CC: "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>,
        seamoby@diameter.org
Subject: Re: [seamoby] Is Mobile IP too slow or is Routing Table UpdateToo slow? 
 (was....)
References: <4.1.20010227104059.040eea10@mira-sjcm-2.cisco.com>
Content-Type: multipart/alternative;
 boundary="------------6BB3D6273384751250CF82EE"
Sender: owner-seamoby@diameter.org
Precedence: bulk


--------------6BB3D6273384751250CF82EE
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Dana L. Blair" wrote:

>
> Not really.  I see the HMIP solution as equivalent to introducing NAT's into
> the network.  It breaks end to end addressability.
>

Well what can I tell you: you probably did not read the right HMIP draft (or did you read it at
all?) ...


Claude.

--

----------------------------------------
Claude CASTELLUCCIA, INRIA Rhone-Alpes
ph:  +33 4.76.61.52.15 (fax: 52.52)
http://www.inrialpes.fr/planete/



--------------6BB3D6273384751250CF82EE
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
"Dana L. Blair" wrote:
<blockquote TYPE=CITE>&nbsp;
<br>Not really.&nbsp; I see the HMIP solution as equivalent to introducing
NAT's into
<br>the network.&nbsp; It breaks end to end addressability.
<br>&nbsp;</blockquote>

<p><br>Well what can I tell you: you probably did not read the right HMIP
draft (or did you read it at all?) ...
<br>&nbsp;
<p>Claude.
<pre>--&nbsp;

----------------------------------------
Claude CASTELLUCCIA, INRIA Rhone-Alpes&nbsp;&nbsp;
ph:&nbsp; +33 4.76.61.52.15 (fax: 52.52)
<A HREF="http://www.inrialpes.fr/planete/">http://www.inrialpes.fr/planete/</A></pre>
&nbsp;</html>

--------------6BB3D6273384751250CF82EE--


From owner-seamoby@diameter.org  Fri Mar  2 02:35:21 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA22811
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 02:35:20 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223FUP23570
	for seamoby-list; Thu, 1 Mar 2001 19:15:30 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223FIo23552
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:15:18 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:38 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:29 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 03:43:21 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SIpQQ16460
	for seamoby-list; Wed, 28 Feb 2001 10:51:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SIpOo16455
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 10:51:24 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA06246;
	Wed, 28 Feb 2001 10:00:46 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA22460;
	Wed, 28 Feb 2001 10:00:45 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id KAA29087;
	Wed, 28 Feb 2001 10:00:44 -0800 (PST)
Date: Wed, 28 Feb 2001 09:56:22 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
Subject: [seamoby] The death of a thread....
To: Gary Kenward <gkenward@nortelnetworks.com>
Cc: seamoby@diameter.org
In-Reply-To: "Your message with ID" <13E2EF604DE5D111B2E50000F80824E8057A8D0B@zwdld001.ca.nortel.com>
Message-ID: <Roam.SIMC.2.0.6.983382982.27896.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> But honestly, CDMA2000 and UMTS R3 are both a far cry 
> from being "all IP" networks. Calling either one "all IP" is
> as superficial as stating that they are "link layer" solutions.

This is pointless. I attend the meetings, and I have yet to see you there, so
I don't know where you get your information from. I do all I can to make sure
that the core network contains nothing but IP, and even more imporantly IETF
protocols. If this isn't all-ip, then we would need to debate the meaning on
All-IP (and I don't have time, nor the energy to do so). I know that the RAN
is a little behind, and work is starting there (and perhaps this was what you
meant).

Can we agree to kill this thread? (if you agree, don't bother replying and
kill it now)

PatC


From owner-seamoby@diameter.org  Fri Mar  2 02:48:21 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA22928
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 02:48:20 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222QlH23095
	for seamoby-list; Thu, 1 Mar 2001 18:26:47 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222Qgo23089
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:26:43 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:21:03 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 00:01:26 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SExBN15804
	for seamoby-list; Wed, 28 Feb 2001 06:59:11 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from cisco.com (omega.cisco.com [171.69.26.42])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SEx9o15799
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 06:59:09 -0800
Received: from gopal.cisco.com ([64.104.42.55])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id GAA17253;
	Wed, 28 Feb 2001 06:07:50 -0800 (PST)
Message-Id: <4.3.2.7.2.20010227000549.01db3ba0@omega.cisco.com>
X-Sender: gdommety@omega.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 27 Feb 2001 00:10:39 -0800
To: Claude Castelluccia <claude.castelluccia@inrialpes.fr>
From: Gopal Dommety <gdommety@cisco.com>
Subject: Re: [seamoby] Is Mobile IP too slow or is Routing Table
  UpdateTo o   slow? (was....)
Cc: "Andrew T. Campbell" <campbell@comet.columbia.edu>,
        "'Charlie Perkins'" <charliep@iprg.nokia.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>, seamoby@diameter.org
In-Reply-To: <3A9B95F0.9A36F7EA@inrialpes.fr>
References: <001a01c0a09b$00dd44d0$3d443b80@SWEETPEA>
 <4.3.2.7.2.20010226022757.00b8acb0@omega.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-seamoby@diameter.org
Precedence: bulk



At 12:56 PM 27/02/01 +0100, Claude Castelluccia wrote:
>Gopal Dommety wrote: 
>>  
>>There are several components to handoff delay (see an  old anchor handoff draft). One of the delays is the backhaul delay 
>>(most of the time this is not the problem unless you are doing VPN etc). If this is a problem it is better to perform anchor kind of a handoff.
>I don't understand your point...HMIP provides "anchor-based" handoffs... 
> It is based on MAP (Mobile ANCHOR Points) but these MAPs do not have to be deployed (although they 
>can) on every links (as most of others fast handoff solutions require) .... 
>>  
>>Hierarchical instantiations do help but mainly to reduce the signaling (or limit the signaling to the local domain). 
>> 
>not only ....it reduces handoff delay, provides location privacy and a lot more ;-)  

Depending on the hierarchys and the movement it could increase the latency (the packet processing time is typicall order of magnitude than the
packet forwarding time). Long time  ago I happen to have done some research on the
number of hierarchies on the impact of handoff latencies and signalling. For internet kind of traffic (the actual paraments are the packet
processing  times and the forwarding delays of routers) the number of hierarchies tended to be 2 (HA and FA) for handoff latencies.

-Gopal



>Claude. 
>-- 
>
>----------------------------------------
>Claude CASTELLUCCIA, INRIA Rhone-Alpes  
>ph:  +33 4.76.61.52.15 (fax: 52.52)
><http://www.inrialpes.fr/planete/>http://www.inrialpes.fr/planete/  


From owner-seamoby@diameter.org  Fri Mar  2 03:04:59 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA23160
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 03:04:58 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222VVr23231
	for seamoby-list; Thu, 1 Mar 2001 18:31:31 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222VPo23216
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:31:25 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:26:39 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 06:55:06 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SM8tC17041
	for seamoby-list; Wed, 28 Feb 2001 14:08:55 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SM8po17036
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 14:08:51 -0800
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f1SLIOd06280
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 22:18:24 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Wed Feb 28 22:18:23 2001 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2651.58)
	id <F1J9BXG0>; Wed, 28 Feb 2001 22:19:52 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBAC@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'James Kempf'" <james.kempf@sun.com>
Cc: Claude Castelluccia <claude.castelluccia@inrialpes.fr>,
        seamoby@diameter.org, "'Gopal Dommety'" <gdommety@cisco.com>
Subject: RE: [seamoby] Is Mobile IP too slow or is Routing Table UpdateTo 
	 o slow? (was....)
Date: Wed, 28 Feb 2001 22:18:21 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk

	Hi James

> Can you elaborate why you believe a design that accommodates multiple levels of
> hierarchy is a bad idea? The draft doesn't go into much detail on this point.
> 
	=> Well since the MIP list is broken we can take the discusion
	on the sister list :)
	First of all we do support the multi-level case in the draft, however 
	we only recommend it for the mobile router case, where the MR
	is a MAP and it connects to another MAP in the network. 
	This is clearly mentioned in the draft I'm submitting 
	tomorrow. So apologies if it's not obvious in the current draft. 

	As for the normal case (mobile nodes and not networks) we 
	can't see the benefit of having a mult-level hierarchy where 
	packets are routed from one level to another down the 
	hierarchy till they reach the MN. We see that as an 
	equivalent to a "circuit" in the IP network and I don't 
	think that's a benefit. Definitely less robust. 
	Obviously all these routers in the hierarchy are single
	points of failure. If one crashes not only the services 
	will be distrupted, but the MN will not know about it 
	(if the hierarchy is hidden). 

	We do see great benefits in having multiple MAPs
	for redundany and  load sharing, but not for a tree 
	of hierarchies.

	So let me turn the question around and as you if 
	you think there is any benefit in having a multi-level
	hierarchy ?



From owner-seamoby@diameter.org  Fri Mar  2 03:13:28 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA23237
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 03:13:28 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223G4k23614
	for seamoby-list; Thu, 1 Mar 2001 19:16:04 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223Fqo23595
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:15:53 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:51 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:06 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:59:23 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SN3Nl17279
	for seamoby-list; Wed, 28 Feb 2001 15:03:23 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SN3Lo17274
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 15:03:21 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SMBSo14321;
	Wed, 28 Feb 2001 14:11:28 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f1SMCnX06019;
	Wed, 28 Feb 2001 14:12:49 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A01.007A28B7 ; Wed, 28 Feb 2001 14:14:18 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: mobile-ip@sunroof.eng.sun.com
cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Message-ID: <88256A01.007A25AA.00@hqoutbound.ops.3com.com>
Date: Wed, 28 Feb 2001 16:11:37 -0600
Subject: RE: [seamoby] Arch discussions in IETF
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk






Hi Raj,

>Phil,
>
>I do not see anyone saying that Mobile IP is the only solution for all
>scenarios that require mobility. I am sure there are many scenarios
>that Mobile IP may or may not be the most optimal solution. If Mobile
>IP is unable to work as well as anything else you may have in mind
>for specific scenarios, then why deploy Mobile IP in such scenarios?

Then where might these other solutions be standardized in the IETF?
Would this fall under the classification of micro-mobility even though
the "so-called" COA or routing prefix does indeed change?  I guess what
I am getting at is there may be cases of infra-structure-less mobility
where the COA changes but there is no HA.  Would this be micro or
macro mobility?

>Can you be more specific on the kind of environments and requirements
>that these environments have that would make it impossible for Mobile
>IP to work in.

Sure.  Specifically, I am very interested in portable devices that will
find there way into homes.  Wireless appliances, MP3 players, digital
radios, digital security devices, gaming units, VoIP devices, etc.  I
am also interested in these types of devices that may be used in small
to medium business that may not have large infrastructures in place.

Thank you,

Phil Neumiller


From owner-seamoby@diameter.org  Fri Mar  2 03:16:22 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA23266
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 03:16:22 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223FNs23561
	for seamoby-list; Thu, 1 Mar 2001 19:15:23 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223F4o23530
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:15:04 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:19 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:14 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 04:48:00 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SJJmV16521
	for seamoby-list; Wed, 28 Feb 2001 11:19:48 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SJJjo16516
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 11:19:45 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA20764;
	Wed, 28 Feb 2001 10:29:02 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA29990;
	Wed, 28 Feb 2001 10:29:01 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id KAA29593;
	Wed, 28 Feb 2001 10:28:58 -0800 (PST)
Date: Wed, 28 Feb 2001 10:24:36 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
Subject: RE: [seamoby] Yet Another BOF?
To: Gary Kenward <gkenward@nortelnetworks.com>
Cc: "'James Kempf'" <james.kempf@sun.com>, Phil_Neumiller@3com.com,
        seamoby@diameter.org
In-Reply-To: "Your message with ID" <13E2EF604DE5D111B2E50000F80824E8057A8D0D@zwdld001.ca.nortel.com>
Message-ID: <Roam.SIMC.2.0.6.983384676.23816.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

>   I think you miss Phil's point. It's all simply a matter of
> software, and no doubt, with enough extensions, modifications, 
> and bit twiddling, we could turn ARP into some version of a 
> mobility protocol (or any other protocol, heck, there are still
> people working on mobile wireless ATM).
> 
>    The frustration comes because with each attempt at a
> problem statement, MIP proponents come forth and state:
> "oh, well sure, we can make MIP do that". No problem statement
> for MM will ever be sufficient if this is the nature of the game.

Those people are as entitled to their opinions as you and Phil are. The point
is that their opinion may not reflect rough concensus or the WG.

I believe that the problem statement does have some things that Mobile IP will
have a REALLY hard time handling. However, as I have stated numerous times,
statements like "MIP is too slow" just doesn't cut it. Let's get to the meat
of the requirements, and then we can identify whether MIP can do the job.

PatC


From owner-seamoby@diameter.org  Fri Mar  2 03:26:53 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA23341
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 03:26:52 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223GYq23663
	for seamoby-list; Thu, 1 Mar 2001 19:16:34 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223GTo23656
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:16:29 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:59 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:50 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 05:26:44 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SKKI816653
	for seamoby-list; Wed, 28 Feb 2001 12:20:18 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SKJ0o16648
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 12:19:01 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Wed, 28 Feb 2001 14:24:32 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZV97NA8>; Wed, 28 Feb 2001 14:24:33 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D12@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Pat Calhoun'" <pcalhoun@nasnfs.eng.sun.com>
Cc: "'seamoby'" <seamoby@diameter.org>
Subject: [seamoby] RE: The death of a thread....
Date: Wed, 28 Feb 2001 14:24:26 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

> -----Original Message-----
> From: Pat Calhoun [mailto:pcalhoun@nasnfs.Eng.Sun.COM]
> Sent: Wednesday, February 28, 2001 12:56 PM
> To: Kenward, Gary [WDLN2:AN10:EXCH]
> Cc: seamoby@diameter.org
> Subject: The death of a thread....
> 
> 
> > But honestly, CDMA2000 and UMTS R3 are both a far cry 
> > from being "all IP" networks. Calling either one "all IP" is
> > as superficial as stating that they are "link layer" solutions.
> 
> This is pointless. I attend the meetings, and I have yet to 
> see you there, so
It's only pointless if you discount the views of a number of people
who have a different vision of what all-IP means. 

One does not need to be in the middle of situation to understand
the results. 

> I don't know where you get your information from. I do all I 
> can to make sure
> that the core network contains nothing but IP, and even more 
> imporantly IETF
> protocols. If this isn't all-ip, then we would need to debate 
> the meaning on
> All-IP (and I don't have time, nor the energy to do so). I 
> know that the RAN
> is a little behind, and work is starting there (and perhaps 
> this was what you
> meant).

I will concede that the 3G standards have made progress.
However, you've made my point for me, I work on wireless
access networks. 

Wireless is an access technology. If it's not "all-ip" access,
then it's not "all-ip".

> 
> Can we agree to kill this thread? (if you agree, don't bother 
> replying and
> kill it now)

I agree to kill the thread, but I replied because of some of the
logical fallacies in your arguments. 

It's dead.

Gary

> 
> PatC
> 
> 


From owner-seamoby@diameter.org  Fri Mar  2 03:27:02 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA23360
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 03:27:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222lUc23342
	for seamoby-list; Thu, 1 Mar 2001 18:47:30 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222lPo23337
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:47:26 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:34:29 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Wed, 28 Feb 2001 22:02:49 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SD2fk15540
	for seamoby-list; Wed, 28 Feb 2001 05:02:41 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SD2co15535
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 05:02:38 -0800
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f1SCC9C14399
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 13:12:10 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Wed Feb 28 13:12:08 2001 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2651.58)
	id <FV8XKZFK>; Wed, 28 Feb 2001 13:08:24 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBA5@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'James Kempf'" <james.kempf@sun.com>,
        "Andrew T. Campbell"
	 <campbell@comet.columbia.edu>,
        "'Pat Calhoun'"
	 <pcalhoun@nasnfs.eng.sun.com>
Cc: "'Dana L. Blair'" <dblair@cisco.com>,
        "'Claude Castelluccia'"
	 <claude.castelluccia@inrialpes.fr>,
        "'Charlie Perkins'"
	 <charliep@iprg.nokia.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>, seamoby@diameter.org
Subject: RE: [seamoby] Is Mobile IP too slow or is Routing Table Update To
	 o slow? (was....)
Date: Wed, 28 Feb 2001 13:12:03 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk

James, 


> >Pat:
> >
> >You are misinterpreting what I wrote.
> >
> >I never said 3G. I said that the last thing "All-IP" 3G
> >networks are is "All-IP". You'd agree with that I'm sure?
> 
> 
> I think 3GPP2 is making a strong effort to make their All-IP network all 
> IP. They
> even recently started an effort to rearchitect their RAN to be all IP (whether
> it goes so far as to be connectable to the Internet, we shall see, but they
> are trying).
> 
> 3GPP is another story. They have lots of lingering telephony stuff around
> for various reasons.
> 
	=> 3GPP is also aiming for all-IP, but it seems everyone has his /her
	definition of all-IP. The reliance on the MSC ....etc in the core network
	was removed in the first release of GPRS as a step towards all-IP.
	IP in UTRAN is also being introduced in Release 5 with a strong 
	emphasis on IPv6. The telephony stuff (interfacing to the PSTN!) is 
	handled by Media Gateways on the edge of the PS domain.

	Now we could all argue against one architecture or another but
	as far as running your network on IP goes (which is what both 3GPPs 
	claim to be all-IP !)  3GPP did that a long time ago.

	As far as mobility goes, the major differences between the two 3GPPs 
	IMO is that 3GPP2 still relies on the MSC and that 3GPP uses GTP
	while 3GPP2 uses the RP interface. Both have MIP in their architectures.

	Hesham


From owner-seamoby@diameter.org  Fri Mar  2 03:58:25 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA23842
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 03:58:25 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222QE423070
	for seamoby-list; Thu, 1 Mar 2001 18:26:14 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222Pqo23045
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:25:54 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:21:36 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 03:08:02 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21IVA121233
	for seamoby-list; Thu, 1 Mar 2001 10:31:10 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21IV7o21228
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 10:31:07 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id CAA74944;
	Fri, 2 Mar 2001 02:32:03 +0900
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA18709;
 Thu, 1 Mar 2001 09:38:47 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA00081;
 Thu, 1 Mar 2001 09:38:28 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f21Hag316488
 for mobile-ip-dist; Thu, 1 Mar 2001 09:36:42 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f21HaXV16481
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 09:36:33 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA29691
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 09:36:32 -0800 (PST)
Received: from eagle.aud.alcatel.com (host60d9.alcatel.com [128.251.96.217])
 by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA00342
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 09:36:32 -0800 (PST)
Received: from mswitch.aud.alcatel.com by eagle.aud.alcatel.com (8.8.8+Sun/SMI-SVR4)
 id LAA18139; Thu, 1 Mar 2001 11:36:24 -0600 (CST)
Received: from usa.alcatel.com by mswitch.aud.alcatel.com (8.8.8+Sun/SMI-SVR4)
 id LAA14127; Thu, 1 Mar 2001 11:36:22 -0600 (CST)
Message-ID: <3A9E8895.DD789091@usa.alcatel.com>
Date: Thu, 01 Mar 2001 11:36:21 -0600
From: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: seamoby@diameter.org
Subject: Re: [seamoby] Arch discussions in IETF
References: <7B5C0390ACE7D211BC9C0008C7EABA2B0321356A@daeis07nok>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi Raj and Phil,

  I think the critical question for micromobility (mm) branch of the
Seamoby WG is
to be or not to be, i.e.
whether another routing protocol for mobility is required. Presently we
have the MIP and
the Manet routing approaches.
  The alternative seems to be per-host routes or host-based routing. I do
not think there
has been another breakthrough proposal significantly different. We all know
Cellular IP and
Hawaii proposals. Recently there is probably another one based on extending
OSPF with
host-based routes.
  Of course there are a lot of details but I think this is the crux of
Seamoby mm problem.

--
Behcet



From owner-seamoby@diameter.org  Fri Mar  2 04:04:32 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA23997
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:04:31 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223G9P23622
	for seamoby-list; Thu, 1 Mar 2001 19:16:09 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223Fuo23608
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:15:57 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:30 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:20 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 05:57:42 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SKh5N16794
	for seamoby-list; Wed, 28 Feb 2001 12:43:05 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SKh2o16789
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 12:43:02 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id LAA28812;
	Wed, 28 Feb 2001 11:52:32 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABS22950;
	Wed, 28 Feb 2001 11:52:29 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA19501; Wed, 28 Feb 2001 11:52:29 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15005.22269.496276.223454@thomasm-u1.cisco.com>
Date: Wed, 28 Feb 2001 11:52:29 -0800 (PST)
To: James Kempf <james.kempf@sun.com>
Cc: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>,
        "'Gopal Dommety'" <gdommety@cisco.com>,
        Claude Castelluccia <claude.castelluccia@inrialpes.fr>,
        seamoby@diameter.org
Subject: RE: [seamoby] Is Mobile IP too slow or is Routing Table
  UpdateTo  o slow? (was....)
In-Reply-To: <5.0.0.25.1.20010228114252.00a02dc0@localhost>
References: <034BEFD03799D411A59F00508BDF7546013DBBA7@esealnt448.al.sw.
 ericsson.se>
	<5.0.0.25.1.20010228114252.00a02dc0@localhost>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

James Kempf writes:
 > Hi Hesham,
 > 
 > Can you elaborate why you believe a design that accommodates multiple levels of
 > hierarchy is a bad idea? The draft doesn't go into much detail on this point.

   Also: it doesn't seem to make sense given its claimed
   ability to support mobile routers: why wouldn't a 
   mobile router in turn want to hook up to a MAP and
   so on and so forth. It leaves me with the impression
   that it might be "elephants all the way down."

	   Mike

 > 
 > Thanx.
 > 
 >                  jak
 > 
 > At 05:26 PM 2/28/01 +0100, Hesham Soliman  (ERA) wrote:
 > >Hello Gopal,
 > >
 > >I believe  Claude's statement was in reference to HMIPv6.
 > >we don't want a multi-level hierarchy (like v4), just one level is enough.
 > >That doesn't mean one MAP per domain, you can have several,
 > >but the MN only needs to choose one.
 > >
 > >Regards,
 > >Hesham
 > 


From owner-seamoby@diameter.org  Fri Mar  2 04:07:53 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24041
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:07:53 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223FCp23543
	for seamoby-list; Thu, 1 Mar 2001 19:15:12 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223F4o23531
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:15:04 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:28 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:26 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 06:15:17 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SKo5J16810
	for seamoby-list; Wed, 28 Feb 2001 12:50:05 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SKo2o16805
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 12:50:02 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SJwAo14997;
	Wed, 28 Feb 2001 11:58:10 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f1SJxVX00046;
	Wed, 28 Feb 2001 11:59:31 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A01.006DF5F9 ; Wed, 28 Feb 2001 12:01:03 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: mobile-ip@marvin.corpeast.baynetworks.com
cc: seamoby@diameter.org
Message-ID: <88256A01.006DF159.00@hqoutbound.ops.3com.com>
Date: Wed, 28 Feb 2001 13:46:27 -0600
Subject: [seamoby] Arch discussions in IETF
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk




We have said countless times that IETF does not define architecture.  However
MIP did.
Many of the problems people have with MIP are with its basic architecture, not
the protocol.
Why can't their be an architectural debate on MIP in the IETF (not protocol).
There are
boxes defined.  There is a CN, a MN, an HA, a set of routers.  Lets talk about
how these
need to play in today's modern residential and business deployments.  Why do we
always
have to cater to cellular?  Why do the cellular guys get most the say?   The
Internet has
new stuff like FTC, VoIP, SLP,  RSVP, diffserv, and new radio access
technologies that
can enable different types of mobility architectures.   Is an HA still a good
idea in
every scenario?  Why?  Can we talk about this?  If not why not?  Inquiring minds
want to
know.

Here is an example.  Why do I always need to use MIP?  Let's say I have a
community of
VPN's defined to interlink residences that interoperate with mobility (a bunch
of families
allows their mobiles to operate in each other's premises), i.e. mobile hosts are
allowed
to seamless travel within theses spaces but only in theses spaces (could be set
up
in hotel rooms, conferences, etc).  The COA changes but there is no HA.

I have lots of scenarios like this.

Thanks,

Phil



I believe that the problem statement does have some things that Mobile IP will
have a REALLY hard time handling. However, as I have stated numerous times,
statements like "MIP is too slow" just doesn't cut it. Let's get to the meat
of the requirements, and then we can identify whether MIP can do the job.

PatC


From owner-seamoby@diameter.org  Fri Mar  2 04:10:54 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24095
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:10:53 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222Ttq23163
	for seamoby-list; Thu, 1 Mar 2001 18:29:55 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222Tpo23158
	for <seamoby@cdma-2000.org>; Thu, 1 Mar 2001 18:29:52 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:25:52 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Wed, 28 Feb 2001 21:33:00 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SCkHK15494
	for seamoby-list; Wed, 28 Feb 2001 04:46:17 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SCjoo15489
	for <seamoby@cdma-2000.org>; Wed, 28 Feb 2001 04:45:50 -0800
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02071;
	Wed, 28 Feb 2001 06:55:18 -0500 (EST)
Message-Id: <200102281155.GAA02071@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: seamoby@cdma-2000.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [seamoby] I-D ACTION:draft-ietf-seamoby-mm-problem-01.txt
Date: Wed, 28 Feb 2001 06:55:18 -0500
Sender: owner-seamoby@diameter.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Context and Micro-mobility Routing Working Group of the IETF.

	Title		: SeaMoby Micro Mobility Problem Statement
	Author(s)	: J. Loughney et al.
	Filename	: draft-ietf-seamoby-mm-problem-01.txt
	Pages		: 17
	Date		: 27-Feb-01
	
Seamless mobility requires preserving the capability, security, and
quality of service offered to a mobile node during handoffs. To
achieve seamlessness, low (ideally no) latency and low (ideally
zero) packet loss handoff protocols are needed. Limiting the effect
of handoffs has the potential to improve handoff performance in
terms of latency and packet loss. This draft identifies the problem
area for seamless mobility and defines the scope of the work for the
SeaMoby work group.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-seamoby-mm-problem-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-seamoby-mm-problem-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-seamoby-mm-problem-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010227123307.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-seamoby-mm-problem-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-seamoby-mm-problem-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010227123307.I-D@ietf.org>

--OtherAccess--

--NextPart--



From owner-seamoby@diameter.org  Fri Mar  2 04:20:50 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24185
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:20:50 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229Z6e03024
	for seamoby-list; Fri, 2 Mar 2001 01:35:06 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229Ymt02989
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:34:49 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:25 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:10 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 08:07:10 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SMbuU17153
	for seamoby-list; Wed, 28 Feb 2001 14:37:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SMbro17148
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 14:37:53 -0800
Received: from davir03nok.americas.nokia.com (davir03nok.americas.nokia.com [172.18.242.86])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SLl7g00574
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 15:47:17 -0600 (CST)
Received: from daebh01nok.americas.nokia.com (unverified) by davir03nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T520223d95aac12f256081@davir03nok.americas.nokia.com>;
 Wed, 28 Feb 2001 15:47:02 -0600
Received: by daebh01nok with Internet Mail Service (5.5.2652.78)
	id <FWSVH6M2>; Wed, 28 Feb 2001 15:47:02 -0600
Message-ID: <7B5C0390ACE7D211BC9C0008C7EABA2B03213560@daeis07nok>
From: Basavaraj.Patil@nokia.com
To: Phil_Neumiller@3Com.com, mobile-ip@sunroof.eng.sun.com
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Arch discussions in IETF
Date: Wed, 28 Feb 2001 15:47:01 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


Phil,

I do not see anyone saying that Mobile IP is the only solution for all
scenarios that require mobility. I am sure there are many scenarios
that Mobile IP may or may not be the most optimal solution. If Mobile
IP is unable to work as well as anything else you may have in mind 
for specific scenarios, then why deploy Mobile IP in such scenarios?
Can you be more specific on the kind of environments and requirements
that these environments have that would make it impossible for Mobile
IP to work in.

-Basavaraj

Pls. note that the Mobile IP mailing list has a new address.

> -----Original Message-----
> From: ext Phil_Neumiller@3Com.com [mailto:Phil_Neumiller@3Com.com]
> Sent: Wednesday, February 28, 2001 1:46 PM
> To: mobile-ip@marvin.corpeast.baynetworks.com
> Cc: seamoby@diameter.org
> Subject: [seamoby] Arch discussions in IETF
> 
> 
> 
> 
> 
> We have said countless times that IETF does not define 
> architecture.  However
> MIP did.
> Many of the problems people have with MIP are with its basic 
> architecture, not
> the protocol.
> Why can't their be an architectural debate on MIP in the IETF 
> (not protocol).
> There are
> boxes defined.  There is a CN, a MN, an HA, a set of routers. 
>  Lets talk about
> how these
> need to play in today's modern residential and business 
> deployments.  Why do we
> always
> have to cater to cellular?  Why do the cellular guys get most 
> the say?   The
> Internet has
> new stuff like FTC, VoIP, SLP,  RSVP, diffserv, and new radio access
> technologies that
> can enable different types of mobility architectures.   Is an 
> HA still a good
> idea in
> every scenario?  Why?  Can we talk about this?  If not why 
> not?  Inquiring minds
> want to
> know.
> 
> Here is an example.  Why do I always need to use MIP?  Let's 
> say I have a
> community of
> VPN's defined to interlink residences that interoperate with 
> mobility (a bunch
> of families
> allows their mobiles to operate in each other's premises), 
> i.e. mobile hosts are
> allowed
> to seamless travel within theses spaces but only in theses 
> spaces (could be set
> up
> in hotel rooms, conferences, etc).  The COA changes but there 
> is no HA.
> 
> I have lots of scenarios like this.
> 
> Thanks,
> 
> Phil
> 
> 
> 
> I believe that the problem statement does have some things 
> that Mobile IP will
> have a REALLY hard time handling. However, as I have stated 
> numerous times,
> statements like "MIP is too slow" just doesn't cut it. Let's 
> get to the meat
> of the requirements, and then we can identify whether MIP can 
> do the job.
> 
> PatC
> 
> 


From owner-seamoby@diameter.org  Fri Mar  2 04:20:59 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24196
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:20:58 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222Q7n23067
	for seamoby-list; Thu, 1 Mar 2001 18:26:07 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222Pio23031
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:25:44 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:21:12 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 11:56:08 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f213A8a18244
	for seamoby-list; Wed, 28 Feb 2001 19:10:08 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f2139To18239
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 19:09:30 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id LAA229112;
	Thu, 1 Mar 2001 11:10:23 +0900
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
 by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA02460;
 Wed, 28 Feb 2001 18:18:25 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA01216;
 Wed, 28 Feb 2001 18:17:44 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SNpjs03679
 for mobile-ip-dist; Wed, 28 Feb 2001 15:51:48 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SNj2E03460
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:45:55 -0800 (PST)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA01426
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:39:32 -0800 (PST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
 by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA15276
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:39:30 -0800 (PST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
 by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f1SMdNC29492
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 23:39:23 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Wed Feb 28 23:39:06 2001 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2651.58)
 id <FV8XLT2A>; Wed, 28 Feb 2001 23:35:20 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBB0@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Arch discussions in IETF
Date: Wed, 28 Feb 2001 23:39:05 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk

> >Phil,
> >
> >I do not see anyone saying that Mobile IP is the only solution for all
> >scenarios that require mobility. I am sure there are many scenarios
> >that Mobile IP may or may not be the most optimal solution. If Mobile
> >IP is unable to work as well as anything else you may have in mind
> >for specific scenarios, then why deploy Mobile IP in such scenarios?
> 
> Then where might these other solutions be standardized in the IETF?
> Would this fall under the classification of micro-mobility even though
> the "so-called" COA or routing prefix does indeed change?  I guess what
> I am getting at is there may be cases of infra-structure-less mobility
> where the COA changes but there is no HA.  
> 
 => There was a draft presented in San Diego about Homeless 
 MIPv6. Just an example and I'm not trying to force MIP.

 Regards,

 Hesham


From owner-seamoby@diameter.org  Fri Mar  2 04:21:01 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24207
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:21:00 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222VZr23232
	for seamoby-list; Thu, 1 Mar 2001 18:31:35 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222VSo23226
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:31:28 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:26:45 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 12:28:08 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f213YnU18332
	for seamoby-list; Wed, 28 Feb 2001 19:34:49 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f213Yko18327
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 19:34:46 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id LAA155158;
	Thu, 1 Mar 2001 11:35:37 +0900
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
 by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA19021;
 Wed, 28 Feb 2001 18:43:36 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA25834;
 Wed, 28 Feb 2001 18:43:21 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SNpjs03679
 for mobile-ip-dist; Wed, 28 Feb 2001 15:51:48 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SNj2E03460
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:45:55 -0800 (PST)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA01426
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:39:32 -0800 (PST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
 by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA15276
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:39:30 -0800 (PST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
 by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f1SMdNC29492
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 23:39:23 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Wed Feb 28 23:39:06 2001 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2651.58)
 id <FV8XLT2A>; Wed, 28 Feb 2001 23:35:20 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBB0@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Arch discussions in IETF
Date: Wed, 28 Feb 2001 23:39:05 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk

> >Phil,
> >
> >I do not see anyone saying that Mobile IP is the only solution for all
> >scenarios that require mobility. I am sure there are many scenarios
> >that Mobile IP may or may not be the most optimal solution. If Mobile
> >IP is unable to work as well as anything else you may have in mind
> >for specific scenarios, then why deploy Mobile IP in such scenarios?
> 
> Then where might these other solutions be standardized in the IETF?
> Would this fall under the classification of micro-mobility even though
> the "so-called" COA or routing prefix does indeed change?  I guess what
> I am getting at is there may be cases of infra-structure-less mobility
> where the COA changes but there is no HA.  
> 
 => There was a draft presented in San Diego about Homeless 
 MIPv6. Just an example and I'm not trying to force MIP.

 Regards,

 Hesham


From owner-seamoby@diameter.org  Fri Mar  2 04:31:54 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24344
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:31:54 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222XZo23255
	for seamoby-list; Thu, 1 Mar 2001 18:33:35 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222XWo23250
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:33:32 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:27:56 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 04:33:23 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21IrYS21292
	for seamoby-list; Thu, 1 Mar 2001 10:53:34 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21IrVo21287
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 10:53:31 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id KAA14049;
	Thu, 1 Mar 2001 10:03:01 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABV01622;
	Thu, 1 Mar 2001 10:02:55 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA28818; Thu, 1 Mar 2001 10:02:55 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15006.36559.662301.41126@thomasm-u1.cisco.com>
Date: Thu, 1 Mar 2001 10:02:55 -0800 (PST)
To: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
Cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Subject: Re: [seamoby] Arch discussions in IETF
In-Reply-To: <3A9E8895.DD789091@usa.alcatel.com>
References: <7B5C0390ACE7D211BC9C0008C7EABA2B0321356A@daeis07nok>
	<3A9E8895.DD789091@usa.alcatel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I don't think this quite captures the finesse on
the issue. I don't believe that the proper framing
of the question is whether a new routing protocol
needs to be invented or not: it may very well be
that there is nothing to be done on the _routing
protocol_ front to support injecting host routes
if that's the ultimate solution. There may be work
needed to support _signaling_ a router that it
needs to change how a subnet is reachable.

I know this is hair splitting, but I think it's
important to separate out that it's quite possible
that the heavy lifting can already be done by
current protocols, and that all we need is the
ability to trigger them to happen. You might call
that a "routing protocol" too, but it ought not
evoke the fear and loathing that postulating a
Routing Protocol should.

		 MIke


Behcet Sarikaya writes:
 > Hi Raj and Phil,
 > 
 >   I think the critical question for micromobility (mm) branch of the
 > Seamoby WG is
 > to be or not to be, i.e.
 > whether another routing protocol for mobility is required. Presently we
 > have the MIP and
 > the Manet routing approaches.
 >   The alternative seems to be per-host routes or host-based routing. I do
 > not think there
 > has been another breakthrough proposal significantly different. We all know
 > Cellular IP and
 > Hawaii proposals. Recently there is probably another one based on extending
 > OSPF with
 > host-based routes.
 >   Of course there are a lot of details but I think this is the crux of
 > Seamoby mm problem.
 > 
 > --
 > Behcet
 > 


From owner-seamoby@diameter.org  Fri Mar  2 04:32:58 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24364
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:32:57 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223F1r23527
	for seamoby-list; Thu, 1 Mar 2001 19:15:01 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223Evo23522
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:14:57 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:18 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:40:27 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 02:27:17 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SHK6w16151
	for seamoby-list; Wed, 28 Feb 2001 09:20:06 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SHK3o16144
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 09:20:04 -0800
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f1SGTZd00073
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 17:29:35 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Wed Feb 28 17:29:34 2001 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2651.58)
	id <F1J9A4VB>; Wed, 28 Feb 2001 17:29:34 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBA7@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'Gopal Dommety'" <gdommety@cisco.com>
Cc: Claude Castelluccia <claude.castelluccia@inrialpes.fr>,
        seamoby@diameter.org
Subject: RE: [seamoby] Is Mobile IP too slow or is Routing Table UpdateTo 
	o slow? (was....)
Date: Wed, 28 Feb 2001 17:26:45 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hello Gopal,

I believe  Claude's statement was in reference to HMIPv6.
we don't want a multi-level hierarchy (like v4), just one level is enough.
That doesn't mean one MAP per domain, you can have several, 
but the MN only needs to choose one.

Regards,
Hesham


> -----Original Message-----
> From:	Gopal Dommety [SMTP:gdommety@cisco.com]
> Sent:	Tuesday, 27 February 2001 7:11
> To:	Claude Castelluccia
> Cc:	Andrew T. Campbell; 'Charlie Perkins'; 'Gary Kenward'; seamoby@diameter.org
> Subject:	Re: [seamoby] Is Mobile IP too slow or is Routing Table UpdateTo o slow? (was....)
> 
> 
> 
> At 12:56 PM 27/02/01 +0100, Claude Castelluccia wrote:
> >Gopal Dommety wrote: 
> >>  
> >>There are several components to handoff delay (see an  old anchor handoff draft). One of the delays is the backhaul delay 
> >>(most of the time this is not the problem unless you are doing VPN etc). If this is a problem it is better to perform anchor kind of a handoff.
> >I don't understand your point...HMIP provides "anchor-based" handoffs... 
> > It is based on MAP (Mobile ANCHOR Points) but these MAPs do not have to be deployed (although they 
> >can) on every links (as most of others fast handoff solutions require) .... 
> >>  
> >>Hierarchical instantiations do help but mainly to reduce the signaling (or limit the signaling to the local domain). 
> >> 
> >not only ....it reduces handoff delay, provides location privacy and a lot more ;-)  
> 
> Depending on the hierarchys and the movement it could increase the latency (the packet processing time is typicall order of magnitude than the
> packet forwarding time). Long time  ago I happen to have done some research on the
> number of hierarchies on the impact of handoff latencies and signalling. For internet kind of traffic (the actual paraments are the packet
> processing  times and the forwarding delays of routers) the number of hierarchies tended to be 2 (HA and FA) for handoff latencies.
> 
> -Gopal
> 
> 
> 
> >Claude. 
> >-- 
> >
> >----------------------------------------
> >Claude CASTELLUCCIA, INRIA Rhone-Alpes  
> >ph:  +33 4.76.61.52.15 (fax: 52.52)
> ><http://www.inrialpes.fr/planete/>http://www.inrialpes.fr/planete/  


From owner-seamoby@diameter.org  Fri Mar  2 04:33:05 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24375
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:33:04 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222QDD23069
	for seamoby-list; Thu, 1 Mar 2001 18:26:13 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222Pno23040
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:25:50 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:21:25 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 12:50:22 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f213hqC18378
	for seamoby-list; Wed, 28 Feb 2001 19:43:52 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f213hno18372
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 19:43:50 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id LAA138982;
	Thu, 1 Mar 2001 11:44:44 +0900
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
 by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA24652;
 Wed, 28 Feb 2001 18:53:07 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA29100;
 Wed, 28 Feb 2001 18:52:32 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SNpjs03679
 for mobile-ip-dist; Wed, 28 Feb 2001 15:51:48 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SNj2E03460
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:45:55 -0800 (PST)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA01426
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:39:32 -0800 (PST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
 by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA15276
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:39:30 -0800 (PST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
 by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f1SMdNC29492
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 23:39:23 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Wed Feb 28 23:39:06 2001 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2651.58)
 id <FV8XLT2A>; Wed, 28 Feb 2001 23:35:20 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBB0@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Arch discussions in IETF
Date: Wed, 28 Feb 2001 23:39:05 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk

> >Phil,
> >
> >I do not see anyone saying that Mobile IP is the only solution for all
> >scenarios that require mobility. I am sure there are many scenarios
> >that Mobile IP may or may not be the most optimal solution. If Mobile
> >IP is unable to work as well as anything else you may have in mind
> >for specific scenarios, then why deploy Mobile IP in such scenarios?
> 
> Then where might these other solutions be standardized in the IETF?
> Would this fall under the classification of micro-mobility even though
> the "so-called" COA or routing prefix does indeed change?  I guess what
> I am getting at is there may be cases of infra-structure-less mobility
> where the COA changes but there is no HA.  
> 
 => There was a draft presented in San Diego about Homeless 
 MIPv6. Just an example and I'm not trying to force MIP.

 Regards,

 Hesham


From owner-seamoby@diameter.org  Fri Mar  2 04:38:08 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24397
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:38:07 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223HEL23688
	for seamoby-list; Thu, 1 Mar 2001 19:17:14 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223HBo23683
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:17:11 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:03 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:38 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 06:52:38 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SLf5e16953
	for seamoby-list; Wed, 28 Feb 2001 13:41:05 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sirius.ctr.columbia.edu (sirius.ctr.columbia.edu [128.59.64.60])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SLf2o16948
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 13:41:02 -0800
Received: from SWEETPEA (sweetpea.comet.columbia.edu [128.59.68.61]) by sirius.ctr.columbia.edu (8.9.3/8.6.4.287) with SMTP id PAA07057; Wed, 28 Feb 2001 15:48:50 -0500 (EST)
From: "Andrew T. Campbell" <campbell@comet.columbia.edu>
To: "'Pat Calhoun'" <pcalhoun@nasnfs.Eng.Sun.COM>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>
Cc: "'James Kempf'" <james.kempf@sun.com>, <Phil_Neumiller@3com.com>,
        <seamoby@diameter.org>
Subject: RE: [seamoby] Yet Another BOF?
Date: Wed, 28 Feb 2001 15:48:21 -0800
Message-ID: <006501c0a1e0$ef93f010$3d443b80@SWEETPEA>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
In-Reply-To: <Roam.SIMC.2.0.6.983384676.23816.pcalhoun@nasnfs>
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>  However, as I have stated 
> numerous times,
> statements like "MIP is too slow" just doesn't cut it.  

Lets try it this way then - please shoot me down.

We clearly believe that micro-mobility means not invoking
the MIP HAs each time we handoff? So all the action must be local.
That excludes vanilla MIP as a solution and under those
conditions its slow and lossy, etc. 

So what is this local protocol? I would claim that trees,
levels of FAs and tunneling (the base MIP class) are 
costly (tunnel/detunel overhead/complexity)
and not robust (the tree of FAs, single gateways). 
I'm not digging here; just some unsubstantiated 
thoughts off the top of my head. 

The point that a number of people are making (and 
developing solutions for, e.g., CIP, Hawaii, etc.) 
is that if I'm forced to use FAs (trees and levels of them),
tunneling and MIP signaling to solve every new
wireless problem (e.g., QOS, fast handoff, etc.) 
that surfaces in IETF, then, how do we innovate 
and deliver new wireless IP technologies?  

Is this because people think that the investment in MIP
is so great that must reap dividend at no end? sister of
MIP, cousin of MIP, etc.

Coupling each development to the base MIP mechanisms
(FAs, tunneling, MIP signaling) as a perquisite to
the development of new wireless IP protocols is a
little like driving a car with a straight-jacket on.

Building fast/seamless handoff, paging, context, 
QOS, etc. etc., on MIP is where we are heading today;
consensus or not; it looks to me its all engineered
that way? 

The goals should to let MIP be the macro-mobilty 
protocol to interwork with and allow 
new and innovative technologies with 
(for fast handoff, seamless, fast security, 
QOS, context, etc. etc.) to be created.















From owner-seamoby@diameter.org  Fri Mar  2 04:38:32 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24408
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:38:32 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229Y5i02927
	for seamoby-list; Fri, 2 Mar 2001 01:34:05 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229Xwt02921
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:33:59 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:10 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:58 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:58:33 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SN89i17298
	for seamoby-list; Wed, 28 Feb 2001 15:08:09 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SN85o17293
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 15:08:05 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id HAA226548;
	Thu, 1 Mar 2001 07:08:56 +0900
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
 by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA26835;
 Wed, 28 Feb 2001 14:16:56 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA25737;
 Wed, 28 Feb 2001 14:16:22 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SMD6j01965
 for mobile-ip-dist; Wed, 28 Feb 2001 14:13:06 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SMCvE01955
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA00357
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
From: Phil_Neumiller@3Com.com
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA23795
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:12:56 -0700 (MST)
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
 by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SMBSo14321;
 Wed, 28 Feb 2001 14:11:28 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
 by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f1SMCnX06019;
 Wed, 28 Feb 2001 14:12:49 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A01.007A28B7 ; Wed, 28 Feb 2001 14:14:18 -0800
X-Lotus-FromDomain: 3COM
To: mobile-ip@sunroof.eng.sun.com
cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Message-ID: <88256A01.007A25AA.00@hqoutbound.ops.3com.com>
Date: Wed, 28 Feb 2001 16:11:37 -0600
Subject: RE: [seamoby] Arch discussions in IETF
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk





Hi Raj,

>Phil,
>
>I do not see anyone saying that Mobile IP is the only solution for all
>scenarios that require mobility. I am sure there are many scenarios
>that Mobile IP may or may not be the most optimal solution. If Mobile
>IP is unable to work as well as anything else you may have in mind
>for specific scenarios, then why deploy Mobile IP in such scenarios?

Then where might these other solutions be standardized in the IETF?
Would this fall under the classification of micro-mobility even though
the "so-called" COA or routing prefix does indeed change?  I guess what
I am getting at is there may be cases of infra-structure-less mobility
where the COA changes but there is no HA.  Would this be micro or
macro mobility?

>Can you be more specific on the kind of environments and requirements
>that these environments have that would make it impossible for Mobile
>IP to work in.

Sure.  Specifically, I am very interested in portable devices that will
find there way into homes.  Wireless appliances, MP3 players, digital
radios, digital security devices, gaming units, VoIP devices, etc.  I
am also interested in these types of devices that may be used in small
to medium business that may not have large infrastructures in place.

Thank you,

Phil Neumiller



From owner-seamoby@diameter.org  Fri Mar  2 04:38:37 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24419
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:38:35 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222R7O23112
	for seamoby-list; Thu, 1 Mar 2001 18:27:07 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222R2o23106
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:27:03 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:23:36 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 12:17:26 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f213JDc18279
	for seamoby-list; Wed, 28 Feb 2001 19:19:13 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f213J9o18274
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 19:19:10 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id LAA197054;
	Thu, 1 Mar 2001 11:20:04 +0900
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA01623;
 Wed, 28 Feb 2001 18:28:30 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA02844;
 Wed, 28 Feb 2001 18:28:16 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f212QJu05321
 for mobile-ip-dist; Wed, 28 Feb 2001 18:26:19 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f211xBE04716
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 17:59:26 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA26428
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 17:42:18 -0800 (PST)
From: Basavaraj.Patil@nokia.com
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
 by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA11001
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 17:42:18 -0800 (PST)
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
 by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f211g7g18040
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 19:42:17 -0600 (CST)
Received: from daebh02nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5202fb13dbac12f25715a@davir04nok.americas.nokia.com>;
 Wed, 28 Feb 2001 19:42:07 -0600
Received: by daebh02nok with Internet Mail Service (5.5.2652.78)
 id <FWSXVBXT>; Wed, 28 Feb 2001 19:42:07 -0600
Message-ID: <7B5C0390ACE7D211BC9C0008C7EABA2B0321356A@daeis07nok>
To: mobile-ip@sunroof.eng.sun.com
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Arch discussions in IETF
Date: Wed, 28 Feb 2001 19:42:06 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
 charset="iso-8859-1"
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk

Phil,

Comments inline:

>Hi Raj,
>
>>Phil,
>>
>>I do not see anyone saying that Mobile IP is the only solution for all
>>scenarios that require mobility. I am sure there are many scenarios
>>that Mobile IP may or may not be the most optimal solution. If Mobile
>>IP is unable to work as well as anything else you may have in mind
>>for specific scenarios, then why deploy Mobile IP in such scenarios?
>
>Then where might these other solutions be standardized in the IETF?

Seamoby??? Some other WG (MANET, Mobile IP, New WG)? Or is it the
IRTF that 

Do these kind of scenarios and problems get covered in the mobility
management problems statement I-D? If you believe this kind of
mobility currently does not have a WG in the IETF that deals with it,
then maybe that's what Seamoby should do. 

>Would this fall under the classification of micro-mobility even though
>the "so-called" COA or routing prefix does indeed change?  I guess what
>I am getting at is there may be cases of infra-structure-less mobility
>where the COA changes but there is no HA.  Would this be micro or
>macro mobility?
>

The terms micro and macro mobility are overloaded and perceptions are
different w.r.t where micro mobility ends and macro mobility
begins. The non-existence of an HA has no implications on whether you
are dealing with micro or macro mobility. I mean do you consider macro
mobility as only those cases wherein the MN sends a binding update to
the HA?


>>Can you be more specific on the kind of environments and requirements
>>that these environments have that would make it impossible for Mobile
>>IP to work in.
>
>Sure.  Specifically, I am very interested in portable devices that will
>find there way into homes.  Wireless appliances, MP3 players, digital
>radios, digital security devices, gaming units, VoIP devices, etc.  I
>am also interested in these types of devices that may be used in small
>to medium business that may not have large infrastructures in place.
>

Is there any limitation in terms of having Mobile IP support for such
devices? And why would you not be able to have Mobile IP in whatever
infrastructure exists (either in the home network or the small
business)? Are you concerned with the fact that if you have Mobile IP,
then you need an HA at the least (in the case of IPv6)? 

>Thank you,
>
>Phil Neumiller
>
Regards,
-Basavaraj



From owner-seamoby@diameter.org  Fri Mar  2 04:40:31 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24435
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:40:29 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229Z8203026
	for seamoby-list; Fri, 2 Mar 2001 01:35:08 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229Yrt02996
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:34:53 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:10 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:56 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 06:42:56 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SLsLJ17003
	for seamoby-list; Wed, 28 Feb 2001 13:54:21 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SLsHo16998
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 13:54:18 -0800
Received: (from sob@localhost)
	by newdev.harvard.edu (8.9.3/8.9.3) id QAA24054;
	Wed, 28 Feb 2001 16:02:39 -0500 (EST)
Date: Wed, 28 Feb 2001 16:02:39 -0500 (EST)
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200102282102.QAA24054@newdev.harvard.edu>
To: campbell@comet.columbia.edu, gkenward@nortelnetworks.com,
        pcalhoun@nasnfs.eng.sun.com
Subject: RE: [seamoby] Yet Another BOF?
Cc: james.kempf@sun.com, Phil_Neumiller@3Com.com, seamoby@diameter.org
Sender: owner-seamoby@diameter.org
Precedence: bulk

anything that includes the text "That excludes vanilla MIP as a solution"
does not look like a requirements discusison to me 

why is it so hard to discuss what the actual requirents are without
talking about solutions?

Scott


From owner-seamoby@diameter.org  Fri Mar  2 04:41:36 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24450
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:41:35 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222PrF23042
	for seamoby-list; Thu, 1 Mar 2001 18:25:53 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222Peo23026
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:25:41 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:21:10 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 11:29:46 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f212Wx518137
	for seamoby-list; Wed, 28 Feb 2001 18:32:59 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f212Wuo18132
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 18:32:56 -0800
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f211gVg18072
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 19:42:31 -0600 (CST)
Received: from daebh02nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5202fb13dbac12f25715a@davir04nok.americas.nokia.com>;
 Wed, 28 Feb 2001 19:42:07 -0600
Received: by daebh02nok with Internet Mail Service (5.5.2652.78)
	id <FWSXVBXT>; Wed, 28 Feb 2001 19:42:07 -0600
Message-ID: <7B5C0390ACE7D211BC9C0008C7EABA2B0321356A@daeis07nok>
From: Basavaraj.Patil@nokia.com
To: mobile-ip@sunroof.eng.sun.com
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Arch discussions in IETF
Date: Wed, 28 Feb 2001 19:42:06 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


Phil,

Comments inline:

>Hi Raj,
>
>>Phil,
>>
>>I do not see anyone saying that Mobile IP is the only solution for all
>>scenarios that require mobility. I am sure there are many scenarios
>>that Mobile IP may or may not be the most optimal solution. If Mobile
>>IP is unable to work as well as anything else you may have in mind
>>for specific scenarios, then why deploy Mobile IP in such scenarios?
>
>Then where might these other solutions be standardized in the IETF?

Seamoby??? Some other WG (MANET, Mobile IP, New WG)? Or is it the
IRTF that 

Do these kind of scenarios and problems get covered in the mobility
management problems statement I-D? If you believe this kind of
mobility currently does not have a WG in the IETF that deals with it,
then maybe that's what Seamoby should do. 

>Would this fall under the classification of micro-mobility even though
>the "so-called" COA or routing prefix does indeed change?  I guess what
>I am getting at is there may be cases of infra-structure-less mobility
>where the COA changes but there is no HA.  Would this be micro or
>macro mobility?
>

The terms micro and macro mobility are overloaded and perceptions are
different w.r.t where micro mobility ends and macro mobility
begins. The non-existence of an HA has no implications on whether you
are dealing with micro or macro mobility. I mean do you consider macro
mobility as only those cases wherein the MN sends a binding update to
the HA?


>>Can you be more specific on the kind of environments and requirements
>>that these environments have that would make it impossible for Mobile
>>IP to work in.
>
>Sure.  Specifically, I am very interested in portable devices that will
>find there way into homes.  Wireless appliances, MP3 players, digital
>radios, digital security devices, gaming units, VoIP devices, etc.  I
>am also interested in these types of devices that may be used in small
>to medium business that may not have large infrastructures in place.
>

Is there any limitation in terms of having Mobile IP support for such
devices? And why would you not be able to have Mobile IP in whatever
infrastructure exists (either in the home network or the small
business)? Are you concerned with the fact that if you have Mobile IP,
then you need an HA at the least (in the case of IPv6)? 

>Thank you,
>
>Phil Neumiller
>
Regards,
-Basavaraj


From owner-seamoby@diameter.org  Fri Mar  2 04:42:41 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24464
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:42:40 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222QJk23073
	for seamoby-list; Thu, 1 Mar 2001 18:26:19 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222Pno23041
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:25:50 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:21:28 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 09:54:17 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f210oRD17770
	for seamoby-list; Wed, 28 Feb 2001 16:50:27 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f210oNo17765
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 16:50:24 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id IAA142084;
	Thu, 1 Mar 2001 08:51:15 +0900
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA17065;
 Wed, 28 Feb 2001 15:59:32 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA23386;
 Wed, 28 Feb 2001 15:54:13 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SMI3p02222
 for mobile-ip-dist; Wed, 28 Feb 2001 14:18:03 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SMHdE02179
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:17:39 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA27233
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:17:39 -0800 (PST)
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
 by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA13692
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:17:38 -0800 (PST)
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
 by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id HAA226548;
 Thu, 1 Mar 2001 07:08:56 +0900
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
 by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA26835;
 Wed, 28 Feb 2001 14:16:56 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA25737;
 Wed, 28 Feb 2001 14:16:22 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SMD6j01965
 for mobile-ip-dist; Wed, 28 Feb 2001 14:13:06 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SMCvE01955
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA00357
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
From: Phil_Neumiller@3Com.com
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA23795
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:12:56 -0700 (MST)
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
 by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SMBSo14321;
 Wed, 28 Feb 2001 14:11:28 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
 by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f1SMCnX06019;
 Wed, 28 Feb 2001 14:12:49 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A01.007A28B7 ; Wed, 28 Feb 2001 14:14:18 -0800
X-Lotus-FromDomain: 3COM
To: mobile-ip@sunroof.eng.sun.com
cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Message-ID: <88256A01.007A25AA.00@hqoutbound.ops.3com.com>
Date: Wed, 28 Feb 2001 16:11:37 -0600
Subject: RE: [seamoby] Arch discussions in IETF
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk




Hi Raj,

>Phil,
>
>I do not see anyone saying that Mobile IP is the only solution for all
>scenarios that require mobility. I am sure there are many scenarios
>that Mobile IP may or may not be the most optimal solution. If Mobile
>IP is unable to work as well as anything else you may have in mind
>for specific scenarios, then why deploy Mobile IP in such scenarios?

Then where might these other solutions be standardized in the IETF?
Would this fall under the classification of micro-mobility even though
the "so-called" COA or routing prefix does indeed change?  I guess what
I am getting at is there may be cases of infra-structure-less mobility
where the COA changes but there is no HA.  Would this be micro or
macro mobility?

>Can you be more specific on the kind of environments and requirements
>that these environments have that would make it impossible for Mobile
>IP to work in.

Sure.  Specifically, I am very interested in portable devices that will
find there way into homes.  Wireless appliances, MP3 players, digital
radios, digital security devices, gaming units, VoIP devices, etc.  I
am also interested in these types of devices that may be used in small
to medium business that may not have large infrastructures in place.

Thank you,

Phil Neumiller





From owner-seamoby@diameter.org  Fri Mar  2 04:46:46 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24522
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:46:44 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229fgc03224
	for seamoby-list; Fri, 2 Mar 2001 01:41:42 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229fdt03219
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:41:39 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:19:57 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:57:17 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 08:06:48 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21N9kF22316
	for seamoby-list; Thu, 1 Mar 2001 15:09:46 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21N9ho22311
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 15:09:43 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id OAA02681;
	Thu, 1 Mar 2001 14:19:32 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABV08482;
	Thu, 1 Mar 2001 14:19:13 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id OAA28891; Thu, 1 Mar 2001 14:19:13 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
Message-ID: <15006.51937.60735.267223@thomasm-u1.cisco.com>
Date: Thu, 1 Mar 2001 14:19:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Hemant.Chaskar@nokia.com
Cc: mat@cisco.com, hchaskar@hotmail.com, Hesham.Soliman@era.ericsson.se,
        james.kempf@sun.com, mobile-ip@sunroof.eng.sun.com,
        seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
In-Reply-To: <B9CFA6CE8FFDD211A1FB0008C7894E46027F445C@bseis01nok>
References: <B9CFA6CE8FFDD211A1FB0008C7894E46027F445C@bseis01nok>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I really don't even know where to begin. It seems
that your claim is that RSVP's receiver oriented
PATH/RESV is either flawed, or should have a mode
which allows a single pass. I believe this leads
to overbooking for multicast since you don't get
to do flow merging properly and a host of other
reasons that I don't purport to understand well.

What I really don't understand is why MIP would be
the right place to solve this problem. If it has
merit, the RSVP folks seems like a much more
appropriate set of people to entertain such a
proposal. I suspect that they'd be able to supply
a lot more reasons why they designed RSVP the way
they did. Suggesting that mobileip is a breed
apart that requires its own QoS mechanisms sounds
just as wrong headed as RSVP folks designing their
own mobility protocol.

		Mike

Hemant.Chaskar@nokia.com writes:
 > Yes, it goes end to end. But there is a basic difference illustrated 
 > by following example. If we look at the latency between time end nodes
 > are ready to use new CoA and the time QoS forwarding treatment is programmed
 > 
 > over the new path, it can be seen that RSVP takes one end-to-end round trip
 > time 
 > between these two events. On the other hand, including QoS object with
 > binding
 > messages performs QoS programming before the nodes release packets using
 > new CoA. This is shown by following illustration.
 > 
 > Suppose MN is currently at CoA1. Consider data traffic from the
 > CN towards the MN (downlink direction).
 > 
 >    o MN moves to CoA2.
 > 
 >    o MN sends BU from CoA2.
 > 
 >    ----[One way end-to-end delay]----
 > 
 >    o BU reaches CN. CN sends BA to MN at CoA2.
 > 
 >    In RSVP, CN sends PATH message to MN at CoA2.
 > 
 >    In our approach, QoS OBJECT OPTION for downlink packet stream(s)
 >    is included in HOP-by-HOP OPTIONS EXTENSION HEADER with the BA.
 > 
 >    o CN may start sending MN's packets to CoA2. These packets
 >    contain CoA2 as destination address. 
 > 
 >    **In RSVP approach, they are not identified by existing
 >    reservations for MN's sessions. This is because, RSVP session is
 >    primarily identified by destination address which now has changed
 >    from CoA1 to CoA2. Hence, these packets will get default
 >    forwarding treatment.**
 > 
 >    **In our approach, the packet carrying QoS information about these
 >    packets precedes these packets, and hence, they can get proper
 >    forwarding treatment.**
 > 
 >    ----[One way end-to-end delay]----
 > 
 >    o BA reaches MN at CoA2. In RSVP approach, PATH message reaches
 >    MN at CoA2.
 > 
 >    o In RSVP approach, MN sends RESV to CN.
 > 
 >    ----[One way end-to-end delay]----
 > 
 >    o In RSVP approach, RESV reaches CN. 
 > 
 >    **In RSVP approach, it is at this time that the proper QoS
 >    forwarding treatment is programmed at the intermediate network
 >    domains for packets destined to CoA2.**
 > 
 > 
 > Hemant
 > 
 > -----Original Message-----
 > From: Michael Thomas [mailto:mat@cisco.com]
 > Sent: 01. March 2001 13:33
 > To: Hemant Chaskar
 > Cc: Hesham.Soliman@era.ericsson.se; james.kempf@sun.com;
 > mobile-ip@marvin.corpeast.baynetworks.com; seamoby@diameter.org
 > Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
 > 
 > 
 > 
 > I don't see how this fundamentally changes
 > anything that James brought up. It still has to go
 > end to end, and it's still touching every router
 > in between MN and CN. 
 > 
 > What I do see is a lot of reinvention of RSVP
 > Rspec and Tspec's for no known reason.  The only
 > thing I can see of possible value is the ability
 > to piggyback the QoS update with the BU, but even
 > if this is the sole goal -- and that it's a worthy
 > goal which is not at all apparent to me -- I
 > imagine that there are better ways of doing this
 > with out reinventing RSVP: like, maybe,
 > piggybacking the BU on the PATH, or some such.
 > 
 > 	     Mike
 > 
 > 
 > Hemant Chaskar writes:
 >  > Regarding the issue of round-trip latency in programming QoS forwarding 
 >  > treatment along new path after change in CoA:
 >  > 
 >  > This is intrinsic drawback of OPWA model of resource reservation of RSVP.
 > In 
 >  > the worst case, one round-trip time will include traversals of four
 > wireless 
 >  > links. This happens when both CN and MN are mobile.
 >  > 
 >  > Note that this drawback is eliminated in the approach to QoS signaling
 > based 
 >  > on including QoS Object in hop-by-hop options extension header along with
 > 
 >  > binding messages (draft-chaskar-mobileip-qos-00.txt). This draft was 
 >  > presented in SD and revised version (01) will be submitted soon.
 >  > 
 >  > Hemant
 >  > _________________________________________________________________
 >  > Get your FREE download of MSN Explorer at http://explorer.msn.com
 >  > 


From owner-seamoby@diameter.org  Fri Mar  2 04:47:23 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24537
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:47:20 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229Xte02914
	for seamoby-list; Fri, 2 Mar 2001 01:33:55 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229Xqt02908
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:33:52 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:11 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:58 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 05:18:27 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SKWk816728
	for seamoby-list; Wed, 28 Feb 2001 12:32:46 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SKWho16723
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 12:32:44 -0800
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f1SJgGC01869
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 20:42:16 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Wed Feb 28 20:42:17 2001 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2651.58)
	id <F1J9B31L>; Wed, 28 Feb 2001 20:42:15 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBAB@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'James Kempf'" <james.kempf@sun.com>,
        "'mobile-ip@standards.nortelnetworks.com'"
	 <mobile-ip@standards.nortelnetworks.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
Date: Wed, 28 Feb 2001 20:42:15 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk


> (Hoping this gets through the MIP mailing list problems...)
> 
	=> It didn't. I think this is definitely a MIP issue so we should 
	discuss it on the MIP list. You need to send your mail to
	mobile-ip@standards.nortelnetworks.com

> In draft-thomas-seamoby-rsvp-analysis-00.txt, some serious problems with MIP
> and RSVP signalling are identified. 
> 
	=> Sure RSVP doesn't handle IP mobility.

> Specifically, when a handoff occurs,
> a round-trip BU must occur before the CN can issue an RSVP PATH message
> to assure QoS over the new route. Aggregated RSVP (see 
> draft-ietf-rsvp-aggr-02.txt)
> doesn't help, because the BU must still propogate to the CN for the CN to issue
> the PATH. All aggregation does is reduce the state in routers internal to the
> aggregation region, it does not reduce signalling requirements over 
> standard RSVP.
> 
	=> Yes.

> There is a case where signalling can be optimized that is identified in
> draft-thomas-seamoby-rsvp-analysis-00.txt. This is the case where the movement
> of the mobile does not involve a change in CoA but rather is handled by 
> installing
> a new host route up to the join router between the old and new path. 
> Establishment
> of the new route is followed by a PATH message from the new join router
> to the MN, and a RESV from the MN back to the join router (pg. 10 in the 
> draft).
> 
> In draft-malinen-mobileip-regreg6-00.txt, a hierarchical MIP mechanism (called
> regional registrations) is defined that works very much like a host route. 
> Routers
> 
	=> No it doesn't. The MN's CoA changes when the MN moves.

> between the new access router and the join router (called a crossover router
> in the draft) examine a BU routing option and the join router reconfigures its
> binding table to take account of the new route. The routers here are defined
> to be special regional aware routers, but the principle is the same.
> 
> Note that in HMIPv6 (draft-ietf-mobileip-hmipv6-01.txt), since the 
> intervening routers between the MAP and the mobile node never see the 
> topology change, the same severe performance penalties w.r.t. RSVP 
> signalling as in the standard
> MIPv6 case should occur.
> 
	=> If you believe a crossover router solves the problem
	then you can see the MAP as the same thing. But the fact
	is neither a cross over router (in draft-malinen-...) nor HMIPv6
	solves that problem. A new PATH needs to be setup anyway
	for the outgoing traffic. The path between the MAP and the 
	CN is unchanged for incoming traffic.

> So, I'm wondering if the regional registration BU routing option could 
> serve as a trigger for redoing the RSVP signalling for QoS? Comments?
> 
	=> I think the problem is much bigger than that. The issue of mobility 
	and QoS needs to be addressed in more detail. Michael's draft (I haven't
	finished it yet) is a very good start. We can't solve it for HMIP only, 
	the problem needs to be addressed for MIP in general.

	Regards,
	Hesham 


From owner-seamoby@diameter.org  Fri Mar  2 04:48:53 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24554
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 04:48:51 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229cYw03173
	for seamoby-list; Fri, 2 Mar 2001 01:38:34 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229cUt03163
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:38:31 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:19:49 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:57:52 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 08:05:07 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21NIMJ22351
	for seamoby-list; Thu, 1 Mar 2001 15:18:22 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21NIKo22346
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 15:18:20 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f21MQUo08495;
	Thu, 1 Mar 2001 14:26:30 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f21MRpX16576;
	Thu, 1 Mar 2001 14:27:51 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A02.007B8A35 ; Thu, 1 Mar 2001 14:29:23 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
cc: Gary Kenward <gkenward@nortelnetworks.com>, seamoby@diameter.org
Message-ID: <88256A02.007B6BCB.00@hqoutbound.ops.3com.com>
Date: Thu, 1 Mar 2001 16:25:31 -0600
Subject: Re: [seamoby] Yet Another BOF?
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk




Hi Charlie,

.begin  :-) :-O  <- (foot)  :-)

Many pundits state (maybe its in your new book :-)) that mobile hosts will soon
out number fixed hosts.  This makes me think its a good thing that MIP is
becoming the Swiss army knife of mobility.  My thoughts now are that mobility
should be completely embedded into IPvX itself.  Thus MIP should be selectively
absorbed into IP.  IPv6 took some steps in that direction.  Of course a process
such as this would take years.  Why should mobility be separate from the routing
fabric of the global Internet if most the hosts are mobile?

I think its interesting how a double standard has been applied to the rigour
used
when developing macro and micro techniques,  We have been told that qualitative
words like fast wont do yet the  MIP "fast" handoff work is littered with them.

Do you think IPv4 / IPv6 bi-furcated MIP with fast smooth and HMIP will still be
pretty simple when all is RFCd?

People have tried to solve all kinds of problems with SIP and PPP and RADIUS
in places where something else would have worked better.  So I don't understand
your point.  You know the old idiom, if your only  tool is a hammer, everything
looks
like a nail.  In the case of mobility problems, people come to the IETF and see
one mobility tool RFC 2002 (there are some screwdrivers and wrenches being
worked on).

You said un-adorned meaning no speed tricks right?  If not, then better latency
characteristics begs the question of what baseline?  Does the MIP WG expect the
SeaMoby WG to predict how "fast" fast is?   Even unadorned how would SeaMoby
determine a baseline considered fair by all?  Also, this work as James has
indicated would take analytical modelling, simulation, and possibly prototypes
and
or measurement.

Thank you,

Phil Neumiller




Sent by:  "Charles E. Perkins" <charliep@iprg.nokia.com>


To:   Gary Kenward <gkenward@nortelnetworks.com>
cc:   seamoby@diameter.org (Phil Neumiller/MW/US/3Com)
Subject:  Re: [seamoby] Yet Another BOF?




Hello Gary,

That's an interesting statement.  You might apply it to
other protocols to figure out:

"well, we can make SIP do that"
"well, we can make RADIUS do that"
"well, we can make PPP do that"

Mobile IP is supposed to be pretty simple, all in all,
just a way to associate a routing address to an identifying
address as needed.  Now [seamoby-mm] is presumably going to
make some protocol that enables local routability with
better latency characteristics, in addition to the global
association managed by ("unadorned") Mobile IP.  Or,
perhaps instead of, but I don't see so much why the latter.

But, as the success of IP proves, network-layer addressing
is so powerful that it is easy to imagine ways to fiddle
with it and get a lot of cool results.

Thus, it is easy to understand
"well, we can make Mobile IP do that"...
And I don't think it's necessarily an
unfortunate thing that people are thinking
about such things.  But, on the other hand,
it's important to avoid protocol bloat and
unnecessary requirements.  To me that just
means that good engineering is required.

Regards,
Charlie P.




> Gary Kenward wrote:
>
> It's just my perception Scott, but it seems like the response to any
> identified requirement is "well, we can make MIP do that"....
>
> Gary
>
> > -----Original Message-----
> > From: Scott Bradner [mailto:sob@harvard.edu]
> > Sent: Wednesday, February 28, 2001 4:03 PM
> > To: campbell@comet.columbia.edu; Kenward, Gary [WDLN2:AN10:EXCH];
> > pcalhoun@nasnfs.eng.sun.com
> > Cc: james.kempf@sun.com; Phil_Neumiller@3Com.com; seamoby@diameter.org
> > Subject: RE: [seamoby] Yet Another BOF?
> >
> >
> > anything that includes the text "That excludes vanilla MIP as
> > a solution"
> > does not look like a requirements discusison to me
> >
> > why is it so hard to discuss what the actual requirents are without
> > talking about solutions?
> >
> > Scott
> >
> >




From owner-seamoby@diameter.org  Fri Mar  2 05:02:50 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24687
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:02:49 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229Yvw03003
	for seamoby-list; Fri, 2 Mar 2001 01:34:57 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229Ymt02991
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:34:49 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:25 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:08 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:37:27 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SMekh17187
	for seamoby-list; Wed, 28 Feb 2001 14:40:46 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SMego17182
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 14:40:42 -0800
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SLoGg00941
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 15:50:16 -0600 (CST)
Received: from daebh02nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T52022655faac12f25715a@davir04nok.americas.nokia.com>;
 Wed, 28 Feb 2001 15:49:45 -0600
Received: by daebh02nok with Internet Mail Service (5.5.2652.78)
	id <FWSX4951>; Wed, 28 Feb 2001 15:49:45 -0600
Message-ID: <7B5C0390ACE7D211BC9C0008C7EABA2B03213561@daeis07nok>
From: Basavaraj.Patil@nokia.com
To: Hesham.Soliman@era.ericsson.se, james.kempf@sun.com,
        mobile-ip@sunroof.eng.sun.com
Cc: claude.castelluccia@inrialpes.fr, seamoby@diameter.org, gdommety@cisco.com
Subject: RE: [seamoby] Is Mobile IP too slow or is Routing Table UpdateTo 
	 o slow? (was....)
Date: Wed, 28 Feb 2001 15:49:44 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


> 
> 
> 	Hi James
> 
> > Can you elaborate why you believe a design that 
> accommodates multiple levels of
> > hierarchy is a bad idea? The draft doesn't go into much 
> detail on this point.
> > 
> 	=> Well since the MIP list is broken we can take the discusion
> 	on the sister list :)

The new MIP list is located at : mobile-ip@sunroof.eng.sun.com

-Basavaraj


From owner-seamoby@diameter.org  Fri Mar  2 05:03:00 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24699
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:02:59 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229YJ102958
	for seamoby-list; Fri, 2 Mar 2001 01:34:19 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229YBt02943
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:34:11 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:14 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:14 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:52:04 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SMhOT17207
	for seamoby-list; Wed, 28 Feb 2001 14:43:24 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SMhJo17202
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 14:43:20 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id GAA148480;
	Thu, 1 Mar 2001 06:43:49 +0900
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
 by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA03823;
 Wed, 28 Feb 2001 13:51:57 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA25077;
 Wed, 28 Feb 2001 13:51:51 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SLoMM01526
 for mobile-ip-dist; Wed, 28 Feb 2001 13:50:22 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SLo7E01503
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 13:50:08 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA19101
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 13:50:06 -0800 (PST)
From: Basavaraj.Patil@nokia.com
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA10922
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:49:45 -0700 (MST)
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
 by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SLnjg00849
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:49:45 -0600 (CST)
Received: from daebh02nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T52022655faac12f25715a@davir04nok.americas.nokia.com>;
 Wed, 28 Feb 2001 15:49:45 -0600
Received: by daebh02nok with Internet Mail Service (5.5.2652.78)
 id <FWSX4951>; Wed, 28 Feb 2001 15:49:45 -0600
Message-ID: <7B5C0390ACE7D211BC9C0008C7EABA2B03213561@daeis07nok>
To: Hesham.Soliman@era.ericsson.se, james.kempf@sun.com,
        mobile-ip@sunroof.eng.sun.com
Cc: claude.castelluccia@inrialpes.fr, seamoby@diameter.org, gdommety@cisco.com
Subject: RE: [seamoby] Is Mobile IP too slow or is Routing Table UpdateTo 
  o slow? (was....)
Date: Wed, 28 Feb 2001 15:49:44 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
 charset="iso-8859-1"
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk

> 
> 
>  Hi James
> 
> > Can you elaborate why you believe a design that 
> accommodates multiple levels of
> > hierarchy is a bad idea? The draft doesn't go into much 
> detail on this point.
> > 
>  => Well since the MIP list is broken we can take the discusion
>  on the sister list :)

The new MIP list is located at : mobile-ip@sunroof.eng.sun.com

-Basavaraj


From owner-seamoby@diameter.org  Fri Mar  2 05:03:06 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24714
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:03:05 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229ZFT03034
	for seamoby-list; Fri, 2 Mar 2001 01:35:15 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229Z2t03017
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:35:03 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:22 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:06 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:59:01 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SN5nw17289
	for seamoby-list; Wed, 28 Feb 2001 15:05:49 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SN5ko17284
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 15:05:46 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id HAA63294;
	Thu, 1 Mar 2001 07:06:26 +0900
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA00335;
 Wed, 28 Feb 2001 14:14:52 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA25211;
 Wed, 28 Feb 2001 14:14:41 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SMD6j01965
 for mobile-ip-dist; Wed, 28 Feb 2001 14:13:06 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SMCvE01955
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA00357
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
From: Phil_Neumiller@3Com.com
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA23795
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:12:56 -0700 (MST)
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
 by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SMBSo14321;
 Wed, 28 Feb 2001 14:11:28 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
 by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f1SMCnX06019;
 Wed, 28 Feb 2001 14:12:49 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A01.007A28B7 ; Wed, 28 Feb 2001 14:14:18 -0800
X-Lotus-FromDomain: 3COM
To: mobile-ip@sunroof.eng.sun.com
cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Message-ID: <88256A01.007A25AA.00@hqoutbound.ops.3com.com>
Date: Wed, 28 Feb 2001 16:11:37 -0600
Subject: RE: [seamoby] Arch discussions in IETF
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk





Hi Raj,

>Phil,
>
>I do not see anyone saying that Mobile IP is the only solution for all
>scenarios that require mobility. I am sure there are many scenarios
>that Mobile IP may or may not be the most optimal solution. If Mobile
>IP is unable to work as well as anything else you may have in mind
>for specific scenarios, then why deploy Mobile IP in such scenarios?

Then where might these other solutions be standardized in the IETF?
Would this fall under the classification of micro-mobility even though
the "so-called" COA or routing prefix does indeed change?  I guess what
I am getting at is there may be cases of infra-structure-less mobility
where the COA changes but there is no HA.  Would this be micro or
macro mobility?

>Can you be more specific on the kind of environments and requirements
>that these environments have that would make it impossible for Mobile
>IP to work in.

Sure.  Specifically, I am very interested in portable devices that will
find there way into homes.  Wireless appliances, MP3 players, digital
radios, digital security devices, gaming units, VoIP devices, etc.  I
am also interested in these types of devices that may be used in small
to medium business that may not have large infrastructures in place.

Thank you,

Phil Neumiller



From owner-seamoby@diameter.org  Fri Mar  2 05:03:08 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24725
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:03:07 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229ZeO03047
	for seamoby-list; Fri, 2 Mar 2001 01:35:40 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229Zbt03042
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:35:37 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:08 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:02 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:07:49 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SLiu316967
	for seamoby-list; Wed, 28 Feb 2001 13:44:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SLiro16962
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 13:44:53 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA24365;
	Wed, 28 Feb 2001 12:54:12 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA10467;
	Wed, 28 Feb 2001 12:54:11 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id MAA03331;
	Wed, 28 Feb 2001 12:54:09 -0800 (PST)
Date: Wed, 28 Feb 2001 12:49:43 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: RE: [seamoby] Yet Another BOF?
To: "Andrew T. Campbell" <campbell@comet.columbia.edu>
Cc: "'Pat Calhoun'" <pcalhoun@nasnfs.eng.sun.com>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "'James Kempf'" <james.kempf@sun.com>, Phil_Neumiller@3Com.com,
        seamoby@diameter.org
In-Reply-To: "Your message with ID" <006501c0a1e0$ef93f010$3d443b80@SWEETPEA>
Message-ID: <Roam.SIMC.2.0.6.983393383.20901.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> >  However, as I have stated 
> > numerous times,
> > statements like "MIP is too slow" just doesn't cut it.  
> 
> Lets try it this way then - please shoot me down.

ok

> 
> We clearly believe that micro-mobility means not invoking
> the MIP HAs each time we handoff? So all the action must be local.
> That excludes vanilla MIP as a solution and under those
> conditions its slow and lossy, etc. 
> 
> So what is this local protocol? I would claim that trees,
> levels of FAs and tunneling (the base MIP class) are 
> costly (tunnel/detunel overhead/complexity)
> and not robust (the tree of FAs, single gateways). 
> I'm not digging here; just some unsubstantiated 
> thoughts off the top of my head. 
> 
> The point that a number of people are making (and 
> developing solutions for, e.g., CIP, Hawaii, etc.) 
> is that if I'm forced to use FAs (trees and levels of them),
> tunneling and MIP signaling to solve every new
> wireless problem (e.g., QOS, fast handoff, etc.) 
> that surfaces in IETF, then, how do we innovate 
> and deliver new wireless IP technologies?  

Ahhh..... technical arguments. Good. This is all good. This is what we need.
They are alot harder to defend than the "MIP is too slow" argument.

> Is this because people think that the investment in MIP
> is so great that must reap dividend at no end? sister of
> MIP, cousin of MIP, etc.

Sure, and I do understand where they stand, but our charter is not to save
engineering work. It is to build what we need.

> Coupling each development to the base MIP mechanisms
> (FAs, tunneling, MIP signaling) as a perquisite to
> the development of new wireless IP protocols is a
> little like driving a car with a straight-jacket on.
> 
> Building fast/seamless handoff, paging, context, 
> QOS, etc. etc., on MIP is where we are heading today;
> consensus or not; it looks to me its all engineered
> that way? 

well, I haven't seen paging, context nor QoS being built on top of MIP, but
perhaps I've missed something. Of course, I've seen individual contributions
that propose this, but this is hardly a WG's work item.

> 
> The goals should to let MIP be the macro-mobilty 
> protocol to interwork with and allow 
> new and innovative technologies with 
> (for fast handoff, seamless, fast security, 
> QOS, context, etc. etc.) to be created.

Sounds reasonable to me.

PatC


From owner-seamoby@diameter.org  Fri Mar  2 05:03:36 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24736
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:03:35 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222S6323135
	for seamoby-list; Thu, 1 Mar 2001 18:28:06 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222S2o23130
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:28:02 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:23:49 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 03:40:05 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21J26021331
	for seamoby-list; Thu, 1 Mar 2001 11:02:06 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21J23o21326
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 11:02:03 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id DAA155140;
	Fri, 2 Mar 2001 03:02:56 +0900
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
 by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA10965;
 Thu, 1 Mar 2001 10:10:30 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA09819;
 Thu, 1 Mar 2001 10:10:22 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f21I8f716960
 for mobile-ip-dist; Thu, 1 Mar 2001 10:08:41 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f21I8UV16953
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 10:08:31 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA23948
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 10:08:30 -0800 (PST)
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA10766
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 11:08:28 -0700 (MST)
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
 by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id CAA72324;
 Fri, 2 Mar 2001 02:59:44 +0900
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA03112;
 Thu, 1 Mar 2001 10:06:38 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA07381;
 Thu, 1 Mar 2001 10:05:06 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f21I3K816801
 for mobile-ip-dist; Thu, 1 Mar 2001 10:03:20 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f21I3AV16794
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 10:03:11 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA07495
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 10:03:10 -0800 (PST)
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA07392
 for <mobile-ip@sunroof.eng.sun.com>; Thu, 1 Mar 2001 11:03:09 -0700 (MST)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
 by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id KAA14049;
 Thu, 1 Mar 2001 10:03:01 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
 by mira-sjc5-7.cisco.com (Mirapoint)
 with ESMTP id ABV01622;
 Thu, 1 Mar 2001 10:02:55 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA28818; Thu, 1 Mar 2001 10:02:55 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Message-ID: <15006.36559.662301.41126@thomasm-u1.cisco.com>
Date: Thu, 1 Mar 2001 10:02:55 -0800 (PST)
To: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
Cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Subject: Re: [seamoby] Arch discussions in IETF
In-Reply-To: <3A9E8895.DD789091@usa.alcatel.com>
References: <7B5C0390ACE7D211BC9C0008C7EABA2B0321356A@daeis07nok>
 <3A9E8895.DD789091@usa.alcatel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

I don't think this quite captures the finesse on
the issue. I don't believe that the proper framing
of the question is whether a new routing protocol
needs to be invented or not: it may very well be
that there is nothing to be done on the _routing
protocol_ front to support injecting host routes
if that's the ultimate solution. There may be work
needed to support _signaling_ a router that it
needs to change how a subnet is reachable.

I know this is hair splitting, but I think it's
important to separate out that it's quite possible
that the heavy lifting can already be done by
current protocols, and that all we need is the
ability to trigger them to happen. You might call
that a "routing protocol" too, but it ought not
evoke the fear and loathing that postulating a
Routing Protocol should.

   MIke


Behcet Sarikaya writes:
 > Hi Raj and Phil,
 > 
 >   I think the critical question for micromobility (mm) branch of the
 > Seamoby WG is
 > to be or not to be, i.e.
 > whether another routing protocol for mobility is required. Presently we
 > have the MIP and
 > the Manet routing approaches.
 >   The alternative seems to be per-host routes or host-based routing. I do
 > not think there
 > has been another breakthrough proposal significantly different. We all know
 > Cellular IP and
 > Hawaii proposals. Recently there is probably another one based on extending
 > OSPF with
 > host-based routes.
 >   Of course there are a lot of details but I think this is the crux of
 > Seamoby mm problem.
 > 
 > --
 > Behcet
 > 



From owner-seamoby@diameter.org  Fri Mar  2 05:08:23 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24772
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:08:21 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229bmt03122
	for seamoby-list; Fri, 2 Mar 2001 01:37:48 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229bgt03117
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:37:42 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:19 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:09 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 08:07:36 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SN8xP17307
	for seamoby-list; Wed, 28 Feb 2001 15:08:59 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SN8to17302
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 15:08:56 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id HAA91342;
	Thu, 1 Mar 2001 07:09:49 +0900
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA01965;
 Wed, 28 Feb 2001 14:18:17 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA27344;
 Wed, 28 Feb 2001 14:18:06 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SMFiI02040
 for mobile-ip-dist; Wed, 28 Feb 2001 14:15:44 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SMFKE02010
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:15:21 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA25412
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:15:20 -0800 (PST)
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
 by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA11504
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:15:17 -0800 (PST)
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
 by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id HAA63294;
 Thu, 1 Mar 2001 07:06:26 +0900
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA00335;
 Wed, 28 Feb 2001 14:14:52 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA25211;
 Wed, 28 Feb 2001 14:14:41 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SMD6j01965
 for mobile-ip-dist; Wed, 28 Feb 2001 14:13:06 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SMCvE01955
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA00357
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
From: Phil_Neumiller@3Com.com
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA23795
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:12:56 -0700 (MST)
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
 by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SMBSo14321;
 Wed, 28 Feb 2001 14:11:28 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
 by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f1SMCnX06019;
 Wed, 28 Feb 2001 14:12:49 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A01.007A28B7 ; Wed, 28 Feb 2001 14:14:18 -0800
X-Lotus-FromDomain: 3COM
To: mobile-ip@sunroof.eng.sun.com
cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Message-ID: <88256A01.007A25AA.00@hqoutbound.ops.3com.com>
Date: Wed, 28 Feb 2001 16:11:37 -0600
Subject: RE: [seamoby] Arch discussions in IETF
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk




Hi Raj,

>Phil,
>
>I do not see anyone saying that Mobile IP is the only solution for all
>scenarios that require mobility. I am sure there are many scenarios
>that Mobile IP may or may not be the most optimal solution. If Mobile
>IP is unable to work as well as anything else you may have in mind
>for specific scenarios, then why deploy Mobile IP in such scenarios?

Then where might these other solutions be standardized in the IETF?
Would this fall under the classification of micro-mobility even though
the "so-called" COA or routing prefix does indeed change?  I guess what
I am getting at is there may be cases of infra-structure-less mobility
where the COA changes but there is no HA.  Would this be micro or
macro mobility?

>Can you be more specific on the kind of environments and requirements
>that these environments have that would make it impossible for Mobile
>IP to work in.

Sure.  Specifically, I am very interested in portable devices that will
find there way into homes.  Wireless appliances, MP3 players, digital
radios, digital security devices, gaming units, VoIP devices, etc.  I
am also interested in these types of devices that may be used in small
to medium business that may not have large infrastructures in place.

Thank you,

Phil Neumiller




From owner-seamoby@diameter.org  Fri Mar  2 05:08:24 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24773
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:08:21 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229cNH03158
	for seamoby-list; Fri, 2 Mar 2001 01:38:23 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229cGt03144
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:38:17 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:19 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:04 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 06:16:07 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SLLQv16900
	for seamoby-list; Wed, 28 Feb 2001 13:21:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SLLNo16895
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 13:21:23 -0800
Received: from zrchb200.us.nortel.com (actually zrchb200) 
          by smtprch1.nortel.com; Wed, 28 Feb 2001 14:15:58 -0600
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZ1P18XB>; Wed, 28 Feb 2001 14:15:43 -0600
Message-ID: <85AA7486A2C1D411BCA20000F8073E4351C709@crchy271.us.nortel.com>
From: "Glenn Morrow" <gmorrow@nortelnetworks.com>
To: "'Hesham Soliman (ERA)'" <Hesham.Soliman@era.ericsson.se>,
        "'Michael Thomas'" <mat@cisco.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] I-D ACTION:draft-ietf-seamoby-mm-problem-00.txt
Date: Wed, 28 Feb 2001 14:15:35 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A1C3.35401260"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A1C3.35401260
Content-Type: text/plain;
	charset="iso-8859-1"

I don't mean to jump but IMHO here are some things to realize about MIP in
relation to these NAT statements:

Route Optimized MIP is essentially per-host routing with some signaling (BU)
and a double NAT function built into the end-nodes (hosts if you prefer).

Functionally you could decompose a MIP MN or a CN into the NAT, per-host
routing (binding cache) functions and the "pure" host (applications) which
uses the home addresses.

You could also think of the HA as a part of this double NAT as well; albeit,
it is using a tunnel to statelessly signal the address translation.

The reason I am trying to bring this up to people is to make them realize
the following:

- It is per-host routing.
- It is double NAT (address translation at both ends)

Because it is per-host routing the route tables of the hosts may indeed grow
large. For example, one of the hosts may be a website which millions of
mobile hosts communicate simultaneously. Imagine a media or even just an
HTTP server with a million per-host route entries. 

Are there server companies and chip manufacturers working on hardware
assisted look-up engines and code to do these lookups to meet the delay
requirements?

Another approach we might take it to move the double NAT and fast (per-host
routing) lookup functions to the (purpose built) subnet routers where they
might have a chance of scaling. 

This might also serve to provide simultaneous route optimization with
location privacy and allow the existing SA's between routers to be leveraged
in order to avoid the necessity of setting up SA's every time a mobile node
wishes to communicate with another node on the network.

I am also fairly convinced that there are solutions which do not compromise
the connectionless (redundant) nature of IP, especially in the IPv6 case.

Indeed this would not be creating a new protocol to solve the node mobility
problem - it would be changing IP, itself, to solve the node mobility
problem - essentially making a new "pure" IP.

O.K. fire away  - at least we might get off the "what is a router" debate.

Glenn




> -----Original Message-----
> From:	Hesham Soliman (ERA) [SMTP:Hesham.Soliman@era.ericsson.se]
> Sent:	Tuesday, February 27, 2001 11:25 AM
> To:	seamoby@cdma-2000.org
> Subject:	RE: [seamoby] I-D
> ACTION:draft-ietf-seamoby-mm-problem-00.txt
> 
> 
> > >	means choosing the shortest path between two nodes
> > >	on the Internet. 
> > 
> > Can you define node ?
> > 
> 	=> Host ? Terminal ? 
> 
> > >	I hope you don't mean that having a router in the 
> > >	middle that encapsulates a packet and forwards it
> > >	to the right address is breaking the Internet 
> > >	model. That _is_routing.
> > 
> > But that is not what a Home Agent does.  No user application like
> > email or web browsing on the internet addresses a router.  The cNode
> > and MN in Mobile IP actually address the Home Agent which has no
> > user application executing on it.
> > 
> 	=> No it doesn't address the HA, this not true at all. The
> application
> 	addresses the Home address of the MN. The HA receives the 
> 	packet because of its ND/ARP advertisements. I'm sure you 
> 	know that already. So I don't know why you say that.
> 
> 
> > tunnels the packet.  The inner portion of an IP tunnel is the
> application
> > layer of the outer header.  So the Home Agent is in effect an
> application
> > layer switch in the middle of the network which is not too different
> than a NAT.
> > 
> 	=> That is a gross misinterpretation of a HA. How could it possibly
> be a NAT ?
> 	Do I need to list all the protocols that do not work through a NAT ?
> 	A HA does not operate above L3. This is the whole point behind MIP.
> 
> > >
> > >> An
> > >> anchor point anywhere in the network is neither client nor
> > >> server nor peer and therefore 
> > >> 
> > >	=> It's a router ! They are usually in the middle
> > >	and they're not clients or servers.
> > 
> > See my point above.  The Home Agent is not a router.  
> > 
> 	=> Of course it's a router, define a router ? 
> 	your claims above abou it being a NAT are wrong.
> 	The first few pages in the MIP spec tell you 
> 	that it's a router don't they ?
> 
> > Non-mobile
> > clients, servers, and peers do not address routers.  IOW, the IP
> > destination address of a packet originiating from a fixed client,
> server, or
> > peer on the internet is not the address of a router.  
> > 
> 	=> I think you need to reread MIP. The CN does not 
> 	address the HA.
> 
> > >	=> I agree, but there are ways of making it redundant
> > >	like any other router.
> > 
> > The only way is stateful transfer which requires some state other
> > than IP routing to be transfered.  It's expensive an wasteful.
> > What about networks that want to be multihomed ?
> > 
> 	=> I was talking about a transfer of the binding cache.
> 	Multihoming is not an issues here is it ?
> 
> 	Regards,
> 	Hesham

------_=_NextPart_001_01C0A1C3.35401260
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: [seamoby] I-D =
ACTION:draft-ietf-seamoby-mm-problem-00.txt</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I don't mean to jump =
but IMHO here are some things to realize about MIP in relation to these =
NAT statements:</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Route Optimized MIP =
is essentially per-host routing with some signaling (BU) and a double =
NAT function built into the end-nodes (hosts if you prefer).</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Functionally you =
could decompose a MIP MN or a CN into the NAT, per-host routing =
(binding cache) functions and the &quot;pure&quot; host (applications) =
which uses the home addresses.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">You could also think =
of the HA as a part of this double NAT as well; albeit, it is using a =
tunnel to statelessly signal the address translation.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">The reason I am =
trying to bring this up to people is to make them realize the =
following:</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">- It is per-host =
routing.</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">- It is double NAT =
(address translation at both ends)</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Because it is =
per-host routing the route tables of the hosts may indeed grow large. =
For example, one of the hosts may be a website which millions of mobile =
hosts communicate simultaneously. Imagine a media or even just an HTTP =
server with a million per-host route entries. </FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Are there server =
companies and chip manufacturers working on hardware assisted look-up =
engines and code to do these lookups to meet the delay =
requirements?</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Another approach we =
might take it to move the double NAT and fast (per-host routing) lookup =
functions to the (purpose built) subnet routers where they might have a =
chance of scaling. </FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">This might also =
serve to provide simultaneous route optimization with location privacy =
and allow the existing SA's between routers to be leveraged in order to =
avoid the necessity of setting up SA's every time a mobile node wishes =
to communicate with another node on the network.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I am also fairly =
convinced that there are solutions which do not compromise the =
connectionless (redundant) nature of IP, especially in the IPv6 =
case.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Indeed this would =
not be creating a new protocol to solve the node mobility problem - it =
would be changing IP, itself, to solve the node mobility problem - =
essentially making a new &quot;pure&quot; IP.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">O.K. fire away&nbsp; =
- at least we might get off the &quot;what is a router&quot; =
debate.</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Glenn</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D1 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">From:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Hesham Soliman (ERA) =
[SMTP:Hesham.Soliman@era.ericsson.se]</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Tuesday, February 27, 2001 11:25 AM</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">seamoby@cdma-2000.org</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Arial">RE: [seamoby] I-D =
ACTION:draft-ietf-seamoby-mm-problem-00.txt</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; =
means choosing the shortest path between two nodes</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; on =
the Internet. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Can you define node ?</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">=3D&gt; Host ? Terminal ? </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; I =
hope you don't mean that having a router in the </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; =
middle that encapsulates a packet and forwards it</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; to =
the right address is breaking the Internet </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; =
model. That _is_routing.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; But that is not what a Home =
Agent does.&nbsp; No user application like</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; email or web browsing on the =
internet addresses a router.&nbsp; The cNode</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; and MN in Mobile IP actually =
address the Home Agent which has no</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; user application executing on =
it.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">=3D&gt; No it doesn't address the HA, this not true at =
all. The application</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">addresses the Home address of the MN. The HA receives =
the </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">packet because of its ND/ARP advertisements. I'm sure =
you </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">know that already. So I don't know why you say =
that.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; tunnels the packet.&nbsp; The =
inner portion of an IP tunnel is the application</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; layer of the outer header.&nbsp; =
So the Home Agent is in effect an application</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; layer switch in the middle of =
the network which is not too different than a NAT.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">=3D&gt; That is a gross misinterpretation of a HA. How =
could it possibly be a NAT ?</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Do I need to list all the protocols that do not work =
through a NAT ?</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">A HA does not operate above L3. This is the whole point =
behind MIP.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&gt; An</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&gt; anchor point anywhere =
in the network is neither client nor</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&gt; server nor peer and =
therefore </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; =
=3D&gt; It's a router ! They are usually in the middle</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; and =
they're not clients or servers.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; See my point above.&nbsp; The =
Home Agent is not a router.&nbsp; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">=3D&gt; Of course it's a router, define a router ? =
</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">your claims above abou it being a NAT are wrong.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">The first few pages in the MIP spec tell you </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">that it's a router don't they ?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; Non-mobile</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; clients, servers, and peers do =
not address routers.&nbsp; IOW, the IP</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; destination address of a packet =
originiating from a fixed client, server, or</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; peer on the internet is not the =
address of a router.&nbsp; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">=3D&gt; I think you need to reread MIP. The CN does not =
</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">address the HA.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; =
=3D&gt; I agree, but there are ways of making it redundant</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; =
like any other router.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; The only way is stateful =
transfer which requires some state other</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; than IP routing to be =
transfered.&nbsp; It's expensive an wasteful.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; What about networks that want to =
be multihomed ?</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">=3D&gt; I was talking about a transfer of the binding =
cache.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Multihoming is not an issues here is it ?</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Hesham</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A1C3.35401260--


From owner-seamoby@diameter.org  Fri Mar  2 05:09:51 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24794
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:09:50 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229XwJ02920
	for seamoby-list; Fri, 2 Mar 2001 01:33:58 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229Xrt02913
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:33:53 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:15 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:07 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:16:32 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SLpQw16994
	for seamoby-list; Wed, 28 Feb 2001 13:51:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SLnZo16975
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 13:49:36 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id FAA138862;
	Thu, 1 Mar 2001 05:50:15 +0900
Received: from smtprch2.nortel.com (erchg0k.us.nortel.com [47.113.64.104])
 by zrtps06u.us.nortel.com (8.11.0/8.11.0) with ESMTP id f1SKvsl13168
 for <paullee@korea.ac.kr>; Wed, 28 Feb 2001 15:57:54 -0500 (EST)
Received: from zrchh190 by smtprch2.nortel.com; Wed, 28 Feb 2001 13:53:16 -0600
Received: from marvin.corpeast.baynetworks.com by zrchh190;
          Wed, 28 Feb 2001 13:49:23 -0600
Received: from qcarh006.nortelnetworks.com (zcars00w.ca.nortel.com [47.128.0.50]) 
          by marvin.corpeast.baynetworks.com (8.8.8+Sun/8.8.8) with ESMTP 
          id OAA20083 for <mobile-ip@marvin.baynetworks.com>;
          Wed, 28 Feb 2001 14:42:30 -0500 (EST)
Received: from ecarsaaa.nortelnetworks.com by qcarh006.nortelnetworks.com;
          Wed, 28 Feb 2001 14:40:12 -0500
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116]) 
          by ecarsaaa.nortelnetworks.com with SMTP (MailShield v1.5);
          Wed, 28 Feb 2001 14:42:18 -0500
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61]) 
          by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) 
          with SMTP id f1SJgGC01873 
          for <mobile-ip@standards.nortelnetworks.com>;
          Wed, 28 Feb 2001 20:42:17 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ;
          Wed Feb 28 20:42:17 2001 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2651.58) id <F1J9B31L>;
          Wed, 28 Feb 2001 20:42:15 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBAB@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'James Kempf'" <james.kempf@sun.com>,
        mobile-ip@marvin.corpeast.baynetworks.com
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
Date: Wed, 28 Feb 2001 20:42:15 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
X-SMTP-HELO: albatross-ext.wise.edt.ericsson.se
X-SMTP-MAIL-FROM: Hesham.Soliman@era.ericsson.se
X-SMTP-RCPT-TO: mobile-ip@standards.nortelnetworks.com
X-SMTP-PEER-INFO: albatross-ext.wise.edt.ericsson.se [194.237.142.116]
X-Orig: <ronyoung@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk


> (Hoping this gets through the MIP mailing list problems...)
> 
 => It didn't. I think this is definitely a MIP issue so we should 
 discuss it on the MIP list. You need to send your mail to
 mobile-ip@standards.nortelnetworks.com

> In draft-thomas-seamoby-rsvp-analysis-00.txt, some serious problems with MIP
> and RSVP signalling are identified. 
> 
 => Sure RSVP doesn't handle IP mobility.

> Specifically, when a handoff occurs,
> a round-trip BU must occur before the CN can issue an RSVP PATH message
> to assure QoS over the new route. Aggregated RSVP (see 
> draft-ietf-rsvp-aggr-02.txt)
> doesn't help, because the BU must still propogate to the CN for the CN to issue
> the PATH. All aggregation does is reduce the state in routers internal to the
> aggregation region, it does not reduce signalling requirements over 
> standard RSVP.
> 
 => Yes.

> There is a case where signalling can be optimized that is identified in
> draft-thomas-seamoby-rsvp-analysis-00.txt. This is the case where the movement
> of the mobile does not involve a change in CoA but rather is handled by 
> installing
> a new host route up to the join router between the old and new path. 
> Establishment
> of the new route is followed by a PATH message from the new join router
> to the MN, and a RESV from the MN back to the join router (pg. 10 in the 
> draft).
> 
> In draft-malinen-mobileip-regreg6-00.txt, a hierarchical MIP mechanism (called
> regional registrations) is defined that works very much like a host route. 
> Routers
> 
 => No it doesn't. The MN's CoA changes when the MN moves.

> between the new access router and the join router (called a crossover router
> in the draft) examine a BU routing option and the join router reconfigures its
> binding table to take account of the new route. The routers here are defined
> to be special regional aware routers, but the principle is the same.
> 
> Note that in HMIPv6 (draft-ietf-mobileip-hmipv6-01.txt), since the 
> intervening routers between the MAP and the mobile node never see the 
> topology change, the same severe performance penalties w.r.t. RSVP 
> signalling as in the standard
> MIPv6 case should occur.
> 
 => If you believe a crossover router solves the problem
 then you can see the MAP as the same thing. But the fact
 is neither a cross over router (in draft-malinen-...) nor HMIPv6
 solves that problem. A new PATH needs to be setup anyway
 for the outgoing traffic. The path between the MAP and the 
 CN is unchanged for incoming traffic.

> So, I'm wondering if the regional registration BU routing option could 
> serve as a trigger for redoing the RSVP signalling for QoS? Comments?
> 
 => I think the problem is much bigger than that. The issue of mobility 
 and QoS needs to be addressed in more detail. Michael's draft (I haven't
 finished it yet) is a very good start. We can't solve it for HMIP only, 
 the problem needs to be addressed for MIP in general.

 Regards,
 Hesham 




From owner-seamoby@diameter.org  Fri Mar  2 05:10:41 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24813
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:10:40 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229Z4P03022
	for seamoby-list; Fri, 2 Mar 2001 01:35:04 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229Ymt02990
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:34:49 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:19:34 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:58:35 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 08:51:29 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21NoZt22434
	for seamoby-list; Thu, 1 Mar 2001 15:50:35 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21NoWo22429
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 15:50:32 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id HAA142334;
	Fri, 2 Mar 2001 07:50:06 +0900
Received: from zrchh190 by smtprch2.nortel.com; Thu, 1 Mar 2001 15:37:22 -0600
Received: from marvin.corpeast.baynetworks.com by zrchh190;
          Thu, 1 Mar 2001 15:40:20 -0600
Received: from zrchb200.us.nortel.com (zrchb200.us.nortel.com [47.100.129.29]) 
          by marvin.corpeast.baynetworks.com (8.8.8+Sun/8.8.8) with ESMTP 
          id QAA06248 for <mobile-ip@marvin.corpeast.baynetworks.com>;
          Thu, 1 Mar 2001 16:30:22 -0500 (EST)
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZ1PF0WZ>; Thu, 1 Mar 2001 15:30:00 -0600
Message-ID: <85AA7486A2C1D411BCA20000F8073E4351C70F@crchy271.us.nortel.com>
From: "Glenn Morrow" <gmorrow@nortelnetworks.com>
To: "'Michael Thomas'" <mat@cisco.com>, Hemant Chaskar <hchaskar@hotmail.com>
Cc: Hesham.Soliman@era.ericsson.se, james.kempf@sun.com,
        mobile-ip@marvin.corpeast.baynetworks.com, seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
Date: Thu, 1 Mar 2001 15:29:53 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A296.C11978C0"
X-Orig: <ronyoung@nortelnetworks.com>
X-Orig: <ronyoung@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A296.C11978C0
Content-Type: text/plain

Sounds like a no-brainer to me. The handoff signaling was the question and
it looks like an ICMP solution has emerged? 

Where do you propose to put the objects there or have you not resigned
yourselves to accept the ICMP solution (i.e. do you still want to try to
push RSVP)?

I really care more about the function than the WG or the protocol choosen -
pick one.

One advantage (tenous as it may be) of putting the QoS objects in IP itself
is that it pretty much stops the argument about which protocol or WG to use
for what, when more than one function is needed. 

Extremely counter to this is the investment each party has made in existing
signaling solutions. 

With a start from scratch mentality I would put in an IP header as I feel
that it is a network layer function.


Regards,

Glenn

> -----Original Message-----
> From: Michael Thomas [SMTP:mat@cisco.com]
> Sent: Thursday, March 01, 2001 12:33 PM
> To: Hemant Chaskar
> Cc: Hesham.Soliman@era.ericsson.se; james.kempf@sun.com;
> mobile-ip@marvin.corpeast.baynetworks.com; seamoby@diameter.org
> Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
> 
> 
> I don't see how this fundamentally changes
> anything that James brought up. It still has to go
> end to end, and it's still touching every router
> in between MN and CN. 
> 
> What I do see is a lot of reinvention of RSVP
> Rspec and Tspec's for no known reason.  The only
> thing I can see of possible value is the ability
> to piggyback the QoS update with the BU, but even
> if this is the sole goal -- and that it's a worthy
> goal which is not at all apparent to me -- I
> imagine that there are better ways of doing this
> with out reinventing RSVP: like, maybe,
> piggybacking the BU on the PATH, or some such.
> 
>       Mike
> 
> 
> Hemant Chaskar writes:
>  > Regarding the issue of round-trip latency in programming QoS forwarding
> 
>  > treatment along new path after change in CoA:
>  > 
>  > This is intrinsic drawback of OPWA model of resource reservation of
> RSVP. In 
>  > the worst case, one round-trip time will include traversals of four
> wireless 
>  > links. This happens when both CN and MN are mobile.
>  > 
>  > Note that this drawback is eliminated in the approach to QoS signaling
> based 
>  > on including QoS Object in hop-by-hop options extension header along
> with 
>  > binding messages (draft-chaskar-mobileip-qos-00.txt). This draft was 
>  > presented in SD and revised version (01) will be submitted soon.
>  > 
>  > Hemant
>  > _________________________________________________________________
>  > Get your FREE download of MSN Explorer at http://explorer.msn.com
>  > 

------_=_NextPart_001_01C0A296.C11978C0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: [seamoby] Hierarchical MIP, QoS, and Handoff</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Sounds like a =
no-brainer to me. The handoff signaling was the question and it looks =
like an ICMP solution has emerged? </FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Where do you propose =
to put the objects there or have you not resigned yourselves to accept =
the ICMP solution (i.e. do you still want to try to push =
RSVP)?</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I really care more =
about the function than the WG or the protocol choosen - pick =
one.</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">One advantage =
(tenous as it may be) of putting the QoS objects in IP itself is that =
it pretty much stops the argument about which protocol or WG to use for =
what, when more than one function is needed. </FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Extremely counter to =
this is the investment each party has made in existing signaling =
solutions. </FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">With a start from =
scratch mentality I would put in an IP header as I feel that it is a =
network layer function.</FONT>
</P>
<BR>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Regards,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Glenn</FONT>
</P>

<P><FONT SIZE=3D1 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">From:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Michael Thomas [SMTP:mat@cisco.com]</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Thursday, March 01, 2001 12:33 PM</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">Hemant Chaskar</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">Hesham.Soliman@era.ericsson.se; james.kempf@sun.com; =
mobile-ip@marvin.corpeast.baynetworks.com; =
seamoby@diameter.org</FONT></P>

<P><B><FONT SIZE=3D1 =
FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Arial">RE: [seamoby] Hierarchical MIP, QoS, =
and Handoff</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">I don't see how this fundamentally =
changes</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">anything that James brought up. It =
still has to go</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">end to end, and it's still touching =
every router</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">in between MN and CN. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">What I do see is a lot of reinvention =
of RSVP</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Rspec and Tspec's for no known =
reason.&nbsp; The only</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">thing I can see of possible value is =
the ability</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">to piggyback the QoS update with the =
BU, but even</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">if this is the sole goal -- and that =
it's a worthy</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">goal which is not at all apparent to =
me -- I</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">imagine that there are better ways of =
doing this</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">with out reinventing RSVP: like, =
maybe,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">piggybacking the BU on the PATH, or =
some such.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp; Mike</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hemant Chaskar writes:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Regarding the issue of =
round-trip latency in programming QoS forwarding </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; treatment along new path =
after change in CoA:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; This is intrinsic drawback =
of OPWA model of resource reservation of RSVP. In </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; the worst case, one =
round-trip time will include traversals of four wireless </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; links. This happens when =
both CN and MN are mobile.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Note that this drawback is =
eliminated in the approach to QoS signaling based </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; on including QoS Object in =
hop-by-hop options extension header along with </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; binding messages =
(draft-chaskar-mobileip-qos-00.txt). This draft was </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; presented in SD and =
revised version (01) will be submitted soon.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Hemant</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; =
_________________________________________________________________</FONT>=

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Get your FREE download of =
MSN Explorer at <A HREF=3D"http://explorer.msn.com" =
TARGET=3D"_blank">http://explorer.msn.com</A></FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A296.C11978C0--


From owner-seamoby@diameter.org  Fri Mar  2 05:15:46 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24870
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:15:46 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229bMF03109
	for seamoby-list; Fri, 2 Mar 2001 01:37:22 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229bDt03103
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:37:14 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:38 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:41 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 13:04:03 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f213qLM18416
	for seamoby-list; Wed, 28 Feb 2001 19:52:21 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f213qJo18411
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 19:52:19 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <FZGPC54A>; Wed, 28 Feb 2001 22:01:53 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D29DC@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <KAtwal@zucotto.com>
To: seamoby@diameter.org
Subject: RE: [seamoby] Yet Another BOF?
Date: Wed, 28 Feb 2001 22:01:52 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

3.2 MANET / Ad-Hoc Networking Comparison

   The MANET WG in the IETF has an important charter to create a
   protocol for mobiles arranged in arbitrary and highly dynamic
   associations.  This work is striving for robust and highly scalable
   routing solutions.  Currently, MANET is not considering fast or
   seamless handover.

   In many instances, for example small residential networks found in
   the home, the network may be relatively small and has far less
   dynamics.  The network may still have a requirement for fast and/or
   seamless handovers. For this reason there may be some overlap
   between SeaMoby and ad-hoc networking solutions.  Therefore, SeaMoby
   MUST be able to co-exist gracefully with any MANET solutions
   algorithm that does become standardized.

> -----Original Message-----
> From: Phil_Neumiller@3com.com [mailto:Phil_Neumiller@3com.com]
> Sent: Tuesday, February 27, 2001 6:51 PM
> To: seamoby@diameter.org
> Subject: [seamoby] Yet Another BOF?
> 
> 
> 
> 
> 
> After a brief history with mobility BOFs,  I am convinced 
> that they are of
> limited use.  Perhaps an
> informational RFC is a better approach (not my idea).  I am 
> convinced that many
> of us (perhaps
> Gary, (Andrew, James, John, Peter, and the other OBAST 
> disciples:-))) that
> wanted to build true
> all IP based, edge oriented, routers with wireless cards, 
> with a standardized
> backhaul, some
> how got muscled out of the IETF by the powerful forces of the 
> MIP and MANET
> groups.  

In the Micro-mobility draft the following section appears:

3.2 MANET / Ad-Hoc Networking Comparison

   The MANET WG in the IETF has an important charter to create a
   protocol for mobiles arranged in arbitrary and highly dynamic
   associations.  This work is striving for robust and highly scalable
   routing solutions.  Currently, MANET is not considering fast or
   seamless handover.

   In many instances, for example small residential networks found in
   the home, the network may be relatively small and has far less
   dynamics.  The network may still have a requirement for fast and/or
   seamless handovers. For this reason there may be some overlap
   between SeaMoby and ad-hoc networking solutions.  Therefore, SeaMoby
   MUST be able to co-exist gracefully with any MANET solutions
   algorithm that does become standardized.

Comments:

Why 'MUST' SeaMoby be confined by MANET/MIP?  
If SeaMoby does its job there will be no need for MANET in local mobility.
If SeaMoby does its job there will be no need for MIP in local mobility.

Are we forgetting that devices in the home are low cost?
Why would any vendor support MIP, MANET and Seamoby to do one thing: moving?
Why would any Bluetooth vendor support three protocols when the same vendor 
can go to the Bluetooth SIG and use the work of a SIG WG to get one
protocol?

The title of the section says ,"Comparion", but states a mandatory
requirement.
By making MANET a 'MUST' requirement for Seamoby is a sure way to see that
Seamoby is 
never deployed.

I would like someone the justify the opening statement in section 3.2:

   The MANET WG in the IETF has an important charter to create a
   protocol for mobiles arranged in arbitrary and highly dynamic
   associations.

Is the MANET charter more important than the SeaMoby Charter?

What is an "arbitary association" and how does it differ from mobility?

What is the timescale for "highly dynamic associations"?

- Kulwinder.


From owner-seamoby@diameter.org  Fri Mar  2 05:20:17 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24886
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:20:15 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f222fA023282
	for seamoby-list; Thu, 1 Mar 2001 18:41:10 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f222f5o23276
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 18:41:05 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:29:37 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 03:15:00 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f21IA5a21142
	for seamoby-list; Thu, 1 Mar 2001 10:10:05 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zrtps06u.us.nortel.com (h52s48a140n47.user.nortelnetworks.com [47.140.48.52])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f21IA2o21135
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 10:10:02 -0800
Received: from smtprch2.nortel.com (erchg0k.us.nortel.com [47.113.64.104])
	by zrtps06u.us.nortel.com (8.11.0/8.11.0) with ESMTP id f21HIXl29398
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 12:18:33 -0500 (EST)
Received: from zrchb200.us.nortel.com (actually zrchb200) 
          by smtprch2.nortel.com; Thu, 1 Mar 2001 10:23:59 -0600
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZ1PFTHC>; Thu, 1 Mar 2001 10:26:48 -0600
Message-ID: <85AA7486A2C1D411BCA20000F8073E4351C70C@crchy271.us.nortel.com>
From: "Glenn Morrow" <gmorrow@nortelnetworks.com>
To: "'Hesham Soliman (ERA)'" <Hesham.Soliman@era.ericsson.se>
Cc: "'Michael Thomas'" <mat@cisco.com>, seamoby@diameter.org
Subject: RE: [seamoby] I-D ACTION:draft-ietf-seamoby-mm-problem-00.txt
Date: Thu, 1 Mar 2001 10:25:41 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A26C.420CD9C0"
X-Orig: <gmorrow@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A26C.420CD9C0
Content-Type: text/plain;
	charset="iso-8859-1"

Hesham,

See below:


> Hello Glenn, 
> 
> A router is a device that forwards packets from one interface to
> another. That makes a NAT a router and so is a HA. 
> A router CAN definitely tunnel, I hope you agree with that.
[[gm]]  Sounds like a reasonable definition to me; however, I do suspect
that some routers can't tunnel and can't do NAT. I think we should say "some
routers can" and be done with this banter which has occured since the
original MIPv6 handoff discussion. 

> A NAT is a device that hides addresses on one side of the 
> network from the other side and the end nodes. Typically 
> because they are not routable. 
[[gm]]  You have limited your definition of NAT. A NAT is a device or
process that translates a source and or desination address to another. It
matters not whether the addresses are globally routable or not. One could
say that one application of network address translation is to hide internal
addresses from the external network.

> A HA _does_not_hide addresses from anyone. 
[[gm]]  Really - does a correspondent node know the MN's COA unless route
optmization is used?

> The end nodes 
> and the entire Internet can route a MN's Home address.
[[gm]]  I am extremely please by this. I am also pleased that the entire
Internet does not know the MN's COA. I am not please with the fact that in
order to provide route optimization, the entire Internet must know the COA.
I would suggest a solution that exposes the COA information to only routers
and not hosts.
>  
> NATs typically break end to end security and many peer to
> peer protocols. A HA doesn't.
[[gm]]  
If you apply network address translation at both sides (as route optmized
MIP does) then you have no problem with peer to peer protocols. One way of
avoiding the necessity of changing of supposedly un-mutable fields is to use
encapsulation. Do you see that in optimized MIP, the MN could use a tunnel
to the CN to deliver a packet instead of address translation. The packet is
delivered either way (i.e. same functionality - different mechanism).

> I'm a bit surprised by your analogy and definitions but 
> I dont really think we should spend our lives looking 
> for a definition that makes a HA look like a NAT. 
> Surely there are better reasons for justifying
> the mm problem and better things to do.
[[gm]]  begin
Surely the following:

- a list of true requirements for node mobility (macro, micro)
- an analysis of data-hiding ramifications of these requirments
- an analysis of the scaling ramifications of these requirments

are essential to any problem and solution set.

You are quite correct that I was not focusing merely on the micro-solution.
I was also addressing end to end security associations, scaling, etc.. that
are some of the "excuses" for micromobility solutions - not that I am
opposed to some solutions. I believe we need both solutions that can support
real-time handover. 

If you note, the HA correlation with NAT is only one aspect about what is
discussed below. Making an HA equivalent to a limited definition of a NAT
was not my goal. I am a bit perplexed as to why your response focuses so
much on such a minor analogy and adapt an attitude that I somehow do not
understand the difference. 

If you look, I believe you might find some more pertinent suggestions in
terms of requirements, ramifications and possible ways forward. I and I hope
others would see much more value for you to focus on these.

Regards,

Glenn


[[gm]]  end

> Regards,
> Hesham
> 
> > -----Original Message-----
> > From:	Glenn Morrow [SMTP:gmorrow@nortelnetworks.com]
> > Sent:	Thursday, 1 March 2001 7:16
> > To:	'Hesham Soliman (ERA)'; 'Michael Thomas'
> > Cc:	seamoby@diameter.org
> > Subject:	RE: [seamoby] I-D
> ACTION:draft-ietf-seamoby-mm-problem-00.txt
> > 
> > I don't mean to jump but IMHO here are some things to realize about MIP
> in relation to these NAT statements: 
> > 
> > Route Optimized MIP is essentially per-host routing with some signaling
> (BU) and a double NAT function built into the end-nodes (hosts if you
> prefer).
> > 
> > Functionally you could decompose a MIP MN or a CN into the NAT, per-host
> routing (binding cache) functions and the "pure" host (applications) which
> uses the home addresses.
> > 
> > You could also think of the HA as a part of this double NAT as well;
> albeit, it is using a tunnel to statelessly signal the address
> translation.
> > 
> > The reason I am trying to bring this up to people is to make them
> realize the following: 
> > 
> > - It is per-host routing. 
> > - It is double NAT (address translation at both ends) 
> > 
> > Because it is per-host routing the route tables of the hosts may indeed
> grow large. For example, one of the hosts may be a website which millions
> of mobile hosts communicate simultaneously. Imagine a media or even just
> an HTTP server with a million per-host route entries. 
> > 
> > Are there server companies and chip manufacturers working on hardware
> assisted look-up engines and code to do these lookups to meet the delay
> requirements?
> > 
> > Another approach we might take it to move the double NAT and fast
> (per-host routing) lookup functions to the (purpose built) subnet routers
> where they might have a chance of scaling. 
> > 
> > This might also serve to provide simultaneous route optimization with
> location privacy and allow the existing SA's between routers to be
> leveraged in order to avoid the necessity of setting up SA's every time a
> mobile node wishes to communicate with another node on the network.
> > 
> > I am also fairly convinced that there are solutions which do not
> compromise the connectionless (redundant) nature of IP, especially in the
> IPv6 case.
> > 
> > Indeed this would not be creating a new protocol to solve the node
> mobility problem - it would be changing IP, itself, to solve the node
> mobility problem - essentially making a new "pure" IP.
> > 
> > O.K. fire away  - at least we might get off the "what is a router"
> debate. 
> > 
> > Glenn 
> > 
> > 
> > 
> > 

------_=_NextPart_001_01C0A26C.420CD9C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: [seamoby] I-D =
ACTION:draft-ietf-seamoby-mm-problem-00.txt</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Hesham,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">See below:</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hello Glenn, </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">A router is a device that forwards =
packets from one interface to</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">another. That makes a NAT a router =
and so is a HA. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">A router CAN definitely tunnel, I =
hope you agree with that.</FONT>
<BR><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> Sounds like a reasonable =
definition to me; however, I do suspect that some routers can't tunnel =
and can't do NAT. I think we should say &quot;some routers can&quot; =
and be done with this banter which has occured since the original MIPv6 =
handoff discussion.</FONT> </P>

<P><FONT SIZE=3D2 FACE=3D"Arial">A NAT is a device that hides addresses =
on one side of the </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">network from the other side and the =
end nodes. Typically </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">because they are not routable. =
</FONT>
<BR><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> You have limited your =
definition of NAT. A NAT is a device or process that translates a =
source and or desination address to another. It matters not whether the =
addresses are globally routable or not. One could say that one =
application of network address translation is to hide internal =
addresses from the external network.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">A HA _does_not_hide addresses from =
anyone. </FONT>
<BR><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> Really - does a =
correspondent node know the MN's COA unless route optmization is =
used?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The end nodes </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">and the entire Internet can route a =
MN's Home address.</FONT>
<BR><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> I am extremely please by =
this. I am also pleased that the entire</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Internet does not =
know the MN's COA. I am not please with the fact that in order to =
provide route optimization, the entire Internet must know the =
COA.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I would suggest a =
solution that exposes the COA information to only routers and not =
hosts.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">NATs typically break end to end =
security and many peer to</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">peer protocols. A HA doesn't.</FONT>
<BR><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> </FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">If you apply =
network address translation at both sides (as route optmized MIP does) =
then you have no problem with peer to peer protocols. One way of =
avoiding the necessity of changing of supposedly un-mutable fields is =
to use encapsulation. Do you see that in optimized MIP, the MN could =
use a tunnel to the CN to deliver a packet instead of address =
translation. The packet is delivered either way (i.e. same =
functionality - different mechanism).</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I'm a bit surprised by your analogy =
and definitions but </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">I dont really think we should spend =
our lives looking </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">for a definition that makes a HA look =
like a NAT. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Surely there are better reasons for =
justifying</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">the mm problem and better things to =
do.</FONT>
<BR><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> begin</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Surely the =
following:</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">- a list of true =
requirements for node mobility (macro, micro)</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">- an analysis of =
data-hiding ramifications of these requirments</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">- an analysis of =
the scaling ramifications of these requirments</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">are essential to any =
problem and solution set.</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">You are quite =
correct that I was not focusing merely on the micro-solution. I was =
also addressing end to end security associations, scaling, etc.. that =
are some of the &quot;excuses&quot; for micromobility solutions - not =
that I am opposed to some solutions. I believe we need both solutions =
that can support real-time handover. </FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">If you note, the HA =
correlation with NAT is only one aspect about what is discussed below. =
Making an HA equivalent to a limited definition of a NAT was not my =
goal. I am a bit perplexed as to why your response focuses so much on =
such a minor analogy and adapt an attitude that I somehow do not =
understand the difference. </FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">If you look, I =
believe you might find some more pertinent suggestions in terms of =
requirements, ramifications and possible ways forward. I and I hope =
others would see much more value for you to focus on these.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Regards,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Glenn</FONT>
</P>
<BR>

<P><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">[[gm]]</FONT></I></B><I></I>&nbsp;<FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> end</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Hesham</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; From: Glenn Morrow =
[SMTP:gmorrow@nortelnetworks.com]</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Sent: Thursday, 1 March 2001 =
7:16</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; To:&nbsp;&nbsp; 'Hesham Soliman =
(ERA)'; 'Michael Thomas'</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Cc:&nbsp;&nbsp; =
seamoby@diameter.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RE: [seamoby] I-D =
ACTION:draft-ietf-seamoby-mm-problem-00.txt</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; I don't mean to jump but IMHO =
here are some things to realize about MIP in relation to these NAT =
statements: </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Route Optimized MIP is =
essentially per-host routing with some signaling (BU) and a double NAT =
function built into the end-nodes (hosts if you prefer).</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Functionally you could decompose =
a MIP MN or a CN into the NAT, per-host routing (binding cache) =
functions and the &quot;pure&quot; host (applications) which uses the =
home addresses.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; You could also think of the HA =
as a part of this double NAT as well; albeit, it is using a tunnel to =
statelessly signal the address translation.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; The reason I am trying to bring =
this up to people is to make them realize the following: </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; - It is per-host routing. =
</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; - It is double NAT (address =
translation at both ends) </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Because it is per-host routing =
the route tables of the hosts may indeed grow large. For example, one =
of the hosts may be a website which millions of mobile hosts =
communicate simultaneously. Imagine a media or even just an HTTP server =
with a million per-host route entries. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Are there server companies and =
chip manufacturers working on hardware assisted look-up engines and =
code to do these lookups to meet the delay requirements?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Another approach we might take =
it to move the double NAT and fast (per-host routing) lookup functions =
to the (purpose built) subnet routers where they might have a chance of =
scaling. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; This might also serve to provide =
simultaneous route optimization with location privacy and allow the =
existing SA's between routers to be leveraged in order to avoid the =
necessity of setting up SA's every time a mobile node wishes to =
communicate with another node on the network.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; I am also fairly convinced that =
there are solutions which do not compromise the connectionless =
(redundant) nature of IP, especially in the IPv6 case.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Indeed this would not be =
creating a new protocol to solve the node mobility problem - it would =
be changing IP, itself, to solve the node mobility problem - =
essentially making a new &quot;pure&quot; IP.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; O.K. fire away&nbsp; - at least =
we might get off the &quot;what is a router&quot; debate. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Glenn </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A26C.420CD9C0--


From owner-seamoby@diameter.org  Fri Mar  2 05:23:11 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24935
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:23:10 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229YB202944
	for seamoby-list; Fri, 2 Mar 2001 01:34:11 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229Y6t02929
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:34:06 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:15 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:04 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 08:06:59 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SMs9E17245
	for seamoby-list; Wed, 28 Feb 2001 14:54:09 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SMs5o17240
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 14:54:05 -0800
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f1SM3cC20344
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 23:03:38 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Wed Feb 28 23:03:38 2001 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2651.58)
	id <F1J9B6M8>; Wed, 28 Feb 2001 23:05:06 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBAE@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'Glenn Morrow'" <gmorrow@nortelnetworks.com>
Cc: "'Michael Thomas'" <mat@cisco.com>, seamoby@diameter.org
Subject: RE: [seamoby] I-D ACTION:draft-ietf-seamoby-mm-problem-00.txt
Date: Wed, 28 Feb 2001 23:03:36 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hello Glenn, 

A router is a device that forwards packets from one interface to
another. That makes a NAT a router and so is a HA. 
A router CAN definitely tunnel, I hope you agree with that.

A NAT is a device that hides addresses on one side of the 
network from the other side and the end nodes. Typically 
because they are not routable. 
A HA _does_not_hide addresses from anyone. The end nodes 
and the entire Internet can route a MN's Home address. 
NATs typically break end to end security and many peer to
peer protocols. A HA doesn't.

I'm a bit surprised by your analogy and definitions but 
I dont really think we should spend our lives looking 
for a definition that makes a HA look like a NAT. 
Surely there are better reasons for justifying
the mm problem and better things to do.

Regards,
Hesham

> -----Original Message-----
> From:	Glenn Morrow [SMTP:gmorrow@nortelnetworks.com]
> Sent:	Thursday, 1 March 2001 7:16
> To:	'Hesham Soliman (ERA)'; 'Michael Thomas'
> Cc:	seamoby@diameter.org
> Subject:	RE: [seamoby] I-D ACTION:draft-ietf-seamoby-mm-problem-00.txt
> 
> I don't mean to jump but IMHO here are some things to realize about MIP in relation to these NAT statements: 
> 
> Route Optimized MIP is essentially per-host routing with some signaling (BU) and a double NAT function built into the end-nodes (hosts if you prefer).
> 
> Functionally you could decompose a MIP MN or a CN into the NAT, per-host routing (binding cache) functions and the "pure" host (applications) which uses the home addresses.
> 
> You could also think of the HA as a part of this double NAT as well; albeit, it is using a tunnel to statelessly signal the address translation.
> 
> The reason I am trying to bring this up to people is to make them realize the following: 
> 
> - It is per-host routing. 
> - It is double NAT (address translation at both ends) 
> 
> Because it is per-host routing the route tables of the hosts may indeed grow large. For example, one of the hosts may be a website which millions of mobile hosts communicate simultaneously. Imagine a media or even just an HTTP server with a million per-host route entries. 
> 
> Are there server companies and chip manufacturers working on hardware assisted look-up engines and code to do these lookups to meet the delay requirements?
> 
> Another approach we might take it to move the double NAT and fast (per-host routing) lookup functions to the (purpose built) subnet routers where they might have a chance of scaling. 
> 
> This might also serve to provide simultaneous route optimization with location privacy and allow the existing SA's between routers to be leveraged in order to avoid the necessity of setting up SA's every time a mobile node wishes to communicate with another node on the network.
> 
> I am also fairly convinced that there are solutions which do not compromise the connectionless (redundant) nature of IP, especially in the IPv6 case.
> 
> Indeed this would not be creating a new protocol to solve the node mobility problem - it would be changing IP, itself, to solve the node mobility problem - essentially making a new "pure" IP.
> 
> O.K. fire away  - at least we might get off the "what is a router" debate. 
> 
> Glenn 
> 
> 
> 
> 
> -----Original Message----- 
> From:   Hesham Soliman (ERA) [SMTP:Hesham.Soliman@era.ericsson.se] 
> Sent:   Tuesday, February 27, 2001 11:25 AM 
> To:     seamoby@cdma-2000.org 
> Subject:        RE: [seamoby] I-D ACTION:draft-ietf-seamoby-mm-problem-00.txt 
> 
> 
> > >     means choosing the shortest path between two nodes 
> > >     on the Internet. 
> > 
> > Can you define node ? 
> > 
>         => Host ? Terminal ? 
> 
> > >     I hope you don't mean that having a router in the 
> > >     middle that encapsulates a packet and forwards it 
> > >     to the right address is breaking the Internet 
> > >     model. That _is_routing.>  
> > 
> > But that is not what a Home Agent does.  No user application like 
> > email or web browsing on the internet addresses a router.  The cNode 
> > and MN in Mobile IP actually address the Home Agent which has no 
> > user application executing on it. 
> > 
>         => No it doesn't address the HA, this not true at all. The application 
>         addresses the Home address of the MN. The HA receives the 
>         packet because of its ND/ARP advertisements. I'm sure you 
>         know that already. So I don't know why you say that. 
> 
> 
> > tunnels the packet.  The inner portion of an IP tunnel is the application 
> > layer of the outer header.  So the Home Agent is in effect an application 
> > layer switch in the middle of the network which is not too different than a NAT. 
> > 
>         => That is a gross misinterpretation of a HA. How could it possibly be a NAT ? 
>         Do I need to list all the protocols that do not work through a NAT ? 
>         A HA does not operate above L3. This is the whole point behind MIP. 
> 
> > > 
> > >> An 
> > >> anchor point anywhere in the network is neither client nor 
> > >> server nor peer and therefore 
> > >> 
> > >     => It's a router ! They are usually in the middle 
> > >     and they're not clients or servers. 
> > 
> > See my point above.  The Home Agent is not a router.  
> > 
>         => Of course it's a router, define a router ? 
>         your claims above abou it being a NAT are wrong. 
>         The first few pages in the MIP spec tell you 
>         that it's a router don't they ? 
> 
> > Non-mobile 
> > clients, servers, and peers do not address routers.  IOW, the IP 
> > destination address of a packet originiating from a fixed client, server, or 
> > peer on the internet is not the address of a router.  
> > 
>         => I think you need to reread MIP. The CN does not 
>         address the HA. 
> 
> > >     => I agree, but there are ways of making it redundant 
> > >     like any other router. 
> > 
> > The only way is stateful transfer which requires some state other 
> > than IP routing to be transfered.  It's expensive an wasteful. 
> > What about networks that want to be multihomed ? 
> > 
>         => I was talking about a transfer of the binding cache. 
>         Multihoming is not an issues here is it ? 
> 
>         Regards, 
>         Hesham 
> 


From owner-seamoby@diameter.org  Fri Mar  2 05:29:51 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24987
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:29:50 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229aQ603073
	for seamoby-list; Fri, 2 Mar 2001 01:36:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229aLt03068
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:36:21 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:25 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:17 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 08:00:58 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SNFRU17352
	for seamoby-list; Wed, 28 Feb 2001 15:15:27 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SNFNo17347
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 15:15:24 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id HAA214380;
	Thu, 1 Mar 2001 07:16:17 +0900
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA04711;
 Wed, 28 Feb 2001 14:24:22 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA28804;
 Wed, 28 Feb 2001 14:23:47 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SMFiI02040
 for mobile-ip-dist; Wed, 28 Feb 2001 14:15:44 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SMFKE02010
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:15:21 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA25412
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:15:20 -0800 (PST)
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
 by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA11504
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:15:17 -0800 (PST)
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
 by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id HAA63294;
 Thu, 1 Mar 2001 07:06:26 +0900
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA00335;
 Wed, 28 Feb 2001 14:14:52 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA25211;
 Wed, 28 Feb 2001 14:14:41 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SMD6j01965
 for mobile-ip-dist; Wed, 28 Feb 2001 14:13:06 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SMCvE01955
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA00357
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
From: Phil_Neumiller@3Com.com
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA23795
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:12:56 -0700 (MST)
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
 by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SMBSo14321;
 Wed, 28 Feb 2001 14:11:28 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
 by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f1SMCnX06019;
 Wed, 28 Feb 2001 14:12:49 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A01.007A28B7 ; Wed, 28 Feb 2001 14:14:18 -0800
X-Lotus-FromDomain: 3COM
To: mobile-ip@sunroof.eng.sun.com
cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Message-ID: <88256A01.007A25AA.00@hqoutbound.ops.3com.com>
Date: Wed, 28 Feb 2001 16:11:37 -0600
Subject: RE: [seamoby] Arch discussions in IETF
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk




Hi Raj,

>Phil,
>
>I do not see anyone saying that Mobile IP is the only solution for all
>scenarios that require mobility. I am sure there are many scenarios
>that Mobile IP may or may not be the most optimal solution. If Mobile
>IP is unable to work as well as anything else you may have in mind
>for specific scenarios, then why deploy Mobile IP in such scenarios?

Then where might these other solutions be standardized in the IETF?
Would this fall under the classification of micro-mobility even though
the "so-called" COA or routing prefix does indeed change?  I guess what
I am getting at is there may be cases of infra-structure-less mobility
where the COA changes but there is no HA.  Would this be micro or
macro mobility?

>Can you be more specific on the kind of environments and requirements
>that these environments have that would make it impossible for Mobile
>IP to work in.

Sure.  Specifically, I am very interested in portable devices that will
find there way into homes.  Wireless appliances, MP3 players, digital
radios, digital security devices, gaming units, VoIP devices, etc.  I
am also interested in these types of devices that may be used in small
to medium business that may not have large infrastructures in place.

Thank you,

Phil Neumiller




From owner-seamoby@diameter.org  Fri Mar  2 05:32:48 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA25011
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:32:47 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229YL502960
	for seamoby-list; Fri, 2 Mar 2001 01:34:21 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229YBt02947
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:34:12 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:19:20 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 11:03:08 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f221XXM22741
	for seamoby-list; Thu, 1 Mar 2001 17:33:33 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f221XVo22736
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 17:33:31 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f220fgo03133;
	Thu, 1 Mar 2001 16:41:42 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f220h3X01328;
	Thu, 1 Mar 2001 16:43:03 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A03.0004133B ; Thu, 1 Mar 2001 16:44:30 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
cc: seamoby@diameter.org
Message-ID: <88256A03.00041298.00@hqoutbound.ops.3com.com>
Date: Thu, 1 Mar 2001 18:41:56 -0600
Subject: [seamoby] Killing the thread (I'm trying)
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk



If these issues were not of systemic importance to the future of SeaMoby the
thread would
have died long ago.  Some people try to ride dead horses, some people dig up
bones,
some people bury the hatchet.  This letter will do a bit of each.

1).  I no longer can nor do I advocate OBAST!  I agree with some of its high
level
      priciples. That technology is owned by Motorola, Inc. .  There are some
parts in
      the public domain of limited use.

2).  Micro-mobility was a tiny portion of OBAST, like an elephant's trunk.

3).  The SeaMoby charter is an IESG creation and has nothing
       to do with either OBAST or the CRAPS BOF.

4).  You will agree with me that the SeaMoby charter is composed of the work MIP
       no longer wanted or did not want to work on.

If we can agree to the above, I will be content that the truth is out about what
SeaMoby is "currently" woking on and what its IETF prospects are.   I will then
shut up (clap clap clap) bury all  hatchets and get to work.  BTW,  I find it
extremely
diffiticult to justify anything without architectural context.

Thanks,

Phil



From owner-seamoby@diameter.org  Fri Mar  2 05:33:10 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA25022
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:33:10 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229cMn03157
	for seamoby-list; Fri, 2 Mar 2001 01:38:22 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229cFt03142
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:38:15 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:18 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:21 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:32:38 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SMiB117216
	for seamoby-list; Wed, 28 Feb 2001 14:44:11 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SMi8o17211
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 14:44:09 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id GAA144468;
	Thu, 1 Mar 2001 06:44:55 +0900
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA20039;
 Wed, 28 Feb 2001 13:53:05 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA25209;
 Wed, 28 Feb 2001 13:52:37 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SLoMM01526
 for mobile-ip-dist; Wed, 28 Feb 2001 13:50:22 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SLo7E01503
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 13:50:08 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA19101
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 13:50:06 -0800 (PST)
From: Basavaraj.Patil@nokia.com
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA10922
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:49:45 -0700 (MST)
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
 by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SLnjg00849
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:49:45 -0600 (CST)
Received: from daebh02nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T52022655faac12f25715a@davir04nok.americas.nokia.com>;
 Wed, 28 Feb 2001 15:49:45 -0600
Received: by daebh02nok with Internet Mail Service (5.5.2652.78)
 id <FWSX4951>; Wed, 28 Feb 2001 15:49:45 -0600
Message-ID: <7B5C0390ACE7D211BC9C0008C7EABA2B03213561@daeis07nok>
To: Hesham.Soliman@era.ericsson.se, james.kempf@sun.com,
        mobile-ip@sunroof.eng.sun.com
Cc: claude.castelluccia@inrialpes.fr, seamoby@diameter.org, gdommety@cisco.com
Subject: RE: [seamoby] Is Mobile IP too slow or is Routing Table UpdateTo 
  o slow? (was....)
Date: Wed, 28 Feb 2001 15:49:44 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
 charset="iso-8859-1"
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk

> 
> 
>  Hi James
> 
> > Can you elaborate why you believe a design that 
> accommodates multiple levels of
> > hierarchy is a bad idea? The draft doesn't go into much 
> detail on this point.
> > 
>  => Well since the MIP list is broken we can take the discusion
>  on the sister list :)

The new MIP list is located at : mobile-ip@sunroof.eng.sun.com

-Basavaraj


From owner-seamoby@diameter.org  Fri Mar  2 05:39:22 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA25044
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 05:39:22 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223GgS23672
	for seamoby-list; Thu, 1 Mar 2001 19:16:42 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223Gco23667
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:16:39 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:57 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:50 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 06:22:20 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SLY7P16926
	for seamoby-list; Wed, 28 Feb 2001 13:34:07 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SLY1o16921
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 13:34:02 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA20117;
	Wed, 28 Feb 2001 12:43:23 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA08252;
	Wed, 28 Feb 2001 12:43:21 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id MAA02966;
	Wed, 28 Feb 2001 12:43:20 -0800 (PST)
Date: Wed, 28 Feb 2001 12:38:59 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
Subject: Re: [seamoby] Arch discussions in IETF
To: Phil_Neumiller@3Com.com
Cc: mobile-ip@marvin.corpeast.baynetworks.com, seamoby@diameter.org
In-Reply-To: "Your message with ID" <88256A01.006DF159.00@hqoutbound.ops.3com.com>
Message-ID: <Roam.SIMC.2.0.6.983392739.32498.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> We have said countless times that IETF does not define architecture.

Correct.

> However
> MIP did. Many of the problems people have with MIP are with its basic
> architecture, not the protocol.
> Why can't their be an architectural debate on MIP in the IETF (not protocol).
> There are boxes defined.  There is a CN, a MN, an HA, a set of routers. 
> Lets talk about how these
> need to play in today's modern residential and business deployments. 

As far as I'm concerned, MIP hasn't discussed architectures. If they had the
Mobile IP team would also be doing AAA, Qos And lots of other protocols. My
point all along is that piece parts are done within different WGs, and it is
the manufacturer's job to put the pieces together. 

My experience with this format has been most successful.

> Why do
> we always
> have to cater to cellular?  Why do the cellular guys get most the say? 

And where does this come from, may I ask? The only reason why you are probably
seeing more cellular stuff than anything else is because the cellular guys are
coming to the IETF and stating their requirements. Once we see people from
IEEE, Bluetooth and other relevant SDOs, I suspect you'll see more interest in
those areas as well.

However, as far as I know, the cellular guys do not have more say, they are
just the only ones present.

>  The
> Internet has
> new stuff like FTC, VoIP, SLP,  RSVP, diffserv, and new radio access
> technologies that
> can enable different types of mobility architectures.   Is an HA still a good
> idea in every scenario?  Why?  Can we talk about this?  If not why not? 
> Inquiring minds want to
> know.

and who exactly stated that one cannot talk about this??? Certainly not me. I
stated that arguments like "too slow" are hard to justify (unless you have
proof, and Andrew claimed 2 IETFs ago that MIP was as far as Cellular IP). If
there are problems with Home Agents, then the requirements should show this,
right?

> 
> Here is an example.  Why do I always need to use MIP?  Let's say I have a
> community of
> VPN's defined to interlink residences that interoperate with mobility (a
> bunch of families
> allows their mobiles to operate in each other's premises), i.e. mobile hosts
> are allowed
> to seamless travel within theses spaces but only in theses spaces (could be
> set up
> in hotel rooms, conferences, etc).  The COA changes but there is no HA.

ok, if that's what MM is, then great. 

> I have lots of scenarios like this.

and they aren't being ignored. Sure there are some Mobile IP folks that want
to protect their investment, but that is not the charter of this WG. We are
here to design a MM, but first need to identify the problem space. The -01 is
a really good start, and I suspect that -02 will be even better.

PatC


From owner-seamoby@diameter.org  Fri Mar  2 06:07:27 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25254
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 06:07:26 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223GQM23652
	for seamoby-list; Thu, 1 Mar 2001 19:16:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223G8o23619
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:16:08 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:55 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:37 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 06:25:39 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SLC5A16876
	for seamoby-list; Wed, 28 Feb 2001 13:12:05 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SLC2o16871
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 13:12:02 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Wed, 28 Feb 2001 15:19:35 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZV9734B>; Wed, 28 Feb 2001 15:19:36 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D17@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'James Kempf'" <james.kempf@sun.com>, Phil_Neumiller@3Com.com,
        seamoby@diameter.org
Subject: RE: [seamoby] Yet Another BOF?
Date: Wed, 28 Feb 2001 15:19:26 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A1C3.BF1AC070"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A1C3.BF1AC070
Content-Type: text/plain;
	charset="iso-8859-1"

Sorry Phil, I guess I misunderstood. The email in the front of my
mind from Phil didn't discuss paging, he was making a general argument.

My apologies for being confused.

Gary


> -----Original Message-----
> From: James Kempf [mailto:james.kempf@sun.com]
> Sent: Wednesday, February 28, 2001 3:08 PM
> To: Kenward, Gary [WDLN2:AN10:EXCH]; Phil_Neumiller@3Com.com;
> seamoby@diameter.org
> Subject: RE: [seamoby] Yet Another BOF?
> 
> 
> Hi Gary,
> 
> I think you missed what I said about paging.
> 
> If you read the paging problem statement draft carefully, you 
> will see that 
> practically
> everything that a paging protocol would do could be done by MIP. The 
> problem is,
> it would result in a considerable complexity increase, and 
> would compromise
> the utility of dormant mode for the mobile. Thus the 
> conclusion, a paging 
> protocol for IP would be a benefit.
> 
> If the MM folks can demonstrate the same w.r.t. to mobility, 
> particularly 
> for security and QoS, then I think a case can be made for an 
> MM protocol. 
> With all due respect to the MM design team and to John, the 
> draft editor, 
> the draft did not present such a clear case (at least, not 
> the 00 draft, I 
> have yet to read the 01 draft), at least not to me.
> If the mobile IP proponents are making these statements, then it is 
> incumbent upon the MM proponents to say: "Oh yeah? Show me 
> how!". If they 
> can't come up with a solution, and a sketch of an MM solution 
> is simpler, 
> then MM is clearly the way to go. The solution doesn't have 
> to be complete, 
> even a simple description is usually enough to see whether 
> the MIP solution 
> would be more complex or compromise particular requirements. 
> However, if in 
> the end, the mobile IP solution is good enough, in the
> sense that it satisfies the requirements, and the working 
> group agrees, 
> then its no good going off in a huff and accusing the mobile 
> IP proponents 
> of stonewalling.
> 
> I have no problem with giving the MM design team more time, since the 
> problem is more complex (and I hope the IESG will agree), 
> but, in the end, 
> I expect to see a technically based analysis, including 
> requirments and how 
> mobile IP can't solve them. It's OK to dream, but the rubber 
> hits the road 
> when you have to explain to skeptical engineers why your 
> completely new 
> solution will replace the existing solution in which they've 
> invested much 
> design and perhaps even implementation effort.
> 
>                  jak
> 
> At 01:18 PM 2/28/01 -0500, Gary Kenward wrote:
> 
> >James:
> >
> >   I think you miss Phil's point. It's all simply a matter of
> >software, and no doubt, with enough extensions, modifications,
> >and bit twiddling, we could turn ARP into some version of a
> >mobility protocol (or any other protocol, heck, there are still
> >people working on mobile wireless ATM).
> >
> >    The frustration comes because with each attempt at a
> >problem statement, MIP proponents come forth and state:
> >"oh, well sure, we can make MIP do that". No problem statement
> >for MM will ever be sufficient if this is the nature of the game.
> >
> >With all due respect,
> >Gary
> 
> 

------_=_NextPart_001_01C0A1C3.BF1AC070
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>RE: [seamoby] Yet Another BOF?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Sorry Phil, I guess I misunderstood. The email in the front of my</FONT>
<BR><FONT SIZE=2>mind from Phil didn't discuss paging, he was making a general argument.</FONT>
</P>

<P><FONT SIZE=2>My apologies for being confused.</FONT>
</P>

<P><FONT SIZE=2>Gary</FONT>
</P>
<BR>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: James Kempf [<A HREF="mailto:james.kempf@sun.com">mailto:james.kempf@sun.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Wednesday, February 28, 2001 3:08 PM</FONT>
<BR><FONT SIZE=2>&gt; To: Kenward, Gary [WDLN2:AN10:EXCH]; Phil_Neumiller@3Com.com;</FONT>
<BR><FONT SIZE=2>&gt; seamoby@diameter.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: RE: [seamoby] Yet Another BOF?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Hi Gary,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I think you missed what I said about paging.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; If you read the paging problem statement draft carefully, you </FONT>
<BR><FONT SIZE=2>&gt; will see that </FONT>
<BR><FONT SIZE=2>&gt; practically</FONT>
<BR><FONT SIZE=2>&gt; everything that a paging protocol would do could be done by MIP. The </FONT>
<BR><FONT SIZE=2>&gt; problem is,</FONT>
<BR><FONT SIZE=2>&gt; it would result in a considerable complexity increase, and </FONT>
<BR><FONT SIZE=2>&gt; would compromise</FONT>
<BR><FONT SIZE=2>&gt; the utility of dormant mode for the mobile. Thus the </FONT>
<BR><FONT SIZE=2>&gt; conclusion, a paging </FONT>
<BR><FONT SIZE=2>&gt; protocol for IP would be a benefit.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; If the MM folks can demonstrate the same w.r.t. to mobility, </FONT>
<BR><FONT SIZE=2>&gt; particularly </FONT>
<BR><FONT SIZE=2>&gt; for security and QoS, then I think a case can be made for an </FONT>
<BR><FONT SIZE=2>&gt; MM protocol. </FONT>
<BR><FONT SIZE=2>&gt; With all due respect to the MM design team and to John, the </FONT>
<BR><FONT SIZE=2>&gt; draft editor, </FONT>
<BR><FONT SIZE=2>&gt; the draft did not present such a clear case (at least, not </FONT>
<BR><FONT SIZE=2>&gt; the 00 draft, I </FONT>
<BR><FONT SIZE=2>&gt; have yet to read the 01 draft), at least not to me.</FONT>
<BR><FONT SIZE=2>&gt; If the mobile IP proponents are making these statements, then it is </FONT>
<BR><FONT SIZE=2>&gt; incumbent upon the MM proponents to say: &quot;Oh yeah? Show me </FONT>
<BR><FONT SIZE=2>&gt; how!&quot;. If they </FONT>
<BR><FONT SIZE=2>&gt; can't come up with a solution, and a sketch of an MM solution </FONT>
<BR><FONT SIZE=2>&gt; is simpler, </FONT>
<BR><FONT SIZE=2>&gt; then MM is clearly the way to go. The solution doesn't have </FONT>
<BR><FONT SIZE=2>&gt; to be complete, </FONT>
<BR><FONT SIZE=2>&gt; even a simple description is usually enough to see whether </FONT>
<BR><FONT SIZE=2>&gt; the MIP solution </FONT>
<BR><FONT SIZE=2>&gt; would be more complex or compromise particular requirements. </FONT>
<BR><FONT SIZE=2>&gt; However, if in </FONT>
<BR><FONT SIZE=2>&gt; the end, the mobile IP solution is good enough, in the</FONT>
<BR><FONT SIZE=2>&gt; sense that it satisfies the requirements, and the working </FONT>
<BR><FONT SIZE=2>&gt; group agrees, </FONT>
<BR><FONT SIZE=2>&gt; then its no good going off in a huff and accusing the mobile </FONT>
<BR><FONT SIZE=2>&gt; IP proponents </FONT>
<BR><FONT SIZE=2>&gt; of stonewalling.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I have no problem with giving the MM design team more time, since the </FONT>
<BR><FONT SIZE=2>&gt; problem is more complex (and I hope the IESG will agree), </FONT>
<BR><FONT SIZE=2>&gt; but, in the end, </FONT>
<BR><FONT SIZE=2>&gt; I expect to see a technically based analysis, including </FONT>
<BR><FONT SIZE=2>&gt; requirments and how </FONT>
<BR><FONT SIZE=2>&gt; mobile IP can't solve them. It's OK to dream, but the rubber </FONT>
<BR><FONT SIZE=2>&gt; hits the road </FONT>
<BR><FONT SIZE=2>&gt; when you have to explain to skeptical engineers why your </FONT>
<BR><FONT SIZE=2>&gt; completely new </FONT>
<BR><FONT SIZE=2>&gt; solution will replace the existing solution in which they've </FONT>
<BR><FONT SIZE=2>&gt; invested much </FONT>
<BR><FONT SIZE=2>&gt; design and perhaps even implementation effort.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jak</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; At 01:18 PM 2/28/01 -0500, Gary Kenward wrote:</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt;James:</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&nbsp;&nbsp; I think you miss Phil's point. It's all simply a matter of</FONT>
<BR><FONT SIZE=2>&gt; &gt;software, and no doubt, with enough extensions, modifications,</FONT>
<BR><FONT SIZE=2>&gt; &gt;and bit twiddling, we could turn ARP into some version of a</FONT>
<BR><FONT SIZE=2>&gt; &gt;mobility protocol (or any other protocol, heck, there are still</FONT>
<BR><FONT SIZE=2>&gt; &gt;people working on mobile wireless ATM).</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&nbsp;&nbsp;&nbsp; The frustration comes because with each attempt at a</FONT>
<BR><FONT SIZE=2>&gt; &gt;problem statement, MIP proponents come forth and state:</FONT>
<BR><FONT SIZE=2>&gt; &gt;&quot;oh, well sure, we can make MIP do that&quot;. No problem statement</FONT>
<BR><FONT SIZE=2>&gt; &gt;for MM will ever be sufficient if this is the nature of the game.</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;With all due respect,</FONT>
<BR><FONT SIZE=2>&gt; &gt;Gary</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A1C3.BF1AC070--


From owner-seamoby@diameter.org  Fri Mar  2 06:08:36 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25291
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 06:08:34 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223G9N23621
	for seamoby-list; Thu, 1 Mar 2001 19:16:09 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223Fqo23596
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:15:53 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:47 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:09 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:48:30 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SMfsW17198
	for seamoby-list; Wed, 28 Feb 2001 14:41:54 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SMfco17193
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 14:41:39 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id GAA145242;
	Thu, 1 Mar 2001 06:42:31 +0900
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA18777;
 Wed, 28 Feb 2001 13:50:40 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA19090;
 Wed, 28 Feb 2001 13:50:00 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SLlT201468
 for mobile-ip-dist; Wed, 28 Feb 2001 13:47:29 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SLlKE01461
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 13:47:20 -0800 (PST)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA19192
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 13:47:18 -0800 (PST)
From: Basavaraj.Patil@nokia.com
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
 by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA24876
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 13:47:03 -0800 (PST)
Received: from davir03nok.americas.nokia.com (davir03nok.americas.nokia.com [172.18.242.86])
 by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SLl2g00544
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:47:02 -0600 (CST)
Received: from daebh01nok.americas.nokia.com (unverified) by davir03nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T520223d95aac12f256081@davir03nok.americas.nokia.com>;
 Wed, 28 Feb 2001 15:47:02 -0600
Received: by daebh01nok with Internet Mail Service (5.5.2652.78)
 id <FWSVH6M2>; Wed, 28 Feb 2001 15:47:02 -0600
Message-ID: <7B5C0390ACE7D211BC9C0008C7EABA2B03213560@daeis07nok>
To: Phil_Neumiller@3com.com, mobile-ip@sunroof.eng.sun.com
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Arch discussions in IETF
Date: Wed, 28 Feb 2001 15:47:01 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
 charset="iso-8859-1"
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk

Phil,

I do not see anyone saying that Mobile IP is the only solution for all
scenarios that require mobility. I am sure there are many scenarios
that Mobile IP may or may not be the most optimal solution. If Mobile
IP is unable to work as well as anything else you may have in mind 
for specific scenarios, then why deploy Mobile IP in such scenarios?
Can you be more specific on the kind of environments and requirements
that these environments have that would make it impossible for Mobile
IP to work in.

-Basavaraj

Pls. note that the Mobile IP mailing list has a new address.

> -----Original Message-----
> From: ext Phil_Neumiller@3Com.com [mailto:Phil_Neumiller@3Com.com]
> Sent: Wednesday, February 28, 2001 1:46 PM
> To: mobile-ip@marvin.corpeast.baynetworks.com
> Cc: seamoby@diameter.org
> Subject: [seamoby] Arch discussions in IETF
> 
> 
> 
> 
> 
> We have said countless times that IETF does not define 
> architecture.  However
> MIP did.
> Many of the problems people have with MIP are with its basic 
> architecture, not
> the protocol.
> Why can't their be an architectural debate on MIP in the IETF 
> (not protocol).
> There are
> boxes defined.  There is a CN, a MN, an HA, a set of routers. 
>  Lets talk about
> how these
> need to play in today's modern residential and business 
> deployments.  Why do we
> always
> have to cater to cellular?  Why do the cellular guys get most 
> the say?   The
> Internet has
> new stuff like FTC, VoIP, SLP,  RSVP, diffserv, and new radio access
> technologies that
> can enable different types of mobility architectures.   Is an 
> HA still a good
> idea in
> every scenario?  Why?  Can we talk about this?  If not why 
> not?  Inquiring minds
> want to
> know.
> 
> Here is an example.  Why do I always need to use MIP?  Let's 
> say I have a
> community of
> VPN's defined to interlink residences that interoperate with 
> mobility (a bunch
> of families
> allows their mobiles to operate in each other's premises), 
> i.e. mobile hosts are
> allowed
> to seamless travel within theses spaces but only in theses 
> spaces (could be set
> up
> in hotel rooms, conferences, etc).  The COA changes but there 
> is no HA.
> 
> I have lots of scenarios like this.
> 
> Thanks,
> 
> Phil
> 
> 
> 
> I believe that the problem statement does have some things 
> that Mobile IP will
> have a REALLY hard time handling. However, as I have stated 
> numerous times,
> statements like "MIP is too slow" just doesn't cut it. Let's 
> get to the meat
> of the requirements, and then we can identify whether MIP can 
> do the job.
> 
> PatC
> 
> 


From owner-seamoby@diameter.org  Fri Mar  2 06:22:11 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25363
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 06:22:10 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223Fql23594
	for seamoby-list; Thu, 1 Mar 2001 19:15:52 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223Fio23584
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:15:44 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:51 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:52 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 08:22:09 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SNFG017342
	for seamoby-list; Wed, 28 Feb 2001 15:15:16 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SNFCo17337
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 15:15:12 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id HAA187722;
	Thu, 1 Mar 2001 07:16:04 +0900
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA04702;
 Wed, 28 Feb 2001 14:24:21 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA27524;
 Wed, 28 Feb 2001 14:23:59 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SMI3p02222
 for mobile-ip-dist; Wed, 28 Feb 2001 14:18:03 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SMHdE02179
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:17:39 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
 by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA27233
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:17:39 -0800 (PST)
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
 by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA13692
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:17:38 -0800 (PST)
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
 by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id HAA226548;
 Thu, 1 Mar 2001 07:08:56 +0900
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
 by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA26835;
 Wed, 28 Feb 2001 14:16:56 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA25737;
 Wed, 28 Feb 2001 14:16:22 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SMD6j01965
 for mobile-ip-dist; Wed, 28 Feb 2001 14:13:06 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SMCvE01955
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA00357
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
From: Phil_Neumiller@3Com.com
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA23795
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:12:56 -0700 (MST)
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
 by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SMBSo14321;
 Wed, 28 Feb 2001 14:11:28 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
 by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f1SMCnX06019;
 Wed, 28 Feb 2001 14:12:49 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A01.007A28B7 ; Wed, 28 Feb 2001 14:14:18 -0800
X-Lotus-FromDomain: 3COM
To: mobile-ip@sunroof.eng.sun.com
cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Message-ID: <88256A01.007A25AA.00@hqoutbound.ops.3com.com>
Date: Wed, 28 Feb 2001 16:11:37 -0600
Subject: RE: [seamoby] Arch discussions in IETF
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk




Hi Raj,

>Phil,
>
>I do not see anyone saying that Mobile IP is the only solution for all
>scenarios that require mobility. I am sure there are many scenarios
>that Mobile IP may or may not be the most optimal solution. If Mobile
>IP is unable to work as well as anything else you may have in mind
>for specific scenarios, then why deploy Mobile IP in such scenarios?

Then where might these other solutions be standardized in the IETF?
Would this fall under the classification of micro-mobility even though
the "so-called" COA or routing prefix does indeed change?  I guess what
I am getting at is there may be cases of infra-structure-less mobility
where the COA changes but there is no HA.  Would this be micro or
macro mobility?

>Can you be more specific on the kind of environments and requirements
>that these environments have that would make it impossible for Mobile
>IP to work in.

Sure.  Specifically, I am very interested in portable devices that will
find there way into homes.  Wireless appliances, MP3 players, digital
radios, digital security devices, gaming units, VoIP devices, etc.  I
am also interested in these types of devices that may be used in small
to medium business that may not have large infrastructures in place.

Thank you,

Phil Neumiller




From owner-seamoby@diameter.org  Fri Mar  2 06:28:57 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25420
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 06:28:54 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223FTe23568
	for seamoby-list; Thu, 1 Mar 2001 19:15:29 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223FGo23547
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:15:16 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:29 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:16 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 04:17:03 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SJBfD16510
	for seamoby-list; Wed, 28 Feb 2001 11:11:41 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SJBco16505
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 11:11:39 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Wed, 28 Feb 2001 13:18:51 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZV97L15>; Wed, 28 Feb 2001 13:18:52 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D0D@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'James Kempf'" <james.kempf@sun.com>, Phil_Neumiller@3Com.com,
        seamoby@diameter.org
Subject: RE: [seamoby] Yet Another BOF?
Date: Wed, 28 Feb 2001 13:18:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A1B2.E4C573D0"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A1B2.E4C573D0
Content-Type: text/plain;
	charset="iso-8859-1"

James:

  I think you miss Phil's point. It's all simply a matter of
software, and no doubt, with enough extensions, modifications, 
and bit twiddling, we could turn ARP into some version of a 
mobility protocol (or any other protocol, heck, there are still
people working on mobile wireless ATM).

   The frustration comes because with each attempt at a
problem statement, MIP proponents come forth and state:
"oh, well sure, we can make MIP do that". No problem statement
for MM will ever be sufficient if this is the nature of the game.

With all due respect,
Gary

> -----Original Message-----
> From: James Kempf [mailto:james.kempf@sun.com]
> Sent: Tuesday, February 27, 2001 7:01 PM
> To: Phil_Neumiller@3Com.com; seamoby@diameter.org
> Subject: Re: [seamoby] Yet Another BOF?
> 
> 
> Phil,
> 
> I think you are being much too pessimistic. Dana and Mike 
> Thomas have raised
> some significant issues regarding the interaction between MIP 
> and routing. 
> Thought
> the rhetoric and accusations have been flying, there is the 
> kernel of some 
> serious questions that need to be addressed. In particular, 
> the interaction 
> of RSVP and MIP that Mike has identified in his draft are 
> serious, since 
> RSVP was designed with standard routing protocols in mind, 
> not with MIP. 
> Perhaps they can be fixed by aggregated RSVP, perhaps not 
> (after reading 
> the aggregated RSVP draft, I
> have my doubts).
> 
> In any event, working out the details and pinning down 
> exactly what can and 
> can't be
> done using MIP will be what tips the balance of whether a 
> routing based 
> micromobility protocol gets done or not. If you look in the 
> paging draft, 
> ultimately, we determined that it would be possible to do 
> most everything 
> using MIP, but practical considerations and the complexity of 
> doing it 
> argued for a modest IP paging protocol. Something similar may 
> happen for 
> micromobility as well.
> 
> So...hang in there!
> 
>                  jak
> 
> PS: regarding fiber in Nebraska and New York, the point is, New York 
> probably has
> the fiber, and the ROI of laying it in Nebraska probably 
> isn't big enough 
> (especially
> considering the telco financial condition these days) to do 
> justify it. 
> Just as with paging, you need to give the people doing the network 
> engineering some flexibility
> without overwhelming them with options.
> 
> At 05:50 PM 2/27/01 -0600, Phil_Neumiller@3Com.com wrote:
> 
> 
> 
> >After a brief history with mobility BOFs,  I am convinced 
> that they are of
> >limited use.  Perhaps an
> >informational RFC is a better approach (not my idea).  I am 
> convinced that 
> >many
> >of us (perhaps
> >Gary, (Andrew, James, John, Peter, and the other OBAST 
> disciples:-))) that
> >wanted to build true
> >all IP based, edge oriented, routers with wireless cards, 
> with a standardized
> >backhaul, some
> >how got muscled out of the IETF by the powerful forces of 
> the MIP and MANET
> >groups.  We
> >played nice, let them hack up the charter into what is now a 
> tenuous set of
> >problem statements
> >dangling on the edge of existence.
> >
> >I for one find it difficult to contribute or create in this type of 
> >forum.  Its
> >completely stifling.  We need
> >to throw out all the assumptions and start from a clean 
> slate.  We need to
> >consider the implications of
> >ultra-wideband, widespread deployment of MMDS/LMDS, OFDM, 
> hybrid fiber 
> >wireless
> >schemes and
> >how they interact with mobility, and the failure of 3G.  I 
> am tired of arguing
> >about the minutia of where
> >an FA lives or whether its macro or micro mobility.  They 
> will all likely be
> >irrelevant in the forth coming
> >world of glass pipes everywhere (its easier to lay glass in 
> Nebraska than 
> >in NYC
> >James :-)).
> >
> >Some folks have approached me about another BOF.  I am 
> convinced it would 
> >NOT be
> >a good thing.
> >An informational RFC COULD provide a way to articulate some 
> ideas in a way 
> >that
> >at least gets them
> >documented and shared.  Some other folks have approached me 
> about this 
> >concept.
> >I am in favor
> >of this.  How about a seamoby4g mail list?  Anybody 
> interested in a 4g seamoby
> >list?  This would
> >get all the off charter dreamware chatter off the seamoby list.
> >
> >As for the SeaMoby WG, at this point I don't know.  We have 
> to see what 
> >happens.
> >It looks to me
> >like SeaMoby is becoming MIP's newborn cousin at this point. 
>  Hopefully, late
> >term abortions aren't
> >allowed.
> >
> >Thanks,
> >
> >Phil Neumiller
> 
> 

------_=_NextPart_001_01C0A1B2.E4C573D0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>RE: [seamoby] Yet Another BOF?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>James:</FONT>
</P>

<P><FONT SIZE=2>&nbsp; I think you miss Phil's point. It's all simply a matter of</FONT>
<BR><FONT SIZE=2>software, and no doubt, with enough extensions, modifications, </FONT>
<BR><FONT SIZE=2>and bit twiddling, we could turn ARP into some version of a </FONT>
<BR><FONT SIZE=2>mobility protocol (or any other protocol, heck, there are still</FONT>
<BR><FONT SIZE=2>people working on mobile wireless ATM).</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp; The frustration comes because with each attempt at a</FONT>
<BR><FONT SIZE=2>problem statement, MIP proponents come forth and state:</FONT>
<BR><FONT SIZE=2>&quot;oh, well sure, we can make MIP do that&quot;. No problem statement</FONT>
<BR><FONT SIZE=2>for MM will ever be sufficient if this is the nature of the game.</FONT>
</P>

<P><FONT SIZE=2>With all due respect,</FONT>
<BR><FONT SIZE=2>Gary</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: James Kempf [<A HREF="mailto:james.kempf@sun.com">mailto:james.kempf@sun.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Tuesday, February 27, 2001 7:01 PM</FONT>
<BR><FONT SIZE=2>&gt; To: Phil_Neumiller@3Com.com; seamoby@diameter.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: Re: [seamoby] Yet Another BOF?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Phil,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I think you are being much too pessimistic. Dana and Mike </FONT>
<BR><FONT SIZE=2>&gt; Thomas have raised</FONT>
<BR><FONT SIZE=2>&gt; some significant issues regarding the interaction between MIP </FONT>
<BR><FONT SIZE=2>&gt; and routing. </FONT>
<BR><FONT SIZE=2>&gt; Thought</FONT>
<BR><FONT SIZE=2>&gt; the rhetoric and accusations have been flying, there is the </FONT>
<BR><FONT SIZE=2>&gt; kernel of some </FONT>
<BR><FONT SIZE=2>&gt; serious questions that need to be addressed. In particular, </FONT>
<BR><FONT SIZE=2>&gt; the interaction </FONT>
<BR><FONT SIZE=2>&gt; of RSVP and MIP that Mike has identified in his draft are </FONT>
<BR><FONT SIZE=2>&gt; serious, since </FONT>
<BR><FONT SIZE=2>&gt; RSVP was designed with standard routing protocols in mind, </FONT>
<BR><FONT SIZE=2>&gt; not with MIP. </FONT>
<BR><FONT SIZE=2>&gt; Perhaps they can be fixed by aggregated RSVP, perhaps not </FONT>
<BR><FONT SIZE=2>&gt; (after reading </FONT>
<BR><FONT SIZE=2>&gt; the aggregated RSVP draft, I</FONT>
<BR><FONT SIZE=2>&gt; have my doubts).</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; In any event, working out the details and pinning down </FONT>
<BR><FONT SIZE=2>&gt; exactly what can and </FONT>
<BR><FONT SIZE=2>&gt; can't be</FONT>
<BR><FONT SIZE=2>&gt; done using MIP will be what tips the balance of whether a </FONT>
<BR><FONT SIZE=2>&gt; routing based </FONT>
<BR><FONT SIZE=2>&gt; micromobility protocol gets done or not. If you look in the </FONT>
<BR><FONT SIZE=2>&gt; paging draft, </FONT>
<BR><FONT SIZE=2>&gt; ultimately, we determined that it would be possible to do </FONT>
<BR><FONT SIZE=2>&gt; most everything </FONT>
<BR><FONT SIZE=2>&gt; using MIP, but practical considerations and the complexity of </FONT>
<BR><FONT SIZE=2>&gt; doing it </FONT>
<BR><FONT SIZE=2>&gt; argued for a modest IP paging protocol. Something similar may </FONT>
<BR><FONT SIZE=2>&gt; happen for </FONT>
<BR><FONT SIZE=2>&gt; micromobility as well.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; So...hang in there!</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jak</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; PS: regarding fiber in Nebraska and New York, the point is, New York </FONT>
<BR><FONT SIZE=2>&gt; probably has</FONT>
<BR><FONT SIZE=2>&gt; the fiber, and the ROI of laying it in Nebraska probably </FONT>
<BR><FONT SIZE=2>&gt; isn't big enough </FONT>
<BR><FONT SIZE=2>&gt; (especially</FONT>
<BR><FONT SIZE=2>&gt; considering the telco financial condition these days) to do </FONT>
<BR><FONT SIZE=2>&gt; justify it. </FONT>
<BR><FONT SIZE=2>&gt; Just as with paging, you need to give the people doing the network </FONT>
<BR><FONT SIZE=2>&gt; engineering some flexibility</FONT>
<BR><FONT SIZE=2>&gt; without overwhelming them with options.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; At 05:50 PM 2/27/01 -0600, Phil_Neumiller@3Com.com wrote:</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt;After a brief history with mobility BOFs,&nbsp; I am convinced </FONT>
<BR><FONT SIZE=2>&gt; that they are of</FONT>
<BR><FONT SIZE=2>&gt; &gt;limited use.&nbsp; Perhaps an</FONT>
<BR><FONT SIZE=2>&gt; &gt;informational RFC is a better approach (not my idea).&nbsp; I am </FONT>
<BR><FONT SIZE=2>&gt; convinced that </FONT>
<BR><FONT SIZE=2>&gt; &gt;many</FONT>
<BR><FONT SIZE=2>&gt; &gt;of us (perhaps</FONT>
<BR><FONT SIZE=2>&gt; &gt;Gary, (Andrew, James, John, Peter, and the other OBAST </FONT>
<BR><FONT SIZE=2>&gt; disciples:-))) that</FONT>
<BR><FONT SIZE=2>&gt; &gt;wanted to build true</FONT>
<BR><FONT SIZE=2>&gt; &gt;all IP based, edge oriented, routers with wireless cards, </FONT>
<BR><FONT SIZE=2>&gt; with a standardized</FONT>
<BR><FONT SIZE=2>&gt; &gt;backhaul, some</FONT>
<BR><FONT SIZE=2>&gt; &gt;how got muscled out of the IETF by the powerful forces of </FONT>
<BR><FONT SIZE=2>&gt; the MIP and MANET</FONT>
<BR><FONT SIZE=2>&gt; &gt;groups.&nbsp; We</FONT>
<BR><FONT SIZE=2>&gt; &gt;played nice, let them hack up the charter into what is now a </FONT>
<BR><FONT SIZE=2>&gt; tenuous set of</FONT>
<BR><FONT SIZE=2>&gt; &gt;problem statements</FONT>
<BR><FONT SIZE=2>&gt; &gt;dangling on the edge of existence.</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;I for one find it difficult to contribute or create in this type of </FONT>
<BR><FONT SIZE=2>&gt; &gt;forum.&nbsp; Its</FONT>
<BR><FONT SIZE=2>&gt; &gt;completely stifling.&nbsp; We need</FONT>
<BR><FONT SIZE=2>&gt; &gt;to throw out all the assumptions and start from a clean </FONT>
<BR><FONT SIZE=2>&gt; slate.&nbsp; We need to</FONT>
<BR><FONT SIZE=2>&gt; &gt;consider the implications of</FONT>
<BR><FONT SIZE=2>&gt; &gt;ultra-wideband, widespread deployment of MMDS/LMDS, OFDM, </FONT>
<BR><FONT SIZE=2>&gt; hybrid fiber </FONT>
<BR><FONT SIZE=2>&gt; &gt;wireless</FONT>
<BR><FONT SIZE=2>&gt; &gt;schemes and</FONT>
<BR><FONT SIZE=2>&gt; &gt;how they interact with mobility, and the failure of 3G.&nbsp; I </FONT>
<BR><FONT SIZE=2>&gt; am tired of arguing</FONT>
<BR><FONT SIZE=2>&gt; &gt;about the minutia of where</FONT>
<BR><FONT SIZE=2>&gt; &gt;an FA lives or whether its macro or micro mobility.&nbsp; They </FONT>
<BR><FONT SIZE=2>&gt; will all likely be</FONT>
<BR><FONT SIZE=2>&gt; &gt;irrelevant in the forth coming</FONT>
<BR><FONT SIZE=2>&gt; &gt;world of glass pipes everywhere (its easier to lay glass in </FONT>
<BR><FONT SIZE=2>&gt; Nebraska than </FONT>
<BR><FONT SIZE=2>&gt; &gt;in NYC</FONT>
<BR><FONT SIZE=2>&gt; &gt;James :-)).</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;Some folks have approached me about another BOF.&nbsp; I am </FONT>
<BR><FONT SIZE=2>&gt; convinced it would </FONT>
<BR><FONT SIZE=2>&gt; &gt;NOT be</FONT>
<BR><FONT SIZE=2>&gt; &gt;a good thing.</FONT>
<BR><FONT SIZE=2>&gt; &gt;An informational RFC COULD provide a way to articulate some </FONT>
<BR><FONT SIZE=2>&gt; ideas in a way </FONT>
<BR><FONT SIZE=2>&gt; &gt;that</FONT>
<BR><FONT SIZE=2>&gt; &gt;at least gets them</FONT>
<BR><FONT SIZE=2>&gt; &gt;documented and shared.&nbsp; Some other folks have approached me </FONT>
<BR><FONT SIZE=2>&gt; about this </FONT>
<BR><FONT SIZE=2>&gt; &gt;concept.</FONT>
<BR><FONT SIZE=2>&gt; &gt;I am in favor</FONT>
<BR><FONT SIZE=2>&gt; &gt;of this.&nbsp; How about a seamoby4g mail list?&nbsp; Anybody </FONT>
<BR><FONT SIZE=2>&gt; interested in a 4g seamoby</FONT>
<BR><FONT SIZE=2>&gt; &gt;list?&nbsp; This would</FONT>
<BR><FONT SIZE=2>&gt; &gt;get all the off charter dreamware chatter off the seamoby list.</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;As for the SeaMoby WG, at this point I don't know.&nbsp; We have </FONT>
<BR><FONT SIZE=2>&gt; to see what </FONT>
<BR><FONT SIZE=2>&gt; &gt;happens.</FONT>
<BR><FONT SIZE=2>&gt; &gt;It looks to me</FONT>
<BR><FONT SIZE=2>&gt; &gt;like SeaMoby is becoming MIP's newborn cousin at this point. </FONT>
<BR><FONT SIZE=2>&gt;&nbsp; Hopefully, late</FONT>
<BR><FONT SIZE=2>&gt; &gt;term abortions aren't</FONT>
<BR><FONT SIZE=2>&gt; &gt;allowed.</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;Thanks,</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;Phil Neumiller</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A1B2.E4C573D0--


From owner-seamoby@diameter.org  Fri Mar  2 06:41:07 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25526
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 06:41:04 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f22BUAT04965
	for seamoby-list; Fri, 2 Mar 2001 03:30:10 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f22BU7t04951
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 03:30:07 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 19:31:04 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 18:49:40 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229bMF03109
	for seamoby-list; Fri, 2 Mar 2001 01:37:22 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229bDt03103
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:37:14 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:38 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:41 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 13:04:03 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f213qLM18416
	for seamoby-list; Wed, 28 Feb 2001 19:52:21 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f213qJo18411
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 19:52:19 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <FZGPC54A>; Wed, 28 Feb 2001 22:01:53 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D29DC@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <KAtwal@zucotto.com>
To: seamoby@diameter.org
Subject: RE: [seamoby] Yet Another BOF?
Date: Wed, 28 Feb 2001 22:01:52 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

3.2 MANET / Ad-Hoc Networking Comparison

   The MANET WG in the IETF has an important charter to create a
   protocol for mobiles arranged in arbitrary and highly dynamic
   associations.  This work is striving for robust and highly scalable
   routing solutions.  Currently, MANET is not considering fast or
   seamless handover.

   In many instances, for example small residential networks found in
   the home, the network may be relatively small and has far less
   dynamics.  The network may still have a requirement for fast and/or
   seamless handovers. For this reason there may be some overlap
   between SeaMoby and ad-hoc networking solutions.  Therefore, SeaMoby
   MUST be able to co-exist gracefully with any MANET solutions
   algorithm that does become standardized.

> -----Original Message-----
> From: Phil_Neumiller@3com.com [mailto:Phil_Neumiller@3com.com]
> Sent: Tuesday, February 27, 2001 6:51 PM
> To: seamoby@diameter.org
> Subject: [seamoby] Yet Another BOF?
> 
> 
> 
> 
> 
> After a brief history with mobility BOFs,  I am convinced 
> that they are of
> limited use.  Perhaps an
> informational RFC is a better approach (not my idea).  I am 
> convinced that many
> of us (perhaps
> Gary, (Andrew, James, John, Peter, and the other OBAST 
> disciples:-))) that
> wanted to build true
> all IP based, edge oriented, routers with wireless cards, 
> with a standardized
> backhaul, some
> how got muscled out of the IETF by the powerful forces of the 
> MIP and MANET
> groups.  

In the Micro-mobility draft the following section appears:

3.2 MANET / Ad-Hoc Networking Comparison

   The MANET WG in the IETF has an important charter to create a
   protocol for mobiles arranged in arbitrary and highly dynamic
   associations.  This work is striving for robust and highly scalable
   routing solutions.  Currently, MANET is not considering fast or
   seamless handover.

   In many instances, for example small residential networks found in
   the home, the network may be relatively small and has far less
   dynamics.  The network may still have a requirement for fast and/or
   seamless handovers. For this reason there may be some overlap
   between SeaMoby and ad-hoc networking solutions.  Therefore, SeaMoby
   MUST be able to co-exist gracefully with any MANET solutions
   algorithm that does become standardized.

Comments:

Why 'MUST' SeaMoby be confined by MANET/MIP?  
If SeaMoby does its job there will be no need for MANET in local mobility.
If SeaMoby does its job there will be no need for MIP in local mobility.

Are we forgetting that devices in the home are low cost?
Why would any vendor support MIP, MANET and Seamoby to do one thing: moving?
Why would any Bluetooth vendor support three protocols when the same vendor 
can go to the Bluetooth SIG and use the work of a SIG WG to get one
protocol?

The title of the section says ,"Comparion", but states a mandatory
requirement.
By making MANET a 'MUST' requirement for Seamoby is a sure way to see that
Seamoby is 
never deployed.

I would like someone the justify the opening statement in section 3.2:

   The MANET WG in the IETF has an important charter to create a
   protocol for mobiles arranged in arbitrary and highly dynamic
   associations.

Is the MANET charter more important than the SeaMoby Charter?

What is an "arbitary association" and how does it differ from mobility?

What is the timescale for "highly dynamic associations"?

- Kulwinder.


From owner-seamoby@diameter.org  Fri Mar  2 06:43:04 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25553
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 06:43:03 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f22BW6m05073
	for seamoby-list; Fri, 2 Mar 2001 03:32:06 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f22BW0t05065
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 03:32:00 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 19:33:35 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 18:41:15 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229XwJ02920
	for seamoby-list; Fri, 2 Mar 2001 01:33:58 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229Xrt02913
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:33:53 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:15 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:07 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:16:32 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SLpQw16994
	for seamoby-list; Wed, 28 Feb 2001 13:51:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SLnZo16975
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 13:49:36 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id FAA138862;
	Thu, 1 Mar 2001 05:50:15 +0900
Received: from smtprch2.nortel.com (erchg0k.us.nortel.com [47.113.64.104])
 by zrtps06u.us.nortel.com (8.11.0/8.11.0) with ESMTP id f1SKvsl13168
 for <paullee@korea.ac.kr>; Wed, 28 Feb 2001 15:57:54 -0500 (EST)
Received: from zrchh190 by smtprch2.nortel.com; Wed, 28 Feb 2001 13:53:16 -0600
Received: from marvin.corpeast.baynetworks.com by zrchh190;
          Wed, 28 Feb 2001 13:49:23 -0600
Received: from qcarh006.nortelnetworks.com (zcars00w.ca.nortel.com [47.128.0.50]) 
          by marvin.corpeast.baynetworks.com (8.8.8+Sun/8.8.8) with ESMTP 
          id OAA20083 for <mobile-ip@marvin.baynetworks.com>;
          Wed, 28 Feb 2001 14:42:30 -0500 (EST)
Received: from ecarsaaa.nortelnetworks.com by qcarh006.nortelnetworks.com;
          Wed, 28 Feb 2001 14:40:12 -0500
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116]) 
          by ecarsaaa.nortelnetworks.com with SMTP (MailShield v1.5);
          Wed, 28 Feb 2001 14:42:18 -0500
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61]) 
          by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) 
          with SMTP id f1SJgGC01873 
          for <mobile-ip@standards.nortelnetworks.com>;
          Wed, 28 Feb 2001 20:42:17 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ;
          Wed Feb 28 20:42:17 2001 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2651.58) id <F1J9B31L>;
          Wed, 28 Feb 2001 20:42:15 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBAB@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'James Kempf'" <james.kempf@sun.com>,
        mobile-ip@marvin.corpeast.baynetworks.com
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
Date: Wed, 28 Feb 2001 20:42:15 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
X-SMTP-HELO: albatross-ext.wise.edt.ericsson.se
X-SMTP-MAIL-FROM: Hesham.Soliman@era.ericsson.se
X-SMTP-RCPT-TO: mobile-ip@standards.nortelnetworks.com
X-SMTP-PEER-INFO: albatross-ext.wise.edt.ericsson.se [194.237.142.116]
X-Orig: <ronyoung@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk


> (Hoping this gets through the MIP mailing list problems...)
> 
 => It didn't. I think this is definitely a MIP issue so we should 
 discuss it on the MIP list. You need to send your mail to
 mobile-ip@standards.nortelnetworks.com

> In draft-thomas-seamoby-rsvp-analysis-00.txt, some serious problems with MIP
> and RSVP signalling are identified. 
> 
 => Sure RSVP doesn't handle IP mobility.

> Specifically, when a handoff occurs,
> a round-trip BU must occur before the CN can issue an RSVP PATH message
> to assure QoS over the new route. Aggregated RSVP (see 
> draft-ietf-rsvp-aggr-02.txt)
> doesn't help, because the BU must still propogate to the CN for the CN to issue
> the PATH. All aggregation does is reduce the state in routers internal to the
> aggregation region, it does not reduce signalling requirements over 
> standard RSVP.
> 
 => Yes.

> There is a case where signalling can be optimized that is identified in
> draft-thomas-seamoby-rsvp-analysis-00.txt. This is the case where the movement
> of the mobile does not involve a change in CoA but rather is handled by 
> installing
> a new host route up to the join router between the old and new path. 
> Establishment
> of the new route is followed by a PATH message from the new join router
> to the MN, and a RESV from the MN back to the join router (pg. 10 in the 
> draft).
> 
> In draft-malinen-mobileip-regreg6-00.txt, a hierarchical MIP mechanism (called
> regional registrations) is defined that works very much like a host route. 
> Routers
> 
 => No it doesn't. The MN's CoA changes when the MN moves.

> between the new access router and the join router (called a crossover router
> in the draft) examine a BU routing option and the join router reconfigures its
> binding table to take account of the new route. The routers here are defined
> to be special regional aware routers, but the principle is the same.
> 
> Note that in HMIPv6 (draft-ietf-mobileip-hmipv6-01.txt), since the 
> intervening routers between the MAP and the mobile node never see the 
> topology change, the same severe performance penalties w.r.t. RSVP 
> signalling as in the standard
> MIPv6 case should occur.
> 
 => If you believe a crossover router solves the problem
 then you can see the MAP as the same thing. But the fact
 is neither a cross over router (in draft-malinen-...) nor HMIPv6
 solves that problem. A new PATH needs to be setup anyway
 for the outgoing traffic. The path between the MAP and the 
 CN is unchanged for incoming traffic.

> So, I'm wondering if the regional registration BU routing option could 
> serve as a trigger for redoing the RSVP signalling for QoS? Comments?
> 
 => I think the problem is much bigger than that. The issue of mobility 
 and QoS needs to be addressed in more detail. Michael's draft (I haven't
 finished it yet) is a very good start. We can't solve it for HMIP only, 
 the problem needs to be addressed for MIP in general.

 Regards,
 Hesham 



From owner-seamoby@diameter.org  Fri Mar  2 06:44:20 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25564
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 06:44:19 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f22BUO205000
	for seamoby-list; Fri, 2 Mar 2001 03:30:24 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f22BUAt04966
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 03:30:10 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 19:31:04 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 18:35:59 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229Yvw03003
	for seamoby-list; Fri, 2 Mar 2001 01:34:57 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229Ymt02991
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:34:49 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:25 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:08 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:37:27 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SMekh17187
	for seamoby-list; Wed, 28 Feb 2001 14:40:46 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SMego17182
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 14:40:42 -0800
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SLoGg00941
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 15:50:16 -0600 (CST)
Received: from daebh02nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T52022655faac12f25715a@davir04nok.americas.nokia.com>;
 Wed, 28 Feb 2001 15:49:45 -0600
Received: by daebh02nok with Internet Mail Service (5.5.2652.78)
	id <FWSX4951>; Wed, 28 Feb 2001 15:49:45 -0600
Message-ID: <7B5C0390ACE7D211BC9C0008C7EABA2B03213561@daeis07nok>
From: Basavaraj.Patil@nokia.com
To: Hesham.Soliman@era.ericsson.se, james.kempf@sun.com,
        mobile-ip@sunroof.eng.sun.com
Cc: claude.castelluccia@inrialpes.fr, seamoby@diameter.org, gdommety@cisco.com
Subject: RE: [seamoby] Is Mobile IP too slow or is Routing Table UpdateTo 
	 o slow? (was....)
Date: Wed, 28 Feb 2001 15:49:44 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


> 
> 
> 	Hi James
> 
> > Can you elaborate why you believe a design that 
> accommodates multiple levels of
> > hierarchy is a bad idea? The draft doesn't go into much 
> detail on this point.
> > 
> 	=> Well since the MIP list is broken we can take the discusion
> 	on the sister list :)

The new MIP list is located at : mobile-ip@sunroof.eng.sun.com

-Basavaraj


From owner-seamoby@diameter.org  Fri Mar  2 06:45:14 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25575
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 06:45:12 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f22BW3C05070
	for seamoby-list; Fri, 2 Mar 2001 03:32:03 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f22BVvt05055
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 03:31:58 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 19:33:25 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 19:12:21 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f223GgS23672
	for seamoby-list; Thu, 1 Mar 2001 19:16:42 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f223Gco23667
	for <seamoby@diameter.org>; Thu, 1 Mar 2001 19:16:39 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:17:57 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:41:50 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 06:22:20 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SLY7P16926
	for seamoby-list; Wed, 28 Feb 2001 13:34:07 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SLY1o16921
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 13:34:02 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA20117;
	Wed, 28 Feb 2001 12:43:23 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA08252;
	Wed, 28 Feb 2001 12:43:21 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id MAA02966;
	Wed, 28 Feb 2001 12:43:20 -0800 (PST)
Date: Wed, 28 Feb 2001 12:38:59 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: Re: [seamoby] Arch discussions in IETF
To: Phil_Neumiller@3Com.com
Cc: mobile-ip@marvin.corpeast.baynetworks.com, seamoby@diameter.org
In-Reply-To: "Your message with ID" <88256A01.006DF159.00@hqoutbound.ops.3com.com>
Message-ID: <Roam.SIMC.2.0.6.983392739.32498.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> We have said countless times that IETF does not define architecture.

Correct.

> However
> MIP did. Many of the problems people have with MIP are with its basic
> architecture, not the protocol.
> Why can't their be an architectural debate on MIP in the IETF (not protocol).
> There are boxes defined.  There is a CN, a MN, an HA, a set of routers. 
> Lets talk about how these
> need to play in today's modern residential and business deployments. 

As far as I'm concerned, MIP hasn't discussed architectures. If they had the
Mobile IP team would also be doing AAA, Qos And lots of other protocols. My
point all along is that piece parts are done within different WGs, and it is
the manufacturer's job to put the pieces together. 

My experience with this format has been most successful.

> Why do
> we always
> have to cater to cellular?  Why do the cellular guys get most the say? 

And where does this come from, may I ask? The only reason why you are probably
seeing more cellular stuff than anything else is because the cellular guys are
coming to the IETF and stating their requirements. Once we see people from
IEEE, Bluetooth and other relevant SDOs, I suspect you'll see more interest in
those areas as well.

However, as far as I know, the cellular guys do not have more say, they are
just the only ones present.

>  The
> Internet has
> new stuff like FTC, VoIP, SLP,  RSVP, diffserv, and new radio access
> technologies that
> can enable different types of mobility architectures.   Is an HA still a good
> idea in every scenario?  Why?  Can we talk about this?  If not why not? 
> Inquiring minds want to
> know.

and who exactly stated that one cannot talk about this??? Certainly not me. I
stated that arguments like "too slow" are hard to justify (unless you have
proof, and Andrew claimed 2 IETFs ago that MIP was as far as Cellular IP). If
there are problems with Home Agents, then the requirements should show this,
right?

> 
> Here is an example.  Why do I always need to use MIP?  Let's say I have a
> community of
> VPN's defined to interlink residences that interoperate with mobility (a
> bunch of families
> allows their mobiles to operate in each other's premises), i.e. mobile hosts
> are allowed
> to seamless travel within theses spaces but only in theses spaces (could be
> set up
> in hotel rooms, conferences, etc).  The COA changes but there is no HA.

ok, if that's what MM is, then great. 

> I have lots of scenarios like this.

and they aren't being ignored. Sure there are some Mobile IP folks that want
to protect their investment, but that is not the charter of this WG. We are
here to design a MM, but first need to identify the problem space. The -01 is
a really good start, and I suspect that -02 will be even better.

PatC


From owner-seamoby@diameter.org  Fri Mar  2 06:50:01 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25767
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 06:49:59 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f22BZiu05158
	for seamoby-list; Fri, 2 Mar 2001 03:35:44 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f22BZdt05151
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 03:35:39 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 19:37:09 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 18:34:15 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229YJ102958
	for seamoby-list; Fri, 2 Mar 2001 01:34:19 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229YBt02943
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:34:11 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:14 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:14 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:52:04 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SMhOT17207
	for seamoby-list; Wed, 28 Feb 2001 14:43:24 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SMhJo17202
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 14:43:20 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id GAA148480;
	Thu, 1 Mar 2001 06:43:49 +0900
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
 by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA03823;
 Wed, 28 Feb 2001 13:51:57 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA25077;
 Wed, 28 Feb 2001 13:51:51 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SLoMM01526
 for mobile-ip-dist; Wed, 28 Feb 2001 13:50:22 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SLo7E01503
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 13:50:08 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA19101
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 13:50:06 -0800 (PST)
From: Basavaraj.Patil@nokia.com
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA10922
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:49:45 -0700 (MST)
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
 by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SLnjg00849
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:49:45 -0600 (CST)
Received: from daebh02nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T52022655faac12f25715a@davir04nok.americas.nokia.com>;
 Wed, 28 Feb 2001 15:49:45 -0600
Received: by daebh02nok with Internet Mail Service (5.5.2652.78)
 id <FWSX4951>; Wed, 28 Feb 2001 15:49:45 -0600
Message-ID: <7B5C0390ACE7D211BC9C0008C7EABA2B03213561@daeis07nok>
To: Hesham.Soliman@era.ericsson.se, james.kempf@sun.com,
        mobile-ip@sunroof.eng.sun.com
Cc: claude.castelluccia@inrialpes.fr, seamoby@diameter.org, gdommety@cisco.com
Subject: RE: [seamoby] Is Mobile IP too slow or is Routing Table UpdateTo 
  o slow? (was....)
Date: Wed, 28 Feb 2001 15:49:44 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
 charset="iso-8859-1"
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk

> 
> 
>  Hi James
> 
> > Can you elaborate why you believe a design that 
> accommodates multiple levels of
> > hierarchy is a bad idea? The draft doesn't go into much 
> detail on this point.
> > 
>  => Well since the MIP list is broken we can take the discusion
>  on the sister list :)

The new MIP list is located at : mobile-ip@sunroof.eng.sun.com

-Basavaraj


From owner-seamoby@diameter.org  Fri Mar  2 06:50:23 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25782
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 06:50:19 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f22BbqT05190
	for seamoby-list; Fri, 2 Mar 2001 03:37:52 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f22Bbit05185
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 03:37:44 -0800
Received: from esvir06nok.ntc.nokia.com (esvir06nokt.ntc.nokia.com [172.21.143.38])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f22Ajtf21969
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 12:45:55 +0200 (EET)
Received: from esebh01nok.ntc.nokia.com (unverified) by esvir06nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T520bcac000ac158f26129@esvir06nok.ntc.nokia.com> for <seamoby@diameter.org>;
 Fri, 2 Mar 2001 12:45:55 +0200
Received: by esebh01nok.ntc.nokia.com with Internet Mail Service (5.5.2652.78)
	id <GCF7MM3V>; Fri, 2 Mar 2001 12:45:54 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680AB21@eseis04nok>
From: john.loughney@nokia.com
To: seamoby@diameter.org
Subject: [seamoby] A 'Psuedo' MM Problem Statement draft
Date: Fri, 2 Mar 2001 12:45:46 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi all,

All of the various mails back and forth have actually been very productive
(for me).  I think a good number of points.  I've attempted to summarize
some of the better points bellow.  This is a psuedo-draft - meaning that if
I've made any sense in my points below, I shall try to insert the sensible
words into the next revision of the MM problem draft.  I'd like to thank all
of the persons whose email messages I've plagerized.

John

=================================

Why Micromobility

The Internet scales well with clients, servers, and peers using the same IP
address while connected to the Internet.   The Internet works by addressing
devices at the edge of the network, not in the middle of the network.
Mobile clients, servers, and peers should operate the same way.  What is the
best way the Internet can support mobile clients, servers, and peers while
maintaining the same scalability allowed by the current internet
architecture?

Capacity: A Sea of Mobile Nodes 

The Internet is being more and more wireless - or to put it another way,
users should be able to connect to the Internet via fixed lines or
wirelessly.  More wireless nodes, moving about will create more demand for
capacity.

One method to achieve higher capacity and/or higher access speeds in a
wireless network is through the reduction of cell sizes (micro-cells,
pico-cells, nano-cells ...). One can imagine a scenario where each office
has its series of base stations (access points), offering tens to hundreds
of megabits per second of wireless access. These type of pico-cellular
environments must ultimately compete with wireline LAN service quality,
costs, security, and plug-and-play scalability.

Having smaller cells with higher access speeds also means higher
requirements from the mobility management protocols. This naturally due to
the fact that as cells become smaller (i.e. access point density increases),
handover rates and thus also the associated signaling loads will increase.
The mobility management protocol must allow seamless mobility, i.e. the
ability of the network to support fast handoff (low delay) between base
stations, with minimum or zero packet loss (smooth handoff).  In this
setting, it is important to minimize the associated signaling in order to
ensure that the signaling does not interfer with user data.

What About Mobile IP

Mobile IP mainly solves the macro-mobility management problem. It has been
widely stated (even in RFC 2005) that Mobile IP is not a suitable protocol
to handle micro-mobility management. The inefficiency of Mobile IP in
micro-cell environments can be attributable to the fact that Mobile IP is an
end-to-end delivery protocol, where only the CN and HA adjust to the
movement of a MN. This involves signaling only between endpoints and results
in slow adjustments to the movement of a MN. Thus Mobile IP works best when
the MN does not change its link-layer connections very often - which is not
true for micro-environments. However, in response to the desire to push
Mobile IP down to the access, there are various research activities that
investigate the possibility of enhancing the Mobile IP functionality to
support micro-mobility.

In the words of the tallest MIP designer:

It is easy to understand "well, we can make Mobile IP do that"... And I
don't think it's necessarily an unfortunate thing that people are thinking
about such things.  But, on the other hand, it's important to avoid protocol
bloat and unnecessary requirements.  To me that just means that good
engineering is required.

Philosophic Conundrum: Hierarchy or end-to-end?

Mobile IP is a known protocol.  It has been implemented and seeing
deployments.  Certain optimizations are being developed to insure
performance and scalability.  There are a number of papers showing the
applicability of Mobile IP to a range of applications.

However, fixing the transport path for a MN at various points only
introduces more opportunity for failure while possibly improving handover
speed but not guaranteeing an improvement in handover.  Peer to Peer
addressability is the only scalable technique for large scale mobility.
Addressing various middleman routers increases the latency because optimal
paths may not be used and decreases reliability because a stateful single
point of failure is introduced into the network.  If any hierarchy is needed
then it should only be introduced temporarily for the duration of a handoff
between ALn and ALn+1 where the MN IP address changes.  If the MN IP address
does not change then hierarchy is not needed.  Maintaining network
intelligence outside of handover window introduces unnecessary complexity in
the routing path and unreliability.

A Sea of Protocols & a Head full of Aches

All of this may be solvable, if this was the only problem.  Howover, routing
is seldom an application.  A user may be using connection-oriented protocols
on top of IP, connection less protocols on top of IP, QoS protocols,
security protocols, AAA protocols and so on.  As most of these protocols
have been designed with the end-to-end concept in mind, mobility and
frequent routable IP address changes may inflict much extra signaling and a
greater probability that the user may not get the expected results

Possible Way Forward

One question is whether another routing protocol for mobility is required.
Presently we have the MIP and the Manet routing approaches (Tunneling vs.
host based routing).  It may be so that a new routing protocol is not
needed, but there may be work needed to support _signaling_ a router that it
needs to change how a subnet is reachable. It is quite possible that the
heavy lifting can already be done by current protocols, and that all we need
is the ability to trigger them to happen. You might call that a "routing
protocol" too, but it ought not evoke the fear and loathing that postulating
a Routing Protocol should.

Bottom Line

SeaMoby should study solutions and determine if a protocol that enables
local routability with better latency characteristics, in addition to the
global association managed by Mobile IP is the proper approach to solving
the problem.


From owner-seamoby@diameter.org  Fri Mar  2 06:50:30 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25793
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 06:50:26 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f22BTS004925
	for seamoby-list; Fri, 2 Mar 2001 03:29:28 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f22BTOt04920
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 03:29:24 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 19:31:00 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Fri, 2 Mar 2001 18:30:30 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f229ZFT03034
	for seamoby-list; Fri, 2 Mar 2001 01:35:15 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f229Z2t03017
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 01:35:03 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 11:18:22 +0900
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 10:42:06 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 1 Mar 2001 07:59:01 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id f1SN5nw17289
	for seamoby-list; Wed, 28 Feb 2001 15:05:49 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mail.korea.ac.kr (korea.ac.kr [163.152.1.251])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id f1SN5ko17284
	for <seamoby@diameter.org>; Wed, 28 Feb 2001 15:05:46 -0800
Received: from smart (smtp.korea.ac.kr [163.152.1.10])
	by mail.korea.ac.kr (8.8.8H1/8.8.8) with SMTP id HAA63294;
	Thu, 1 Mar 2001 07:06:26 +0900
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
 by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA00335;
 Wed, 28 Feb 2001 14:14:52 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
 by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA25211;
 Wed, 28 Feb 2001 14:14:41 -0800 (PST)
Received: (from majordomo@localhost)
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) id f1SMD6j01965
 for mobile-ip-dist; Wed, 28 Feb 2001 14:13:06 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
 by sunroof.eng.sun.com (8.11.3+Sun/8.11.3) with ESMTP id f1SMCvE01955
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
 by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA00357
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 14:12:57 -0800 (PST)
From: Phil_Neumiller@3Com.com
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
 by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA23795
 for <mobile-ip@sunroof.eng.sun.com>; Wed, 28 Feb 2001 15:12:56 -0700 (MST)
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
 by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f1SMBSo14321;
 Wed, 28 Feb 2001 14:11:28 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
 by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f1SMCnX06019;
 Wed, 28 Feb 2001 14:12:49 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A01.007A28B7 ; Wed, 28 Feb 2001 14:14:18 -0800
X-Lotus-FromDomain: 3COM
To: mobile-ip@sunroof.eng.sun.com
cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Message-ID: <88256A01.007A25AA.00@hqoutbound.ops.3com.com>
Date: Wed, 28 Feb 2001 16:11:37 -0600
Subject: RE: [seamoby] Arch discussions in IETF
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-seamoby@diameter.org
Precedence: bulk





Hi Raj,

>Phil,
>
>I do not see anyone saying that Mobile IP is the only solution for all
>scenarios that require mobility. I am sure there are many scenarios
>that Mobile IP may or may not be the most optimal solution. If Mobile
>IP is unable to work as well as anything else you may have in mind
>for specific scenarios, then why deploy Mobile IP in such scenarios?

Then where might these other solutions be standardized in the IETF?
Would this fall under the classification of micro-mobility even though
the "so-called" COA or routing prefix does indeed change?  I guess what
I am getting at is there may be cases of infra-structure-less mobility
where the COA changes but there is no HA.  Would this be micro or
macro mobility?

>Can you be more specific on the kind of environments and requirements
>that these environments have that would make it impossible for Mobile
>IP to work in.

Sure.  Specifically, I am very interested in portable devices that will
find there way into homes.  Wireless appliances, MP3 players, digital
radios, digital security devices, gaming units, VoIP devices, etc.  I
am also interested in these types of devices that may be used in small
to medium business that may not have large infrastructures in place.

Thank you,

Phil Neumiller


From owner-seamoby@diameter.org  Fri Mar  2 09:28:46 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA00383
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 09:28:45 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22CkQH09933
	for seamoby-list; Fri, 2 Mar 2001 04:46:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22CkOT09928
	for <seamoby@cdma-2000.org>; Fri, 2 Mar 2001 04:46:24 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA23944
	for <seamoby@cdma-2000.org>; Fri, 2 Mar 2001 04:54:17 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA18959
	for <seamoby@cdma-2000.org>; Fri, 2 Mar 2001 04:54:17 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id EAA05964
	for <seamoby@cdma-2000.org>; Fri, 2 Mar 2001 04:54:16 -0800 (PST)
Date: Fri, 2 Mar 2001 04:49:48 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] What a morning (or is it night?!?)
To: seamoby@cdma-2000.org
Message-ID: <Roam.SIMC.2.0.6.983537388.4725.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

Well, after waking up early to get an early start on some coding, I found the
list to be.... well.... screwed up. I am not quite sure what's going on, but
it seems there is a site m018.com that is forwarding old e-mail from the list,
back to the list. I am not sure if this is an intentional attack or not.

So, I have just upgraded sendmail to the latest version, and added some
anti-spamming configuration to disallow anything from that site. Therefore, if
your traffic traverses from that site... well you are probably not reading
this e-mail, nor will you be able to send.

If anyone has *any* ideas on how to get this fixed up, I would appreciate any
pointers.

(btw, all of my other lists on my box such as L2TP, Cellular and others are
NOT being subjected to this problem, so it isn't a local problem....)

And now onto coding.....

PatC



From owner-seamoby@diameter.org  Fri Mar  2 11:53:07 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA06497
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 11:53:06 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22F6MA11040
	for seamoby-list; Fri, 2 Mar 2001 07:06:22 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from idcpa4.pa.interdigital.com (idcmail.interdigital.com [12.32.197.142])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22F6GT11035
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 07:06:16 -0800
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <DLAL4KB4>; Fri, 2 Mar 2001 10:12:26 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D01F1F748@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        seamoby_context@marvin.corpeast.baynetworks.com,
        "'seamoby'"
	 <seamoby@diameter.org>
Subject: [seamoby] RE: Context Transfer Design Team
Date: Fri, 2 Mar 2001 10:12:18 -0500 
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Gary,

This is short noice for me. I will need time to prepare. Could you please
postpone it till Monday March, 12.

Thanks,

Sharif

-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Friday, March 02, 2001 10:10 AM
To: seamoby_context@marvin.corpeast.baynetworks.com; 'seamoby'
Subject: Context Transfer Design Team
Importance: High
Sensitivity: Confidential


There seems to be a smattering of consensus that we continue with the
design teams to develop the requirements draft. 

I realize this is very short notice, but are people up to a conference call
this coming Monday (March 5) at 11am?

If I get at least 4 responses, I will go ahead and schedule a call, but
I need feedback by 12 today, EST.

If not, I will set something up for the following Monday.

Cheers,
Gary

==========================================================================

I find that the harder I work, the more luck I seem to have.
- Thomas Jefferson

The contents of this email are Nortel Networks Confidential



From owner-seamoby@diameter.org  Fri Mar  2 12:21:14 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA07736
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 12:21:13 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22FpVE11777
	for seamoby-list; Fri, 2 Mar 2001 07:51:31 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from c007.snv.cp.net (c007-h000.c007.snv.cp.net [209.228.33.206])
	by charizard.diameter.org (8.11.3/8.11.3) with SMTP id f22FpQT11772
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 07:51:26 -0800
Received: (cpmta 25346 invoked from network); 2 Mar 2001 07:59:10 -0800
Received: from dsl-64-193-0-129.telocity.com (HELO PhilsSony) (64.193.0.129)
  by smtp.telocity.com (209.228.33.206) with SMTP; 2 Mar 2001 07:59:10 -0800
X-Sent: 2 Mar 2001 15:59:10 GMT
Message-ID: <006301c0a331$eb458260$6501a8c0@mw.3com.com>
From: "Phillip Neumiller" <neumiller@telocity.com>
To: <john.loughney@nokia.com>, <seamoby@diameter.org>
References: <01D91AFB08B6D211BFD00008C7EABAE10680AB21@eseis04nok>
Subject: Re: [seamoby] A 'Psuedo' MM Problem Statement draft
Date: Fri, 2 Mar 2001 10:00:35 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hats off John very nice summary.

-pdn



From owner-seamoby@diameter.org  Fri Mar  2 12:21:50 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA07768
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 12:21:50 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22FFsY11137
	for seamoby-list; Fri, 2 Mar 2001 07:15:54 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22FFqT11132
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 07:15:52 -0800
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Fri, 2 Mar 2001 10:09:37 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <FZV98T3M>; Fri, 2 Mar 2001 10:09:40 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D30@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'seamoby_context'" <seamoby_context@marvin.baynetworks.com>,
        "'seamoby'" <seamoby@diameter.org>
Subject: [seamoby] Context Transfer Design Team
Date: Fri, 2 Mar 2001 10:09:36 -0500
Importance: high
X-Priority: 1
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

There seems to be a smattering of consensus that we continue with the
design teams to develop the requirements draft. 

I realize this is very short notice, but are people up to a conference call
this coming Monday (March 5) at 11am?

If I get at least 4 responses, I will go ahead and schedule a call, but
I need feedback by 12 today, EST.

If not, I will set something up for the following Monday.

Cheers,
Gary

==========================================================================

I find that the harder I work, the more luck I seem to have.
- Thomas Jefferson

The contents of this email are Nortel Networks Confidential




From owner-seamoby@diameter.org  Fri Mar  2 12:30:28 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA08149
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 12:30:26 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22GR8912351
	for seamoby-list; Fri, 2 Mar 2001 08:27:08 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22GPwT12345
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 08:25:58 -0800
Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.130])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id IAA25602;
	Fri, 2 Mar 2001 08:34:01 -0800 (PST)
Received: from mailman.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-1.cisco.com (8.10.1/8.10.1) with ESMTP id f22GXsF07045;
	Fri, 2 Mar 2001 08:33:54 -0800 (PST)
Received: from cisco.com (ssh-rtp1.cisco.com [161.44.11.166]) by mailman.cisco.com (8.9.3/CISCO.SERVER.1.2) with ESMTP id IAA08141; Fri, 2 Mar 2001 08:33:43 -0800 (PST)
Message-ID: <3A9FCB3F.73F27EFA@cisco.com>
Date: Fri, 02 Mar 2001 10:33:03 -0600
From: Peter Lei <PeterLei@cisco.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: john.loughney@nokia.com
CC: seamoby@diameter.org
Subject: Re: [seamoby] A 'Psuedo' MM Problem Statement draft
References: <01D91AFB08B6D211BFD00008C7EABAE10680AB21@eseis04nok>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

Nice summary...

> Mobile IP mainly solves the macro-mobility management problem. It has been
> widely stated (even in RFC 2005) that Mobile IP is not a suitable protocol
> to handle micro-mobility management. The inefficiency of Mobile IP in
> micro-cell environments can be attributable to the fact that Mobile IP is an
> end-to-end delivery protocol, where only the CN and HA adjust to the
                                      ^^^^
> movement of a MN. 

This doesn't read clearly/correctly to me... I think this should say
"where the HA and/or CN must adjust to each movement of a MN" (via
end-to-end signaling such as binding updates...).

Thanks!
--peter

> This involves signaling only between endpoints and results
> in slow adjustments to the movement of a MN. Thus Mobile IP works best when
> the MN does not change its link-layer connections very often - which is not
> true for micro-environments. However, in response to the desire to push
> Mobile IP down to the access, there are various research activities that
> investigate the possibility of enhancing the Mobile IP functionality to
> support micro-mobility.


From owner-seamoby@diameter.org  Fri Mar  2 12:37:18 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA08616
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 12:37:17 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22GZ5S12524
	for seamoby-list; Fri, 2 Mar 2001 08:35:05 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22GYtT12517
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 08:34:55 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id IAA18312;
	Fri, 2 Mar 2001 08:40:55 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f22GerM12903;
	Fri, 2 Mar 2001 08:40:53 -0800
X-mProtect:  Fri, 2 Mar 2001 08:40:53 -0800 Nokia Silicon Valley Messaging Protection
Received: from tpagtzis.iprg.nokia.com (205.226.2.115, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdbkrJCU; Fri, 02 Mar 2001 08:40:42 PST
Message-ID: <3A9FCD0C.AC652441@iprg.nokia.com>
Date: Fri, 02 Mar 2001 08:40:44 -0800
From: Theo Pagtzis <tpagtzis@iprg.nokia.com>
Reply-To: tpagtzis@iprg.nokia.com
Organization: UCL/NOKIA
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1-STABLE i386)
X-Accept-Language: el, en
MIME-Version: 1.0
To: Gary Kenward <gkenward@nortelnetworks.com>, seamoby@diameter.org
CC: seamoby_context@marvin.baynetworks.com
Subject: [seamoby] Re: Context Transfer Design Team
References: <13E2EF604DE5D111B2E50000F80824E8057A8D30@zwdld001.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Gary Kenward wrote:

> There seems to be a smattering of consensus that we continue with the
> design teams to develop the requirements draft.
>
> I realize this is very short notice, but are people up to a conference call
> this coming Monday (March 5) at 11am?
>
> If I get at least 4 responses, I will go ahead and schedule a call, but
> I need feedback by 12 today, EST.
>
> If not, I will set something up for the following Monday.
>
> Cheers,
> Gary
>
> ==========================================================================
>
> I find that the harder I work, the more luck I seem to have.
> - Thomas Jefferson
>
> The contents of this email are Nortel Networks Confidential

Hi Gary,

   my deepest apologies for not responding any sooner. I have been trying to
watch closely the email discussion as well as try to aclimatize myself with
the Nokia environment (intern) coming from UCL London.


I have read at least three times the draft requirement and I am a proponent of
the idea that it need a lot more work. I have a different view about certain
things and for that I will be sending you the suggestions that I had in mind
but kept postponing sending them to the group and discussing further.

I think that jumping out to get a couple of new drafts just to capture the
attention of people is something we would need to refrain from if we would
like to produce any results that make sense as a good design not as patchwork
design that tries to capture what the others forgot in the way.

So here are my thoughts. If you feel that they are worth contributed to the
problem statement I would be more than happy to expand and definetely
participate in the draft requirements and problem definition.

Also I am a bit confused with the mailing list. What are we posting on
seamoby_context? seamoby? I see email all over the place here...

So here they are:


Defining Seamless Mobility


The term of seamlessness in the greater context of mobility maps different
semantics according to different
individual mobility contexts classes. These context classes may range between:

security
header compression
Accounting and billing
service provisioning guarantees
session management
tcp-friendliness
roaming
<others..>

In the majority of the above subcontexts seamlessness may distinguish between
subjective/perceived and
objective seamlessness.

The reason for such separation of concerns over the semantics of seamlessness
is apparent as well as two
fold: the degree of seamlessness may be tracked by humans
(subjective/perceived) or automata (objective).

In the light of such semantic separation, seamlessness may be defined as the
sustainment of quantifiable or non
quantifiable metrics over each individual subcontext according

a) to some perceivably acceptable boundaries (upper and lower). A boundary may
be considered acceptable
according to some specific context policy with respect to seamlessness

b) to some objectively qualitative metrics that are bound by specific upper
and lower threshold,  This class of
seamless semantics may at worst be allowed to degrade to perceivably
acceptable boundaries of case (a).

With respect to individual subcontexts seamlessness may be polymorphically
overloaded to denote in the
subcontext of :

1) Security : the sustainment of secure transmission between two entities. In
the case of perceivably acceptable
boundaries, secure transmission may be defined the dispatch of securely
guarded flows according to some
perceived security requirements, such as at least one symmetric/asymmetric
ciphering algorithm within a set of
available one. In the case of objectively acceptable boundaries the
sustainment requirement will need to comply
to specific number of bit-key, availability of PFS, delay bounds on SA
setup/teardown, etc.

2) Header Compression: sustaining compression of header state in IP flows.
Differentiation between levels of
compression (potentially more than 2) may provide a clear separation between
perceived compression (marked
increase on the throuput or decrease of loss rates) and objective compression
(higher density levels in the
compression hierarchy).

3) Accounting and billing: here notion of perceived sustainment can be
identified as provisional/estimate (much
like electricity) metrics over network usage. On the contrary the notion of
objective sustainment of the funtions
may transcend to objective and atomically accurate accounting and billing that
can provide granularity to the last
bit of information.

4) service provisioning guarrantees: sustainment of perceived quality. The
sustainment "metric" upgrade to
objective quality of the network flow depending on the level of granularity
quality is guaranteed upon (bit, byte,
packet, flow, flow-agregate, session, utility).

5) session management: sustaining of is perceived to be the session for an
individual MN. That implies that
certain flows-members of a session may need to be degraded/dropped if their
subjective imprortance is lower
(what people would not consider as their session flow representations (active
ones). Alternatevery the
sustainement metric may transcent in more atomic approaches that consider the
entire session as a critical
sustainment goal (eg. remote cruise control flows of a remotely piloted
vehicle).

6) tcp-friendlyness: the degree of sustainment of tcp-friendlyness metrics in
domain. Loose sustainment of
tcp-friendlyness may be considere as perceived seamlessness, while tight
tcp-friendlyness control on udp flows
(eg CBQ penalties on top of delay) would map over objective tcp-friendly
seamlessness.


Furthermore, the architectural diagram does not provide any rationale about
potential such architectural
diagrams. I can imaging meshing between ARs and ANGs for AD1, however in the
second case AD2, why could
one possibly want to get two ARs on the SAME AP... Juniper these days amongst
others ensure that you need a lot
more AP/BS connected to a single AR before the AR can start feeling that it
doesn't go to sleep. What are the
diagrams try to convey...? a topology?...a realistic one? all potential
topologies of interest? ...a couple that croped
in mind and can be expanded?

The doc defines that more than 1 microflow may be supporting a higher layer
application. Do you intend to go all
the way to the app layer or would be will to stop at 3.5 (say RTP). I do not
see that the definition proposes
optional support or propagation of state all the way up to the app layer.

As a problem statement I would like to see something along the lines of :


Individual microflows may be identified under some seamoby protocol
interaction. Under such seamoby
interactions higher layer above transport, such as RTP or application, may be
provided with the required
SeaMoby semantics (contextual or not) as an added value option,that will
enable apps to support sustainment
BUT MORE IMPORTANT  DECISION CONTROL of seamlessness at the application layer.



The "implicit" of the document declaration that seamless handover would
preserve higher layer context is not at
all clear for a problem statement.

"...degradation of the context for even one of a set of
   co-dependent microflows may have a disproportionate impact on the
   function or performance of the application."

So how is the problem formulated according to that ? I do not see any
formulation from that inference.

I have been thinking about the terminology adopted here. I find a difficulty
digesting the term Feature. Of course
it may mean anything..but I think that the granularity semantics for that
terms are TOO THIN. I would expect to
hear the term feature about a characteristic, not an entire class of
characteristics.

I have been thinking about the terms again and again and believe that we would
need to revisit the terms here
since they are going to be used heavily. My own suggestion in the
term-hierarchy about context transfer is the
following:



Seamoby is called to deal with a set of context classes. Some of them have
been mentioned already above.
Each microflow is being tracked/characterized by the instantiation of context
objects from their respective
context classes. In particular the CT-objects track
Each of these context classes may identify a context signature. The
CT-signature comprizes of the tuple
(capability,state)
Context Capapbility:


furthermore what is the difference between feature state and feature
context....if that is one and the same then
do we need both?


Regs.


Theo

UCL/Mobile Systems group



From owner-seamoby@diameter.org  Fri Mar  2 12:47:12 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09113
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 12:47:11 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22GemG12649
	for seamoby-list; Fri, 2 Mar 2001 08:40:48 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22GegT12643
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 08:40:43 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id IAA19027;
	Fri, 2 Mar 2001 08:48:28 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f22GmRm04126;
	Fri, 2 Mar 2001 08:48:27 -0800
X-mProtect:  Fri, 2 Mar 2001 08:48:27 -0800 Nokia Silicon Valley Messaging Protection
Received: from tpagtzis.iprg.nokia.com (205.226.2.115, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpd5LkTvV; Fri, 02 Mar 2001 08:48:08 PST
Message-ID: <3A9FCEC9.2350C77@iprg.nokia.com>
Date: Fri, 02 Mar 2001 08:48:09 -0800
From: Theo Pagtzis <tpagtzis@iprg.nokia.com>
Reply-To: tpagtzis@iprg.nokia.com
Organization: UCL/NOKIA
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1-STABLE i386)
X-Accept-Language: el, en
MIME-Version: 1.0
To: Gary Kenward <gkenward@nortelnetworks.com>
CC: "'seamoby_context'" <seamoby_context@marvin.baynetworks.com>,
        "'seamoby'" <seamoby@diameter.org>
Subject: Re: [seamoby] Context Transfer Design Team
References: <13E2EF604DE5D111B2E50000F80824E8057A8D30@zwdld001.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Gary Kenward wrote:

> There seems to be a smattering of consensus that we continue with the
> design teams to develop the requirements draft.
>
> I realize this is very short notice, but are people up to a conference call
> this coming Monday (March 5) at 11am?
>
> If I get at least 4 responses, I will go ahead and schedule a call, but
> I need feedback by 12 today, EST.
>
> If not, I will set something up for the following Monday.
>
> Cheers,
> Gary
>
> ==========================================================================
>
> I find that the harder I work, the more luck I seem to have.
> - Thomas Jefferson
>
> The contents of this email are Nortel Networks Confidential

I would further like to propose that the context tranfer design team promotes
the requirements draft to a design draft. This way

1) everybody that would like to propose something new it would be considered
by the totality of the team (much like the fast handoffs v6 /v4 design team)

2) the design would go through a sanity check by at least one peer entity
(sound)
3) faster acceptance convergence
4) faster results
5) long lasting
6) real results instead of changing terminology to the same principle and then
preaching that it is different by 0.0000001 % such that it constitutes a
reason to exist on its own (despite the fact that 99% of the idea is similar
to the rest of the design team participants)

What does the team think ?


Theo

UCL/ Mobile systems group



From owner-seamoby@diameter.org  Fri Mar  2 13:01:27 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA09768
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 13:01:26 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22GYcO12512
	for seamoby-list; Fri, 2 Mar 2001 08:34:38 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22GYPT12504
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 08:34:25 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id IAA18468;
	Fri, 2 Mar 2001 08:42:03 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f22Gg1q15842;
	Fri, 2 Mar 2001 08:42:01 -0800
X-mProtect:  Fri, 2 Mar 2001 08:42:01 -0800 Nokia Silicon Valley Messaging Protection
Received: from tpagtzis.iprg.nokia.com (205.226.2.115, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpd3IZGJc; Fri, 02 Mar 2001 08:41:33 PST
Message-ID: <3A9FCD3E.D15EAB7C@iprg.nokia.com>
Date: Fri, 02 Mar 2001 08:41:34 -0800
From: Theo Pagtzis <tpagtzis@iprg.nokia.com>
Reply-To: tpagtzis@iprg.nokia.com
Organization: UCL/NOKIA
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1-STABLE i386)
X-Accept-Language: el, en
MIME-Version: 1.0
To: Gary Kenward <gkenward@nortelnetworks.com>
CC: "'seamoby_context'" <seamoby_context@marvin.baynetworks.com>,
        "'seamoby'" <seamoby@diameter.org>
Subject: Re: [seamoby] Context Transfer Design Team
References: <13E2EF604DE5D111B2E50000F80824E8057A8D30@zwdld001.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Gary Kenward wrote:

> There seems to be a smattering of consensus that we continue with the
> design teams to develop the requirements draft.
>
> I realize this is very short notice, but are people up to a conference call
> this coming Monday (March 5) at 11am?
>
> If I get at least 4 responses, I will go ahead and schedule a call, but
> I need feedback by 12 today, EST.
>
> If not, I will set something up for the following Monday.
>
> Cheers,
> Gary
>
> ==========================================================================
>
> I find that the harder I work, the more luck I seem to have.
> - Thomas Jefferson
>
> The contents of this email are Nortel Networks Confidential

I forgot to say that I would be more than happy to participate in this
conference call please let me know of the details..


Theo



From owner-seamoby@diameter.org  Fri Mar  2 14:33:13 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA14475
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 14:33:12 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22HWDF13527
	for seamoby-list; Fri, 2 Mar 2001 09:32:13 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from hotmail.com (f60.law7.hotmail.com [216.33.237.60])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22HW9T13521
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 09:32:09 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 2 Mar 2001 09:39:59 -0800
Received: from 63.78.179.5 by lw7fd.law7.hotmail.msn.com with HTTP;	Fri, 02 Mar 2001 17:39:58 GMT
X-Originating-IP: [63.78.179.5]
From: "Hemant Chaskar" <hchaskar@hotmail.com>
To: mobile-ip@sunroof.eng.sun.com
Cc: seamoby@diameter.org, mobile-ip@marvin.corpeast.baynetworks.com,
        hemant.chaskar@nokia.com
Subject: [seamoby] QoS and Mobile IP
Date: Fri, 02 Mar 2001 17:39:58 
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F60ORiI9bWLJBO9E0l000003afb@hotmail.com>
X-OriginalArrivalTime: 02 Mar 2001 17:39:59.0224 (UTC) FILETIME=[CD7E2F80:01C0A33F]
Sender: owner-seamoby@diameter.org
Precedence: bulk




>From: Michael Thomas <mat@cisco.com>

>I really don't even know where to begin. It seems
>that your claim is that RSVP's receiver oriented
>PATH/RESV is either flawed, or should have a mode
>which allows a single pass. I believe this leads
>to overbooking for multicast since you don't get
>to do flow merging properly and a host of other
>reasons that I don't purport to understand well.

=> Despite a host of other reasons, if RSVP's OPWA has
performance inefficiencies in mobile environment, it cannot
be pushed to work with Mobile IP.

=> The solution of enclosing QoS Object in hop-by-hop
extension header, preferably with binding messages, performs
fast reservation on forward path. This will be important in
many unicast applications such as VoIP that cannot tolerate
interruption in quality, due to RSVP's round trip latency in
programming QoS on the new path, on every hanover.

=> Speaking of multicast. The question that comes to my mind is
whether it is necessary to send binding messages from MN if it
is receiving multicast traffic. If MN changes CoA, it can simply
use IGMP to register to multicast at that location. Conclusion:
Multicast and Unicast can be studied in different perspectives.

Also, state merging is an issue only when you use IntServ. In
DiffServ and MPLS cases there is no state to merge!

=> Overall, solution of including QoS object in hop-by-hop extension
header and performing forward reservations has its own merits. It
blends in well with mobility signals, works with micro-mobility
techniques and has performance edge over RSVP (at least in unicast
scenarios).

==>Hemant

>
>What I really don't understand is why MIP would be
>the right place to solve this problem. If it has
>merit, the RSVP folks seems like a much more
>appropriate set of people to entertain such a
>proposal. I suspect that they'd be able to supply
>a lot more reasons why they designed RSVP the way
>they did. Suggesting that mobileip is a breed
>apart that requires its own QoS mechanisms sounds
>just as wrong headed as RSVP folks designing their
>own mobility protocol.
>
>		Mike
>
>Hemant.Chaskar@nokia.com writes:
>  > Yes, it goes end to end. But there is a basic difference illustrated
>  > by following example. If we look at the latency between time end nodes
>  > are ready to use new CoA and the time QoS forwarding treatment is 
>programmed
>  >
>  > over the new path, it can be seen that RSVP takes one end-to-end round 
>trip
>  > time
>  > between these two events. On the other hand, including QoS object with
>  > binding
>  > messages performs QoS programming before the nodes release packets 
>using
>  > new CoA. This is shown by following illustration.
>  >
>  > Suppose MN is currently at CoA1. Consider data traffic from the
>  > CN towards the MN (downlink direction).
>  >
>  >    o MN moves to CoA2.
>  >
>  >    o MN sends BU from CoA2.
>  >
>  >    ----[One way end-to-end delay]----
>  >
>  >    o BU reaches CN. CN sends BA to MN at CoA2.
>  >
>  >    In RSVP, CN sends PATH message to MN at CoA2.
>  >
>  >    In our approach, QoS OBJECT OPTION for downlink packet stream(s)
>  >    is included in HOP-by-HOP OPTIONS EXTENSION HEADER with the BA.
>  >
>  >    o CN may start sending MN's packets to CoA2. These packets
>  >    contain CoA2 as destination address.
>  >
>  >    **In RSVP approach, they are not identified by existing
>  >    reservations for MN's sessions. This is because, RSVP session is
>  >    primarily identified by destination address which now has changed
>  >    from CoA1 to CoA2. Hence, these packets will get default
>  >    forwarding treatment.**
>  >
>  >    **In our approach, the packet carrying QoS information about these
>  >    packets precedes these packets, and hence, they can get proper
>  >    forwarding treatment.**
>  >
>  >    ----[One way end-to-end delay]----
>  >
>  >    o BA reaches MN at CoA2. In RSVP approach, PATH message reaches
>  >    MN at CoA2.
>  >
>  >    o In RSVP approach, MN sends RESV to CN.
>  >
>  >    ----[One way end-to-end delay]----
>  >
>  >    o In RSVP approach, RESV reaches CN.
>  >
>  >    **In RSVP approach, it is at this time that the proper QoS
>  >    forwarding treatment is programmed at the intermediate network
>  >    domains for packets destined to CoA2.**
>  >
>  >
>  > Hemant
>  >
>  > -----Original Message-----
>  > From: Michael Thomas [mailto:mat@cisco.com]
>  > Sent: 01. March 2001 13:33
>  > To: Hemant Chaskar
>  > Cc: Hesham.Soliman@era.ericsson.se; james.kempf@sun.com;
>  > mobile-ip@marvin.corpeast.baynetworks.com; seamoby@diameter.org
>  > Subject: RE: [seamoby] Hierarchical MIP, QoS, and Handoff
>  >
>  >
>  >
>  > I don't see how this fundamentally changes
>  > anything that James brought up. It still has to go
>  > end to end, and it's still touching every router
>  > in between MN and CN.
>  >
>  > What I do see is a lot of reinvention of RSVP
>  > Rspec and Tspec's for no known reason.  The only
>  > thing I can see of possible value is the ability
>  > to piggyback the QoS update with the BU, but even
>  > if this is the sole goal -- and that it's a worthy
>  > goal which is not at all apparent to me -- I
>  > imagine that there are better ways of doing this
>  > with out reinventing RSVP: like, maybe,
>  > piggybacking the BU on the PATH, or some such.
>  >
>  > 	     Mike
>  >
>  >
>  > Hemant Chaskar writes:
>  >  > Regarding the issue of round-trip latency in programming QoS 
>forwarding
>  >  > treatment along new path after change in CoA:
>  >  >
>  >  > This is intrinsic drawback of OPWA model of resource reservation of 
>RSVP.
>  > In
>  >  > the worst case, one round-trip time will include traversals of four
>  > wireless
>  >  > links. This happens when both CN and MN are mobile.
>  >  >
>  >  > Note that this drawback is eliminated in the approach to QoS 
>signaling
>  > based
>  >  > on including QoS Object in hop-by-hop options extension header along 
>with
>  >
>  >  > binding messages (draft-chaskar-mobileip-qos-00.txt). This draft was
>  >  > presented in SD and revised version (01) will be submitted soon.
>  >  >
>  >  > Hemant
>  >  > _________________________________________________________________
>  >  > Get your FREE download of MSN Explorer at http://explorer.msn.com
>  >  >

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com



From owner-seamoby@diameter.org  Fri Mar  2 14:50:02 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15156
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 14:50:02 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22I1LJ14041
	for seamoby-list; Fri, 2 Mar 2001 10:01:21 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22I19T14028
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 10:01:09 -0800
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Fri, 2 Mar 2001 12:49:21 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GFB8R88M>; Fri, 2 Mar 2001 12:49:24 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D36@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'seamoby_context'" <seamoby_context@marvin.baynetworks.com>
Cc: "'seamoby'" <seamoby@diameter.org>
Subject: [seamoby] Seamoby Context Transfer Requirements kick-off conference call, M 
         onday, March 5, 2001
Date: Fri, 2 Mar 2001 12:49:15 -0500
Importance: high
X-Priority: 1
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

Apparently, not everyone is available on Monday. However, there are enough
of us available that I belief we can and should get started.

Date: 			Monday, March 5, 2001
Time:			11 AM EST.
US Phone Number: 	972-684-6338
PassCode:		793142
Agenda
*	attendance, hellos, etc.
*	agenda bashing
*	selection of an editor for the requirements draft
*	authorship
*	discussion of format / table of contents
*	action items
*	meeting schedule
For those who cannot make it, and I do apologize again for the
short notice, please submit your thoughts to the seamoby context
transfer email list.
Cheers,
Gary Kenward

==========================================================================

I find that the harder I work, the more luck I seem to have.
- Thomas Jefferson

The contents of this email are Nortel Networks Confidential




From owner-seamoby@diameter.org  Fri Mar  2 14:51:24 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15192
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 14:51:23 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22HvWg13952
	for seamoby-list; Fri, 2 Mar 2001 09:57:32 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22HvST13947
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 09:57:29 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id KAA19946;
	Fri, 2 Mar 2001 10:01:45 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABW01202;
	Fri, 2 Mar 2001 10:01:24 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA03068; Fri, 2 Mar 2001 10:01:24 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15007.57332.399239.487112@thomasm-u1.cisco.com>
Date: Fri, 2 Mar 2001 10:01:24 -0800 (PST)
To: "Hemant Chaskar" <hchaskar@hotmail.com>
Cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org,
        mobile-ip@marvin.corpeast.baynetworks.com, hemant.chaskar@nokia.com
Subject: [seamoby] QoS and Mobile IP
In-Reply-To: <F60ORiI9bWLJBO9E0l000003afb@hotmail.com>
References: <F60ORiI9bWLJBO9E0l000003afb@hotmail.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hemant Chaskar writes:
 > 
 > 
 > 
 > >From: Michael Thomas <mat@cisco.com>
 > 
 > >I really don't even know where to begin. It seems
 > >that your claim is that RSVP's receiver oriented
 > >PATH/RESV is either flawed, or should have a mode
 > >which allows a single pass. I believe this leads
 > >to overbooking for multicast since you don't get
 > >to do flow merging properly and a host of other
 > >reasons that I don't purport to understand well.
 > 
 > => Despite a host of other reasons, if RSVP's OPWA has
 > performance inefficiencies in mobile environment, it cannot
 > be pushed to work with Mobile IP.

   You're surely not saying that RSVP should never
   be used with MIP?

   And I generally object to always characterizing
   MIP and wireless by its least common denominator
   of cellular. 802.11 has, for all intents and
   purposes, the same characteristics as ethernet
   and RSVP, etc, work just fine there, thankyouverymuch.

 > => The solution of enclosing QoS Object in hop-by-hop
 > extension header, preferably with binding messages, performs
 > fast reservation on forward path. 

   No it doesn't. If it needs to go clear back to the
   correspondent node to change filter specs, you're
   already too slow in the degeneate case. 

 > => Speaking of multicast. The question that comes to my mind is
 > whether it is necessary to send binding messages from MN if it
 > is receiving multicast traffic. If MN changes CoA, it can simply
 > use IGMP to register to multicast at that location. Conclusion:
 > Multicast and Unicast can be studied in different perspectives.

   You can have shared reservations that do not
   involve multicast, you realize?

 > Also, state merging is an issue only when you use IntServ. In
 > DiffServ and MPLS cases there is no state to merge!
 > 
 > => Overall, solution of including QoS object in hop-by-hop extension
 > header and performing forward reservations has its own merits. 

   I find this claim rather dubious, but my main point
   is that I do not believe that anything this radical
   belongs in MIP WG. It should either be taken up in
   the (currently dormant) Network WG, or get enough
   support to do a BOF or something. 

	      Mike


From owner-seamoby@diameter.org  Fri Mar  2 14:53:10 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15270
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 14:53:10 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22IE1914277
	for seamoby-list; Fri, 2 Mar 2001 10:14:01 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22IDqT14266
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 10:13:52 -0800
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f22INJw01921
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 12:23:19 -0600 (CST)
Received: from daebh01nok.americas.nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T520bb38918ac12f254102@davir01nok.americas.nokia.com>;
 Fri, 2 Mar 2001 12:20:33 -0600
Received: by daebh01nok with Internet Mail Service (5.5.2652.78)
	id <G17VYATS>; Fri, 2 Mar 2001 12:20:33 -0600
Message-ID: <B9CFA6CE8FFDD211A1FB0008C7894E46027F4460@bseis01nok>
From: Hemant.Chaskar@nokia.com
To: mat@cisco.com, hchaskar@hotmail.com
Cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org,
        mobile-ip@marvin.corpeast.baynetworks.com
Subject: RE: [seamoby] QoS and Mobile IP
Date: Fri, 2 Mar 2001 12:20:30 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

 > => The solution of enclosing QoS Object in hop-by-hop
 > extension header, preferably with binding messages, performs
 > fast reservation on forward path. 

   No it doesn't. If it needs to go clear back to the
   correspondent node to change filter specs, you're
   already too slow in the degeneate case. 

-----> No, you don't get the point still. You have to 
-----> realize that packet carrying QoS object PRECEDES any 
-----> data packets using new CoA. Please read the illustration that
-----> I gave in previous email again. Hence, QoS forwarding will
-----> be in place when these new CoA packets hit the intermediate
-----> routers. RSVP takes one round trip time for that. 


From owner-seamoby@diameter.org  Fri Mar  2 14:56:33 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15367
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 14:56:33 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22I69u14110
	for seamoby-list; Fri, 2 Mar 2001 10:06:09 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22I65T14104
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 10:06:05 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA28571;
	Fri, 2 Mar 2001 10:13:54 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f22IDpb14843;
	Fri, 2 Mar 2001 10:13:51 -0800
X-mProtect:  Fri, 2 Mar 2001 10:13:51 -0800 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90)
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdnXNJJx; Fri, 02 Mar 2001 10:13:15 PST
Message-ID: <3A9FE2BD.7DE14518@iprg.nokia.com>
Date: Fri, 02 Mar 2001 10:13:17 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 2.2.6-RELEASE i386)
MIME-Version: 1.0
To: Gary Kenward <gkenward@nortelnetworks.com>
CC: seamoby_context@marvin.corpeast.baynetworks.com, pat.calhoun@eng.sun.com,
        seamoby@diameter.org
Subject: [seamoby] Re: Seamoby Context Transfer Requirements kick-off conference call, M           onday, March 5, 2001
References: <13E2EF604DE5D111B2E50000F80824E8057A8D36@zwdld001.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello Gary,

I would like to say this meeting _cannot_ be considered as a design team
meeting. First, you pulled out this meeting without sufficient time for
everyone. Second, I would like to point out that the seamoby chair
should initiate such a meeting. Unless I am poorly informed, you are not
a chair of the working group. Finally, even after people respond to you
by not responding to your "invitation", you seem to go ahead with such a
meeting anyway.

Unilateral, blanket positions are not very useful if you wish to
contribute constructively.

Regards,

-Rajeev


Gary Kenward wrote:
> 
> Apparently, not everyone is available on Monday. However, there are enough
> of us available that I belief we can and should get started.
> 
> Date:                   Monday, March 5, 2001
> Time:                   11 AM EST.
> US Phone Number:        972-684-6338
> PassCode:               793142
> Agenda
> *       attendance, hellos, etc.
> *       agenda bashing
> *       selection of an editor for the requirements draft
> *       authorship
> *       discussion of format / table of contents
> *       action items
> *       meeting schedule
> For those who cannot make it, and I do apologize again for the
> short notice, please submit your thoughts to the seamoby context
> transfer email list.
> Cheers,
> Gary Kenward
> 
> ==========================================================================
> 
> I find that the harder I work, the more luck I seem to have.
> - Thomas Jefferson
> 
> The contents of this email are Nortel Networks Confidential


From owner-seamoby@diameter.org  Fri Mar  2 15:10:08 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA15874
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 15:10:07 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22Iox114939
	for seamoby-list; Fri, 2 Mar 2001 10:50:59 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22IoqT14934
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 10:50:53 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Fri, 2 Mar 2001 13:42:07 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GFB8R0T8>; Fri, 2 Mar 2001 13:42:10 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D38@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Rajeev Koodli'" <rajeev@iprg.nokia.com>
Cc: seamoby_context@marvin.corpeast.baynetworks.com, pat.calhoun@eng.sun.com,
        seamoby@diameter.org
Subject: [seamoby] RE: Seamoby Context Transfer Requirements kick-off conference cal l, M 
         onday, March 5, 2001
Date: Fri, 2 Mar 2001 13:42:01 -0500
Importance: high
X-Priority: 1
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A348.78614FB0"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A348.78614FB0
Content-Type: text/plain;
	charset="iso-8859-1"

> -----Original Message-----
> From: Rajeev Koodli [mailto:rajeev@IPRG.nokia.com]
> Sent: Friday, March 02, 2001 1:13 PM
> To: Kenward, Gary [WDLN2:AN10:EXCH]
> Cc: seamoby_context@marvin.corpeast.baynetworks.com;
> pat.calhoun@eng.sun.com; seamoby@diameter.org
> Subject: Re: Seamoby Context Transfer Requirements kick-off conference
> call, M onday, March 5, 2001
> 
> 
> Hello Gary,
> 
> I would like to say this meeting _cannot_ be considered as a 
> design team
> meeting. First, you pulled out this meeting without 
> sufficient time for
> everyone. Second, I would like to point out that the seamoby chair
> should initiate such a meeting. Unless I am poorly informed, 
> you are not

The meeting was called at the request of the working group chair.
Indeed, the chair request that the requirements work proceed
as soon as possible.

> a chair of the working group. Finally, even after people 
> respond to you

I remain the design team leader, for the moment. I verified this
with the working group chair. Certainly, if there is a rough consensus
that it is time for a new leader,  I will be happy to step aside. 

> by not responding to your "invitation", you seem to go ahead 
> with such a

Here you are very wrong. I have received about ten responses,
and I believe 4 people could not attend out of the ten, including 
you.

While some commented that the notification was short, you are the
first to insinuate that there was any other motivation then simply
to move on to the next phase. You are as wrong in that insinuation
as you are in assuming that no one has responded.

> meeting anyway.
> 
> Unilateral, blanket positions are not very useful if you wish to
> contribute constructively.

Ill-informed, aggravating accusations are specifically damaging
to constructive contributions.

> 
> Regards,
> 
> -Rajeev

Gary

> 
> 
> Gary Kenward wrote:
> > 
> > Apparently, not everyone is available on Monday. However, 
> there are enough
> > of us available that I belief we can and should get started.
> > 
> > Date:                   Monday, March 5, 2001
> > Time:                   11 AM EST.
> > US Phone Number:        972-684-6338
> > PassCode:               793142
> > Agenda
> > *       attendance, hellos, etc.
> > *       agenda bashing
> > *       selection of an editor for the requirements draft
> > *       authorship
> > *       discussion of format / table of contents
> > *       action items
> > *       meeting schedule
> > For those who cannot make it, and I do apologize again for the
> > short notice, please submit your thoughts to the seamoby context
> > transfer email list.
> > Cheers,
> > Gary Kenward
> > 
> > 
> ==============================================================
> ============
> > 
> > I find that the harder I work, the more luck I seem to have.
> > - Thomas Jefferson
> > 
> > The contents of this email are Nortel Networks Confidential
> 

------_=_NextPart_001_01C0A348.78614FB0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>RE: Seamoby Context Transfer Requirements kick-off conference call, M  onday, March 5, 2001</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: Rajeev Koodli [<A HREF="mailto:rajeev@IPRG.nokia.com">mailto:rajeev@IPRG.nokia.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Friday, March 02, 2001 1:13 PM</FONT>
<BR><FONT SIZE=2>&gt; To: Kenward, Gary [WDLN2:AN10:EXCH]</FONT>
<BR><FONT SIZE=2>&gt; Cc: seamoby_context@marvin.corpeast.baynetworks.com;</FONT>
<BR><FONT SIZE=2>&gt; pat.calhoun@eng.sun.com; seamoby@diameter.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: Re: Seamoby Context Transfer Requirements kick-off conference</FONT>
<BR><FONT SIZE=2>&gt; call, M onday, March 5, 2001</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Hello Gary,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I would like to say this meeting _cannot_ be considered as a </FONT>
<BR><FONT SIZE=2>&gt; design team</FONT>
<BR><FONT SIZE=2>&gt; meeting. First, you pulled out this meeting without </FONT>
<BR><FONT SIZE=2>&gt; sufficient time for</FONT>
<BR><FONT SIZE=2>&gt; everyone. Second, I would like to point out that the seamoby chair</FONT>
<BR><FONT SIZE=2>&gt; should initiate such a meeting. Unless I am poorly informed, </FONT>
<BR><FONT SIZE=2>&gt; you are not</FONT>
</P>

<P><FONT SIZE=2>The meeting was called at the request of the working group chair.</FONT>
<BR><FONT SIZE=2>Indeed, the chair request that the requirements work proceed</FONT>
<BR><FONT SIZE=2>as soon as possible.</FONT>
</P>

<P><FONT SIZE=2>&gt; a chair of the working group. Finally, even after people </FONT>
<BR><FONT SIZE=2>&gt; respond to you</FONT>
</P>

<P><FONT SIZE=2>I remain the design team leader, for the moment. I verified this</FONT>
<BR><FONT SIZE=2>with the working group chair. Certainly, if there is a rough consensus</FONT>
<BR><FONT SIZE=2>that it is time for a new leader,&nbsp; I will be happy to step aside. </FONT>
</P>

<P><FONT SIZE=2>&gt; by not responding to your &quot;invitation&quot;, you seem to go ahead </FONT>
<BR><FONT SIZE=2>&gt; with such a</FONT>
</P>

<P><FONT SIZE=2>Here you are very wrong. I have received about ten responses,</FONT>
<BR><FONT SIZE=2>and I believe 4 people could not attend out of the ten, including </FONT>
<BR><FONT SIZE=2>you.</FONT>
</P>

<P><FONT SIZE=2>While some commented that the notification was short, you are the</FONT>
<BR><FONT SIZE=2>first to insinuate that there was any other motivation then simply</FONT>
<BR><FONT SIZE=2>to move on to the next phase. You are as wrong in that insinuation</FONT>
<BR><FONT SIZE=2>as you are in assuming that no one has responded.</FONT>
</P>

<P><FONT SIZE=2>&gt; meeting anyway.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Unilateral, blanket positions are not very useful if you wish to</FONT>
<BR><FONT SIZE=2>&gt; contribute constructively.</FONT>
</P>

<P><FONT SIZE=2>Ill-informed, aggravating accusations are specifically damaging</FONT>
<BR><FONT SIZE=2>to constructive contributions.</FONT>
</P>

<P><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Regards,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; -Rajeev</FONT>
</P>

<P><FONT SIZE=2>Gary</FONT>
</P>

<P><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Gary Kenward wrote:</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Apparently, not everyone is available on Monday. However, </FONT>
<BR><FONT SIZE=2>&gt; there are enough</FONT>
<BR><FONT SIZE=2>&gt; &gt; of us available that I belief we can and should get started.</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Monday, March 5, 2001</FONT>
<BR><FONT SIZE=2>&gt; &gt; Time:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 11 AM EST.</FONT>
<BR><FONT SIZE=2>&gt; &gt; US Phone Number:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 972-684-6338</FONT>
<BR><FONT SIZE=2>&gt; &gt; PassCode:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 793142</FONT>
<BR><FONT SIZE=2>&gt; &gt; Agenda</FONT>
<BR><FONT SIZE=2>&gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; attendance, hellos, etc.</FONT>
<BR><FONT SIZE=2>&gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; agenda bashing</FONT>
<BR><FONT SIZE=2>&gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; selection of an editor for the requirements draft</FONT>
<BR><FONT SIZE=2>&gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; authorship</FONT>
<BR><FONT SIZE=2>&gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; discussion of format / table of contents</FONT>
<BR><FONT SIZE=2>&gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; action items</FONT>
<BR><FONT SIZE=2>&gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; meeting schedule</FONT>
<BR><FONT SIZE=2>&gt; &gt; For those who cannot make it, and I do apologize again for the</FONT>
<BR><FONT SIZE=2>&gt; &gt; short notice, please submit your thoughts to the seamoby context</FONT>
<BR><FONT SIZE=2>&gt; &gt; transfer email list.</FONT>
<BR><FONT SIZE=2>&gt; &gt; Cheers,</FONT>
<BR><FONT SIZE=2>&gt; &gt; Gary Kenward</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; ==============================================================</FONT>
<BR><FONT SIZE=2>&gt; ============</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; I find that the harder I work, the more luck I seem to have.</FONT>
<BR><FONT SIZE=2>&gt; &gt; - Thomas Jefferson</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; The contents of this email are Nortel Networks Confidential</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A348.78614FB0--


From owner-seamoby@diameter.org  Fri Mar  2 15:40:21 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17342
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 15:40:20 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22Ixos15079
	for seamoby-list; Fri, 2 Mar 2001 10:59:50 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22IxjT15073
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 10:59:46 -0800
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Fri, 2 Mar 2001 13:44:33 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GFB8R0WW>; Fri, 2 Mar 2001 13:44:36 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D39@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Pat Calhoun'" <pcalhoun@nasnfs.eng.sun.com>,
        Rajeev Koodli <rajeev@iprg.nokia.com>
Cc: seamoby_context@marvin.corpeast.baynetworks.com, pat.calhoun@eng.sun.com,
        seamoby@diameter.org
Subject: [seamoby] RE: Seamoby Context Transfer Requirements kick-off conference cal l, M 
         onday, March 5, 2001
Date: Fri, 2 Mar 2001 13:44:30 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A348.D0CCCF30"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A348.D0CCCF30
Content-Type: text/plain;
	charset="iso-8859-1"

Pat:

  As I indicated in my response to Rajeev's posting, there have
been a majority of positive responses to a Monday meeting. 
I would not have gone ahead with all the effort to schedule
a conference call otherwise.

  I am perfectly fine with delaying this by a week. I have plenty
of other irons in the fire. However, given that we have seven
attendees, maybe more, do you still want the meeting delayed?

Gary

> -----Original Message-----
> From: Pat Calhoun [mailto:pcalhoun@nasnfs.Eng.Sun.COM]
> Sent: Friday, March 02, 2001 1:17 PM
> To: Rajeev Koodli
> Cc: Kenward, Gary [WDLN2:AN10:EXCH];
> seamoby_context@marvin.corpeast.baynetworks.com;
> pat.calhoun@eng.sun.com; seamoby@diameter.org
> Subject: Re: Seamoby Context Transfer Requirements kick-off conference
> call, M onday, March 5, 2001
> 
> 
> Given the WG comments, let's postpone the first meeting until 3/12. 
> 
> Rajeev, you are correct that Gary isn't the chair, but he is 
> the meeting
> "facilitator". What that means is that he is the lucky one 
> organizing the
> conference call. I believe that's all Gary was trying to do. 
> I also believe
> that he wanted to get an early start to have more output at 
> the IETF meeting.
> 
> PatC
> > Hello Gary,
> > 
> > I would like to say this meeting _cannot_ be considered as 
> a design team
> > meeting. First, you pulled out this meeting without 
> sufficient time for
> > everyone. Second, I would like to point out that the seamoby chair
> > should initiate such a meeting. Unless I am poorly 
> informed, you are not
> > a chair of the working group. Finally, even after people 
> respond to you
> > by not responding to your "invitation", you seem to go 
> ahead with such a
> > meeting anyway.
> > 
> > Unilateral, blanket positions are not very useful if you wish to
> > contribute constructively.
> > 
> > Regards,
> > 
> > -Rajeev
> > 
> > 
> > Gary Kenward wrote:
> > > 
> > > Apparently, not everyone is available on Monday. However, 
> there are enough
> > > of us available that I belief we can and should get started.
> > > 
> > > Date:                   Monday, March 5, 2001
> > > Time:                   11 AM EST.
> > > US Phone Number:        972-684-6338
> > > PassCode:               793142
> > > Agenda
> > > *       attendance, hellos, etc.
> > > *       agenda bashing
> > > *       selection of an editor for the requirements draft
> > > *       authorship
> > > *       discussion of format / table of contents
> > > *       action items
> > > *       meeting schedule
> > > For those who cannot make it, and I do apologize again for the
> > > short notice, please submit your thoughts to the seamoby context
> > > transfer email list.
> > > Cheers,
> > > Gary Kenward
> > > 
> > > 
> ==============================================================
> ============
> > > 
> > > I find that the harder I work, the more luck I seem to have.
> > > - Thomas Jefferson
> > > 
> > > The contents of this email are Nortel Networks Confidential
> 
> 
> 

------_=_NextPart_001_01C0A348.D0CCCF30
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>RE: Seamoby Context Transfer Requirements kick-off conference call, M  onday, March 5, 2001</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Pat:</FONT>
</P>

<P><FONT SIZE=2>&nbsp; As I indicated in my response to Rajeev's posting, there have</FONT>
<BR><FONT SIZE=2>been a majority of positive responses to a Monday meeting. </FONT>
<BR><FONT SIZE=2>I would not have gone ahead with all the effort to schedule</FONT>
<BR><FONT SIZE=2>a conference call otherwise.</FONT>
</P>

<P><FONT SIZE=2>&nbsp; I am perfectly fine with delaying this by a week. I have plenty</FONT>
<BR><FONT SIZE=2>of other irons in the fire. However, given that we have seven</FONT>
<BR><FONT SIZE=2>attendees, maybe more, do you still want the meeting delayed?</FONT>
</P>

<P><FONT SIZE=2>Gary</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: Pat Calhoun [<A HREF="mailto:pcalhoun@nasnfs.Eng.Sun.COM">mailto:pcalhoun@nasnfs.Eng.Sun.COM</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Friday, March 02, 2001 1:17 PM</FONT>
<BR><FONT SIZE=2>&gt; To: Rajeev Koodli</FONT>
<BR><FONT SIZE=2>&gt; Cc: Kenward, Gary [WDLN2:AN10:EXCH];</FONT>
<BR><FONT SIZE=2>&gt; seamoby_context@marvin.corpeast.baynetworks.com;</FONT>
<BR><FONT SIZE=2>&gt; pat.calhoun@eng.sun.com; seamoby@diameter.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: Re: Seamoby Context Transfer Requirements kick-off conference</FONT>
<BR><FONT SIZE=2>&gt; call, M onday, March 5, 2001</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Given the WG comments, let's postpone the first meeting until 3/12. </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Rajeev, you are correct that Gary isn't the chair, but he is </FONT>
<BR><FONT SIZE=2>&gt; the meeting</FONT>
<BR><FONT SIZE=2>&gt; &quot;facilitator&quot;. What that means is that he is the lucky one </FONT>
<BR><FONT SIZE=2>&gt; organizing the</FONT>
<BR><FONT SIZE=2>&gt; conference call. I believe that's all Gary was trying to do. </FONT>
<BR><FONT SIZE=2>&gt; I also believe</FONT>
<BR><FONT SIZE=2>&gt; that he wanted to get an early start to have more output at </FONT>
<BR><FONT SIZE=2>&gt; the IETF meeting.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; PatC</FONT>
<BR><FONT SIZE=2>&gt; &gt; Hello Gary,</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; I would like to say this meeting _cannot_ be considered as </FONT>
<BR><FONT SIZE=2>&gt; a design team</FONT>
<BR><FONT SIZE=2>&gt; &gt; meeting. First, you pulled out this meeting without </FONT>
<BR><FONT SIZE=2>&gt; sufficient time for</FONT>
<BR><FONT SIZE=2>&gt; &gt; everyone. Second, I would like to point out that the seamoby chair</FONT>
<BR><FONT SIZE=2>&gt; &gt; should initiate such a meeting. Unless I am poorly </FONT>
<BR><FONT SIZE=2>&gt; informed, you are not</FONT>
<BR><FONT SIZE=2>&gt; &gt; a chair of the working group. Finally, even after people </FONT>
<BR><FONT SIZE=2>&gt; respond to you</FONT>
<BR><FONT SIZE=2>&gt; &gt; by not responding to your &quot;invitation&quot;, you seem to go </FONT>
<BR><FONT SIZE=2>&gt; ahead with such a</FONT>
<BR><FONT SIZE=2>&gt; &gt; meeting anyway.</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Unilateral, blanket positions are not very useful if you wish to</FONT>
<BR><FONT SIZE=2>&gt; &gt; contribute constructively.</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Regards,</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; -Rajeev</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Gary Kenward wrote:</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Apparently, not everyone is available on Monday. However, </FONT>
<BR><FONT SIZE=2>&gt; there are enough</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; of us available that I belief we can and should get started.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Monday, March 5, 2001</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Time:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 11 AM EST.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; US Phone Number:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 972-684-6338</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; PassCode:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 793142</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Agenda</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; attendance, hellos, etc.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; agenda bashing</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; selection of an editor for the requirements draft</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; authorship</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; discussion of format / table of contents</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; action items</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; meeting schedule</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; For those who cannot make it, and I do apologize again for the</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; short notice, please submit your thoughts to the seamoby context</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; transfer email list.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Cheers,</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Gary Kenward</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; ==============================================================</FONT>
<BR><FONT SIZE=2>&gt; ============</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; I find that the harder I work, the more luck I seem to have.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; - Thomas Jefferson</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; The contents of this email are Nortel Networks Confidential</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A348.D0CCCF30--


From owner-seamoby@diameter.org  Fri Mar  2 15:41:15 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17402
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 15:41:15 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22JAd515310
	for seamoby-list; Fri, 2 Mar 2001 11:10:39 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22JAKT15296
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 11:10:20 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAB26287;
	Fri, 2 Mar 2001 11:15:19 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA11817;
	Fri, 2 Mar 2001 11:15:18 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id LAA11688;
	Fri, 2 Mar 2001 11:15:09 -0800 (PST)
Date: Fri, 2 Mar 2001 11:10:47 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] Re: Seamoby Context Transfer Requirements kick-off conference call, M           onday, March 5, 2001
To: Rajeev Koodli <rajeev@iprg.nokia.com>
Cc: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>,
        Gary Kenward <gkenward@nortelnetworks.com>,
        seamoby_context@marvin.corpeast.baynetworks.com,
        pat.calhoun@eng.sun.com, seamoby@diameter.org
In-Reply-To: "Your message with ID" <3A9FEE92.41C67EA6@iprg.nokia.com>
Message-ID: <Roam.SIMC.2.0.6.983560247.6176.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> thanks for the reply. I understand and appreciate Gary's effort.

as do I.

> However, what would be the value of having a meeting without sufficient
> minds ? The proposal for a conference call for new effort (such as the
> requirements draft) should come from WG chair(s). 

I sent a couple of notes stating that this would be setup. In my note I stated
that DTs would be used, and as with the previous efforts, the conference calls
have been setup by the DT leaders. I see no reason to change how we operate at
this point in time. As long as the conference info is made available to the
list, then it really shouldn't matter, right?

> Once agreed, the
> subsequent e-mails could come from the facilitator.   

I have received many e-mails stating that DT was the preferred approach.

> Also, getting a head start is valuable, but again not at the expense of
> hastiness. 
> I hope that we can have thoughtfully facilitated meetings!

Correct, hence my note that the first call will occur on 3/12.

PatC



From owner-seamoby@diameter.org  Fri Mar  2 15:57:36 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA18360
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 15:57:36 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22J7U915215
	for seamoby-list; Fri, 2 Mar 2001 11:07:30 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22J7RT15208
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 11:07:27 -0800
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Fri, 2 Mar 2001 14:15:01 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GFB8SAWT>; Fri, 2 Mar 2001 14:15:05 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D3B@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'seamoby_context'" <seamoby_context@marvin.baynetworks.com>
Cc: "'seamoby'" <seamoby@diameter.org>
Subject: [seamoby] mondays conference call
Date: Fri, 2 Mar 2001 14:15:00 -0500
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
X-Orig: <gkenward@americasm01.nt.com>
X-MIME-Autoconverted: from quoted-printable to 8bit by charizard.diameter.org id f22J7ST15209
Sender: owner-seamoby@diameter.org
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by charizard.diameter.org id f22J7U915215
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA18360

Well, even though we had a consensus for a first meeting this Monday, it 
seems that this is not sufficient.

The first meeting will be Monday, March 12. The agenda remains the
same, with the addition of a new item to determine there is a consensus
to select a new team leader. Although at this point, I am unclear as to
what constitutes a consensus.

My apologies to those of you who committed to Monday's meeting and
actually starting the requirements work.

Gary

==========================================================================

Plus ça change, plus c'est la même chose.




From owner-seamoby@diameter.org  Fri Mar  2 17:04:28 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA21822
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 17:04:27 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22JrrH15690
	for seamoby-list; Fri, 2 Mar 2001 11:53:53 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from eagle.aud.alcatel.com (host60d9.alcatel.com [128.251.96.217])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22JroT15685
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 11:53:50 -0800
Received: from mswitch.aud.alcatel.com by eagle.aud.alcatel.com (8.8.8+Sun/SMI-SVR4)
	id OAA04224; Fri, 2 Mar 2001 14:01:38 -0600 (CST)
Received: from usa.alcatel.com by mswitch.aud.alcatel.com (8.8.8+Sun/SMI-SVR4)
	id OAA16257; Fri, 2 Mar 2001 14:01:34 -0600 (CST)
Message-ID: <3A9FFC1E.1C081B77@usa.alcatel.com>
Date: Fri, 02 Mar 2001 14:01:34 -0600
From: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: seamoby@diameter.org
Subject: [seamoby] No I-D action yet
Content-Type: multipart/alternative;
 boundary="------------D044C3E2046737D4DF125957"
Sender: owner-seamoby@diameter.org
Precedence: bulk


--------------D044C3E2046737D4DF125957
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Seamoby folks,
  I submitted an I-D draft-sarikaya-seamoby-paging-requirements-00.txt
which has been revolving at 3,600 rpm on IETF and its mirror site disks.

So far no official I-D Action email has been issued by IETF. I do expect
that
it will be soon.
  Your comments are welcome.

--
Behcet



--------------D044C3E2046737D4DF125957
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Seamoby folks,
<br>&nbsp; I submitted an I-D draft-sarikaya-seamoby-paging-requirements-00.txt
<br>which has been revolving at 3,600 rpm on IETF and its mirror site disks.
<br>So far no official I-D Action email has been issued by IETF. I do expect
that
<br>it will be soon.
<br>&nbsp; Your comments are welcome.
<pre>--&nbsp;
Behcet</pre>
&nbsp;</html>

--------------D044C3E2046737D4DF125957--



From owner-seamoby@diameter.org  Fri Mar  2 17:09:10 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA22010
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 17:09:09 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22J99I15257
	for seamoby-list; Fri, 2 Mar 2001 11:09:09 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22J95T15251
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 11:09:05 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA06704;
	Fri, 2 Mar 2001 11:16:47 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA12213;
	Fri, 2 Mar 2001 11:16:46 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id LAA11769;
	Fri, 2 Mar 2001 11:16:44 -0800 (PST)
Date: Fri, 2 Mar 2001 11:12:19 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
Subject: [seamoby] RE: Seamoby Context Transfer Requirements kick-off conference cal l, M          onday, March 5, 2001
To: Gary Kenward <gkenward@nortelnetworks.com>
Cc: "'Pat Calhoun'" <pcalhoun@nasnfs.Eng.Sun.COM>,
        Rajeev Koodli <rajeev@iprg.nokia.com>,
        seamoby_context@marvin.corpeast.baynetworks.com,
        pat.calhoun@eng.sun.com, seamoby@diameter.org
In-Reply-To: "Your message with ID" <13E2EF604DE5D111B2E50000F80824E8057A8D39@zwdld001.ca.nortel.com>
Message-ID: <Roam.SIMC.2.0.6.983560339.31697.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

>   As I indicated in my response to Rajeev's posting, there have
> been a majority of positive responses to a Monday meeting. 
> I would not have gone ahead with all the effort to schedule
> a conference call otherwise.

I understand this.

>   I am perfectly fine with delaying this by a week. I have plenty
> of other irons in the fire. However, given that we have seven
> attendees, maybe more, do you still want the meeting delayed?

Right, but providing one business day notice doesn't really allow one to
change their plans, and a week is a little better. I would prefer that we stay
with 3/12.

Thanks again for taking care of this,

PatC



From owner-seamoby@diameter.org  Fri Mar  2 17:13:44 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA22153
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 17:13:43 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22IvUU15038
	for seamoby-list; Fri, 2 Mar 2001 10:57:30 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22IvQT15032
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 10:57:26 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id LAA04501;
	Fri, 2 Mar 2001 11:05:15 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f22J5ED24479;
	Fri, 2 Mar 2001 11:05:14 -0800
X-mProtect:  Fri, 2 Mar 2001 11:05:14 -0800 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90)
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdTZp2ZF; Fri, 02 Mar 2001 11:03:45 PST
Message-ID: <3A9FEE92.41C67EA6@iprg.nokia.com>
Date: Fri, 02 Mar 2001 11:03:46 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 2.2.6-RELEASE i386)
MIME-Version: 1.0
To: Pat Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
CC: Gary Kenward <gkenward@nortelnetworks.com>,
        seamoby_context@marvin.corpeast.baynetworks.com,
        pat.calhoun@eng.sun.com, seamoby@diameter.org
Subject: [seamoby] Re: Seamoby Context Transfer Requirements kick-off conference call, M           onday, March 5, 2001
References: <Roam.SIMC.2.0.6.983557012.29586.pcalhoun@nasnfs>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pat,

thanks for the reply. I understand and appreciate Gary's effort.
However, what would be the value of having a meeting without sufficient
minds ? The proposal for a conference call for new effort (such as the
requirements draft) should come from WG chair(s). Once agreed, the
subsequent e-mails could come from the facilitator.   
Also, getting a head start is valuable, but again not at the expense of
hastiness. 
I hope that we can have thoughtfully facilitated meetings!

Regards,

-Rajeev


Pat Calhoun wrote:
> 
> Given the WG comments, let's postpone the first meeting until 3/12.
> 
> Rajeev, you are correct that Gary isn't the chair, but he is the meeting
> "facilitator". What that means is that he is the lucky one organizing the
> conference call. I believe that's all Gary was trying to do. I also believe
> that he wanted to get an early start to have more output at the IETF meeting.
> 
> PatC
> > Hello Gary,
> >
> > I would like to say this meeting _cannot_ be considered as a design team
> > meeting. First, you pulled out this meeting without sufficient time for
> > everyone. Second, I would like to point out that the seamoby chair
> > should initiate such a meeting. Unless I am poorly informed, you are not
> > a chair of the working group. Finally, even after people respond to you
> > by not responding to your "invitation", you seem to go ahead with such a
> > meeting anyway.
> >
> > Unilateral, blanket positions are not very useful if you wish to
> > contribute constructively.
> >
> > Regards,
> >
> > -Rajeev
> >
> >
> > Gary Kenward wrote:
> > >
> > > Apparently, not everyone is available on Monday. However, there are enough
> > > of us available that I belief we can and should get started.
> > >
> > > Date:                   Monday, March 5, 2001
> > > Time:                   11 AM EST.
> > > US Phone Number:        972-684-6338
> > > PassCode:               793142
> > > Agenda
> > > *       attendance, hellos, etc.
> > > *       agenda bashing
> > > *       selection of an editor for the requirements draft
> > > *       authorship
> > > *       discussion of format / table of contents
> > > *       action items
> > > *       meeting schedule
> > > For those who cannot make it, and I do apologize again for the
> > > short notice, please submit your thoughts to the seamoby context
> > > transfer email list.
> > > Cheers,
> > > Gary Kenward
> > >
> > > ==========================================================================
> > >
> > > I find that the harder I work, the more luck I seem to have.
> > > - Thomas Jefferson
> > >
> > > The contents of this email are Nortel Networks Confidential


From owner-seamoby@diameter.org  Fri Mar  2 17:15:24 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA22266
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 17:15:23 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22Ixos15079
	for seamoby-list; Fri, 2 Mar 2001 10:59:50 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22IxjT15073
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 10:59:46 -0800
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Fri, 2 Mar 2001 13:44:33 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GFB8R0WW>; Fri, 2 Mar 2001 13:44:36 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D39@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Pat Calhoun'" <pcalhoun@nasnfs.Eng.Sun.COM>,
        Rajeev Koodli <rajeev@IPRG.nokia.com>
Cc: seamoby_context@marvin.corpeast.baynetworks.com, pat.calhoun@eng.sun.com,
        seamoby@diameter.org
Subject: [seamoby] RE: Seamoby Context Transfer Requirements kick-off conference cal l, M 
         onday, March 5, 2001
Date: Fri, 2 Mar 2001 13:44:30 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A348.D0CCCF30"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A348.D0CCCF30
Content-Type: text/plain;
	charset="iso-8859-1"

Pat:

  As I indicated in my response to Rajeev's posting, there have
been a majority of positive responses to a Monday meeting. 
I would not have gone ahead with all the effort to schedule
a conference call otherwise.

  I am perfectly fine with delaying this by a week. I have plenty
of other irons in the fire. However, given that we have seven
attendees, maybe more, do you still want the meeting delayed?

Gary

> -----Original Message-----
> From: Pat Calhoun [mailto:pcalhoun@nasnfs.Eng.Sun.COM]
> Sent: Friday, March 02, 2001 1:17 PM
> To: Rajeev Koodli
> Cc: Kenward, Gary [WDLN2:AN10:EXCH];
> seamoby_context@marvin.corpeast.baynetworks.com;
> pat.calhoun@eng.sun.com; seamoby@diameter.org
> Subject: Re: Seamoby Context Transfer Requirements kick-off conference
> call, M onday, March 5, 2001
> 
> 
> Given the WG comments, let's postpone the first meeting until 3/12. 
> 
> Rajeev, you are correct that Gary isn't the chair, but he is 
> the meeting
> "facilitator". What that means is that he is the lucky one 
> organizing the
> conference call. I believe that's all Gary was trying to do. 
> I also believe
> that he wanted to get an early start to have more output at 
> the IETF meeting.
> 
> PatC
> > Hello Gary,
> > 
> > I would like to say this meeting _cannot_ be considered as 
> a design team
> > meeting. First, you pulled out this meeting without 
> sufficient time for
> > everyone. Second, I would like to point out that the seamoby chair
> > should initiate such a meeting. Unless I am poorly 
> informed, you are not
> > a chair of the working group. Finally, even after people 
> respond to you
> > by not responding to your "invitation", you seem to go 
> ahead with such a
> > meeting anyway.
> > 
> > Unilateral, blanket positions are not very useful if you wish to
> > contribute constructively.
> > 
> > Regards,
> > 
> > -Rajeev
> > 
> > 
> > Gary Kenward wrote:
> > > 
> > > Apparently, not everyone is available on Monday. However, 
> there are enough
> > > of us available that I belief we can and should get started.
> > > 
> > > Date:                   Monday, March 5, 2001
> > > Time:                   11 AM EST.
> > > US Phone Number:        972-684-6338
> > > PassCode:               793142
> > > Agenda
> > > *       attendance, hellos, etc.
> > > *       agenda bashing
> > > *       selection of an editor for the requirements draft
> > > *       authorship
> > > *       discussion of format / table of contents
> > > *       action items
> > > *       meeting schedule
> > > For those who cannot make it, and I do apologize again for the
> > > short notice, please submit your thoughts to the seamoby context
> > > transfer email list.
> > > Cheers,
> > > Gary Kenward
> > > 
> > > 
> ==============================================================
> ============
> > > 
> > > I find that the harder I work, the more luck I seem to have.
> > > - Thomas Jefferson
> > > 
> > > The contents of this email are Nortel Networks Confidential
> 
> 
> 

------_=_NextPart_001_01C0A348.D0CCCF30
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>RE: Seamoby Context Transfer Requirements kick-off conference call, M  onday, March 5, 2001</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Pat:</FONT>
</P>

<P><FONT SIZE=2>&nbsp; As I indicated in my response to Rajeev's posting, there have</FONT>
<BR><FONT SIZE=2>been a majority of positive responses to a Monday meeting. </FONT>
<BR><FONT SIZE=2>I would not have gone ahead with all the effort to schedule</FONT>
<BR><FONT SIZE=2>a conference call otherwise.</FONT>
</P>

<P><FONT SIZE=2>&nbsp; I am perfectly fine with delaying this by a week. I have plenty</FONT>
<BR><FONT SIZE=2>of other irons in the fire. However, given that we have seven</FONT>
<BR><FONT SIZE=2>attendees, maybe more, do you still want the meeting delayed?</FONT>
</P>

<P><FONT SIZE=2>Gary</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: Pat Calhoun [<A HREF="mailto:pcalhoun@nasnfs.Eng.Sun.COM">mailto:pcalhoun@nasnfs.Eng.Sun.COM</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Friday, March 02, 2001 1:17 PM</FONT>
<BR><FONT SIZE=2>&gt; To: Rajeev Koodli</FONT>
<BR><FONT SIZE=2>&gt; Cc: Kenward, Gary [WDLN2:AN10:EXCH];</FONT>
<BR><FONT SIZE=2>&gt; seamoby_context@marvin.corpeast.baynetworks.com;</FONT>
<BR><FONT SIZE=2>&gt; pat.calhoun@eng.sun.com; seamoby@diameter.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: Re: Seamoby Context Transfer Requirements kick-off conference</FONT>
<BR><FONT SIZE=2>&gt; call, M onday, March 5, 2001</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Given the WG comments, let's postpone the first meeting until 3/12. </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Rajeev, you are correct that Gary isn't the chair, but he is </FONT>
<BR><FONT SIZE=2>&gt; the meeting</FONT>
<BR><FONT SIZE=2>&gt; &quot;facilitator&quot;. What that means is that he is the lucky one </FONT>
<BR><FONT SIZE=2>&gt; organizing the</FONT>
<BR><FONT SIZE=2>&gt; conference call. I believe that's all Gary was trying to do. </FONT>
<BR><FONT SIZE=2>&gt; I also believe</FONT>
<BR><FONT SIZE=2>&gt; that he wanted to get an early start to have more output at </FONT>
<BR><FONT SIZE=2>&gt; the IETF meeting.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; PatC</FONT>
<BR><FONT SIZE=2>&gt; &gt; Hello Gary,</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; I would like to say this meeting _cannot_ be considered as </FONT>
<BR><FONT SIZE=2>&gt; a design team</FONT>
<BR><FONT SIZE=2>&gt; &gt; meeting. First, you pulled out this meeting without </FONT>
<BR><FONT SIZE=2>&gt; sufficient time for</FONT>
<BR><FONT SIZE=2>&gt; &gt; everyone. Second, I would like to point out that the seamoby chair</FONT>
<BR><FONT SIZE=2>&gt; &gt; should initiate such a meeting. Unless I am poorly </FONT>
<BR><FONT SIZE=2>&gt; informed, you are not</FONT>
<BR><FONT SIZE=2>&gt; &gt; a chair of the working group. Finally, even after people </FONT>
<BR><FONT SIZE=2>&gt; respond to you</FONT>
<BR><FONT SIZE=2>&gt; &gt; by not responding to your &quot;invitation&quot;, you seem to go </FONT>
<BR><FONT SIZE=2>&gt; ahead with such a</FONT>
<BR><FONT SIZE=2>&gt; &gt; meeting anyway.</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Unilateral, blanket positions are not very useful if you wish to</FONT>
<BR><FONT SIZE=2>&gt; &gt; contribute constructively.</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Regards,</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; -Rajeev</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Gary Kenward wrote:</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Apparently, not everyone is available on Monday. However, </FONT>
<BR><FONT SIZE=2>&gt; there are enough</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; of us available that I belief we can and should get started.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Monday, March 5, 2001</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Time:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 11 AM EST.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; US Phone Number:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 972-684-6338</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; PassCode:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 793142</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Agenda</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; attendance, hellos, etc.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; agenda bashing</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; selection of an editor for the requirements draft</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; authorship</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; discussion of format / table of contents</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; action items</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; meeting schedule</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; For those who cannot make it, and I do apologize again for the</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; short notice, please submit your thoughts to the seamoby context</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; transfer email list.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Cheers,</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Gary Kenward</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; ==============================================================</FONT>
<BR><FONT SIZE=2>&gt; ============</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; I find that the harder I work, the more luck I seem to have.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; - Thomas Jefferson</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; The contents of this email are Nortel Networks Confidential</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A348.D0CCCF30--


From owner-seamoby@diameter.org  Fri Mar  2 17:24:56 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA22511
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 17:24:56 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22L8AZ16702
	for seamoby-list; Fri, 2 Mar 2001 13:08:10 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22L88Y16696
	for <seamoby@cdma-2000.org>; Fri, 2 Mar 2001 13:08:08 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA22017
	for <seamoby@cdma-2000.org>; Fri, 2 Mar 2001 13:15:58 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA18026
	for <seamoby@cdma-2000.org>; Fri, 2 Mar 2001 13:15:52 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id NAA14651
	for <seamoby@cdma-2000.org>; Fri, 2 Mar 2001 13:15:51 -0800 (PST)
Date: Fri, 2 Mar 2001 13:11:28 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] test
To: seamoby@cdma-2000.org
Message-ID: <Roam.SIMC.2.0.6.983567488.482.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

test of new spam filters

PatC



From owner-seamoby@diameter.org  Fri Mar  2 17:59:59 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA23848
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 17:59:58 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22IE2M14278
	for seamoby-list; Fri, 2 Mar 2001 10:14:02 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22IDtT14270
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 10:13:55 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA12445;
	Fri, 2 Mar 2001 10:21:19 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA26432;
	Fri, 2 Mar 2001 10:21:19 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id KAA10405;
	Fri, 2 Mar 2001 10:21:14 -0800 (PST)
Date: Fri, 2 Mar 2001 10:16:52 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
Subject: [seamoby] Re: Seamoby Context Transfer Requirements kick-off conference call, M           onday, March 5, 2001
To: Rajeev Koodli <rajeev@IPRG.nokia.com>
Cc: Gary Kenward <gkenward@nortelnetworks.com>,
        seamoby_context@marvin.corpeast.baynetworks.com,
        pat.calhoun@eng.sun.com, seamoby@diameter.org
In-Reply-To: "Your message with ID" <3A9FE2BD.7DE14518@iprg.nokia.com>
Message-ID: <Roam.SIMC.2.0.6.983557012.29586.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

Given the WG comments, let's postpone the first meeting until 3/12. 

Rajeev, you are correct that Gary isn't the chair, but he is the meeting
"facilitator". What that means is that he is the lucky one organizing the
conference call. I believe that's all Gary was trying to do. I also believe
that he wanted to get an early start to have more output at the IETF meeting.

PatC
> Hello Gary,
> 
> I would like to say this meeting _cannot_ be considered as a design team
> meeting. First, you pulled out this meeting without sufficient time for
> everyone. Second, I would like to point out that the seamoby chair
> should initiate such a meeting. Unless I am poorly informed, you are not
> a chair of the working group. Finally, even after people respond to you
> by not responding to your "invitation", you seem to go ahead with such a
> meeting anyway.
> 
> Unilateral, blanket positions are not very useful if you wish to
> contribute constructively.
> 
> Regards,
> 
> -Rajeev
> 
> 
> Gary Kenward wrote:
> > 
> > Apparently, not everyone is available on Monday. However, there are enough
> > of us available that I belief we can and should get started.
> > 
> > Date:                   Monday, March 5, 2001
> > Time:                   11 AM EST.
> > US Phone Number:        972-684-6338
> > PassCode:               793142
> > Agenda
> > *       attendance, hellos, etc.
> > *       agenda bashing
> > *       selection of an editor for the requirements draft
> > *       authorship
> > *       discussion of format / table of contents
> > *       action items
> > *       meeting schedule
> > For those who cannot make it, and I do apologize again for the
> > short notice, please submit your thoughts to the seamoby context
> > transfer email list.
> > Cheers,
> > Gary Kenward
> > 
> > ==========================================================================
> > 
> > I find that the harder I work, the more luck I seem to have.
> > - Thomas Jefferson
> > 
> > The contents of this email are Nortel Networks Confidential




From owner-seamoby@diameter.org  Fri Mar  2 18:24:10 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA24478
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 18:24:09 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22MDRN17197
	for seamoby-list; Fri, 2 Mar 2001 14:13:27 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22MDPY17192
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 14:13:25 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id OAA25027;
	Fri, 2 Mar 2001 14:21:15 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f22MLCl08196;
	Fri, 2 Mar 2001 14:21:12 -0800
X-mProtect:  Fri, 2 Mar 2001 14:21:12 -0800 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90)
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdPkW0xe; Fri, 02 Mar 2001 14:20:34 PST
Message-ID: <3AA01CB2.15FB7483@iprg.nokia.com>
Date: Fri, 02 Mar 2001 14:20:34 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 2.2.6-RELEASE i386)
MIME-Version: 1.0
To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
CC: Gary Kenward <gkenward@nortelnetworks.com>,
        seamoby_context@marvin.corpeast.baynetworks.com,
        pat.calhoun@eng.sun.com, seamoby@diameter.org
Subject: [seamoby] Re: Seamoby Context Transfer Requirements kick-off conference call, M           onday, March 5, 2001
References: <Roam.SIMC.2.0.6.983560247.6176.pcalhoun@nasnfs>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Now that the ID deadline is over, I can respond to this thread. 

Pat Calhoun wrote:
> 
> I sent a couple of notes stating that this would be setup. In my note I stated
> that DTs would be used, and as with the previous efforts, the conference calls
> have been setup by the DT leaders. I see no reason to change how we operate at
> this point in time. As long as the conference info is made available to the
> list, then it really shouldn't matter, right?
> 

Which note are you referring to ? I have not seen such a note. I am
(supposed to be anyway) subscribed to seamoby and seamoby_context
mailing lists. 

I am not suggesting that we change the approach. I am suggesting that
the conference logisitics be conducted more thoughtfully. 
If I missed your note in which you mentioned that DTs would be making a
call on the Requirements phase, I am sorry. 

> > Once agreed, the
> > subsequent e-mails could come from the facilitator.
> 
> I have received many e-mails stating that DT was the preferred approach.
> 
> > Also, getting a head start is valuable, but again not at the expense of
> > hastiness.
> > I hope that we can have thoughtfully facilitated meetings!
> 
> Correct, hence my note that the first call will occur on 3/12.
> 

Thanks.

-Rajeev

> PatC


From owner-seamoby@diameter.org  Fri Mar  2 18:45:00 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA24801
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 18:45:00 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f22Mk2w17462
	for seamoby-list; Fri, 2 Mar 2001 14:46:02 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f22MijY17457
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 14:44:45 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id OAA28121;
	Fri, 2 Mar 2001 14:52:35 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f22MqXf05850;
	Fri, 2 Mar 2001 14:52:33 -0800
X-mProtect:  Fri, 2 Mar 2001 14:52:33 -0800 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90)
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdeuhpeR; Fri, 02 Mar 2001 14:52:21 PST
Message-ID: <3AA02427.59E2B600@iprg.nokia.com>
Date: Fri, 02 Mar 2001 14:52:23 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 2.2.6-RELEASE i386)
MIME-Version: 1.0
To: Gary Kenward <gkenward@nortelnetworks.com>
CC: seamoby_context@marvin.corpeast.baynetworks.com, pat.calhoun@eng.sun.com,
        seamoby@diameter.org
Subject: [seamoby] Re: Seamoby Context Transfer Requirements kick-off conference cal l, M           onday, March 5, 2001
References: <13E2EF604DE5D111B2E50000F80824E8057A8D38@zwdld001.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Gary Kenward wrote:
> >
> >
> > Hello Gary,
> >
> > I would like to say this meeting _cannot_ be considered as a
> > design team
> > meeting. First, you pulled out this meeting without
> > sufficient time for
> > everyone. Second, I would like to point out that the seamoby chair
> > should initiate such a meeting. Unless I am poorly informed,
> > you are not
> 
> The meeting was called at the request of the working group chair.
> Indeed, the chair request that the requirements work proceed
> as soon as possible.
> 

You SHOULD have stated this in your message.


> I have received about ten responses,
> and I believe 4 people could not attend out of the ten, including
> you.
> 

You should have stated this as well. 


> While some commented that the notification was short, you are the
> first to insinuate that there was any other motivation then simply
> to move on to the next phase. You are as wrong in that insinuation
> as you are in assuming that no one has responded.
> 

I was not insinuating anything. I was straight away wondering how you
could go ahead with the conference call when it looked from observing
the mailing list that there was no quorum. Is the mailing list broken
again (for me ) ? If the responses were in private correspondence, you
should have clearly stated it in your e-mail as you did above in your
reply.


> > meeting anyway.
> >
> > Unilateral, blanket positions are not very useful if you wish to
> > contribute constructively.
> 
> Ill-informed, aggravating accusations are specifically damaging
> to constructive contributions.
> 

If I was ill-informed, it was not entirely my fault. As a facilitator,
could you keep everyone properly informed and provide sufficient time to
respond ?
 

Regards,

-Rajeev

> >
> > Regards,
> >
> > -Rajeev
> 
> Gary
> 
> >
> >


From owner-seamoby@diameter.org  Fri Mar  2 21:07:56 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA27272
	for <seamoby-archive@odin.ietf.org>; Fri, 2 Mar 2001 21:07:55 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f231JQB19410
	for seamoby-list; Fri, 2 Mar 2001 17:19:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f231JNY19405
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 17:19:23 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA12928
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 17:27:19 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA01107
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 17:27:18 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (eastapp2.East.Sun.COM [129.148.162.99])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id RAA09789
	for <seamoby@diameter.org>; Fri, 2 Mar 2001 17:27:02 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Message-Id: <200103030127.RAA09789@heliopolis.Eng.Sun.COM>
Date: Fri, 2 Mar 2001 17:23:42 -0800
To: <seamoby@diameter.org>
Reply-To: <kempf@heliopolis.Eng.Sun.COM>
Subject: [seamoby] Paging Requirements
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Please send any requirements (including the location of drafts) to the
seamoby-paging@diameter.org list. Thanx.

		jak



From owner-seamoby@diameter.org  Mon Mar  5 10:58:38 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA18968
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 10:58:38 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25Eblv13083
	for seamoby-list; Mon, 5 Mar 2001 06:37:47 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25EbiT13078
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 06:37:44 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA06467;
	Sun, 4 Mar 2001 16:27:01 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA17837;
	Sun, 4 Mar 2001 16:27:01 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id QAA14992;
	Sun, 4 Mar 2001 16:26:54 -0800 (PST)
Date: Sun, 4 Mar 2001 16:22:29 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: RE: [seamoby] Yet Another BOF?
To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Cc: "Andrew T. Campbell" <campbell@comet.columbia.edu>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "'James Kempf'" <james.kempf@sun.com>, Phil_Neumiller@3Com.com,
        seamoby@diameter.org
In-Reply-To: "Your message with ID" <Roam.SIMC.2.0.6.983393383.20901.pcalhoun@nasnfs>
Message-ID: <Roam.SIMC.2.0.6.983751749.28177.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

All,

This is an old e-mail that was resent by someone at m018.com. Somehow, this
site is resending old e-mail from both seamoby and mobileip lists. I have had
to shutdown my list (as has mobileip), as we are being attacked quite
viciously by this site. I do not know of a way to re-enable the site and not
be attacked.

This morning I had over 1800 e-mails resent from this site to my box. I am
getting quite annoyed.

In short, disregard these e-mails.

PatC
> > >  However, as I have stated 
> > > numerous times,
> > > statements like "MIP is too slow" just doesn't cut it.  
> > 
> > Lets try it this way then - please shoot me down.
> 
> ok
> 
> > 
> > We clearly believe that micro-mobility means not invoking
> > the MIP HAs each time we handoff? So all the action must be local.
> > That excludes vanilla MIP as a solution and under those
> > conditions its slow and lossy, etc. 
> > 
> > So what is this local protocol? I would claim that trees,
> > levels of FAs and tunneling (the base MIP class) are 
> > costly (tunnel/detunel overhead/complexity)
> > and not robust (the tree of FAs, single gateways). 
> > I'm not digging here; just some unsubstantiated 
> > thoughts off the top of my head. 
> > 
> > The point that a number of people are making (and 
> > developing solutions for, e.g., CIP, Hawaii, etc.) 
> > is that if I'm forced to use FAs (trees and levels of them),
> > tunneling and MIP signaling to solve every new
> > wireless problem (e.g., QOS, fast handoff, etc.) 
> > that surfaces in IETF, then, how do we innovate 
> > and deliver new wireless IP technologies?  
> 
> Ahhh..... technical arguments. Good. This is all good. This is what we need.
> They are alot harder to defend than the "MIP is too slow" argument.
> 
> > Is this because people think that the investment in MIP
> > is so great that must reap dividend at no end? sister of
> > MIP, cousin of MIP, etc.
> 
> Sure, and I do understand where they stand, but our charter is not to save
> engineering work. It is to build what we need.
> 
> > Coupling each development to the base MIP mechanisms
> > (FAs, tunneling, MIP signaling) as a perquisite to
> > the development of new wireless IP protocols is a
> > little like driving a car with a straight-jacket on.
> > 
> > Building fast/seamless handoff, paging, context, 
> > QOS, etc. etc., on MIP is where we are heading today;
> > consensus or not; it looks to me its all engineered
> > that way? 
> 
> well, I haven't seen paging, context nor QoS being built on top of MIP, but
> perhaps I've missed something. Of course, I've seen individual contributions
> that propose this, but this is hardly a WG's work item.
> 
> > 
> > The goals should to let MIP be the macro-mobilty 
> > protocol to interwork with and allow 
> > new and innovative technologies with 
> > (for fast handoff, seamless, fast security, 
> > QOS, context, etc. etc.) to be created.
> 
> Sounds reasonable to me.
> 
> PatC




From owner-seamoby@diameter.org  Mon Mar  5 11:58:51 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA21311
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 11:58:51 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25EdTb13092
	for seamoby-list; Mon, 5 Mar 2001 06:39:29 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25EdQT13087
	for <seamoby@cdma-2000.org>; Mon, 5 Mar 2001 06:39:26 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA16142
	for <seamoby@cdma-2000.org>; Mon, 5 Mar 2001 06:47:30 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA12559
	for <seamoby@cdma-2000.org>; Mon, 5 Mar 2001 06:47:29 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id GAA19807
	for <seamoby@cdma-2000.org>; Mon, 5 Mar 2001 06:47:28 -0800 (PST)
Date: Mon, 5 Mar 2001 06:43:02 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] List problems
To: seamoby@cdma-2000.org
Message-ID: <Roam.SIMC.2.0.6.983803382.32213.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

All,

Yesterday morning I had to take down the list, in *hopes* that the korean site
times out, and stops forwarding me old e-mails. As most of you probably know,
the Mobile IP list is also being subjected to this attack.

I wrote an e-mail to the postmaster @ m018.com, but it unfortunately went
unanswered.

So my only recourse was to add a filter to disallow ANY IP traffic from that
site. Therefore, for those of you that will not be receiving any future
e-mails from the list, chances are your site is handled by m018.com.

If anyone has *any* other ideas, please do let me know.

PatC



From owner-seamoby@diameter.org  Mon Mar  5 12:08:04 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA21705
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 12:08:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25EhFY13166
	for seamoby-list; Mon, 5 Mar 2001 06:43:15 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from hotmail.com (f311.law7.hotmail.com [216.33.236.189])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25EhDT13161
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 06:43:13 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 5 Mar 2001 06:51:12 -0800
Received: from 63.78.179.4 by lw7fd.law7.hotmail.msn.com with HTTP;	Mon, 05 Mar 2001 14:51:11 GMT
X-Originating-IP: [63.78.179.4]
From: "Hemant Chaskar" <hchaskar@hotmail.com>
To: mobile-ip@sunroof.eng.sun.com
Cc: seamoby@diameter.org
Subject: [seamoby] I-D on MIP QoS Submitted
Date: Mon, 05 Mar 2001 14:51:11 
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_209f_406f_2843"
Message-ID: <F3116mqv5n9xVoqLRKh0001fc27@hotmail.com>
X-OriginalArrivalTime: 05 Mar 2001 14:51:12.0253 (UTC) FILETIME=[B8964AD0:01C0A583]
Sender: owner-seamoby@diameter.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_209f_406f_2843
Content-Type: text/plain; format=flowed

Hi,

Please note that we have submitted following I-D to draft directories. It is 
included in this email as well for quick retrieval. Here are the details of 
the draft:

Title: A Framework for QoS Support in Mobile IPv6
Authors: Hemant Chaskar and Rajeev Koodli
Filename: draft-chaskar-mobileip-qos-01.txt
(00 version was presented in San Diego meeting of MIP WG)

Abstract

This draft describes a solution to perform QoS signaling along
the new network path, when mobile node using Mobile IPv6
acquires a new care-of address. The solution is based on the
definition of new option called QoS OBJECT OPTION. This option
is included in the hop-by-hop extension header of certain
packets, preferably the ones carrying binding messages,
propagating between mobile node and correspondent node
or between mobile node and regional mobility agent(s). Such an
approach takes advantage of mobility signaling inherent in
Mobile IPv6 to program QoS forwarding treatment as well, along
the new network path. It naturally blends in with micro-mobility
techniques. Further, compared to using RSVP, our solution has
much smaller latency until QoS forwarding treatment is
programmed over the new network path after handover.


Thanks,
Hemant Chaskar
Nokia
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

------=_NextPart_000_209f_406f_2843
Content-Type: text/plain; name="draft-chaskar-mobileip-qos-01.txt"; format=flowed
Content-Disposition: attachment; filename="draft-chaskar-mobileip-qos-01.txt"
X-MIME-Autoconverted: from 8bit to quoted-printable by charizard.diameter.org id f25EhFY13166
Content-Transfer-Encoding: quoted-printable


IETF Mobile IP Working Group                          Hemant Chaskar
INTERNET-DRAFT                                         Rajeev Koodli
Expires: September 2001                        Nokia Research Center
                                                          March 2001

               A Framework for QoS Support in Mobile IPv6
                    draft-chaskar-mobileip-qos-01.txt

Status of This Memo

   This document is an Internet-Draft and is in full conformance
   with all provisions of Section 10 of RFC2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that
   other groups may also distribute working documents as Internet
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six
   months  and may be updated, replaced, or made obsolete by other
   documents at any time. It is inappropriate to use Internet-Drafts
   as reference material or to cite them other than as "work in
   progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.
   The  list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

Copyright Notice

   Copyright (c) The Internet Society (2001). All rights reserved.

Abstract

    This draft describes a solution to perform QoS signaling along
    the new network path, when mobile node using Mobile IPv6
    acquires a new care-of address. The solution is based on the
    definition of new option called QoS OBJECT OPTION. This option
    is included in the hop-by-hop extension header of certain
    packets, preferably the ones carrying binding messages,
    propagating between mobile node and correspondent node
    or between mobile node and regional mobility agent(s). Such an
    approach takes advantage of mobility signaling inherent in
    Mobile IPv6 to program QoS forwarding treatment as well, along
    the new network path. It naturally blends in with micro-mobility
    techniques. Further, compared to using RSVP, our solution has
    much smaller latency until QoS forwarding treatment is
    programmed over the new network path after handover.





Chaskar, Koodli                                             [Page i]

INTERNET-DRAFT        QoS Support in Mobile IPv6         March, 2001




                              Contents



Status of This Memo                                                i

Abstract                                                           i

1.0 Introduction                                                  1

1.1 Problem statement
1.2 Solution overview

2.0 Terminology and Abbreviations                                 2

3.0 Composition of QoS OBJECT OPTION                              3

4.0 Inclusion of QoS OBJECT OPTION in hop-by-hop extension header 4

4.1 Basic Mobile IPv6
4.2 Micro-mobility scenarios

5.0 Performance Considerations (Comparison with RSVP)             6

6.0 Processing of QoS OBJECT OPTION at Intermediate Networks      7

6.1 IntServ domain
6.2 MPLS domain
6.3 DiffServ domain

7.0 Security considerations  (TBD)                                9

8.0 Acknowledgment                                                9

9.0 References                                                   10

10.0 Addresses                                                   11













Chaskar, Koodli                                            [Page ii]

INTERNET-DRAFT        QoS Support in Mobile IPv6          March,2001

1.0 Introduction

   While Mobile IP [1] ensures correct and efficient routing of
   mobile node's (MN) packets as the MN changes its point of
   attachment with the Internet, the issue of Quality of Service
   (QoS) for MN's packet streams is not addressed yet. This document
   describes the problem statement, outlines a solution and provides
   comparison with existing (mobility-unaware) approaches such as
   RSVP [2] to QoS signaling.

1.1 Problem statement

   As an MN moves from one access router (AR) to another, the paths
   traversed by MN's packet streams with its correspondent nodes
   (CNs), may change. This is always true for the path in the access
   network to which MN is attached. In addition, handover between
   ARs in different access networks may cause the path traversed by
   MN's packet streams in the core network to change as well. If the
   MN's packet streams are QoS-sensitive, a mechanism is needed to
   signal desired QoS forwarding treatment along the new paths in
   the network. It is important to note that while the routing
   aspect of mobility has been addressed in Mobile IPv6, the problem
   of maintaining desired QoS forwarding treatment in the light of
   mobility has not been addressed.

   Subsequent to handover, the new end-to-end path between CN(s) and
   MN may span a number of networks (access and core) employing a
   variety of QoS schemes, notably IntServ [3] in access and
   MPLS [4] and DiffServ [5] in core. There may as well be best
   effort networks in the end-to-end path. Thus, as a basic
   requirement, mobility-aware QoS signaling mechanism must be
   capable of providing QoS forwarding information for MN's packet
   streams to relevant routers in different networks in the
   end-to-end path. The QoS signaling mechanism must have fast
   response time so that the latency between the time packets using
   the new care-of address (CoA) are released into the network and
   the time QoS forwarding information is signaled along the new
   path should be minimized. In other words, the mechanism must be
   able to make use of intrinsic handover signaling to minimize
   "QoS alignment" latency for MN's packet streams. Furthermore,
   any mobility-aware QoS signaling mechanism should be able to
   exploit micro-mobility [6,7] and fast handover [8] solutions in
   order to localize the extent of signaling to affected branches of
   the network only. Finally, such a mechanism should impose minimal
   requirements on the end terminals with limited processing power,
   memory and battery resources.

1.2 Solution overview

   Our solution is based on the use of new option called QoS OBJECT
   OPTION. It may contain a number of QoS OBJECTs, each of which
   corresponds to one unidirectional QoS-sensitive packet stream of

Chaskar, Koodli                                             [Page 1]

INTERNET-DRAFT        QoS Support in Mobile IPv6         March, 2001

   MN. The basic idea is to include QoS OBJECT OPTION in IPv6
   hop-by-hop extension header along with packets propagating in
   the same direction as the QoS-sensitive packet streams of MN.
   Since binding update (BU) is sent as soon as the data
   transmission from the new CoA is ready to begin, the QoS
   OBJECT OPTION sent along with it in hop-by-hop extension
   header, promptly triggers the necessary actions to set up QoS
   forwarding treatment along the new path. Same is true regarding
   binding acknowledgment (BA) when the packet streams in the
   direction from CN(s) to MN are considered. With basic Mobile
   IPv6, the binding messages travel end-to-end. Thus, the QoS
   object processing also spans end-to-end network path. With
   micro-mobility solutions, these messages travel only as far as
   the nearest mobility agent that needs to update its route table
   entry. Note that the QoS OBJECT OPTION also needs to travel only
   as far as the nearest node requiring an update to its route
   entry. Thus, by combining the transmission of QoS OBJECT OPTION
   with binding messages, a natural optimization is achieved with
   micro-mobility solutions. However, note that QoS object option
   may be included in hop-by-hop extension header of any other
   packet propagating in the same direction as QoS-sensitive packet
   stream.

   The actions taken by intermediate routers upon examining the QoS
   OBJECT OPTION in hop-by-hop extension header depend on
   the QoS scheme employed by their network domains. Generally, in
   access networks, QoS OBJECTs in QoS OBJECT OPTION will be used by
   all routers to program QoS forwarding treatment for MN's packets.
   In the core network, typically edge routers process the QoS
   OBJECT OPTION, while internal routers ignore it.

   Note that our approach does not relay on round-trip signaling
   such as PATH/RESV of RSVP, but rather performs programing of QoS
   forwarding treatment along the new network path in one pass.
   Also, this is done ahead of the time the packets using new CoA
   arrive at intermediate routers along the new end-to-end path.
   This minimizes the number of packets that would get default
   forwarding treatment at intermediate nodes due to lack of
   QoS forwarding information in those nodes after handover.

2.0 Terminology and Abbreviations

  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
   this document are to be interpreted as described in RFC 2119.

  MN: Mobile node
  CN: Correspondent node
  QoS: Quality of service
  CoA: Care-of-address
  HoA: Home address
  AR: Access router

Chaskar, Koodli                                             [Page 2]

INTERNET-DRAFT        QoS Support in Mobile IPv6         March, 2001

  BU/BA: Binding update/Binding acknowledgment
  ER: Edge router of network domain
  IR: Interior router of network domain
  MPLS: Multi-protocol label switching
  FEC: Forwarding equivalence class
  DiffServ: Differentiated services
  IntServ: Integrated services
  Uplink/Downlink direction: From MN/Towards MN

3.0 Composition of QoS OBJECT OPTION

   The QoS signaling solution described here uses a new IPv6
   extension header option called QoS OBJECT OPTION. The
   composition of QoS OBJECT OPTION is shown in Figure 1. It
   contains zero or more QoS OBJECTs in TLV format.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
                                   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1                                  |0|0|1| Opt Type| Opt Data Len  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2  |     Reserved  |        One or more QoS OBJECTs in TLV format
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

           Figure 1: Composition of QoS OBJECT OPTION

   The composition of a QoS OBJECT is shown in Figure 2. A QoS
   OBJECT is an extension of RSVP QoS and FILTER_SPEC objects.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
                   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1                  |    Reserved   | Object Length |QoS Requirement|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2  | Max Delay (16-bit integer) ms |Delay Jitter (16-bit integer)ms|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3  |     Average Data Rate (32-bit IEEE floating point number)     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4  |Burstiness:Token Bucket Size(32-bit IEEE floating point number)|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5  |      Peak Data Rate  (32-bit IEEE floating point number)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6  |            Minimum Policed Unit  (32-bit integer)             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
7  |           Maximum Packet Size  (32-bit integer)               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
8  |                                                               |
   |                                                               |
   |            Values of Packet Classification Parameters         |
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                     Figure 2: Composition of a QoS OBJECT
Chaskar, Koodli                                             [Page 3]

INTERNET-DRAFT        QoS Support in Mobile IPv6         March, 2001

   o QoS Requirement: This field describes the QoS requirement of
     the MN's packet stream in terms of traffic class. An example is
     the QoS specification in terms of delay sensitivity, such as
     interactive-delay sensitive, non-interactive delay sensitive or
     delay insensitive, as in UMTS QoS specification [9]. Another
     example is specification in terms of DiffServ PHB classes such
     as EF or AF. Yet another alternative is QoS specification in
     terms of IntServ classes such as guaranteed service or
     controlled load service. Some examples are,

     00000xxx: DiffServ EF PHB
     00001xxx: DiffServ AF PHB

     00010xxx: IntServ guaranteed service
     00011xxx: IntServ controlled load service

     00100xxx: UMTS traffic class

   o Delay specification: The fields "Max Delay" and "Delay Jitter"
     specify the end-to-end values of respective quantities in
     milliseconds that the packet stream can tolerate.

   o Traffic Volume: The fields Average Data Rate, Burstiness, Peak
     Data Rate, Minimum Policed Unit and Maximum Packet Size
     describe the volume and nature of traffic that the
     corresponding packet stream is expected to generate.

   o Packet Classification Parameters: This field provides values
     for parameters in packet headers that can be used for packet
     classification. In particular, it specifies a subset of TCP/UDP
     port numbers, IPv6 flow label and SPI corresponding to
     particular packet stream. Typically, source and destination IP
     addresses to be used for packet classification can be inferred
     from header of packet carrying QoS OBJECT OPTION.

4.0 Inclusion of QoS OBJECT OPTION in hop-by-hop extension header

   The basic idea here is to include QoS OBJECT OPTION containing
   QoS OBJECTs corresponding to MN's packet stream(s), in the
   hop-by-hop extension header along with the packet that
   propagates in the same direction as the corresponding packet
   stream(s). QoS OBJECTs in this option can then inform the routers
   at the intermediate network domains about the QoS forwarding
   requirement of the relevant packet streams. Routers make use of
   this information, in a manner that is consistent with the QoS
   scheme employed by their network domains (see Section 6), to
   immediately program proper QoS forwarding treatment for those
   packet stream(s).





Chaskar, Koodli                                             [Page 4]

INTERNET-DRAFT        QoS Support in Mobile IPv6         March, 2001

4.1 Basic Mobile IPv6

   In basic Mobile IPv6, MN sends BU to CN as soon as it is ready to
   use new CoA. QoS OBJECT OPTION containing QoS OBJECT(s)
   corresponding to uplink packet stream(s) SHOULD be included in
   hop-by-hop extension header with this BU. QoS OBJECT OPTION
   promptly triggers necessary processing at the intermediate
   routers so as to offer proper QoS forwarding treatment to MN's
   uplink packet streams along the new end-to-end path.

   By the same reasoning, QoS OBJECT OPTION containing QoS OBJECT(s)
   corresponding to downlink packet stream(s), SHOULD be included in
   hop-by-hop extension header along with BA that is sent
   from CN to MN.

   Note however that QoS OBJECT OPTION can be included in the
   hop-by-hop extension header of any packet that propagates
   in the same direction as the corresponding packet stream(s).

4.2 Micro-mobility scenarios

   Micro-mobility solutions introduce local mobility agents, such as
   a Gateway Mobility Agent (GMA) in Regional Registration or
   Mobility Anchor Point (MAP) in Hierarchical Mobile IPv6 approach
   for proxying a regional CoA. Regional CoA remains constant while
   the MN moves inside the visited domain. This approach alleviates
   the need for sending BUs to all the CNs for every handover. This
   conserves wireless bandwidth as well as reduces the signaling
   load caused by binding messages outside the visited domain. It
   decreases the latency associated with binding messages as they
   are sent only up to the local mobility agent.

   The proposed solution readily makes use of micro-mobility
   mechanisms, facilitating QoS modification along only those
   segments of end-to-end forwarding path that are affected by the
   MN=92s movement. The QoS OBJECT OPTION would be carried in the BU
   to the regional mobility agent, and the routers in the path
   traversed by BU process this hop-by-hop option, making
   modifications to their QoS forwarding engines as necessary.
   The BA from the regional mobility agent would trigger similar
   adjustments for QoS forwarding treatment for packets destined
   to the MN.

   We observe some significant performance benefits in combining QoS
   signaling with micro-mobility. First, the QoS signal
   itself would travel only as far as what is deemed necessary by
   the particular micro-mobility mechanism. This reduces the
   round-trip signaling latency. Incidentally, we note that with
   Regional Registrations for Mobile IPv6, this distance is up to
   the cross-over router, where as with HMIPv6, it is the number of
   hops up to MAP. Second, QoS object option with micro-mobility
   greatly enhances existing state re-usage. That is, the existing

Chaskar, Koodli                                             [Page 5]

INTERNET-DRAFT        QoS Support in Mobile IPv6         March, 2001

   QoS state beyond the GMA or the MAP need not be modified at all
   when the mobile node=92s movement is limited to the visited domain
   (implying that the Regional CoA does not change). Regional
   Registrations further extends this state re-use to the nodes
   within the visited domain itself. For example, when the mobility
   limits route changes to a node below the GMA in hierarchy, such
   as a cross-over router, the existing state above the cross-over
   state can be re-used, since those nodes do not perceive a change
   in the source address in the packets.

5.0 Performance Considerations (Comparison with RSVP)

   In this section, we compare the performance of QoS signaling
   approach proposed in this document to that of using RSVP for QoS
   signaling upon handover. The performance metric used is the
   latency between the time nodes (MN or CN) are ready to use new
   CoA and the time QoS forwarding requirement is signaled over the
   new forwarding path.

   We observe that RSVP introduces latency of about one round-trip
   time (between the MN and the CN) from the time packets using new
   CoA are released into the network until the time QoS forwarding
   treatment is programmed over the new path. Note that one
   end-to-end round-trip may involve, in the worst case, four
   traversals of wireless links. The worst case happens when both MN
   and CN are attached via low bandwidth wireless links. In that
   case, the packets released into the network during this time
   period would get default forwarding treatment at intermediate
   network domains. On the contrary, in our approach, programming
   of QoS forwarding treatment along the new end-to-end path is
   immediate. This is shown by the following illustration.

   Suppose MN is currently at CoA1. Consider data traffic from the
   CN towards the MN (downlink direction). The following events
   occur:

   o MN moves to CoA2 and sends BU from CoA2 to CN. BU reaches CN.
   CN sends BA to MN at CoA2.

              RSVP                |   HOP-by-HOP QoS OBJECT OPTION

   CN initiates RSVP signaling    | QoS OBJECT OPTION for downlink
   to program QoS forwarding      | packet stream(s) is included in
   treatment for downlink traffic | HOP-by-HOP OPTIONS EXTENSION
   over the new network path. For | HEADER along with the BA.
   this, CN sends RSVP PATH to MN |
   at CoA2.                       |

   o CN may start sending MN's packets to CoA2. These packets
   contain CoA2 as destination address.



Chaskar, Koodli                                             [Page 6]

INTERNET-DRAFT        QoS Support in Mobile IPv6         March, 2001

              RSVP                |   HOP-by-HOP QoS OBJECT OPTION

   Note that QoS forwarding       | QoS OBJECT OPTION precedes these
   treatment for these packets is | these packets and programs QoS
   not yet programmed along the   | forwarding treatment along the
   new network path. This is      | new network path. The processing
   certainly true for the segment | time of QoS OBJECT OPTION along
   of end-to-end path that was    | the new network path would
   not present in the old         | determine how quickly proper QoS
   end-to-end path. Even over     |forwarding treatment is offered.
   that segment of the end-to-end |In RSVP, this latency is at least
   path which remains unchanged   |one round-trip time plus the
   after handover, these packets  |processing time of PATH and RESV
   would get default forwarding   |messages along the new end-to-end
   treatment. This is because,    |network path.
   RSVP session is primarily      |
   identified by destination      |
   address which now has changed  |
   from CoA1 to CoA2.             |

   ----[One way end-to-end delay ellapses, then]----

   o BA reaches MN at CoA2.

   RSVP PATH reaches MN at CoA2. |
   MN sends RSVP RESV to CN.     |

   ----[One way end-to-end delay ellapses, then]----

             RSVP                |

   o RSVP RESV reaches CN.       |
                                 |
   It is at this time that the   |
   proper QoS forwarding         |
   treatment is programmed at the|
   intermediate nodes for packets|
   destined to CoA2.             |

   It is worth noting that the above drawback of RSVP's OPWA (One
   Pass with Advertisement) method is also observed in [10].It is
   shown in [10] that under certain assumptions, the severity of
   this drawback can be reduced. However, validity of those
   assumptions is not obvious.

6.0 Processing of QoS OBJECT OPTION at Intermediate Networks

   When QoS OBJECT OPTION is included in the HOP-by-HOP OPTIONS
   EXTENSION HEADER in IPv6 packet, intermediate routers MUST
   examine this option. The purpose of this is to obtain information
   about QoS forwarding requirement about MN's packet streams.


Chaskar, Koodli                                             [Page 7]

INTERNET-DRAFT        QoS Support in Mobile IPv6         March, 2001

   Typically, there are multiple and possibly heterogeneous (in
   terms of QoS mechanism employed) network domains in the
   end-to-end path. Here, a network domain is defined as a
   collection of network nodes (routers) that implements a
   particular QoS mechanism independently and under the same control

   framework. There are edge routers (ER) at the edge of these
   domains and internal routers (IR) inside the domains. Each of
   these domains may be a best-effort domain or may employ QoS
   mechanisms such as MPLS, DiffServ or IntServ. Typically, access
   networks would employ flow-based QoS mechanisms such as IntServ,
   while core network will use aggregate-based schemes such as MPLS
   and DiffServ. Note that QoS OBJECT contains enough information so
   that any of these QoS schemes can extract the information
   relevant to them from the QoS OBJECT. The actual mapping between
   QoS object parameters to the parameters used by different QoS
   schemes is implementation specific, and thus beyond the scope
   of this document. In the following, we outline the semantics of
   processing QoS OBJECT OPTION at ERs and IRs of these network
   domains.

6.1 IntServ domain

   In IntServ domain, there are two ways to process the QoS OBJECT
   OPTION. According to one method which fully complies with One
   Pass with Advertisement (OPWA) model of RSVP, ingress ER
   examines the QoS OBJECT OPTION in hop-by-hop extension header
   to determine QoS forwarding requirement of MN's packet
   streams. It also determines the egress ER of that network domain
   where MN's packets will be forwarded. Ingress ER sends RSVP PATH
   message to egress ER. Ingress ER MAY include (a version of) QoS
   OBJECT OPTION in _destination_ extension header of the
   packet carrying RSVP PATH message. This will provide egress ER
   with the information necessary to determine the actual resources
   that are required to be reserved. Egress ER sends RSVP RESV to
   ingress ER. Once ingress ER receives RESV from egress ER, it
   forwards the packet containing QoS OBJECT OPTION through the
   network domain. IRs in the network domain simply ignore the QoS
   OBJECT OPTION.

   The above method has the following drawback that is intrinsic to
   OPWA model of resource reservation of RSVP, when it is used in
   mobile environment. It takes one round trip time in the network
   domain before QoS forwarding treatment is programmed at the
   routers in the network domain. In other words, MN's packets that
   arrive at the ingress ER get default forwarding treatment until
   the time RESV reaches ingress ER. This drawback is eliminated if
   the following method of resource reservation is used instead.

   Ingress ER of IntServ network domain examines the QoS OBJECT
   OPTION and immediately performs reservation of resources such as
   buffer, bandwidth, priority etc. at that router. Ingress ER then

Chaskar, Koodli                                             [Page 8]

INTERNET-DRAFT        QoS Support in Mobile IPv6         March, 2001

   forwards the packet containing QoS OBJECT OPTION to next IR in
   the network domain. IR examines the QoS OBJECT OPTION and
   immediately performs resource reservation at that router. IR then
   forwards the packet to next IR in the network domain. This
   continues until the packet reaches egress ER which performs
   resource reservation at that router, and forwards the packet to
   next network domain.

6.2 MPLS domain

   Ingress ER at MPLS domain (often called edge label switching

   router (edge LSR)) determines the forwarding equivalence class
   (FEC) to which the packets of MN's packet stream(s) should belong
   to in that domain. This decision is based on the destination IP
   address of the packet and QoS forwarding requirement of packet
   stream(s). FEC translates to label switching path (LSP) over
   which the packets should be forwarded through that domain.
   Ingress ER may also use traffic volume parameters in QoS
   OBJECT(s) to perform admission control over those LSPs. Ingress
   ER creates FEC mapping context that would map subsequent packets
   of MN's packet stream(s) onto appropriate LSPs. Packet
   classification parameters in the QoS OBJECT(s) are used to set up
   FEC mapping context.

   Ingress ER then forwards the packet containing QoS OBJECT OPTION
   through the network domain using label based forwarding paradigm.
   As a result of this, IRs do not even see the IP header, and
   hence, do not process any hop-by-hop options.

6.3 DiffServ domain

   Ingress ER at DiffServ domain uses QoS OBJECT(s) in QoS OBJECT
   OPTION to program packet classification context for the packets
   of MN's packet stream(s). This context would assign appropriate
   differentiated services code point (DSCP) to subsequent packets
   of these packet stream(s). ER may also perform admission control
   to ensure that service level agreement (SLA) is not violated by
   the volume of traffic generated by these packet stream(s).

   IRs in DiffServ domain simply ignore the QoS OBJECT OPTION.

7.0 Security considerations

   To be discussed.

8.0 Acknowledgment

    Thanks are due to Charlie Perkins (Nokia) for his useful
    comments during the revision of this document.



Chaskar, Koodli                                             [Page 9]

INTERNET-DRAFT        QoS Support in Mobile IPv6         March, 2001

9.0. References

   [1] D. Johnson and C. Perkins. Mobility Support in IPv6. Internet
       Draft, Internet Engineering Task Force.
       draft-ietf-mobileip-ipv6-12.txt. April 2000.

   [2] R. Braden and L. Zhang. Resource ReSerVation Protocol (RSVP):
       Version 1 Functional Specification. Request for Comments
       (Standards track) 2205.  September 1997.

   [3] R. Braden, D. Clark, and S. Shenker. Integrated Services
       in the Internet Architecture: An Overview. Request for
       Comments (Informational) 1633. June 1994.

   [4] E. Rosen, A. Viswanathan, and R. Callon. Multiprotocol Label
       Switching Architecture. Internet Draft, Internet Engineering
       Task Force. draft-ietf-mpls-arch-06.txt. July 2000.

   [5] S. Blake et. al. An Architecture for Differentiated Services.
       Request for Comments (Informational) 2475. December 1998.

   [6] J. Malinen and C. Perkins. Mobile IPv6 Regional
       Registrations. Internet Draft, Internet Engineering Task
       Force. draft-malinen-mobileip-regreg6-00.txt. July 2000.

   [7] H. Soliman et. al. Hierarchical MIPv6 mobility management.
       Internet Draft, Internet Engineering Task Force.
       draft-soliman-mobileip-hmipv6-01.txt. September 2000.

   [8] C. Perkins et. al. Fast Handovers for Mobile IPv6. Internet
       Draft, Internet Engineering Task Force.
       draft-perkins-mobileip-handover-00.txt. November 2000.

   [9] 3GPP Technical Specification 23.107, Version 3.2.0: QoS
        Concept and Architecture, March 2000.

   [10] Michael Thomas. Analysis of Mobile IP and RSVP Interactions.
        Internet Draft, Internet Engineering Task Force.
        draft-thomas-seamoby-rsvp-analysis-00.txt. February 2001.














Chaskar, Koodli                                            [Page 10]

INTERNET-DRAFT        QoS Support in Mobile IPv6         March, 2001

10.0 Addresses

  The working group can be contacted via the current chairs:

    Basavaraj Patil                     Phil Roberts
    Nokia Corporation                   Motorola
    6000 Connection Drive               1501 West Shure Drive
    M/S M8-540
    Irving, Texas 75039                 Arlington Heights, IL 60004
    USA                                 USA
    Phone:  +1 972-894-6709             Phone:  +1 847-632-3148
    EMail:  Basavaraj.Patil@nokia.com   EMail:  QA3445@email.mot.com

  Questions about this memo can be directed to the authors:

   Hemant Chaskar
   Communication Systems Laboratory
   Nokia Research Center
   5 Wayside Road
   Burlington, MA 01803, USA
   Phone: +1 781-993-3785
   EMail: hemant.chaskar@nokia.com

   Rajeev Koodli
   Communication Systems Laboratory
   Nokia Research Center
   313 Fairchild Drive
   Mountain View, CA 94043, USA
   Phone: +1 650-625-2359
   EMail: rajeev.koodli@nokia.com























Chaskar, Koodli                                            [Page 11]


------=_NextPart_000_209f_406f_2843--


From owner-seamoby@diameter.org  Mon Mar  5 12:17:21 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA22110
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 12:17:20 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25Ejdc13175
	for seamoby-list; Mon, 5 Mar 2001 06:45:39 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from idcpa4.pa.interdigital.com (idcmail.interdigital.com [12.32.197.142])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25EjbT13170
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 06:45:37 -0800
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <DLAL4NHJ>; Mon, 5 Mar 2001 09:51:57 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D01F1F750@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>
To: "'kempf@heliopolis.Eng.Sun.COM'" <kempf@heliopolis.Eng.Sun.COM>,
        seamoby@diameter.org
Subject: RE: [seamoby] Paging requirements phase #1
Date: Mon, 5 Mar 2001 09:51:56 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

I have not been following this. Are we ready to start with the requirements
phase in "paging"?




-----Original Message-----
From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
Sent: Friday, March 02, 2001 8:24 PM
To: seamoby@diameter.org
Subject: [seamoby] Paging Requirements


Please send any requirements (including the location of drafts) to the
seamoby-paging@diameter.org list. Thanx.

		jak


From owner-seamoby@diameter.org  Mon Mar  5 12:17:41 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA22143
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 12:17:40 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25Epvd13222
	for seamoby-list; Mon, 5 Mar 2001 06:51:57 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25EprT13217
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 06:51:53 -0800
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f257ei224979
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 09:40:44 +0200 (EET)
Received: from esebh01nok.ntc.nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T521a943d2bac158f21115@esvir01nok.ntc.nokia.com>;
 Mon, 5 Mar 2001 09:40:40 +0200
Received: by esebh01nok.ntc.nokia.com with Internet Mail Service (5.5.2652.78)
	id <GCF7N7R1>; Mon, 5 Mar 2001 09:40:40 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680AB56@eseis04nok>
From: john.loughney@nokia.com
To: seamoby_context@marvin.corpeast.baynetworks.com
Cc: seamoby@diameter.org
Subject: [seamoby] RE: mondays conference call
Date: Mon, 5 Mar 2001 09:40:39 +0200 
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Gary,

> The first meeting will be Monday, March 12. The agenda remains the
> same, with the addition of a new item to determine there is a 
> consensus to select a new team leader. Although at this point, I am 
> unclear as to what constitutes a consensus.

Does this mean that you are stepping down?	

Also, about the change of times - this is a good thing, as I didn't
get the announcement of the conference call until this (Monday)
morning.

thanks,
John


From owner-seamoby@diameter.org  Mon Mar  5 12:26:20 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA22447
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 12:26:20 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25F57T13332
	for seamoby-list; Mon, 5 Mar 2001 07:05:07 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25F55T13327
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 07:05:05 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id HAA18845;
	Mon, 5 Mar 2001 07:13:18 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABY12234;
	Mon, 5 Mar 2001 07:13:00 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id HAA04723; Mon, 5 Mar 2001 07:12:59 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15011.44283.769856.977491@thomasm-u1.cisco.com>
Date: Mon, 5 Mar 2001 07:12:59 -0800 (PST)
To: <Hemant.Chaskar@nokia.com>
Cc: mat@cisco.com, hchaskar@hotmail.com, mobile-ip@sunroof.eng.sun.com,
        seamoby@diameter.org, mobile-ip@marvin.corpeast.baynetworks.com
Subject: RE: [seamoby] QoS and Mobile IP
In-Reply-To: <B9CFA6CE8FFDD211A1FB0008C7894E46027F4460@bseis01nok>
References: <B9CFA6CE8FFDD211A1FB0008C7894E46027F4460@bseis01nok>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hemant.Chaskar@nokia.com writes:
 >  > => The solution of enclosing QoS Object in hop-by-hop
 >  > extension header, preferably with binding messages, performs
 >  > fast reservation on forward path. 
 > 
 >    No it doesn't. If it needs to go clear back to the
 >    correspondent node to change filter specs, you're
 >    already too slow in the degeneate case. 
 > 
 > -----> No, you don't get the point still. You have to 
 > -----> realize that packet carrying QoS object PRECEDES any 
 > -----> data packets using new CoA. Please read the illustration that
 > -----> I gave in previous email again. Hence, QoS forwarding will
 > -----> be in place when these new CoA packets hit the intermediate
 > -----> routers. RSVP takes one round trip time for that. 

  What makes you think that other packets will not
  overtake the qos establishment packet? FIB based
  forwarding is a whole lot faster than installing
  a reservation.

	Mike


From owner-seamoby@diameter.org  Mon Mar  5 12:31:42 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA22633
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 12:31:41 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25FdG813454
	for seamoby-list; Mon, 5 Mar 2001 07:39:16 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25FdDT13449
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 07:39:13 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA29059;
	Mon, 5 Mar 2001 07:45:23 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA12280;
	Mon, 5 Mar 2001 07:45:22 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id HAA20448;
	Mon, 5 Mar 2001 07:45:20 -0800 (PST)
Date: Mon, 5 Mar 2001 07:40:53 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] Re: Spam idiots
To: Phil_Neumiller@3Com.com
Cc: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>,
        "Andrew T. Campbell" <campbell@comet.columbia.edu>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "'James Kempf'" <james.kempf@sun.com>, seamoby@diameter.org
In-Reply-To: "Your message with ID" <88256A06.00568B31.00@hqoutbound.ops.3com.com>
Message-ID: <Roam.SIMC.2.0.6.983806853.28014.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

An investigation is underway as we type...

PatC
> 
> 
> 
> Hi Pat,
> 
> Did you complain to the domain admins?  They can  almost always find
> spammers originating from their domains since they leave all kinds
> of digital footprints.
> 
> regards,
> 
> Phil
> 
> 
> 
> 
> 
> Pat Calhoun <pcalhoun@nasnfs.eng.sun.com> on 03/04/2001 06:22:29 PM
> 
> Please respond to Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
> 
> Sent by:  Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
> 
> 
> To:   Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
> cc:   "Andrew T. Campbell" <campbell@comet.columbia.edu>, "'Gary Kenward'"
>       <gkenward@nortelnetworks.com>, "'James Kempf'" <james.kempf@sun.com>,
> Phil
>       Neumiller/MW/US/3Com, seamoby@diameter.org
> Subject:  RE: [seamoby] Yet Another BOF?
> 
> 
> 
> All,
> 
> This is an old e-mail that was resent by someone at m018.com. Somehow, this
> site is resending old e-mail from both seamoby and mobileip lists. I have had
> to shutdown my list (as has mobileip), as we are being attacked quite
> viciously by this site. I do not know of a way to re-enable the site and not
> be attacked.
> 
> This morning I had over 1800 e-mails resent from this site to my box. I am
> getting quite annoyed.
> 
> In short, disregard these e-mails.
> 
> PatC
> > > >  However, as I have stated
> > > > numerous times,
> > > > statements like "MIP is too slow" just doesn't cut it.
> > >
> > > Lets try it this way then - please shoot me down.
> >
> > ok
> >
> > >
> > > We clearly believe that micro-mobility means not invoking
> > > the MIP HAs each time we handoff? So all the action must be local.
> > > That excludes vanilla MIP as a solution and under those
> > > conditions its slow and lossy, etc.
> > >
> > > So what is this local protocol? I would claim that trees,
> > > levels of FAs and tunneling (the base MIP class) are
> > > costly (tunnel/detunel overhead/complexity)
> > > and not robust (the tree of FAs, single gateways).
> > > I'm not digging here; just some unsubstantiated
> > > thoughts off the top of my head.
> > >
> > > The point that a number of people are making (and
> > > developing solutions for, e.g., CIP, Hawaii, etc.)
> > > is that if I'm forced to use FAs (trees and levels of them),
> > > tunneling and MIP signaling to solve every new
> > > wireless problem (e.g., QOS, fast handoff, etc.)
> > > that surfaces in IETF, then, how do we innovate
> > > and deliver new wireless IP technologies?
> >
> > Ahhh..... technical arguments. Good. This is all good. This is what we need.
> > They are alot harder to defend than the "MIP is too slow" argument.
> >
> > > Is this because people think that the investment in MIP
> > > is so great that must reap dividend at no end? sister of
> > > MIP, cousin of MIP, etc.
> >
> > Sure, and I do understand where they stand, but our charter is not to save
> > engineering work. It is to build what we need.
> >
> > > Coupling each development to the base MIP mechanisms
> > > (FAs, tunneling, MIP signaling) as a perquisite to
> > > the development of new wireless IP protocols is a
> > > little like driving a car with a straight-jacket on.
> > >
> > > Building fast/seamless handoff, paging, context,
> > > QOS, etc. etc., on MIP is where we are heading today;
> > > consensus or not; it looks to me its all engineered
> > > that way?
> >
> > well, I haven't seen paging, context nor QoS being built on top of MIP, but
> > perhaps I've missed something. Of course, I've seen individual contributions
> > that propose this, but this is hardly a WG's work item.
> >
> > >
> > > The goals should to let MIP be the macro-mobilty
> > > protocol to interwork with and allow
> > > new and innovative technologies with
> > > (for fast handoff, seamless, fast security,
> > > QOS, context, etc. etc.) to be created.
> >
> > Sounds reasonable to me.
> >
> > PatC
> 
> 
> 
> 
> 
> 




From owner-seamoby@diameter.org  Mon Mar  5 12:34:13 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA22807
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 12:34:08 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25Ewrj13290
	for seamoby-list; Mon, 5 Mar 2001 06:58:53 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25EwnT13285
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 06:58:49 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA12155;
	Mon, 5 Mar 2001 07:06:41 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA14564;
	Mon, 5 Mar 2001 07:06:40 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id HAA20072;
	Mon, 5 Mar 2001 07:06:39 -0800 (PST)
Date: Mon, 5 Mar 2001 07:02:14 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: Re: [seamoby] RE: mondays conference call
To: john.loughney@nokia.com
Cc: seamoby_context@marvin.corpeast.baynetworks.com, seamoby@diameter.org
In-Reply-To: "Your message with ID" <01D91AFB08B6D211BFD00008C7EABAE10680AB56@eseis04nok>
Message-ID: <Roam.SIMC.2.0.6.983804534.26094.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> Hi Gary,
> 
> > The first meeting will be Monday, March 12. The agenda remains the
> > same, with the addition of a new item to determine there is a 
> > consensus to select a new team leader. Although at this point, I am 
> > unclear as to what constitutes a consensus.
> 
> Does this mean that you are stepping down?

Not that I am aware of....
	
> 
> Also, about the change of times - this is a good thing, as I didn't
> get the announcement of the conference call until this (Monday)
> morning.

Yes, and I appologize. I had to take down the list due to some denial of
service attacks from a site in Korea. I really need to figure out how to get
back on track :(

PatC



From owner-seamoby@diameter.org  Mon Mar  5 12:45:13 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA23557
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 12:45:11 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25FaS613440
	for seamoby-list; Mon, 5 Mar 2001 07:36:28 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25FaPT13435
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 07:36:25 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f25Fgtr14264;
	Mon, 5 Mar 2001 07:42:59 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f25FiII04989;
	Mon, 5 Mar 2001 07:44:18 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A06.00569727 ; Mon, 5 Mar 2001 07:45:47 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
cc: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>,
        "Andrew T. Campbell" <campbell@comet.columbia.edu>,
        "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "'James Kempf'" <james.kempf@sun.com>, seamoby@diameter.org
Message-ID: <88256A06.00568B31.00@hqoutbound.ops.3com.com>
Date: Mon, 5 Mar 2001 09:42:35 -0600
Subject: [seamoby] Spam idiots
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk




Hi Pat,

Did you complain to the domain admins?  They can  almost always find
spammers originating from their domains since they leave all kinds
of digital footprints.

regards,

Phil





Pat Calhoun <pcalhoun@nasnfs.eng.sun.com> on 03/04/2001 06:22:29 PM

Please respond to Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>

Sent by:  Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>


To:   Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
cc:   "Andrew T. Campbell" <campbell@comet.columbia.edu>, "'Gary Kenward'"
      <gkenward@nortelnetworks.com>, "'James Kempf'" <james.kempf@sun.com>, Phil
      Neumiller/MW/US/3Com, seamoby@diameter.org
Subject:  RE: [seamoby] Yet Another BOF?



All,

This is an old e-mail that was resent by someone at m018.com. Somehow, this
site is resending old e-mail from both seamoby and mobileip lists. I have had
to shutdown my list (as has mobileip), as we are being attacked quite
viciously by this site. I do not know of a way to re-enable the site and not
be attacked.

This morning I had over 1800 e-mails resent from this site to my box. I am
getting quite annoyed.

In short, disregard these e-mails.

PatC
> > >  However, as I have stated
> > > numerous times,
> > > statements like "MIP is too slow" just doesn't cut it.
> >
> > Lets try it this way then - please shoot me down.
>
> ok
>
> >
> > We clearly believe that micro-mobility means not invoking
> > the MIP HAs each time we handoff? So all the action must be local.
> > That excludes vanilla MIP as a solution and under those
> > conditions its slow and lossy, etc.
> >
> > So what is this local protocol? I would claim that trees,
> > levels of FAs and tunneling (the base MIP class) are
> > costly (tunnel/detunel overhead/complexity)
> > and not robust (the tree of FAs, single gateways).
> > I'm not digging here; just some unsubstantiated
> > thoughts off the top of my head.
> >
> > The point that a number of people are making (and
> > developing solutions for, e.g., CIP, Hawaii, etc.)
> > is that if I'm forced to use FAs (trees and levels of them),
> > tunneling and MIP signaling to solve every new
> > wireless problem (e.g., QOS, fast handoff, etc.)
> > that surfaces in IETF, then, how do we innovate
> > and deliver new wireless IP technologies?
>
> Ahhh..... technical arguments. Good. This is all good. This is what we need.
> They are alot harder to defend than the "MIP is too slow" argument.
>
> > Is this because people think that the investment in MIP
> > is so great that must reap dividend at no end? sister of
> > MIP, cousin of MIP, etc.
>
> Sure, and I do understand where they stand, but our charter is not to save
> engineering work. It is to build what we need.
>
> > Coupling each development to the base MIP mechanisms
> > (FAs, tunneling, MIP signaling) as a perquisite to
> > the development of new wireless IP protocols is a
> > little like driving a car with a straight-jacket on.
> >
> > Building fast/seamless handoff, paging, context,
> > QOS, etc. etc., on MIP is where we are heading today;
> > consensus or not; it looks to me its all engineered
> > that way?
>
> well, I haven't seen paging, context nor QoS being built on top of MIP, but
> perhaps I've missed something. Of course, I've seen individual contributions
> that propose this, but this is hardly a WG's work item.
>
> >
> > The goals should to let MIP be the macro-mobilty
> > protocol to interwork with and allow
> > new and innovative technologies with
> > (for fast handoff, seamless, fast security,
> > QOS, context, etc. etc.) to be created.
>
> Sounds reasonable to me.
>
> PatC








From owner-seamoby@diameter.org  Mon Mar  5 12:59:13 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA24145
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 12:59:13 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25FnK713517
	for seamoby-list; Mon, 5 Mar 2001 07:49:20 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25FnIT13512
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 07:49:18 -0800
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f25FvIg25017
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 09:57:18 -0600 (CST)
Received: from daebh01nok.americas.nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T521aa34975ac12f255117@davir02nok.americas.nokia.com>;
 Mon, 5 Mar 2001 09:57:07 -0600
Received: by daebh01nok with Internet Mail Service (5.5.2652.78)
	id <GKQL0HG3>; Mon, 5 Mar 2001 09:57:07 -0600
Message-ID: <B9CFA6CE8FFDD211A1FB0008C7894E46027F4471@bseis01nok>
From: Hemant.Chaskar@nokia.com
To: mat@cisco.com
Cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org
Subject: [seamoby] Latency if QoS programming
Date: Mon, 5 Mar 2001 09:57:06 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Some packets may overtake the packet carrying QoS information packet. But
let us look at the following math. Assume that T is forwarding delay (not
counting processing time required) for a hop. Let P be the processing time
of PATH or RESV or QoS Object hop-by-hop option at a network node.

Assume 3 hops in the end-to-end path that are concerned with programming QoS
forwarding treatment. Let us look at the packet stream from CN to MN and let
us count the number of packets at each of these nodes that would get default
forwarding treatment due to lack of QoS forwarding information. Let us take
the time difference between the potential arrival of first packet at a
network node and the time QoS forwarding treatment is programmed at that
node as an indication of number of packets that would get default forwarding
treatment at that node. 

Let us indicate the node closest to CN by Node 1. I.e. I am assuming the
following scenario CN--->Node 1---->Node 2---->Node 3--->MN. I am also
assuming that PATH packet/QoS Object hop-by-hop option packet and first data
packet arrive at Node 1 one after another.


               RSVP                           QoS object hop-by-hop option

Node 1    3T+3P (for PATH) + 3T+3P (RESV)           P

Node 2    3T+3P (for PATH) + 2T+2P (RESV)           T+2P

Node 3    3T+3P (for PATH) + T+P  (RESV)            2T+3P

It can be seen that the latencies in second column (and hence number of
packets getting default treatment) are much smaller that those the first
one.

Hemant Chaskar
Nokia

-----Original Message-----
From: ext Michael Thomas [mailto:mat@cisco.com]
Sent: 05. March 2001 10:13
To: Hemant.Chaskar@nokia.com
Cc: mat@cisco.com; hchaskar@hotmail.com; mobile-ip@sunroof.eng.sun.com;
seamoby@diameter.org; mobile-ip@marvin.corpeast.baynetworks.com
Subject: RE: [seamoby] QoS and Mobile IP


Hemant.Chaskar@nokia.com writes:
 >  > => The solution of enclosing QoS Object in hop-by-hop
 >  > extension header, preferably with binding messages, performs
 >  > fast reservation on forward path. 
 > 
 >    No it doesn't. If it needs to go clear back to the
 >    correspondent node to change filter specs, you're
 >    already too slow in the degeneate case. 
 > 
 > -----> No, you don't get the point still. You have to 
 > -----> realize that packet carrying QoS object PRECEDES any 
 > -----> data packets using new CoA. Please read the illustration that
 > -----> I gave in previous email again. Hence, QoS forwarding will
 > -----> be in place when these new CoA packets hit the intermediate
 > -----> routers. RSVP takes one round trip time for that. 

  What makes you think that other packets will not
  overtake the qos establishment packet? FIB based
  forwarding is a whole lot faster than installing
  a reservation.

	Mike


From owner-seamoby@diameter.org  Mon Mar  5 14:12:05 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA28895
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 14:12:04 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25HOko14002
	for seamoby-list; Mon, 5 Mar 2001 09:24:46 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25HOhT13996
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 09:24:43 -0800
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Mon, 5 Mar 2001 10:57:55 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GFB8SY5W>; Mon, 5 Mar 2001 10:57:56 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D4D@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'seamoby_context'" <seamoby_context@marvin.baynetworks.com>
Cc: "'seamoby'" <seamoby@diameter.org>,
        "'Pat Calhoun'" <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] Seamoby Context Transfer Design Team Requirements kick-off confe rence 
         call, Monday, March 12, 2001, 11 am EST
Date: Mon, 5 Mar 2001 10:57:53 -0500
Importance: high
X-Priority: 1
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This email is formal request for participation in the next
Seamless Mobility Context Transfer Design Team conference call.

In the past we have held these calls on Monday mornings
at 11 am EST. I have tentatively scheduled the next meeting
for Monday, March 12, 2001 at 11 am EST. However, this time
can be changed *if* there is a consensus. Keep in mind that there
are participants on three continents, at least, and it is difficult
to accommodate everyone.

As I understand it, the design team's next task is the 
development of a *requirements* draft. We must complete this 
draft before the ADs will consider giving us the go-ahead to work on 
solutions. 

The *tentative* agenda is:
	 *	attendance, hellos, etc.
	 *	selection of an editor for the requirements draft
	 *	rules for authorship
	 *	discussion of format / table of contents
	 *	action items
	 *	meeting schedule

We have this week to modify this agenda.

The conference call information is:

Date: 			Monday, March 5, 2001
Time:			11 AM EST.
US Phone Number: 	972-684-6338
PassCode:		793142

I request that all replies to this email be copied to the
seamoby and seamoby_context lists to ensure that 
there is an open discussion and an archive.

Thank you,
Gary Kenward

PS  I assume that a consensus means 50% + 1 of the respondents.


From owner-seamoby@diameter.org  Mon Mar  5 14:14:32 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA28996
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 14:14:31 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25HA3213912
	for seamoby-list; Mon, 5 Mar 2001 09:10:03 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25HA1T13907
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 09:10:01 -0800
Received: from davir03nok.americas.nokia.com (davir03nok.americas.nokia.com [172.18.242.86])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f25HI5g07621
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 11:18:05 -0600 (CST)
Received: from daebh01nok.americas.nokia.com (unverified) by davir03nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T521aed40c1ac12f256081@davir03nok.americas.nokia.com>;
 Mon, 5 Mar 2001 11:17:54 -0600
Received: by daebh01nok with Internet Mail Service (5.5.2652.78)
	id <GKQL0253>; Mon, 5 Mar 2001 11:17:54 -0600
Message-ID: <B9CFA6CE8FFDD211A1FB0008C7894E46027F4473@bseis01nok>
From: Hemant.Chaskar@nokia.com
To: mat@cisco.com
Cc: mobile-ip@sunroof.eng.sun.com, seamoby@diameter.org,
        mobile-ip@marvin.corpeast.baynetworks.com
Subject: [seamoby] Latency in QoS programming
Date: Mon, 5 Mar 2001 11:17:53 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



-----Original Message-----
From: ext Michael Thomas [mailto:mat@cisco.com]
Sent: 05. March 2001 11:43
To: Hemant.Chaskar@nokia.com
Cc: mat@cisco.com; mobile-ip@sunroof.eng.sun.com
Subject: Latency if QoS programming



Hemant,

I'd have a lot more sympathy for this argument if
what you'd proposed is, essentially, RESV with
router alert.

==> Mike, 

==> No concept of router alert in IPv6

As it stands, your proposal does
not address:

- multicast

==> I replied in the earlier email that you do not need binding messages
with multicast. Clearly, this is not Mobile IP issue. Anything that does not
have binding messages in it is not Mobile IP issue.

- flow merging

==> No multicast issue, so no flow merging issue to be studied in Mobile IP.

- topology changes and localized healing

==> This is an interesting point. I will study this further. I have no
answer to it at this time.

- cryptographic identity

==> This is irrelevant. Let us stick to point.

- hopwise integrity

==> Irrelevant. Let us stick to point.

- policy based admission control

==> Irrelevant. This is implementation issue. IETF never addresses it. QoS
object has enough information in it for policy based admission control.

- flow aggregation

==> Irrelevant. I am not doing network traffic engineering with this scheme.
Go to MPLS WG to study this. It is router-router issue. Not stream-router
issue.

- admission based diffserv

==> Again, implementation issue. QoS object has sufficient information to
implement this. Creating interdomain SLAs is not done on a per stream basis.
When the stream arrives at DiffServ edge, edge router has to decide whether
it lies within SLA (this is nothing but what you call policy). Our QoS
object has sufficient information to implement this. QoS object will not do
SLA, it will provide information about packet stream to the module that
checks that SLA is not violated.

- tunneling

==> I don't understand this point.

- mpls-te 

==> Go to MPLS WG. It is router-router issue and not stream-router issue.
Using MPLS TE (scope of MPLS WG) edge router would know how much traffic
destined to particular egress and at what QoS it can admit over that LSP.
When packet carrying QoS object hits this edge router, that router uses
information in QoS object option to decide whether it can admit this packet
stream on that LSP.

- the mapping to various L2's

==> Irrelevant for this draft. Go to ISSLL and ask them to enlarge their
scope to include this solution.

and probably a half a dozen other things
I can't remember off the top of my head.

==> They are probably as irrelevant as some of the above issues.

In other words, in order to replace RSVP you are
going to have to reinvent RSVP. I frankly find no
motivation to do so, and in fact given recent
developments I think that RSVP may be salvageable
close to as-is and perform better than your
proposal.

==> I strongly suggest that we stick to the point and remain within the
scope of Mobile IP. We should not create confusion by bringing in irrelevant
issues just to push RSVP further. This way, we cannot arrive at a good
protocol to meet our performance needs.

==> Further, I don't need any sympathies as I am not zealous about one
protocol or the other. What I care about is technical merit and performance
of protocol! Also, you should look into bigger picture of IP QoS and
differentiate various issues in different scopes. End-to-end QoS cannot be
studied in one WG, neither can be done using one protocol. What we need is
protocol that integrates with different QoS modules that might exist in the
end-to-end path.

==> Hemant

		Mike

Hemant.Chaskar@nokia.com writes:
 > Some packets may overtake the packet carrying QoS information packet. But
 > let us look at the following math. Assume that T is forwarding delay (not
 > counting processing time required) for a hop. Let P be the processing
time
 > of PATH or RESV or QoS Object hop-by-hop option at a network node.
 > 
 > Assume 3 hops in the end-to-end path that are concerned with programming
QoS
 > forwarding treatment. Let us look at the packet stream from CN to MN and
let
 > us count the number of packets at each of these nodes that would get
default
 > forwarding treatment due to lack of QoS forwarding information. Let us
take
 > the time difference between the potential arrival of first packet at a
 > network node and the time QoS forwarding treatment is programmed at that
 > node as an indication of number of packets that would get default
forwarding
 > treatment at that node. 
 > 
 > Let us indicate the node closest to CN by Node 1. I.e. I am assuming the
 > following scenario CN--->Node 1---->Node 2---->Node 3--->MN. I am also
 > assuming that PATH packet/QoS Object hop-by-hop option packet and first
data
 > packet arrive at Node 1 one after another.
 > 
 > 
 >                RSVP                           QoS object hop-by-hop
option
 > 
 > Node 1    3T+3P (for PATH) + 3T+3P (RESV)           P
 > 
 > Node 2    3T+3P (for PATH) + 2T+2P (RESV)           T+2P
 > 
 > Node 3    3T+3P (for PATH) + T+P  (RESV)            2T+3P
 > 
 > It can be seen that the latencies in second column (and hence number of
 > packets getting default treatment) are much smaller that those the first
 > one.
 > 
 > Hemant Chaskar
 > Nokia
 > 
 > -----Original Message-----
 > From: ext Michael Thomas [mailto:mat@cisco.com]
 > Sent: 05. March 2001 10:13
 > To: Hemant.Chaskar@nokia.com
 > Cc: mat@cisco.com; hchaskar@hotmail.com; mobile-ip@sunroof.eng.sun.com;
 > seamoby@diameter.org; mobile-ip@marvin.corpeast.baynetworks.com
 > Subject: RE: [seamoby] QoS and Mobile IP
 > 
 > 
 > Hemant.Chaskar@nokia.com writes:
 >  >  > => The solution of enclosing QoS Object in hop-by-hop
 >  >  > extension header, preferably with binding messages, performs
 >  >  > fast reservation on forward path. 
 >  > 
 >  >    No it doesn't. If it needs to go clear back to the
 >  >    correspondent node to change filter specs, you're
 >  >    already too slow in the degeneate case. 
 >  > 
 >  > -----> No, you don't get the point still. You have to 
 >  > -----> realize that packet carrying QoS object PRECEDES any 
 >  > -----> data packets using new CoA. Please read the illustration that
 >  > -----> I gave in previous email again. Hence, QoS forwarding will
 >  > -----> be in place when these new CoA packets hit the intermediate
 >  > -----> routers. RSVP takes one round trip time for that. 
 > 
 >   What makes you think that other packets will not
 >   overtake the qos establishment packet? FIB based
 >   forwarding is a whole lot faster than installing
 >   a reservation.
 > 
 > 	Mike


From owner-seamoby@diameter.org  Mon Mar  5 14:22:29 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA29392
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 14:22:29 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25HjoH14097
	for seamoby-list; Mon, 5 Mar 2001 09:45:50 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25HjmT14092
	for <seamoby@cdma-2000.org>; Mon, 5 Mar 2001 09:45:48 -0800
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Mon, 5 Mar 2001 09:29:21 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GFB8S4TZ>; Mon, 5 Mar 2001 09:29:22 -0500
Message-ID: <E1A4B2CC91EBD1118A510000F80836F801FD071C@zwdld002.ca.nortel.com>
From: "Hongyi Li" <hyli@nortelnetworks.com>
To: "'Pat Calhoun'" <pcalhoun@nasnfs.eng.sun.com>
Cc: seamoby@cdma-2000.org
Subject: RE: MM Draft v1 WAS: [seamoby] Context Transfer and Paging
Date: Mon, 5 Mar 2001 09:29:20 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A580.AAC0E8A0"
X-Orig: <hyli@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A580.AAC0E8A0
Content-Type: text/plain;
	charset="iso-8859-1"

Hi Pat,
  Do you have idea about how do we precede with the requirements for
Micro-mobility routing protocol?

Hongyi

------_=_NextPart_001_01C0A580.AAC0E8A0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>RE: MM Draft v1 WAS: [seamoby] Context Transfer and Paging</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Hi Pat,</FONT>
<BR><FONT SIZE=2>&nbsp; Do you have idea about how do we precede with the requirements for</FONT>
<BR><FONT SIZE=2>Micro-mobility routing protocol?</FONT>
</P>

<P><FONT SIZE=2>Hongyi</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A580.AAC0E8A0--


From owner-seamoby@diameter.org  Mon Mar  5 15:27:02 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA02434
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 15:27:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25IwGb14323
	for seamoby-list; Mon, 5 Mar 2001 10:58:16 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25IwET14318
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 10:58:14 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GCB6RJ1Z>; Mon, 5 Mar 2001 14:06:17 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A05@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "'seamoby_context'"
	 <seamoby_context@marvin.baynetworks.com>
Cc: "'seamoby'" <seamoby@diameter.org>,
        "'Pat Calhoun'"
	 <pcalhoun@nasnfs.eng.sun.com>
Subject: RE: [seamoby] Seamoby Context Transfer Design Team Requirements k
	ick-off confe rence  call, Monday, March 12, 2001, 11 am EST
Date: Mon, 5 Mar 2001 14:06:17 -0500 
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


Sir,

I graciously accept your formal invitation for participation in the next
Seamless Mobility Context Transfer Design Team conference call.  

Thankyou.
 
- Kulwinder.

> -----Original Message-----
> From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
> Sent: Monday, March 05, 2001 10:58 AM
> To: 'seamoby_context'
> Cc: 'seamoby'; 'Pat Calhoun'
> Subject: [seamoby] Seamoby Context Transfer Design Team Requirements
> kick-off confe rence call, Monday, March 12, 2001, 11 am EST
> Importance: High
> Sensitivity: Confidential
> 
> 
> This email is formal request for participation in the next
> Seamless Mobility Context Transfer Design Team conference call.
> 
> In the past we have held these calls on Monday mornings
> at 11 am EST. I have tentatively scheduled the next meeting
> for Monday, March 12, 2001 at 11 am EST. However, this time
> can be changed *if* there is a consensus. Keep in mind that there
> are participants on three continents, at least, and it is difficult
> to accommodate everyone.
> 
> As I understand it, the design team's next task is the 
> development of a *requirements* draft. We must complete this 
> draft before the ADs will consider giving us the go-ahead to work on 
> solutions. 
> 
> The *tentative* agenda is:
> 	 *	attendance, hellos, etc.
> 	 *	selection of an editor for the requirements draft
> 	 *	rules for authorship
> 	 *	discussion of format / table of contents
> 	 *	action items
> 	 *	meeting schedule
> 
> We have this week to modify this agenda.
> 
> The conference call information is:
> 
> Date: 			Monday, March 5, 2001
> Time:			11 AM EST.
> US Phone Number: 	972-684-6338
> PassCode:		793142
> 
> I request that all replies to this email be copied to the
> seamoby and seamoby_context lists to ensure that 
> there is an open discussion and an archive.
> 
> Thank you,
> Gary Kenward
> 
> PS  I assume that a consensus means 50% + 1 of the respondents.
> 


From owner-seamoby@diameter.org  Mon Mar  5 16:21:10 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA04803
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 16:21:09 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25JAsv14364
	for seamoby-list; Mon, 5 Mar 2001 11:10:54 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from maild.telia.com (maild.telia.com [194.22.190.3])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25JApT14359
	for <seamoby@cdma-2000.org>; Mon, 5 Mar 2001 11:10:52 -0800
Received: from parchment (h242n1fls33o801.telia.com [213.64.180.242])
	by maild.telia.com (8.9.3/8.9.3) with SMTP id UAA19860;
	Mon, 5 Mar 2001 20:17:15 +0100 (CET)
Message-ID: <002201c0a5a8$ff1e52c0$0601a8c0@levkowetz.com>
From: "Henrik Levkowetz" <henrik@levkowetz.com>
To: "Gary Kenward" <gkenward@nortelnetworks.com>
Cc: <seamoby@cdma-2000.org>, <seamoby_context@standards.nortelnetworks.com>
References: <13E2EF604DE5D111B2E50000F80824E8057A8D4D@zwdld001.ca.nortel.com>
Subject: [seamoby] Re: Seamoby Context Transfer Design Team Requirements kick-off confe     rence call, Monday, March 12, 2001, 11 am EST
Date: Mon, 5 Mar 2001 20:17:59 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-Mimeole: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Gary,

    Although I did not reply, I saw the correspondence around a conference
call today Monday March 5th, and would have participated. Anyhow, I'll
try to attend the call on March 12th. I'm glad we can go forward with a
requirements draft.  The time is OK for me.

    Best regards,
        Henrik

----- Original Message ----- 
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: <seamoby_context@marvin.corpeast.baynetworks.com>
Cc: "'seamoby'" <seamoby@diameter.org>; "'Pat Calhoun'" <pcalhoun@nasnfs.Eng.Sun.COM>
Sent: Monday, March 05, 2001 16:57
Subject: Seamoby Context Transfer Design Team Requirements kick-off confe rence call, Monday, March 12, 2001, 11 am EST


> This email is formal request for participation in the next
> Seamless Mobility Context Transfer Design Team conference call.
> 
> In the past we have held these calls on Monday mornings
> at 11 am EST. I have tentatively scheduled the next meeting
> for Monday, March 12, 2001 at 11 am EST. However, this time
> can be changed *if* there is a consensus. Keep in mind that there
> are participants on three continents, at least, and it is difficult
> to accommodate everyone.
> 
> As I understand it, the design team's next task is the 
> development of a *requirements* draft. We must complete this 
> draft before the ADs will consider giving us the go-ahead to work on 
> solutions. 
> 
> The *tentative* agenda is:
> * attendance, hellos, etc.
> * selection of an editor for the requirements draft
> * rules for authorship
> * discussion of format / table of contents
> * action items
> * meeting schedule
> 
> We have this week to modify this agenda.
> 
> The conference call information is:
> 
> Date: Monday, March 5, 2001
> Time: 11 AM EST.
> US Phone Number: 972-684-6338
> PassCode: 793142
> 
> I request that all replies to this email be copied to the
> seamoby and seamoby_context lists to ensure that 
> there is an open discussion and an archive.
> 
> Thank you,
> Gary Kenward
> 
> PS  I assume that a consensus means 50% + 1 of the respondents.
> 



From owner-seamoby@diameter.org  Mon Mar  5 17:56:09 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA08831
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 17:56:08 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25KnVQ14610
	for seamoby-list; Mon, 5 Mar 2001 12:49:31 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25KmXT14605
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 12:48:33 -0800
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Mon, 5 Mar 2001 15:15:19 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GLQTSV84>; Mon, 5 Mar 2001 15:15:19 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D59@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'seamoby_context'" <seamoby_context@marvin.baynetworks.com>
Cc: "'seamoby'" <seamoby@diameter.org>,
        "'Pat Calhoun'" <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] Repeat: Seamoby Context Transfer Design Team Requirements kick-o ff 
         conference call, Monday, March 12, 2001, 11 am EST
Date: Mon, 5 Mar 2001 15:15:12 -0500
Importance: high
X-Priority: 1
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

(This is a repeat of a previous message. There was a typo in the date 
under the conference call information which has been fixed)

This email is formal request for participation in the next
Seamless Mobility Context Transfer Design Team conference call.

In the past we have held these calls on Monday mornings
at 11 am EST. I have tentatively scheduled the next meeting
for Monday, March 12, 2001 at 11 am EST. However, this time
can be changed *if* there is a consensus. Keep in mind that there
are participants on three continents, at least, and it is difficult
to accommodate everyone.

As I understand it, the design team's next task is the 
development of a *requirements* draft. We must complete this 
draft before the ADs will consider giving us the go-ahead to work on 
solutions. 

The *tentative* agenda is:
	 *	attendance, hellos, etc.
	 *	selection of an editor for the requirements draft
	 *	rules for authorship
	 *	discussion of format / table of contents
	 *	action items
	 *	meeting schedule

We have this week to modify this agenda.

The conference call information is:

Date: 			Monday, March 12,  2001
Time:			11 AM EST.
US Phone Number: 	972-684-6338
PassCode:		793142

I request that all replies to this email be copied to the
seamoby and seamoby_context lists to ensure that 
there is an open discussion and an archive.

Thank you,
Gary Kenward

PS  I assume that a consensus means 50% + 1 of the respondents.


From owner-seamoby@diameter.org  Mon Mar  5 17:59:19 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA08934
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 17:59:18 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25KOXw14559
	for seamoby-list; Mon, 5 Mar 2001 12:24:33 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25KOUT14554
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 12:24:30 -0800
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate2.mot.com (motgate2 2.1) with ESMTP id NAA27496 for <seamoby@diameter.org>; Mon, 5 Mar 2001 13:32:34 -0700 (MST)]
Received: [from il35exm01.cig.mot.com (IL35EXM01.cig.mot.com [160.19.16.101]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id NAA11779 for <seamoby@diameter.org>; Mon, 5 Mar 2001 13:32:33 -0700 (MST)]
Received: by IL35EXM01 with Internet Mail Service (5.5.2651.58)
	id <FZVW1KAK>; Mon, 5 Mar 2001 14:32:33 -0600
Message-ID: <0DF9920C9AD8D211AB0C0008C7CF1C9A062EDE65@il27exm02.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        seamoby_context@marvin.corpeast.baynetworks.com
Cc: "'seamoby'" <seamoby@diameter.org>,
        "'Pat Calhoun'"
	 <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] RE: Repeat: Seamoby Context Transfer Design Team Requirements kic
	k-o ff         conference call, Monday, March 12, 2001, 11 am EST
Date: Mon, 5 Mar 2001 14:32:30 -0600 
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Gary,

Thank you for all the good work so far and thank you for arranging the conference calls.
I should be able to attend the conference call.

Regards,
Madjid Nakhjiri

-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Monday, March 05, 2001 2:15 PM
To: seamoby_context@marvin.corpeast.baynetworks.com
Cc: 'seamoby'; 'Pat Calhoun'
Subject: Repeat: Seamoby Context Transfer Design Team Requirements
kick-o ff conference call, Monday, March 12, 2001, 11 am EST
Importance: High
Sensitivity: Confidential


(This is a repeat of a previous message. There was a typo in the date 
under the conference call information which has been fixed)

This email is formal request for participation in the next
Seamless Mobility Context Transfer Design Team conference call.

In the past we have held these calls on Monday mornings
at 11 am EST. I have tentatively scheduled the next meeting
for Monday, March 12, 2001 at 11 am EST. However, this time
can be changed *if* there is a consensus. Keep in mind that there
are participants on three continents, at least, and it is difficult
to accommodate everyone.

As I understand it, the design team's next task is the 
development of a *requirements* draft. We must complete this 
draft before the ADs will consider giving us the go-ahead to work on 
solutions. 

The *tentative* agenda is:
	 *	attendance, hellos, etc.
	 *	selection of an editor for the requirements draft
	 *	rules for authorship
	 *	discussion of format / table of contents
	 *	action items
	 *	meeting schedule

We have this week to modify this agenda.

The conference call information is:

Date: 			Monday, March 12,  2001
Time:			11 AM EST.
US Phone Number: 	972-684-6338
PassCode:		793142

I request that all replies to this email be copied to the
seamoby and seamoby_context lists to ensure that 
there is an open discussion and an archive.

Thank you,
Gary Kenward

PS  I assume that a consensus means 50% + 1 of the respondents.


From owner-seamoby@diameter.org  Mon Mar  5 18:01:33 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA09046
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 18:01:32 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25KxCm14641
	for seamoby-list; Mon, 5 Mar 2001 12:59:12 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25KwrT14636
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 12:58:54 -0800
Received: (from sob@localhost)
	by newdev.harvard.edu (8.9.3/8.9.3) id QAA06655;
	Mon, 5 Mar 2001 16:04:56 -0500 (EST)
Date: Mon, 5 Mar 2001 16:04:56 -0500 (EST)
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200103052104.QAA06655@newdev.harvard.edu>
To: gkenward@nortelnetworks.com, seamoby_context@marvin.baynetworks.com
Subject: Re: [seamoby] Repeat: Seamoby Context Transfer Design Team Requirements kick-o ff conference call, Monday, March 12, 2001, 11 am EST
Cc: pcalhoun@nasnfs.eng.sun.com, seamoby@diameter.org
Sender: owner-seamoby@diameter.org
Precedence: bulk

> PS  I assume that a consensus means 50% + 1 of the respondents.


"consensus" " General agreement or accord" (dict deff) - in the
context of the IETF normally consensus means more than 80 or 90%

Scott


From owner-seamoby@diameter.org  Mon Mar  5 18:58:12 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA10829
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 18:58:11 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25MPZE14940
	for seamoby-list; Mon, 5 Mar 2001 14:25:35 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25MPWT14935;
	Mon, 5 Mar 2001 14:25:32 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA16143;
	Mon, 5 Mar 2001 14:33:36 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA04729;
	Mon, 5 Mar 2001 14:33:36 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id OAA06461;
	Mon, 5 Mar 2001 14:33:35 -0800 (PST)
Message-Id: <200103052233.OAA06461@heliopolis.Eng.Sun.COM>
Date: Mon, 5 Mar 2001 14:33:35 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: [seamoby] Re: [seamoby-paging] Fwd: No I-D action yet
To: seamoby-paging@diameter.org, pcalhoun@nasnfs.eng.sun.com,
        behcet.sarikaya@usa.alcatel.com, seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 8d/o50Tp2njVSjmZGe3CSQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Behcet,

I have been trying to get a discussion of paging requirements on the
seamoby-paging list. Your draft is a good start, however, I think the
draft needs some clean up and we need to make sure that the requirements
collected from other memebers of the design team are also included. Would you 
like to be the requirements draft editor? 

If so, then I would suggest that you take the time slot for "ongoing
work" to present the state of the requirements discussion on the
seamoby-paging list, including your draft.

		jak



From owner-seamoby@diameter.org  Mon Mar  5 19:29:03 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA11956
	for <seamoby-archive@odin.ietf.org>; Mon, 5 Mar 2001 19:29:02 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f25MDg814882
	for seamoby-list; Mon, 5 Mar 2001 14:13:42 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f25MDeT14877
	for <seamoby@diameter.org>; Mon, 5 Mar 2001 14:13:40 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Mon, 5 Mar 2001 17:12:52 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GLQTSZM4>; Mon, 5 Mar 2001 17:12:49 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D5D@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Scott Bradner'" <sob@harvard.edu>,
        seamoby_context@marvin.baynetworks.com
Cc: pcalhoun@nasnfs.eng.sun.com, seamoby@diameter.org
Subject: RE: [seamoby] Repeat: Seamoby Context Transfer Design Team Requi 
         rements kick-o ff conference call, Monday, March 12, 2001, 11 am EST
Date: Mon, 5 Mar 2001 17:12:44 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A5C1.67661B70"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A5C1.67661B70
Content-Type: text/plain;
	charset="iso-8859-1"

No problem.

Thanks for the clarification.

Gary


> -----Original Message-----
> From: Scott Bradner [mailto:sob@harvard.edu]
> Sent: Monday, March 05, 2001 4:05 PM
> To: Kenward, Gary [WDLN2:AN10:EXCH];
> seamoby_context@marvin.baynetworks.com
> Cc: pcalhoun@nasnfs.eng.sun.com; seamoby@diameter.org
> Subject: Re: [seamoby] Repeat: Seamoby Context Transfer Design Team
> Requirements kick-o ff conference call, Monday, March 12, 2001, 11 am
> EST
> 
> 
> > PS  I assume that a consensus means 50% + 1 of the respondents.
> 
> 
> "consensus" " General agreement or accord" (dict deff) - in the
> context of the IETF normally consensus means more than 80 or 90%
> 
> Scott
> 

------_=_NextPart_001_01C0A5C1.67661B70
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: [seamoby] Repeat: Seamoby Context Transfer Design Team  =
Requirements kick-o ff conference call, Monday, March 12, 2001, 11 am  =
EST</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>No problem.</FONT>
</P>

<P><FONT SIZE=3D2>Thanks for the clarification.</FONT>
</P>

<P><FONT SIZE=3D2>Gary</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Scott Bradner [<A =
HREF=3D"mailto:sob@harvard.edu">mailto:sob@harvard.edu</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Monday, March 05, 2001 4:05 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Kenward, Gary [WDLN2:AN10:EXCH];</FONT>
<BR><FONT SIZE=3D2>&gt; seamoby_context@marvin.baynetworks.com</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: pcalhoun@nasnfs.eng.sun.com; =
seamoby@diameter.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [seamoby] Repeat: Seamoby Context =
Transfer Design Team</FONT>
<BR><FONT SIZE=3D2>&gt; Requirements kick-o ff conference call, Monday, =
March 12, 2001, 11 am</FONT>
<BR><FONT SIZE=3D2>&gt; EST</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; PS&nbsp; I assume that a consensus means =
50% + 1 of the respondents.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &quot;consensus&quot; &quot; General agreement =
or accord&quot; (dict deff) - in the</FONT>
<BR><FONT SIZE=3D2>&gt; context of the IETF normally consensus means =
more than 80 or 90%</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Scott</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A5C1.67661B70--


From owner-seamoby@diameter.org  Tue Mar  6 10:25:57 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA14406
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 10:25:56 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f26Dpx117785
	for seamoby-list; Tue, 6 Mar 2001 05:51:59 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from idcpa4.pa.interdigital.com (idcmail.interdigital.com [12.32.197.142])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f26DpvT17780
	for <seamoby@cdma-2000.org>; Tue, 6 Mar 2001 05:51:57 -0800
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <DLAL4PDW>; Tue, 6 Mar 2001 08:58:18 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D01F1F753@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>
Cc: "'pcalhoun@nasnfs.eng.sun.com'" <pcalhoun@nasnfs.eng.sun.com>,
        "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Paging requirements phase #2
Date: Tue, 6 Mar 2001 08:58:14 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


James,

I had not realized that the requirements phase for "paging" had even started
yet?
From what you say below, it would appear you already have a draft -- is this
true?
I did want to make some contributions to the "requirements", thus is it too
late now?

Sharif


-----Original Message-----
From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
Sent: Monday, March 05, 2001 5:35 PM
To: Sharif.Shahrier@InterDigital.com
Subject: RE: [seamoby] Paging requirements phase #1


Yes, I sent a list and Behcet from Alcatel has a draft that I would like
to see become the base for the working group draft.

	jak


From owner-seamoby@diameter.org  Tue Mar  6 13:20:41 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA20441
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 13:20:39 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f26GWt018190
	for seamoby-list; Tue, 6 Mar 2001 08:32:55 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f26GWrT18185
	for <seamoby@cdma-2000.org>; Tue, 6 Mar 2001 08:32:53 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA04588;
	Tue, 6 Mar 2001 08:40:58 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA14042;
	Tue, 6 Mar 2001 08:40:56 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id IAA22833;
	Tue, 6 Mar 2001 08:40:56 -0800 (PST)
Message-Id: <200103061640.IAA22833@heliopolis.Eng.Sun.COM>
Date: Tue, 6 Mar 2001 08:40:56 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] Paging requirements phase #2
To: Sharif.Shahrier@interdigital.com
Cc: seamoby@cdma-2000.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Ba+KDUqcTDYJk9pRh4fKzA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

The requirements discussion has just started. There is an individual
draft that has some potential to become a working group draft, but it
needs work and input from other working group participants. You
are welcome to submit requirements too, please send them to 
seamoby-paging@diameter.org.

This is where we are at. 

		jak

>From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
>To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>
>Cc: "'pcalhoun@nasnfs.eng.sun.com'" <pcalhoun@nasnfs.Eng.Sun.COM>, 
"'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
>Subject: RE: [seamoby] Paging requirements phase #2
>Date: Tue, 6 Mar 2001 08:58:14 -0500 
>MIME-Version: 1.0
>
>
>James,
>
>I had not realized that the requirements phase for "paging" had even started
>yet?
>>From what you say below, it would appear you already have a draft -- is this
>true?
>I did want to make some contributions to the "requirements", thus is it too
>late now?
>
>Sharif
>
>
>-----Original Message-----
>From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
>Sent: Monday, March 05, 2001 5:35 PM
>To: Sharif.Shahrier@InterDigital.com
>Subject: RE: [seamoby] Paging requirements phase #1
>
>
>Yes, I sent a list and Behcet from Alcatel has a draft that I would like
>to see become the base for the working group draft.
>
>	jak



From owner-seamoby@diameter.org  Tue Mar  6 15:04:20 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA25422
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 15:04:20 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f26I8wB18422
	for seamoby-list; Tue, 6 Mar 2001 10:08:58 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f26I8uT18417
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 10:08:56 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id KAA20022;
	Tue, 6 Mar 2001 10:12:09 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ACB01218;
	Tue, 6 Mar 2001 10:11:49 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA19272; Tue, 6 Mar 2001 10:11:49 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15013.10341.186392.374180@thomasm-u1.cisco.com>
Date: Tue, 6 Mar 2001 10:11:49 -0800 (PST)
To: Kulwinder Atwal <KAtwal@zucotto.com>
Cc: "'Charles E. Perkins'" <charliep@iprg.nokia.com>, seamoby@diameter.org,
        Gary Kenward <gkenward@nortelnetworks.com>
Subject: RE: [seamoby] MANET Critique  ( was  Yet Another BOF?
In-Reply-To: <6833D86F1B05CA4FBAB3C73DD98BD8B90D29EE@NEPTUNE.zucotto.com>
References: <6833D86F1B05CA4FBAB3C73DD98BD8B90D29EE@NEPTUNE.zucotto.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Kulwinder Atwal writes:
 > Unfortunately, I cannot think of an AD HOC network where this is a problem.
 > Maybe, your intent is to suggest it as a solution for Bluetooth?

   []

   I'm sorry, but Bluetooth is not the center of the Universe
   and your characterization of MANET as having no importance
   to anything known seems rather harsh and short-sighted. 
   I've read the TORA draft and it does seem like it has
   some interesting properties given a local routing based
   solution being bandied around. I've not read AODV so
   don't have an specific opinion about it.

   If it doesn't work well for Bluetooth, then
   well, it doesn't work well for Bluetooth. I'm
   not in a position to comment on your analysis,
   but I can tell when babies are being ejected
   with the bathwater.

	    Mike


From owner-seamoby@diameter.org  Tue Mar  6 15:22:18 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA26382
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 15:22:17 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f26IGbZ18469
	for seamoby-list; Tue, 6 Mar 2001 10:16:37 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from idcpa4.pa.interdigital.com (idcmail.interdigital.com [12.32.197.142])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f26IGZT18464
	for <seamoby@cdma-2000.org>; Tue, 6 Mar 2001 10:16:35 -0800
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <DLAL4P57>; Tue, 6 Mar 2001 13:22:57 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D01F1F755@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        "Shahrier, Sharif M."
	 <Sharif.Shahrier@interdigital.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Paging requirements phase #2
Date: Tue, 6 Mar 2001 13:22:47 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

James,

Could you please tell me what is the name of the draft, and can I access it
from the usual
I-D repository?

Sharif

-----Original Message-----
From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
Sent: Tuesday, March 06, 2001 11:41 AM
To: Sharif.Shahrier@InterDigital.com
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] Paging requirements phase #2


The requirements discussion has just started. There is an individual
draft that has some potential to become a working group draft, but it
needs work and input from other working group participants. You
are welcome to submit requirements too, please send them to 
seamoby-paging@diameter.org.

This is where we are at. 

		jak

>From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
>To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>
>Cc: "'pcalhoun@nasnfs.eng.sun.com'" <pcalhoun@nasnfs.Eng.Sun.COM>, 
"'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
>Subject: RE: [seamoby] Paging requirements phase #2
>Date: Tue, 6 Mar 2001 08:58:14 -0500 
>MIME-Version: 1.0
>
>
>James,
>
>I had not realized that the requirements phase for "paging" had even
started
>yet?
>>From what you say below, it would appear you already have a draft -- is
this
>true?
>I did want to make some contributions to the "requirements", thus is it too
>late now?
>
>Sharif
>
>
>-----Original Message-----
>From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
>Sent: Monday, March 05, 2001 5:35 PM
>To: Sharif.Shahrier@InterDigital.com
>Subject: RE: [seamoby] Paging requirements phase #1
>
>
>Yes, I sent a list and Behcet from Alcatel has a draft that I would like
>to see become the base for the working group draft.
>
>	jak


From owner-seamoby@diameter.org  Tue Mar  6 16:30:28 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA28999
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 16:30:28 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f26JdC918701
	for seamoby-list; Tue, 6 Mar 2001 11:39:12 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f26JdAT18696
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 11:39:10 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f26JjS014875;
	Tue, 6 Mar 2001 11:45:28 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f26JkpI13410;
	Tue, 6 Mar 2001 11:46:51 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A07.006CCAB1 ; Tue, 6 Mar 2001 11:48:17 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: Michael Thomas <mat@cisco.com>
cc: Kulwinder Atwal <KAtwal@zucotto.com>,
        "'Charles E. Perkins'" <charliep@iprg.nokia.com>, seamoby@diameter.org,
        Gary Kenward <gkenward@nortelnetworks.com>
Message-ID: <88256A07.006CC86B.00@hqoutbound.ops.3com.com>
Date: Tue, 6 Mar 2001 13:45:38 -0600
Subject: RE: [seamoby] MANET Critique ( was Yet Another BOF?
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk



What I never understood is why didn't Bluetooth just pick one of the MANET
ad hoc routing standards and  and run with it?

Pick TORA?  Pick AODV?  I don't care. Just run with something.    I guess I am
the
evil bandy abouter, but not without the justification that something scalable
will arive
someday.  My feeling is that we can get a few hops standardized now and
into consumer devices now and not have to wait until the cows come home.
Does the IETF have to move this slow?  Internet time is like watching paint
dry these days...

Thanks,

Phil





Sent by:  Michael Thomas <mat@cisco.com>


To:   Kulwinder Atwal <KAtwal@zucotto.com>
cc:   "'Charles E. Perkins'" <charliep@iprg.nokia.com>, seamoby@diameter.org,
      Gary Kenward <gkenward@nortelnetworks.com> (Phil Neumiller/MW/US/3Com)
Subject:  RE: [seamoby] MANET Critique  ( was  Yet Another BOF?

Kulwinder Atwal writes:
   solution being bandied around. I've not read AODV so






From owner-seamoby@diameter.org  Tue Mar  6 17:11:34 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA00464
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 17:11:33 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f26K0x018766
	for seamoby-list; Tue, 6 Mar 2001 12:00:59 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f26K0vT18761
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 12:00:57 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id MAA01146;
	Tue, 6 Mar 2001 12:09:00 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f26K8vq25617;
	Tue, 6 Mar 2001 12:08:57 -0800
X-mProtect:  Tue, 6 Mar 2001 12:08:57 -0800 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdwOgXwP; Tue, 06 Mar 2001 12:07:24 PST
Message-ID: <3AA5437D.D5CF06C4@iprg.nokia.com>
Date: Tue, 06 Mar 2001 12:07:26 -0800
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Phil_Neumiller@3Com.com
CC: seamoby@diameter.org
Subject: Re: [seamoby] MANET Critique ( was Yet Another BOF?
References: <88256A07.006CC86B.00@hqoutbound.ops.3com.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello Phil,

I'd like to suggest a very slight modification to your proposal.

Why didn't Bluetooth _participate_ in the [manet] work?
I am 99.99% confident in stating that any of the authors of
protocols submitted to [manet] would have been delighted
to respond to design concerns that might have been voiced
by Bluetooth proponents -- perhaps to the point of redesigning
the basic protocols as needed.

Instead, we seem to have been blindsided and then accused
of being ignorant of their requirements.

Determining the final outcome of such conflicts is, indeed,
slightly less quick than watching paint dry -- and not really
quite as much fun.

Regards,
Charlie P.




Phil_Neumiller@3com.com wrote:
> 
> What I never understood is why didn't Bluetooth just pick one of the MANET
> ad hoc routing standards and  and run with it?
> 
> Pick TORA?  Pick AODV?  I don't care. Just run with something.    I guess I am
> the
> evil bandy abouter, but not without the justification that something scalable
> will arive
> someday.  My feeling is that we can get a few hops standardized now and
> into consumer devices now and not have to wait until the cows come home.
> Does the IETF have to move this slow?  Internet time is like watching paint
> dry these days...
> 
> Thanks,
> 
> Phil
> 
> Sent by:  Michael Thomas <mat@cisco.com>
> 
> To:   Kulwinder Atwal <KAtwal@zucotto.com>
> cc:   "'Charles E. Perkins'" <charliep@iprg.nokia.com>, seamoby@diameter.org,
>       Gary Kenward <gkenward@nortelnetworks.com> (Phil Neumiller/MW/US/3Com)
> Subject:  RE: [seamoby] MANET Critique  ( was  Yet Another BOF?
> 
> Kulwinder Atwal writes:
>    solution being bandied around. I've not read AODV so


From owner-seamoby@diameter.org  Tue Mar  6 17:52:10 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA01666
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 17:52:10 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f26KOLc18861
	for seamoby-list; Tue, 6 Mar 2001 12:24:21 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f26KOJT18856
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 12:24:19 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GNPD3MAV>; Tue, 6 Mar 2001 15:32:26 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A16@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Michael Thomas'" <mat@cisco.com>,
        Kulwinder Atwal
	 <KAtwal@herc.zucotto.com>
Cc: "'Charles E. Perkins'" <charliep@iprg.nokia.com>, seamoby@diameter.org,
        Gary Kenward <gkenward@nortelnetworks.com>
Subject: RE: [seamoby] MANET Critique  ( was  Yet Another BOF?
Date: Tue, 6 Mar 2001 15:32:25 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

> -----Original Message-----
> From: Michael Thomas [mailto:mat@cisco.com]
> Sent: Tuesday, March 06, 2001 1:12 PM
> To: Kulwinder Atwal
> Cc: 'Charles E. Perkins'; seamoby@diameter.org; Gary Kenward
> Subject: RE: [seamoby] MANET Critique ( was Yet Another BOF?
> 
> 
> Kulwinder Atwal writes:
>  > Unfortunately, I cannot think of an AD HOC network where 
> this is a problem.
>  > Maybe, your intent is to suggest it as a solution for Bluetooth?
> 
>    []
> 
>    I'm sorry, but Bluetooth is not the center of the Universe
>    and your characterization of MANET as having no importance
>    to anything known seems rather harsh and short-sighted. 

Upon reflection it did seem rather harsh.  What I was hoping for were
examples of ADOV use.

>    I've read the TORA draft and it does seem like it has
>    some interesting properties given a local routing based
>    solution being bandied around. I've not read AODV so
>    don't have an specific opinion about it.

I looked over the TORA draft it seems like a start, although some sections
are missing like security.  But, perhaps security can be dealt with by other
means.

What I am really afraid of is, us getting into a MANET rathole without some
technology examples for us to test  MANET approaches on.  Maybe 802.11 is
another candidate.

> 	    Mike
> 


From owner-seamoby@diameter.org  Tue Mar  6 18:01:43 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA02018
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 18:01:42 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f26KW7B18917
	for seamoby-list; Tue, 6 Mar 2001 12:32:07 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f26KW5T18912
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 12:32:05 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GNPD3MBA>; Tue, 6 Mar 2001 15:40:13 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A17@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Phil_Neumiller@3com.com'" <Phil_Neumiller@3Com.com>,
        Michael Thomas
	 <mat@cisco.com>
Cc: Kulwinder Atwal <KAtwal@herc.zucotto.com>,
        "'Charles E. Perkins'"
	 <charliep@iprg.nokia.com>,
        seamoby@diameter.org, Gary Kenward
	 <gkenward@nortelnetworks.com>
Subject: RE: [seamoby] MANET Critique ( was Yet Another BOF?
Date: Tue, 6 Mar 2001 15:40:12 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Phil_Neumiller@3com.com [mailto:Phil_Neumiller@3com.com]
> Sent: Tuesday, March 06, 2001 2:46 PM
> To: Michael Thomas
> Cc: Kulwinder Atwal; 'Charles E. Perkins'; seamoby@diameter.org; Gary
> Kenward
> Subject: RE: [seamoby] MANET Critique ( was Yet Another BOF?
> 
> 
> 
> 
> What I never understood is why didn't Bluetooth just pick one 
> of the MANET
> ad hoc routing standards and  and run with it?

I guess the answer is nobody thought that far ahead.  It started out as just
a 'cable replacement' technology.  A wireless RS-232.

> 
> Pick TORA?  Pick AODV?  I don't care. Just run with 
> something.

The technology netural place for it may be on top of IP.  In which case the
place and time for that discussion may be here in the IETF with people just
like yourself.

- Kulwinder.


From owner-seamoby@diameter.org  Tue Mar  6 19:34:49 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA05147
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 19:34:48 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f26Lvc419177
	for seamoby-list; Tue, 6 Mar 2001 13:57:38 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f26LvaT19172
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 13:57:36 -0800
Received: from zrchb200.us.nortel.com by smtprch1.nortel.com;
          Tue, 6 Mar 2001 14:46:16 -0600
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GMXHAJDQ>; Tue, 6 Mar 2001 14:42:41 -0600
Message-ID: <85AA7486A2C1D411BCA20000F8073E4351C71F@crchy271.us.nortel.com>
From: "Glenn Morrow" <gmorrow@nortelnetworks.com>
To: "'Michael Thomas'" <mat@cisco.com>
Cc: "'Charles E. Perkins'" <charliep@iprg.nokia.com>, seamoby@diameter.org,
        "Gary Kenward" <gkenward@nortelnetworks.com>,
        Kulwinder Atwal <KAtwal@zucotto.com>
Subject: RE: [seamoby] MANET Critique ( was Yet Another BOF?
Date: Tue, 6 Mar 2001 14:42:37 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A67D.FAB877D0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A67D.FAB877D0
Content-Type: text/plain

Mike,

What purpose are you serving with statements like the one below? 

Please go and get yourself a copy of good book on logical argument
(Aristotle might do fine) and please discover the definition of something
called a "logical-fallacy".

You also might look some common 7 letter colloquialisms related to
biological waste disposal systems that one might describe you as.

I suggest you take a few minutes out of your day to read this as well:

http://www.ietf.org/internet-drafts/draft-ietf-poisson-code-02.txt

In particular, I suggest you pay close attention to item 2 of the document.

Your blantant disrespect to litterally everyone is bordering on intolerable
levels. You are "the" "poster boy" for the need of a code and perhaps a
"baby" that could use some "ejecting" yourself. 


Have a nice day.

Glenn



Michael Thomas writes:
----------------------------

>  I'm
>    not in a position to comment on your analysis,
>    but I can tell when babies are being ejected
>    with the bathwater.
> 
> 	    Mike

------_=_NextPart_001_01C0A67D.FAB877D0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: [seamoby] MANET Critique ( was Yet Another BOF?</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Mike,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">What purpose are you =
serving with statements like the one below? </FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Please go and get =
yourself a copy of good book on logical argument (Aristotle might do =
fine) and please discover the definition of something called a =
&quot;logical-fallacy&quot;.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">You also might look =
some common 7 letter colloquialisms related to biological waste =
disposal systems that one might describe you as.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I suggest you take a =
few minutes out of your day to read this as well:</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-poisson-code-02.t=
xt" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-poisson=
-code-02.txt</A></FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">In particular, I =
suggest you pay close attention to item 2 of the document.</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Your blantant =
disrespect to litterally everyone is bordering on intolerable levels. =
You are &quot;the&quot; &quot;poster boy&quot; for the need of a code =
and perhaps a &quot;baby&quot; that could use some &quot;ejecting&quot; =
yourself. </FONT></P>
<BR>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Have a nice =
day.</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Glenn</FONT>
</P>
<BR>
<BR>

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">Michael Thomas =
writes:</FONT>
<BR><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">----------------------------</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;I'm</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; not in a position to =
comment on your analysis,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; but I can tell when =
babies are being ejected</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; with the =
bathwater.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp; Mike</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A67D.FAB877D0--


From owner-seamoby@diameter.org  Tue Mar  6 19:50:33 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA05407
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 19:50:32 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f26NCua19390
	for seamoby-list; Tue, 6 Mar 2001 15:12:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from c007.snv.cp.net (c007-h012.c007.snv.cp.net [209.228.33.219])
	by charizard.diameter.org (8.11.3/8.11.3) with SMTP id f26NCsT19385
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 15:12:54 -0800
Received: (cpmta 5425 invoked from network); 6 Mar 2001 15:20:53 -0800
Received: from dsl-64-193-0-129.telocity.com (HELO PhilsSony) (64.193.0.129)
  by smtp.telocity.com (209.228.33.219) with SMTP; 6 Mar 2001 15:20:53 -0800
X-Sent: 6 Mar 2001 23:20:53 GMT
Message-ID: <001101c0a694$4c93d020$6501a8c0@mw.3com.com>
From: "Phillip Neumiller" <neumiller@telocity.com>
To: "Kulwinder Atwal" <kulwinder.atwal@zucotto.com>,
        "'Phil_Neumiller@3com.com'" <Phil_Neumiller@3Com.com>,
        "Michael Thomas" <mat@cisco.com>
Cc: "Kulwinder Atwal" <KAtwal@herc.zucotto.com>,
        "'Charles E. Perkins'" <charliep@iprg.nokia.com>,
        <seamoby@diameter.org>
References: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A17@NEPTUNE.zucotto.com>
Subject: Re: [seamoby] MANET Critique ( was Yet Another BOF?
Date: Tue, 6 Mar 2001 17:22:22 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Well I suggested this would be a problem over a year ago.  I guess I was a
henny penny back then
saying "Bluetooth is coming and guess what guys its NOT going to be MANET.
I posted this to
the Bluetooth SIG and MANET and it sparked a yawn of a thread (I do recall
Charlie perking up
to his credit :-)  Here we are a year later and Bluetooth (which was clearly
overhyped) barely has
a workable IP binding.  What to do?  Maybe you are right Kulwinder.  1st
things 1st.  Lets get the
IP binding fixed up and then worry about ad hoc netwoking in the IETF
sense???

My two cents,

-Phil


----- Original Message -----
From: "Kulwinder Atwal" <kulwinder.atwal@zucotto.com>
To: "'Phil_Neumiller@3com.com'" <Phil_Neumiller@3Com.com>; "Michael Thomas"
<mat@cisco.com>
Cc: "Kulwinder Atwal" <KAtwal@herc.zucotto.com>; "'Charles E. Perkins'"
<charliep@iprg.nokia.com>; <seamoby@diameter.org>; "Gary Kenward"
<gkenward@nortelnetworks.com>
Sent: Tuesday, March 06, 2001 2:40 PM
Subject: RE: [seamoby] MANET Critique ( was Yet Another BOF?


>
>
> > -----Original Message-----
> > From: Phil_Neumiller@3com.com [mailto:Phil_Neumiller@3com.com]
> > Sent: Tuesday, March 06, 2001 2:46 PM
> > To: Michael Thomas
> > Cc: Kulwinder Atwal; 'Charles E. Perkins'; seamoby@diameter.org; Gary
> > Kenward
> > Subject: RE: [seamoby] MANET Critique ( was Yet Another BOF?
> >
> >
> >
> >
> > What I never understood is why didn't Bluetooth just pick one
> > of the MANET
> > ad hoc routing standards and  and run with it?
>
> I guess the answer is nobody thought that far ahead.  It started out as
just
> a 'cable replacement' technology.  A wireless RS-232.
>
> >
> > Pick TORA?  Pick AODV?  I don't care. Just run with
> > something.
>
> The technology netural place for it may be on top of IP.  In which case
the
> place and time for that discussion may be here in the IETF with people
just
> like yourself.
>
> - Kulwinder.
>



From owner-seamoby@diameter.org  Tue Mar  6 20:18:11 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA05906
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 20:18:10 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f26Ndg419453
	for seamoby-list; Tue, 6 Mar 2001 15:39:42 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from cs.tamu.edu (IDENT:0@clavin.cs.tamu.edu [128.194.130.106])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f26NdeT19448
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 15:39:41 -0800
Received: from sun.cs.tamu.edu (IDENT:2654@sun [128.194.135.14])
	by cs.tamu.edu (8.11.0/8.11.0) with ESMTP id f26NlmI05159;
	Tue, 6 Mar 2001 17:47:48 -0600 (CST)
Received: (from vaidya@localhost)
	by sun.cs.tamu.edu (8.11.0/8.11.0) id f26Nk6V28361;
	Tue, 6 Mar 2001 17:46:06 -0600 (CST)
Date: Tue, 6 Mar 2001 17:46:06 -0600 (CST)
From: Nitin H Vaidya <vaidya@cs.tamu.edu>
Message-Id: <200103062346.f26Nk6V28361@sun.cs.tamu.edu>
To: Phil_Neumiller@3Com.com
Subject: RE: [seamoby] MANET Critique ( was Yet Another BOF?
Cc: seamoby@diameter.org
Sender: owner-seamoby@diameter.org
Precedence: bulk


  >> From owner-seamoby@diameter.org Tue Mar  6 15:45:03 2001
  >> 
  >> What I never understood is why didn't Bluetooth just pick one of the MANET
  >> ad hoc routing standards and  and run with it?

I guess partly because, without some changes, these protocols won't
necessarily work on BlueTooth. I am no BlueTooth expert, but
as I understand, different piconets in vicinity of each other
operate on different "channels", which is a slightly different
environment than the single channel environment used in evaluating
the typical MANET proposals. So, at least, some caution is called for.

Besides, perhaps more importantly, it is not obvious (to me) that the
mobility scenarios that MANET working group tends to worry about most 
terribly relevant to the typical applications of BlueTooth.
As would be intuitive, differences in performance of the various
MANET proposals becomes more interesting when mobility is "high"
(meaning that links tend to break often).

  >> Pick TORA?  Pick AODV?  I don't care. Just run with something.    I guess I am
  >> the
  >> evil bandy abouter, but not without the justification that something scalable
  >> will arive
  >> someday.  My feeling is that we can get a few hops standardized now and
  >> into consumer devices now and not have to wait until the cows come home.
  >> Does the IETF have to move this slow?  Internet time is like watching paint
  >> dry these days...

Before one decides whether it is worth watching the paint dry
or not, it would be good to know whether "typical" BlueTooth networks
will change topology frequently or not. If not, then
you are dealing with a much simpler problem, and may be able to
use/adapt proposals from other IETF routing area working groups
as well.

To put it differently, let us not equate "ad hoc"
with high rate of topology change. When topology change is
infrequent, in my view, routing "overhead" is not as important
an issue, as the "quality" chosen routes.

Cheerio.

- nitin


  >> 
  >> Thanks,
  >> 
  >> Phil
  >> 



From owner-seamoby@diameter.org  Tue Mar  6 20:31:56 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA06193
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 20:31:55 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2704Ig19514
	for seamoby-list; Tue, 6 Mar 2001 16:04:18 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2704GT19509
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 16:04:16 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA19204;
	Tue, 6 Mar 2001 16:12:14 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA20249;
	Tue, 6 Mar 2001 16:12:14 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id QAA11942;
	Tue, 6 Mar 2001 16:12:13 -0800 (PST)
Message-Id: <200103070012.QAA11942@heliopolis.Eng.Sun.COM>
Date: Tue, 6 Mar 2001 16:12:13 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: [seamoby] How to Convince the BARB to work with IETF?
To: charliep@iprg.nokia.com, Phil_Neumiller@3Com.com,
        kulwinder.atwal@zucotto.com
Cc: seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: PwI/dba2Fj1k3NnU3FleyA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Kulwinder,

Well, this account is certainly a cause for concern. 

Do you think the upcoming Bluetooth BOF will be enough to convince
the BARB that IETF is "moving in the direction of Bluetooth"? 

The problem is that IETF is a rather big beast and I don't think the
optical networking guys care much about Bluetooth. If what the BARB
means is that IETF mobility solutions are moving toward accommodating
Bluetooth, then I am  not exactly sure what they want. 

Most IETF technologies are designed to be broadly implementable on various link
layers. There are specific WGs that implement specific L3 technologies
on specific L2  (example: the Intserv on Specific L2 WG). Up 
till now, that has not been the case with mobility technologies, probably
because of two reasons:

	- Wireless LAN technologies don't need much help getting the
	IP mobility technologies implemented on them. In fact, one
	can argue that most IP mobility technologies were designed
	with wireless LANs in mind.
	
	- The cellular industry, which has been the other big consumer
	of IETF mobility protocols, has its own two SDOs which have
	been working together with IETF in their own ways. This has
	typically involved doing their own thing as far as their own L2
	is concerned and coming to IETF when they need something changed
	at L3. There have been a few cases where changes have been
	needed (authentication, special handling in MIPv4 when the 
	FA is not one hop from the access point, perhaps fast handoff),
	there may be more upcoming (maybe paging and context transfer). 
	
Do you think the BARB wants a series of "X on Y" 
working groups where X is a particular mobility technology (manet, mobile-ip,
maybe micromo, maybe paging, maybe context transfer) and Y is a particular
link layer (Bluetooth, 802.11, etc.)? Or, specifically, do they want 
such a working group for Bluetooth? How likely is such a working group
to be successful when the Bluetooth SIGs seem to have difficulty
communicating information between themselves? How do you think IETF can work 
together with the Bluetooth SIG to develop the kinds of L3 protocols that will 
work on PANs?

I'm really confused.

		jak


>X-Authentication-Warning: charizard.diameter.org: majordomo set sender to 
owner-seamoby@diameter.org using -f
>From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
>To: "'Charles E. Perkins'" <charliep@iprg.nokia.com>, Phil_Neumiller@3Com.com
>Cc: seamoby@diameter.org
>Subject: RE: [seamoby] MANET Critique ( was Yet Another BOF?
>Date: Tue, 6 Mar 2001 18:42:10 -0500 
>MIME-Version: 1.0
>
>Well, here's a look inside the 'sausage factory'.
>
>I raised these very concerns, and many others with a member of the BARB
>(Bluetooth Architechure Review Board) over the weekend and yesterday.  The
>BARB has similiar responsibilities as the IESG.  It oversees the SIG Working
>Groups, sets the technical direction of the SIG and reports directly to the
>SIG Board of Directors.
>
>There is no "official SIG position".  Even a Director of the Board, when
>speaking publically is giving a personal opinion.  The SIG has no
>spokesperson.  If you hear anyone at the BOF talking as if there was an
>"official SIG position", please feel free to correct them.  
>
>The WGs have a history of claiming a very wide scope which prevents others
>from innovating in that space.
>Further, they have in the past, chosen to work in secrecy releasing no more
>that some Power Point to most SIG members.  All SIG members are under NDA,
>therefore the only reason one can think of for this is the competive
>advantage of WG members.  This has been a sore point amoung many SIG
>members.
>
>For the first time, yesterday the PAN WG released its technical docs for
>review and feedback from all SIG members.  Today, the Printing WG did the
>same.
>
>In Phase I (Ethernet over Bluetooth), the PAN WG aimed a mobility within a
>piconet.  In Phase II, the PAN WG plans to decide whether to go with a layer
>3 approach for mobility outside of a piconet.  I have stated that Phase II
>will require changes to IETF protocols, and at least an IP over Bluetooth
>solution.  Phase II cannot occur without IETF involvement.  Further, I
>stated that the IETF is moving at a faster pace, with a more comprehensive
>and robust mobility solution in several WGs, whereas the SIG has just the
>PAN WG. Therefore, I proposed that Phase II be done in the IETF.
>
>The BARB view seems to be,"Well the IETF did not have an IP over Bluetooth
>solution when the PAN WG was formed."   I pointed out that the IETF is not
>capable of reading the minds of the PAN WG and BARB members.  The view in
>the BARB seems to be, change will happen when they "see the IETF moving a
>direction that fits with Bluetooth". 
>
>I hope you will raise your concerns at the BOF and on the pre-BOF mailing
>list.
>
>- Kulwinder.
>
>> -----Original Message-----
>> From: Charles E. Perkins [mailto:charliep@iprg.nokia.com]
>> Sent: Tuesday, March 06, 2001 3:07 PM
>> To: Phil_Neumiller@3com.com
>> Cc: seamoby@diameter.org
>> Subject: Re: [seamoby] MANET Critique ( was Yet Another BOF?
>> 
>> 
>> 
>> Hello Phil,
>> 
>> I'd like to suggest a very slight modification to your proposal.
>> 
>> Why didn't Bluetooth _participate_ in the [manet] work?
>> I am 99.99% confident in stating that any of the authors of
>> protocols submitted to [manet] would have been delighted
>> to respond to design concerns that might have been voiced
>> by Bluetooth proponents -- perhaps to the point of redesigning
>> the basic protocols as needed.
>> 
>> Instead, we seem to have been blindsided and then accused
>> of being ignorant of their requirements.
>> 
>> Determining the final outcome of such conflicts is, indeed,
>> slightly less quick than watching paint dry -- and not really
>> quite as much fun.
>> 
>> Regards,
>> Charlie P.
>> 
>> 
>> 
>> 
>> Phil_Neumiller@3com.com wrote:
>> > 
>> > What I never understood is why didn't Bluetooth just pick 
>> one of the MANET
>> > ad hoc routing standards and  and run with it?
>> > 
>> > Pick TORA?  Pick AODV?  I don't care. Just run with 
>> something.    I guess I am
>> > the
>> > evil bandy abouter, but not without the justification that 
>> something scalable
>> > will arive
>> > someday.  My feeling is that we can get a few hops 
>> standardized now and
>> > into consumer devices now and not have to wait until the 
>> cows come home.
>> > Does the IETF have to move this slow?  Internet time is 
>> like watching paint
>> > dry these days...
>> > 
>> > Thanks,
>> > 
>> > Phil
>> > 
>> > Sent by:  Michael Thomas <mat@cisco.com>
>> > 
>> > To:   Kulwinder Atwal <KAtwal@zucotto.com>
>> > cc:   "'Charles E. Perkins'" <charliep@iprg.nokia.com>, 
>> seamoby@diameter.org,
>> >       Gary Kenward <gkenward@nortelnetworks.com> (Phil 
>> Neumiller/MW/US/3Com)
>> > Subject:  RE: [seamoby] MANET Critique  ( was  Yet Another BOF?
>> > 
>> > Kulwinder Atwal writes:
>> >    solution being bandied around. I've not read AODV so
>> 



From owner-seamoby@diameter.org  Tue Mar  6 20:42:38 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA06403
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 20:42:37 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f26NY6g19441
	for seamoby-list; Tue, 6 Mar 2001 15:34:06 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f26NY4T19436
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 15:34:04 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GNPD3MHA>; Tue, 6 Mar 2001 18:42:11 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A1A@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Charles E. Perkins'" <charliep@iprg.nokia.com>, Phil_Neumiller@3Com.com
Cc: seamoby@diameter.org
Subject: RE: [seamoby] MANET Critique ( was Yet Another BOF?
Date: Tue, 6 Mar 2001 18:42:10 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Well, here's a look inside the 'sausage factory'.

I raised these very concerns, and many others with a member of the BARB
(Bluetooth Architechure Review Board) over the weekend and yesterday.  The
BARB has similiar responsibilities as the IESG.  It oversees the SIG Working
Groups, sets the technical direction of the SIG and reports directly to the
SIG Board of Directors.

There is no "official SIG position".  Even a Director of the Board, when
speaking publically is giving a personal opinion.  The SIG has no
spokesperson.  If you hear anyone at the BOF talking as if there was an
"official SIG position", please feel free to correct them.  

The WGs have a history of claiming a very wide scope which prevents others
from innovating in that space.
Further, they have in the past, chosen to work in secrecy releasing no more
that some Power Point to most SIG members.  All SIG members are under NDA,
therefore the only reason one can think of for this is the competive
advantage of WG members.  This has been a sore point amoung many SIG
members.

For the first time, yesterday the PAN WG released its technical docs for
review and feedback from all SIG members.  Today, the Printing WG did the
same.

In Phase I (Ethernet over Bluetooth), the PAN WG aimed a mobility within a
piconet.  In Phase II, the PAN WG plans to decide whether to go with a layer
3 approach for mobility outside of a piconet.  I have stated that Phase II
will require changes to IETF protocols, and at least an IP over Bluetooth
solution.  Phase II cannot occur without IETF involvement.  Further, I
stated that the IETF is moving at a faster pace, with a more comprehensive
and robust mobility solution in several WGs, whereas the SIG has just the
PAN WG. Therefore, I proposed that Phase II be done in the IETF.

The BARB view seems to be,"Well the IETF did not have an IP over Bluetooth
solution when the PAN WG was formed."   I pointed out that the IETF is not
capable of reading the minds of the PAN WG and BARB members.  The view in
the BARB seems to be, change will happen when they "see the IETF moving a
direction that fits with Bluetooth". 

I hope you will raise your concerns at the BOF and on the pre-BOF mailing
list.

- Kulwinder.

> -----Original Message-----
> From: Charles E. Perkins [mailto:charliep@iprg.nokia.com]
> Sent: Tuesday, March 06, 2001 3:07 PM
> To: Phil_Neumiller@3com.com
> Cc: seamoby@diameter.org
> Subject: Re: [seamoby] MANET Critique ( was Yet Another BOF?
> 
> 
> 
> Hello Phil,
> 
> I'd like to suggest a very slight modification to your proposal.
> 
> Why didn't Bluetooth _participate_ in the [manet] work?
> I am 99.99% confident in stating that any of the authors of
> protocols submitted to [manet] would have been delighted
> to respond to design concerns that might have been voiced
> by Bluetooth proponents -- perhaps to the point of redesigning
> the basic protocols as needed.
> 
> Instead, we seem to have been blindsided and then accused
> of being ignorant of their requirements.
> 
> Determining the final outcome of such conflicts is, indeed,
> slightly less quick than watching paint dry -- and not really
> quite as much fun.
> 
> Regards,
> Charlie P.
> 
> 
> 
> 
> Phil_Neumiller@3com.com wrote:
> > 
> > What I never understood is why didn't Bluetooth just pick 
> one of the MANET
> > ad hoc routing standards and  and run with it?
> > 
> > Pick TORA?  Pick AODV?  I don't care. Just run with 
> something.    I guess I am
> > the
> > evil bandy abouter, but not without the justification that 
> something scalable
> > will arive
> > someday.  My feeling is that we can get a few hops 
> standardized now and
> > into consumer devices now and not have to wait until the 
> cows come home.
> > Does the IETF have to move this slow?  Internet time is 
> like watching paint
> > dry these days...
> > 
> > Thanks,
> > 
> > Phil
> > 
> > Sent by:  Michael Thomas <mat@cisco.com>
> > 
> > To:   Kulwinder Atwal <KAtwal@zucotto.com>
> > cc:   "'Charles E. Perkins'" <charliep@iprg.nokia.com>, 
> seamoby@diameter.org,
> >       Gary Kenward <gkenward@nortelnetworks.com> (Phil 
> Neumiller/MW/US/3Com)
> > Subject:  RE: [seamoby] MANET Critique  ( was  Yet Another BOF?
> > 
> > Kulwinder Atwal writes:
> >    solution being bandied around. I've not read AODV so
> 


From owner-seamoby@diameter.org  Tue Mar  6 20:50:38 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA06557
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 20:50:37 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f270PBc19552
	for seamoby-list; Tue, 6 Mar 2001 16:25:11 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f270P9T19547
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 16:25:09 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id QAA01208;
	Tue, 6 Mar 2001 16:33:12 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f270XAV03422;
	Tue, 6 Mar 2001 16:33:10 -0800
X-mProtect:  Tue, 6 Mar 2001 16:33:10 -0800 Nokia Silicon Valley Messaging Protection
Received: from tpagtzis.iprg.nokia.com (205.226.2.115, claiming to be "cs.ucl.ac.uk")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpd1rXrnc; Tue, 06 Mar 2001 16:30:41 PST
Message-ID: <3AA58130.2473B472@cs.ucl.ac.uk>
Date: Tue, 06 Mar 2001 16:30:41 -0800
From: Theo Pagtzis <t.pagtzis@cs.ucl.ac.uk>
Reply-To: tpagtzis@iprg.nokia.com
Organization: UCL/NOKIA
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1-STABLE i386)
X-Accept-Language: el, en
MIME-Version: 1.0
To: Glenn Morrow <gmorrow@nortelnetworks.com>
CC: "'Michael Thomas'" <mat@cisco.com>, seamoby@diameter.org
Subject: Re: [seamoby] MANET Critique ( was Yet Another BOF?
References: <85AA7486A2C1D411BCA20000F8073E4351C71F@crchy271.us.nortel.com>
Content-Type: multipart/alternative;
 boundary="------------3A95EFEF475CD00492D1B00D"
Sender: owner-seamoby@diameter.org
Precedence: bulk


--------------3A95EFEF475CD00492D1B00D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Guys,

   with all due respect....please cool down...it doesn't help anyone and
more importantly the work if each one of us gets aggrovated by
comments/statements of the sort.

Aggrovation can only detract from the depth of our work. This is not in
our interest both as individuals and as a WG list. You know that better
than me.... :)

Theo



Glenn Morrow wrote:

>
>
> Mike,
>
> What purpose are you serving with statements like the one below?
>
> Please go and get yourself a copy of good book on logical argument
> (Aristotle might do fine) and please discover the definition of
> something called a "logical-fallacy".
>
> You also might look some common 7 letter colloquialisms related to
> biological waste disposal systems that one might describe you as.
>
> I suggest you take a few minutes out of your day to read this as well:
>
> http://www.ietf.org/internet-drafts/draft-ietf-poisson-code-02.txt
>
> In particular, I suggest you pay close attention to item 2 of the
> document.
>
> Your blantant disrespect to litterally everyone is bordering on
> intolerable levels. You are "the" "poster boy" for the need of a code
> and perhaps a "baby" that could use some "ejecting" yourself.
>
> Have a nice day.
>
> Glenn
>
>
> Michael Thomas writes:
> ----------------------------
>
>  I'm
>    not in a position to comment on your analysis,
>    but I can tell when babies are being ejected
>    with the bathwater.
>
>             Mike

--------------3A95EFEF475CD00492D1B00D
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Guys,
<p>&nbsp;&nbsp; with all due respect....please cool down...it doesn't help
anyone and more importantly the work if each one of us gets aggrovated
by comments/statements of the sort.
<p>Aggrovation can only detract from the depth of our work. This is not
in our interest both as individuals and as a WG list. You know that better
than me.... :)
<p>Theo
<br>&nbsp;
<br>&nbsp;
<p>Glenn Morrow wrote:
<blockquote TYPE=CITE>&nbsp;
<p><font face="Arial"><font color="#0000FF"><font size=-1>Mike,</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>What purpose
are you serving with statements like the one below?</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Please go and
get yourself a copy of good book on logical argument (Aristotle might do
fine) and please discover the definition of something called a "logical-fallacy".</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>You also might
look some common 7 letter colloquialisms related to biological waste disposal
systems that one might describe you as.</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>I suggest you
take a few minutes out of your day to read this as well:</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1><a href="http://www.ietf.org/internet-drafts/draft-ietf-poisson-code-02.txt" TARGET="_blank">http://www.ietf.org/internet-drafts/draft-ietf-poisson-code-02.txt</a></font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>In particular,
I suggest you pay close attention to item 2 of the document.</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Your blantant
disrespect to litterally everyone is bordering on intolerable levels. You
are "the" "poster boy" for the need of a code and perhaps a "baby" that
could use some "ejecting" yourself.</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Have a nice day.</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Glenn</font></font></font>
<br>&nbsp;
<p><font face="Arial"><font color="#000000"><font size=-1>Michael Thomas
writes:</font></font></font>
<br><font face="Arial"><font color="#000000"><font size=-1>----------------------------</font></font></font>
<p><font face="Arial"><font size=-1>&nbsp;I'm</font></font>
<br><font face="Arial"><font size=-1>&nbsp;&nbsp; not in a position to
comment on your analysis,</font></font>
<br><font face="Arial"><font size=-1>&nbsp;&nbsp; but I can tell when babies
are being ejected</font></font>
<br><font face="Arial"><font size=-1>&nbsp;&nbsp; with the bathwater.</font></font>
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font face="Arial"><font size=-1>&nbsp;&nbsp;&nbsp;
Mike</font></font></blockquote>
</html>

--------------3A95EFEF475CD00492D1B00D--



From owner-seamoby@diameter.org  Tue Mar  6 21:38:07 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA08254
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 21:38:05 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27111M19678
	for seamoby-list; Tue, 6 Mar 2001 17:01:01 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2710xT19668
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 17:00:59 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GNPD3M22>; Tue, 6 Mar 2001 20:09:07 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A1B@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>, charliep@iprg.nokia.com,
        Phil_Neumiller@3Com.com, kulwinder.atwal@herc.zucotto.com
Cc: seamoby@diameter.org
Subject: [seamoby] RE: How to Convince the BARB to work with IETF?
Date: Tue, 6 Mar 2001 20:09:06 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

	
> Do you think the BARB wants a series of "X on Y" 
> working groups where X is a particular mobility technology 
> (manet, mobile-ip,
> maybe micromo, maybe paging, maybe context transfer) and Y is 
> a particular
> link layer (Bluetooth, 802.11, etc.)? Or, specifically, do they want 
> such a working group for Bluetooth? How likely is such a working group
> to be successful when the Bluetooth SIGs seem to have difficulty
> communicating information between themselves? How do you 
> think IETF can work 
> together with the Bluetooth SIG to develop the kinds of L3 
> protocols that will 
> work on PANs?
> 

The people who presented at the last BOF were PAN WG members and Program
Management.  The SIG WG members have a vested interest in not working with
the IETF.  Being in a WG with its secrecy, is a competitive advantage.

There is a bit of a cultural difference here.  In the SIG, unlike the IETF,
the Working Group members are selected primarily based on their company's
expertise, together with their own expertise.  I don't think SIG members
know the criteria for IETF WG participation. 

What I am saying is that we need to focus on convincing the BARB and SIG
members.  

It maybe better to talk about how the IETF works, and extend invitations to
individuals on the pre-BOF mailing list to participate in the IETF WGs
related to mobility by stating that their Bluetooth expertise is welcome.
It would also be good to list all of the current groups working on mobility
related issues within the IETF.

- Kulwinder.

   


From owner-seamoby@diameter.org  Tue Mar  6 22:54:04 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA10342
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 22:54:04 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f271dON19754
	for seamoby-list; Tue, 6 Mar 2001 17:39:24 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f271dLT19749
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 17:39:21 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id RAA07266;
	Tue, 6 Mar 2001 17:47:24 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f271lMl16403;
	Tue, 6 Mar 2001 17:47:22 -0800
X-mProtect:  Tue, 6 Mar 2001 17:47:22 -0800 Nokia Silicon Valley Messaging Protection
Received: from tpagtzis.iprg.nokia.com (205.226.2.115, claiming to be "cs.ucl.ac.uk")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdzYvuCh; Tue, 06 Mar 2001 17:47:10 PST
Message-ID: <3AA5931F.14A72653@cs.ucl.ac.uk>
Date: Tue, 06 Mar 2001 17:47:11 -0800
From: Theo Pagtzis <t.pagtzis@cs.ucl.ac.uk>
Reply-To: tpagtzis@iprg.nokia.com
Organization: UCL/NOKIA
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1-STABLE i386)
X-Accept-Language: el, en
MIME-Version: 1.0
To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
CC: charliep@iprg.nokia.com, Phil_Neumiller@3Com.com,
        kulwinder.atwal@zucotto.com, seamoby@diameter.org
Subject: Re: [seamoby] How to Convince the BARB to work with IETF?
References: <200103070012.QAA11942@heliopolis.Eng.Sun.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Having read the Bluetooth BOF considerations below I am wondering whether there
will be an upcoming

W-CDMA or UMTS BOF
802.11 BOF
HIPERLAN  BOF

so that we can investigate in particular issues of

IP over W-CDMA/UMTS protocols
IP over 802.11b/d/e protocols
IP over HIPERLAN protocols.

and if we really want to be pedantic

IP over diffuse Infra Red since some spec of IR managed to come out


If that is the case then we should be wondering whether 3gpp, IEEE and ETSI will
be thinking that may want to work with IETF if we get such BOFS and subsequent WG
under way...

Alternatively we may start pondering about interfaces between each of these L2
technologies with IP, if we want to start using L2 particulars of the individual
technology. Otherwise I feel that MANET has been doing an excellent job in
specifying IP interactions over ad-hoc nets at L3; beyond
that it is the duty of the technology implementor to provide the necessary
interface hooks for the L2 so as to interface with L3 (already considered by
MANET).

This really belongs in the realm of W-NIC drivers implementation, unless we want
to standardize the input /output from WNIC drivers...

Isn't that the case?

Theo

UCL/ Mobile systems





James Kempf wrote:

> Hi Kulwinder,
>
> Well, this account is certainly a cause for concern.
>
> Do you think the upcoming Bluetooth BOF will be enough to convince
> the BARB that IETF is "moving in the direction of Bluetooth"?
>
> The problem is that IETF is a rather big beast and I don't think the
> optical networking guys care much about Bluetooth. If what the BARB
> means is that IETF mobility solutions are moving toward accommodating
> Bluetooth, then I am  not exactly sure what they want.
>
> Most IETF technologies are designed to be broadly implementable on various link
> layers. There are specific WGs that implement specific L3 technologies
> on specific L2  (example: the Intserv on Specific L2 WG). Up
> till now, that has not been the case with mobility technologies, probably
> because of two reasons:
>
>         - Wireless LAN technologies don't need much help getting the
>         IP mobility technologies implemented on them. In fact, one
>         can argue that most IP mobility technologies were designed
>         with wireless LANs in mind.
>
>         - The cellular industry, which has been the other big consumer
>         of IETF mobility protocols, has its own two SDOs which have
>         been working together with IETF in their own ways. This has
>         typically involved doing their own thing as far as their own L2
>         is concerned and coming to IETF when they need something changed
>         at L3. There have been a few cases where changes have been
>         needed (authentication, special handling in MIPv4 when the
>         FA is not one hop from the access point, perhaps fast handoff),
>         there may be more upcoming (maybe paging and context transfer).
>
> Do you think the BARB wants a series of "X on Y"
> working groups where X is a particular mobility technology (manet, mobile-ip,
> maybe micromo, maybe paging, maybe context transfer) and Y is a particular
> link layer (Bluetooth, 802.11, etc.)? Or, specifically, do they want
> such a working group for Bluetooth? How likely is such a working group
> to be successful when the Bluetooth SIGs seem to have difficulty
> communicating information between themselves? How do you think IETF can work
> together with the Bluetooth SIG to develop the kinds of L3 protocols that will
> work on PANs?
>
> I'm really confused.
>
>                 jak



From owner-seamoby@diameter.org  Tue Mar  6 23:13:47 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA10697
	for <seamoby-archive@odin.ietf.org>; Tue, 6 Mar 2001 23:13:46 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f272HLD19857
	for seamoby-list; Tue, 6 Mar 2001 18:17:21 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f272HJT19852
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 18:17:19 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GNPD3MJ0>; Tue, 6 Mar 2001 21:25:27 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A1D@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Phillip Neumiller'" <neumiller@telocity.com>,
        Kulwinder Atwal
	 <kulwinder.atwal@herc.zucotto.com>,
        "'Phil_Neumiller@3com.com'"
	 <Phil_Neumiller@3Com.com>,
        Michael Thomas <mat@cisco.com>
Cc: Kulwinder Atwal <KAtwal@herc.zucotto.com>,
        "'Charles E. Perkins'"
	 <charliep@iprg.nokia.com>,
        seamoby@diameter.org
Subject: RE: [seamoby] MANET Critique ( was Yet Another BOF?
Date: Tue, 6 Mar 2001 21:25:27 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

> -----Original Message-----
> From: Phillip Neumiller [mailto:neumiller@telocity.com]
> Sent: Tuesday, March 06, 2001 6:22 PM
> To: Kulwinder Atwal; 'Phil_Neumiller@3com.com'; Michael Thomas
> Cc: Kulwinder Atwal; 'Charles E. Perkins'; seamoby@diameter.org
> Subject: Re: [seamoby] MANET Critique ( was Yet Another BOF?
> 
> 
> Well I suggested this would be a problem over a year ago.  I 
> guess I was a
> henny penny back then
> saying "Bluetooth is coming and guess what guys its NOT going 
> to be MANET.


A reason that it is Master-Slave, is because of the Frequency Hopping that
it does.
The Master provides the clock that keeps the piconet synchronized to the
Frequency Hopping Sequence. (FHS)
During discovery, the Master sends an FHS packet to a Slave for it to
synchronize to the Master.
A Slave is required re-synchronize its clock on every Master transmission
that is addressed to it, to account for clock drift.  

Each transmission slot is: 625 microseconds.
Clock drift must be better than 20 parts per million.

It makes sense to use the Master transmission not only for data, but for
clock drift compensation as well. 

If a MANET solution is designed for on top of IP, it needs to be free of
link layer specifics.  

Can a timeout independant IP MANET solution be designed that does not
compete with link layer timeouts?

- Kulwinder.


From owner-seamoby@diameter.org  Wed Mar  7 00:23:16 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA11953
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 00:23:15 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f273ES919972
	for seamoby-list; Tue, 6 Mar 2001 19:14:28 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f273EQT19967
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 19:14:26 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GNPD3MKP>; Tue, 6 Mar 2001 22:22:34 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A1E@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Michael Thomas'" <mat@cisco.com>,
        Kulwinder Atwal
	 <KAtwal@herc.zucotto.com>
Cc: "'Charles E. Perkins'" <charliep@iprg.nokia.com>, seamoby@diameter.org,
        Gary Kenward <gkenward@nortelnetworks.com>
Subject: RE: [seamoby] MANET Critique  ( was  Yet Another BOF?
Date: Tue, 6 Mar 2001 22:22:33 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

>   I've read the TORA draft and it does seem like it has
>    some interesting properties given a local routing based
>    solution being bandied around. 

I thought about the TORA draft some more.  It is trying to solve the problem
of which way is upstream and which way is downstream by using "heights".  In
a Master-Slave Network a device knows that upstream is toward its Master,
and downstream is toward its Slave.  

In a technology neutral Ad Hoc routing solution the upstream/downstream
problem does not exist.

- Kulwinder.
   
> 	    Mike
> 


From owner-seamoby@diameter.org  Wed Mar  7 00:49:23 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA12188
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 00:49:23 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f273IFw19981
	for seamoby-list; Tue, 6 Mar 2001 19:18:15 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from rajma.kniveton.com (adsl-63-197-0-77.dsl.snfc21.pacbell.net [63.197.0.77])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f273IDT19976
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 19:18:13 -0800
Received: from Kniveton.com (nokia-3.Connectathon.ORG [130.128.65.3])
	by rajma.kniveton.com (8.11.1/8.11.1) with ESMTP id f273QEb44327
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 19:26:15 -0800 (PST)
Message-ID: <3AA5AA04.FFD55D05@Kniveton.com>
Date: Tue, 06 Mar 2001 19:24:52 -0800
From: "T.J. Kniveton" <TJ@Kniveton.com>
Organization: NOKIA Research
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.4.0-1-mip i686)
X-Accept-Language: en
MIME-Version: 1.0
To: seamoby@diameter.org
Subject: Re: [seamoby] Re: Spam idiots
References: <Roam.SIMC.2.0.6.983806853.28014.pcalhoun@nasnfs>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pat Calhoun wrote:

> An investigation is underway as we type...
>
> PatC
> >
> >
> >
> > Hi Pat,
> >
> > Did you complain to the domain admins?  They can  almost always find
> > spammers originating from their domains since they leave all kinds
> > of digital footprints.
> >
> > regards,
> >
> > Phil
> >
> >
> >
> >
> >
> > Pat Calhoun <pcalhoun@nasnfs.eng.sun.com> on 03/04/2001 06:22:29 PM
> >
> > Please respond to Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
> >
> > Sent by:  Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
> >
> >
> > To:   Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
> > cc:   "Andrew T. Campbell" <campbell@comet.columbia.edu>, "'Gary Kenward'"
> >       <gkenward@nortelnetworks.com>, "'James Kempf'" <james.kempf@sun.com>,
> > Phil
> >       Neumiller/MW/US/3Com, seamoby@diameter.org
> > Subject:  RE: [seamoby] Yet Another BOF?
> >
> >
> >
> > All,
> >
> > This is an old e-mail that was resent by someone at m018.com. Somehow, this
> > site is resending old e-mail from both seamoby and mobileip lists. I have had
> > to shutdown my list (as has mobileip), as we are being attacked quite
> > viciously by this site. I do not know of a way to re-enable the site and not
> > be attacked.
> >
> > This morning I had over 1800 e-mails resent from this site to my box. I am
> > getting quite annoyed.
> >
> > In short, disregard these e-mails.
> >
> > PatC

Wow, nasty problem. Maybe I don't fully understand it, but it sure seems like it
could be solved by upgrading your version of Sendmail to one that supports an
"access" database and spam controls.. Then, you can add an entry to your access
file, such as "naughtydomain.com REJECT" and rebuild the database. Works for me..
--
T.J. Kniveton



From owner-seamoby@diameter.org  Wed Mar  7 00:57:38 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA12250
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 00:57:37 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f274O6I20133
	for seamoby-list; Tue, 6 Mar 2001 20:24:06 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f274O4T20128
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 20:24:04 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GNPD3MLJ>; Tue, 6 Mar 2001 23:32:13 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A1F@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>, charliep@iprg.nokia.com,
        Phil_Neumiller@3Com.com, kulwinder.atwal@herc.zucotto.com
Cc: seamoby@diameter.org
Subject: RE: [seamoby]  Convince the BARB to work with IETF?
Date: Tue, 6 Mar 2001 23:32:12 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
> Sent: Tuesday, March 06, 2001 7:12 PM
> To: charliep@iprg.nokia.com; Phil_Neumiller@3com.com;
> kulwinder.atwal@herc.zucotto.com
> Cc: seamoby@diameter.org
> Subject: [seamoby] How to Convince the BARB to work with IETF?
> 
> 
> Hi Kulwinder,
> 
> Well, this account is certainly a cause for concern. 
> 
> Do you think the upcoming Bluetooth BOF will be enough to convince
> the BARB that IETF is "moving in the direction of Bluetooth"? 
> 

Late Breaking News......

The SIG will be discussing a "position" on the BOF next week.  The general
mood of the SIG Board of Directors seems to be that they will be happy if
the outcome of the discussions results in a relationship between the SIG and
the IETF similiar to the relationship between the SIG and the IEEE.  A
Director of the Board will be attending the BOF to present the results of
the discussion.

- Kulwinder.



From owner-seamoby@diameter.org  Wed Mar  7 04:20:53 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA28503
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 04:20:52 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f277psd20705
	for seamoby-list; Tue, 6 Mar 2001 23:51:54 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from porsta.cs.Helsinki.FI (root@porsta.cs.Helsinki.FI [128.214.48.124])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f277ppT20700
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 23:51:52 -0800
Received: from melkinpaasi.cs.Helsinki.FI (jmanner@melkinpaasi.cs.Helsinki.FI [128.214.10.13]) by porsta.cs.Helsinki.FI (8.8.8/8.8.8) with ESMTP id JAA29389 for <seamoby@diameter.org>; Wed, 7 Mar 2001 09:59:59 +0200
Date: Wed, 7 Mar 2001 09:59:49 +0200 (EET)
From: Jukka Manner <jmanner@cs.helsinki.fi>
To: Seamoby Working Group <seamoby@diameter.org>
Subject: [seamoby] I-D ACTION:draft-manner-seamoby-terms-01.txt (fwd)
Message-ID: <Pine.LNX.4.30.0103070948210.31396-100000@melkinpaasi.cs.Helsinki.FI>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.30.0103070948212.31396@melkinpaasi.cs.Helsinki.FI>
Sender: owner-seamoby@diameter.org
Precedence: bulk


	Hi,

	We have created a new version of the terminology draft. Comments and
discussions would be very welcome.

	Regards,

	Jukka

---------- Forwarded message ----------
Date: Tue, 06 Mar 2001 06:42:17 -0500
From: Internet-Drafts@ietf.org
To: IETF-Announce:  ;
Subject: I-D ACTION:draft-manner-seamoby-terms-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Mobility Related Terminology
	Author(s)	: J. Manner et al.
	Filename	: draft-manner-seamoby-terms-01.txt
	Pages		: 18
	Date		: 05-Mar-01

There is a need for common definitions of terminology in the work to
be done around IP mobility. This memo defines terms for mobility
related terminology. It is intended as a living document for use by
the Seamoby working group, and especially for use in Seamoby drafts
and in WG discussions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-manner-seamoby-terms-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-manner-seamoby-terms-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-manner-seamoby-terms-01.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.



From owner-seamoby@diameter.org  Wed Mar  7 04:32:24 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA28617
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 04:32:24 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f277oUQ20695
	for seamoby-list; Tue, 6 Mar 2001 23:50:30 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from porsta.cs.Helsinki.FI (root@porsta.cs.Helsinki.FI [128.214.48.124])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f277oRT20690
	for <seamoby@diameter.org>; Tue, 6 Mar 2001 23:50:27 -0800
Received: from melkinpaasi.cs.Helsinki.FI (jmanner@melkinpaasi.cs.Helsinki.FI [128.214.10.13]) by porsta.cs.Helsinki.FI (8.8.8/8.8.8) with ESMTP id JAA28496; Wed, 7 Mar 2001 09:52:14 +0200
Date: Wed, 7 Mar 2001 09:52:03 +0200 (EET)
From: Jukka Manner <jmanner@cs.helsinki.fi>
To: Gary Kenward <gkenward@nortelnetworks.com>
cc: "'seamoby_context'" <seamoby_context@marvin.baynetworks.com>,
        "'seamoby'" <seamoby@diameter.org>
Subject: Re: [seamoby] Seamoby Context Transfer Design Team Requirements
 kick-off confe rence          call, Monday, March 12, 2001, 11 am EST
In-Reply-To: <13E2EF604DE5D111B2E50000F80824E8057A8D4D@zwdld001.ca.nortel.com>
Message-ID: <Pine.LNX.4.30.0103070951120.31396-100000@melkinpaasi.cs.Helsinki.FI>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk


	Hi Gary,

	Count me in.


	Regards,

	Jukka

On Mon, 5 Mar 2001, Gary Kenward wrote:

> This email is formal request for participation in the next
> Seamless Mobility Context Transfer Design Team conference call.
>
> In the past we have held these calls on Monday mornings
> at 11 am EST. I have tentatively scheduled the next meeting
> for Monday, March 12, 2001 at 11 am EST. However, this time
> can be changed *if* there is a consensus. Keep in mind that there
> are participants on three continents, at least, and it is difficult
> to accommodate everyone.
>
> As I understand it, the design team's next task is the
> development of a *requirements* draft. We must complete this
> draft before the ADs will consider giving us the go-ahead to work on
> solutions.
>
> The *tentative* agenda is:
> 	 *	attendance, hellos, etc.
> 	 *	selection of an editor for the requirements draft
> 	 *	rules for authorship
> 	 *	discussion of format / table of contents
> 	 *	action items
> 	 *	meeting schedule
>
> We have this week to modify this agenda.
>
> The conference call information is:
>
> Date: 			Monday, March 5, 2001
> Time:			11 AM EST.
> US Phone Number: 	972-684-6338
> PassCode:		793142
>
> I request that all replies to this email be copied to the
> seamoby and seamoby_context lists to ensure that
> there is an open discussion and an archive.
>
> Thank you,
> Gary Kenward
>
> PS  I assume that a consensus means 50% + 1 of the respondents.
>



From owner-seamoby@diameter.org  Wed Mar  7 06:47:50 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA29859
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 06:47:48 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f279G6N20959
	for seamoby-list; Wed, 7 Mar 2001 01:16:06 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from ms.hansol.co.kr (IDENT:root@[210.112.2.207])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f279FxT20954
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 01:16:00 -0800
Received: from ns ([211.113.87.7])
	by ms.hansol.co.kr (8.9.3/8.9.3) with SMTP id SAA19370
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 18:18:20 +0900
Message-ID: <03e801c0a6e8$581ea240$5c12060a@hansol.co.kr>
From: "Jiwoong Lee" <porce@kaist.ac.kr>
To: <seamoby@diameter.org>
Subject: [seamoby] Link Layer Technologies
Date: Wed, 7 Mar 2001 18:23:29 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

All,

Many hot parts of Mobile IP discussions seem to move to here. I sometimes
feel embarrassed by the barrage of emails to this WG. :>

By the way, I feel a bit uncomfortable with the fact that this Transport
Area WG is happy to deal with network layer problems and link layer
technologies in detail. Please don't say that "It's stated in the WG
charter. So, no worries." The reason I feel so is, I guess,
due to that I'm not familar with those too many layer technologies at the
same time. Maybe there is another reason in my mind. (I'll think about it.)

I've read through previous threads on paging problem statement. Many of the
arguments were beginning with "I'm not an expert on cellular stuff, but as
far as I know..."

Yes, right. Many of IETF engineers (including me) are not familar with
cellular stuff (or other link layer technologies). That is one reason why
the argument sounds too abstract sometimes, too specific othertimes. No
matter what link layer technologies SeaMoby folks are assuming, I think we
need to specifically address those technologies. Yes. that does not belong
to IETF boundary. Without this, the discussion and argument will be floating
for so long time.

Again, the charter says something so vague. We have IS-95A,B/cdma2000-1x,
3x, Release 99, Release 2000, blah, blah, blah. Wow. so many (sometimes in
one name!).
We may need the base link layer technologies (probably including the common
features of the futuer ones.)

Huge bunch of comments.

Best regards,
Jiwoong




From owner-seamoby@diameter.org  Wed Mar  7 09:20:38 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA05106
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 09:20:38 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27CJYq21614
	for seamoby-list; Wed, 7 Mar 2001 04:19:34 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from cs.tamu.edu (IDENT:0@clavin.cs.tamu.edu [128.194.130.106])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27CJVT21609
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 04:19:32 -0800
Received: from photon.cs.tamu.edu (IDENT:2654@photon [128.194.134.1])
	by cs.tamu.edu (8.11.0/8.11.0) with ESMTP id f27CRfI24109;
	Wed, 7 Mar 2001 06:27:41 -0600 (CST)
Received: (from vaidya@localhost)
	by photon.cs.tamu.edu (8.11.0/8.11.0) id f27CRwN24268;
	Wed, 7 Mar 2001 06:27:58 -0600 (CST)
Date: Wed, 7 Mar 2001 06:27:58 -0600 (CST)
From: Nitin H Vaidya <vaidya@cs.tamu.edu>
Message-Id: <200103071227.f27CRwN24268@photon.cs.tamu.edu>
To: KAtwal@herc.zucotto.com
Subject: RE: [seamoby] MANET Critique  ( was  Yet Another BOF?
Cc: seamoby@diameter.org
Sender: owner-seamoby@diameter.org
Precedence: bulk

  >> From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
  ...
  >> I thought about the TORA draft some more.  It is trying to solve the problem
  >> of which way is upstream and which way is downstream by using "heights".  In
  >> a Master-Slave Network a device knows that upstream is toward its Master,
  >> and downstream is toward its Slave.  
  >> 
  >> In a technology neutral Ad Hoc routing solution the upstream/downstream
  >> problem does not exist.

I am afraid you may have misinterpreted TORA (which is, incidentally,
derived from a very nice paper by Gafni and Bertsekas on
"link reversal" algorithms).
Or, perhaps what you mean by ad hoc is different from what TORA
assumes.

Your statement may be accurate if all you have is one Master, and its
slaves talking to each other. But if the network of interest contains
multiple piconets (hence multiple masters), one would need a protocol
to route packets between the piconets -- "downstream" is just
TORAs way of saying "this way to destination D", nothing
more than that. So, it makes sense to assign downstream
directions in case of BlueTooth as well. Heights in TORA are just
a means to decide which way a link points, not an end unto
themselves.

Since piconets have a Master-Slave organization, one can use
hierarchical routing, where packets are routed to the destination's
"cluster head" (i.e., Master), and then to the slave. Many such
hierarchical protocols have been proposed for MANETs, needless
to say, and one could easily adapt TORA (or AODV, etc.) to optimize
for such a hierarchy.

For a brief overview of MANET research, you may want to take a look
at the tutorial available at www.cs.tamu.edu/facylty/vaidya (click
on Seminars). Hopefully, the tutorial is easier to read than some of
the papers. The tutorial is not comprehensive, particularly, it lacks
coverage of many cluster-based schemes.

Just to elaborate briefly on the "link reversal" algorithms
by Gafni/Bertsekas (also used in TORA): for each plausible
destination, a given node maintains 0 or more "downstream"
pointers -- following any of the pointers will eventually get
the packet to that destination. The trick is to maintain these
downstream pointers correctly, which is what Gafni/Bertsekas do
well . TORAs contribution is to detect when network is "partitioned"
and avoid doing fruitless work trying to find routes between the
partitions. This is important since in MANETs, partitions may occur.

Cheerio.

- nitin



  >> 
  >> - Kulwinder.
  >>    
  >> > 	    Mike
  >> > 
  >> 


From owner-seamoby@diameter.org  Wed Mar  7 10:38:08 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA07861
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 10:38:07 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27Db7W21825
	for seamoby-list; Wed, 7 Mar 2001 05:37:07 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from atlsnmx1.nextel.com (atlsnmx1.nextel.com [167.20.198.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27Db5T21820
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 05:37:05 -0800
Received: from atlntgw02.nextel.com (atlntgw02.nextel.com [10.8.79.186])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id IAA26227;
	Wed, 7 Mar 2001 08:44:55 -0500 (EST)
Received: by atlntgw02.nextel.com with Internet Mail Service (5.5.2650.21)
	id <FXB2J164>; Wed, 7 Mar 2001 08:45:28 -0500
Message-ID: <020A5EC56F3FD411B5230008C716D08586841E@nhqntex01.nextel.com>
From: "Martin, David P" <David.P.Martin@nextel.com>
To: "'tpagtzis@iprg.nokia.com'" <tpagtzis@iprg.nokia.com>,
        James Kempf
	 <kempf@heliopolis.Eng.Sun.COM>
Cc: charliep@iprg.nokia.com, Phil_Neumiller@3Com.com,
        kulwinder.atwal@zucotto.com, seamoby@diameter.org
Subject: RE: [seamoby] IP on specific L2 (Was ...  How to Convince the BAR
	B to work with IETF?)
Date: Wed, 7 Mar 2001 08:40:17 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

I think it is dangerous to focus on underlying protocols when designing a
new higher level protocol.  To many assumptions could be made, and the
extensibility of the the new protocol would be suspect.

However, I think it is perfectly reasonable to focus on protocol
interoperability.  For example, I think it is perfectly acceptable for a
micro-mobility protocol to have hooks built in for Layer 2 (aka access
network) triggers in order to achieve greater efficiency.  Of course it
would be great if existing layer 2 protocols could take advantage of these
hooks from day one, but if not, that's a layer 2 problem.  I think of
several examples of where this would help in the Mobile IP space, and my
guess is that there maybe some that could help in the seamoby space as well
(we'll find out as we start moving into the solution space).



<snip>
> 
> This really belongs in the realm of W-NIC drivers 
> implementation, unless we want
> to standardize the input /output from WNIC drivers...
> 
> Isn't that the case?
> 
> Theo
> 
> UCL/ Mobile systems
> 
> 
<snip>
> >
> > Do you think the BARB wants a series of "X on Y"
> > working groups where X is a particular mobility technology 
> (manet, mobile-ip,
> > maybe micromo, maybe paging, maybe context transfer) and Y 
> is a particular
> > link layer (Bluetooth, 802.11, etc.)? Or, specifically, do they want
> > such a working group for Bluetooth? How likely is such a 
> working group
> > to be successful when the Bluetooth SIGs seem to have difficulty
> > communicating information between themselves? How do you 
> think IETF can work
> > together with the Bluetooth SIG to develop the kinds of L3 
> protocols that will
> > work on PANs?
> >
> > I'm really confused.
> >
> >                 jak
> 


From owner-seamoby@diameter.org  Wed Mar  7 10:54:00 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA08486
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 10:54:00 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27Di5k21852
	for seamoby-list; Wed, 7 Mar 2001 05:44:05 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from idcpa4.pa.interdigital.com (idcmail.interdigital.com [12.32.197.142])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27Di3T21847
	for <seamoby@cdma-2000.org>; Wed, 7 Mar 2001 05:44:03 -0800
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <DLAL4RMG>; Wed, 7 Mar 2001 08:50:27 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D01F1F758@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>
Cc: "'pcalhoun@nasnfs.eng.sun.com'" <pcalhoun@nasnfs.eng.sun.com>,
        "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Paging requirements phase #3
Date: Wed, 7 Mar 2001 08:50:24 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



-----Original Message-----
From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
Sent: Tuesday, March 06, 2001 1:37 PM
To: Sharif.Shahrier@interdigital.com
Subject: RE: [seamoby] Paging requirements phase #2


draft-sarikaya-seamoby-paging-requirements-00.txt

THIS DRAFT IS NOT AVAILABLE IN THE I-D ARCHIVES.

HOWEVER, I AM EXTREMELY PUZZULED HOW THIS I-D COULD HAVE BEEN ACCEPTED AS A
WORKING GROUP DRAFT ON THE "REQUIREMENTS" PHASE BEFORE ALL THE INTERESTED
PEOPLE HAD TIME TO READ IT BEFOREHAND AND VOICED THEIR OPPINIONS. IT IS ALSO
SURPRISING TO ME THAT NO OTHER CANDIDATE DRAFTS HAD BEEN CONSIDERED AS
ALTERNATIVES AND THEIR RELATIVE MERITS AND DE-MERITS HAD BEEN DEBATED BY ALL
THE INTERESTED PARTIES. I FOLLOW THE SEAMOBY WORKING GROUP SEVERAL TIMES A
DAY, AND I HAD NOT SEEN ANY DISCUSSIONS ON THIS ISSUE. THANK YOU.

SHARIF SHAHRIER


From owner-seamoby@diameter.org  Wed Mar  7 11:09:06 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA09020
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 11:09:06 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27EB4U21948
	for seamoby-list; Wed, 7 Mar 2001 06:11:04 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from idcpa4.pa.interdigital.com (idcmail.interdigital.com [12.32.197.142])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27EB2T21943
	for <seamoby@cdma-2000.org>; Wed, 7 Mar 2001 06:11:02 -0800
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <DLAL4R32>; Wed, 7 Mar 2001 09:17:27 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D01F1F759@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>
To: "'pcalhoun@nasnfs.eng.sun.com'" <pcalhoun@nasnfs.eng.sun.com>
Cc: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>,
        "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: [seamoby] micro-mobility requirements phase
Date: Wed, 7 Mar 2001 09:17:20 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Pat,

Could you please tell me when the micro-mobility "requirements" phase is
about to start, and what is the format for this?
Thanks.

Sharif


From owner-seamoby@diameter.org  Wed Mar  7 11:29:49 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA09882
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 11:29:49 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27EqbM22077
	for seamoby-list; Wed, 7 Mar 2001 06:52:37 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27EqYT22070
	for <seamoby@cdma-2000.org>; Wed, 7 Mar 2001 06:52:35 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-3.cisco.com (8.9.3/8.9.1) with ESMTP id GAA29105;
	Wed, 7 Mar 2001 06:59:27 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ACB18201;
	Wed, 7 Mar 2001 07:00:36 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id HAA28124; Wed, 7 Mar 2001 07:00:35 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15014.19731.739064.445615@thomasm-u1.cisco.com>
Date: Wed, 7 Mar 2001 07:00:35 -0800 (PST)
To: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>
Cc: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        "'pcalhoun@nasnfs.eng.sun.com'" <pcalhoun@nasnfs.eng.sun.com>,
        "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Paging requirements phase #3
In-Reply-To: <A1170612471BD21185B90008C7FA0A0D01F1F758@idcpa4.pa.interdigital.com>
References: <A1170612471BD21185B90008C7FA0A0D01F1F758@idcpa4.pa.interdigital.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Um, Sharif, this looks to be an individual
submission.  If it were a working group draft, it
would start draft-ietf-seamoby-[...]

	    Mike


Shahrier, Sharif M. writes:
 > 
 > 
 > -----Original Message-----
 > From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
 > Sent: Tuesday, March 06, 2001 1:37 PM
 > To: Sharif.Shahrier@interdigital.com
 > Subject: RE: [seamoby] Paging requirements phase #2
 > 
 > 
 > draft-sarikaya-seamoby-paging-requirements-00.txt
 > 
 > THIS DRAFT IS NOT AVAILABLE IN THE I-D ARCHIVES.
 > 
 > HOWEVER, I AM EXTREMELY PUZZULED HOW THIS I-D COULD HAVE BEEN ACCEPTED AS A
 > WORKING GROUP DRAFT ON THE "REQUIREMENTS" PHASE BEFORE ALL THE INTERESTED
 > PEOPLE HAD TIME TO READ IT BEFOREHAND AND VOICED THEIR OPPINIONS. IT IS ALSO
 > SURPRISING TO ME THAT NO OTHER CANDIDATE DRAFTS HAD BEEN CONSIDERED AS
 > ALTERNATIVES AND THEIR RELATIVE MERITS AND DE-MERITS HAD BEEN DEBATED BY ALL
 > THE INTERESTED PARTIES. I FOLLOW THE SEAMOBY WORKING GROUP SEVERAL TIMES A
 > DAY, AND I HAD NOT SEEN ANY DISCUSSIONS ON THIS ISSUE. THANK YOU.
 > 
 > SHARIF SHAHRIER


From owner-seamoby@diameter.org  Wed Mar  7 12:07:12 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA11805
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 12:07:12 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27FQlu22276
	for seamoby-list; Wed, 7 Mar 2001 07:26:47 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from idcpa4.pa.interdigital.com (idcmail.interdigital.com [12.32.197.142])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27FQjT22271
	for <seamoby@cdma-2000.org>; Wed, 7 Mar 2001 07:26:45 -0800
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <DLAL4RW9>; Wed, 7 Mar 2001 10:33:09 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D01F1F75B@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>
To: "'Michael Thomas'" <mat@cisco.com>,
        "Shahrier, Sharif M."
	 <Sharif.Shahrier@interdigital.com>
Cc: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        "'pcalhoun@nasnfs.eng.sun.com'" <pcalhoun@nasnfs.eng.sun.com>,
        "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Paging requirements phase #3
Date: Wed, 7 Mar 2001 10:33:05 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Mike,

I know this is an indiviual draft, but if I'm not mistaken the e-mail from
James stated that this draft was being cosidered as a working group draft.
Is this true? 
Personally speaking, I would have preferred if all the interested working
group people had a chance to read it first and voice their oppinions. 
I tried to get it from the I-D directory, but aparantly, its not there.

Sharif

-----Original Message-----
From: Michael Thomas [mailto:mat@cisco.com]
Sent: Wednesday, March 07, 2001 10:01 AM
To: Shahrier, Sharif M.
Cc: 'James Kempf'; 'pcalhoun@nasnfs.eng.sun.com';
'seamoby@cdma-2000.org'
Subject: RE: [seamoby] Paging requirements phase #3



Um, Sharif, this looks to be an individual
submission.  If it were a working group draft, it
would start draft-ietf-seamoby-[...]

	    Mike


Shahrier, Sharif M. writes:
 > 
 > 
 > -----Original Message-----
 > From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
 > Sent: Tuesday, March 06, 2001 1:37 PM
 > To: Sharif.Shahrier@interdigital.com
 > Subject: RE: [seamoby] Paging requirements phase #2
 > 
 > 
 > draft-sarikaya-seamoby-paging-requirements-00.txt
 > 
 > THIS DRAFT IS NOT AVAILABLE IN THE I-D ARCHIVES.
 > 
 > HOWEVER, I AM EXTREMELY PUZZULED HOW THIS I-D COULD HAVE BEEN ACCEPTED AS
A
 > WORKING GROUP DRAFT ON THE "REQUIREMENTS" PHASE BEFORE ALL THE INTERESTED
 > PEOPLE HAD TIME TO READ IT BEFOREHAND AND VOICED THEIR OPPINIONS. IT IS
ALSO
 > SURPRISING TO ME THAT NO OTHER CANDIDATE DRAFTS HAD BEEN CONSIDERED AS
 > ALTERNATIVES AND THEIR RELATIVE MERITS AND DE-MERITS HAD BEEN DEBATED BY
ALL
 > THE INTERESTED PARTIES. I FOLLOW THE SEAMOBY WORKING GROUP SEVERAL TIMES
A
 > DAY, AND I HAD NOT SEEN ANY DISCUSSIONS ON THIS ISSUE. THANK YOU.
 > 
 > SHARIF SHAHRIER


From owner-seamoby@diameter.org  Wed Mar  7 12:21:44 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA12836
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 12:21:43 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27EZbR22017
	for seamoby-list; Wed, 7 Mar 2001 06:35:37 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27EZYT22012
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 06:35:34 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA10572;
	Wed, 7 Mar 2001 06:43:42 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA24671;
	Wed, 7 Mar 2001 06:43:40 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (eastapp2.East.Sun.COM [129.148.162.99])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id GAA29194;
	Wed, 7 Mar 2001 06:43:33 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Message-Id: <200103071443.GAA29194@nasnfs.Eng.Sun.COM>
Date: Wed, 7 Mar 2001 06:50:36 -0800
To: "T.J. Kniveton" <TJ@Kniveton.com>, <seamoby@diameter.org>
Reply-To: <pcalhoun@eng.sun.com>
Subject: Re: [seamoby] Re: Spam idiots
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


>Wow, nasty problem. Maybe I don't fully understand it, but it sure seems like
>it
>could be solved by upgrading your version of Sendmail to one that supports an
>"access" database and spam controls.. Then, you can add an entry to your access
>file, such as "naughtydomain.com REJECT" and rebuild the database. Works for
>me..

Did that already, and it does help (actually, I used DISCARD). As far as I
can tell, this only works if the user sending it is from the domain you state,
not if the server's domain is in the access file :(

In any case, I have an IP filter.... no packets to/from that site.

PatC



From owner-seamoby@diameter.org  Wed Mar  7 12:21:47 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA12847
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 12:21:46 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27FqPG22378
	for seamoby-list; Wed, 7 Mar 2001 07:52:25 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from cs.tamu.edu (IDENT:0@clavin.cs.tamu.edu [128.194.130.106])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27FqNT22373
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 07:52:23 -0800
Received: from sun.cs.tamu.edu (IDENT:2654@sun [128.194.135.14])
	by cs.tamu.edu (8.11.0/8.11.0) with ESMTP id f27G0TI29684;
	Wed, 7 Mar 2001 10:00:30 -0600 (CST)
Received: (from vaidya@localhost)
	by sun.cs.tamu.edu (8.11.0/8.11.0) id f27Fwk228594;
	Wed, 7 Mar 2001 09:58:46 -0600 (CST)
Date: Wed, 7 Mar 2001 09:58:46 -0600 (CST)
From: Nitin H Vaidya <vaidya@cs.tamu.edu>
Message-Id: <200103071558.f27Fwk228594@sun.cs.tamu.edu>
To: tpagtzis@iprg.nokia.com
Subject: Re: [seamoby] MANET Critique ( was Yet Another BOF?
Cc: seamoby@diameter.org
Sender: owner-seamoby@diameter.org
Precedence: bulk



hi Theo

  >> From t.pagtzis@cs.ucl.ac.uk Wed Mar  7 09:28:21 2001
  >> 
  >> > Since piconets have a Master-Slave organization, one can use
  >> > hierarchical routing, where packets are routed to the destination's
  >> > "cluster head" (i.e., Master), and then to the slave. Many such
  >> > hierarchical protocols have been proposed for MANETs, needless
  >> > to say, and one could easily adapt TORA (or AODV, etc.) to optimize
  >> > for such a hierarchy.
  >> 
  >> Master-slave organization (or better point to point to multipoint) is also over
  >> 802.11 at infrastructure mode
  >> This is the case over PCF (no contention) and DCF (with contention). Does that
  >> render a constitute a reason for using MANET protocols
  >> over 802.11 at that mode?

No, it doesn't.
I guess it might be redundant, but useful, to add that
"mobile ad hoc networking (MANET) protocols" are most suited
for "mobile ad hoc networks".

So, if a mobile directly talks only to a fixed basestation, and the
basestations are connected by an infrastrcture network, then (even if it
is 802.11), it is NOT a mobile ad hoc environment. (One can certainly imagine an
ad hoc environment, which also uses an infrastructure when feasible, but that is
not the environment you imply above).

  >> 
  >> What I am trying to say is that there will be two distinct cases for piconets.
  >> 
  >> 1) the case where the Blue(tooth) AP that forwards traffic to the Bluetooth node
  >> (for instance a stereo forwards traffic to some headphone, a laptop forwards traffic
  >> to some cellphone/palm pilot. In that case we would expect the AP to be fixed,
  >> wouldn't we? This is more faithfull to the intent also of a cable interconnect,
  >> which I think people would like to market FIRST if they want their money BACK.

This is how I too thought BlueTooth was supposed to be used, and should/would be
used in initial products. But since there seems to be interest in MANET protocols,
I can only presume that there would be applications that call for other forms of
BlueTooth connectivity, such as in item 2 you describe below.

  >> 
  >> 2) the case where the Blue AP moves independently of the Bluetooth node. In that
  >> case we have two cases
  >>        a) you have ad-hoc mode where both Blue AP and node work over ad-hoc mode
  >> clusterhead scheme and hope for the best if the population of the Blue nodes is
  >> sparse (indoor/inhouse outdoors)
  >>        b) continue on infrastructure mode by making use of fixed-point Blue
  >> relay-APs (for instance the Blue node is near the fridge in the kitchen
  >> and so the Blue node reassociates with the fridge Blue AP so that the traffic does
  >> not go through the PREVIOUS Blue AP.


  >> As far as I can see MANET protocols kick in during the havoc of movement of BOTH the

If these movements are not too frequent, you might get away with good old
link state routing protocols, without having to do anything particularly new.

  >> Blue AP and the Blue node. Why are we jumping into the MANET boat on this list at a
  >> time where the MANET guys are already solving the problem????

One reason you may not want MANET folks to drift along happily is that BlueTooth
is not the same as 802.11, and most MANET protocols lately have been
evaluated assuming 802.11-like MAC, and certain mobility/traffic models.
What looks great in these evaluations may not necessarily be the best bet for
BlueTooth, considering the differences in layer 2, mobility patterns, and
traffic models. So it will be a good idea for the BlueTooth group to provide
inputs to the MANET group.

Regards.

- nitin

  >> 
  >> Theo
  >> 
  >> UCL/Mobile systems
  >> 



From owner-seamoby@diameter.org  Wed Mar  7 12:27:24 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA13099
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 12:27:23 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27FIri22241
	for seamoby-list; Wed, 7 Mar 2001 07:18:53 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27FIGT22236
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 07:18:16 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id HAA13117;
	Wed, 7 Mar 2001 07:26:21 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f27FQJJ02730;
	Wed, 7 Mar 2001 07:26:19 -0800
X-mProtect:  Wed, 7 Mar 2001 07:26:19 -0800 Nokia Silicon Valley Messaging Protection
Received: from tpagtzis.iprg.nokia.com (205.226.2.115, claiming to be "cs.ucl.ac.uk")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdIo0G7q; Wed, 07 Mar 2001 07:26:13 PST
Message-ID: <3AA65317.80EC0B5B@cs.ucl.ac.uk>
Date: Wed, 07 Mar 2001 07:26:15 -0800
From: Theo Pagtzis <t.pagtzis@cs.ucl.ac.uk>
Reply-To: tpagtzis@iprg.nokia.com
Organization: UCL/NOKIA
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1-STABLE i386)
X-Accept-Language: el, en
MIME-Version: 1.0
To: Nitin H Vaidya <vaidya@cs.tamu.edu>
CC: KAtwal@herc.zucotto.com, seamoby@diameter.org
Subject: Re: [seamoby] MANET Critique ( was Yet Another BOF?
References: <200103071227.f27CRwN24268@photon.cs.tamu.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>

Nitin,

   I have some reservations to what has been said over Bluetooth.
In particular

>
>
> Since piconets have a Master-Slave organization, one can use
> hierarchical routing, where packets are routed to the destination's
> "cluster head" (i.e., Master), and then to the slave. Many such
> hierarchical protocols have been proposed for MANETs, needless
> to say, and one could easily adapt TORA (or AODV, etc.) to optimize
> for such a hierarchy.

Master-slave organization (or better point to point to multipoint) is also over
802.11 at infrastructure mode
This is the case over PCF (no contention) and DCF (with contention). Does that
render a constitute a reason for using MANET protocols
over 802.11 at that mode?

What I am trying to say is that there will be two distinct cases for piconets.

1) the case where the Blue(tooth) AP that forwards traffic to the Bluetooth node
(for instance a stereo forwards traffic to some headphone, a laptop forwards traffic
to some cellphone/palm pilot. In that case we would expect the AP to be fixed,
wouldn't we? This is more faithfull to the intent also of a cable interconnect,
which I think people would like to market FIRST if they want their money BACK.

2) the case where the Blue AP moves independently of the Bluetooth node. In that
case we have two cases
       a) you have ad-hoc mode where both Blue AP and node work over ad-hoc mode
clusterhead scheme and hope for the best if the population of the Blue nodes is
sparse (indoor/inhouse outdoors)
       b) continue on infrastructure mode by making use of fixed-point Blue
relay-APs (for instance the Blue node is near the fridge in the kitchen
and so the Blue node reassociates with the fridge Blue AP so that the traffic does
not go through the PREVIOUS Blue AP.

As far as I can see MANET protocols kick in during the havoc of movement of BOTH the
Blue AP and the Blue node. Why are we jumping into the MANET boat on this list at a
time where the MANET guys are already solving the problem????

Theo

UCL/Mobile systems


>
>
> For a brief overview of MANET research, you may want to take a look
> at the tutorial available at www.cs.tamu.edu/facylty/vaidya (click
> on Seminars). Hopefully, the tutorial is easier to read than some of
> the papers. The tutorial is not comprehensive, particularly, it lacks
> coverage of many cluster-based schemes.
>
> Just to elaborate briefly on the "link reversal" algorithms
> by Gafni/Bertsekas (also used in TORA): for each plausible
> destination, a given node maintains 0 or more "downstream"
> pointers -- following any of the pointers will eventually get
> the packet to that destination. The trick is to maintain these
> downstream pointers correctly, which is what Gafni/Bertsekas do
> well . TORAs contribution is to detect when network is "partitioned"
> and avoid doing fruitless work trying to find routes between the
> partitions. This is important since in MANETs, partitions may occur.
>
> Cheerio.
>
> - nitin
>
>   >>
>   >> - Kulwinder.
>   >>
>   >> >      Mike
>   >> >
>   >>



From owner-seamoby@diameter.org  Wed Mar  7 12:56:48 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14271
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 12:56:43 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27GQx822511
	for seamoby-list; Wed, 7 Mar 2001 08:26:59 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27GQvT22506
	for <seamoby@cdma-2000.org>; Wed, 7 Mar 2001 08:26:57 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA09493;
	Wed, 7 Mar 2001 08:34:40 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA11652;
	Wed, 7 Mar 2001 08:34:40 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (esun1as-be.Central.Sun.COM [129.147.34.142])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id IAA00499;
	Wed, 7 Mar 2001 08:34:29 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Message-Id: <200103071634.IAA00499@nasnfs.Eng.Sun.COM>
Date: Wed, 7 Mar 2001 08:41:37 -0800
To: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>,
        "'Michael Thomas'" <mat@cisco.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>,
        "'pcalhoun@nasnfs.eng.sun.com'" <pcalhoun@nasnfs.eng.sun.com>,
        "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>
Reply-To: <pcalhoun@eng.sun.com>
Subject: RE: [seamoby] Paging requirements phase #3
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>I know this is an indiviual draft, but if I'm not mistaken the e-mail from
>James stated that this draft was being cosidered as a working group draft.
>Is this true? 

No. He stated that it *could* be the starting point for the design team. A far
cry from *the* WG document.

>Personally speaking, I would have preferred if all the interested working
>group people had a chance to read it first and voice their oppinions. 

That is exactly what we are here to do.

>I tried to get it from the I-D directory, but aparantly, its not there.

could be the I-D editor is real busy. Try again, and if unsuccessful send an
e-mail to the author.

PatC



From owner-seamoby@diameter.org  Wed Mar  7 13:03:37 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA14660
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 13:03:36 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27FBiU22218
	for seamoby-list; Wed, 7 Mar 2001 07:11:44 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27FBdT22207;
	Wed, 7 Mar 2001 07:11:39 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA25274;
	Wed, 7 Mar 2001 07:19:49 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA29709;
	Wed, 7 Mar 2001 07:19:48 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (eastapp2.East.Sun.COM [129.148.162.99])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id HAA29516;
	Wed, 7 Mar 2001 07:19:17 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Message-Id: <200103071519.HAA29516@nasnfs.Eng.Sun.COM>
Date: Wed, 7 Mar 2001 07:26:44 -0800
To: "James Kempf" <kempf@heliopolis.Eng.Sun.COM>, <seamoby@diameter.org>,
        <behcet.sarikaya@usa.alcatel.com>, <pcalhoun@nasnfs.eng.sun.com>,
        <seamoby-paging@diameter.org>
Reply-To: <pcalhoun@eng.sun.com>
Subject: Re: [seamoby] Re: [seamoby-paging] Fwd: No I-D action yet
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Could we restrict discussions to a single list? Cross-posting is a good idea when
announcing new on-going work, but it seems silly for everyone to receive two
copies of e-mails like the one below.

Please prune recipient lists when replying to a cross-posted e-mail.

PatC
>Behcet,
>
>I have been trying to get a discussion of paging requirements on the
>seamoby-paging list. Your draft is a good start, however, I think the
>draft needs some clean up and we need to make sure that the requirements
>collected from other memebers of the design team are also included. Would you 
>like to be the requirements draft editor? 
>
>If so, then I would suggest that you take the time slot for "ongoing
>work" to present the state of the requirements discussion on the
>seamoby-paging list, including your draft.
>
>		jak
>




From owner-seamoby@diameter.org  Wed Mar  7 13:13:03 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15050
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 13:13:02 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27F9vI22188
	for seamoby-list; Wed, 7 Mar 2001 07:09:57 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27F9tT22183
	for <seamoby@cdma-2000.org>; Wed, 7 Mar 2001 07:09:55 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA24233;
	Wed, 7 Mar 2001 07:17:29 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA29326;
	Wed, 7 Mar 2001 07:17:28 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (eastapp2.East.Sun.COM [129.148.162.99])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id HAA29484;
	Wed, 7 Mar 2001 07:17:18 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Message-Id: <200103071517.HAA29484@nasnfs.Eng.Sun.COM>
Date: Wed, 7 Mar 2001 07:24:24 -0800
To: "Hongyi Li" <hyli@nortelnetworks.com>,
        "'Pat Calhoun'" <pcalhoun@nasnfs.eng.sun.com>
Cc: <seamoby@cdma-2000.org>
Reply-To: <pcalhoun@eng.sun.com>
Subject: RE: MM Draft v1 WAS: [seamoby] Context Transfer and Paging
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I will be sitting down with the IESG in Minn to determine how to proceed in
this area. I will keep the list posted.

PatC
>   Do you have idea about how do we precede with the requirements for
> Micro-mobility routing protocol?



From owner-seamoby@diameter.org  Wed Mar  7 13:50:53 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17255
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 13:50:52 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27GSU622522
	for seamoby-list; Wed, 7 Mar 2001 08:28:30 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27GSST22517
	for <seamoby@cdma-2000.org>; Wed, 7 Mar 2001 08:28:28 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA01321;
	Wed, 7 Mar 2001 08:36:31 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA12129;
	Wed, 7 Mar 2001 08:36:30 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (esun1as-be.Central.Sun.COM [129.147.34.142])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id IAA00517;
	Wed, 7 Mar 2001 08:36:20 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Message-Id: <200103071636.IAA00517@nasnfs.Eng.Sun.COM>
Date: Wed, 7 Mar 2001 08:43:27 -0800
To: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>,
        "'pcalhoun@nasnfs.eng.sun.com'" <pcalhoun@nasnfs.eng.sun.com>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>,
        "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>
Reply-To: <pcalhoun@eng.sun.com>
Subject: [seamoby] Re: micro-mobility requirements phase
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The ADs and I will be sitting down in Minn to figure out how to proceed.

I will keep the list posted on the result.

PatC
>Pat,
>
>Could you please tell me when the micro-mobility "requirements" phase is
>about to start, and what is the format for this?
>Thanks.
>
>Sharif




From owner-seamoby@diameter.org  Wed Mar  7 13:51:01 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17287
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 13:51:00 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27GsVr22609
	for seamoby-list; Wed, 7 Mar 2001 08:54:31 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27GsST22604
	for <seamoby@cdma-2000.org>; Wed, 7 Mar 2001 08:54:28 -0800
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Wed, 7 Mar 2001 10:59:42 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GLQTT6LH>; Wed, 7 Mar 2001 10:58:21 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E805B22638@zwdld001.ca.nortel.com>
From: "Hamid Syed" <hmsyed@nortelnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@interdigital.com>,
        "'Michael Thomas'" <mat@cisco.com>
Cc: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        "'pcalhoun@nasnfs.eng.sun.com'" <pcalhoun@nasnfs.eng.sun.com>,
        "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Paging requirements phase #3
Date: Wed, 7 Mar 2001 10:58:16 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A71F.6C34AC70"
X-Orig: <hmsyed@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A71F.6C34AC70
Content-Type: text/plain

Sharif,

here is the link for the draft .
http://www.ietf.org/internet-drafts/draft-sarikaya-seamoby-paging-requiremen
ts-00.txt

-Hamid

> -----Original Message-----
> From:	Shahrier, Sharif M. [SMTP:Sharif.Shahrier@interdigital.com]
> Sent:	Wednesday, March 07, 2001 10:33 AM
> To:	'Michael Thomas'; Shahrier, Sharif M.
> Cc:	'James Kempf'; 'pcalhoun@nasnfs.eng.sun.com';
> 'seamoby@cdma-2000.org'
> Subject:	RE: [seamoby] Paging requirements phase #3
> 
> Mike,
> 
> I know this is an indiviual draft, but if I'm not mistaken the e-mail from
> James stated that this draft was being cosidered as a working group draft.
> Is this true? 
> Personally speaking, I would have preferred if all the interested working
> group people had a chance to read it first and voice their oppinions. 
> I tried to get it from the I-D directory, but aparantly, its not there.
> 
> Sharif
> 
> -----Original Message-----
> From: Michael Thomas [mailto:mat@cisco.com]
> Sent: Wednesday, March 07, 2001 10:01 AM
> To: Shahrier, Sharif M.
> Cc: 'James Kempf'; 'pcalhoun@nasnfs.eng.sun.com';
> 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Paging requirements phase #3
> 
> 
> 
> Um, Sharif, this looks to be an individual
> submission.  If it were a working group draft, it
> would start draft-ietf-seamoby-[...]
> 
> 	    Mike
> 
> 
> Shahrier, Sharif M. writes:
>  > 
>  > 
>  > -----Original Message-----
>  > From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
>  > Sent: Tuesday, March 06, 2001 1:37 PM
>  > To: Sharif.Shahrier@interdigital.com
>  > Subject: RE: [seamoby] Paging requirements phase #2
>  > 
>  > 
>  > draft-sarikaya-seamoby-paging-requirements-00.txt
>  > 
>  > THIS DRAFT IS NOT AVAILABLE IN THE I-D ARCHIVES.
>  > 
>  > HOWEVER, I AM EXTREMELY PUZZULED HOW THIS I-D COULD HAVE BEEN ACCEPTED
> AS
> A
>  > WORKING GROUP DRAFT ON THE "REQUIREMENTS" PHASE BEFORE ALL THE
> INTERESTED
>  > PEOPLE HAD TIME TO READ IT BEFOREHAND AND VOICED THEIR OPPINIONS. IT IS
> ALSO
>  > SURPRISING TO ME THAT NO OTHER CANDIDATE DRAFTS HAD BEEN CONSIDERED AS
>  > ALTERNATIVES AND THEIR RELATIVE MERITS AND DE-MERITS HAD BEEN DEBATED
> BY
> ALL
>  > THE INTERESTED PARTIES. I FOLLOW THE SEAMOBY WORKING GROUP SEVERAL
> TIMES
> A
>  > DAY, AND I HAD NOT SEEN ANY DISCUSSIONS ON THIS ISSUE. THANK YOU.
>  > 
>  > SHARIF SHAHRIER

------_=_NextPart_001_01C0A71F.6C34AC70
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: [seamoby] Paging requirements phase #3</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Sharif,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">here is the link for =
the draft .</FONT>
<BR><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-sarikaya-seamoby-pagin=
g-requirements-00.txt" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-sarikaya-sea=
moby-paging-requirements-00.txt</A></FONT></U>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">-Hamid</FONT>
</P>
<UL>
<P><FONT SIZE=3D1 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">From:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Shahrier, Sharif M. =
[SMTP:Sharif.Shahrier@interdigital.com]</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Wednesday, March 07, 2001 10:33 AM</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">'Michael Thomas'; Shahrier, Sharif M.</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">'James Kempf'; 'pcalhoun@nasnfs.eng.sun.com'; =
'seamoby@cdma-2000.org'</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Arial">RE: [seamoby] Paging requirements =
phase #3</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Mike,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I know this is an indiviual draft, but =
if I'm not mistaken the e-mail from</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">James stated that this draft was =
being cosidered as a working group draft.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Is this true? </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Personally speaking, I would have =
preferred if all the interested working</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">group people had a chance to read it =
first and voice their oppinions. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">I tried to get it from the I-D =
directory, but aparantly, its not there.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Sharif</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">From: Michael Thomas [</FONT><U><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"mailto:mat@cisco.com">mailto:mat@cisco.com</A></FONT></U><FONT =
SIZE=3D2 FACE=3D"Arial">]</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Sent: Wednesday, March 07, 2001 10:01 =
AM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">To: Shahrier, Sharif M.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Cc: 'James Kempf'; =
'pcalhoun@nasnfs.eng.sun.com';</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">'seamoby@cdma-2000.org'</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Subject: RE: [seamoby] Paging =
requirements phase #3</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Um, Sharif, this looks to be an =
individual</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">submission.&nbsp; If it were a =
working group draft, it</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">would start =
draft-ietf-seamoby-[...]</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp; Mike</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Shahrier, Sharif M. writes:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; -----Original =
Message-----</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; From: James Kempf =
[</FONT><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"mailto:kempf@heliopolis.Eng.Sun.COM">mailto:kempf@heliopolis.Eng=
.Sun.COM</A></FONT></U><FONT SIZE=3D2 FACE=3D"Arial">]</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Sent: Tuesday, March 06, =
2001 1:37 PM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; To: =
Sharif.Shahrier@interdigital.com</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; Subject: RE: [seamoby] =
Paging requirements phase #2</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; =
draft-sarikaya-seamoby-paging-requirements-00.txt</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; THIS DRAFT IS NOT =
AVAILABLE IN THE I-D ARCHIVES.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; HOWEVER, I AM EXTREMELY =
PUZZULED HOW THIS I-D COULD HAVE BEEN ACCEPTED AS</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">A</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; WORKING GROUP DRAFT ON THE =
&quot;REQUIREMENTS&quot; PHASE BEFORE ALL THE INTERESTED</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; PEOPLE HAD TIME TO READ IT =
BEFOREHAND AND VOICED THEIR OPPINIONS. IT IS</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">ALSO</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; SURPRISING TO ME THAT NO =
OTHER CANDIDATE DRAFTS HAD BEEN CONSIDERED AS</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; ALTERNATIVES AND THEIR =
RELATIVE MERITS AND DE-MERITS HAD BEEN DEBATED BY</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">ALL</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; THE INTERESTED PARTIES. I =
FOLLOW THE SEAMOBY WORKING GROUP SEVERAL TIMES</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">A</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; DAY, AND I HAD NOT SEEN =
ANY DISCUSSIONS ON THIS ISSUE. THANK YOU.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&gt; SHARIF SHAHRIER</FONT>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C0A71F.6C34AC70--


From owner-seamoby@diameter.org  Wed Mar  7 14:15:41 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18390
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 14:15:41 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27GOP522502
	for seamoby-list; Wed, 7 Mar 2001 08:24:25 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27GOMT22497
	for <seamoby@cdma-2000.org>; Wed, 7 Mar 2001 08:24:22 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA29123;
	Wed, 7 Mar 2001 08:32:27 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA11128;
	Wed, 7 Mar 2001 08:32:26 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (esun1as-be.Central.Sun.COM [129.147.34.142])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id IAA00466;
	Wed, 7 Mar 2001 08:32:16 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Message-Id: <200103071632.IAA00466@nasnfs.Eng.Sun.COM>
Date: Wed, 7 Mar 2001 08:39:22 -0800
To: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>,
        "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>
Cc: "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>,
        "'pcalhoun@nasnfs.eng.sun.com'" <pcalhoun@nasnfs.eng.sun.com>
Reply-To: <pcalhoun@eng.sun.com>
Subject: RE: [seamoby] Paging requirements phase #3
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


>draft-sarikaya-seamoby-paging-requirements-00.txt
>
>THIS DRAFT IS NOT AVAILABLE IN THE I-D ARCHIVES.

First, no need to shout.

>
>HOWEVER, I AM EXTREMELY PUZZULED HOW THIS I-D COULD HAVE BEEN ACCEPTED AS A
>WORKING GROUP DRAFT ON THE "REQUIREMENTS" PHASE BEFORE ALL THE INTERESTED
>PEOPLE HAD TIME TO READ IT BEFOREHAND AND VOICED THEIR OPPINIONS. 

If the draft does have the prefix draft-ietf-seamoby-, it is NOT a WG draft.
This is an individual submission, and is not considered WG work. If the \
design team decides that it wants to use an existing draft as a starting point,
then it is free to do so, but this is not mandated.

PatC



From owner-seamoby@diameter.org  Wed Mar  7 14:30:07 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19010
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 14:30:06 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27HBY222668
	for seamoby-list; Wed, 7 Mar 2001 09:11:34 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27HBVT22663
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 09:11:31 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f27HIE001105;
	Wed, 7 Mar 2001 09:18:14 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f27HJaI04991;
	Wed, 7 Mar 2001 09:19:36 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A08.005F526F ; Wed, 7 Mar 2001 09:21:10 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: tpagtzis@iprg.nokia.com
cc: James Kempf <kempf@heliopolis.Eng.Sun.COM>, charliep@iprg.nokia.com,
        kulwinder.atwal@zucotto.com, seamoby@diameter.org
Message-ID: <88256A08.005F505A.00@hqoutbound.ops.3com.com>
Date: Wed, 7 Mar 2001 11:15:52 -0600
Subject: Re: [seamoby] How to Convince the BARB to work with IETF?
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk




Hi Theo,

I am quite happy to see that I am not the only person that occasionally gets
"passionate" about this stuff.  BTW, it doesn't pay to snipe at people getting
fiesty at each other.  Sometimes the creative juices really flow then!    Let
them rant and rave, it can open dark caverns of their minds that we can all
collectively explore.  :-)

Anyway,  with respect to all these different BOFs potentially coming down
the pipe in the IETF , AAAAaaaarrrrggggghhh!!!!

THAT IS EXACTLY WHAT THE CRAPS BOF WAS FOR!!!!!!

GIMME A C = COMMON
GIMME A R = RADIO
GIMME A A = ACCESS
GIMME A P = PROTOCOL
GIMME S S = SET

I thought we could avoid this mess by realizing the commonolalities that
many radio  L2's have (yes I know what PILC is doing & that's different) in
signalling, access, and handoff control and create an IP based
L2 to L3 hinting and Network Access Point (NAP) peer-to-peer and
NAP to MN protocol.  Alas, it got plucked out of the SeaMoby charter
faster than you can say Bob's your uncle.  So the Bluetooth BOF
is the another in the series of L2X over IP BOFs that will continue
to bombard the IETF and waste all of our precious time and mimize
commonalities I guess.

C Ya real soon,

Phil



Having read the Bluetooth BOF considerations below I am wondering whether there
will be an upcoming

W-CDMA or UMTS BOF
802.11 BOF
HIPERLAN  BOF

so that we can investigate in particular issues of

IP over W-CDMA/UMTS protocols
IP over 802.11b/d/e protocols
IP over HIPERLAN protocols.

and if we really want to be pedantic

IP over diffuse Infra Red since some spec of IR managed to come out





From owner-seamoby@diameter.org  Wed Mar  7 14:31:25 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19094
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 14:31:24 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27HVm922747
	for seamoby-list; Wed, 7 Mar 2001 09:31:48 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27HVkT22742
	for <seamoby@cdma-2000.org>; Wed, 7 Mar 2001 09:31:46 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GNPD3NA1>; Wed, 7 Mar 2001 12:39:56 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A26@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@interdigital.com>,
        "'Michael Thomas'" <mat@cisco.com>
Cc: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        "'pcalhoun@nasnfs.eng.sun.com'" <pcalhoun@nasnfs.eng.sun.com>,
        "'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
Subject: RE: [seamoby] Paging requirements phase #3
Date: Wed, 7 Mar 2001 12:39:56 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@interdigital.com]
> Sent: Wednesday, March 07, 2001 10:33 AM
> To: 'Michael Thomas'; Shahrier, Sharif M.
> Cc: 'James Kempf'; 'pcalhoun@nasnfs.eng.sun.com';
> 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Paging requirements phase #3
> 
> 
> Mike,
> 
> I know this is an indiviual draft, but if I'm not mistaken 
> the e-mail from
> James stated that this draft was being cosidered as a working 
> group draft.
> Is this true?
> Personally speaking, I would have preferred if all the 
> interested working
> group people had a chance to read it first and voice their oppinions. 
> I tried to get it from the I-D directory, but aparantly, its 
> not there.

I found it attached to an email sent to the seamoby-paging list by Behcet
dated Mon 12, Feb.  He said, he was having trouble getting it into the I-D
directory so he sent to the seamoby-paging list.

- Kulwinder.

> 
> Sharif
> 
> -----Original Message-----
> From: Michael Thomas [mailto:mat@cisco.com]
> Sent: Wednesday, March 07, 2001 10:01 AM
> To: Shahrier, Sharif M.
> Cc: 'James Kempf'; 'pcalhoun@nasnfs.eng.sun.com';
> 'seamoby@cdma-2000.org'
> Subject: RE: [seamoby] Paging requirements phase #3
> 
> 
> 
> Um, Sharif, this looks to be an individual
> submission.  If it were a working group draft, it
> would start draft-ietf-seamoby-[...]
> 
> 	    Mike
> 
> 
> Shahrier, Sharif M. writes:
>  > 
>  > 
>  > -----Original Message-----
>  > From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
>  > Sent: Tuesday, March 06, 2001 1:37 PM
>  > To: Sharif.Shahrier@interdigital.com
>  > Subject: RE: [seamoby] Paging requirements phase #2
>  > 
>  > 
>  > draft-sarikaya-seamoby-paging-requirements-00.txt
>  > 
>  > THIS DRAFT IS NOT AVAILABLE IN THE I-D ARCHIVES.
>  > 
>  > HOWEVER, I AM EXTREMELY PUZZULED HOW THIS I-D COULD HAVE 
> BEEN ACCEPTED AS
> A
>  > WORKING GROUP DRAFT ON THE "REQUIREMENTS" PHASE BEFORE ALL 
> THE INTERESTED
>  > PEOPLE HAD TIME TO READ IT BEFOREHAND AND VOICED THEIR 
> OPPINIONS. IT IS
> ALSO
>  > SURPRISING TO ME THAT NO OTHER CANDIDATE DRAFTS HAD BEEN 
> CONSIDERED AS
>  > ALTERNATIVES AND THEIR RELATIVE MERITS AND DE-MERITS HAD 
> BEEN DEBATED BY
> ALL
>  > THE INTERESTED PARTIES. I FOLLOW THE SEAMOBY WORKING GROUP 
> SEVERAL TIMES
> A
>  > DAY, AND I HAD NOT SEEN ANY DISCUSSIONS ON THIS ISSUE. THANK YOU.
>  > 
>  > SHARIF SHAHRIER
> 


From owner-seamoby@diameter.org  Wed Mar  7 14:33:57 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19187
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 14:33:57 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27Hju322812
	for seamoby-list; Wed, 7 Mar 2001 09:45:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27HjsT22807
	for <seamoby@cdma-2000.org>; Wed, 7 Mar 2001 09:45:54 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA09132;
	Wed, 7 Mar 2001 09:54:02 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA21550;
	Wed, 7 Mar 2001 09:53:59 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id JAA28082;
	Wed, 7 Mar 2001 09:53:58 -0800 (PST)
Message-Id: <200103071753.JAA28082@heliopolis.Eng.Sun.COM>
Date: Wed, 7 Mar 2001 09:53:58 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] Paging requirements phase #3
To: kempf@heliopolis.Eng.Sun.COM, Sharif.Shahrier@interdigital.com
Cc: pcalhoun@nasnfs.eng.sun.com, seamoby@cdma-2000.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: +LQf3ul/b1MGbptGr0Sofw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Sharif,

You don't have to shout. :-)

Anybody can submit an individual draft to internet-drafts@ietf.org
about anything they want. It is not a working group draft at
this point. My opinion (and it is mine alone so far) is that it
is a good start, and the fact that the author submitted it suggested
to me that he may be interested in becoming the document editor,
which is why I asked. He hasn't answered yet.

Ultimately, the working group requirements draft will reflect the
requirements that the working group presents. Now, could you please
stop asking about this and start sending your requirements to
the seamoby-paging@diameter.org paging design team alias? Thanx.

		jak


>From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
>To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>
>Cc: "'pcalhoun@nasnfs.eng.sun.com'" <pcalhoun@nasnfs.Eng.Sun.COM>, 
"'seamoby@cdma-2000.org'" <seamoby@cdma-2000.org>
>Subject: RE: [seamoby] Paging requirements phase #3
>Date: Wed, 7 Mar 2001 08:50:24 -0500 
>MIME-Version: 1.0
>
>
>
>-----Original Message-----
>From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
>Sent: Tuesday, March 06, 2001 1:37 PM
>To: Sharif.Shahrier@interdigital.com
>Subject: RE: [seamoby] Paging requirements phase #2
>
>
>draft-sarikaya-seamoby-paging-requirements-00.txt
>
>THIS DRAFT IS NOT AVAILABLE IN THE I-D ARCHIVES.
>
>HOWEVER, I AM EXTREMELY PUZZULED HOW THIS I-D COULD HAVE BEEN ACCEPTED AS A
>WORKING GROUP DRAFT ON THE "REQUIREMENTS" PHASE BEFORE ALL THE INTERESTED
>PEOPLE HAD TIME TO READ IT BEFOREHAND AND VOICED THEIR OPPINIONS. IT IS ALSO
>SURPRISING TO ME THAT NO OTHER CANDIDATE DRAFTS HAD BEEN CONSIDERED AS
>ALTERNATIVES AND THEIR RELATIVE MERITS AND DE-MERITS HAD BEEN DEBATED BY ALL
>THE INTERESTED PARTIES. I FOLLOW THE SEAMOBY WORKING GROUP SEVERAL TIMES A
>DAY, AND I HAD NOT SEEN ANY DISCUSSIONS ON THIS ISSUE. THANK YOU.
>
>SHARIF SHAHRIER



From owner-seamoby@diameter.org  Wed Mar  7 15:19:19 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA21264
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 15:19:18 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27Hcof22773
	for seamoby-list; Wed, 7 Mar 2001 09:38:50 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27HcmT22768
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 09:38:48 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA25566;
	Wed, 7 Mar 2001 09:46:54 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f27HkqQ27394;
	Wed, 7 Mar 2001 09:46:52 -0800
X-mProtect:  Wed, 7 Mar 2001 09:46:52 -0800 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90)
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdMm8Sdc; Wed, 07 Mar 2001 09:46:39 PST
Message-ID: <3AA673FF.15FB7483@iprg.nokia.com>
Date: Wed, 07 Mar 2001 09:46:39 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 2.2.6-RELEASE i386)
MIME-Version: 1.0
To: seamoby_context@standards.nortelnetworks.com
CC: seamoby@diameter.org
Subject: [seamoby] Input for CT requirements
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello folks,

here is some input for the conference call on Monday. These are some
basic requirements, and are explained in detail in the draft:

http://people.nokia.net/charliep/txt/smoothv6/CT-02.txt

Regards,

-Rajeev


- Feature contexts must be represented so that they are inter-operable.
In other words, a receiving node must be able to interpret the feature
context and process it appropriately in a standard manner.

- It should be possible to separate how the feature contexts are carried
from what messages carry them. This would allow handling multiple
handover scenarios in a flexible fashion.

- It must be possible to carry feature contexts in signals that
facilitate fast handover response times.


From owner-seamoby@diameter.org  Wed Mar  7 16:13:26 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22894
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 16:13:25 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27IwfR23027
	for seamoby-list; Wed, 7 Mar 2001 10:58:41 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27IwdT23022
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 10:58:39 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA10664;
	Wed, 7 Mar 2001 11:06:46 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA22855;
	Wed, 7 Mar 2001 11:06:41 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id LAA00960;
	Wed, 7 Mar 2001 11:06:41 -0800 (PST)
Message-Id: <200103071906.LAA00960@heliopolis.Eng.Sun.COM>
Date: Wed, 7 Mar 2001 11:06:41 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: [seamoby] To talk about L2 or not? 
To: David.P.Martin@nextel.com
Cc: charliep@iprg.nokia.com, seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 0VixrUGbIdhLCMZx7X75GA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Dave,

>However, I think it is perfectly reasonable to focus on protocol
>interoperability.  For example, I think it is perfectly acceptable for a
>micro-mobility protocol to have hooks built in for Layer 2 (aka access
>network) triggers in order to achieve greater efficiency.  Of course it
>would be great if existing layer 2 protocols could take advantage of these
>hooks from day one, but if not, that's a layer 2 problem.  I think of
>several examples of where this would help in the Mobile IP space, and my
>guess is that there maybe some that could help in the seamoby space as well
>(we'll find out as we start moving into the solution space).

This is an idea that I have been in favor of for some time, particularly
with respect to fast handoff in Mobile IP.

The problem is that it is very difficult to get good performance and
a clean design without making some assumptions about what L2 provides. My 
feeling is that one can come up with a set of abstractions which describe the L2
support required, then design the protocol around those. The abstractions
are not specific to any particular L2, and they can be structured such that a 
particular L2 can implement a certain set, and the L3 protocol can
be designed to reflect that. If the L2 implements none of these hooks,
then there needs to be a simple fallback L3 implementation which might not
perform the best, but nevertheless is possible.

A precedent is how maximum frame size is handled in the IPv6 specification.
In RFC 2460 on pg. 24, IPv6 requires that every link layer have an
MTU of 1280 octets or greater. This establishes an abstract L2 specification
for IPv6 with regard to MTU size, and specific L2 implementations must
match it by providing segmentation/reassembly if they don't support
that large an MTU.

It seems reasonable to me that the new functionality involved in mobility
(handoff, maybe paging) will naturally require similar L2 abstractions, 
because mobility has historically not been part of the base assumed
available for implementing IP. Naturally, one doesn't want to go
overboard, so the abstractions should be carefully chosen. 

There seems to be a certain amount of resistance to this position within
the mobile IP group, and I have not yet heard anyone articulate a clear
position why. Deering and Hinden could have left out the abstraction
of L2 included in the IPv6 spec, but they chose to include it, presumably
because it simplified the IPv6 design, or promised better performance,
or possibly both. I think the same will prove to be true of L2 
abstractions for mobility.

		jak



From owner-seamoby@diameter.org  Wed Mar  7 17:07:44 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA24432
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 17:07:43 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27K5wk23229
	for seamoby-list; Wed, 7 Mar 2001 12:05:58 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27K5tT23224
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 12:05:56 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GNPD3NGV>; Wed, 7 Mar 2001 15:14:06 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A31@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Phil_Neumiller@3com.com'" <Phil_Neumiller@3Com.com>,
        tpagtzis@iprg.nokia.com
Cc: James Kempf <kempf@heliopolis.Eng.Sun.COM>, charliep@iprg.nokia.com,
        kulwinder.atwal@herc.zucotto.com, seamoby@diameter.org
Subject: RE: [seamoby] How to Convince the BARB to work with IETF?
Date: Wed, 7 Mar 2001 15:14:05 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Phil_Neumiller@3com.com [mailto:Phil_Neumiller@3com.com]
> Sent: Wednesday, March 07, 2001 12:16 PM
> To: tpagtzis@iprg.nokia.com
> Cc: James Kempf; charliep@iprg.nokia.com;
> kulwinder.atwal@herc.zucotto.com; seamoby@diameter.org
> Subject: Re: [seamoby] How to Convince the BARB to work with IETF?
> 
> 
> 
> 
> 
> Hi Theo,
> 
> I am quite happy to see that I am not the only person that 
> occasionally gets
> "passionate" about this stuff.  BTW, it doesn't pay to snipe 
> at people getting
> fiesty at each other.  Sometimes the creative juices really 
> flow then!    Let
> them rant and rave, it can open dark caverns of their minds 
> that we can all
> collectively explore.  :-)
> 
> Anyway,  with respect to all these different BOFs potentially 
> coming down
> the pipe in the IETF , AAAAaaaarrrrggggghhh!!!!
> 
> THAT IS EXACTLY WHAT THE CRAPS BOF WAS FOR!!!!!!
> 
> GIMME A C = COMMON
> GIMME A R = RADIO
> GIMME A A = ACCESS
> GIMME A P = PROTOCOL
> GIMME S S = SET

Do you have a draft to go with this CRAPS?

- Kulwinder.


From owner-seamoby@diameter.org  Wed Mar  7 17:19:16 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA24808
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 17:19:16 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27KD9b23269
	for seamoby-list; Wed, 7 Mar 2001 12:13:09 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27KD5T23264
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 12:13:05 -0800
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f27KL8202827
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 22:21:08 +0200 (EET)
Received: from esebh12nok.ntc.nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T52279944baac158f21082@esvir01nok.ntc.nokia.com> for <seamoby@diameter.org>;
 Wed, 7 Mar 2001 22:21:14 +0200
Received: by esebh12nok with Internet Mail Service (5.5.2652.78)
	id <G3T1F2ND>; Wed, 7 Mar 2001 22:21:14 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680AB88@eseis04nok>
From: john.loughney@nokia.com
To: seamoby@diameter.org
Subject: [seamoby] MM vs CT
Date: Wed, 7 Mar 2001 22:21:12 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi all,

I'd like to get everyone's feeling about an issue.

It has been suggested that a handoff mechanism
may like to know the capabilities of a handoff 
target.  This could be useful, for example, when
there is more than one target.  The handoff 
mechanism may want to chose the one which
fufills the QoS requirements, for example.

My question is: what design team should tackle
this issue, MicroMobility or Context Transfer?

thanks,
John


From owner-seamoby@diameter.org  Wed Mar  7 18:19:51 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA26872
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 18:19:50 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27KFAT23279
	for seamoby-list; Wed, 7 Mar 2001 12:15:10 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27KF7T23274
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 12:15:07 -0800
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f27KNGd10868
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 21:23:16 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Wed Mar 07 21:24:52 2001 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2651.58)
	id <FV8X446L>; Wed, 7 Mar 2001 21:19:23 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBF7@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: seamoby@diameter.org
Subject: RE: [seamoby] To talk about L2 or not?
Date: Wed, 7 Mar 2001 21:23:14 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk


> There seems to be a certain amount of resistance to this position within
> the mobile IP group, and I have not yet heard anyone articulate a clear
> position why. 
> 
	=> Actually I've talked to a few active members in the MIP group
	about that idea last year and they all seemed to be supportive. 
	I've had a half finished draft on this topic (with a couple of people 
	here ) for over a year and never got around to it. But I think it's 
	essential to do .... one day !

	Hesham




From owner-seamoby@diameter.org  Wed Mar  7 18:46:46 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA27620
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 18:46:46 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27Lm3K23581
	for seamoby-list; Wed, 7 Mar 2001 13:48:03 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from atlsnmx1.nextel.com (atlsnmx1.nextel.com [167.20.198.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27Lm0T23576
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 13:48:00 -0800
Received: from atlntgw01.nextel.com (atlntgw01.nextel.com [10.8.79.187])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id QAA29561;
	Wed, 7 Mar 2001 16:56:08 -0500 (EST)
Received: by atlntgw01.nextel.com with Internet Mail Service (5.5.2650.21)
	id <FXBJG38Q>; Wed, 7 Mar 2001 16:56:10 -0500
Message-ID: <020A5EC56F3FD411B5230008C716D085868430@nhqntex01.nextel.com>
From: "Martin, David P" <David.P.Martin@nextel.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        "Martin, David P"
	 <David.P.Martin@nextel.com>
Cc: charliep@iprg.nokia.com, seamoby@diameter.org
Subject: RE: [seamoby] To talk about L2 or not? 
Date: Wed, 7 Mar 2001 16:51:24 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

James,
I agree as well, in fact it was probably you or someone else in one of these
groups that converted me :)

> 
> Hi Dave,
> 
> >However, I think it is perfectly reasonable to focus on protocol
> >interoperability.  For example, I think it is perfectly 
> acceptable for a
> >micro-mobility protocol to have hooks built in for Layer 2 
> (aka access
> >network) triggers in order to achieve greater efficiency.  
> Of course it
> >would be great if existing layer 2 protocols could take 
> advantage of these
> >hooks from day one, but if not, that's a layer 2 problem.  I think of
> >several examples of where this would help in the Mobile IP 
> space, and my
> >guess is that there maybe some that could help in the 
> seamoby space as well
> >(we'll find out as we start moving into the solution space).
> 
> This is an idea that I have been in favor of for some time, 
> particularly
> with respect to fast handoff in Mobile IP.
> 
> The problem is that it is very difficult to get good performance and
> a clean design without making some assumptions about what L2 
> provides. My 
> feeling is that one can come up with a set of abstractions 
> which describe the L2
> support required, then design the protocol around those. The 
> abstractions
> are not specific to any particular L2, and they can be 
> structured such that a 
> particular L2 can implement a certain set, and the L3 protocol can
> be designed to reflect that. If the L2 implements none of these hooks,
> then there needs to be a simple fallback L3 implementation 
> which might not
> perform the best, but nevertheless is possible.
> 
> A precedent is how maximum frame size is handled in the IPv6 
> specification.
> In RFC 2460 on pg. 24, IPv6 requires that every link layer have an
> MTU of 1280 octets or greater. This establishes an abstract 
> L2 specification
> for IPv6 with regard to MTU size, and specific L2 implementations must
> match it by providing segmentation/reassembly if they don't support
> that large an MTU.
> 
> It seems reasonable to me that the new functionality involved 
> in mobility
> (handoff, maybe paging) will naturally require similar L2 
> abstractions, 
> because mobility has historically not been part of the base assumed
> available for implementing IP. Naturally, one doesn't want to go
> overboard, so the abstractions should be carefully chosen. 
> 
> There seems to be a certain amount of resistance to this 
> position within
> the mobile IP group, and I have not yet heard anyone 
> articulate a clear
> position why. Deering and Hinden could have left out the abstraction
> of L2 included in the IPv6 spec, but they chose to include 
> it, presumably
> because it simplified the IPv6 design, or promised better performance,
> or possibly both. I think the same will prove to be true of L2 
> abstractions for mobility.
> 
> 		jak
> 


From owner-seamoby@diameter.org  Wed Mar  7 19:00:19 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27927
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 19:00:18 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27ML5l23718
	for seamoby-list; Wed, 7 Mar 2001 14:21:05 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27ML2T23713
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 14:21:02 -0800
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f27MTCd24815
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 23:29:12 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Wed Mar 07 23:29:12 2001 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2651.58)
	id <F1J0PNHL>; Wed, 7 Mar 2001 23:29:11 +0100
Message-ID: <034BEFD03799D411A59F00508BDF7546013DBBFB@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: seamoby@diameter.org
Subject: RE: [seamoby] To talk about L2 or not?
Date: Wed, 7 Mar 2001 23:29:10 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk

	Hi John,

> > 	=> Actually I've talked to a few active members in the MIP group
> > 	about that idea last year and they all seemed to be supportive. 
> > 	I've had a half finished draft on this topic (with a 
> >     couple of people 
> > 	here ) for over a year and never got around to it. But 
> >     I think it's essential to do .... one day !
> 
> I'm sure there are some folks on this list that will help you
> finish it.  Would you consider discussion of this work here?
> 
	=> Sure, it seems there is interest in this area. I've already
	received a couple of supporitve private mails expressing 
	interest. So hopefully we can have something out after 
	Minneapolis.

	Hesham 


From owner-seamoby@diameter.org  Wed Mar  7 19:26:02 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA28393
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 19:26:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27Lt7g23607
	for seamoby-list; Wed, 7 Mar 2001 13:55:07 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27Lt3T23602
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 13:55:03 -0800
Received: from esvir08nok.nokia.com (esvir08nokt.ntc.nokia.com [172.21.143.40])
	by mgw-x4.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f27M5HR14346
	for <seamoby@diameter.org>; Thu, 8 Mar 2001 00:05:18 +0200 (EET)
Received: from esebh03nok.ntc.nokia.com (unverified) by esvir08nok.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5227f68fbcac158f28078@esvir08nok.nokia.com>;
 Thu, 8 Mar 2001 00:03:08 +0200
Received: by esebh03nok with Internet Mail Service (5.5.2652.78)
	id <G3SZF2FG>; Thu, 8 Mar 2001 00:03:08 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680AB8B@eseis04nok>
From: john.loughney@nokia.com
To: Hesham.Soliman@era.ericsson.se, seamoby@diameter.org
Subject: RE: [seamoby] To talk about L2 or not?
Date: Thu, 8 Mar 2001 00:03:06 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Hesham,

> 	=> Actually I've talked to a few active members in the MIP group
> 	about that idea last year and they all seemed to be supportive. 
> 	I've had a half finished draft on this topic (with a 
>     couple of people 
> 	here ) for over a year and never got around to it. But 
>     I think it's essential to do .... one day !

I'm sure there are some folks on this list that will help you
finish it.  Would you consider discussion of this work here?

John


From owner-seamoby@diameter.org  Wed Mar  7 19:40:08 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA28715
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 19:40:07 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27MjMk23814
	for seamoby-list; Wed, 7 Mar 2001 14:45:22 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27MjKT23809
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 14:45:20 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GNPD3NNP>; Wed, 7 Mar 2001 17:53:31 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A3E@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        seamoby@diameter.org
Subject: RE: [seamoby] MM vs CT   ( was FW: CT problem statement and CNP
Date: Wed, 7 Mar 2001 17:53:30 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

We discussed this issue on the CT team.  Below you will find the short
thread.

A better place for it might the MM mechanism, or MM protocol.

- Kulwinder.

> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> Sent: Wednesday, March 07, 2001 3:21 PM
> To: seamoby@diameter.org
> Subject: [seamoby] MM vs CT
> 
> 
> Hi all,
> 
> I'd like to get everyone's feeling about an issue.
> 
> It has been suggested that a handoff mechanism
> may like to know the capabilities of a handoff 
> target.  This could be useful, for example, when
> there is more than one target.  The handoff 
> mechanism may want to chose the one which
> fufills the QoS requirements, for example.
> 
> My question is: what design team should tackle
> this issue, MicroMobility or Context Transfer?
> 
> thanks,
> John
> 


-----Original Message-----
From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
Sent: Thursday, January 18, 2001 2:23 PM
To: SEAMOBY_CONTEXT@standards.nortelnetworks.com
Subject: CT problem statement and CNP


Hi,

I changed the subject a bit.

I agree with Kulwinder about the administrative context, and Phil: I am not
talking about negotiations either:) In order to make context transfer/
handover as successful as possible, the source should know about its
neighbors and their capabilities, such as supported QoS, AAA mechanisms
(diameter, radius) and such.

So we might want to talk about possibility of capability transfer (in
reverse direction and maybe prior to context transfer) as a part of problem
statement.

This might be going into solution space, but we are talking a lot about
context transfer failure and protocol mismatch, so I feel, we should at
least take a position about whether we want to have capability transfer as
part of a context transfer protocol or not (I am favorable to it) and if not
mention it in the problem statement.

The reason, I am for it, is that, it would also make any protocol like
Phil's contract net protocol go smoother by making it proactive, rather than
ACK/Nack type protocol.

Regards,
Madjid



-----Original Message-----
From: Jukka Manner [mailto:jmanner@CS.HELSINKI.FI]
Sent: Thursday, January 18, 2001 1:26 AM
To: SEAMOBY_CONTEXT@STANDARDS.NORTELNETWORKS.COM
Subject: Re: About CT & 'Negotiation'


        Hi,

        I know the idea of deciding on the target of CT is part of the
solutions
space, but I would (not sure though) see that some mentioning of this could
be
part of the the problem discussion: what could Seamoby do better than the
present schemes don't do...

        Jukka


On Wed, 17 Jan 2001, Kulwinder Atwal wrote:

>
>
> >     Hi, addiotonal question to that:
> >
> >     If there are two candidate ARs (CARs), of which one
> > could provide a PQ
> > and the other can only provide MAQ. Shouldn't the current AR
> > have a way to know
> > this beforehand, or at least get feedback from the new AR
> > about how well it can
> > support the transfered context?
> >
> >     I know we are moving into the implementation/technology
> > too soon...
> >
> >
> >     Jukka
> > > > I've clipped your comments out, but I wanted to address Context
> > > > Negotiation & Context Transfer thread.
> > > >
> > > > IMO, the 'entity' (the piece of code, for example) that decides
> > > > whether to hand-off or not, should decide if the target
> > > > node can support the handoff.  I don't think that should be
> > > > part of the context transfer.
>
> I referred to this about a month ago, but I was accused of jumping into
the
> solution space way too early.  We need two classes of context:
>
> - Micro-flow Context
> - Administrative Context:
>
> Administrative Context: Context that describes the QoS policy of the APs
> nearby.
>
> I referred to it as a Radio Map for a hetrogenous neighbourhood, and a
> Tri-cell for a homogenous neighbourhood.  A Tri-cell because a minimum of
> three pionts are needed to triangulate the relative position of a mobile
> based on signal strength.  And a Bi-cell becuase a minumum of two points
are
> needed to get a fix on relative velocity.  This of course assumes that
> Multi-path and other types of Interference are managable.
>
> But, again I have digressed into solution space.
>
> - Kulwinder.


From owner-seamoby@diameter.org  Wed Mar  7 19:43:31 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA28794
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 19:43:30 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27MdtG23786
	for seamoby-list; Wed, 7 Mar 2001 14:39:55 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6])
	by charizard.diameter.org (8.11.3/8.11.3) with SMTP id f27MdrT23781
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 14:39:53 -0800
Received: from bronx.dnrc.bell-labs.com ([135.180.160.8]) by dirty; Wed Mar  7 17:47:39 EST 2001
Received: from dnrc.bell-labs.com (IDENT:ramjee@mandak [135.180.240.136])
	by bronx.dnrc.bell-labs.com (8.9.3/8.9.3) with ESMTP id RAA26330;
	Wed, 7 Mar 2001 17:47:42 -0500 (EST)
Message-ID: <3AA6BAE1.7A9BEEF3@dnrc.bell-labs.com>
Date: Wed, 07 Mar 2001 17:49:05 -0500
From: Ramachandran Ramjee <ramjee@dnrc.bell-labs.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.17-14 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: john.loughney@nokia.com
CC: seamoby@diameter.org
Subject: Re: [seamoby] MM vs CT
References: <01D91AFB08B6D211BFD00008C7EABAE10680AB88@eseis04nok>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi John,

My view is that capability discovery should be
separate from micro-mobility since
capability discovery is applicable to both
Mobile IP and micro-mobility. Now whether that
should be part of CT or a separate item, I will
leave it to the higher powers to decide :-)

-Ram



john.loughney@nokia.com wrote:
> 
> Hi all,
> 
> I'd like to get everyone's feeling about an issue.
> 
> It has been suggested that a handoff mechanism
> may like to know the capabilities of a handoff
> target.  This could be useful, for example, when
> there is more than one target.  The handoff
> mechanism may want to chose the one which
> fufills the QoS requirements, for example.
> 
> My question is: what design team should tackle
> this issue, MicroMobility or Context Transfer?
> 
> thanks,
> John


From owner-seamoby@diameter.org  Wed Mar  7 20:29:21 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA29421
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 20:29:20 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27NhbQ23990
	for seamoby-list; Wed, 7 Mar 2001 15:43:37 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27NhYT23985
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 15:43:35 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f27NoI006440;
	Wed, 7 Mar 2001 15:50:18 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f27NpeI29935;
	Wed, 7 Mar 2001 15:51:40 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A08.008334C8 ; Wed, 7 Mar 2001 15:53:07 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: john.loughney@nokia.com
cc: seamoby@diameter.org
Message-ID: <88256A08.008333B3.00@hqoutbound.ops.3com.com>
Date: Wed, 7 Mar 2001 17:50:30 -0600
Subject: Re: [seamoby] MM vs CT
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk



Hi John,

Boy am I on the same page with you here John.  I take a much MORE
radical stance (as usual :-)) and believe they are inseparable.  In the
CNP draft (that was submitted long before the group was prepared
for such an animal) I combined a "contract" with a handoff request
and "bid" with a handoff reply messages that came in from the bidders
i.e. all the handoff candidates.  Recently, I have been exploring
how this exact same mechanism COULD be extended "seamlessly"
to AODV thus giving us a very nice contract handover mechanism
that works for MIP, (micro-IF-needed???), and ad-hoc.

Sorry for the sales pitch, but I have just been working on this and
I have been kind of excited about it.

1).  Without getting hung up on the technical details let us assume that
       macro diversity soft-handover i.e. a common bearer format can be
       collected from multiple APs/BTSs even with different RF technologies
        in a central point AP and we call it IPSHO OK.

2). Given 1 we have 4-5? handover types from an AP perspective

     0)  Softer (not allowed according to the IETF) :-)  Intra-AP handover
     1) Softy (micro-mobilility) (aka SeaMoby) (no IP addr change) existence
tenuous
          NOTE:  Happens in the real world all the time.
          NOTE:  Being standardized by IEEE 802.11 TG 11 as we argue here.
    A).  Hard handover
    B)   Hard handover (with make before break)
    C).  IPSHO (keeps multiple IP tunnels active)

3). It seems pretty obvious that in cases B and C that the AP would
      like to know what it's cared for MN is getting into before subjecting
      it's MN to the new AP.

I know this does not answer your question directly.   Maybe its
munchies for thought.  I hope.

Take it easy.

Phil




Sent by:  john.loughney@nokia.com


To:   seamoby@diameter.org
cc:    (Phil Neumiller/MW/US/3Com)
Subject:  [seamoby] MM vs CT



Hi all,

I'd like to get everyone's feeling about an issue.

It has been suggested that a handoff mechanism
may like to know the capabilities of a handoff
target.  This could be useful, for example, when
there is more than one target.  The handoff
mechanism may want to chose the one which
fufills the QoS requirements, for example.

My question is: what design team should tackle
this issue, MicroMobility or Context Transfer?

thanks,
John






From owner-seamoby@diameter.org  Wed Mar  7 20:29:51 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA29432
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 20:29:51 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f27Nlqf24001
	for seamoby-list; Wed, 7 Mar 2001 15:47:52 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from motgate3.mot.com (motgate3.mot.com [144.189.100.103])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f27NloT23996
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 15:47:50 -0800
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate3.mot.com (motgate3 2.1) with ESMTP id QAA21859 for <seamoby@diameter.org>; Wed, 7 Mar 2001 16:51:03 -0700 (MST)]
Received: [from il75exm02.cig.mot.com (IL75EXM02.cig.mot.com [136.182.110.102]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id QAA02398 for <seamoby@diameter.org>; Wed, 7 Mar 2001 16:56:00 -0700 (MST)]
Received: by IL75EXM02.cig.mot.com with Internet Mail Service (5.5.2651.58)
	id <G3NSQ1TP>; Wed, 7 Mar 2001 17:56:00 -0600
Message-ID: <0DF9920C9AD8D211AB0C0008C7CF1C9A062EDEA1@il27exm02.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        seamoby@diameter.org
Subject: RE: [seamoby] MM vs CT
Date: Wed, 7 Mar 2001 17:55:58 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

John,

That is a very good point. I raised the issue of capability during our
conference calls, I think Phil N. did as well (sorry if I am wrong Phil). It
did make it to the A.4 appendix of the ct draft. 
Actually, looking at mm draft, I saw there are some other areas that I felt
could be border line issues, maybe not always to the point that we want to
tip the bucket to move the issue to one team versus the other, but sometimes
issues that need attention both for MM and CT problems. A degree of
awareness about how the other team is tackling a "common" issue would be
useful.

In this email, I don't want to advocate for including capability into one
design team or the other (I may in a later email :) ). However, at this
point, I do think, that it would be very beneficial, if the design teams
post at least their meeting minutes on the WG list, or to each other's list
or both (whatever), so we don't get too many surprises/ overlaps/
discrepancies when the drafts are out.

just my 2/100.

Madjid

-----Original Message-----
From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
Sent: Wednesday, March 07, 2001 2:21 PM
To: seamoby@diameter.org
Subject: [seamoby] MM vs CT


Hi all,

I'd like to get everyone's feeling about an issue.

It has been suggested that a handoff mechanism
may like to know the capabilities of a handoff 
target.  This could be useful, for example, when
there is more than one target.  The handoff 
mechanism may want to chose the one which
fufills the QoS requirements, for example.

My question is: what design team should tackle
this issue, MicroMobility or Context Transfer?

thanks,
John


From owner-seamoby@diameter.org  Wed Mar  7 20:34:46 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA29473
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 20:34:45 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2808VP24078
	for seamoby-list; Wed, 7 Mar 2001 16:08:31 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2808TT24073
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 16:08:29 -0800
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id RAA08276 for <seamoby@diameter.org>; Wed, 7 Mar 2001 17:16:40 -0700 (MST)]
Received: [from il75exm02.cig.mot.com (IL75EXM02.cig.mot.com [136.182.110.102]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id RAA10981 for <seamoby@diameter.org>; Wed, 7 Mar 2001 17:16:40 -0700 (MST)]
Received: by IL75EXM02.cig.mot.com with Internet Mail Service (5.5.2651.58)
	id <G3NSQ10Z>; Wed, 7 Mar 2001 18:16:40 -0600
Message-ID: <0DF9920C9AD8D211AB0C0008C7CF1C9A062EDEA2@il27exm02.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Kulwinder Atwal'" <kulwinder.atwal@zucotto.com>,
        "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        seamoby@diameter.org
Subject: RE: [seamoby] MM vs CT   ( was FW: CT problem statement and CNP
Date: Wed, 7 Mar 2001 18:16:38 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Thanks Kulwinder, for sending the emails.
Boy, I have the memory span of a parrot, I did not think of the thread!!

My  feeling is (cheating and reading from the old email :) )
that the knowledge of neighbors capability is necessary to make a wise
handoff decision. The MM team is mentioning this in their plug and play
discussion. Although, I fail to locate the exact section in the draft right
now, I believe the MM team has taken on the task of solving the problem of
[which AR/AP to handoff to] (if not blame, it on my parrot memory).

So it makes sense that the capability discovery should be considered as part
of handoff decision (in MM team). However, I think that signalling of
capability (since it is a "type of context", but in reverse direction) is
part of the data that needs to be transferred during a handover, so IMHO,
the transfer of capabilities should be handled by CT DT.

Did I make any sense?

Madjid

-----Original Message-----
From: Kulwinder Atwal [mailto:kulwinder.atwal@zucotto.com]
Sent: Wednesday, March 07, 2001 4:54 PM
To: 'john.loughney@nokia.com'; seamoby@diameter.org
Subject: RE: [seamoby] MM vs CT ( was FW: CT problem statement and CNP


We discussed this issue on the CT team.  Below you will find the short
thread.

A better place for it might the MM mechanism, or MM protocol.

- Kulwinder.

> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> Sent: Wednesday, March 07, 2001 3:21 PM
> To: seamoby@diameter.org
> Subject: [seamoby] MM vs CT
> 
> 
> Hi all,
> 
> I'd like to get everyone's feeling about an issue.
> 
> It has been suggested that a handoff mechanism
> may like to know the capabilities of a handoff 
> target.  This could be useful, for example, when
> there is more than one target.  The handoff 
> mechanism may want to chose the one which
> fufills the QoS requirements, for example.
> 
> My question is: what design team should tackle
> this issue, MicroMobility or Context Transfer?
> 
> thanks,
> John
> 


-----Original Message-----
From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
Sent: Thursday, January 18, 2001 2:23 PM
To: SEAMOBY_CONTEXT@standards.nortelnetworks.com
Subject: CT problem statement and CNP


Hi,

I changed the subject a bit.

I agree with Kulwinder about the administrative context, and Phil: I am not
talking about negotiations either:) In order to make context transfer/
handover as successful as possible, the source should know about its
neighbors and their capabilities, such as supported QoS, AAA mechanisms
(diameter, radius) and such.

So we might want to talk about possibility of capability transfer (in
reverse direction and maybe prior to context transfer) as a part of problem
statement.

This might be going into solution space, but we are talking a lot about
context transfer failure and protocol mismatch, so I feel, we should at
least take a position about whether we want to have capability transfer as
part of a context transfer protocol or not (I am favorable to it) and if not
mention it in the problem statement.

The reason, I am for it, is that, it would also make any protocol like
Phil's contract net protocol go smoother by making it proactive, rather than
ACK/Nack type protocol.

Regards,
Madjid



-----Original Message-----
From: Jukka Manner [mailto:jmanner@CS.HELSINKI.FI]
Sent: Thursday, January 18, 2001 1:26 AM
To: SEAMOBY_CONTEXT@STANDARDS.NORTELNETWORKS.COM
Subject: Re: About CT & 'Negotiation'


        Hi,

        I know the idea of deciding on the target of CT is part of the
solutions
space, but I would (not sure though) see that some mentioning of this could
be
part of the the problem discussion: what could Seamoby do better than the
present schemes don't do...

        Jukka


On Wed, 17 Jan 2001, Kulwinder Atwal wrote:

>
>
> >     Hi, addiotonal question to that:
> >
> >     If there are two candidate ARs (CARs), of which one
> > could provide a PQ
> > and the other can only provide MAQ. Shouldn't the current AR
> > have a way to know
> > this beforehand, or at least get feedback from the new AR
> > about how well it can
> > support the transfered context?
> >
> >     I know we are moving into the implementation/technology
> > too soon...
> >
> >
> >     Jukka
> > > > I've clipped your comments out, but I wanted to address Context
> > > > Negotiation & Context Transfer thread.
> > > >
> > > > IMO, the 'entity' (the piece of code, for example) that decides
> > > > whether to hand-off or not, should decide if the target
> > > > node can support the handoff.  I don't think that should be
> > > > part of the context transfer.
>
> I referred to this about a month ago, but I was accused of jumping into
the
> solution space way too early.  We need two classes of context:
>
> - Micro-flow Context
> - Administrative Context:
>
> Administrative Context: Context that describes the QoS policy of the APs
> nearby.
>
> I referred to it as a Radio Map for a hetrogenous neighbourhood, and a
> Tri-cell for a homogenous neighbourhood.  A Tri-cell because a minimum of
> three pionts are needed to triangulate the relative position of a mobile
> based on signal strength.  And a Bi-cell becuase a minumum of two points
are
> needed to get a fix on relative velocity.  This of course assumes that
> Multi-path and other types of Interference are managable.
>
> But, again I have digressed into solution space.
>
> - Kulwinder.


From owner-seamoby@diameter.org  Wed Mar  7 21:08:25 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA29943
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 21:08:24 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f280bHi24196
	for seamoby-list; Wed, 7 Mar 2001 16:37:17 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f280bFT24191
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 16:37:15 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GNPD3NQW>; Wed, 7 Mar 2001 19:45:26 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A41@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Nakhjiri Madjid-MNAKHJI1'" <Madjid.Nakhjiri@motorola.com>,
        "'Kulwinder Atwal'" <kulwinder.atwal@herc.zucotto.com>,
        "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        seamoby@diameter.org
Subject: RE: [seamoby] MM vs CT   ( was FW: CT problem statement and CNP
Date: Wed, 7 Mar 2001 19:45:25 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
> Sent: Wednesday, March 07, 2001 7:17 PM
> To: 'Kulwinder Atwal'; 'john.loughney@nokia.com'; seamoby@diameter.org
> Subject: RE: [seamoby] MM vs CT ( was FW: CT problem statement and CNP
> 
> 
> Thanks Kulwinder, for sending the emails.
> Boy, I have the memory span of a parrot, I did not think of 
> the thread!!
> 
> My  feeling is (cheating and reading from the old email :) )
> that the knowledge of neighbors capability is necessary to make a wise
> handoff decision. The MM team is mentioning this in their 
> plug and play
> discussion. Although, I fail to locate the exact section in 
> the draft right
> now, I believe the MM team has taken on the task of solving 
> the problem of
> [which AR/AP to handoff to] (if not blame, it on my parrot memory).
> 
> So it makes sense that the capability discovery should be 
> considered as part
> of handoff decision (in MM team). However, I think that signalling of
> capability (since it is a "type of context", but in reverse 
> direction) is
> part of the data that needs to be transferred during a 
> handover, so IMHO,
> the transfer of capabilities should be handled by CT DT.
> 

Some parts may not need to be transferred during handover, but can be
transferred during Neighbour Capability Discovery.  For example, what are
the max. physical limits of neighbour AR/AP?  Here think MNs / Mobile
Routers/ Auto Configurable APs/ARs.  

If a device has a request that exceeds the physical limits of a neighbour
there is no point in even starting the handoff signalling.  The current
AP/AR can inform the mobile that the handoff is denied due to an unsupported
feature (ie. 100 Mbps channel) on the neighbour.

But, also there are the max. logical limits (ie. too many current
connections) on the next AP/AR that can be apart of the Handoff Negotiation.


- Kulwinder.


From owner-seamoby@diameter.org  Wed Mar  7 22:26:52 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA01659
	for <seamoby-archive@odin.ietf.org>; Wed, 7 Mar 2001 22:26:51 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f280wBf24245
	for seamoby-list; Wed, 7 Mar 2001 16:58:11 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f280usT24240
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 16:56:54 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GNPD3NRH>; Wed, 7 Mar 2001 20:05:05 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A42@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Phil_Neumiller@3com.com'" <Phil_Neumiller@3Com.com>,
        tpagtzis@iprg.nokia.com
Cc: James Kempf <kempf@heliopolis.Eng.Sun.COM>, charliep@iprg.nokia.com,
        kulwinder.atwal@herc.zucotto.com, seamoby@diameter.org
Subject: RE: [seamoby] How to Convince the BARB to work with IETF?
Date: Wed, 7 Mar 2001 20:05:05 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Phil_Neumiller@3com.com [mailto:Phil_Neumiller@3com.com]
> Sent: Wednesday, March 07, 2001 12:16 PM
> To: tpagtzis@iprg.nokia.com
> Cc: James Kempf; charliep@iprg.nokia.com;
> kulwinder.atwal@herc.zucotto.com; seamoby@diameter.org
> Subject: Re: [seamoby] How to Convince the BARB to work with IETF?
> 
> 
> 
> 
> 
> Hi Theo,
> 
> I am quite happy to see that I am not the only person that 
> occasionally gets
> "passionate" about this stuff.  BTW, it doesn't pay to snipe 
> at people getting
> fiesty at each other.  Sometimes the creative juices really 
> flow then!    Let
> them rant and rave, it can open dark caverns of their minds 
> that we can all
> collectively explore.  :-)
> 
> Anyway,  with respect to all these different BOFs potentially 
> coming down
> the pipe in the IETF , AAAAaaaarrrrggggghhh!!!!
> 
> THAT IS EXACTLY WHAT THE CRAPS BOF WAS FOR!!!!!!
> 
> GIMME A C = COMMON
> GIMME A R = RADIO
> GIMME A A = ACCESS
> GIMME A P = PROTOCOL
> GIMME S S = SET
> 
> I thought we could avoid this mess by realizing the 
> commonolalities that
> many radio  L2's have (yes I know what PILC is doing & that's 
> different) in
> signalling, access, and handoff control and create an IP based
> L2 to L3 hinting and Network Access Point (NAP) peer-to-peer and
> NAP to MN protocol.  Alas, it got plucked out of the SeaMoby charter
> faster than you can say Bob's your uncle.  So the Bluetooth BOF
> is the another in the series of L2X over IP BOFs that will continue
> to bombard the IETF and waste all of our precious time and mimize
> commonalities I guess.
> 

So, what is a Common Radio?

- Kulwinder.


From owner-seamoby@diameter.org  Thu Mar  8 02:41:37 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA19811
	for <seamoby-archive@odin.ietf.org>; Thu, 8 Mar 2001 02:41:36 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f285Sbv24866
	for seamoby-list; Wed, 7 Mar 2001 21:28:37 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f285RJT24861
	for <seamoby@diameter.org>; Wed, 7 Mar 2001 21:27:19 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GNPD3NVB>; Thu, 8 Mar 2001 00:35:31 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A44@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Nitin H Vaidya'" <vaidya@cs.tamu.edu>, KAtwal@herc.zucotto.com
Cc: seamoby@diameter.org
Subject: RE: [seamoby] MANET Critique  ( was  Yet Another BOF?
Date: Thu, 8 Mar 2001 00:35:31 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Nitin H Vaidya [mailto:vaidya@cs.tamu.edu]
> Sent: Wednesday, March 07, 2001 7:28 AM
> To: KAtwal@herc.zucotto.com
> Cc: seamoby@diameter.org
> Subject: RE: [seamoby] MANET Critique ( was Yet Another BOF?
> 
> I am afraid you may have misinterpreted TORA (which is, incidentally,
> derived from a very nice paper by Gafni and Bertsekas on
> "link reversal" algorithms).
> Or, perhaps what you mean by ad hoc is different from what TORA
> assumes.
> 
> Your statement may be accurate if all you have is one Master, and its
> slaves talking to each other. But if the network of interest contains
> multiple piconets (hence multiple masters), one would need a protocol
> to route packets between the piconets -- "downstream" is just
> TORAs way of saying "this way to destination D", nothing
> more than that. So, it makes sense to assign downstream
> directions in case of BlueTooth as well. Heights in TORA are just
> a means to decide which way a link points, not an end unto
> themselves.

Consider this:

1. All the Masters are arranged in a tree structure such that each Master
itself is a Slave in the piconet of its Master.  

2. The root of the tree contains a 'Super-Master'.

3. The 'Super-Master' may be an Isolated Mobile Node (no link to an Access
Point).

4. Only the 'Super-Master' may be an a Access Point.

5. Only the 'Super-Master' can attach the entire tree to an Access Point. 

6. Any Mobile Node may leave to join another Access Point, or become an
Isolated Mobile Node, taking any and all of its Slave Nodes that are
attached to it. (its subnet)

7. An Isolated Mobile Node when linking to an Access Point will surrender
its 'Super-Master' Role.

Do we still need TORA?

- Kulwinder.

> Cheerio.
> 
> - nitin
> 


From owner-seamoby@diameter.org  Thu Mar  8 08:26:03 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA25408
	for <seamoby-archive@odin.ietf.org>; Thu, 8 Mar 2001 08:26:02 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f28BnQm25845
	for seamoby-list; Thu, 8 Mar 2001 03:49:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from cs.tamu.edu (IDENT:0@clavin.cs.tamu.edu [128.194.130.106])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f28BnOT25840
	for <seamoby@diameter.org>; Thu, 8 Mar 2001 03:49:24 -0800
Received: from photon.cs.tamu.edu (IDENT:2654@photon [128.194.134.1])
	by cs.tamu.edu (8.11.0/8.11.0) with ESMTP id f28BvbI12131;
	Thu, 8 Mar 2001 05:57:37 -0600 (CST)
Received: (from vaidya@localhost)
	by photon.cs.tamu.edu (8.11.0/8.11.0) id f28Bvr228702;
	Thu, 8 Mar 2001 05:57:53 -0600 (CST)
Date: Thu, 8 Mar 2001 05:57:53 -0600 (CST)
From: Nitin H Vaidya <vaidya@cs.tamu.edu>
Message-Id: <200103081157.f28Bvr228702@photon.cs.tamu.edu>
To: KAtwal@herc.zucotto.com
Subject: RE: [seamoby] MANET Critique  ( was  Yet Another BOF?
Cc: seamoby@diameter.org
Sender: owner-seamoby@diameter.org
Precedence: bulk

hi Kulwinder

My reply below. As I read what I wrote below, I see that I
am starting to repeat myself. So I plan to drop off this
thread here.

  >> From kulwinder.atwal@zucotto.com Wed Mar  7 23:35:32 2001
  >> 
  >> Consider this:
  >> 
  >> 1. All the Masters are arranged in a tree structure such that each Master
  >> itself is a Slave in the piconet of its Master.  
  >> 
  >> 2. The root of the tree contains a 'Super-Master'.
  >> 
  >> 3. The 'Super-Master' may be an Isolated Mobile Node (no link to an Access
  >> Point).
  >> 
  >> 4. Only the 'Super-Master' may be an a Access Point.
  >> 
  >> 5. Only the 'Super-Master' can attach the entire tree to an Access Point. 
  >> 
  >> 6. Any Mobile Node may leave to join another Access Point, or become an
  >> Isolated Mobile Node, taking any and all of its Slave Nodes that are
  >> attached to it. (its subnet)
  >> 
  >> 7. An Isolated Mobile Node when linking to an Access Point will surrender
  >> its 'Super-Master' Role.
  >> 
  >> Do we still need TORA?


You would never *need* TORA as such.
TORA is just *a* routing protocol. If you think you *need*
*a* routing protocol, then TORA, AODV, DSR, Link State,
Distance Vector, manual configuration, are all plausible
options. The correct question to ask would be is TORA
the best choice in the above situation.

Sounds like the tree structure you describe above is
not static, which will call for some sort of routing protocol.
Which protocol is best? Hard to say. But with low mobility,
the choice is not terribly critical, pick something simple
but reasonable (say, one of Link State/AODV/DSR depending
on bandwidth/latency constraints).

Cheerio.

- nitin


  >> 
  >> - Kulwinder.
  >> 



From owner-seamoby@diameter.org  Thu Mar  8 11:32:03 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA02531
	for <seamoby-archive@odin.ietf.org>; Thu, 8 Mar 2001 11:32:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f28EMoG26444
	for seamoby-list; Thu, 8 Mar 2001 06:22:50 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f28EMlT26439
	for <seamoby@diameter.org>; Thu, 8 Mar 2001 06:22:48 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Thu, 8 Mar 2001 09:20:12 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GLQT4P4N>; Thu, 8 Mar 2001 09:17:34 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D78@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Kulwinder Atwal'" <kulwinder.atwal@zucotto.com>, seamoby@diameter.org
Subject: RE: [seamoby] MM vs CT ( was FW: CT problem statement and CNP
Date: Thu, 8 Mar 2001 09:17:28 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A7DA.81A66A10"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A7DA.81A66A10
Content-Type: text/plain;
	charset="iso-8859-1"

Why don't we wait and see what comes out of the CT and MM requirements
and solution discussions before deciding. It would seem that we don't have
a good shared handle on the issues, and we certainly do not know yet what
capabilities
CT or MM might have to support this function.

gary

> -----Original Message-----
> From: Kulwinder Atwal [mailto:kulwinder.atwal@zucotto.com]
> Sent: Wednesday, March 07, 2001 5:54 PM
> To: 'john.loughney@nokia.com'; seamoby@diameter.org
> Subject: RE: [seamoby] MM vs CT ( was FW: CT problem statement and CNP
> 
> 
> We discussed this issue on the CT team.  Below you will find the short
> thread.
> 
> A better place for it might the MM mechanism, or MM protocol.
> 
> - Kulwinder.
> 
> > -----Original Message-----
> > From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> > Sent: Wednesday, March 07, 2001 3:21 PM
> > To: seamoby@diameter.org
> > Subject: [seamoby] MM vs CT
> > 
> > 
> > Hi all,
> > 
> > I'd like to get everyone's feeling about an issue.
> > 
> > It has been suggested that a handoff mechanism
> > may like to know the capabilities of a handoff 
> > target.  This could be useful, for example, when
> > there is more than one target.  The handoff 
> > mechanism may want to chose the one which
> > fufills the QoS requirements, for example.
> > 
> > My question is: what design team should tackle
> > this issue, MicroMobility or Context Transfer?
> > 
> > thanks,
> > John
> > 
> 
> 
> -----Original Message-----
> From: Nakhjiri Madjid-MNAKHJI1 [mailto:Madjid.Nakhjiri@motorola.com]
> Sent: Thursday, January 18, 2001 2:23 PM
> To: SEAMOBY_CONTEXT@standards.nortelnetworks.com
> Subject: CT problem statement and CNP
> 
> 
> Hi,
> 
> I changed the subject a bit.
> 
> I agree with Kulwinder about the administrative context, and 
> Phil: I am not
> talking about negotiations either:) In order to make context transfer/
> handover as successful as possible, the source should know about its
> neighbors and their capabilities, such as supported QoS, AAA 
> mechanisms
> (diameter, radius) and such.
> 
> So we might want to talk about possibility of capability transfer (in
> reverse direction and maybe prior to context transfer) as a 
> part of problem
> statement.
> 
> This might be going into solution space, but we are talking a 
> lot about
> context transfer failure and protocol mismatch, so I feel, we 
> should at
> least take a position about whether we want to have 
> capability transfer as
> part of a context transfer protocol or not (I am favorable to 
> it) and if not
> mention it in the problem statement.
> 
> The reason, I am for it, is that, it would also make any protocol like
> Phil's contract net protocol go smoother by making it 
> proactive, rather than
> ACK/Nack type protocol.
> 
> Regards,
> Madjid
> 
> 
> 
> -----Original Message-----
> From: Jukka Manner [mailto:jmanner@CS.HELSINKI.FI]
> Sent: Thursday, January 18, 2001 1:26 AM
> To: SEAMOBY_CONTEXT@STANDARDS.NORTELNETWORKS.COM
> Subject: Re: About CT & 'Negotiation'
> 
> 
>         Hi,
> 
>         I know the idea of deciding on the target of CT is part of the
> solutions
> space, but I would (not sure though) see that some mentioning 
> of this could
> be
> part of the the problem discussion: what could Seamoby do 
> better than the
> present schemes don't do...
> 
>         Jukka
> 
> 
> On Wed, 17 Jan 2001, Kulwinder Atwal wrote:
> 
> >
> >
> > >     Hi, addiotonal question to that:
> > >
> > >     If there are two candidate ARs (CARs), of which one
> > > could provide a PQ
> > > and the other can only provide MAQ. Shouldn't the current AR
> > > have a way to know
> > > this beforehand, or at least get feedback from the new AR
> > > about how well it can
> > > support the transfered context?
> > >
> > >     I know we are moving into the implementation/technology
> > > too soon...
> > >
> > >
> > >     Jukka
> > > > > I've clipped your comments out, but I wanted to 
> address Context
> > > > > Negotiation & Context Transfer thread.
> > > > >
> > > > > IMO, the 'entity' (the piece of code, for example) 
> that decides
> > > > > whether to hand-off or not, should decide if the target
> > > > > node can support the handoff.  I don't think that should be
> > > > > part of the context transfer.
> >
> > I referred to this about a month ago, but I was accused of 
> jumping into
> the
> > solution space way too early.  We need two classes of context:
> >
> > - Micro-flow Context
> > - Administrative Context:
> >
> > Administrative Context: Context that describes the QoS 
> policy of the APs
> > nearby.
> >
> > I referred to it as a Radio Map for a hetrogenous 
> neighbourhood, and a
> > Tri-cell for a homogenous neighbourhood.  A Tri-cell 
> because a minimum of
> > three pionts are needed to triangulate the relative 
> position of a mobile
> > based on signal strength.  And a Bi-cell becuase a minumum 
> of two points
> are
> > needed to get a fix on relative velocity.  This of course 
> assumes that
> > Multi-path and other types of Interference are managable.
> >
> > But, again I have digressed into solution space.
> >
> > - Kulwinder.
> 

------_=_NextPart_001_01C0A7DA.81A66A10
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: [seamoby] MM vs CT ( was FW: CT problem statement and =
CNP</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Why don't we wait and see what comes out of the CT =
and MM requirements</FONT>
<BR><FONT SIZE=3D2>and solution discussions before deciding. It would =
seem that we don't have</FONT>
<BR><FONT SIZE=3D2>a good shared handle on the issues, and we certainly =
do not know yet what capabilities</FONT>
<BR><FONT SIZE=3D2>CT or MM might have to support this function.</FONT>
</P>

<P><FONT SIZE=3D2>gary</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Kulwinder Atwal [<A =
HREF=3D"mailto:kulwinder.atwal@zucotto.com">mailto:kulwinder.atwal@zucot=
to.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Wednesday, March 07, 2001 5:54 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'john.loughney@nokia.com'; =
seamoby@diameter.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [seamoby] MM vs CT ( was FW: CT =
problem statement and CNP</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; We discussed this issue on the CT team.&nbsp; =
Below you will find the short</FONT>
<BR><FONT SIZE=3D2>&gt; thread.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; A better place for it might the MM mechanism, =
or MM protocol.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; - Kulwinder.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: john.loughney@nokia.com [<A =
HREF=3D"mailto:john.loughney@nokia.com">mailto:john.loughney@nokia.com</=
A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Wednesday, March 07, 2001 3:21 =
PM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: seamoby@diameter.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: [seamoby] MM vs CT</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Hi all,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I'd like to get everyone's feeling about =
an issue.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; It has been suggested that a handoff =
mechanism</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; may like to know the capabilities of a =
handoff </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; target.&nbsp; This could be useful, for =
example, when</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; there is more than one target.&nbsp; The =
handoff </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; mechanism may want to chose the one =
which</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; fufills the QoS requirements, for =
example.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; My question is: what design team should =
tackle</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; this issue, MicroMobility or Context =
Transfer?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; John</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Nakhjiri Madjid-MNAKHJI1 [<A =
HREF=3D"mailto:Madjid.Nakhjiri@motorola.com">mailto:Madjid.Nakhjiri@moto=
rola.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, January 18, 2001 2:23 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: =
SEAMOBY_CONTEXT@standards.nortelnetworks.com</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: CT problem statement and CNP</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I changed the subject a bit.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I agree with Kulwinder about the administrative =
context, and </FONT>
<BR><FONT SIZE=3D2>&gt; Phil: I am not</FONT>
<BR><FONT SIZE=3D2>&gt; talking about negotiations either:) In order to =
make context transfer/</FONT>
<BR><FONT SIZE=3D2>&gt; handover as successful as possible, the source =
should know about its</FONT>
<BR><FONT SIZE=3D2>&gt; neighbors and their capabilities, such as =
supported QoS, AAA </FONT>
<BR><FONT SIZE=3D2>&gt; mechanisms</FONT>
<BR><FONT SIZE=3D2>&gt; (diameter, radius) and such.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; So we might want to talk about possibility of =
capability transfer (in</FONT>
<BR><FONT SIZE=3D2>&gt; reverse direction and maybe prior to context =
transfer) as a </FONT>
<BR><FONT SIZE=3D2>&gt; part of problem</FONT>
<BR><FONT SIZE=3D2>&gt; statement.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; This might be going into solution space, but we =
are talking a </FONT>
<BR><FONT SIZE=3D2>&gt; lot about</FONT>
<BR><FONT SIZE=3D2>&gt; context transfer failure and protocol mismatch, =
so I feel, we </FONT>
<BR><FONT SIZE=3D2>&gt; should at</FONT>
<BR><FONT SIZE=3D2>&gt; least take a position about whether we want to =
have </FONT>
<BR><FONT SIZE=3D2>&gt; capability transfer as</FONT>
<BR><FONT SIZE=3D2>&gt; part of a context transfer protocol or not (I =
am favorable to </FONT>
<BR><FONT SIZE=3D2>&gt; it) and if not</FONT>
<BR><FONT SIZE=3D2>&gt; mention it in the problem statement.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The reason, I am for it, is that, it would also =
make any protocol like</FONT>
<BR><FONT SIZE=3D2>&gt; Phil's contract net protocol go smoother by =
making it </FONT>
<BR><FONT SIZE=3D2>&gt; proactive, rather than</FONT>
<BR><FONT SIZE=3D2>&gt; ACK/Nack type protocol.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Regards,</FONT>
<BR><FONT SIZE=3D2>&gt; Madjid</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Jukka Manner [<A =
HREF=3D"mailto:jmanner@CS.HELSINKI.FI">mailto:jmanner@CS.HELSINKI.FI</A>=
]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, January 18, 2001 1:26 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: =
SEAMOBY_CONTEXT@STANDARDS.NORTELNETWORKS.COM</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: About CT &amp; =
'Negotiation'</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Hi,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
I know the idea of deciding on the target of CT is part of the</FONT>
<BR><FONT SIZE=3D2>&gt; solutions</FONT>
<BR><FONT SIZE=3D2>&gt; space, but I would (not sure though) see that =
some mentioning </FONT>
<BR><FONT SIZE=3D2>&gt; of this could</FONT>
<BR><FONT SIZE=3D2>&gt; be</FONT>
<BR><FONT SIZE=3D2>&gt; part of the the problem discussion: what could =
Seamoby do </FONT>
<BR><FONT SIZE=3D2>&gt; better than the</FONT>
<BR><FONT SIZE=3D2>&gt; present schemes don't do...</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Jukka</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; On Wed, 17 Jan 2001, Kulwinder Atwal =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Hi, =
addiotonal question to that:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; If there are =
two candidate ARs (CARs), of which one</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; could provide a PQ</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; and the other can only provide MAQ. =
Shouldn't the current AR</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; have a way to know</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; this beforehand, or at least get =
feedback from the new AR</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; about how well it can</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; support the transfered =
context?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; I know we are =
moving into the implementation/technology</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; too soon...</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Jukka</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; I've clipped your comments =
out, but I wanted to </FONT>
<BR><FONT SIZE=3D2>&gt; address Context</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Negotiation &amp; Context =
Transfer thread.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; IMO, the 'entity' (the =
piece of code, for example) </FONT>
<BR><FONT SIZE=3D2>&gt; that decides</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; whether to hand-off or not, =
should decide if the target</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; node can support the =
handoff.&nbsp; I don't think that should be</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; part of the context =
transfer.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I referred to this about a month ago, but =
I was accused of </FONT>
<BR><FONT SIZE=3D2>&gt; jumping into</FONT>
<BR><FONT SIZE=3D2>&gt; the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; solution space way too early.&nbsp; We =
need two classes of context:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; - Micro-flow Context</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; - Administrative Context:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Administrative Context: Context that =
describes the QoS </FONT>
<BR><FONT SIZE=3D2>&gt; policy of the APs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; nearby.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I referred to it as a Radio Map for a =
hetrogenous </FONT>
<BR><FONT SIZE=3D2>&gt; neighbourhood, and a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Tri-cell for a homogenous =
neighbourhood.&nbsp; A Tri-cell </FONT>
<BR><FONT SIZE=3D2>&gt; because a minimum of</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; three pionts are needed to triangulate the =
relative </FONT>
<BR><FONT SIZE=3D2>&gt; position of a mobile</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; based on signal strength.&nbsp; And a =
Bi-cell becuase a minumum </FONT>
<BR><FONT SIZE=3D2>&gt; of two points</FONT>
<BR><FONT SIZE=3D2>&gt; are</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; needed to get a fix on relative =
velocity.&nbsp; This of course </FONT>
<BR><FONT SIZE=3D2>&gt; assumes that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Multi-path and other types of Interference =
are managable.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; But, again I have digressed into solution =
space.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; - Kulwinder.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0A7DA.81A66A10--


From owner-seamoby@diameter.org  Thu Mar  8 13:17:20 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA07092
	for <seamoby-archive@odin.ietf.org>; Thu, 8 Mar 2001 13:17:19 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f28Ft0626707
	for seamoby-list; Thu, 8 Mar 2001 07:55:00 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f28FsvT26698
	for <seamoby@diameter.org>; Thu, 8 Mar 2001 07:54:57 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Thu, 8 Mar 2001 10:18:40 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GLQT4SJW>; Thu, 8 Mar 2001 10:18:31 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E805B2263B@zwdld001.ca.nortel.com>
From: "Hamid Syed" <hmsyed@nortelnetworks.com>
To: "Gary Kenward" <gkenward@nortelnetworks.com>,
        seamoby_context@marvin.corpeast.baynetworks.com
Cc: "'seamoby'" <seamoby@diameter.org>
Subject: [seamoby] RE: Second notice: Seamoby Context Transfer Design Team Requireme nts 
         kick-off conference call, Monday, March 12, 2001, 11 am EST
Date: Thu, 8 Mar 2001 10:18:07 -0500
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0A7E2.FAB5A670"
X-Orig: <hmsyed@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A7E2.FAB5A670
Content-Type: text/plain

Count me in Gary.:-)

-Hamid

> -----Original Message-----
> From:	Kenward, Gary [WDLN2:AN10:EXCH] 
> Sent:	Thursday, March 08, 2001 9:33 AM
> To:	seamoby_context@marvin.corpeast.baynetworks.com
> Cc:	'seamoby'; 'Pat Calhoun'
> Subject:	Second notice: Seamoby Context Transfer Design Team
> Requirements  kick-off conference call, Monday, March 12, 2001, 11 am EST
> Importance:	High
> Sensitivity:	Confidential
> 
> This is a second notification of the intent to hold a Context Transfer
> Design meeting
> this coming Monday. So far, all responses have been positive, and we have
> enough people
> to proceed. Please send your replies to the seamoby context list as soon
> as
> possible.
> 
> =========================================================
> 
> This email is formal request for participation in the next
> Seamless Mobility Context Transfer Design Team conference call.
> 
> In the past we have held these calls on Monday mornings
> at 11 am EST. I have tentatively scheduled the next meeting
> for Monday, March 12, 2001 at 11 am EST. However, this time
> can be changed *if* there is a consensus. Keep in mind that there
> are participants on three continents, at least, and it is difficult
> to accommodate everyone.
> 
> As I understand it, the design team's next task is the 
> development of a *requirements* draft. We must complete this 
> draft before the ADs will consider giving us the go-ahead to work on 
> solutions. 
> 
> The *tentative* agenda is:
> 	 *	attendance, hellos, etc.
> 	 *	selection of an editor for the requirements draft
> 	 *	rules for authorship
> 	 *	discussion of format / table of contents
> 	 *	action items
> 	 *	meeting schedule
> 
> We have this week to modify this agenda.
> 
> The conference call information is:
> 
> Date: 			Monday, March 12,  2001
> Time:			11 AM EST.
> US Phone Number: 	972-684-6338
> PassCode:		793142
> 
> I request that all replies to this email be copied to the
> seamoby and seamoby_context lists to ensure that 
> there is an open discussion and an archive.
> 
> Thank you,
> Gary Kenward
> 
> PS  I assume that a consensus means 50% + 1 of the respondents.

------_=_NextPart_001_01C0A7E2.FAB5A670
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: Second notice: Seamoby Context Transfer Design Team =
Requirements  kick-off conference call, Monday, March 12, 2001, 11 am =
EST</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Count me in =
Gary.:-)</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">-Hamid</FONT>
</P>
<UL>
<P><FONT SIZE=3D1 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">From:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Kenward, Gary [WDLN2:AN10:EXCH] </FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Thursday, March 08, 2001 9:33 AM</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">seamoby_context@marvin.corpeast.baynetworks.com</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">'seamoby'; 'Pat Calhoun'</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Arial">Second notice: Seamoby Context =
Transfer Design Team Requirements&nbsp; kick-off conference call, =
Monday, March 12, 2001, 11 am EST</FONT></P>

<P><B><FONT SIZE=3D1 =
FACE=3D"Arial">Importance:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">High</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">Sensitivity:</FONT></B>&nbsp;&nbsp;&nbsp; <FONT SIZE=3D1 =
FACE=3D"Arial">Confidential</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This is a second notification of the =
intent to hold a Context Transfer</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Design meeting</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">this coming Monday. So far, all =
responses have been positive, and we have</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">enough people</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">to proceed. Please send your replies =
to the seamoby context list as soon as</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">possible.</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Arial">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This email is formal request for =
participation in the next</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Seamless Mobility Context Transfer =
Design Team conference call.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">In the past we have held these calls =
on Monday mornings</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">at 11 am EST. I have tentatively =
scheduled the next meeting</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">for Monday, March 12, 2001 at 11 am =
EST. However, this time</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">can be changed *if* there is a =
consensus. Keep in mind that there</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">are participants on three continents, =
at least, and it is difficult</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">to accommodate everyone.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">As I understand it, the design team's =
next task is the </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">development of a *requirements* =
draft. We must complete this </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">draft before the ADs will consider =
giving us the go-ahead to work on </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">solutions. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The *tentative* agenda is:</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<FONT SIZE=3D2 =
FACE=3D"Arial"> *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; attendance, hellos, =
etc.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<FONT SIZE=3D2 =
FACE=3D"Arial"> *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; selection of an editor =
for the requirements draft</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<FONT SIZE=3D2 =
FACE=3D"Arial"> *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rules for =
authorship</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<FONT SIZE=3D2 =
FACE=3D"Arial"> *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; discussion of format / =
table of contents</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<FONT SIZE=3D2 =
FACE=3D"Arial"> *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; action items</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<FONT SIZE=3D2 =
FACE=3D"Arial"> *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; meeting schedule</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">We have this week to modify this =
agenda.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The conference call information =
is:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Date: &nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Monday, March 12,&nbsp; =
2001</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Time:&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 11 AM EST.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">US Phone Number: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 972-684-6338</FONT>
<BR><FONT SIZE=3D2 =
FACE=3D"Arial">PassCode:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 793142</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I request that all replies to this =
email be copied to the</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">seamoby and seamoby_context lists to =
ensure that </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">there is an open discussion and an =
archive.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thank you,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Gary Kenward</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">PS&nbsp; I assume that a consensus =
means 50% + 1 of the respondents.</FONT>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C0A7E2.FAB5A670--


From owner-seamoby@diameter.org  Thu Mar  8 13:26:34 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA07345
	for <seamoby-archive@odin.ietf.org>; Thu, 8 Mar 2001 13:26:33 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f28Ft9l26709
	for seamoby-list; Thu, 8 Mar 2001 07:55:09 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f28FsvT26699
	for <seamoby@diameter.org>; Thu, 8 Mar 2001 07:54:57 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Thu, 8 Mar 2001 09:34:31 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GLQT4QKW>; Thu, 8 Mar 2001 09:32:39 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8D7A@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'seamoby_context'" <seamoby_context@marvin.baynetworks.com>
Cc: "'seamoby'" <seamoby@diameter.org>,
        "'Pat Calhoun'" <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] Second notice: Seamoby Context Transfer Design Team Requirements 
         kick-off conference call, Monday, March 12, 2001, 11 am EST
Date: Thu, 8 Mar 2001 09:32:36 -0500
Importance: high
X-Priority: 1
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This is a second notification of the intent to hold a Context Transfer
Design meeting
this coming Monday. So far, all responses have been positive, and we have
enough people
to proceed. Please send your replies to the seamoby context list as soon as
possible.

=========================================================

This email is formal request for participation in the next
Seamless Mobility Context Transfer Design Team conference call.

In the past we have held these calls on Monday mornings
at 11 am EST. I have tentatively scheduled the next meeting
for Monday, March 12, 2001 at 11 am EST. However, this time
can be changed *if* there is a consensus. Keep in mind that there
are participants on three continents, at least, and it is difficult
to accommodate everyone.

As I understand it, the design team's next task is the 
development of a *requirements* draft. We must complete this 
draft before the ADs will consider giving us the go-ahead to work on 
solutions. 

The *tentative* agenda is:
	 *	attendance, hellos, etc.
	 *	selection of an editor for the requirements draft
	 *	rules for authorship
	 *	discussion of format / table of contents
	 *	action items
	 *	meeting schedule

We have this week to modify this agenda.

The conference call information is:

Date: 			Monday, March 12,  2001
Time:			11 AM EST.
US Phone Number: 	972-684-6338
PassCode:		793142

I request that all replies to this email be copied to the
seamoby and seamoby_context lists to ensure that 
there is an open discussion and an archive.

Thank you,
Gary Kenward

PS  I assume that a consensus means 50% + 1 of the respondents.


From owner-seamoby@diameter.org  Thu Mar  8 15:05:09 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA10972
	for <seamoby-archive@odin.ietf.org>; Thu, 8 Mar 2001 15:05:07 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f28GMtQ26782
	for seamoby-list; Thu, 8 Mar 2001 08:22:55 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f28GMrT26777
	for <seamoby@diameter.org>; Thu, 8 Mar 2001 08:22:53 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA04917;
	Thu, 8 Mar 2001 08:31:00 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA13240;
	Thu, 8 Mar 2001 08:30:59 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id IAA08152;
	Thu, 8 Mar 2001 08:30:58 -0800 (PST)
Message-Id: <200103081630.IAA08152@heliopolis.Eng.Sun.COM>
Date: Thu, 8 Mar 2001 08:30:58 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] MM vs CT
To: john.loughney@nokia.com, seamoby@diameter.org,
        Madjid.Nakhjiri@motorola.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: lk2EuPnFX4PuuA77pltmPg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Madjid/John/PhilN,

Actually, I think micromo covers both context transfer and paging in its
own way. The paging group talked about doing paging for micromo and
decided it was premature, before the outlines of the micromo problem
were clearly stated. So we primarily focussed on mobile IP, but we
did include an item in our recommendations to look at paging for
micromo when a clear problem statement emerged, and, of course, if
a solution to paging were part of the micromo requirements. This 
is actually part of the problem of not having completed a clear problem 
about micromo, it is hard to see exactly what it covers. 

		jak

>X-Authentication-Warning: charizard.diameter.org: majordomo set sender to 
owner-seamoby@diameter.org using -f
>From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
>To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>, seamoby@diameter.org
>Subject: RE: [seamoby] MM vs CT
>Date: Wed, 7 Mar 2001 17:55:58 -0600 
>MIME-Version: 1.0
>
>John,
>
>That is a very good point. I raised the issue of capability during our
>conference calls, I think Phil N. did as well (sorry if I am wrong Phil). It
>did make it to the A.4 appendix of the ct draft. 
>Actually, looking at mm draft, I saw there are some other areas that I felt
>could be border line issues, maybe not always to the point that we want to
>tip the bucket to move the issue to one team versus the other, but sometimes
>issues that need attention both for MM and CT problems. A degree of
>awareness about how the other team is tackling a "common" issue would be
>useful.
>
>In this email, I don't want to advocate for including capability into one
>design team or the other (I may in a later email :) ). However, at this
>point, I do think, that it would be very beneficial, if the design teams
>post at least their meeting minutes on the WG list, or to each other's list
>or both (whatever), so we don't get too many surprises/ overlaps/
>discrepancies when the drafts are out.
>
>just my 2/100.
>
>Madjid
>
>-----Original Message-----
>From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
>Sent: Wednesday, March 07, 2001 2:21 PM
>To: seamoby@diameter.org
>Subject: [seamoby] MM vs CT
>
>
>Hi all,
>
>I'd like to get everyone's feeling about an issue.
>
>It has been suggested that a handoff mechanism
>may like to know the capabilities of a handoff 
>target.  This could be useful, for example, when
>there is more than one target.  The handoff 
>mechanism may want to chose the one which
>fufills the QoS requirements, for example.
>
>My question is: what design team should tackle
>this issue, MicroMobility or Context Transfer?
>
>thanks,
>John



From owner-seamoby@diameter.org  Thu Mar  8 15:24:30 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA11805
	for <seamoby-archive@odin.ietf.org>; Thu, 8 Mar 2001 15:24:30 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f28I3TF27005
	for seamoby-list; Thu, 8 Mar 2001 10:03:29 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f28I2YT27000
	for <seamoby@diameter.org>; Thu, 8 Mar 2001 10:02:35 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id KAA22477;
	Thu, 8 Mar 2001 10:10:37 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ACC19056;
	Thu, 8 Mar 2001 10:10:36 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA00696; Thu, 8 Mar 2001 10:10:36 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15015.51996.360649.817132@thomasm-u1.cisco.com>
Date: Thu, 8 Mar 2001 10:10:36 -0800 (PST)
To: tpagtzis@iprg.nokia.com
Cc: Nitin H Vaidya <vaidya@cs.tamu.edu>, KAtwal@herc.zucotto.com,
        seamoby@diameter.org
Subject: Re: [seamoby] MANET Critique ( was Yet Another BOF?
In-Reply-To: <3AA65317.80EC0B5B@cs.ucl.ac.uk>
References: <200103071227.f27CRwN24268@photon.cs.tamu.edu>
	<3AA65317.80EC0B5B@cs.ucl.ac.uk>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Theo Pagtzis writes:
 > Master-slave organization (or better point to point to multipoint) is also over
 > 802.11 at infrastructure mode
 > This is the case over PCF (no contention) and DCF (with contention). Does that
 > render a constitute a reason for using MANET protocols
 > over 802.11 at that mode?

   I think Nitin described the situation well. I'll 
   point out that routing protocols would be useful
   if you want to keep your IP address across multiple
   different AP/AR's. 802.11 with its IAPP, I believe, is
   an L2 scheme for doing that. TORA and other L3 routing
   protocols could provide a means of doing the
   same thing across different L2's.

   This is completely independent of how a
   particular L2 manages its spectrum while you
   are attached to it.


		Mike


From owner-seamoby@diameter.org  Thu Mar  8 17:39:59 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA15861
	for <seamoby-archive@odin.ietf.org>; Thu, 8 Mar 2001 17:39:58 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f28J8Vg27184
	for seamoby-list; Thu, 8 Mar 2001 11:08:31 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f28J8TT27179
	for <seamoby@diameter.org>; Thu, 8 Mar 2001 11:08:29 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id LAA11937;
	Thu, 8 Mar 2001 11:16:38 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f28JGaY09570;
	Thu, 8 Mar 2001 11:16:36 -0800
X-mProtect:  Thu, 8 Mar 2001 11:16:36 -0800 Nokia Silicon Valley Messaging Protection
Received: from Icharliep-1.iprg.nokia.com (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdn4fuXw; Thu, 08 Mar 2001 11:15:43 PST
Message-ID: <3AA7DA9A.73507AE1@iprg.nokia.com>
Date: Thu, 08 Mar 2001 11:16:42 -0800
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Nitin H Vaidya <vaidya@cs.tamu.edu>
CC: KAtwal@herc.zucotto.com, seamoby@diameter.org
Subject: Re: [seamoby] MANET Critique  ( was  Yet Another BOF?
References: <200103081157.f28Bvr228702@photon.cs.tamu.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello,

Your proposed structure places severe restrictions.  With no loss
of functionality, or increase in complexity, it would be quite possible
to let any ad hoc node be an Internet Access Point.

I also would like to suggest that manet protocols (and AODV in
particular) have been portrayed as necessarily heavyweight because
they assure loop freedom even over multiple hops.  This isn't right,
and AODV in particular was intended to be a lightweight protocol.

I think that a distance-vector approach is quite suitable for
Bluetooth's master-slave architecture.  AODV only has to say
where the next hop is.  Enforcing the master-slave connectivity
is going to happen below IP anyway.

I'm pretty sure this discussion doesn't belong here, though...

Regards,
Charlie P.


>   >> From kulwinder.atwal@zucotto.com Wed Mar  7 23:35:32 2001
>   >>
>   >> Consider this:
>   >>
>   >> 1. All the Masters are arranged in a tree structure such that each Master
>   >> itself is a Slave in the piconet of its Master.
>   >>
>   >> 2. The root of the tree contains a 'Super-Master'.
>   >>
>   >> 3. The 'Super-Master' may be an Isolated Mobile Node (no link to an Access
>   >> Point).
>   >>
>   >> 4. Only the 'Super-Master' may be an a Access Point.
>   >>
>   >> 5. Only the 'Super-Master' can attach the entire tree to an Access Point.
>   >>
>   >> 6. Any Mobile Node may leave to join another Access Point, or become an
>   >> Isolated Mobile Node, taking any and all of its Slave Nodes that are
>   >> attached to it. (its subnet)
>   >>
>   >> 7. An Isolated Mobile Node when linking to an Access Point will surrender
>   >> its 'Super-Master' Role.
>   >>
>   >> Do we still need TORA?
>
> You would never *need* TORA as such.
> TORA is just *a* routing protocol. If you think you *need*
> *a* routing protocol, then TORA, AODV, DSR, Link State,
> Distance Vector, manual configuration, are all plausible
> options. The correct question to ask would be is TORA
> the best choice in the above situation.
>
> Sounds like the tree structure you describe above is
> not static, which will call for some sort of routing protocol.
> Which protocol is best? Hard to say. But with low mobility,
> the choice is not terribly critical, pick something simple
> but reasonable (say, one of Link State/AODV/DSR depending
> on bandwidth/latency constraints).
>
> Cheerio.
>
> - nitin
>
>   >>
>   >> - Kulwinder.
>   >>



From owner-seamoby@diameter.org  Thu Mar  8 17:53:22 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA16125
	for <seamoby-archive@odin.ietf.org>; Thu, 8 Mar 2001 17:53:21 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f28KSq527398
	for seamoby-list; Thu, 8 Mar 2001 12:28:52 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f28KSnT27393
	for <seamoby@diameter.org>; Thu, 8 Mar 2001 12:28:49 -0800
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id NAA01119 for <seamoby@diameter.org>; Thu, 8 Mar 2001 13:37:03 -0700 (MST)]
Received: [from il75exm02.cig.mot.com (IL75EXM02.cig.mot.com [136.182.110.102]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id NAA01756 for <seamoby@diameter.org>; Thu, 8 Mar 2001 13:32:20 -0700 (MST)]
Received: by IL75EXM02.cig.mot.com with Internet Mail Service (5.5.2651.58)
	id <G3NSQ7N6>; Thu, 8 Mar 2001 14:37:02 -0600
Message-ID: <0DF9920C9AD8D211AB0C0008C7CF1C9A062EDEB4@il27exm02.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Gary Kenward'" <gkenward@nortelnetworks.com>,
        "'Kulwinder Atwal'"
	 <kulwinder.atwal@zucotto.com>,
        seamoby@diameter.org, "'James Kempf'"
	 <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] MM vs CT ( was FW: CT problem statement and CNP
Date: Thu, 8 Mar 2001 14:37:01 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0A80F.873FB910"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A80F.873FB910
Content-Type: text/plain;
	charset="iso-8859-1"

Gary/ James,
 
That is a good point, however, as I suggested, the two (or three, if people
want) groups should keep the line of communications open through at least
through meeting minutes (Not that I am adding to the formality here, so far
we had minutes, that is all) and not wait until the end of the requirement
work. 
I think Phil N. had these sort of issues in mind, when he once posted the mm
meeting minutes on the WG list, I personally enjoyed the news break. This
should happen regardless of which team the item goes to.
 
BR,
 
Madjid

-----Original Message-----
From: Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Thursday, March 08, 2001 8:17 AM
To: 'Kulwinder Atwal'; seamoby@diameter.org
Subject: RE: [seamoby] MM vs CT ( was FW: CT problem statement and CNP



Why don't we wait and see what comes out of the CT and MM requirements 
and solution discussions before deciding. It would seem that we don't have 
a good shared handle on the issues, and we certainly do not know yet what
capabilities 
CT or MM might have to support this function. 

gary 

> -----Original Message----- 
> From: Kulwinder Atwal [ mailto:kulwinder.atwal@zucotto.com
<mailto:kulwinder.atwal@zucotto.com> ] 
> Sent: Wednesday, March 07, 2001 5:54 PM 
> To: 'john.loughney@nokia.com'; seamoby@diameter.org 
> Subject: RE: [seamoby] MM vs CT ( was FW: CT problem statement and CNP 
> 
> 
> We discussed this issue on the CT team.  Below you will find the short 
> thread. 
> 
> A better place for it might the MM mechanism, or MM protocol. 
> 
> - Kulwinder. 
> 
> > -----Original Message----- 
> > From: john.loughney@nokia.com [ mailto:john.loughney@nokia.com
<mailto:john.loughney@nokia.com> ] 
> > Sent: Wednesday, March 07, 2001 3:21 PM 
> > To: seamoby@diameter.org 
> > Subject: [seamoby] MM vs CT 
> > 
> > 
> > Hi all, 
> > 
> > I'd like to get everyone's feeling about an issue. 
> > 
> > It has been suggested that a handoff mechanism 
> > may like to know the capabilities of a handoff 
> > target.  This could be useful, for example, when 
> > there is more than one target.  The handoff 
> > mechanism may want to chose the one which 
> > fufills the QoS requirements, for example. 
> > 
> > My question is: what design team should tackle 
> > this issue, MicroMobility or Context Transfer? 
> > 
> > thanks, 
> > John 
> > 
> 
> 
> -----Original Message----- 
> From: Nakhjiri Madjid-MNAKHJI1 [ mailto:Madjid.Nakhjiri@motorola.com
<mailto:Madjid.Nakhjiri@motorola.com> ] 
> Sent: Thursday, January 18, 2001 2:23 PM 
> To: SEAMOBY_CONTEXT@standards.nortelnetworks.com 
> Subject: CT problem statement and CNP 
> 
> 
> Hi, 
> 
> I changed the subject a bit. 
> 
> I agree with Kulwinder about the administrative context, and 
> Phil: I am not 
> talking about negotiations either:) In order to make context transfer/ 
> handover as successful as possible, the source should know about its 
> neighbors and their capabilities, such as supported QoS, AAA 
> mechanisms 
> (diameter, radius) and such. 
> 
> So we might want to talk about possibility of capability transfer (in 
> reverse direction and maybe prior to context transfer) as a 
> part of problem 
> statement. 
> 
> This might be going into solution space, but we are talking a 
> lot about 
> context transfer failure and protocol mismatch, so I feel, we 
> should at 
> least take a position about whether we want to have 
> capability transfer as 
> part of a context transfer protocol or not (I am favorable to 
> it) and if not 
> mention it in the problem statement. 
> 
> The reason, I am for it, is that, it would also make any protocol like 
> Phil's contract net protocol go smoother by making it 
> proactive, rather than 
> ACK/Nack type protocol. 
> 
> Regards, 
> Madjid 
> 
> 
> 
> -----Original Message----- 
> From: Jukka Manner [ mailto:jmanner@CS.HELSINKI.FI
<mailto:jmanner@CS.HELSINKI.FI> ] 
> Sent: Thursday, January 18, 2001 1:26 AM 
> To: SEAMOBY_CONTEXT@STANDARDS.NORTELNETWORKS.COM 
> Subject: Re: About CT & 'Negotiation' 
> 
> 
>         Hi, 
> 
>         I know the idea of deciding on the target of CT is part of the 
> solutions 
> space, but I would (not sure though) see that some mentioning 
> of this could 
> be 
> part of the the problem discussion: what could Seamoby do 
> better than the 
> present schemes don't do... 
> 
>         Jukka 
> 
> 
> On Wed, 17 Jan 2001, Kulwinder Atwal wrote: 
> 
> > 
> > 
> > >     Hi, addiotonal question to that: 
> > > 
> > >     If there are two candidate ARs (CARs), of which one 
> > > could provide a PQ 
> > > and the other can only provide MAQ. Shouldn't the current AR 
> > > have a way to know 
> > > this beforehand, or at least get feedback from the new AR 
> > > about how well it can 
> > > support the transfered context? 
> > > 
> > >     I know we are moving into the implementation/technology 
> > > too soon... 
> > > 
> > > 
> > >     Jukka 
> > > > > I've clipped your comments out, but I wanted to 
> address Context 
> > > > > Negotiation & Context Transfer thread. 
> > > > > 
> > > > > IMO, the 'entity' (the piece of code, for example) 
> that decides 
> > > > > whether to hand-off or not, should decide if the target 
> > > > > node can support the handoff.  I don't think that should be 
> > > > > part of the context transfer. 
> > 
> > I referred to this about a month ago, but I was accused of 
> jumping into 
> the 
> > solution space way too early.  We need two classes of context: 
> > 
> > - Micro-flow Context 
> > - Administrative Context: 
> > 
> > Administrative Context: Context that describes the QoS 
> policy of the APs 
> > nearby. 
> > 
> > I referred to it as a Radio Map for a hetrogenous 
> neighbourhood, and a 
> > Tri-cell for a homogenous neighbourhood.  A Tri-cell 
> because a minimum of 
> > three pionts are needed to triangulate the relative 
> position of a mobile 
> > based on signal strength.  And a Bi-cell becuase a minumum 
> of two points 
> are 
> > needed to get a fix on relative velocity.  This of course 
> assumes that 
> > Multi-path and other types of Interference are managable. 
> > 
> > But, again I have digressed into solution space. 
> > 
> > - Kulwinder. 
> 


------_=_NextPart_001_01C0A80F.873FB910
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [seamoby] MM vs CT ( was FW: CT problem statement and CNP</TITLE>

<META content="MSHTML 5.00.2920.0" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=455512820-08032001>Gary/ 
James,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=455512820-08032001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=455512820-08032001>That 
is a good point, however, as I suggested, the two (or three, if people want) 
groups should keep the line of communications open through at least through 
meeting minutes (Not that I am adding to the formality here,  so far we had 
minutes, that is all) and not wait until the end of the requirement work. 
</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=455512820-08032001>I 
think Phil N. had these sort of issues in mind, when he once posted the mm 
meeting minutes on the WG list, I personally enjoyed the news break. This 
should&nbsp;happen regardless of which team  the item goes 
to.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=455512820-08032001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=455512820-08032001>BR,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=455512820-08032001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=455512820-08032001>Madjid</SPAN></FONT></DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Gary Kenward 
  [mailto:gkenward@nortelnetworks.com]<BR><B>Sent:</B> Thursday, March 08, 2001 
  8:17 AM<BR><B>To:</B> 'Kulwinder Atwal'; 
  seamoby@diameter.org<BR><B>Subject:</B> RE: [seamoby] MM vs CT ( was FW: CT 
  problem statement and CNP<BR><BR></DIV></FONT>
  <P><FONT size=2>Why don't we wait and see what comes out of the CT and MM 
  requirements</FONT> <BR><FONT size=2>and solution discussions before deciding. 
  It would seem that we don't have</FONT> <BR><FONT size=2>a good shared handle 
  on the issues, and we certainly do not know yet what capabilities</FONT> 
  <BR><FONT size=2>CT or MM might have to support this function.</FONT> </P>
  <P><FONT size=2>gary</FONT> </P>
  <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
  From: Kulwinder Atwal [<A 
  href="mailto:kulwinder.atwal@zucotto.com">mailto:kulwinder.atwal@zucotto.com</A>]</FONT> 
  <BR><FONT size=2>&gt; Sent: Wednesday, March 07, 2001 5:54 PM</FONT> <BR><FONT 
  size=2>&gt; To: 'john.loughney@nokia.com'; seamoby@diameter.org</FONT> 
  <BR><FONT size=2>&gt; Subject: RE: [seamoby] MM vs CT ( was FW: CT problem 
  statement and CNP</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; We discussed this issue on the CT team.&nbsp; 
  Below you will find the short</FONT> <BR><FONT size=2>&gt; thread.</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; A better place for it might 
  the MM mechanism, or MM protocol.</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; - Kulwinder.</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; &gt; -----Original Message-----</FONT> <BR><FONT 
  size=2>&gt; &gt; From: john.loughney@nokia.com [<A 
  href="mailto:john.loughney@nokia.com">mailto:john.loughney@nokia.com</A>]</FONT> 
  <BR><FONT size=2>&gt; &gt; Sent: Wednesday, March 07, 2001 3:21 PM</FONT> 
  <BR><FONT size=2>&gt; &gt; To: seamoby@diameter.org</FONT> <BR><FONT 
  size=2>&gt; &gt; Subject: [seamoby] MM vs CT</FONT> <BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Hi 
  all,</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; I'd 
  like to get everyone's feeling about an issue.</FONT> <BR><FONT size=2>&gt; 
  &gt; </FONT><BR><FONT size=2>&gt; &gt; It has been suggested that a handoff 
  mechanism</FONT> <BR><FONT size=2>&gt; &gt; may like to know the capabilities 
  of a handoff </FONT><BR><FONT size=2>&gt; &gt; target.&nbsp; This could be 
  useful, for example, when</FONT> <BR><FONT size=2>&gt; &gt; there is more than 
  one target.&nbsp; The handoff </FONT><BR><FONT size=2>&gt; &gt; mechanism may 
  want to chose the one which</FONT> <BR><FONT size=2>&gt; &gt; fufills the QoS 
  requirements, for example.</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
  size=2>&gt; &gt; My question is: what design team should tackle</FONT> 
  <BR><FONT size=2>&gt; &gt; this issue, MicroMobility or Context 
  Transfer?</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
  thanks,</FONT> <BR><FONT size=2>&gt; &gt; John</FONT> <BR><FONT size=2>&gt; 
  &gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT 
  size=2>&gt; From: Nakhjiri Madjid-MNAKHJI1 [<A 
  href="mailto:Madjid.Nakhjiri@motorola.com">mailto:Madjid.Nakhjiri@motorola.com</A>]</FONT> 
  <BR><FONT size=2>&gt; Sent: Thursday, January 18, 2001 2:23 PM</FONT> 
  <BR><FONT size=2>&gt; To: SEAMOBY_CONTEXT@standards.nortelnetworks.com</FONT> 
  <BR><FONT size=2>&gt; Subject: CT problem statement and CNP</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  Hi,</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; I changed the 
  subject a bit.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; I 
  agree with Kulwinder about the administrative context, and </FONT><BR><FONT 
  size=2>&gt; Phil: I am not</FONT> <BR><FONT size=2>&gt; talking about 
  negotiations either:) In order to make context transfer/</FONT> <BR><FONT 
  size=2>&gt; handover as successful as possible, the source should know about 
  its</FONT> <BR><FONT size=2>&gt; neighbors and their capabilities, such as 
  supported QoS, AAA </FONT><BR><FONT size=2>&gt; mechanisms</FONT> <BR><FONT 
  size=2>&gt; (diameter, radius) and such.</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; So we might want to talk about possibility of 
  capability transfer (in</FONT> <BR><FONT size=2>&gt; reverse direction and 
  maybe prior to context transfer) as a </FONT><BR><FONT size=2>&gt; part of 
  problem</FONT> <BR><FONT size=2>&gt; statement.</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; This might be going into solution space, but we 
  are talking a </FONT><BR><FONT size=2>&gt; lot about</FONT> <BR><FONT 
  size=2>&gt; context transfer failure and protocol mismatch, so I feel, we 
  </FONT><BR><FONT size=2>&gt; should at</FONT> <BR><FONT size=2>&gt; least take 
  a position about whether we want to have </FONT><BR><FONT size=2>&gt; 
  capability transfer as</FONT> <BR><FONT size=2>&gt; part of a context transfer 
  protocol or not (I am favorable to </FONT><BR><FONT size=2>&gt; it) and if 
  not</FONT> <BR><FONT size=2>&gt; mention it in the problem statement.</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; The reason, I am for it, is 
  that, it would also make any protocol like</FONT> <BR><FONT size=2>&gt; Phil's 
  contract net protocol go smoother by making it </FONT><BR><FONT size=2>&gt; 
  proactive, rather than</FONT> <BR><FONT size=2>&gt; ACK/Nack type 
  protocol.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  Regards,</FONT> <BR><FONT size=2>&gt; Madjid</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; From: 
  Jukka Manner [<A 
  href="mailto:jmanner@CS.HELSINKI.FI">mailto:jmanner@CS.HELSINKI.FI</A>]</FONT> 
  <BR><FONT size=2>&gt; Sent: Thursday, January 18, 2001 1:26 AM</FONT> 
  <BR><FONT size=2>&gt; To: SEAMOBY_CONTEXT@STANDARDS.NORTELNETWORKS.COM</FONT> 
  <BR><FONT size=2>&gt; Subject: Re: About CT &amp; 'Negotiation'</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Hi,</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I know the idea of 
  deciding on the target of CT is part of the</FONT> <BR><FONT size=2>&gt; 
  solutions</FONT> <BR><FONT size=2>&gt; space, but I would (not sure though) 
  see that some mentioning </FONT><BR><FONT size=2>&gt; of this could</FONT> 
  <BR><FONT size=2>&gt; be</FONT> <BR><FONT size=2>&gt; part of the the problem 
  discussion: what could Seamoby do </FONT><BR><FONT size=2>&gt; better than 
  the</FONT> <BR><FONT size=2>&gt; present schemes don't do...</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Jukka</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; On Wed, 17 Jan 2001, Kulwinder Atwal wrote:</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt;</FONT> <BR><FONT size=2>&gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Hi, 
  addiotonal question to that:</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> 
  <BR><FONT size=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; If there are two 
  candidate ARs (CARs), of which one</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  could provide a PQ</FONT> <BR><FONT size=2>&gt; &gt; &gt; and the other can 
  only provide MAQ. Shouldn't the current AR</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; have a way to know</FONT> <BR><FONT size=2>&gt; &gt; &gt; this 
  beforehand, or at least get feedback from the new AR</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt; about how well it can</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; support the transfered context?</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; I know we 
  are moving into the implementation/technology</FONT> <BR><FONT size=2>&gt; 
  &gt; &gt; too soon...</FONT> <BR><FONT size=2>&gt; &gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp; Jukka</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; 
  &gt; I've clipped your comments out, but I wanted to </FONT><BR><FONT 
  size=2>&gt; address Context</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; 
  Negotiation &amp; Context Transfer thread.</FONT> <BR><FONT size=2>&gt; &gt; 
  &gt; &gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; IMO, the 
  'entity' (the piece of code, for example) </FONT><BR><FONT size=2>&gt; that 
  decides</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; whether to hand-off 
  or not, should decide if the target</FONT> <BR><FONT size=2>&gt; &gt; &gt; 
  &gt; &gt; node can support the handoff.&nbsp; I don't think that should 
  be</FONT> <BR><FONT size=2>&gt; &gt; &gt; &gt; &gt; part of the context 
  transfer.</FONT> <BR><FONT size=2>&gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; 
  I referred to this about a month ago, but I was accused of </FONT><BR><FONT 
  size=2>&gt; jumping into</FONT> <BR><FONT size=2>&gt; the</FONT> <BR><FONT 
  size=2>&gt; &gt; solution space way too early.&nbsp; We need two classes of 
  context:</FONT> <BR><FONT size=2>&gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; - 
  Micro-flow Context</FONT> <BR><FONT size=2>&gt; &gt; - Administrative 
  Context:</FONT> <BR><FONT size=2>&gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; 
  Administrative Context: Context that describes the QoS </FONT><BR><FONT 
  size=2>&gt; policy of the APs</FONT> <BR><FONT size=2>&gt; &gt; nearby.</FONT> 
  <BR><FONT size=2>&gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; I referred to it 
  as a Radio Map for a hetrogenous </FONT><BR><FONT size=2>&gt; neighbourhood, 
  and a</FONT> <BR><FONT size=2>&gt; &gt; Tri-cell for a homogenous 
  neighbourhood.&nbsp; A Tri-cell </FONT><BR><FONT size=2>&gt; because a minimum 
  of</FONT> <BR><FONT size=2>&gt; &gt; three pionts are needed to triangulate 
  the relative </FONT><BR><FONT size=2>&gt; position of a mobile</FONT> 
  <BR><FONT size=2>&gt; &gt; based on signal strength.&nbsp; And a Bi-cell 
  becuase a minumum </FONT><BR><FONT size=2>&gt; of two points</FONT> <BR><FONT 
  size=2>&gt; are</FONT> <BR><FONT size=2>&gt; &gt; needed to get a fix on 
  relative velocity.&nbsp; This of course </FONT><BR><FONT size=2>&gt; assumes 
  that</FONT> <BR><FONT size=2>&gt; &gt; Multi-path and other types of 
  Interference are managable.</FONT> <BR><FONT size=2>&gt; &gt;</FONT> <BR><FONT 
  size=2>&gt; &gt; But, again I have digressed into solution space.</FONT> 
  <BR><FONT size=2>&gt; &gt;</FONT> <BR><FONT size=2>&gt; &gt; - 
  Kulwinder.</FONT> <BR><FONT size=2>&gt; </FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C0A80F.873FB910--


From owner-seamoby@diameter.org  Thu Mar  8 20:07:33 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA19205
	for <seamoby-archive@odin.ietf.org>; Thu, 8 Mar 2001 20:07:33 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f28MoPO27731
	for seamoby-list; Thu, 8 Mar 2001 14:50:25 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f28MoNT27726
	for <seamoby@diameter.org>; Thu, 8 Mar 2001 14:50:23 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4SK56>; Thu, 8 Mar 2001 17:58:37 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A4B@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Charlie Perkins'" <charliep@iprg.nokia.com>,
        Nitin H Vaidya
	 <vaidya@cs.tamu.edu>
Cc: KAtwal@herc.zucotto.com, seamoby@diameter.org
Subject: RE: [seamoby] MANET Critique  ( was  Yet Another BOF?
Date: Thu, 8 Mar 2001 17:58:36 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Charlie Perkins [mailto:charliep@iprg.nokia.com]
> Sent: Thursday, March 08, 2001 2:17 PM
> To: Nitin H Vaidya
> Cc: KAtwal@herc.zucotto.com; seamoby@diameter.org
> Subject: Re: [seamoby] MANET Critique ( was Yet Another BOF?
> 
> 
> 
> Hello,
> 
> Your proposed structure places severe restrictions.  With no loss
> of functionality, or increase in complexity, it would be 
> quite possible
> to let any ad hoc node be an Internet Access Point.
 
Any physical node can be an Internet Access Point.  'Super-Master' just like
'Master' and 'Slave' is a software mode (Role).

- Kulwinder.


From owner-seamoby@diameter.org  Fri Mar  9 07:05:00 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA11278
	for <seamoby-archive@odin.ietf.org>; Fri, 9 Mar 2001 07:04:59 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f29APNl29285
	for seamoby-list; Fri, 9 Mar 2001 02:25:23 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x3.nokia.com (mgw-x3.nokia.com [131.228.20.26])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f29APFT29280
	for <seamoby@diameter.org>; Fri, 9 Mar 2001 02:25:15 -0800
Received: from esvir07nok.ntc.nokia.com (esvir07nokt.ntc.nokia.com [172.21.143.39])
	by mgw-x3.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f29AXEH15053
	for <seamoby@diameter.org>; Fri, 9 Mar 2001 12:33:20 +0200 (EET)
Received: from esebh12nok.ntc.nokia.com (unverified) by esvir07nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T522fcb9146ac158f27079@esvir07nok.ntc.nokia.com>;
 Fri, 9 Mar 2001 12:33:08 +0200
Received: by esebh12nok with Internet Mail Service (5.5.2652.78)
	id <GS5RN84J>; Fri, 9 Mar 2001 12:33:08 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680AB95@eseis04nok>
From: john.loughney@nokia.com
To: kempf@heliopolis.Eng.Sun.COM, john.loughney@nokia.com,
        seamoby@diameter.org, Madjid.Nakhjiri@motorola.com
Subject: RE: [seamoby] MM vs CT
Date: Fri, 9 Mar 2001 12:33:06 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi James,

> Actually, I think micromo covers both context transfer and 
> paging in its
> own way. The paging group talked about doing paging for micromo and
> decided it was premature, before the outlines of the micromo problem
> were clearly stated. So we primarily focussed on mobile IP, but we
> did include an item in our recommendations to look at paging for
> micromo when a clear problem statement emerged, and, of course, if
> a solution to paging were part of the micromo requirements. This 
> is actually part of the problem of not having completed a 
> clear problem  about micromo, it is hard to see exactly what it covers. 

I agree completely with you.  Of course, we should clear up
issues with the problem statement [everyone can comment on 
v01 of the draft!] but it would be good to define the
'interfaces' so to speak between CT, MM & Paging.

John


From owner-seamoby@diameter.org  Fri Mar  9 12:38:05 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA25066
	for <seamoby-archive@odin.ietf.org>; Fri, 9 Mar 2001 12:38:04 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f29G9K630289
	for seamoby-list; Fri, 9 Mar 2001 08:09:20 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from idcpa4.pa.interdigital.com (idcmail.interdigital.com [12.32.197.142])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f29G81T30284
	for <seamoby@cdma-2000.org>; Fri, 9 Mar 2001 08:08:02 -0800
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <DLAL4W99>; Fri, 9 Mar 2001 11:15:29 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D01F1F76D@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>
To: Gary Kenward <gkenward@nortelnetworks.com>,
        IETF seamless micro-mobility <seamoby@cdma-2000.org>,
        Pat Calhoun
	 <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] test *****1
Date: Fri, 9 Mar 2001 11:15:27 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

this is a test


From owner-seamoby@diameter.org  Fri Mar  9 16:18:23 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA05397
	for <seamoby-archive@odin.ietf.org>; Fri, 9 Mar 2001 16:18:23 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f29JJWU30850
	for seamoby-list; Fri, 9 Mar 2001 11:19:32 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f29JJUT30845
	for <seamoby@diameter.org>; Fri, 9 Mar 2001 11:19:30 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f29JQI013703
	for <seamoby@diameter.org>; Fri, 9 Mar 2001 11:26:19 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f29JRfI24738
	for <seamoby@diameter.org>; Fri, 9 Mar 2001 11:27:41 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A0A.006B0C74 ; Fri, 9 Mar 2001 11:29:15 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: seamoby@diameter.org
Message-ID: <88256A0A.006B0A96.00@hqoutbound.ops.3com.com>
Date: Fri, 9 Mar 2001 13:26:37 -0600
Subject: [seamoby] MESSAGE FOR KULWINDER
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk



PLEASE FIX YOUR FROM ADDRESS!

Sorry for shouting.  I have tried a few times in the past to answer
questions directly to you and they have always bounced.  Is the
from address in your Email set up properly?  Sorry for the spam
to the list.

Thanks Kulwinder and list,

Phil




From owner-seamoby@diameter.org  Fri Mar  9 18:08:39 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA09432
	for <seamoby-archive@odin.ietf.org>; Fri, 9 Mar 2001 18:08:30 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f29LLKf31155
	for seamoby-list; Fri, 9 Mar 2001 13:21:20 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f29LLET31150
	for <seamoby@diameter.org>; Fri, 9 Mar 2001 13:21:14 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4SLZP>; Fri, 9 Mar 2001 16:29:31 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A5E@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Phil_Neumiller@3com.com'" <Phil_Neumiller@3Com.com>,
        seamoby@diameter.org
Subject: RE: [seamoby] MESSAGE FOR KULWINDER
Date: Fri, 9 Mar 2001 16:29:30 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Try this one. Sorry, there were some email changes.
I too apologize to the list.

> -----Original Message-----
> From: Phil_Neumiller@3com.com [mailto:Phil_Neumiller@3com.com]
> Sent: Friday, March 09, 2001 2:27 PM
> To: seamoby@diameter.org
> Subject: [seamoby] MESSAGE FOR KULWINDER
> 
> 
> 
> 
> PLEASE FIX YOUR FROM ADDRESS!
> 
> Sorry for shouting.  I have tried a few times in the past to answer
> questions directly to you and they have always bounced.  Is the
> from address in your Email set up properly?  Sorry for the spam
> to the list.
> 
> Thanks Kulwinder and list,
> 
> Phil
> 
> 


From owner-seamoby@diameter.org  Mon Mar 12 16:30:42 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA20699
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Mar 2001 16:30:41 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2CIup715216
	for seamoby-list; Mon, 12 Mar 2001 10:56:51 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2CIumT15211
	for <seamoby@diameter.org>; Mon, 12 Mar 2001 10:56:48 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2CJ3jJ17791
	for <seamoby@diameter.org>; Mon, 12 Mar 2001 11:03:45 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f2CJ59I11343
	for <seamoby@diameter.org>; Mon, 12 Mar 2001 11:05:09 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A0D.0068FC54 ; Mon, 12 Mar 2001 11:06:43 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: seamoby@diameter.org
Message-ID: <88256A0D.00688623.00@hqoutbound.ops.3com.com>
Date: Mon, 12 Mar 2001 12:30:26 -0600
Subject: [seamoby] Context Transfer Meeting Minutes Requirements Meeting Kick-Off!
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk



Meeting Minutes for Context Transfer Meeting March 12, 2001 14:00 UTC.

In attendence
--------------------
Rajeev Koodlee
Sharif M. Shahrier
Jukka Manner
Peter Lei
Govind Christian
Madjid Nakhjiri
Gary Kenward
Theo Pagtzis
Michael Thomas
Hamid Sayed
Phil Neumiller



Minutes

+++++++

First order of business hellos.

Agenda bashing.



Talked about nominating a new draft editor.

3 people volunteered, Madjid (half-time) was disqualified.

and Hamid and Shairf.

We can't get hold of Henrik!



Madjid may need to prepare slides for the CT problem statement

presentation at IETF 50.



Someone offered up a personal draft.  It was suggested that to

make the SeaMoby design team "look" more like a co-hesive

team it would be better to have the work reviewed inside the

design team before submitting the draft to the IETF.  It was

felt that the group as a whole was not ready to submit a

draft.  The design team also wants to avoid the dueling

draft phenomena and the un-necessary editorial work of

combining drafts later.



The dicsussion of "what is a requirement" came up.  I was

pretty surprised at this.  For one, requirements work is not

un-precedented in the IETF at all.  There is a huge amount

of it in fact.  Check out these fine examples:


ftp://ftp.isi.edu/in-notes/std/std4.txt
ftp://ftp.isi.edu/in-notes/rfc1122.txt
ftp://ftp.isi.edu/in-notes/rfc1123.txt
ftp://ftp.isi.edu/in-notes/rfc3067.txt
ftp://ftp.isi.edu/in-notes/rfc2906.txt
ftp://ftp.isi.edu/in-notes/rfc2882.txt
ftp://ftp.isi.edu/in-notes/rfc2805.txt
ftp://ftp.isi.edu/in-notes/rfc2779.txt

My all time favorite book on requirements is:

Exploring Requirements : Quality Before Design
by Donald C. Gause, Gerald M. Weinberg
- Its great!

The discussion meandered from there into "what is
context".  Of course it got into what can we can
assume about the architecture:

Then the people they wondered and they said

well what if its peer-to-peer (and phil said yeah!)
and somebody said what if its centralized (and phil made a
barfing sound!)
and somebody said what if its client-server

and someboby (in a very calm and reassuring voice) said
clearly we will need to consider the context transfer
requirements in terms of different mobility network
architectures.

Somewhere in this part of the discussion there was a
discusion of  contex transfer triggers.  Someone
mentioned tying them to handover and actually tying the
CT to mobility signalling messages.  I almost fell out
of  my chair.  I looked up in the sky and said
YEEEEAAASSSs.  These guys have got it!!!!!

Then Phil said yes and also in the case of

MANETS, micro-mobility, and macro-mobility.

The the people they wondered and they said

Oh no, not manets! but others they said yes, there was
much confusion among the designers...  Someone mentioned
GPRS and Phil become ugly at the mention of GPSRs.
I commend Gary here for bringing order to the onslaught of
chaos that errupted.

The conversation slowly drifted to the actual nature of context.
Whether context should/could be negotiable chunks.  What types
of context would be transferred but this quickly digressed
into a discussion of the temporal aspects i.e. asycnchronous
versus sychronous context transfer methods and Gary quickly
grasped hold of the meandering meeting again.

The meeting then ended with some categorization of high level
bullets that would likely be stakes in the ground for the eventual
context transfer draft

Framework
Functionality
QoS
Robust Transport Protocol
Security
Seperable Context Parts
Negotiation (CNP draft (Extract some requirements))
Evaluation

The CT DT will meet again Monday following the IETF.

As always if you find any errors in these somewhat exagerated
minutes please post followups to the main list.

BTW, I spilled tea all over today's minutes and they are all
washed out so the quality has suffered greatly.  I apologize
for this.

Thank you,

Phil Neumiller




From owner-seamoby@diameter.org  Mon Mar 12 19:48:10 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA26247
	for <seamoby-archive@odin.ietf.org>; Mon, 12 Mar 2001 19:48:09 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2CMFCT15752
	for seamoby-list; Mon, 12 Mar 2001 14:15:12 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2CMDsT15747
	for <seamoby@cdma-2000.org>; Mon, 12 Mar 2001 14:13:54 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA05826
	for <seamoby@cdma-2000.org>; Mon, 12 Mar 2001 14:22:20 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA10069
	for <seamoby@cdma-2000.org>; Mon, 12 Mar 2001 14:22:20 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id OAA11340
	for <seamoby@cdma-2000.org>; Mon, 12 Mar 2001 14:22:19 -0800 (PST)
Date: Mon, 12 Mar 2001 14:17:47 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] To all seamoby DT presenters
To: seamoby@cdma-2000.org
Message-ID: <Roam.SIMC.2.0.6.984435467.25595.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

You know who you are, but I don't. Could the people that were selected to
discuss the DT results please contact me with:

1. Amount of time required (need this by tomorrow)
2. Your Name (by tomorrow)
3. Your slides (need this by Friday)

PatC



From owner-seamoby@diameter.org  Wed Mar 14 12:22:03 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA28689
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 12:22:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2EGdWc01002
	for seamoby-list; Wed, 14 Mar 2001 08:39:32 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2EGdSF00991
	for <seamoby@cdma-2000.org>; Wed, 14 Mar 2001 08:39:29 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA24012;
	Wed, 14 Mar 2001 07:47:52 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA07684;
	Wed, 14 Mar 2001 07:47:52 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id HAA16171;
	Wed, 14 Mar 2001 07:47:50 -0800 (PST)
Date: Wed, 14 Mar 2001 07:43:16 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] Thanks to all those find folks at my broadband provider...
To: seamoby@cdma-2000.org, l2tp@l2pt.net, diameter@diameter.org
Message-ID: <Roam.SIMC.2.0.6.984584596.17741.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

... the list has been down for nearly a day. We are back in business.

PatC



From owner-seamoby@diameter.org  Wed Mar 14 12:51:03 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA29714
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 12:51:02 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2EHCXG01143
	for seamoby-list; Wed, 14 Mar 2001 09:12:33 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2EHCVF01136
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 09:12:31 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA03319;
	Wed, 14 Mar 2001 08:20:56 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA20622;
	Wed, 14 Mar 2001 08:20:55 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id IAA23456;
	Wed, 14 Mar 2001 08:20:54 -0800 (PST)
Message-Id: <200103141620.IAA23456@heliopolis.Eng.Sun.COM>
Date: Wed, 14 Mar 2001 08:20:54 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: Re: [seamoby] Micro-mobility Issues for IESG to Consider
To: seamoby@diameter.org, Phil_Neumiller@3Com.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: WfirrApfzXr+3xnXyF+NMA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Phil,

>1).  If the IESG  is looking for Justification for Micro-mobility
>
>     A).  We may look no farther than the justification used for
>                        fast handoff work in the MIP group.
>                B).  The justification for micro-mobility is precisely the same
>                       as that used for fast handoff (i.e. at this point 
stricly
>                       an emotional appeal since no hard data currently 
exists).
>                C).  All the very same logical arguments apply.
>                D).  Should it be stricly SeaMoby's burden to dig up the
>                        hard data?  If so it should be explicitly stated in the
>                        charter that we are to conduct analytical modelling,
>                        simulations, and measurements of controlled
>                        experimental testbeds of MIP, micro-mobility options,
>                        and interaction MANET alternatives.  This may actually
>                        get us somewhere useful.
>

In fact, the fast handoff work in MIP is based on several years of
experience and experiments involving mobile IP, in addition to 
some considerable discussion in TSG-P during the development of IOS 4.1
in which the usability and deployment of MIP was considered outside
of an IETF context. I know your opinion of the 3G work is low, but
this work was extremely useful in refining MIP and identifying problems
(and handoff performance was one of them). 3GPP2 is committed to
MIP, and to seeing that it works well. 3GPP chose not to go that
route, and, instead, invented their own proprietary protocol, and 3GPP
has never come to IETF with a list of issues regarding MIP, not before
they decided on GPRS nor now. 

>2).  Since Pat is heavily involved in the fast handoff work, and he is
>       going to argue the case for SeaMoby micro-mobility:
>       [Please NOTE: I am not making any accusations of Pat ]
>                A).  Do we have a case of the fox gaurding the hen house?
>                       (Please don't go non-linear Pat (I want the group to 
seem
>                         unbiased on the surface))
>                B).  Should a micro-mobility "fanatic" chosen by the WG join
>                       Pat in the IESG justification discusssion?

Actually, if I were Pat, I *would* go nonlinear on this. I think Pat
has done an excellent job as working group chair in maintaining
impartiality and representing all of the viewpoints in the
working group to the IESG. I, personally, resent this implication
that he cannot be unbiased. 

I suspect that the IESG would look far more favorably on a positive
recommendation from Pat about micromobility than on one from a
"fanatic". Fanatics are a dime a dozen in the IETF, people with good
architectural sense, experience in designing complex systems, and the
ability to articulate that, like Pat, are a lot more rare.

		jak




From owner-seamoby@diameter.org  Wed Mar 14 13:00:20 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA29946
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 13:00:19 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2EGwpo01090
	for seamoby-list; Wed, 14 Mar 2001 08:58:51 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2EGwnF01085
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 08:58:49 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2EG5hv15669
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 08:05:44 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f2EEXBq06484
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 06:34:13 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A0F.004FE5E4 ; Wed, 14 Mar 2001 06:32:41 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: seamoby@diameter.org
Message-ID: <88256A0F.004FE3EB.00@hqoutbound.ops.3com.com>
Date: Wed, 14 Mar 2001 08:30:59 -0600
Subject: [seamoby] Micro-mobility Issues for IESG to Consider
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk




Fellow SeaMobites,

1).  If the IESG  is looking for Justification for Micro-mobility

     A).  We may look no farther than the justification used for
                        fast handoff work in the MIP group.
                B).  The justification for micro-mobility is precisely the same
                       as that used for fast handoff (i.e. at this point stricly
                       an emotional appeal since no hard data currently exists).
                C).  All the very same logical arguments apply.
                D).  Should it be stricly SeaMoby's burden to dig up the
                        hard data?  If so it should be explicitly stated in the
                        charter that we are to conduct analytical modelling,
                        simulations, and measurements of controlled
                        experimental testbeds of MIP, micro-mobility options,
                        and interaction MANET alternatives.  This may actually
                        get us somewhere useful.

2).  Since Pat is heavily involved in the fast handoff work, and he is
       going to argue the case for SeaMoby micro-mobility:
       [Please NOTE: I am not making any accusations of Pat ]
                A).  Do we have a case of the fox gaurding the hen house?
                       (Please don't go non-linear Pat (I want the group to seem
                         unbiased on the surface))
                B).  Should a micro-mobility "fanatic" chosen by the WG join
                       Pat in the IESG justification discusssion?

I apologize for my last Email's rants against GPRS and UMTS.  I could
have just as well have chosen Bluetooth or cdma2000.  My message
is not to build empires around layer 2 technologies which is all too
common these days.  As for the rest of the rant, well I hope it was
entertaining and not boorish.  The first part and the last part were
dead serious and I hope were not ignored.  The silence has been
deafening, hence I have sent this Dale Caregie-ized follow-up.

Thank you,

Phil Neumiller.




From owner-seamoby@diameter.org  Wed Mar 14 13:47:11 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA01075
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 13:47:10 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2EGsuU01081
	for seamoby-list; Wed, 14 Mar 2001 08:54:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2EGsrF01076
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 08:54:53 -0800
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2DKtq208588
	for <seamoby@diameter.org>; Tue, 13 Mar 2001 22:55:52 +0200 (EET)
Received: from esebh24nok.ntc.nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T52469f449fac158f25063@esvir05nok.ntc.nokia.com>;
 Tue, 13 Mar 2001 22:56:01 +0200
Received: by esebh24nok with Internet Mail Service (5.5.2652.78)
	id <G6LV991R>; Tue, 13 Mar 2001 22:56:01 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680ABB8@eseis04nok>
From: john.loughney@nokia.com
To: Phil_Neumiller@3Com.com, seamoby@diameter.org
Subject: [seamoby] Some thoughts on micro-mob before 50th
Date: Tue, 13 Mar 2001 22:56:00 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Phil,

You don't need to send this to both the Seamoby & the MM list - 
I believe that everyone on the MM DT is also on the Seamoby list.

Secondly,

> We need to preserve our freedoms at least in America guys!

the IETF is not America & the Internet sure isn't America.
2G, 2.5G and 3G (of both kinds) isn't the Internet either.

Finally, I really don't see any point in the mail - at least
anything relevant to SeaMoby.  If you feel like having a long 
rant, why not do it at the bar bof.  I'll even spot you a 
beer!

I'm sure that you have very good ideas on ways to procede, so why
not channel your energies into submitting your requirements for
paging, ct & mm to the list?

cheers,
John


From owner-seamoby@diameter.org  Wed Mar 14 14:55:18 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA02903
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 14:55:17 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2EIZK901469
	for seamoby-list; Wed, 14 Mar 2001 10:35:20 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2EIY2F01464
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 10:34:02 -0800
Received: from esvir08nok.nokia.com (esvir08nokt.ntc.nokia.com [172.21.143.40])
	by mgw-x4.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2EHgX824629
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 19:42:33 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir08nok.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T524b146202ac158f28ff6@esvir08nok.nokia.com>;
 Wed, 14 Mar 2001 19:42:25 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <G8D9SC8K>; Wed, 14 Mar 2001 19:42:25 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680ABC7@eseis04nok>
From: john.loughney@nokia.com
To: Phil_Neumiller@3Com.com, seamoby@diameter.org
Subject: RE: [seamoby] Micro-mobility Issues for IESG to Consider
Date: Wed, 14 Mar 2001 19:42:23 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Phil,

One comment:

>                 B).  The justification for micro-mobility is 
> 				precisely the same
>                       as that used for fast handoff (i.e. at 
> 				this point stricly
>                       an emotional appeal since no hard data 
> 				currently exists).

MIP has been deployed, at least in lab situations, by many 
companies.  Fast Handoff is an enhancement to an existing
protocol based upon experience.  MM isn't really in the 
same league (yet).  I don't see any parallels between the
two (useful parallels, at least).  If we want MM, then
we need to justify it on its own merits.

John


From owner-seamoby@diameter.org  Wed Mar 14 18:08:21 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA06231
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 18:08:20 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2EMc5U02222
	for seamoby-list; Wed, 14 Mar 2001 14:38:05 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2EMbRF02217
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 14:37:28 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2ELiMd03031;
	Wed, 14 Mar 2001 13:44:22 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f2ELjlE16157;
	Wed, 14 Mar 2001 13:45:47 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A0F.00778ABD ; Wed, 14 Mar 2001 13:45:43 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: john.loughney@nokia.com
cc: seamoby@diameter.org
Message-ID: <88256A0F.0077708D.00@hqoutbound.ops.3com.com>
Date: Wed, 14 Mar 2001 15:41:05 -0600
Subject: RE: [seamoby] Micro-mobility Issues for IESG to Consider
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk




Hi John,

Comments are below.




>Phil,
>
>One comment:

>>                 B).  The justification for micro-mobility is
>>                  precisely the same
>>                       as that used for fast handoff (i.e. at
>>                  this point stricly
>>                       an emotional appeal since no hard data
>>                  currently exists).

>MIP has been deployed, at least in lab situations, by many
>companies.

1).  I believe in the world, the US based carrier Nextel has
     the largest Mobile-IP installed base.  They are using
     Motorola/3Com equipment.

2).  The second largest installation is also in the US and it
     is Sprint, also a combination of Motorola/3Com equipment.

[If somebody has other data please correct me]

3).  In both cases, I believe their metropolitan subnets are just
     big subnets, i.e. the subscriber's can not roam off the
     edge, i.e. there is never a mobile IP handoff!  So these
     are not very good testbeds.  [again please correct me if
     I am wrong]  I would cc Phil Roberts to get the data but
     he has just left Motorola!


>  Fast Handoff is an enhancement to an existing
> protocol based upon experience.  MM isn't really in the
> same league (yet).  I don't see any parallels between the
> two (useful parallels, at least).  If we want MM, then
> we need to justify it on its own merits.
>
> John

4).  It is clearly not based on customer installed base
     experience John, at least for the largest installed
     bases in the world.

5).  Regarding parallels.  IMO they both do the same thing
     in the requirements sense NOT in the PROTOCOL SENSE.
     They both reduce or stop signallignalling upstream to
     the home for or foreign agent, they both make handovers
     qualitatively more seamless (nobody has numbers!).

So I disagree.  I say it is just as justified as Fast handover
and presents a viable alternative to fast handover.  In fact
it presents a solution for implementations where there is
no mobile IP infrastructure in place like perhaps in home
networking situations, camping trips, remote automobile
scenarios, dozens of other adhoc situations.

Thanks,

Phil Neumiller








From owner-seamoby@diameter.org  Wed Mar 14 20:33:44 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA07567
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 20:33:44 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2F1JLZ02529
	for seamoby-list; Wed, 14 Mar 2001 17:19:21 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2F1JIF02524
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 17:19:18 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2F0QDd07172
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 16:26:13 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f2F0RdE22929
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 16:27:39 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A10.00028719 ; Wed, 14 Mar 2001 16:27:36 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: seamoby@diameter.org
Message-ID: <88256A10.00028646.00@hqoutbound.ops.3com.com>
Date: Wed, 14 Mar 2001 18:26:37 -0600
Subject: [seamoby] Mis-understandings
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk



I don't usually apologize.  I am going to now.  I want each and every person
on this list to know that I have the deepest trust and respect for our chair and
all our
leaders and old timers on this group.

Since I left my co-chair position of the SeaMoby group you may have noticed that
I have in general become kind of become a butt head or much worse of a ____
(fill in  your favorite pejoritive).  Forgive me for this.  I will work for
change.

I want to apologize for my rants and spam to the list.  I want to apologize for
stupid
unfounded accusations and stupid remarks.  I hope to continue to contribute to
the
technical arguments on the list in the future.

I look forward to an improved working relationship with all and realize this
will take
much effort on my part since its primarly a growth issue for me.  BTW, guys this
is what happens to old programmers that sit debugging code in a cubicle for
a couple decades.

Sincerely,

Phil Neumiler





From owner-seamoby@diameter.org  Wed Mar 14 21:03:14 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA07939
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 21:03:13 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2F1jeq02614
	for seamoby-list; Wed, 14 Mar 2001 17:45:40 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2F1jcF02609
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 17:45:38 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2F0qXd11259
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 16:52:33 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f2F0rxE28565
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 16:53:59 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A10.0004EFA3 ; Wed, 14 Mar 2001 16:53:54 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: seamoby@diameter.org
Message-ID: <88256A10.0004EE18.00@hqoutbound.ops.3com.com>
Date: Wed, 14 Mar 2001 18:52:36 -0600
Subject: [seamoby] Minutes: Paging Design Team Meeting Requirements Kick Off!
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk




March 14, 2001 17:00 UTC

In Attendence
----------------------------------------------
Sharif N, Shahrier,      Interdigital, Inc.
Arthur H. M. Ross,  Novatel Wireless, Inc.
Bechet Sarikaya,         Alcatel, Inc.
Peter Lei,               Cisco Systems, Inc.
Ramachandran Ramjee,     Lucent Technologies, Inc.
James Kemp,         Sun Microsystems, Inc.
Phil Neumiller,          3Com, Inc.

-1).  Hellos

0). General Agenda was discuss list questions about the paging draft
    and the draft and upcoming IETF meeting.

1). There was a brief and rapid discussion about agent advertisements
     and MIP extensions that were brought out in the HAWAII proposal.
     I did not catch the conclusion of this conversation.  If it could be posted
     to the paging list so that it could be captured in the draf that would be
     very good.

2).  We agreed to a bi-weekly process of draft updates.

        Bi-weekly Draft Revision Process for Paging DT
       ==========================================
       A). Comments on  the paging DT submitted drafts are due by Monday
             morning.
       B). All previously posted comments meeting the Monday deadline
             will be discussed during the Wednesday conference call.
       C). The draft editor will incorporate the consensus of the DT
              changes into the draft by the following Monday allowing a
              a one week review period for the new draft.

3).  There was a brief discusion about whether a mobile should
        notify the network when it goes dormant.

Phil's NOTE:  I like the idea of preparing a paging draft specifically
for MIP that we can finish right away and send on its way and a more
forward looking draft that we can build into a more utopian paging
draft.  In the case of the MIP draft we can make some assumptions
about the architecture like the existance of an HA or FA for instance
and we can talk about what a MN might notify when it goes dormant.
My $2.

4).  Further discuss centered around James followup Email on
       Bechet's draft that was posted to the list.


5).  Its a sticky issue to isolate a problem statement from a requirment
       from a solution space issue sometimes.

6).  Recognizing James comment recognizing Kulwinders comments
       about the many different paging modes, I would suggest that
       we be flexible enough to support network clue and mobile
        clued modes or even mobile gives network a clue about
        supported paging modes (context transfer?)

7). Phil's NOTE on James Pg 2 comment.
       I am not sure about the dorman mode MN MUST have to respond
      to L3 pages.  As Kulwinder has stated this may imply waking up
      a heavy current draining micro-processor where a CMOS radio
      L2 is actively linked to a base site and the L3 ACK can be proxy
       from there.  You get the same effect.

8).  I think the concept of keeping paging state in a router should
       not be implied.  This is making a solution space decision.
       If it is a router, is it an edge router, a core, router, is it a home
       agent router?  Why couldn't it be a server?  -pdn

9).  Saying that paging protocol must be robust is rather redundant.
       I assume that we will pick a robust transport protocol to carry
       it right?

As always please post any followups or corrections to these
minutes.

Thank you!

Phil Neumiller




From owner-seamoby@diameter.org  Wed Mar 14 21:03:17 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA07950
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 21:03:16 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2F1iiY02605
	for seamoby-list; Wed, 14 Mar 2001 17:44:44 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2F1hQF02600
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 17:43:26 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Thu, 15 Mar 2001 09:44:53 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 15 Mar 2001 02:35:44 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2EHCXG01143
	for seamoby-list; Wed, 14 Mar 2001 09:12:33 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2EHCVF01136
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 09:12:31 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA03319;
	Wed, 14 Mar 2001 08:20:56 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA20622;
	Wed, 14 Mar 2001 08:20:55 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id IAA23456;
	Wed, 14 Mar 2001 08:20:54 -0800 (PST)
Message-Id: <200103141620.IAA23456@heliopolis.Eng.Sun.COM>
Date: Wed, 14 Mar 2001 08:20:54 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: Re: [seamoby] Micro-mobility Issues for IESG to Consider
To: seamoby@diameter.org, Phil_Neumiller@3Com.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: WfirrApfzXr+3xnXyF+NMA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Phil,

>1).  If the IESG  is looking for Justification for Micro-mobility
>
>     A).  We may look no farther than the justification used for
>                        fast handoff work in the MIP group.
>                B).  The justification for micro-mobility is precisely the same
>                       as that used for fast handoff (i.e. at this point 
stricly
>                       an emotional appeal since no hard data currently 
exists).
>                C).  All the very same logical arguments apply.
>                D).  Should it be stricly SeaMoby's burden to dig up the
>                        hard data?  If so it should be explicitly stated in the
>                        charter that we are to conduct analytical modelling,
>                        simulations, and measurements of controlled
>                        experimental testbeds of MIP, micro-mobility options,
>                        and interaction MANET alternatives.  This may actually
>                        get us somewhere useful.
>

In fact, the fast handoff work in MIP is based on several years of
experience and experiments involving mobile IP, in addition to 
some considerable discussion in TSG-P during the development of IOS 4.1
in which the usability and deployment of MIP was considered outside
of an IETF context. I know your opinion of the 3G work is low, but
this work was extremely useful in refining MIP and identifying problems
(and handoff performance was one of them). 3GPP2 is committed to
MIP, and to seeing that it works well. 3GPP chose not to go that
route, and, instead, invented their own proprietary protocol, and 3GPP
has never come to IETF with a list of issues regarding MIP, not before
they decided on GPRS nor now. 

>2).  Since Pat is heavily involved in the fast handoff work, and he is
>       going to argue the case for SeaMoby micro-mobility:
>       [Please NOTE: I am not making any accusations of Pat ]
>                A).  Do we have a case of the fox gaurding the hen house?
>                       (Please don't go non-linear Pat (I want the group to 
seem
>                         unbiased on the surface))
>                B).  Should a micro-mobility "fanatic" chosen by the WG join
>                       Pat in the IESG justification discusssion?

Actually, if I were Pat, I *would* go nonlinear on this. I think Pat
has done an excellent job as working group chair in maintaining
impartiality and representing all of the viewpoints in the
working group to the IESG. I, personally, resent this implication
that he cannot be unbiased. 

I suspect that the IESG would look far more favorably on a positive
recommendation from Pat about micromobility than on one from a
"fanatic". Fanatics are a dime a dozen in the IETF, people with good
architectural sense, experience in designing complex systems, and the
ability to articulate that, like Pat, are a lot more rare.

		jak



From owner-seamoby@diameter.org  Wed Mar 14 21:05:46 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA07962
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 21:05:46 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2F1bYS02567
	for seamoby-list; Wed, 14 Mar 2001 17:37:34 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2F1bWF02562
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 17:37:32 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Thu, 15 Mar 2001 09:39:04 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 15 Mar 2001 02:27:46 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2EGwpo01090
	for seamoby-list; Wed, 14 Mar 2001 08:58:51 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2EGwnF01085
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 08:58:49 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2EG5hv15669
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 08:05:44 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f2EEXBq06484
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 06:34:13 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A0F.004FE5E4 ; Wed, 14 Mar 2001 06:32:41 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: seamoby@diameter.org
Message-ID: <88256A0F.004FE3EB.00@hqoutbound.ops.3com.com>
Date: Wed, 14 Mar 2001 08:30:59 -0600
Subject: [seamoby] Micro-mobility Issues for IESG to Consider
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk




Fellow SeaMobites,

1).  If the IESG  is looking for Justification for Micro-mobility

     A).  We may look no farther than the justification used for
                        fast handoff work in the MIP group.
                B).  The justification for micro-mobility is precisely the same
                       as that used for fast handoff (i.e. at this point stricly
                       an emotional appeal since no hard data currently exists).
                C).  All the very same logical arguments apply.
                D).  Should it be stricly SeaMoby's burden to dig up the
                        hard data?  If so it should be explicitly stated in the
                        charter that we are to conduct analytical modelling,
                        simulations, and measurements of controlled
                        experimental testbeds of MIP, micro-mobility options,
                        and interaction MANET alternatives.  This may actually
                        get us somewhere useful.

2).  Since Pat is heavily involved in the fast handoff work, and he is
       going to argue the case for SeaMoby micro-mobility:
       [Please NOTE: I am not making any accusations of Pat ]
                A).  Do we have a case of the fox gaurding the hen house?
                       (Please don't go non-linear Pat (I want the group to seem
                         unbiased on the surface))
                B).  Should a micro-mobility "fanatic" chosen by the WG join
                       Pat in the IESG justification discusssion?

I apologize for my last Email's rants against GPRS and UMTS.  I could
have just as well have chosen Bluetooth or cdma2000.  My message
is not to build empires around layer 2 technologies which is all too
common these days.  As for the rest of the rant, well I hope it was
entertaining and not boorish.  The first part and the last part were
dead serious and I hope were not ignored.  The silence has been
deafening, hence I have sent this Dale Caregie-ized follow-up.

Thank you,

Phil Neumiller.



From owner-seamoby@diameter.org  Wed Mar 14 21:10:30 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA08001
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 21:10:29 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2F1uEZ02653
	for seamoby-list; Wed, 14 Mar 2001 17:56:14 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2F1uBF02648
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 17:56:11 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Thu, 15 Mar 2001 09:57:34 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 15 Mar 2001 04:37:54 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2EIZK901469
	for seamoby-list; Wed, 14 Mar 2001 10:35:20 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2EIY2F01464
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 10:34:02 -0800
Received: from esvir08nok.nokia.com (esvir08nokt.ntc.nokia.com [172.21.143.40])
	by mgw-x4.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2EHgX824629
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 19:42:33 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir08nok.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T524b146202ac158f28ff6@esvir08nok.nokia.com>;
 Wed, 14 Mar 2001 19:42:25 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <G8D9SC8K>; Wed, 14 Mar 2001 19:42:25 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680ABC7@eseis04nok>
From: john.loughney@nokia.com
To: Phil_Neumiller@3Com.com, seamoby@diameter.org
Subject: RE: [seamoby] Micro-mobility Issues for IESG to Consider
Date: Wed, 14 Mar 2001 19:42:23 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Phil,

One comment:

>                 B).  The justification for micro-mobility is 
> 				precisely the same
>                       as that used for fast handoff (i.e. at 
> 				this point stricly
>                       an emotional appeal since no hard data 
> 				currently exists).

MIP has been deployed, at least in lab situations, by many 
companies.  Fast Handoff is an enhancement to an existing
protocol based upon experience.  MM isn't really in the 
same league (yet).  I don't see any parallels between the
two (useful parallels, at least).  If we want MM, then
we need to justify it on its own merits.

John


From owner-seamoby@diameter.org  Wed Mar 14 21:18:11 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA08032
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 21:18:10 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2F1mc002628
	for seamoby-list; Wed, 14 Mar 2001 17:48:38 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2F1mZF02623
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 17:48:35 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Thu, 15 Mar 2001 09:49:12 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 15 Mar 2001 03:31:35 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2EGsuU01081
	for seamoby-list; Wed, 14 Mar 2001 08:54:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2EGsrF01076
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 08:54:53 -0800
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2DKtq208588
	for <seamoby@diameter.org>; Tue, 13 Mar 2001 22:55:52 +0200 (EET)
Received: from esebh24nok.ntc.nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T52469f449fac158f25063@esvir05nok.ntc.nokia.com>;
 Tue, 13 Mar 2001 22:56:01 +0200
Received: by esebh24nok with Internet Mail Service (5.5.2652.78)
	id <G6LV991R>; Tue, 13 Mar 2001 22:56:01 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680ABB8@eseis04nok>
From: john.loughney@nokia.com
To: Phil_Neumiller@3Com.com, seamoby@diameter.org
Subject: [seamoby] Some thoughts on micro-mob before 50th
Date: Tue, 13 Mar 2001 22:56:00 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Phil,

You don't need to send this to both the Seamoby & the MM list - 
I believe that everyone on the MM DT is also on the Seamoby list.

Secondly,

> We need to preserve our freedoms at least in America guys!

the IETF is not America & the Internet sure isn't America.
2G, 2.5G and 3G (of both kinds) isn't the Internet either.

Finally, I really don't see any point in the mail - at least
anything relevant to SeaMoby.  If you feel like having a long 
rant, why not do it at the bar bof.  I'll even spot you a 
beer!

I'm sure that you have very good ideas on ways to procede, so why
not channel your energies into submitting your requirements for
paging, ct & mm to the list?

cheers,
John


From owner-seamoby@diameter.org  Wed Mar 14 21:36:09 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA09177
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 21:36:09 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2F1iXo02595
	for seamoby-list; Wed, 14 Mar 2001 17:44:33 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2F1hFF02586
	for <seamoby@cdma-2000.org>; Wed, 14 Mar 2001 17:43:15 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Thu, 15 Mar 2001 09:44:51 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 15 Mar 2001 01:59:36 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2EGdWc01002
	for seamoby-list; Wed, 14 Mar 2001 08:39:32 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2EGdSF00991
	for <seamoby@cdma-2000.org>; Wed, 14 Mar 2001 08:39:29 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA24012;
	Wed, 14 Mar 2001 07:47:52 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA07684;
	Wed, 14 Mar 2001 07:47:52 -0800 (PST)
Received: from mordor (mordor.Eng.Sun.COM [129.146.120.122])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id HAA16171;
	Wed, 14 Mar 2001 07:47:50 -0800 (PST)
Date: Wed, 14 Mar 2001 07:43:16 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] Thanks to all those find folks at my broadband provider...
To: seamoby@cdma-2000.org, l2tp@l2pt.net, diameter@diameter.org
Message-ID: <Roam.SIMC.2.0.6.984584596.17741.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

... the list has been down for nearly a day. We are back in business.

PatC


From owner-seamoby@diameter.org  Wed Mar 14 21:41:32 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA09209
	for <seamoby-archive@odin.ietf.org>; Wed, 14 Mar 2001 21:41:32 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2F2ERh02696
	for seamoby-list; Wed, 14 Mar 2001 18:14:27 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m018.com ([210.112.11.138])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2F2EOF02691
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 18:14:24 -0800
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Thu, 15 Mar 2001 10:15:32 +0900
Received: from charizard.diameter.org ([24.20.167.220]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 15 Mar 2001 07:51:54 +0900
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2EMc5U02222
	for seamoby-list; Wed, 14 Mar 2001 14:38:05 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2EMbRF02217
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 14:37:28 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2ELiMd03031;
	Wed, 14 Mar 2001 13:44:22 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f2ELjlE16157;
	Wed, 14 Mar 2001 13:45:47 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A0F.00778ABD ; Wed, 14 Mar 2001 13:45:43 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: john.loughney@nokia.com
cc: seamoby@diameter.org
Message-ID: <88256A0F.0077708D.00@hqoutbound.ops.3com.com>
Date: Wed, 14 Mar 2001 15:41:05 -0600
Subject: RE: [seamoby] Micro-mobility Issues for IESG to Consider
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk




Hi John,

Comments are below.




>Phil,
>
>One comment:

>>                 B).  The justification for micro-mobility is
>>                  precisely the same
>>                       as that used for fast handoff (i.e. at
>>                  this point stricly
>>                       an emotional appeal since no hard data
>>                  currently exists).

>MIP has been deployed, at least in lab situations, by many
>companies.

1).  I believe in the world, the US based carrier Nextel has
     the largest Mobile-IP installed base.  They are using
     Motorola/3Com equipment.

2).  The second largest installation is also in the US and it
     is Sprint, also a combination of Motorola/3Com equipment.

[If somebody has other data please correct me]

3).  In both cases, I believe their metropolitan subnets are just
     big subnets, i.e. the subscriber's can not roam off the
     edge, i.e. there is never a mobile IP handoff!  So these
     are not very good testbeds.  [again please correct me if
     I am wrong]  I would cc Phil Roberts to get the data but
     he has just left Motorola!


>  Fast Handoff is an enhancement to an existing
> protocol based upon experience.  MM isn't really in the
> same league (yet).  I don't see any parallels between the
> two (useful parallels, at least).  If we want MM, then
> we need to justify it on its own merits.
>
> John

4).  It is clearly not based on customer installed base
     experience John, at least for the largest installed
     bases in the world.

5).  Regarding parallels.  IMO they both do the same thing
     in the requirements sense NOT in the PROTOCOL SENSE.
     They both reduce or stop signallignalling upstream to
     the home for or foreign agent, they both make handovers
     qualitatively more seamless (nobody has numbers!).

So I disagree.  I say it is just as justified as Fast handover
and presents a viable alternative to fast handover.  In fact
it presents a solution for implementations where there is
no mobile IP infrastructure in place like perhaps in home
networking situations, camping trips, remote automobile
scenarios, dozens of other adhoc situations.

Thanks,

Phil Neumiller







From owner-seamoby@diameter.org  Thu Mar 15 01:51:54 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA18191
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Mar 2001 01:51:54 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2F65Dx03146
	for seamoby-list; Wed, 14 Mar 2001 22:05:13 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2F65BF03141
	for <seamoby@diameter.org>; Wed, 14 Mar 2001 22:05:11 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4SP0J>; Thu, 15 Mar 2001 00:13:38 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A79@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        Phil_Neumiller@3Com.com, seamoby@diameter.org
Subject: RE: [seamoby] Micro-mobility Issues for IESG to Consider
Date: Thu, 15 Mar 2001 00:13:30 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> Sent: Wednesday, March 14, 2001 12:42 PM
> To: Phil_Neumiller@3com.com; seamoby@diameter.org
> Subject: RE: [seamoby] Micro-mobility Issues for IESG to Consider
> 
> 
> Phil,
> 
> One comment:
> 
> >                 B).  The justification for micro-mobility is 
> > 				precisely the same
> >                       as that used for fast handoff (i.e. at 
> > 				this point stricly
> >                       an emotional appeal since no hard data 
> > 				currently exists).
> 
> MIP has been deployed, at least in lab situations, by many 
> companies.  Fast Handoff is an enhancement to an existing
> protocol based upon experience.  MM isn't really in the 
> same league (yet).  

Is MIP willing to wait for a MM with lab experience?
Do you have preformance numbers for MIP across the Internet, or only on
private 3GPP2 IP networks?

> I don't see any parallels between the
> two (useful parallels, at least).

Useful parallels:

Access	Core
LAN		WAN
Seamoby	MIP
Private	Service Provider
Low Cost	Fault Tolerant Redundancy
Small		Big

We can continue to discuss details like which is faster, but the real issue
is structural.  
Do we really want to write another Core mobility protocol to work with other
wireless access technologies?  
Or, promote protocol re-use by requiring that all IP mobility solutions
adhere to the Access/Core model? 

The real problem with MIP, as stated by many others, is deployment
flexibility across various wireless access technologies.

What I would like to see MIP proponents focus on discussing is:  

What are the merits of IP mobility protocol re-use across various core
network and mobile access network technologies?

Can MIP work effectively on and with:

Mobile Access Network Gateways?
Mobile Routers?
Mobile Nodes?
Mobile Hosts?
Mobile unaware nodes?
Ad Hoc mobile networks?

What is the clear division of labour between the core mobility protocol MIP
and access mobility protocols?

These questions are no longer esoteric, but will require real answers from
MIP proponents next week.

3G Cellular is no longer alone in seeking IP mobility solutions from the
IETF.

- Kulwinder.

>  If we want MM, then
> we need to justify it on its own merits.
> 
> John
> 


From owner-seamoby@diameter.org  Thu Mar 15 09:51:46 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA00547
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Mar 2001 09:51:45 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2FEI0604342
	for seamoby-list; Thu, 15 Mar 2001 06:18:00 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from ns.kreative.net (root@ns.kreative.net [216.181.1.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2FEHwF04337
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 06:17:58 -0800
Received: from david (laurel-108.dsdial.net [209.12.175.108])
	by ns.kreative.net (8.9.3/8.9.3) with SMTP id IAA07088;
	Thu, 15 Mar 2001 08:27:01 -0500
Message-ID: <001a01c0ad6d$6b882960$0100000a@david>
From: "David Martin" <dmartin@kreative.net>
To: <Phil_Neumiller@3Com.com>, <john.loughney@nokia.com>
Cc: <seamoby@diameter.org>
References: <88256A0F.0077708D.00@hqoutbound.ops.3com.com>
Subject: Re: [seamoby] Micro-mobility Issues for IESG to Consider
Date: Thu, 15 Mar 2001 08:31:42 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Nextel has ~20 HA and ~200 FAs
They are used to support a large percentage of the 7 million subscribers
(all data subscribers).
*All* of Nextel's data subscribers are Mobile IP clients, *All* do binding
updates several times a day (based mostly on mobility).  HA-FA Tunnells are
built nation-wide.
In short, Nextel has had Mobile IP fully deployed and operational for almost
a year.
----- Original Message -----
From: <Phil_Neumiller@3Com.com>
To: <john.loughney@nokia.com>
Cc: <seamoby@diameter.org>
Sent: Wednesday, March 14, 2001 1:41 PM
Subject: RE: [seamoby] Micro-mobility Issues for IESG to Consider


>
>
>
> Hi John,
>
> Comments are below.
>
>
>
>
> >Phil,
> >
> >One comment:
>
> >>                 B).  The justification for micro-mobility is
> >>                  precisely the same
> >>                       as that used for fast handoff (i.e. at
> >>                  this point stricly
> >>                       an emotional appeal since no hard data
> >>                  currently exists).
>
> >MIP has been deployed, at least in lab situations, by many
> >companies.
>
> 1).  I believe in the world, the US based carrier Nextel has
>      the largest Mobile-IP installed base.  They are using
>      Motorola/3Com equipment.
>
> 2).  The second largest installation is also in the US and it
>      is Sprint, also a combination of Motorola/3Com equipment.
>
> [If somebody has other data please correct me]
>
> 3).  In both cases, I believe their metropolitan subnets are just
>      big subnets, i.e. the subscriber's can not roam off the
>      edge, i.e. there is never a mobile IP handoff!  So these
>      are not very good testbeds.  [again please correct me if
>      I am wrong]  I would cc Phil Roberts to get the data but
>      he has just left Motorola!
>
>
> >  Fast Handoff is an enhancement to an existing
> > protocol based upon experience.  MM isn't really in the
> > same league (yet).  I don't see any parallels between the
> > two (useful parallels, at least).  If we want MM, then
> > we need to justify it on its own merits.
> >
> > John
>
> 4).  It is clearly not based on customer installed base
>      experience John, at least for the largest installed
>      bases in the world.
>
> 5).  Regarding parallels.  IMO they both do the same thing
>      in the requirements sense NOT in the PROTOCOL SENSE.
>      They both reduce or stop signallignalling upstream to
>      the home for or foreign agent, they both make handovers
>      qualitatively more seamless (nobody has numbers!).
>
> So I disagree.  I say it is just as justified as Fast handover
> and presents a viable alternative to fast handover.  In fact
> it presents a solution for implementations where there is
> no mobile IP infrastructure in place like perhaps in home
> networking situations, camping trips, remote automobile
> scenarios, dozens of other adhoc situations.
>
> Thanks,
>
> Phil Neumiller
>
>
>
>
>



From owner-seamoby@diameter.org  Thu Mar 15 10:52:10 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA01676
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Mar 2001 10:52:10 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2FFTCr04494
	for seamoby-list; Thu, 15 Mar 2001 07:29:12 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2FFT9F04489
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 07:29:09 -0800
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2FEbS225724
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 16:37:28 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T524f91844cac158f21082@esvir01nok.ntc.nokia.com>;
 Thu, 15 Mar 2001 16:37:34 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <G8D9SZAL>; Thu, 15 Mar 2001 16:35:23 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE10680ABE1@eseis04nok>
From: john.loughney@nokia.com
To: kulwinder.atwal@zucotto.com, Phil_Neumiller@3Com.com, seamoby@diameter.org
Subject: RE: [seamoby] Micro-mobility Issues for IESG to Consider
Date: Thu, 15 Mar 2001 16:35:17 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Kulwinder,

At the end of the day, we need to have a strong problem statement.
The current draft is good, but can be better.  We need another
version, which should be done ASAP after the Minneapolis meeting.

I do think that, independently of the problem statement, individuals
could be sending their individual requirements for MM.  

IMO, I think the process has been working fine - the biggest hiccup
was when someone sent attacking MIP & CC:ing the MIP list.  I don't
think that is a constructive approach ...


> The real problem with MIP, as stated by many others, is deployment
> flexibility across various wireless access technologies.
> 
> What I would like to see MIP proponents focus on discussing is:  
> 
> What are the merits of IP mobility protocol re-use across various core
> network and mobile access network technologies?
> 
> Can MIP work effectively on and with:
> 
> Mobile Access Network Gateways?
> Mobile Routers?
> Mobile Nodes?
> Mobile Hosts?
> Mobile unaware nodes?
> Ad Hoc mobile networks?

These are all points I think we need to address.  But can
we focus on the Problem Statement & the Requirements?
I see no reason to be consistantly beating on MIP until
we have done the first two things.

John


From owner-seamoby@diameter.org  Thu Mar 15 12:16:54 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA03570
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Mar 2001 12:16:53 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2FGikn04673
	for seamoby-list; Thu, 15 Mar 2001 08:44:46 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2FGiiF04668
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 08:44:44 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA17876;
	Thu, 15 Mar 2001 07:52:58 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA08976;
	Thu, 15 Mar 2001 07:52:57 -0800 (PST)
Received: from sunray-mpke (sunray-mpke.Eng.Sun.COM [129.146.6.32])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id HAA09030;
	Thu, 15 Mar 2001 07:52:56 -0800 (PST)
Date: Thu, 15 Mar 2001 07:52:57 -0800 (PST)
From: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Pat Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: RE: [seamoby] Micro-mobility Issues for IESG to Consider
To: john.loughney@nokia.com
Cc: kulwinder.atwal@zucotto.com, Phil_Neumiller@3Com.com, seamoby@diameter.org
In-Reply-To: "Your message with ID" <01D91AFB08B6D211BFD00008C7EABAE10680ABE1@eseis04nok>
Message-ID: <Roam.SIMC.2.0.6.984671577.11357.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> Kulwinder,
> 
> At the end of the day, we need to have a strong problem statement.
> The current draft is good, but can be better.  We need another
> version, which should be done ASAP after the Minneapolis meeting.
> 
> I do think that, independently of the problem statement, individuals
> could be sending their individual requirements for MM.  

Could not have said it better myself.

PatC



From owner-seamoby@diameter.org  Thu Mar 15 12:18:01 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA03589
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Mar 2001 12:18:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2FGH0A04602
	for seamoby-list; Thu, 15 Mar 2001 08:17:00 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2FGGwF04597
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 08:16:58 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2FFNtd20429;
	Thu, 15 Mar 2001 07:23:55 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f2FFPLE12319;
	Thu, 15 Mar 2001 07:25:21 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A10.0054B30A ; Thu, 15 Mar 2001 07:25:08 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: "David Martin" <dmartin@kreative.net>
cc: seamoby@diameter.org
Message-ID: <88256A10.0054A9B2.00@hqoutbound.ops.3com.com>
Date: Thu, 15 Mar 2001 09:22:46 -0600
Subject: Re: [seamoby] Micro-mobility Issues for IESG to Consider
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk



This really great information Dave.  May I ask your source?  Also, could I ask
for some more information from you?  Like do you have any performance stats
perhaps?

Thanks,

Phil Neumiller




From owner-seamoby@diameter.org  Thu Mar 15 12:31:22 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA03913
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Mar 2001 12:31:21 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2FGoIZ04697
	for seamoby-list; Thu, 15 Mar 2001 08:50:18 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from atlsnmx1.nextel.com (atlsnmx1.nextel.com [167.20.198.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2FGoGF04692
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 08:50:16 -0800
Received: from atlntgw02.nextel.com (atlntgw02.nextel.com [10.8.79.186])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id KAA27618;
	Thu, 15 Mar 2001 10:58:32 -0500 (EST)
Received: by atlntgw02.nextel.com with Internet Mail Service (5.5.2650.21)
	id <GV38MHRH>; Thu, 15 Mar 2001 10:57:17 -0500
Message-ID: <020A5EC56F3FD411B5230008C716D085868495@nhqntex01.nextel.com>
From: "Martin, David P" <David.P.Martin@nextel.com>
To: "'Phil_Neumiller@3com.com'" <Phil_Neumiller@3Com.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Mobile IP Commercially Deployed (was .. Micro-mobil
	ity Issues for IESG to Consider)
Date: Thu, 15 Mar 2001 10:52:02 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

I work about 10 feet from the team that do the design, configuration and
testing of the Nextel Mobile IP network.

We have performance stats, I'll have to see what we can share.  I can tell
you that the user experience of using Mobile IP on any type of real time
service (i.e. VoIP) would be painful given the existing Mobile IP
implementation.

Also, we use Motorola/Cisco equipment, not 3Com (nothing against 3com ... we
just don't have their equipment).

> -----Original Message-----
> From: Phil_Neumiller@3com.com [mailto:Phil_Neumiller@3com.com]
> Sent: Thursday, March 15, 2001 10:23 AM
> To: David Martin
> Cc: seamoby@diameter.org
> Subject: Re: [seamoby] Micro-mobility Issues for IESG to Consider
> 
> 
> 
> 
> This really great information Dave.  May I ask your source?  
> Also, could I ask
> for some more information from you?  Like do you have any 
> performance stats
> perhaps?
> 
> Thanks,
> 
> Phil Neumiller
> 
> 


From owner-seamoby@diameter.org  Thu Mar 15 12:58:09 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04532
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Mar 2001 12:58:09 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2FGgrh04664
	for seamoby-list; Thu, 15 Mar 2001 08:42:53 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2FGgjF04659
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 08:42:45 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2FFnWd24414;
	Thu, 15 Mar 2001 07:49:32 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f2FFowE16007;
	Thu, 15 Mar 2001 07:50:58 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A10.00570DEA ; Thu, 15 Mar 2001 07:50:51 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: seamoby@diameter.org
cc: kulwinder.atwal@zucotto.com, charliep@iprg.nokia.com, dblair@cisco.com
Message-ID: <88256A10.00570C59.00@hqoutbound.ops.3com.com>
Date: Thu, 15 Mar 2001 09:49:37 -0600
Subject: [seamoby] The increasing importance of MANET and Micromobility
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk



Some more comments on justication of Micro-mobility.

I think it is important to hunt down actual deployment
statistics on MIP.  I have contacted some old collegues
at Motorola that work in the performance analysis groups
for the worlds largest MIP deployments which are Nextel
and Sprint.  We now know that Nextel is setup as
follows (thanks to Dave Martin of Kreative) and we will
continue to gather more performance stats:

Nextel has ~20 HA and ~200 FAs.  They are used to support
a large percentage of the 7 million subscribers (all data
subscribers). *All* of Nextel's data subscribers are
Mobile IP clients, *All* do binding updates several
times a day (based mostly on mobility).  HA-FA Tunnells
are built nation-wide.  In short, Nextel has had Mobile
IP fully deployed and operational for almost a year.

Motorola has packet latency numbers from end-to-end from
the MN through 3COM equipment through MOT equipment etc.
Due to the extremely sensitive nature of this information
I will not be able to post it directly to the list.

However, I will be able deduce whether there is even a
need for a fast handoff  based on the type workload
the mobiles have currently.  From what I can tell already
there is no such need for a fast handoff due to the low
bit rate provided by the 2G types of devices deployed.

Now when 3G comes along and there will be multi-media work
loads and VOIP applications I agree that it is a different
ball game, but not quite see additional comments below.

Now on the other hand.  In the HOME MARKET.  We have
another phenomena occuring at least in the US.  We have an
explosian of cheap wireless devices.  Also we have a trend
toward wireless broadband infrastructure deployment in the
last mile.  This introduces many new types of mobility
scenarios that are much better suited for micromobility
and put a huge demand on an RFC for a MANET protocol.

IN SUMMARY:
I see an incredible need for AODV to go to RFC ASAP.
I think micro-mobility has a more pressing impirical market
need than fast handoff now.  Fast handoff is not even
needed for the first version of 3G in 2002 since it will
be handled by the RANS themselves.  Fast handoff wont
likely be needed until 2004 by the cellular guys.  So
micro-mobility in summary is much more important than
fast handoff.

Thanks,

Phil



THE REAL DEMAND IS FOR an RFC for AD HOC NETWORKING NOW!


Sent by:  john.loughney@nokia.com
To:  kulwinder.atwal@zucotto.com, Phil Neumiller/MW/US/3Com,
seamoby@diameter.org
cc:
Subject:  RE: [seamoby] Micro-mobility Issues for IESG to Consider



Kulwinder,

At the end of the day, we need to have a strong problem statement.
The current draft is good, but can be better.  We need another
version, which should be done ASAP after the Minneapolis meeting.

I do think that, independently of the problem statement, individuals
could be sending their individual requirements for MM.

IMO, I think the process has been working fine - the biggest hiccup
was when someone sent attacking MIP & CC:ing the MIP list.  I don't
think that is a constructive approach ...


> The real problem with MIP, as stated by many others, is deployment
> flexibility across various wireless access technologies.
>
> What I would like to see MIP proponents focus on discussing is:
>
> What are the merits of IP mobility protocol re-use across various core
> network and mobile access network technologies?
>
> Can MIP work effectively on and with:
>
> Mobile Access Network Gateways?
> Mobile Routers?
> Mobile Nodes?
> Mobile Hosts?
> Mobile unaware nodes?
> Ad Hoc mobile networks?

These are all points I think we need to address.  But can
we focus on the Problem Statement & the Requirements?
I see no reason to be consistantly beating on MIP until
we have done the first two things.

John





From owner-seamoby@diameter.org  Thu Mar 15 13:33:18 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA05100
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Mar 2001 13:33:17 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2FHppS04878
	for seamoby-list; Thu, 15 Mar 2001 09:51:51 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2FHpnF04873
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 09:51:49 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4SQP0>; Thu, 15 Mar 2001 12:00:17 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A7C@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Charles E. Perkins'" <charliep@iprg.nokia.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Micro-mobility Issues for IESG to Consider
Date: Thu, 15 Mar 2001 12:00:15 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Charles E. Perkins [mailto:charliep@iprg.nokia.com]
> Sent: Thursday, March 15, 2001 11:27 AM
> To: Kulwinder Atwal
> Cc: seamoby@diameter.org
> Subject: Re: [seamoby] Micro-mobility Issues for IESG to Consider
> 
> 
> 
> Hello,
> 
> I guess I count as a Mobile IP proponent, insofar as I want
> to be sure that the "micromobility" (still dislike that term)
> proposal should work well with Mobile IP.
> 

> The merits are those of Mobile IP, which are supposed to include:
> - seamless mobility, except that now that term is becoming
>   more closely associated with the [seamoby] working group
> - "always-on" operation for a node
> - global reachability for mobile nodes with global IP addresses
> 
> If you don't care about "always on", or global IP addressability,
> then you can do with less, but I always wonder about why.
> 

It depends on what is meant by 'always on'.  
Is it full power mode with fast response?
Is it low Power mode with fast response?
Is it low power mode with slow response?

How long can a device take to wake-up and respond to still be considered
'always on'?

> 
> Charlie P.
> 


From owner-seamoby@diameter.org  Thu Mar 15 13:34:37 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA05139
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Mar 2001 13:34:36 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2FHJD304789
	for seamoby-list; Thu, 15 Mar 2001 09:19:13 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2FHJBF04784
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 09:19:11 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id IAA09424;
	Thu, 15 Mar 2001 08:27:34 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f2FGRV107659;
	Thu, 15 Mar 2001 08:27:31 -0800
X-mProtect:  Thu, 15 Mar 2001 08:27:31 -0800 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdnXMWtf; Thu, 15 Mar 2001 08:27:21 PST
Message-ID: <3AB0ED6B.A91FF32@iprg.nokia.com>
Date: Thu, 15 Mar 2001 08:27:23 -0800
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
CC: seamoby@diameter.org
Subject: Re: [seamoby] Micro-mobility Issues for IESG to Consider
References: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A79@NEPTUNE.zucotto.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello,

I guess I count as a Mobile IP proponent, insofar as I want
to be sure that the "micromobility" (still dislike that term)
proposal should work well with Mobile IP.

> Is MIP willing to wait for a MM with lab experience?
> Do you have preformance numbers for MIP across the Internet, or only on
> private 3GPP2 IP networks?
> 
> > I don't see any parallels between the
> > two (useful parallels, at least).
> 
             > Useful parallels:
             > 
definition?  > Access          Core
disagree     > LAN             WAN
definition   > Seamoby         MIP
disagree     > Private         Service Provider
disagree     > Low Cost        Fault Tolerant Redundancy
definition?  > Small           Big

I put some spaces in there so it would look O.K. on my screen.
I disagree with your classifications.   For instance, Mobile IP
can work in a private deployment as well as with a service
provider.  And, the intention was to make Mobile IP a small
protocol.  There are a few bells and whistles, but they could
be removed as the protocol progresses from Proposed Standard
to Draft Standard, depending on working group consensus and
experience.  I'd like to find out if you have any analysis to
support these assertions.  Of course, we'd all like protocols
to be smaller, lower cost, and all that.  Unfortunately, one
person's bell is another person's crucial part of the protocol
sometimes.  I don't believe that the evidence presented so far
proves that [seamoby] will be immune to that phenomenon.

> We can continue to discuss details like which is faster, but the real issue
> is structural.
> Do we really want to write another Core mobility protocol to work with other
> wireless access technologies?
> Or, promote protocol re-use by requiring that all IP mobility solutions
> adhere to the Access/Core model?

Maybe an explicit statement of the Access/Core model would be useful
to be able to understand your point.  IP itself does not require nor
even suggest such a model.  [seamoby-mm] might, by the pure device of
stating that it serves a domain of applicability called an "access
network".  Or maybe you mean the Access Network to be the same thing
that is called a "Local Mobility Domain" in the draft.
 
> The real problem with MIP, as stated by many others, is deployment
> flexibility across various wireless access technologies.

Here is where I am really surprised.  Mobile IP is suitable for various
wireless access technologies.  I almost said all, but then I remembered
that I haven't done them all myself -- only quite a few.

> What I would like to see MIP proponents focus on discussing is:
> 
> What are the merits of IP mobility protocol re-use across various core
> network and mobile access network technologies?

The merits are those of Mobile IP, which are supposed to include:
- seamless mobility, except that now that term is becoming
  more closely associated with the [seamoby] working group
- "always-on" operation for a node
- global reachability for mobile nodes with global IP addresses

If you don't care about "always on", or global IP addressability,
then you can do with less, but I always wonder about why.

> Can MIP work effectively on and with:
> 
> Mobile Access Network Gateways?

Why not?  I would say yes.  Do they offer care-of addresses?

> Mobile Routers?

Here the answer is "yes", depending on how you would like to
inject routes into rest of the Internet for the mobile portion
which is to be served by the mobile router.

> Mobile Nodes?

Yes -- but why is this different than the last question?

> Mobile Hosts?

Yes -- but maybe you weren't seriously asking this question...

> Mobile unaware nodes?

No.

> Ad Hoc mobile networks?

No.

> What is the clear division of labour between the core mobility protocol MIP
> and access mobility protocols?

Mobile IP wants to deal with changing IP addresses, and wants the home
agent to find out about changed care-of addresses.  Keep the IP address
the same, and Mobile IP doesn't have to know.  If it's viewed as too
expensive to update the home agent, then one might find ways to keep
the care-of address known by the home agent to be the same.  Thus, we
have [seamoby], apparently for the case when the care-of address just
doesn't change at all, and various other proposals for localizing the
reporting requirements for changed care-of addresses.

That seems clear to me.  Is it unclear?

> These questions are no longer esoteric, but will require real answers from
> MIP proponents next week.

How about now?

Also, if I may ask, were they actually questions or part of an ultimatum?


Charlie P.


From owner-seamoby@diameter.org  Thu Mar 15 13:54:43 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA05412
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Mar 2001 13:54:42 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2FI1Yn04925
	for seamoby-list; Thu, 15 Mar 2001 10:01:34 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2FI1WF04920
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 10:01:32 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA13318
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 09:09:55 -0800 (PST)
X-Delivered-For: <seamoby@diameter.org>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f2FH9rb25389
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 09:09:53 -0800
X-mProtect:  Thu, 15 Mar 2001 09:09:53 -0800 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdu2jf4H; Thu, 15 Mar 2001 09:09:44 PST
Message-ID: <3AB0F759.10ECC91@iprg.nokia.com>
Date: Thu, 15 Mar 2001 09:09:45 -0800
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: seamoby@diameter.org
Subject: Re: [seamoby] Micro-mobility Issues for IESG to Consider
References: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A7C@NEPTUNE.zucotto.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello,

> > If you don't care about "always on", or global IP addressability,
> > then you can do with less, but I always wonder about why.
> >
> 
> It depends on what is meant by 'always on'.
> Is it full power mode with fast response?
> Is it low Power mode with fast response?
> Is it low power mode with slow response?
> 
> How long can a device take to wake-up and respond to still be considered
> 'always on'?

This should properly be considered as a problem area outside
the domain of Mobile IP.  Mobile IP is a routing area protocol.
It was not designed to be used as a power control mechanism,
nor a paging protocol.  Mobile IP does not specifically handle
fast/slow response considerations; for IPv4, it only manages the
details needed for tunnel establishment to a care-of address.

On the other hand, I think that additional control mechanisms
can be built for the features, that still work well with Mobile
IP, but are separate from Mobile IP.  If interactions need to
be designed, that would be a good topic for discussion, once the
interactions are identified.

Regards,
Charlie P.


From owner-seamoby@diameter.org  Thu Mar 15 14:17:15 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA05935
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Mar 2001 14:17:15 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2FHqan04887
	for seamoby-list; Thu, 15 Mar 2001 09:52:37 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2FHqYF04882
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 09:52:34 -0800
Received: from msubbara-u10.cisco.com (msubbara-u10.cisco.com [64.102.66.20])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id JAA01080;
	Thu, 15 Mar 2001 09:01:02 -0800 (PST)
Received: (msubbara@localhost) by msubbara-u10.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id MAA22360; Thu, 15 Mar 2001 12:00:50 -0500 (EST)
Date: Thu, 15 Mar 2001 12:00:50 -0500
From: Madhavi Subbarao <msubbara@cisco.com>
To: Phil_Neumiller@3Com.com
Cc: seamoby@diameter.org
Subject: [seamoby] Re: seamoby] Micro-mobility Issues for IESG to Consider
Message-ID: <20010315120050.A22356@cisco.com>
References: <88256A0F.0077708D.00@hqoutbound.ops.3com.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <88256A0F.0077708D.00@hqoutbound.ops.3com.com>; from Phil_Neumiller@3Com.com on Wed, Mar 14, 2001 at 03:41:05PM -0600
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Phil,

On Wed, Mar 14, 2001 at 03:41:05PM -0600, Phil_Neumiller@3Com.com wrote:
> 
> 
> 
> Hi John,
> 
> Comments are below.
> 
> 
> 
> 
> >Phil,
> >
> >One comment:
> 
> >>                 B).  The justification for micro-mobility is
> >>                  precisely the same
> >>                       as that used for fast handoff (i.e. at
> >>                  this point stricly
> >>                       an emotional appeal since no hard data
> >>                  currently exists).
> 
> >MIP has been deployed, at least in lab situations, by many
> >companies.
> 
> 1).  I believe in the world, the US based carrier Nextel has
>      the largest Mobile-IP installed base.  They are using
>      Motorola/3Com equipment.

Actually, the HA and base network is all Cisco equipment. 
The FA is a Motorola Computing Group VME based chassis running
Motorola code on PowerPC chips.  No 3Com equipment (as far as we
know).

> 
> 2).  The second largest installation is also in the US and it
>      is Sprint, also a combination of Motorola/3Com equipment.
> 
> [If somebody has other data please correct me]
> 
> 3).  In both cases, I believe their metropolitan subnets are just
>      big subnets, i.e. the subscriber's can not roam off the
>      edge, i.e. there is never a mobile IP handoff!  So these
>      are not very good testbeds.  [again please correct me if
>      I am wrong]  I would cc Phil Roberts to get the data but
>      he has just left Motorola!

According to Stefan Raab (used to be at Nextel, now at Cisco),
the markets are divided into up to 4 foreign agent domains.
A large percentage of users hand-off several times a day in almost
every market. There are also plenty of inter-market hand-offs. People
can actually drive most of the east coast on route 95 and never lose 
coverage. 

Thanks,
Madhavi

> 
> 
> >  Fast Handoff is an enhancement to an existing
> > protocol based upon experience.  MM isn't really in the
> > same league (yet).  I don't see any parallels between the
> > two (useful parallels, at least).  If we want MM, then
> > we need to justify it on its own merits.
> >
> > John
> 
> 4).  It is clearly not based on customer installed base
>      experience John, at least for the largest installed
>      bases in the world.
> 
> 5).  Regarding parallels.  IMO they both do the same thing
>      in the requirements sense NOT in the PROTOCOL SENSE.
>      They both reduce or stop signallignalling upstream to
>      the home for or foreign agent, they both make handovers
>      qualitatively more seamless (nobody has numbers!).
> 
> So I disagree.  I say it is just as justified as Fast handover
> and presents a viable alternative to fast handover.  In fact
> it presents a solution for implementations where there is
> no mobile IP infrastructure in place like perhaps in home
> networking situations, camping trips, remote automobile
> scenarios, dozens of other adhoc situations.
> 
> Thanks,
> 
> Phil Neumiller
> 
> 
> 
> 
> 


From owner-seamoby@diameter.org  Thu Mar 15 19:25:50 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA10971
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Mar 2001 19:25:49 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2G02wr06094
	for seamoby-list; Thu, 15 Mar 2001 16:02:58 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from c007.snv.cp.net (c007-h015.c007.snv.cp.net [209.228.33.222])
	by charizard.diameter.org (8.11.3/8.11.3) with SMTP id f2G02uF06089
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 16:02:56 -0800
Received: (cpmta 20043 invoked from network); 15 Mar 2001 15:11:12 -0800
Received: from dsl-64-193-0-129.telocity.com (HELO PhilsSony) (64.193.0.129)
  by smtp.telocity.com (209.228.33.222) with SMTP; 15 Mar 2001 15:11:12 -0800
X-Sent: 15 Mar 2001 23:11:12 GMT
Message-ID: <003501c0ada5$73e3ec60$6801a8c0@mw.3com.com>
From: "Phillip Neumiller" <neumiller@telocity.com>
To: "Martin, David P" <David.P.Martin@nextel.com>,
        "'Phil_Neumiller@3com.com'" <Phil_Neumiller@3Com.com>
Cc: <seamoby@diameter.org>
References: <020A5EC56F3FD411B5230008C716D085868495@nhqntex01.nextel.com>
Subject: Re: [seamoby] Mobile IP Commercially Deployed 
Date: Thu, 15 Mar 2001 17:12:47 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Yes, Nextel = Mot + Crisco :-)
The only "sanitized for viewing" data I have seen is Mot+3Com IWUs in the
Sprint
PCS IS95B System Mobile IP deployments.  The iDen systems do indeed use
Cisco routers for the HAs and FAs.  Note that iDen MNs uses GSM-like voice
channel no VOIP of course.  We will continue to collect data and then
summarize.
There seems to be some large CDMA mobile IP deployments in Japan that are
growing nicely.



From owner-seamoby@diameter.org  Thu Mar 15 20:16:51 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA11685
	for <seamoby-archive@odin.ietf.org>; Thu, 15 Mar 2001 20:16:51 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2G0vI706283
	for seamoby-list; Thu, 15 Mar 2001 16:57:18 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from atlsnmx1.nextel.com (atlsnmx1.nextel.com [167.20.198.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2G0vFF06278
	for <seamoby@diameter.org>; Thu, 15 Mar 2001 16:57:15 -0800
Received: from atlntgw02.nextel.com (atlntgw02.nextel.com [10.8.79.186])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id TAA05742;
	Thu, 15 Mar 2001 19:05:31 -0500 (EST)
Received: by atlntgw02.nextel.com with Internet Mail Service (5.5.2650.21)
	id <GV38MX3G>; Thu, 15 Mar 2001 19:06:03 -0500
Message-ID: <020A5EC56F3FD411B5230008C716D0858684A4@nhqntex01.nextel.com>
From: "Martin, David P" <David.P.Martin@nextel.com>
To: "'Phillip Neumiller'" <neumiller@telocity.com>,
        "Martin, David P"
	 <David.P.Martin@nextel.com>,
        "'Phil_Neumiller@3com.com'"
	 <Phil_Neumiller@3Com.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Mobile IP Commercially Deployed 
Date: Thu, 15 Mar 2001 19:00:44 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> The iDen systems do 
> indeed use
> Cisco routers for the HAs and FAs.  Note that iDen MNs uses 
> GSM-like voice
> channel no VOIP of course.

iDEN *does* have packet voice, and it is a substantial amount of the voice
traffic.  This voice traffic *does not* utilize the Mobile IP network, and
does not use any IP standard for mobility.


From owner-seamoby@diameter.org  Fri Mar 16 07:21:24 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA02367
	for <seamoby-archive@odin.ietf.org>; Fri, 16 Mar 2001 07:21:23 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2GBCj508002
	for seamoby-list; Fri, 16 Mar 2001 03:12:45 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2GBBvF07997
	for <seamoby@diameter.org>; Fri, 16 Mar 2001 03:11:57 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2GAIud13997;
	Fri, 16 Mar 2001 02:18:56 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f2GAKME00103;
	Fri, 16 Mar 2001 02:20:22 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A11.0038C9BD ; Fri, 16 Mar 2001 02:20:16 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: "Martin, David P" <David.P.Martin@nextel.com>
cc: "'Phillip Neumiller'" <neumiller@telocity.com>,
        "Martin, David P" <David.P.Martin@nextel.com>, seamoby@diameter.org
Message-ID: <88256A11.0038C872.00@hqoutbound.ops.3com.com>
Date: Fri, 16 Mar 2001 04:19:15 -0600
Subject: RE: [seamoby] Mobile IP Commercially Deployed
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk



We are quite off subject.  I worked at Mot many years. ;-)  It uses
packet (buffered-store-and-forward) for the dispatch mode of communication
but regular olde GSM like stuff form mobile to land calls.
We never considered dispatch issues the paging design team here
in Sea
Its sort of like instant messaging on steroids!!!



iDEN *does* have packet voice, and it is a substantial amount of the voice
traffic.  This voice traffic *does not* utilize the Mobile IP network, and
does not use any IP standard for mobility.






From owner-seamoby@diameter.org  Fri Mar 16 19:29:27 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA16242
	for <seamoby-archive@odin.ietf.org>; Fri, 16 Mar 2001 19:29:26 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2GMgLG10723
	for seamoby-list; Fri, 16 Mar 2001 14:42:21 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2GMgJF10718
	for <seamoby@diameter.org>; Fri, 16 Mar 2001 14:42:19 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA06861
	for <seamoby@diameter.org>; Fri, 16 Mar 2001 13:50:49 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA02985
	for <seamoby@diameter.org>; Fri, 16 Mar 2001 13:50:47 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id NAA23863
	for <seamoby@diameter.org>; Fri, 16 Mar 2001 13:50:47 -0800 (PST)
Message-Id: <200103162150.NAA23863@heliopolis.Eng.Sun.COM>
Date: Fri, 16 Mar 2001 13:50:47 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: [seamoby] Context Transfer for Header Compression State?
To: seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: QOhTxx1jTUi0TgrwHimR1w==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

I recall reading somewhere (maybe an email?) that context transfer
for header compression state would be difficult to do and that it
might take 10-12 packets before the compression context would be
reestablished.

I am trying to track down this reference because one of the issues
in selection of a hierarchical MIP protocol is spectral efficiency,
and I want to make sure I have the reference right.

Can anybody on the CT design team help? Thanx!

		jak



From owner-seamoby@diameter.org  Fri Mar 16 20:56:57 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA17232
	for <seamoby-archive@odin.ietf.org>; Fri, 16 Mar 2001 20:56:57 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2H1Ghb11244
	for seamoby-list; Fri, 16 Mar 2001 17:16:43 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2H1GfF11239
	for <seamoby@diameter.org>; Fri, 16 Mar 2001 17:16:41 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2H0NAd12591;
	Fri, 16 Mar 2001 16:23:10 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f2H0ObQ15285;
	Fri, 16 Mar 2001 16:24:37 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A12.00023DB6 ; Fri, 16 Mar 2001 16:24:28 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
cc: seamoby@diameter.org, mankin@east.isi.edu
Message-ID: <88256A12.00023C21.00@hqoutbound.ops.3com.com>
Date: Fri, 16 Mar 2001 18:23:27 -0600
Subject: [seamoby] Re: [seamoby-paging] Re: Minutes of the teleconference on Wed. 03
	/13
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk




I did post the paging meeting minutes Behcet.   BTW, I am both Phil's :-)
Sorry for the confusion.  The  minutes were posted  to the main SeaMoby list.
I can understand your confusion Behcet.

The following was MY choice which I thought was a good one:

"Design team meeting minutes MUST always be posted to the MAIN
WG list so that the WHOLE WG is CROSS informed regularly."

Bad idea?  Many WG members seem to think so for some reason?  Yet,
none have stepped forward to say why?  Other WG members think it
is a good idea.  Time for a hum?  I don't now.  Up to Pat and Allison or
Scott.

I am CC'ing  this to  Pat and Allison because I am tired of all the whining
directed at me about meeting minutes.  Your mail was not whining Behcet
you were rightfully confused, and I take responsibility for it.  The whining
has occured in the actual teleconferences. I would like the process of design
team minutes to be settled once and for all please.

Thank you,

Phil Neumiller




From owner-seamoby@diameter.org  Fri Mar 16 21:00:47 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA17251
	for <seamoby-archive@odin.ietf.org>; Fri, 16 Mar 2001 21:00:46 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2H1T3M11286
	for seamoby-list; Fri, 16 Mar 2001 17:29:03 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2H1T1F11281
	for <seamoby@diameter.org>; Fri, 16 Mar 2001 17:29:01 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id QAA15668;
	Fri, 16 Mar 2001 16:37:29 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f2H0bRw27638;
	Fri, 16 Mar 2001 16:37:27 -0800
X-mProtect:  Fri, 16 Mar 2001 16:37:27 -0800 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90)
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdPJB9Qw; Fri, 16 Mar 2001 16:37:19 PST
Message-ID: <3AB2B1C0.59E2B600@iprg.nokia.com>
Date: Fri, 16 Mar 2001 16:37:20 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 2.2.6-RELEASE i386)
MIME-Version: 1.0
To: kempf@heliopolis.Eng.Sun.COM
CC: seamoby@diameter.org
Subject: [seamoby] [Fwd: Revised HC Relocation statement]
Content-Type: multipart/mixed; boundary="------------FF6D5DF3F54BC7E1CFBAE39"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This is a multi-part message in MIME format.

--------------FF6D5DF3F54BC7E1CFBAE39
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello James,

here is the posting to CT list that might be of interest to you. 

A deduction from this analysis is that header compression context
initialization is an expensive process in certain links. Thus, there is
a trade-off between the benefit it offers versus how long-lived the flow
is. If you have to do it for web traffic for example, some flow may live
as long as only 20 packets. So, you would have to weigh the overhead
versus the longevity of the flow.

Best Regards,

-Rajeev

--------------FF6D5DF3F54BC7E1CFBAE39
Content-Type: message/rfc822
Content-Disposition: inline

Message-ID: <3A708D5C.33590565@iprg.nokia.com>
Date: Thu, 25 Jan 2001 12:32:28 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 2.2.6-RELEASE i386)
MIME-Version: 1.0
To: seamoby_context@standards.nortelnetworks.com
CC: rajeev@iprg.nokia.com
Subject: Revised HC Relocation statement
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello folks,

following is a revised version. 

PatC, the co-chair: I wish to register a complaint that I can post
messages to this group, but I cannot see them myself! Any positive
action would be appreciated.

Regards,

-Rajeev


Header Compression (HC) Context Relocation
------------------------------------------

Compression of IP and transport layer headers is crucial over
low-bandwidth links in order to achieve efficient utilization of the
link capacity to deliver useful payload to applications. This header
compression involves maintaining state (context) information on the
network
periphery and the terminal and operating according to well-defined
protocol. When terminal mobility is involved, relocation of the
compression context(s) is needed in order to avoid surges in bandwidth
consumption associated with compression context re-establishment, which
causes interruptions to the smooth delivery real-time packets. This
overhead can be avoided, and thus the seamless operation of header
compression facilitated, by a simple transfer of context variables
from an access router's compression engine to that of the terminal's
new access router. 


The following terminology is used in describing the need for header
compression context relocation.

Full Header (FH) packet: Contains the full IP and transport protocol
headers,
plus the HC-specific fields

First Order (FO) [packet]: Contains only those fields that change from
packet to packet (e.g. RTP timestamp), and does not contain fields
that do not change at all.

Second Order (SO): Contains HC-specific header and sequence number. The
rest of the fields are constructed from the sequence number info and
the information maintained by the decompressor.

Problem Statement
-----------------
The motivation for HC context relocation is best understood by
examining the typical header compression operation.

A compressor starts by sending Full Header (FH) packets with HC-specific
headers in them and waits for few of the FHs to be reliably propagated
(e.g., ACK-based or 'n' number of headers transmitted). Note that in
bandwidth-constrained links, the link latency as well as higher error
probabilities could force the transmission of many FHs before confirming
reliable propagation of header information. Similarly, many FO packets
are sent before confirming that transition to the SO state is possible.
This process of "reference state" establishment is expensive. E.g., on a
60 ms cellular link and with 20 ms packetization for voice, it would
take 6 FHs (assuming no errors and dropped packets) to establish the FH
state
that allows transition to FO, and 6 more FOs to establish the
FH+FO reference state that allows transition to SO state. The total
overhead is thus 240 ms plus the processing overhead associated with
the header compression operation. Perhaps a value of 300 ms may be
deemed typical. Since this context establishment needs to be
done for each unidirectional packet stream, the overhead gets
worse with multiple packets streams belonging to the same mobile node
(approximately 600 ms for bidirectional voice).
When Mobile IPv6 is used with Home Address option, FH = 84 bytes
(excluding HC-specific fields) for a payload of about 20-30 bytes, and
FO could be 8 bytes. In comparison, the overhead is 1 byte when
operating in the SO state. 

The expensive overheads associated with context re-establishment can be
avoided by relocating the appropriate context between access routers.
For each type of compression mechanism used (e.g.,IPv6/UDP/RTP, IPv6
only, IPv6/TCP wtc), a Compression Profile Type (CPT) identifies the
particular type, and defines the state variables. Thus, the combination
of CPT, and the associated state variables (along with a suitable
identifier) constitutes the context for transfer purpose. This transfer
(presumably) occurs synchronously with handover signaling associated
with terminal mobility.

--------------FF6D5DF3F54BC7E1CFBAE39--



From owner-seamoby@diameter.org  Fri Mar 16 21:03:23 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA17273
	for <seamoby-archive@odin.ietf.org>; Fri, 16 Mar 2001 21:03:22 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2H1OfA11271
	for seamoby-list; Fri, 16 Mar 2001 17:24:41 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2H1OdF11266;
	Fri, 16 Mar 2001 17:24:39 -0800
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id SAA14964;
	Fri, 16 Mar 2001 18:33:11 -0600 (CST)
Received: from usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id f2H0XA229701;
	Fri, 16 Mar 2001 18:33:10 -0600 (CST)
Message-ID: <3AB2A29B.EA9D5026@usa.alcatel.com>
Date: Fri, 16 Mar 2001 18:32:43 -0500
From: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD BDPjm-Sony3  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Phil_Neumiller@3Com.com
CC: seamoby@diameter.org, seamoby-paging@diameter.org
Subject: [seamoby] Re: [seamoby-paging] Re: Minutes of the teleconference on Wed. 03/13
References: <88256A12.00023C21.00@hqoutbound.ops.3com.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Phil, my apologies. The problem is that I do not receive the mails sent to the
main list, although I thought that I had registered to the main mailing list. I
receive seamoby-mm and seamoby-paging posts.


Phil_Neumiller@3com.com wrote:

> I did post the paging meeting minutes Behcet.   BTW, I am both Phil's :-)
> Sorry for the confusion.  The  minutes were posted  to the main SeaMoby list.
> I can understand your confusion Behcet.
>
> The following was MY choice which I thought was a good one:
>
> "Design team meeting minutes MUST always be posted to the MAIN
> WG list so that the WHOLE WG is CROSS informed regularly."
>
> Bad idea?  Many WG members seem to think so for some reason?  Yet,
> none have stepped forward to say why?  Other WG members think it
> is a good idea.  Time for a hum?  I don't now.  Up to Pat and Allison or
> Scott.
>
> I am CC'ing  this to  Pat and Allison because I am tired of all the whining
> directed at me about meeting minutes.  Your mail was not whining Behcet
> you were rightfully confused, and I take responsibility for it.  The whining
> has occured in the actual teleconferences. I would like the process of design
> team minutes to be settled once and for all please.
>
> Thank you,
>
> Phil Neumiller

--
Behcet Sarikaya
Network Strategy Group, Mobile Networking Team
Alcatel USA M/S CTO2
1201 E. Campbell Rd.
Richardson, TX 75081-1936 USA
Email: behcet.sarikaya@usa.alcatel.com
Phone: (972) 996-5075 Fax: (972) 996 5174




From owner-seamoby@diameter.org  Sat Mar 17 02:14:14 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA04688
	for <seamoby-archive@odin.ietf.org>; Sat, 17 Mar 2001 02:14:13 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2H6nO811985
	for seamoby-list; Fri, 16 Mar 2001 22:49:24 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2H6nLF11980
	for <seamoby@cdma-2000.org>; Fri, 16 Mar 2001 22:49:21 -0800
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2H5w4823776
	for <seamoby@cdma-2000.org>; Sat, 17 Mar 2001 07:58:04 +0200 (EET)
Received: from esebh24nok.ntc.nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T525802709bac158f2417d@esvir04nok.ntc.nokia.com>;
 Sat, 17 Mar 2001 07:57:53 +0200
Received: by esebh24nok with Internet Mail Service (5.5.2652.78)
	id <G8C7AC0X>; Sat, 17 Mar 2001 07:57:53 +0200
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE107101B23@eseis04nok>
From: john.loughney@nokia.com
To: Sharif.Shahrier@interdigital.com
Cc: seamoby@cdma-2000.org
Subject: [seamoby] RE: comments on the micro-mobility problem statement draft
Date: Sat, 17 Mar 2001 07:57:52 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Sharif,

> 1.	After the second paragraph in section 1 "introduction", 
> I would like the following paragraph to be added.

I hesitate to add your paragraph - as it I am not sure what
it adds - if you feel that it is important - please give me
supporting reasons.

> 2.	In section 1.1 "scope": I want to add:
> 	Possiblities include:
> 
> 	Mobility where the user's rouable IP address does change.

I'd call this macromobility.  

> 	I also request to add the following:
> 
> 	Where mobility may be:
> 
> 		Within a sub-net.
> 		Across muliple sub-nets.

Agreed.
 
> 3.	In section 1.2 "problem statement add the bullet to the list of
> considerations:
> 
> 		*	Buffering to minimize packet delay/loss during
> handoff.

Buffering I consider part of Context transfer.

> 4.	Section 1.3
> 
> 	In the definition of Local Mobility, it is stated that the "IP
> address must not change".
> 
> 	This has been stated several times throughout the document.
> 
> 	With the permission of the WG, I would like to re-phrase this
> definition. I request that the mandate "IP address must not change" 
> be dropped, so people can persure solutions where the IP address may 
> change, but not frequently. 

This would be the point where MM crosses with macromobility.  

> 	Section 2.1
> 
>       In the "Mandatory" section there is a bulleted item :
> 
> 		*	Use Mobile IP WG protocols for mobility between
> local mobility domains.

These are all updated according to v1 of the draft.
 

>       Section 3
> 
>       Minor changes requested here:
>       Local Mobility will interwork with Context Transfer and Paging.
> 
>       And also add the bullet:
> 
> 		*	paging

Agreed.

John


From owner-seamoby@diameter.org  Sat Mar 17 10:42:00 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA07145
	for <seamoby-archive@odin.ietf.org>; Sat, 17 Mar 2001 10:41:59 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2HEgE613190
	for seamoby-list; Sat, 17 Mar 2001 06:42:14 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from c007.snv.cp.net (c007-h008.c007.snv.cp.net [209.228.33.214])
	by charizard.diameter.org (8.11.3/8.11.3) with SMTP id f2HEgCF13185
	for <seamoby@diameter.org>; Sat, 17 Mar 2001 06:42:12 -0800
Received: (cpmta 4048 invoked from network); 17 Mar 2001 05:50:41 -0800
Received: from dsl-64-193-0-129.telocity.com (HELO PhilsSony) (64.193.0.129)
  by smtp.telocity.com (209.228.33.214) with SMTP; 17 Mar 2001 05:50:41 -0800
X-Sent: 17 Mar 2001 13:50:41 GMT
Message-ID: <002501c0aee9$7c7db500$6801a8c0@mw.3com.com>
From: "Phillip Neumiller" <neumiller@telocity.com>
To: <seamoby@diameter.org>
References: <Roam.SIMC.2.0.6.984693468.2700.pcalhoun@nasnfs> <3AB29482.A2DFC64@usa.alcatel.com>
Subject: [seamoby] ?final? Agenda
Date: Sat, 17 Mar 2001 07:52:19 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The current ?final? agenda for seamoby and all other IETF WGs and BOFs can
be found at: http://www.ietf.org/meetings/agenda_50.html.  I saw someone
ask.
-pdn



From owner-seamoby@diameter.org  Sat Mar 17 12:47:10 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA08049
	for <seamoby-archive@odin.ietf.org>; Sat, 17 Mar 2001 12:47:10 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2HH1iK13469
	for seamoby-list; Sat, 17 Mar 2001 09:01:44 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2HH0RF13464
	for <seamoby@diameter.org>; Sat, 17 Mar 2001 09:00:27 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA06961;
	Sat, 17 Mar 2001 08:09:01 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA06013;
	Sat, 17 Mar 2001 08:09:00 -0800 (PST)
Received: from darius (darius [10.6.84.105])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id IAA03809;
	Sat, 17 Mar 2001 08:08:59 -0800 (PST)
Date: Sat, 17 Mar 2001 08:08:58 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: Re: [seamoby] ?final? Agenda
To: Phillip Neumiller <neumiller@telocity.com>
Cc: seamoby@diameter.org
In-Reply-To: "Your message with ID" <002501c0aee9$7c7db500$6801a8c0@mw.3com.com>
Message-ID: <Roam.SIMC.2.0.6.984845337.7074.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

Yes, it is the final agenda.

PatC



From owner-seamoby@diameter.org  Sat Mar 17 15:39:05 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA09070
	for <seamoby-archive@odin.ietf.org>; Sat, 17 Mar 2001 15:39:04 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2HKAJB13935
	for seamoby-list; Sat, 17 Mar 2001 12:10:19 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from idcpa4.pa.interdigital.com (idcmail.interdigital.com [12.32.197.142])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2HKAHF13930
	for <seamoby@cdma-2000.org>; Sat, 17 Mar 2001 12:10:17 -0800
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <DLALVF2C>; Sat, 17 Mar 2001 14:17:56 -0500
Message-ID: <A1170612471BD21185B90008C7FA0A0D01F1F79F@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        "Shahrier, Sharif M." <Sharif.Shahrier@interdigital.com>
Cc: seamoby@cdma-2000.org,
        "Shahrier, Sharif M."
	 <Sharif.Shahrier@interdigital.com>
Subject: [seamoby] RE: comments on the micro-mobility problem statement draft
Date: Sat, 17 Mar 2001 14:17:55 -0500
Importance: high
X-Priority: 1
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


JOHN,

-----Original Message-----
From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
Sent: Saturday, March 17, 2001 12:58 AM
To: Sharif.Shahrier@interdigital.com
Cc: seamoby@cdma-2000.org
Subject: RE: comments on the micro-mobility problem statement draft


Hi Sharif,

> 1.	After the second paragraph in section 1 "introduction", 
> I would like the following paragraph to be added.

I hesitate to add your paragraph - as it I am not sure what
it adds - if you feel that it is important - please give me
supporting reasons.

ON SECOND READING, IT IS NOT NECCESSARY TO ADD THE PARAGRAPH.

> 2.	In section 1.1 "scope": I want to add:
> 	Possiblities include:
> 
> 	Mobility where the user's rouable IP address does change.

I'd call this macromobility.  

NO, THIS IS JUST AN IMPLEMENTATION ISSUE. I HAVE DEVELOPED A MICRO-MOBILITY
PROTOCOL, WHICH USES A TWO LEVEL ADDRESSING. (1) TO GET TO THE NEW "AR"
WITHIN THE SAME DOMAIN, (2) LOCAL ADDRESS OF THE "MN". ALTHOUGH, THE LOCAL
ADDRESS OF "MN" STAYS THE SAME, THE "AR" ADDRESS WILL CHANGE DURING HANDOFF,
TO A TOTALLY NEW "AR". NOTE, THAT WE'RE TALKING ABOUT "AR"'S WITHIN THE SAME
ADMINISTRATIVE DOMAIN, AND THAT IS MICRO-MOBILITY.

THIS PROTOCOL INTEGRATES BOTH MICRO-MOBILITY AND ROAMING INTO A SINGLE
PROTOCOL.

I WILL BE PUTTING THIS DRAFT OUT SHORTLY, AND IT WILL BE CLEARER THEN. BUT I
CAN'T SAY ANY MORE TILL THEN.

IT WILL REQUIRE "...user's routable IP address does change" TO BE PUT IN THE
DRAFT, TO ALLOW FOR MY DESIGN, AND POSSIBLY SOME OTHER PEOPLE'S AS WELL.

THAT IS MY REASON FOR THE INCLUSION OF THIS IMPORTANT TEXT.

> 	I also request to add the following:
> 
> 	Where mobility may be:
> 
> 		Within a sub-net.
> 		Across muliple sub-nets.

Agreed.
 
> 3.	In section 1.2 "problem statement add the bullet to the list of
> considerations:
> 
> 		*	Buffering to minimize packet delay/loss during
> handoff.

Buffering I consider part of Context transfer.

OK.

> 4.	Section 1.3
> 
> 	In the definition of Local Mobility, it is stated that the "IP
> address must not change".
> 
> 	This has been stated several times throughout the document.
> 
> 	With the permission of the WG, I would like to re-phrase this
> definition. I request that the mandate "IP address must not change" 
> be dropped, so people can persure solutions where the IP address may 
> change, but not frequently. 

This would be the point where MM crosses with macromobility.  

PLEASE SEE MY REASONS FOR (2) ABOVE.

> 	Section 2.1
> 
>       In the "Mandatory" section there is a bulleted item :
> 
> 		*	Use Mobile IP WG protocols for mobility between
> local mobility domains.

These are all updated according to v1 of the draft.
 

>       Section 3
> 
>       Minor changes requested here:
>       Local Mobility will interwork with Context Transfer and Paging.
> 
>       And also add the bullet:
> 
> 		*	paging

Agreed.

John


From owner-seamoby@diameter.org  Sat Mar 17 15:49:01 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA09184
	for <seamoby-archive@odin.ietf.org>; Sat, 17 Mar 2001 15:49:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2HK9MH13912
	for seamoby-list; Sat, 17 Mar 2001 12:09:22 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2HK9JF13907
	for <seamoby@diameter.org>; Sat, 17 Mar 2001 12:09:19 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA22789;
	Sat, 17 Mar 2001 11:17:46 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA29575;
	Sat, 17 Mar 2001 11:17:45 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id LAA03294;
	Sat, 17 Mar 2001 11:17:45 -0800 (PST)
Message-Id: <200103171917.LAA03294@heliopolis.Eng.Sun.COM>
Date: Sat, 17 Mar 2001 11:17:45 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: Re: [seamoby] Re: [seamoby-paging] Re: Minutes of the teleconference on Wed. 03 /13
To: behcet.sarikaya@usa.alcatel.com, Phil_Neumiller@3Com.com
Cc: seamoby@diameter.org, mankin@east.isi.edu
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: /1rAv7qSbYjU+B/OcX5jIw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Phil,

I think it is a good idea to post (but not cross post) to the main list rather
than just the design team list. Behcet's confusion is understandable because we 
did not announce this policy ahead of time. However, as you point out, it does 
allow the rest of the working group to keep track of the meetings, and to 
chime in if there is anything they have to say.

		jak

>X-Authentication-Warning: charizard.diameter.org: majordomo set sender to 
owner-seamoby@diameter.org using -f
>X-Lotus-FromDomain: 3COM
>From: Phil_Neumiller@3Com.com
>To: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
>cc: seamoby@diameter.org, mankin@east.isi.edu
>Date: Fri, 16 Mar 2001 18:23:27 -0600
>Subject: [seamoby] Re: [seamoby-paging] Re: Minutes of the teleconference on 
Wed. 03 /13
>Mime-Version: 1.0
>Content-Disposition: inline
>
>
>
>
>I did post the paging meeting minutes Behcet.   BTW, I am both Phil's :-)
>Sorry for the confusion.  The  minutes were posted  to the main SeaMoby list.
>I can understand your confusion Behcet.
>
>The following was MY choice which I thought was a good one:
>
>"Design team meeting minutes MUST always be posted to the MAIN
>WG list so that the WHOLE WG is CROSS informed regularly."
>
>Bad idea?  Many WG members seem to think so for some reason?  Yet,
>none have stepped forward to say why?  Other WG members think it
>is a good idea.  Time for a hum?  I don't now.  Up to Pat and Allison or
>Scott.
>
>I am CC'ing  this to  Pat and Allison because I am tired of all the whining
>directed at me about meeting minutes.  Your mail was not whining Behcet
>you were rightfully confused, and I take responsibility for it.  The whining
>has occured in the actual teleconferences. I would like the process of design
>team minutes to be settled once and for all please.
>
>Thank you,
>
>Phil Neumiller
>
>



From owner-seamoby@diameter.org  Mon Mar 19 05:58:14 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA07756
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Mar 2001 05:58:13 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2JAP3q24903
	for seamoby-list; Mon, 19 Mar 2001 02:25:03 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2JAP1F24898
	for <seamoby@cdma-2000.org>; Mon, 19 Mar 2001 02:25:01 -0800
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate.mot.com (motgate 2.1) with ESMTP id CAA21374 for <seamoby@cdma-2000.org>; Mon, 19 Mar 2001 02:33:41 -0700 (MST)]
Received: [from m-il06-r4.mot.com (m-il06-r4.mot.com [129.188.137.196]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id CAA03645 for <seamoby@cdma-2000.org>; Mon, 19 Mar 2001 02:33:40 -0700 (MST)]
Received: from [140.101.173.9] by m-il06-r4.mot.com with ESMTP for seamoby@cdma-2000.org; Mon, 19 Mar 2001 03:33:39 -0600
Received: (from root@localhost)
	by zorglub.crm.mot.com (8.8.8/8.8.8/crm-1.6) id KAA15576
	for seamoby@cdma-2000.org.DELIVER; Mon, 19 Mar 2001 10:33:37 +0100 (MET)
Received: from riri.crm.mot.com.crm.mot.com (riri.crm.mot.com [140.101.173.128])
	by zorglub.crm.mot.com (8.8.8/8.8.8/crm-1.6) with ESMTP id KAA15520;
	Mon, 19 Mar 2001 10:33:35 +0100 (MET)
Cc: seamoby@cdma-2000.org, mobile-ip@sunroof.eng.sun.com
Subject: [seamoby] Re: Who implements MIP?
References: <88256A11.00727F9F.00@hqoutbound.ops.3com.com>
From: Alexandru Petrescu <Alexandru_Petrescu-AAP021@email.mot.com>
Date: 19 Mar 2001 10:33:34 +0100
In-Reply-To: <88256A11.00727F9F.00@hqoutbound.ops.3com.com>
Message-Id: <m3lmq2ays1.fsf@riri.crm.mot.com>
Lines: 53
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
X-MIME-Autoconverted: from quoted-printable to 8bit by charizard.diameter.org id f2JAP1F24899
Sender: owner-seamoby@diameter.org
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by charizard.diameter.org id f2JAP3q24903
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA07756

Phil_Neumiller@3com.com writes:
> There are millions of active subscribers doing MIP handoffs on
> Nextel (US), Sprint (US) and KDD (Japan) systems worldwide.

I maintain a list of publicly-available (simple) mobile ipv6
implementations and I'd like to know more details about the above in
order to add them to my list.

The information in the attached list is gathered by private email, I
purposefully not included url's, use google.

Thank you,

Alex

KAME
-bsd-ish.
-Mobile-IPv6 code from Ericsson.
-draft 09.

INRIA
-has a mipv6 part by Francis Dupont, draft-13.
-has a hmipv6 part by Ludovic Bellier, Claude Castelluccia, based on
 the mipv6 part.

MONARCH
-based on INRIA ipv6 stack.
-1997.
-draft 03.

MICROSOFT RESEARCH
-Windows.
-partial IPv6 mobility support.

NUS (National Univ of Singapore)
-linux.

LANCASTER UNIVERSITY
-linux
-draft-ietf-mobileip-ipv6-05
-Stefan Schmid, sschmid@COMP.LANCS.AC.UK.
-finneyj@exchange.lancs.ac.uk, LandMARK project.

MIPL at hut.fi
-linux 2.4.0
-Sami Kivisaari, Niklas Kämpe, Juha Mynttinen, Toni Nykänen, Henrik
 Petander and Antti Tuominen
-draft-12.

SFC of WIDE
-FreeBSD
-for automotive
-presented at Conectathon March 2001.



From owner-seamoby@diameter.org  Mon Mar 19 12:32:50 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA16279
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Mar 2001 12:32:49 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2JH4Ph26990
	for seamoby-list; Mon, 19 Mar 2001 09:04:25 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2JH4MF26985
	for <seamoby@diameter.org>; Mon, 19 Mar 2001 09:04:22 -0800
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Mon, 19 Mar 2001 11:05:18 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GR4V9RP8>; Mon, 19 Mar 2001 11:05:24 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8E02@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        behcet.sarikaya@usa.alcatel.com, Phil_Neumiller@3Com.com
Cc: seamoby@diameter.org, mankin@east.isi.edu
Subject: RE: [seamoby] Re: [seamoby-paging] Re: Minutes of the teleconfere nce 
         on Wed. 03 /13
Date: Mon, 19 Mar 2001 11:05:12 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0B08E.6142DB70"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0B08E.6142DB70
Content-Type: text/plain;
	charset="ISO-8859-1"

Perhaps I have a unique perception of what a design team is all about.
I have no real problem with posting to the main list, but I do have a
problem with opening the debate too far. Those that want to be part
of the dt can subscribe (if you have any problems, email me direct).

If the wg wants an open discussion of the drafts, then let's dissolve
the design teams. They only exist in order to provide focus so that 
progress can be made. If we start cross posting, and the debate
widens (as has happened in the past), then progress will be slowed.

No matter how well minutes are written, they will not capture the
context of a complete discussion. Statements taken out of context
will often regenerate a debate that has already taken place.
And when you have minutes full of personal opinion (with apologies to 
Phil - he did warn us), then there is an even greater risk. 

PLEASE NOTE: I am not saying that the discussions should be closed,
I am simply saying that the dts have a specific purpose, and if the wg
does not value that purpose, then let's dissolve the dts and return
to the main list.

Gary

> -----Original Message-----
> From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
> Sent: Saturday, March 17, 2001 2:18 PM
> To: behcet.sarikaya@usa.alcatel.com; Phil_Neumiller@3Com.com
> Cc: seamoby@diameter.org; mankin@east.isi.edu
> Subject: Re: [seamoby] Re: [seamoby-paging] Re: Minutes of the
> teleconference on Wed. 03 /13
> 
> 
> Phil,
> 
> I think it is a good idea to post (but not cross post) to the 
> main list rather
> than just the design team list. Behcet's confusion is 
> understandable because we 
> did not announce this policy ahead of time. However, as you 
> point out, it does 
> allow the rest of the working group to keep track of the 
> meetings, and to 
> chime in if there is anything they have to say.
> 
> 		jak
> 
> >X-Authentication-Warning: charizard.diameter.org: majordomo 
> set sender to 
> owner-seamoby@diameter.org using -f
> >X-Lotus-FromDomain: 3COM
> >From: Phil_Neumiller@3Com.com
> >To: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
> >cc: seamoby@diameter.org, mankin@east.isi.edu
> >Date: Fri, 16 Mar 2001 18:23:27 -0600
> >Subject: [seamoby] Re: [seamoby-paging] Re: Minutes of the 
> teleconference on 
> Wed. 03 /13
> >Mime-Version: 1.0
> >Content-Disposition: inline
> >
> >
> >
> >
> >I did post the paging meeting minutes Behcet.   BTW, I am 
> both Phil's :-)
> >Sorry for the confusion.  The  minutes were posted  to the 
> main SeaMoby list.
> >I can understand your confusion Behcet.
> >
> >The following was MY choice which I thought was a good one:
> >
> >"Design team meeting minutes MUST always be posted to the MAIN
> >WG list so that the WHOLE WG is CROSS informed regularly."
> >
> >Bad idea?  Many WG members seem to think so for some reason?  Yet,
> >none have stepped forward to say why?  Other WG members think it
> >is a good idea.  Time for a hum?  I don't now.  Up to Pat 
> and Allison or
> >Scott.
> >
> >I am CC'ing  this to  Pat and Allison because I am tired of 
> all the whining
> >directed at me about meeting minutes.  Your mail was not 
> whining Behcet
> >you were rightfully confused, and I take responsibility for 
> it.  The whining
> >has occured in the actual teleconferences. I would like the 
> process of design
> >team minutes to be settled once and for all please.
> >
> >Thank you,
> >
> >Phil Neumiller
> >
> >
> 
> 

------_=_NextPart_001_01C0B08E.6142DB70
Content-Type: text/html;
	charset="ISO-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>RE: [seamoby] Re: [seamoby-paging] Re: Minutes of the teleconference  on Wed. 03 /13</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Perhaps I have a unique perception of what a design team is all about.</FONT>
<BR><FONT SIZE=2>I have no real problem with posting to the main list, but I do have a</FONT>
<BR><FONT SIZE=2>problem with opening the debate too far. Those that want to be part</FONT>
<BR><FONT SIZE=2>of the dt can subscribe (if you have any problems, email me direct).</FONT>
</P>

<P><FONT SIZE=2>If the wg wants an open discussion of the drafts, then let's dissolve</FONT>
<BR><FONT SIZE=2>the design teams. They only exist in order to provide focus so that </FONT>
<BR><FONT SIZE=2>progress can be made. If we start cross posting, and the debate</FONT>
<BR><FONT SIZE=2>widens (as has happened in the past), then progress will be slowed.</FONT>
</P>

<P><FONT SIZE=2>No matter how well minutes are written, they will not capture the</FONT>
<BR><FONT SIZE=2>context of a complete discussion. Statements taken out of context</FONT>
<BR><FONT SIZE=2>will often regenerate a debate that has already taken place.</FONT>
<BR><FONT SIZE=2>And when you have minutes full of personal opinion (with apologies to </FONT>
<BR><FONT SIZE=2>Phil - he did warn us), then there is an even greater risk. </FONT>
</P>

<P><FONT SIZE=2>PLEASE NOTE: I am not saying that the discussions should be closed,</FONT>
<BR><FONT SIZE=2>I am simply saying that the dts have a specific purpose, and if the wg</FONT>
<BR><FONT SIZE=2>does not value that purpose, then let's dissolve the dts and return</FONT>
<BR><FONT SIZE=2>to the main list.</FONT>
</P>

<P><FONT SIZE=2>Gary</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: James Kempf [<A HREF="mailto:kempf@heliopolis.Eng.Sun.COM">mailto:kempf@heliopolis.Eng.Sun.COM</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Saturday, March 17, 2001 2:18 PM</FONT>
<BR><FONT SIZE=2>&gt; To: behcet.sarikaya@usa.alcatel.com; Phil_Neumiller@3Com.com</FONT>
<BR><FONT SIZE=2>&gt; Cc: seamoby@diameter.org; mankin@east.isi.edu</FONT>
<BR><FONT SIZE=2>&gt; Subject: Re: [seamoby] Re: [seamoby-paging] Re: Minutes of the</FONT>
<BR><FONT SIZE=2>&gt; teleconference on Wed. 03 /13</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Phil,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I think it is a good idea to post (but not cross post) to the </FONT>
<BR><FONT SIZE=2>&gt; main list rather</FONT>
<BR><FONT SIZE=2>&gt; than just the design team list. Behcet's confusion is </FONT>
<BR><FONT SIZE=2>&gt; understandable because we </FONT>
<BR><FONT SIZE=2>&gt; did not announce this policy ahead of time. However, as you </FONT>
<BR><FONT SIZE=2>&gt; point out, it does </FONT>
<BR><FONT SIZE=2>&gt; allow the rest of the working group to keep track of the </FONT>
<BR><FONT SIZE=2>&gt; meetings, and to </FONT>
<BR><FONT SIZE=2>&gt; chime in if there is anything they have to say.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jak</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt;X-Authentication-Warning: charizard.diameter.org: majordomo </FONT>
<BR><FONT SIZE=2>&gt; set sender to </FONT>
<BR><FONT SIZE=2>&gt; owner-seamoby@diameter.org using -f</FONT>
<BR><FONT SIZE=2>&gt; &gt;X-Lotus-FromDomain: 3COM</FONT>
<BR><FONT SIZE=2>&gt; &gt;From: Phil_Neumiller@3Com.com</FONT>
<BR><FONT SIZE=2>&gt; &gt;To: Behcet Sarikaya &lt;behcet.sarikaya@usa.alcatel.com&gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;cc: seamoby@diameter.org, mankin@east.isi.edu</FONT>
<BR><FONT SIZE=2>&gt; &gt;Date: Fri, 16 Mar 2001 18:23:27 -0600</FONT>
<BR><FONT SIZE=2>&gt; &gt;Subject: [seamoby] Re: [seamoby-paging] Re: Minutes of the </FONT>
<BR><FONT SIZE=2>&gt; teleconference on </FONT>
<BR><FONT SIZE=2>&gt; Wed. 03 /13</FONT>
<BR><FONT SIZE=2>&gt; &gt;Mime-Version: 1.0</FONT>
<BR><FONT SIZE=2>&gt; &gt;Content-Disposition: inline</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;I did post the paging meeting minutes Behcet.&nbsp;&nbsp; BTW, I am </FONT>
<BR><FONT SIZE=2>&gt; both Phil's :-)</FONT>
<BR><FONT SIZE=2>&gt; &gt;Sorry for the confusion.&nbsp; The&nbsp; minutes were posted&nbsp; to the </FONT>
<BR><FONT SIZE=2>&gt; main SeaMoby list.</FONT>
<BR><FONT SIZE=2>&gt; &gt;I can understand your confusion Behcet.</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;The following was MY choice which I thought was a good one:</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&quot;Design team meeting minutes MUST always be posted to the MAIN</FONT>
<BR><FONT SIZE=2>&gt; &gt;WG list so that the WHOLE WG is CROSS informed regularly.&quot;</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;Bad idea?&nbsp; Many WG members seem to think so for some reason?&nbsp; Yet,</FONT>
<BR><FONT SIZE=2>&gt; &gt;none have stepped forward to say why?&nbsp; Other WG members think it</FONT>
<BR><FONT SIZE=2>&gt; &gt;is a good idea.&nbsp; Time for a hum?&nbsp; I don't now.&nbsp; Up to Pat </FONT>
<BR><FONT SIZE=2>&gt; and Allison or</FONT>
<BR><FONT SIZE=2>&gt; &gt;Scott.</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;I am CC'ing&nbsp; this to&nbsp; Pat and Allison because I am tired of </FONT>
<BR><FONT SIZE=2>&gt; all the whining</FONT>
<BR><FONT SIZE=2>&gt; &gt;directed at me about meeting minutes.&nbsp; Your mail was not </FONT>
<BR><FONT SIZE=2>&gt; whining Behcet</FONT>
<BR><FONT SIZE=2>&gt; &gt;you were rightfully confused, and I take responsibility for </FONT>
<BR><FONT SIZE=2>&gt; it.&nbsp; The whining</FONT>
<BR><FONT SIZE=2>&gt; &gt;has occured in the actual teleconferences. I would like the </FONT>
<BR><FONT SIZE=2>&gt; process of design</FONT>
<BR><FONT SIZE=2>&gt; &gt;team minutes to be settled once and for all please.</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;Thank you,</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;Phil Neumiller</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0B08E.6142DB70--


From owner-seamoby@diameter.org  Mon Mar 19 12:50:05 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA16718
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Mar 2001 12:50:05 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2JH1M126972
	for seamoby-list; Mon, 19 Mar 2001 09:01:22 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2JH1EF26966;
	Mon, 19 Mar 2001 09:01:14 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Mon, 19 Mar 2001 10:53:52 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GR4V9Q08>; Mon, 19 Mar 2001 10:53:58 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8E00@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Behcet Sarikaya'" <behcet.sarikaya@usa.alcatel.com>,
        Phil_Neumiller@3Com.com
Cc: seamoby@diameter.org, seamoby-paging@diameter.org
Subject: RE: [seamoby] Re: [seamoby-paging] Re: Minutes of the teleconfere nce 
         on Wed. 03/13
Date: Mon, 19 Mar 2001 10:53:45 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0B08C.C7AA7140"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0B08C.C7AA7140
Content-Type: text/plain;
	charset="ISO-8859-1"

Behcet:

  I'm not sure which mailing list you are referring to, but you were not
subscribed to seamoby_context. You are now. If you do not want to be
subscribed to seamoby_context, send me email and I will delete you.

  Second, although Phil has clearly stated his desire, it is my view, shared
by Pat Calhoun, that the minutes need only be posted on seamoby_context.
The only "harm" I see in posting to the seamoby list is the spam it
generates,
and the possible confusion that might result from statements taken out of
context (as good as the minutes might be, they never capture the complete
context of the conversation - hmmm, I guess I'm saying the context transfer
is not perfect ;^} ). The design team is, as far as I understand it, a
focussed
effort by a group of contributors, by definition, the intent is to limit the

scope of any conversation in order to make progress, and have the wg at
large
critique the outcome, not the process.

  Having said this, you are certainly welcome to join the context transfer
design
team.

Cheers,
Gary

> -----Original Message-----
> From: Behcet Sarikaya [mailto:behcet.sarikaya@usa.alcatel.com]
> Sent: Friday, March 16, 2001 6:33 PM
> To: Phil_Neumiller@3Com.com
> Cc: seamoby@diameter.org; seamoby-paging@diameter.org
> Subject: [seamoby] Re: [seamoby-paging] Re: Minutes of the
> teleconference on Wed. 03/13
> 
> 
> Phil, my apologies. The problem is that I do not receive the 
> mails sent to the
> main list, although I thought that I had registered to the 
> main mailing list. I
> receive seamoby-mm and seamoby-paging posts.
> 
> 
> Phil_Neumiller@3com.com wrote:
> 
> > I did post the paging meeting minutes Behcet.   BTW, I am 
> both Phil's :-)
> > Sorry for the confusion.  The  minutes were posted  to the 
> main SeaMoby list.
> > I can understand your confusion Behcet.
> >
> > The following was MY choice which I thought was a good one:
> >
> > "Design team meeting minutes MUST always be posted to the MAIN
> > WG list so that the WHOLE WG is CROSS informed regularly."
> >
> > Bad idea?  Many WG members seem to think so for some reason?  Yet,
> > none have stepped forward to say why?  Other WG members think it
> > is a good idea.  Time for a hum?  I don't now.  Up to Pat 
> and Allison or
> > Scott.
> >
> > I am CC'ing  this to  Pat and Allison because I am tired of 
> all the whining
> > directed at me about meeting minutes.  Your mail was not 
> whining Behcet
> > you were rightfully confused, and I take responsibility for 
> it.  The whining
> > has occured in the actual teleconferences. I would like the 
> process of design
> > team minutes to be settled once and for all please.
> >
> > Thank you,
> >
> > Phil Neumiller
> 
> --
> Behcet Sarikaya
> Network Strategy Group, Mobile Networking Team
> Alcatel USA M/S CTO2
> 1201 E. Campbell Rd.
> Richardson, TX 75081-1936 USA
> Email: behcet.sarikaya@usa.alcatel.com
> Phone: (972) 996-5075 Fax: (972) 996 5174
> 
> 
> 

------_=_NextPart_001_01C0B08C.C7AA7140
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: [seamoby] Re: [seamoby-paging] Re: Minutes of the =
teleconference on  Wed. 03/13</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Behcet:</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp; I'm not sure which mailing list you are =
referring to, but you were not</FONT>
<BR><FONT SIZE=3D2>subscribed to seamoby_context. You are now. If you =
do not want to be</FONT>
<BR><FONT SIZE=3D2>subscribed to seamoby_context, send me email and I =
will delete you.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp; Second, although Phil has clearly stated his =
desire, it is my view, shared</FONT>
<BR><FONT SIZE=3D2>by Pat Calhoun, that the minutes need only be posted =
on seamoby_context.</FONT>
<BR><FONT SIZE=3D2>The only &quot;harm&quot; I see in posting to the =
seamoby list is the spam it generates,</FONT>
<BR><FONT SIZE=3D2>and the possible confusion that might result from =
statements taken out of</FONT>
<BR><FONT SIZE=3D2>context (as good as the minutes might be, they never =
capture the complete</FONT>
<BR><FONT SIZE=3D2>context of the conversation - hmmm, I guess I'm =
saying the context transfer</FONT>
<BR><FONT SIZE=3D2>is not perfect ;^} ). The design team is, as far as =
I understand it, a focussed</FONT>
<BR><FONT SIZE=3D2>effort by a group of contributors, by definition, =
the intent is to limit the </FONT>
<BR><FONT SIZE=3D2>scope of any conversation in order to make progress, =
and have the wg at large</FONT>
<BR><FONT SIZE=3D2>critique the outcome, not the process.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp; Having said this, you are certainly welcome to =
join the context transfer design</FONT>
<BR><FONT SIZE=3D2>team.</FONT>
</P>

<P><FONT SIZE=3D2>Cheers,</FONT>
<BR><FONT SIZE=3D2>Gary</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Behcet Sarikaya [<A =
HREF=3D"mailto:behcet.sarikaya@usa.alcatel.com">mailto:behcet.sarikaya@u=
sa.alcatel.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Friday, March 16, 2001 6:33 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Phil_Neumiller@3Com.com</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: seamoby@diameter.org; =
seamoby-paging@diameter.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [seamoby] Re: [seamoby-paging] Re: =
Minutes of the</FONT>
<BR><FONT SIZE=3D2>&gt; teleconference on Wed. 03/13</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Phil, my apologies. The problem is that I do =
not receive the </FONT>
<BR><FONT SIZE=3D2>&gt; mails sent to the</FONT>
<BR><FONT SIZE=3D2>&gt; main list, although I thought that I had =
registered to the </FONT>
<BR><FONT SIZE=3D2>&gt; main mailing list. I</FONT>
<BR><FONT SIZE=3D2>&gt; receive seamoby-mm and seamoby-paging =
posts.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Phil_Neumiller@3com.com wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I did post the paging meeting minutes =
Behcet.&nbsp;&nbsp; BTW, I am </FONT>
<BR><FONT SIZE=3D2>&gt; both Phil's :-)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sorry for the confusion.&nbsp; The&nbsp; =
minutes were posted&nbsp; to the </FONT>
<BR><FONT SIZE=3D2>&gt; main SeaMoby list.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I can understand your confusion =
Behcet.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The following was MY choice which I =
thought was a good one:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &quot;Design team meeting minutes MUST =
always be posted to the MAIN</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; WG list so that the WHOLE WG is CROSS =
informed regularly.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Bad idea?&nbsp; Many WG members seem to =
think so for some reason?&nbsp; Yet,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; none have stepped forward to say =
why?&nbsp; Other WG members think it</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; is a good idea.&nbsp; Time for a =
hum?&nbsp; I don't now.&nbsp; Up to Pat </FONT>
<BR><FONT SIZE=3D2>&gt; and Allison or</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Scott.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I am CC'ing&nbsp; this to&nbsp; Pat and =
Allison because I am tired of </FONT>
<BR><FONT SIZE=3D2>&gt; all the whining</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; directed at me about meeting =
minutes.&nbsp; Your mail was not </FONT>
<BR><FONT SIZE=3D2>&gt; whining Behcet</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; you were rightfully confused, and I take =
responsibility for </FONT>
<BR><FONT SIZE=3D2>&gt; it.&nbsp; The whining</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; has occured in the actual teleconferences. =
I would like the </FONT>
<BR><FONT SIZE=3D2>&gt; process of design</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; team minutes to be settled once and for =
all please.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Thank you,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Phil Neumiller</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; Behcet Sarikaya</FONT>
<BR><FONT SIZE=3D2>&gt; Network Strategy Group, Mobile Networking =
Team</FONT>
<BR><FONT SIZE=3D2>&gt; Alcatel USA M/S CTO2</FONT>
<BR><FONT SIZE=3D2>&gt; 1201 E. Campbell Rd.</FONT>
<BR><FONT SIZE=3D2>&gt; Richardson, TX 75081-1936 USA</FONT>
<BR><FONT SIZE=3D2>&gt; Email: behcet.sarikaya@usa.alcatel.com</FONT>
<BR><FONT SIZE=3D2>&gt; Phone: (972) 996-5075 Fax: (972) 996 =
5174</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0B08C.C7AA7140--


From owner-seamoby@diameter.org  Mon Mar 19 13:21:45 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17368
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Mar 2001 13:21:42 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2JHibG27103
	for seamoby-list; Mon, 19 Mar 2001 09:44:37 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2JHiZF27098
	for <seamoby@diameter.org>; Mon, 19 Mar 2001 09:44:35 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA00870;
	Mon, 19 Mar 2001 08:51:48 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA16415;
	Mon, 19 Mar 2001 08:51:47 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (esun1as-be.Central.Sun.COM [129.147.34.142])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id IAA14794;
	Mon, 19 Mar 2001 08:51:41 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Message-Id: <200103191651.IAA14794@heliopolis.Eng.Sun.COM>
Date: Mon, 19 Mar 2001 10:50:41 -0700
To: "Gary Kenward" <gkenward@nortelnetworks.com>, <Phil_Neumiller@3Com.com>,
        <behcet.sarikaya@usa.alcatel.com>
Cc: <mankin@east.isi.edu>, <seamoby@diameter.org>
Reply-To: <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] Re: [seamoby-paging] Re: Minutes of the teleconfere nce          on Wed. 03 /13
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Gary,

Actually, I don't particularly care one way or the other; however, posting
the minutes to the main list certainly does serve the purpose of keeping
the entire working group updated between IETF meetings. Since the design
teams are trying to move quickly, and since the working group has the
final say on the design, I think it makes some sense to get early feedback.
I agree that opening discussion on details can be counterproductive, but
if we have the convention that anybody who wants to comment on the minutes
should go to the design team list and particpate in the design team
teleconferences, rather than simply posting to the main list,
perhaps that would help.

The only other alternative is to wait until a draft of the document is
done before updating the entire working group, and that tends to be
somewhat more heavy weight. It happens less often, and the working group
members need to read through the entire document, which takes longer. 

Design teams are a relatively recent IETF custom, I'm not sure that
we have all the corners worked out yet.

		jak

>Perhaps I have a unique perception of what a design team is all about.
>I have no real problem with posting to the main list, but I do have a
>problem with opening the debate too far. Those that want to be part
>of the dt can subscribe (if you have any problems, email me direct).
>
>If the wg wants an open discussion of the drafts, then let's dissolve
>the design teams. They only exist in order to provide focus so that 
>progress can be made. If we start cross posting, and the debate
>widens (as has happened in the past), then progress will be slowed.
>
>No matter how well minutes are written, they will not capture the
>context of a complete discussion. Statements taken out of context
>will often regenerate a debate that has already taken place.
>And when you have minutes full of personal opinion (with apologies to 
>Phil - he did warn us), then there is an even greater risk. 
>
>PLEASE NOTE: I am not saying that the discussions should be closed,
>I am simply saying that the dts have a specific purpose, and if the wg
>does not value that purpose, then let's dissolve the dts and return
>to the main list.
>
>Gary
>
>> -----Original Message-----
>> From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
>> Sent: Saturday, March 17, 2001 2:18 PM
>> To: behcet.sarikaya@usa.alcatel.com; Phil_Neumiller@3Com.com
>> Cc: seamoby@diameter.org; mankin@east.isi.edu
>> Subject: Re: [seamoby] Re: [seamoby-paging] Re: Minutes of the
>> teleconference on Wed. 03 /13
>> 
>> 
>> Phil,
>> 
>> I think it is a good idea to post (but not cross post) to the 
>> main list rather
>> than just the design team list. Behcet's confusion is 
>> understandable because we 
>> did not announce this policy ahead of time. However, as you 
>> point out, it does 
>> allow the rest of the working group to keep track of the 
>> meetings, and to 
>> chime in if there is anything they have to say.
>> 
>> 		jak
>> 
>> >X-Authentication-Warning: charizard.diameter.org: majordomo 
>> set sender to 
>> owner-seamoby@diameter.org using -f
>> >X-Lotus-FromDomain: 3COM
>> >From: Phil_Neumiller@3Com.com
>> >To: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
>> >cc: seamoby@diameter.org, mankin@east.isi.edu
>> >Date: Fri, 16 Mar 2001 18:23:27 -0600
>> >Subject: [seamoby] Re: [seamoby-paging] Re: Minutes of the 
>> teleconference on 
>> Wed. 03 /13
>> >Mime-Version: 1.0
>> >Content-Disposition: inline
>> >
>> >
>> >
>> >
>> >I did post the paging meeting minutes Behcet.   BTW, I am 
>> both Phil's :-)
>> >Sorry for the confusion.  The  minutes were posted  to the 
>> main SeaMoby list.
>> >I can understand your confusion Behcet.
>> >
>> >The following was MY choice which I thought was a good one:
>> >
>> >"Design team meeting minutes MUST always be posted to the MAIN
>> >WG list so that the WHOLE WG is CROSS informed regularly."
>> >
>> >Bad idea?  Many WG members seem to think so for some reason?  Yet,
>> >none have stepped forward to say why?  Other WG members think it
>> >is a good idea.  Time for a hum?  I don't now.  Up to Pat 
>> and Allison or
>> >Scott.
>> >
>> >I am CC'ing  this to  Pat and Allison because I am tired of 
>> all the whining
>> >directed at me about meeting minutes.  Your mail was not 
>> whining Behcet
>> >you were rightfully confused, and I take responsibility for 
>> it.  The whining
>> >has occured in the actual teleconferences. I would like the 
>> process of design
>> >team minutes to be settled once and for all please.
>> >
>> >Thank you,
>> >
>> >Phil Neumiller
>> >
>> >
>> 
>> 




From owner-seamoby@diameter.org  Mon Mar 19 14:10:04 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18700
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Mar 2001 14:10:03 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2JHuf327139
	for seamoby-list; Mon, 19 Mar 2001 09:56:41 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from ebene.inrialpes.fr (ebene.inrialpes.fr [194.199.18.70])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2JHucF27134
	for <seamoby@diameter.org>; Mon, 19 Mar 2001 09:56:39 -0800
Received: from pop-serv.inrialpes.fr (pop-serv.inrialpes.fr [194.199.18.66])
	by ebene.inrialpes.fr (8.9.3/8.8.6) with ESMTP id SAA00853
	for <seamoby@diameter.org>; Mon, 19 Mar 2001 18:05:19 +0100 (MET)
Received: from inrialpes.fr (galibier.inrialpes.fr [194.199.24.97])
	by pop-serv.inrialpes.fr (8.9.3+Sun/8.8.5) with ESMTP id SAA04279
	for <seamoby@diameter.org>; Mon, 19 Mar 2001 18:05:20 +0100 (MET)
Message-ID: <3AB63C4E.67CDBFC3@inrialpes.fr>
Date: Mon, 19 Mar 2001 18:05:19 +0100
From: Thierry Ernst <thierry.ernst@inrialpes.fr>
Organization: INRIA Rhone-Alpes
X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: seamoby@diameter.org
Subject: Re: [seamoby] Micro-mobility Issues for IESG to Consider
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

My understanding is that Charlie only replied about Mobile IPv4, not
Mobile IPv6.  See my answer about Mobile IPv6.

> > Can MIP work effectively on and with:
> > Mobile Access Network Gateways?
> Why not?  I would say yes.  Do they offer care-of addresses?
> 
> > Mobile Routers?
> Here the answer is "yes", depending on how you would like to
> inject routes into rest of the Internet for the mobile portion
> which is to be served by the mobile router.

As far as you are dealing with mobile routers, you are also dealing with
a complete mobile network.  

Mobile networks can be supportted by Mobile IPv4; however,  I would say
that the solution described in RFC2002 is not scalable.

Mobile networks are NOT SUPPORTED by today's Mobile IPv6.  The reason is
because the Home Agent does not know how to redirect packets to hosts
behind the mobile router.  See my draft
http://www.inrialpes.fr/planete/people/ernst/Documents/draft-ernst-mobileip-v6-network.txt
for a comprehensive explanation of the problem.  However, Mobile IPv6
only require minor extensions to support mobile networks, and this is
also covered in the draft. 
 
> > Mobile Nodes?
> > Mobile Hosts?
A node is whether a host or a router.   Mobile IPv6 does not distinguish
between host and router.   Therefore, MIPv6 support both of them (but
not what is behind the mobile router as said before).

> > Mobile unaware nodes?
> No.

In my solution to support mobile networks in MIPv6, hosts located in the
mobile network are unaware of the mobility of the mobile network.  Thus,
mobility of the network is transparent to them, and mobility is entirely
managed by the mobile router.
 
> > Ad Hoc mobile networks?
> No.

In Mobile IPp6, ad-hoc networks may be connected to the Internet through
a mobile router. In this case, the solution described in my draft might
help.

Thierry.


--
* mailto:Thierry.Ernst@inrialpes.fr  Tel +33 (0) 4 76 61 52 69 
* INRIA Rhone-Alpes Projet PLANETE       (fax 52 52) 
* and MOTOROLA Labs Paris
* http://www.inrialpes.fr/planete/people/ernst/Welcome.html


From owner-seamoby@diameter.org  Mon Mar 19 14:20:57 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18997
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Mar 2001 14:20:55 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2JHwfl27148
	for seamoby-list; Mon, 19 Mar 2001 09:58:41 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2JHwcF27143
	for <seamoby@diameter.org>; Mon, 19 Mar 2001 09:58:39 -0800
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Mon, 19 Mar 2001 12:06:48 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GR4V9T82>; Mon, 19 Mar 2001 12:06:54 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8E09@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        Phil_Neumiller <Phil_Neumiller@3Com.com>,
        "behcet.sarikaya" <behcet.sarikaya@usa.alcatel.com>
Cc: mankin <mankin@east.isi.edu>, seamoby <seamoby@diameter.org>
Subject: RE: [seamoby] Re: [seamoby-paging] Re: Minutes of the teleconfere nce 
         nce on Wed. 03 /13
Date: Mon, 19 Mar 2001 12:06:39 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0B096.F69162C0"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0B096.F69162C0
Content-Type: text/plain;
	charset="ISO-8859-1"

I think we are on the same page here, James.
It is my understanding that the convention you refer to is how it
is supposed to work. We can run the dt's either way (well, at least
until the ADs complain), but I am concerned about churning over
issues if the group gets too large (a problem with either approach,
but hopefully somewhat diminished if we keep the information flow
to the dt's until the deliverables are ready for release to the wg).

Cheers,
Gary

> -----Original Message-----
> From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
> Sent: Monday, March 19, 2001 12:51 PM
> To: Kenward, Gary [WDLN2:AN10:EXCH]; Phil_Neumiller; behcet.sarikaya
> Cc: mankin; seamoby
> Subject: RE: [seamoby] Re: [seamoby-paging] Re: Minutes of the
> teleconfere nce on Wed. 03 /13
> 
> 
> Gary,
> 
> Actually, I don't particularly care one way or the other; 
> however, posting
> the minutes to the main list certainly does serve the purpose 
> of keeping
> the entire working group updated between IETF meetings. Since 
> the design
> teams are trying to move quickly, and since the working group has the
> final say on the design, I think it makes some sense to get 
> early feedback.
> I agree that opening discussion on details can be 
> counterproductive, but
> if we have the convention that anybody who wants to comment 
> on the minutes
> should go to the design team list and particpate in the design team
> teleconferences, rather than simply posting to the main list,
> perhaps that would help.
> 
> The only other alternative is to wait until a draft of the document is
> done before updating the entire working group, and that tends to be
> somewhat more heavy weight. It happens less often, and the 
> working group
> members need to read through the entire document, which takes longer. 
> 
> Design teams are a relatively recent IETF custom, I'm not sure that
> we have all the corners worked out yet.
> 
> 		jak
> 
> >Perhaps I have a unique perception of what a design team is 
> all about.
> >I have no real problem with posting to the main list, but I do have a
> >problem with opening the debate too far. Those that want to be part
> >of the dt can subscribe (if you have any problems, email me direct).
> >
> >If the wg wants an open discussion of the drafts, then let's dissolve
> >the design teams. They only exist in order to provide focus so that 
> >progress can be made. If we start cross posting, and the debate
> >widens (as has happened in the past), then progress will be slowed.
> >
> >No matter how well minutes are written, they will not capture the
> >context of a complete discussion. Statements taken out of context
> >will often regenerate a debate that has already taken place.
> >And when you have minutes full of personal opinion (with 
> apologies to 
> >Phil - he did warn us), then there is an even greater risk. 
> >
> >PLEASE NOTE: I am not saying that the discussions should be closed,
> >I am simply saying that the dts have a specific purpose, and 
> if the wg
> >does not value that purpose, then let's dissolve the dts and return
> >to the main list.
> >
> >Gary
> >
> >> -----Original Message-----
> >> From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
> >> Sent: Saturday, March 17, 2001 2:18 PM
> >> To: behcet.sarikaya@usa.alcatel.com; Phil_Neumiller@3Com.com
> >> Cc: seamoby@diameter.org; mankin@east.isi.edu
> >> Subject: Re: [seamoby] Re: [seamoby-paging] Re: Minutes of the
> >> teleconference on Wed. 03 /13
> >> 
> >> 
> >> Phil,
> >> 
> >> I think it is a good idea to post (but not cross post) to the 
> >> main list rather
> >> than just the design team list. Behcet's confusion is 
> >> understandable because we 
> >> did not announce this policy ahead of time. However, as you 
> >> point out, it does 
> >> allow the rest of the working group to keep track of the 
> >> meetings, and to 
> >> chime in if there is anything they have to say.
> >> 
> >> 		jak
> >> 
> >> >X-Authentication-Warning: charizard.diameter.org: majordomo 
> >> set sender to 
> >> owner-seamoby@diameter.org using -f
> >> >X-Lotus-FromDomain: 3COM
> >> >From: Phil_Neumiller@3Com.com
> >> >To: Behcet Sarikaya <behcet.sarikaya@usa.alcatel.com>
> >> >cc: seamoby@diameter.org, mankin@east.isi.edu
> >> >Date: Fri, 16 Mar 2001 18:23:27 -0600
> >> >Subject: [seamoby] Re: [seamoby-paging] Re: Minutes of the 
> >> teleconference on 
> >> Wed. 03 /13
> >> >Mime-Version: 1.0
> >> >Content-Disposition: inline
> >> >
> >> >
> >> >
> >> >
> >> >I did post the paging meeting minutes Behcet.   BTW, I am 
> >> both Phil's :-)
> >> >Sorry for the confusion.  The  minutes were posted  to the 
> >> main SeaMoby list.
> >> >I can understand your confusion Behcet.
> >> >
> >> >The following was MY choice which I thought was a good one:
> >> >
> >> >"Design team meeting minutes MUST always be posted to the MAIN
> >> >WG list so that the WHOLE WG is CROSS informed regularly."
> >> >
> >> >Bad idea?  Many WG members seem to think so for some reason?  Yet,
> >> >none have stepped forward to say why?  Other WG members think it
> >> >is a good idea.  Time for a hum?  I don't now.  Up to Pat 
> >> and Allison or
> >> >Scott.
> >> >
> >> >I am CC'ing  this to  Pat and Allison because I am tired of 
> >> all the whining
> >> >directed at me about meeting minutes.  Your mail was not 
> >> whining Behcet
> >> >you were rightfully confused, and I take responsibility for 
> >> it.  The whining
> >> >has occured in the actual teleconferences. I would like the 
> >> process of design
> >> >team minutes to be settled once and for all please.
> >> >
> >> >Thank you,
> >> >
> >> >Phil Neumiller
> >> >
> >> >
> >> 
> >> 
> 
> 
> 

------_=_NextPart_001_01C0B096.F69162C0
Content-Type: text/html;
	charset="ISO-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>RE: [seamoby] Re: [seamoby-paging] Re: Minutes of the teleconference nce  on Wed. 03 /13</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>I think we are on the same page here, James.</FONT>
<BR><FONT SIZE=2>It is my understanding that the convention you refer to is how it</FONT>
<BR><FONT SIZE=2>is supposed to work. We can run the dt's either way (well, at least</FONT>
<BR><FONT SIZE=2>until the ADs complain), but I am concerned about churning over</FONT>
<BR><FONT SIZE=2>issues if the group gets too large (a problem with either approach,</FONT>
<BR><FONT SIZE=2>but hopefully somewhat diminished if we keep the information flow</FONT>
<BR><FONT SIZE=2>to the dt's until the deliverables are ready for release to the wg).</FONT>
</P>

<P><FONT SIZE=2>Cheers,</FONT>
<BR><FONT SIZE=2>Gary</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: James Kempf [<A HREF="mailto:kempf@heliopolis.Eng.Sun.COM">mailto:kempf@heliopolis.Eng.Sun.COM</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Monday, March 19, 2001 12:51 PM</FONT>
<BR><FONT SIZE=2>&gt; To: Kenward, Gary [WDLN2:AN10:EXCH]; Phil_Neumiller; behcet.sarikaya</FONT>
<BR><FONT SIZE=2>&gt; Cc: mankin; seamoby</FONT>
<BR><FONT SIZE=2>&gt; Subject: RE: [seamoby] Re: [seamoby-paging] Re: Minutes of the</FONT>
<BR><FONT SIZE=2>&gt; teleconfere nce on Wed. 03 /13</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Gary,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Actually, I don't particularly care one way or the other; </FONT>
<BR><FONT SIZE=2>&gt; however, posting</FONT>
<BR><FONT SIZE=2>&gt; the minutes to the main list certainly does serve the purpose </FONT>
<BR><FONT SIZE=2>&gt; of keeping</FONT>
<BR><FONT SIZE=2>&gt; the entire working group updated between IETF meetings. Since </FONT>
<BR><FONT SIZE=2>&gt; the design</FONT>
<BR><FONT SIZE=2>&gt; teams are trying to move quickly, and since the working group has the</FONT>
<BR><FONT SIZE=2>&gt; final say on the design, I think it makes some sense to get </FONT>
<BR><FONT SIZE=2>&gt; early feedback.</FONT>
<BR><FONT SIZE=2>&gt; I agree that opening discussion on details can be </FONT>
<BR><FONT SIZE=2>&gt; counterproductive, but</FONT>
<BR><FONT SIZE=2>&gt; if we have the convention that anybody who wants to comment </FONT>
<BR><FONT SIZE=2>&gt; on the minutes</FONT>
<BR><FONT SIZE=2>&gt; should go to the design team list and particpate in the design team</FONT>
<BR><FONT SIZE=2>&gt; teleconferences, rather than simply posting to the main list,</FONT>
<BR><FONT SIZE=2>&gt; perhaps that would help.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; The only other alternative is to wait until a draft of the document is</FONT>
<BR><FONT SIZE=2>&gt; done before updating the entire working group, and that tends to be</FONT>
<BR><FONT SIZE=2>&gt; somewhat more heavy weight. It happens less often, and the </FONT>
<BR><FONT SIZE=2>&gt; working group</FONT>
<BR><FONT SIZE=2>&gt; members need to read through the entire document, which takes longer. </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Design teams are a relatively recent IETF custom, I'm not sure that</FONT>
<BR><FONT SIZE=2>&gt; we have all the corners worked out yet.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jak</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt;Perhaps I have a unique perception of what a design team is </FONT>
<BR><FONT SIZE=2>&gt; all about.</FONT>
<BR><FONT SIZE=2>&gt; &gt;I have no real problem with posting to the main list, but I do have a</FONT>
<BR><FONT SIZE=2>&gt; &gt;problem with opening the debate too far. Those that want to be part</FONT>
<BR><FONT SIZE=2>&gt; &gt;of the dt can subscribe (if you have any problems, email me direct).</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;If the wg wants an open discussion of the drafts, then let's dissolve</FONT>
<BR><FONT SIZE=2>&gt; &gt;the design teams. They only exist in order to provide focus so that </FONT>
<BR><FONT SIZE=2>&gt; &gt;progress can be made. If we start cross posting, and the debate</FONT>
<BR><FONT SIZE=2>&gt; &gt;widens (as has happened in the past), then progress will be slowed.</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;No matter how well minutes are written, they will not capture the</FONT>
<BR><FONT SIZE=2>&gt; &gt;context of a complete discussion. Statements taken out of context</FONT>
<BR><FONT SIZE=2>&gt; &gt;will often regenerate a debate that has already taken place.</FONT>
<BR><FONT SIZE=2>&gt; &gt;And when you have minutes full of personal opinion (with </FONT>
<BR><FONT SIZE=2>&gt; apologies to </FONT>
<BR><FONT SIZE=2>&gt; &gt;Phil - he did warn us), then there is an even greater risk. </FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;PLEASE NOTE: I am not saying that the discussions should be closed,</FONT>
<BR><FONT SIZE=2>&gt; &gt;I am simply saying that the dts have a specific purpose, and </FONT>
<BR><FONT SIZE=2>&gt; if the wg</FONT>
<BR><FONT SIZE=2>&gt; &gt;does not value that purpose, then let's dissolve the dts and return</FONT>
<BR><FONT SIZE=2>&gt; &gt;to the main list.</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;Gary</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; From: James Kempf [<A HREF="mailto:kempf@heliopolis.Eng.Sun.COM">mailto:kempf@heliopolis.Eng.Sun.COM</A>]</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; Sent: Saturday, March 17, 2001 2:18 PM</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; To: behcet.sarikaya@usa.alcatel.com; Phil_Neumiller@3Com.com</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; Cc: seamoby@diameter.org; mankin@east.isi.edu</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; Subject: Re: [seamoby] Re: [seamoby-paging] Re: Minutes of the</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; teleconference on Wed. 03 /13</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; Phil,</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; I think it is a good idea to post (but not cross post) to the </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; main list rather</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; than just the design team list. Behcet's confusion is </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; understandable because we </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; did not announce this policy ahead of time. However, as you </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; point out, it does </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; allow the rest of the working group to keep track of the </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; meetings, and to </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; chime in if there is anything they have to say.</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jak</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;X-Authentication-Warning: charizard.diameter.org: majordomo </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; set sender to </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; owner-seamoby@diameter.org using -f</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;X-Lotus-FromDomain: 3COM</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;From: Phil_Neumiller@3Com.com</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;To: Behcet Sarikaya &lt;behcet.sarikaya@usa.alcatel.com&gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;cc: seamoby@diameter.org, mankin@east.isi.edu</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;Date: Fri, 16 Mar 2001 18:23:27 -0600</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;Subject: [seamoby] Re: [seamoby-paging] Re: Minutes of the </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; teleconference on </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; Wed. 03 /13</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;Mime-Version: 1.0</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;Content-Disposition: inline</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;I did post the paging meeting minutes Behcet.&nbsp;&nbsp; BTW, I am </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; both Phil's :-)</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;Sorry for the confusion.&nbsp; The&nbsp; minutes were posted&nbsp; to the </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; main SeaMoby list.</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;I can understand your confusion Behcet.</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;The following was MY choice which I thought was a good one:</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;&quot;Design team meeting minutes MUST always be posted to the MAIN</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;WG list so that the WHOLE WG is CROSS informed regularly.&quot;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;Bad idea?&nbsp; Many WG members seem to think so for some reason?&nbsp; Yet,</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;none have stepped forward to say why?&nbsp; Other WG members think it</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;is a good idea.&nbsp; Time for a hum?&nbsp; I don't now.&nbsp; Up to Pat </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; and Allison or</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;Scott.</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;I am CC'ing&nbsp; this to&nbsp; Pat and Allison because I am tired of </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; all the whining</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;directed at me about meeting minutes.&nbsp; Your mail was not </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; whining Behcet</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;you were rightfully confused, and I take responsibility for </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; it.&nbsp; The whining</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;has occured in the actual teleconferences. I would like the </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; process of design</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;team minutes to be settled once and for all please.</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;Thank you,</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;Phil Neumiller</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0B096.F69162C0--


From owner-seamoby@diameter.org  Mon Mar 19 15:35:46 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA20927
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Mar 2001 15:35:45 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2JJsI727470
	for seamoby-list; Mon, 19 Mar 2001 11:54:18 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from www.sac.or.kr ([210.117.234.11])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2JJsEF27465
	for <seamoby@cdma-2000.org>; Mon, 19 Mar 2001 11:54:14 -0800
Received: from wZ2gCNgII ([12.64.42.197]) by www.sac.or.kr
          (Netscape Mail Server v2.02) with SMTP id AAE16734;
          Mon, 19 Mar 2001 20:48:19 +0900
DATE: 19 Mar 02 4:02:57 AM
FROM: lk89lk99@yahoo.com
Message-ID: <9KQTt3wmGIU9QJGXy0S>
Subject: [seamoby] .
Sender: owner-seamoby@diameter.org
Precedence: bulk

MARKET YOUR BUSINESS OR PRODUCT TO MILLIONS WITHIN HOURS BY MASS EMAILING OVER THE INTERNET!

OUR COMPANY, NATIONAL BULK EMAIL MARKETING, specializes in mass email advertising over the Internet. With NATIONAL BULK EMAIL MARKETING COMPANY, your business, product or service can be promoted to millions of people within hours by sending out your advertisement by emails over the Internet!  Our 100 million plus database of active email account listings can be targeted to a specific Country, State, zip code, by Keyword or by your own targeted email list specification (e.g. email to all dentists only). 

======================================================================== 

EXAMPLE OF YOUR POTENTIAL PROFITS: 

1) Let's say you... Sell a $24.95 product or service.
2) Let's say you... Mass Email to 1,000,000 people daily.
3) Let's say you... Receive just 1 order for every 2,500 Emails.

CALCULATION OF YOUR EARNINGS BASED ON THE ABOVE STATISTICS:
[Day 1]: $9,980  [Week 1]: $69,860  [Month 1]: $279,440
  
Now you know why you receive so many email advertisements ........ MASS EMAIL ADVERTISING IS EXTREMELY PROFITABLE!

========================================================================

ADVANTAGES OF USING NATIONAL BULK EMAIL MARKETING COMPANY   

* 100 MILLION ACTIVE EMAIL ADDRESSES:  We maintain a growing list of over 100 million active email addresses and all are 100% DELIVERABLE.  The list is updated DAILY and WASHED TWICE a week! 

* TARGETED MARKETING:  Our 100 million plus database listings of active email accounts can be targeted to a specific Country, State, zip code, or by Keyword.  Additionally, if your business' has a very particular market nich of advertising that must be targeted to, we can quickly develop specific targeted email lists for your particular business' marketing needs  
    
* WE MASS MAIL 24/7: Order by 12 PM PST and you're SERVICED MASS MAILING by evening.

* 100% TAX WRITE OFF:  Our services can be used as a 100% TAX WRITE OFF for your Business!


MASS MAILING PRICES: 

      =>    500,000 Emails:      $630.00
      =>    750,000 Emails:      $750.00
      => 1,000,000 Emails:      $860.00 
      => 1,500,000 Emails:    $1290.00
      => 2,000,000 Emails:    $1590.00   
      => 3,000,000 Emails:    $2160.00 
      => 4,000,000 + Emails (Please call for quote)

========================================================================

CAUTION

You may receive A HUGE AMOUNT of orders within minutes of sending out your mass Email advertisement!

========================================================================

REFERENCES ATTESTING TO THE BENEFITS OF BULK EMAIL MARKETING

 * "Targeted direct email advertising is the wave of the future.  By no other means can you effectively reach your market so quickly and inexpensively" - ONLINE PROFITS NEWSLETTER

* "Many business people are finding out that they can now advertise in ways that they never could have afforded in the past.  The cost of sending mass e-mail is extremely low, and the response rate is high and quick." - USA TODAY

* According to a recent FIND/SVP Survey, 41% of people check their email daily!

* "When you reach people with e-mail, they're in a work mode.  Even if they're not at work, they're sitting up and they're alert.  You catch them at a good moment, and if you do it right, you have a really good shot of having them respond."  -  WILLIAM THAMES [Revnet Direct Marketing VP]

* "OVER 20,000 BUSINESSES come on the Internet EVERY single day... If you don't send out Mass Email... YOUR COMPETITION WILL!" - LOS ANGELES TIMES

========================================================================

TO ORDER:

To order NATIONAL BULK EMAIL MARKETING services , feel free to call our sales department (310-471-9257).  For more detailed questions, you can ask for one of our Beverly Hills attorneys in our legal department who will be happy field any questions about our company.  Our address is: 

NATIONAL BULK EMAIL MARKETING
9663 SANTA MONICA BLVD., SUITE # 281
BEVERLY HILLS, CA  90210-4303




@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
We apologize if this message has reached you in error.
Save the Planet, Save the Trees! Advertise via E mail.
No wasted paper! Delete with one simple keystroke!
Less refuse in our Dumps! This is the new way of the new millennium
To be removed please email g14toy@yahoo.com with the word "remove" in the subject line.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@


From owner-seamoby@diameter.org  Mon Mar 19 15:53:08 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA21446
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Mar 2001 15:53:08 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2JJVWB27414
	for seamoby-list; Mon, 19 Mar 2001 11:31:32 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from c007.snv.cp.net (c007-h011.c007.snv.cp.net [209.228.33.217])
	by charizard.diameter.org (8.11.3/8.11.3) with SMTP id f2JJUFF27407
	for <seamoby@cdma-2000.org>; Mon, 19 Mar 2001 11:30:15 -0800
Received: (cpmta 26796 invoked from network); 19 Mar 2001 10:03:19 -0800
Received: from pcp000692pcs.wireless.meeting.ietf.org (HELO PhilsSony) (135.222.64.192)
  by smtp.telocity.com (209.228.33.217) with SMTP; 19 Mar 2001 10:03:19 -0800
X-Sent: 19 Mar 2001 18:03:19 GMT
Message-ID: <001301c0b09f$1c538c60$c040de87@mw.3com.com>
From: "Phillip Neumiller" <neumiller@telocity.com>
To: "Alexandru Petrescu" <Alexandru_Petrescu-AAP021@email.mot.com>
Cc: <seamoby@cdma-2000.org>, <mobile-ip@sunroof.eng.sun.com>
References: <88256A11.00727F9F.00@hqoutbound.ops.3com.com> <m3lmq2ays1.fsf@riri.crm.mot.com>
Subject: Re: [seamoby] Re: Who implements MIP?
Date: Mon, 19 Mar 2001 12:04:57 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The difference between your list and mine, is that your list is primarly
a list of free (more research/testbed ) versions for study whereas
my list is commercially deployed versions of MIP.  I am trying to collect
data points and  measurements on commercially deployed MIP systems.

Thanks,

Phil
----- Original Message ----- > 
> I maintain a list of publicly-available (simple) mobile ipv6
> implementations and I'd like to know more details about the above in
> order to add them to my list.
> 



From owner-seamoby@diameter.org  Mon Mar 19 15:55:50 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA21538
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Mar 2001 15:55:49 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2JKJV827551
	for seamoby-list; Mon, 19 Mar 2001 12:19:31 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2JKJTF27546
	for <seamoby@cdma-2000.org>; Mon, 19 Mar 2001 12:19:29 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA17145;
	Mon, 19 Mar 2001 11:27:38 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA11810;
	Mon, 19 Mar 2001 11:27:37 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (esun1as-be.Central.Sun.COM [129.147.34.142])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id LAA18260;
	Mon, 19 Mar 2001 11:27:29 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Message-Id: <200103191927.LAA18260@nasnfs.Eng.Sun.COM>
Date: Mon, 19 Mar 2001 11:23:58 -0800
To: "Phillip Neumiller" <neumiller@telocity.com>,
        "Alexandru Petrescu" <Alexandru_Petrescu-AAP021@email.mot.com>
Cc: <mobile-ip@sunroof.eng.sun.com>, <seamoby@cdma-2000.org>
Reply-To: <pcalhoun@eng.sun.com>
Subject: Re: [seamoby] Re: Who implements MIP?
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

May I ask why the seamoby list needs to be cross-posted on this Mobile IP
topic? 

Could we remove the cross-post in all future e-mails that have no relevance
to Seamoby?

PatC
>The difference between your list and mine, is that your list is primarly
>a list of free (more research/testbed ) versions for study whereas
>my list is commercially deployed versions of MIP.  I am trying to collect
>data points and  measurements on commercially deployed MIP systems.
>
>Thanks,
>
>Phil
>----- Original Message ----- > 
>> I maintain a list of publicly-available (simple) mobile ipv6
>> implementations and I'd like to know more details about the above in
>> order to add them to my list.
>> 
>




From owner-seamoby@diameter.org  Mon Mar 19 16:51:08 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22895
	for <seamoby-archive@odin.ietf.org>; Mon, 19 Mar 2001 16:51:07 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2JKwRb27650
	for seamoby-list; Mon, 19 Mar 2001 12:58:27 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2JKwPF27645;
	Mon, 19 Mar 2001 12:58:26 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA16011;
	Mon, 19 Mar 2001 12:06:22 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA21122;
	Mon, 19 Mar 2001 12:06:19 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (esun1as-be.Central.Sun.COM [129.147.34.142])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id MAA18968;
	Mon, 19 Mar 2001 12:06:09 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Message-Id: <200103192006.MAA18968@nasnfs.Eng.Sun.COM>
Date: Mon, 19 Mar 2001 12:02:39 -0800
To: "Gary Kenward" <gkenward@nortelnetworks.com>, <Phil_Neumiller@3Com.com>,
        "'Behcet Sarikaya'" <behcet.sarikaya@usa.alcatel.com>
Cc: <seamoby-paging@diameter.org>, <seamoby@diameter.org>
Reply-To: <pcalhoun@eng.sun.com>
Subject: RE: [seamoby] Re: [seamoby-paging] Re: Minutes of the teleconfere nce          on Wed. 03/13
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>  Second, although Phil has clearly stated his desire, it is my view, shared
>by Pat Calhoun, that the minutes need only be posted on seamoby_context.
>The only "harm" I see in posting to the seamoby list is the spam it
>generates,
>and the possible confusion that might result from statements taken out of
>context (as good as the minutes might be, they never capture the complete
>context of the conversation - hmmm, I guess I'm saying the context transfer
>is not perfect ;^} ). The design team is, as far as I understand it, a
>focussed
>effort by a group of contributors, by definition, the intent is to limit the

Correct. The minutes only need to be posted to the relevant design team lists,
which are archived. Anyone that cares is either on the list, or can check
the archives.

PatC



From owner-seamoby@diameter.org  Wed Mar 21 13:12:36 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA04290
	for <seamoby-archive@odin.ietf.org>; Wed, 21 Mar 2001 13:12:36 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2LI0ST02244
	for seamoby-list; Wed, 21 Mar 2001 10:00:28 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from usrsrv1.meeting.ietf.org (smtp.meeting.ietf.org [135.222.20.40])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2LI0QF02239
	for <seamoby@diameter.org>; Wed, 21 Mar 2001 10:00:26 -0800
Received: from porce (pcp000838pcs.wireless.meeting.ietf.org [135.222.65.82])
	by usrsrv1.meeting.ietf.org (8.11.2/8.11.2) with SMTP id f2LH9Bw12094
	for <seamoby@diameter.org>; Wed, 21 Mar 2001 11:09:11 -0600 (CST)
Message-ID: <007901c0b229$f7487ca0$5241de87@wireless.meeting.ietf.org>
From: "Jiwoong Lee" <porce@kaist.ac.kr>
To: <seamoby@diameter.org>
Subject: [seamoby] term: inter-technology handover
Date: Thu, 22 Mar 2001 02:11:27 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Isn't this term a bit misleading ?

Jiwoong




From owner-seamoby@diameter.org  Wed Mar 21 19:37:49 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA26638
	for <seamoby-archive@odin.ietf.org>; Wed, 21 Mar 2001 19:37:49 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2LNQxc03488
	for seamoby-list; Wed, 21 Mar 2001 15:26:59 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2LNQvF03482
	for <seamoby@cdma-2000.org>; Wed, 21 Mar 2001 15:26:57 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA26931
	for <seamoby@cdma-2000.org>; Wed, 21 Mar 2001 14:35:45 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA13962
	for <seamoby@cdma-2000.org>; Wed, 21 Mar 2001 14:35:45 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (esun1as-be.Central.Sun.COM [129.147.34.142])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id OAA00566
	for <seamoby@cdma-2000.org>; Wed, 21 Mar 2001 14:35:33 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Message-Id: <200103212235.OAA00566@nasnfs.Eng.Sun.COM>
Date: Wed, 21 Mar 2001 14:31:55 -0800
To: <seamoby@cdma-2000.org>
Reply-To: <pcalhoun@eng.sun.com>
Subject: [seamoby] An MM update from IETF 50
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

All,

This week the ADs and I sat down with the Mobile IP chairs, Routing AD and IRTF
routing chair, and talked about the current problem statement. The current
document currently describes:

	1. There are some seamoby requirements that are not met with the
	   Mobile IP WG.
	2. There is the possibility of a new local mobility protocol, and
	3. A method to discover the capabilities of APs that a mobile can be
	   handed off to, so handoffs are done in a more intelligent way.

So, for all three above points, the following was decided, and discussed at
the meeting:

	1. The MM DT will write a requirements draft for Mobile IP to understand
	   the seamoby requirements. This will be used by the MIP WG to
	   know how Mobile IP needs to be changed.
	2. The IRTF has agreed to take the new local mobility protocol, and
	   as with many other IRTF efforts, the work will move back into the
	   IETF once it is ready.
	3. The MM DT will begin to write the requirements for a new protocol
	   that allows for AP discovery to be done (again, I really don't know
	   what the right name of this work is, but it is similar to what
	   Phil Neumiller calls CNP).

If anyone has issues with the above decisions, please contact me.

Thanks,

PatC



From owner-seamoby@diameter.org  Wed Mar 21 19:51:00 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27462
	for <seamoby-archive@odin.ietf.org>; Wed, 21 Mar 2001 19:51:00 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2LNDGW03458
	for seamoby-list; Wed, 21 Mar 2001 15:13:16 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2LNCsF03453
	for <seamoby@diameter.org>; Wed, 21 Mar 2001 15:12:55 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Wed, 21 Mar 2001 16:54:40 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <GR4WALAS>; Wed, 21 Mar 2001 16:54:41 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8E2A@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'seamoby_context'" <seamoby_context@marvin.baynetworks.com>
Cc: "'seamoby'" <seamoby@diameter.org>,
        "'Pat Calhoun'" <Pat.Calhoun@eng.sun.com>
Subject: [seamoby] Proposed: Context Transfer design team conference call, Monday Ma rch 
         26, 2001, 11 am EST
Date: Wed, 21 Mar 2001 16:54:35 -0500
Importance: high
X-Priority: 1
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="ISO-8859-1"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

Conference call *proposal*. Please respond.
During that last conference call, I believe we decided to have the next call
on
the usual day of the week, at the usual time, right after the IETF meeting.
I have booked a conference bridge, and if there is an interest, we can
proceed
with a design team meeting:
Context Transfer design team conference call
Monday March 26, 2001, 11 am EST
Bridge phone number: 972 684-6338 (North America) 
Passcode:                    793142# 

Since everyone is busy with the IETF meeting, there isn't a
lot of items for the agenda. Hamid Syed has submitted an ID
on requirements that can be discussed, and there have been a 
few email postings.

In addition, I believe that Pat Calhoun will want a few minutes.

Agenda:

	11:00am - 11:10am hellos, attendance
	11:10am - 11:15am agenda bashing
            11:15am - 11:30am discussion of Hamid Syed's requirements draft
	11:30am - 12:00pm general discussion of requirements
	12:00pm - 12:15pm Working Group Chair
	12:15pm  - 12:20pm wrap-up

If anyone wants time on the agenda, or has a comment, please email me
before Friday afternoon (EST) so that there is some time to propagate
the agenda.

If more then 20% of the respondents to this announcement cannot make
the meeting, it will be re-scheduled.

Gary


From owner-seamoby@diameter.org  Wed Mar 21 20:10:43 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA28346
	for <seamoby-archive@odin.ietf.org>; Wed, 21 Mar 2001 20:10:42 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2LNq3i03608
	for seamoby-list; Wed, 21 Mar 2001 15:52:03 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2LNq1F03603
	for <seamoby@cdma-2000.org>; Wed, 21 Mar 2001 15:52:01 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id PAA21547;
	Wed, 21 Mar 2001 15:00:48 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADB04899;
	Wed, 21 Mar 2001 15:00:42 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id PAA00952; Wed, 21 Mar 2001 15:00:42 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15033.12954.736660.607073@thomasm-u1.cisco.com>
Date: Wed, 21 Mar 2001 15:00:42 -0800 (PST)
To: <pcalhoun@eng.sun.com>
Cc: <seamoby@cdma-2000.org>
Subject: [seamoby] An MM update from IETF 50
In-Reply-To: <200103212235.OAA00566@nasnfs.Eng.Sun.COM>
References: <200103212235.OAA00566@nasnfs.Eng.Sun.COM>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Huh. I hear that winters in Siberia aren't as bad
as everybody makes them out to be.

In any case, so long as our requirements for
paging and context transfer take into account and
potentially exploit that the fact that you may end
up with same routable address, I guess I'm mostly
happy for the time being.

	  Mike

Patrice Calhoun writes:
 > All,
 > 
 > This week the ADs and I sat down with the Mobile IP chairs, Routing AD and IRTF
 > routing chair, and talked about the current problem statement. The current
 > document currently describes:
 > 
 > 	1. There are some seamoby requirements that are not met with the
 > 	   Mobile IP WG.
 > 	2. There is the possibility of a new local mobility protocol, and
 > 	3. A method to discover the capabilities of APs that a mobile can be
 > 	   handed off to, so handoffs are done in a more intelligent way.
 > 
 > So, for all three above points, the following was decided, and discussed at
 > the meeting:
 > 
 > 	1. The MM DT will write a requirements draft for Mobile IP to understand
 > 	   the seamoby requirements. This will be used by the MIP WG to
 > 	   know how Mobile IP needs to be changed.
 > 	2. The IRTF has agreed to take the new local mobility protocol, and
 > 	   as with many other IRTF efforts, the work will move back into the
 > 	   IETF once it is ready.
 > 	3. The MM DT will begin to write the requirements for a new protocol
 > 	   that allows for AP discovery to be done (again, I really don't know
 > 	   what the right name of this work is, but it is similar to what
 > 	   Phil Neumiller calls CNP).
 > 
 > If anyone has issues with the above decisions, please contact me.
 > 
 > Thanks,
 > 
 > PatC
 > 


From owner-seamoby@diameter.org  Thu Mar 22 12:49:00 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA15985
	for <seamoby-archive@odin.ietf.org>; Thu, 22 Mar 2001 12:49:00 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2MFjKO05931
	for seamoby-list; Thu, 22 Mar 2001 07:45:20 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2MFjIF05926
	for <seamoby@cdma-2000.org>; Thu, 22 Mar 2001 07:45:18 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA23382;
	Thu, 22 Mar 2001 06:54:04 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA18960;
	Thu, 22 Mar 2001 06:54:02 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (esun1as-be.Central.Sun.COM [129.147.34.142])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id GAA08283;
	Thu, 22 Mar 2001 06:53:58 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Message-Id: <200103221453.GAA08283@nasnfs.Eng.Sun.COM>
Date: Thu, 22 Mar 2001 06:50:14 -0800
To: "Michael Thomas" <mat@cisco.com>
Cc: <seamoby@cdma-2000.org>
Reply-To: <pcalhoun@eng.sun.com>
Subject: Re: [seamoby] An MM update from IETF 50
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


>
>Huh. I hear that winters in Siberia aren't as bad
>as everybody makes them out to be.

Just for the record, SMIng, multicast security and other WGs have had a 
great IRTF->IETF transition, so you paint this to be worse than it really is.

PatC



From owner-seamoby@diameter.org  Thu Mar 22 16:13:01 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA21663
	for <seamoby-archive@odin.ietf.org>; Thu, 22 Mar 2001 16:13:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2MKGu706898
	for seamoby-list; Thu, 22 Mar 2001 12:16:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from optima.CS.Arizona.EDU (optima.CS.Arizona.EDU [192.12.69.5])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2MKGsF06893
	for <seamoby@cdma-2000.org>; Thu, 22 Mar 2001 12:16:54 -0800
Received: from baskerville.CS.Arizona.EDU (baskerville.CS.Arizona.EDU [192.12.69.35])
	by optima.CS.Arizona.EDU (8.11.1/8.11.1) with ESMTP id f2MJMfl10713;
	Thu, 22 Mar 2001 12:22:41 -0700 (MST)
Received: (from micke@localhost)
	by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id f2MJPhM00633;
	Thu, 22 Mar 2001 12:25:43 -0700 (MST)
Date: Thu, 22 Mar 2001 12:25:43 -0700 (MST)
From: micke@CS.Arizona.EDU
Message-Id: <200103221925.f2MJPhM00633@baskerville.CS.Arizona.EDU>
X-Authentication-Warning: baskerville.CS.Arizona.EDU: micke set sender to micke@cs.arizona.edu using -r
To: mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se, seamoby@cdma-2000.org
Subject: [seamoby] Header compression context extablishment
Sender: owner-seamoby@diameter.org
Precedence: bulk

To: mobile-ip@sunroof.eng.sun.com, seamoby@cdma-2000.org, rohc@cdt.luth.se

Re: Header compression state establishment
==========================================

Folks, 

It has come to my attention that some more or less
informed statements have been made regarding header
compression and how efficient/inefficient (re)establishment
of header compression state might be. 

In particular, the statements made in 

draft-ietf-seamoby-context-transfer-problem-stat-00.txt

are not completely accurate. This is an attempt to clarify the
situation for the header compression methodology developed in the 
ROHC WG.

The typical startup scenario for the ROHC header compression
schemes for telephony streams is as follows:

1) send a small number of IR packets with a header size roughly similar
to the header size of uncompressed headers. I expect that most
implementations will send roughly 3 IR packets.

If operating in U-mode or O-mode, this completes the context
initialization, and minimal packets will be sent henceforth.
U-mode can do an exponential backoff when sending IR packets, 
but the typical transition to O-mode or R-mode will prevent 
those IR packets from being sent. 

If operation in R-mode is desired, the minimal packets will be
sent until an acknowledgment (containing a mode transition request)
reaches the compressor. Then, 

2) during an additional roundtrip, non-minimal headers are sent during
transition to R-mode. 


Some parameters are as follows:

link roundtrip for cellular: 120-200 milliseconds.
(6-10 packets at 50 packets per second).

Minimal headers are 1 byte. 

Header size in 2) is rougly 4 bytes.

The header sizes indicated above do not include context identifiers,
which can be omitted completely for context identifier zero. 
Nor do they include the two-byte UDP checksum, which will not be sent at
all if disabled. Nor do they include the two byte IPv4 Identifier, 
which will be sent as-is if it changes randomly. Reasonable IP stacks
will have it change in increments of one, and then it will be 
completely removed. 

Hope this has helped to clarify the situation with regards to header
compression and its context (re) initialization. 


Mikael Degermark
Co-chair, ROHC WG








From owner-seamoby@diameter.org  Thu Mar 22 17:18:05 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA23368
	for <seamoby-archive@odin.ietf.org>; Thu, 22 Mar 2001 17:18:05 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2MKsCW06999
	for seamoby-list; Thu, 22 Mar 2001 12:54:12 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2MKsAF06994
	for <seamoby@cdma-2000.org>; Thu, 22 Mar 2001 12:54:10 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA08453;
	Thu, 22 Mar 2001 12:02:59 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA04056;
	Thu, 22 Mar 2001 12:02:53 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (esun1as-be.Central.Sun.COM [129.147.34.142])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id MAA13448;
	Thu, 22 Mar 2001 12:01:43 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Message-Id: <200103222001.MAA13448@heliopolis.Eng.Sun.COM>
Date: Thu, 22 Mar 2001 14:02:05 -0700
To: <micke@CS.Arizona.EDU>, <seamoby@cdma-2000.org>, <rohc@cdt.luth.se>,
        <mobile-ip@sunroof.eng.sun.com>
Reply-To: <kempf@heliopolis.Eng.Sun.COM>
Subject: Re: [seamoby] Header compression context extablishment
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Mike,

Thanx for your response. Two questions.

>1) send a small number of IR packets with a header size roughly similar
>to the header size of uncompressed headers. I expect that most
>implementations will send roughly 3 IR packets.
>
>If operating in U-mode or O-mode, this completes the context
>initialization, and minimal packets will be sent henceforth.
>U-mode can do an exponential backoff when sending IR packets, 
>but the typical transition to O-mode or R-mode will prevent 
>those IR packets from being sent. 
>
>If operation in R-mode is desired, the minimal packets will be
>sent until an acknowledgment (containing a mode transition request)
>reaches the compressor. Then, 
>
>2) during an additional roundtrip, non-minimal headers are sent during
>transition to R-mode. 
>
>
>Some parameters are as follows:
>
>link roundtrip for cellular: 120-200 milliseconds.
>(6-10 packets at 50 packets per second).
>

Does the compressor have to start from scratch if the IP address in the
header changes? The issue here is that on a mobile IP handover, the
care of address will change. The mobile IP group is working hard
on low latency handover protocols. If the mobile node is forced to
go through a 120-200 ms compressor initialization period, the benefits
of low latency handoff will be substantially negated.

>Minimal headers are 1 byte. 
>
>Header size in 2) is rougly 4 bytes.
>
>The header sizes indicated above do not include context identifiers,
>which can be omitted completely for context identifier zero. 
>Nor do they include the two-byte UDP checksum, which will not be sent at
>all if disabled. Nor do they include the two byte IPv4 Identifier, 
>which will be sent as-is if it changes randomly. Reasonable IP stacks
>will have it change in increments of one, and then it will be 
>completely removed. 
>

Does this analysis change at all for IPv6? Most of our discussion
has been about IPv6 since the need for header compression is much
more urgent, due to the large header size.

			jak



From owner-seamoby@diameter.org  Thu Mar 22 18:47:02 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA26281
	for <seamoby-archive@odin.ietf.org>; Thu, 22 Mar 2001 18:47:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2MMhTv07265
	for seamoby-list; Thu, 22 Mar 2001 14:43:29 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from optima.CS.Arizona.EDU (optima.CS.Arizona.EDU [192.12.69.5])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2MMhRF07260
	for <seamoby@cdma-2000.org>; Thu, 22 Mar 2001 14:43:27 -0800
Received: from baskerville.CS.Arizona.EDU (baskerville.CS.Arizona.EDU [192.12.69.35])
	by optima.CS.Arizona.EDU (8.11.1/8.11.1) with ESMTP id f2MLnDl13015;
	Thu, 22 Mar 2001 14:49:14 -0700 (MST)
Received: (from micke@localhost)
	by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id f2MLqGU03116;
	Thu, 22 Mar 2001 14:52:16 -0700 (MST)
Date: Thu, 22 Mar 2001 14:52:16 -0700 (MST)
From: Mikael Degermark <micke@CS.Arizona.EDU>
Message-Id: <200103222152.f2MLqGU03116@baskerville.CS.Arizona.EDU>
To: kempf@heliopolis.Eng.Sun.COM
Subject: Re: [seamoby] Header compression context extablishment
Cc: mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se, seamoby@cdma-2000.org
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi James, 

We need to talk about exact header formats before I can give
an exact answer. The answer may be different for IPv4 and IPv6.

Your comment regarding low-latency handoff may be understood to 
mean that you think that no packet can be sent during the initial 
120-200 ms. 

Packets can be sent at any time, it is just that the first 3 are
normal size packets, without significantly reduced size. After those
three (or so), headers will be compressed. 

I think we need to talk more. Are you available at 17.30 ?
Let us meet in the lobby (street level) to talk. Is that 
possible?

Cheers,

Mikael Degermark


From owner-seamoby@diameter.org  Thu Mar 22 22:35:18 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA05364
	for <seamoby-archive@odin.ietf.org>; Thu, 22 Mar 2001 22:35:18 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2N2Lmp07806
	for seamoby-list; Thu, 22 Mar 2001 18:21:48 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2N2KVF07801
	for <seamoby@cdma-2000.org>; Thu, 22 Mar 2001 18:20:31 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA23953;
	Thu, 22 Mar 2001 17:29:21 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA29140;
	Thu, 22 Mar 2001 17:29:19 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (esun1as-be.Central.Sun.COM [129.147.34.142])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id RAA22400;
	Thu, 22 Mar 2001 17:29:14 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Message-Id: <200103230129.RAA22400@heliopolis.Eng.Sun.COM>
Date: Thu, 22 Mar 2001 19:28:28 -0700
To: "Mikael Degermark" <micke@CS.Arizona.EDU>
Cc: <seamoby@cdma-2000.org>, <rohc@cdt.luth.se>,
        <mobile-ip@sunroof.eng.sun.com>
Reply-To: <kempf@heliopolis.Eng.Sun.COM>
Subject: Re: [seamoby] Header compression context extablishment
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Michael,

Thanx for your reply.

>We need to talk about exact header formats before I can give
>an exact answer. The answer may be different for IPv4 and IPv6.
>

As we discussed, there will be a difference. For IPv4, the
compressor context will not include the care of address because
the Foreign Agent will strip the tunnel header before compressing. For IPv6,
co-located care-of addresses are implicitly assumed, so 
the care-of address will change.

>Your comment regarding low-latency handoff may be understood to 
>mean that you think that no packet can be sent during the initial 
>120-200 ms. 
>

OK, yes that was a concern, but it will just mean that the first
few packets are uncompressed and so slower. This makes the analysis a bit more
complex, but the upshot is that it would still mean a delay.

>Packets can be sent at any time, it is just that the first 3 are
>normal size packets, without significantly reduced size. After those
>three (or so), headers will be compressed. 
>
>I think we need to talk more. Are you available at 17.30 ?
>Let us meet in the lobby (street level) to talk. Is that 
>possible?
>

Right, as we discussed, I will attempt to locate some
IPv6 headers for you that illustrate the problem.

It would probably be good to co-ordinate between ROHC
and Seamoby context transfer design team so that
we can get this right, since our discussion in the
hotel lobby basically indicated that there may be
some tricky co-ordination issues between the mobile
node and the access router if the CoA header needs
to change.

		jak



From owner-seamoby@diameter.org  Fri Mar 23 14:44:49 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA02186
	for <seamoby-archive@odin.ietf.org>; Fri, 23 Mar 2001 14:44:49 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2NIVSY09982
	for seamoby-list; Fri, 23 Mar 2001 10:31:28 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2NIVQF09977
	for <seamoby@diameter.org>; Fri, 23 Mar 2001 10:31:26 -0800
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2NHcld23215;
	Fri, 23 Mar 2001 09:38:47 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.0/Switch-2.1.0) with SMTP id f2NHeFE04744;
	Fri, 23 Mar 2001 09:40:15 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A18.00610CCD ; Fri, 23 Mar 2001 09:40:02 -0800
X-Lotus-FromDomain: 3COM
From: Phil_Neumiller@3Com.com
To: pcalhoun@eng.sun.com
cc: seamoby@diameter.org
Message-ID: <88256A18.00610A5F.00@hqoutbound.ops.3com.com>
Date: Fri, 23 Mar 2001 11:39:52 -0600
Subject: Re: [seamoby] An MM update from IETF 50
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-seamoby@diameter.org
Precedence: bulk



Hello,

1). I think the mobile IP chairs, Pat, and the ADs have done an
    excellent job revising the charter.  It is really moving in
    the right direction.

2). Tuesday, Pat and I sat down for a bit and hashed out some
    mutual misunderstandings.  I would call it a moment of
    mutual "enlightenment".  More on "enlightenment" below.

3). CNP is not something I named/invented.  It has existed since
    1982.  I will post a new draft after May 1 that will explain
    in detail how it works in theory and how it can be gainfully
    applied to MANET, and MIP and how my code works.

    So far I have it running with AODV, and DSR (both MANET
    routing algorithms), and MIPv4.  The application is completely
    orthogonal i.e. it is done as a glue-on to handover req/rep
    messages.  The enlightened part is that I make some
    different assumptions (I actually assume CDMA-like air interfaces
    like those that will actually be applied in 3G!).  I assume
    that there are multiple pilots.  I assume that there can be
    multiple heterogeneous link layers etc.

4). I would like to propose that we introduce a concept of
    "enlightened handover" Into SeaMoby before we introduce it into
    the MIP group.  I would also suggest we call it enlightedned hand
    over (EHO).  I don't think the abbreviation is used yet.

    This was very much what OBAST did when it borrowed the concepts
    of CDMA active sets and put it over IP in 1998.  This was
    demonstrated with OBAST and SCTP/rspool (then called Quantix)
    running together by the Motorola Aspira Exploratory Testbed
    (core team was Randy Stewart, Xiaobing Xie, Peter Lei,
    & Phil Neumiller) at Geneva Telecom 99 with seven different air
    interface technologies happily talking to each other.  This
    was what got Vern Paxson interested in the first place in OBAST
    at the OBAST pre-BOF at the Australia IETF.

5). I have sent many flames and weird posting to the list.
    They must have seemed strange to folks that are new to the
    list and perhaps to even old timers that have really understood
    me due to my inability to communicate.  Hopefully we are all
    more enlightened now?  Take it light!


Thanks for reading this incredibly long email,

Phil Neumiller




From owner-seamoby@diameter.org  Fri Mar 23 23:52:30 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA12230
	for <seamoby-archive@odin.ietf.org>; Fri, 23 Mar 2001 23:52:29 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2O3uIO11290
	for seamoby-list; Fri, 23 Mar 2001 19:56:18 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2O3u5F11285
	for <seamoby@cdma-2000.org>; Fri, 23 Mar 2001 19:56:05 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id TAA29673;
	Fri, 23 Mar 2001 19:04:55 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f2O34ra26997;
	Fri, 23 Mar 2001 19:04:53 -0800
X-mProtect:  Fri, 23 Mar 2001 19:04:53 -0800 Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14166.americas.nokia.com (172.18.141.66, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdZi5K5s; Fri, 23 Mar 2001 19:04:46 PST
Message-ID: <3ABC0ECD.2787DA19@iprg.nokia.com>
Date: Fri, 23 Mar 2001 19:04:46 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Reply-To: Rajeev.Koodli@nokia.com
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: micke@CS.Arizona.EDU
CC: mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se, seamoby@cdma-2000.org
Subject: Re: [seamoby] Header compression context extablishment
References: <200103221925.f2MJPhM00633@baskerville.CS.Arizona.EDU>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello Mikael,

thanks for your e-mail. The text proposed in the CT problem statement draft,
which I contributed to, may not be complete. I think it was considered
adequate for -00.txt version of the draft. We could always use help from rohc
experts like yourself to improve upon.

Having said this, I don't agree with your overall characterization of the text
that it is not completely accurate. It perhaps needs to be elaborated for
U-mode and O-mode.  Even for these modes, I have questions for you to explain
why my text does not sufficiently capture the motivation needed for a CT
problem statement, which was its purpose to begin with!

I think it is pretty accurate for R-mode.

Regards,

-Rajeev

ps. there is a summary at the end of this e-mail :-)


micke@CS.Arizona.EDU wrote:

> To: mobile-ip@sunroof.eng.sun.com, seamoby@cdma-2000.org, rohc@cdt.luth.se
>
> Re: Header compression state establishment
> ==========================================
>
> Folks,
>
> It has come to my attention that some more or less
> informed statements have been made regarding header
> compression and how efficient/inefficient (re)establishment
> of header compression state might be.
>
> In particular, the statements made in
>
> draft-ietf-seamoby-context-transfer-problem-stat-00.txt
>
> are not completely accurate. This is an attempt to clarify the
> situation for the header compression methodology developed in the
> ROHC WG.
>

Reading your description below, it appears to me that the proposed text is
accurate for the R-mode, with the exception that the FO packet size would be 4
bytes. So, instead of characterizing the text as "not completely accurate", I
hope you would agree if it instead said "it is applicable to R-mode" (using
rohc terms). I appreciate your input so that we could cover all rohc cases
when we take up detailed work.


>
> The typical startup scenario for the ROHC header compression
> schemes for telephony streams is as follows:
>
> 1) send a small number of IR packets with a header size roughly similar
> to the header size of uncompressed headers. I expect that most
> implementations will send roughly 3 IR packets.

If I have voice packets to send at 20 ms intervals, and the link latency is 60
ms one-way, how is it that 3 IR packets are sufficient before I can receive an
Ack ?
Assuming that one of the 3 IR packets establishes "Static Context" at the
decompressor, that would take 3 IR packets worth of time. In order for the Ack
to reach the compressor, that would be another 3 IR packets worth of time. So
the total number of packets is 6 when link RTT is 120 ms, and 10 when link RTT
is 200 ms.  Isn't this correct ?

>
> If operating in U-mode or O-mode, this completes the context
> initialization, and minimal packets will be sent henceforth.
> U-mode can do an exponential backoff when sending IR packets,
> but the typical transition to O-mode or R-mode will prevent
> those IR packets from being sent.
>

What do you mean by saying that after sending 3 IR packets, context
initialization is completed ? Do you mean that the decompressor can transition
from

     No Context -> Static Context -> Full Context

in 3 IR packets ?

For U-mode, this is what the rohc draft says:

5.3.1.1.1
"The compressor normally obtains its confidence about decompressor
   status by sending several packets with the same information according
   to the lower compression state. If the decompressor receives any of
   these packets, it will be in sync with the compressor. The number of
   consecutive packets to send for confidence is not defined in this
   document."

I assume that you think sending 3 IR packets is sufficient for the compressor
to gain confidence to transition all the way to SO state. I cannot comment on
this in U-mode, however, I do have some input for the O-mode later.

Simply for everyone's convenience, I include the paragraph from the rohc draft
for U-mode, in which feedback channel from the decompressor to compressor is
not available.

5.3.1.1.2
"When the optimistic approach is taken as described above, there will
   always be a possibility of failure since the decompressor may not
   have received sufficient information for correct decompression.
   Therefore, the compressor MUST periodically transit to lower
   compression states. Periodic transition to the IR state SHOULD be
   carried out less often than transition to the FO state. Two different
   timeouts SHOULD therefore be used for these transitions. For an
   example of how to implement periodic refreshes, see [IPHC] chapters
   3.3.1-3.3.2."

Reading the above, it appears to me that in the U-mode, the compressor ends up
(re)initializing the context several times according to the period chosen. I
suppose it is ok to say that this does not favor better compression
efficiency, e.g., in cellular links.

Now to the O-mode. You mention that 3 IR packets are sufficient for the
compressor to ascertain that the decompressor has transitioned from "No
Context" to "Static Context" to "Full Context". When I read Section 5.4.2.2
(Feedback Logic (O-mode)), I observed that when the decompressor receives an
IR packet, it always sends an ACK.

"State Actions

   NC:  - When an IR packet passes the CRC check, send an ACK(O).
   ...

 SC:  - When an IR packet is correctly decompressed, send an ACK(O).
 ....

 FC:  - When an IR packet is correctly decompressed, send an ACK(O)."


What would be the purpose of sending this ACK for IR packets ? Perhaps to help
the compressor positively determine that the decompressor has received and
processed the IR packet ? If that is the case, then the compressor has to
obtain the ACK before transitioning to better state. Going with 120 ms RTT, in
order for this ACK to come back, it would take _6_ packets (IR). Isn't this
right ?
Also, I don't know if the ACK gives sufficient confidence for the compressor
to jump from IR state directly to SO state without going through the FO
state..


>
> If operation in R-mode is desired, the minimal packets will be
> sent until an acknowledgment (containing a mode transition request)
> reaches the compressor. Then,
>
> 2) during an additional roundtrip, non-minimal headers are sent during
> transition to R-mode.
>

The R-mode works in lockstep with ACKs. So, the text in the CT problem
statement is right.

>
> Some parameters are as follows:
>
> link roundtrip for cellular: 120-200 milliseconds.
> (6-10 packets at 50 packets per second).
>
> Minimal headers are 1 byte.
>
> Header size in 2) is rougly 4 bytes.
>

Thanks for clarifying that size in 2) is 4 bytes. Thanks also for pointing out
the higher link latency (200 ms).


>
> The header sizes indicated above do not include context identifiers,
> which can be omitted completely for context identifier zero.
> Nor do they include the two-byte UDP checksum, which will not be sent at
> all if disabled. Nor do they include the two byte IPv4 Identifier,
> which will be sent as-is if it changes randomly. Reasonable IP stacks
> will have it change in increments of one, and then it will be
> completely removed.
>
> Hope this has helped to clarify the situation with regards to header
> compression and its context (re) initialization.
>

> Mikael Degermark
> Co-chair, ROHC WG

In summary,

1. I think that given the intent of the problem statement for HC context
relocation, the text served the purpose. It may not have been perfect,
however.

2. Context initialization is expensive in unreliable links. Since this has to
be done for _each_ packet stream individually, it gets worse with multiple
packets streams (such as with multimedia streams). It further exacerbates with
frequent handovers.

3. Context relocation, typically performed over high-speed wireline links,
provides a feasible alternative to context re-establishment during handovers.
It provides a mechanism to _seamlessly_ continue _all_ the compression
contexts belonging to the MN, along with performance benefits. I think this is
just right for seamoby to tackle!





From owner-seamoby@diameter.org  Sat Mar 24 16:32:01 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11177
	for <seamoby-archive@odin.ietf.org>; Sat, 24 Mar 2001 16:32:00 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2OKfWa13503
	for seamoby-list; Sat, 24 Mar 2001 12:41:32 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from optima.CS.Arizona.EDU (optima.CS.Arizona.EDU [192.12.69.5])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2OKfUF13498
	for <seamoby@cdma-2000.org>; Sat, 24 Mar 2001 12:41:30 -0800
Received: from baskerville.CS.Arizona.EDU (baskerville.CS.Arizona.EDU [192.12.69.35])
	by optima.CS.Arizona.EDU (8.11.1/8.11.1) with ESMTP id f2OJlIl13749;
	Sat, 24 Mar 2001 12:47:19 -0700 (MST)
Received: (from micke@localhost)
	by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id f2OJoNg19636;
	Sat, 24 Mar 2001 12:50:23 -0700 (MST)
Date: Sat, 24 Mar 2001 12:50:23 -0700 (MST)
From: Mikael Degermark <micke@CS.Arizona.EDU>
Message-Id: <200103241950.f2OJoNg19636@baskerville.CS.Arizona.EDU>
To: mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se, seamoby@cdma-2000.org
Subject: [seamoby] Compression startup behavior
Sender: owner-seamoby@diameter.org
Precedence: bulk

To: mobile-ip@sunroof.eng.sun.com, seamoby@cdma-2000.org, rohc@cdt.luth.se

Hi Rajeev, 

You are right that the text is a reasonable first approximation, 
but as it portrayed the situation to be somewhat worse than it
really is, I felt that it was prudent to help make it more accurate.

The reality of ROHC context establishment, according to the ROHC
spec, is as follows:

1) All new contexts MUST start out in U-mode. Thus, it is the U-mode
   rules that govern compressor behavior until feedback reaches the
   compressor. The ROHC spec says that the U-mode startup behavior
   is to send a small number of IR packets, followed by periodic
   repetition of IR packets. The period should be rather long. 
   The compressor MAY use an exponential backoff until the 
   periodic interval is reached. 

   The small number I picked, three, will be different for different
   implementations but is not completely unrealistic. It has nothing
   to do with whether an ack is received or not. This is U-mode.

2) Swithcing to R-mode or O-mode cannot happen until feedback 
   indicating that a mode switch is desired is received from the 
   decompressor. Thus, it can happen at the earliest after a
   roundtrip time, and so can happen after 6-10 packets with a 
   roundtrip of 120-200 milliseconds.

3) The decompressor will move to full-context state as soon as it
   receives any IR packet with complete information. 
   The default values for slopes, etc, have been picked such that
   telephony streams only need one such packet before minimal headers can 
   be decompressed correctly. If the actual values deviate from what is
   expected for telephony, two IR packets need to be received 
   before minimal headers can be decompressed correctly. 

4) It *is* possible for the compressor to go to SO state after
   sending only IR packets. Transition to SO state is governed by 
   whether a pattern has been established, and also IR packets can
   establish patterns as they can contain the dynamic part of the
   header. 

OK?

I think that the problems with the text was that it assumed that
the compressor started out in R-mode, and that IR packets could not
establish a pattern. Under those conditions, the text is correct.
Those are not the actual conditions, however.

Cheers, 

Micke










From owner-seamoby@diameter.org  Sun Mar 25 04:51:54 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA09492
	for <seamoby-archive@odin.ietf.org>; Sun, 25 Mar 2001 04:51:54 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2P8trK14982
	for seamoby-list; Sun, 25 Mar 2001 00:55:53 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sm10.texas.rr.com (sm10.texas.rr.com [24.93.35.222])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2P8tZF14977
	for <seamoby@cdma-2000.org>; Sun, 25 Mar 2001 00:55:36 -0800
Received: from localhost (cs2773-200.houston.rr.com [24.27.73.200])
	by sm10.texas.rr.com (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f2P81Bcl013083
	for <seamoby@cdma-2000.org>; Sun, 25 Mar 2001 02:02:39 -0600
Message-Id: <200103250802.f2P81Bcl013083@sm10.texas.rr.com>
X-Sender: hermag@excite.com
From: "hermag@excite.com" <hermag@excite.com>
To: seamoby@cdma-2000.org
Date: Sun, 25 Mar 2001 01:59:21 -0600
Subject: [seamoby] Would you like to recieve information on how to register your pet online for free?
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001__18516816_7161.35"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This is a Multipart MIME message.

------=_NextPart_000_001__18516816_7161.35
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit


------=_NextPart_000_001__18516816_7161.35
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT5VbnRpdGxlZCBEb2N1bWVudDwvdGl0bGU+DQo8bWV0
YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNl
dD1pc28tODg1OS0xIj4NCjwvaGVhZD4NCg0KPGJvZHkgYmdjb2xvcj0iI0ZGRkZGRiIgdGV4
dD0iIzAwMDAwMCI+DQo8cD5IZWxsbyE8L3A+DQo8cD5Xb3VsZCB5b3UgbGlrZSB0byBrbm93
IGhvdyB0byByZWdpc3RlciB5b3VyIHBldCBvbmxpbmUgZm9yIGZyZWU/PC9wPg0KPHA+SWYg
eW91IHdvdWxkIGxpa2UgdG8gYmUgcmVtb3ZlZCBmcm9tIGV2ZXIgcmVjZWl2aW5nIGFub3Ro
ZXIgZW1haWwgcGxlYXNlIHR5cGUgDQogIFJFTU9WRSBvbmx5IGluIHRoZSByZXR1cm4gc3Vi
amVjdCBoZWFkZXIuIFdlIHJlc3BlY3QgeW91ciByaWdodCB0byBwcml2YWN5LjwvcD4NCjxw
PklmIHlvdSB3b3VsZCBsaWtlIHRvIHJlY2VpdmUgbW9yZSBpbmZvcm1hdGlvbiBvbiBob3cg
dG8gcmVnaXN0ZXIgeW91ciBwZXQgZm9yIA0KICBmcmVlIGp1c3QgcmVwbHkgdG8gdGhpcyBl
bWFpbCBtZXNzYWdlIHdpdGggUExFQVNFIFNFTkQgSU5GTyBvbmx5IGluIHRoZSBzdWJqZWN0
IA0KICBoZWFkZXIuPC9wPg0KPHA+PC9wPg0KPHA+VGhhbmsgWW91PGJyPg0KPC9wPg0KPC9i
b2R5Pg0KPC9odG1sPg0K

------=_NextPart_000_001__18516816_7161.35--



From owner-seamoby@diameter.org  Sun Mar 25 16:10:56 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA13369
	for <seamoby-archive@odin.ietf.org>; Sun, 25 Mar 2001 16:10:55 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2PJaGY21760
	for seamoby-list; Sun, 25 Mar 2001 11:36:16 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2PJaEF21755
	for <seamoby@cdma-2000.org>; Sun, 25 Mar 2001 11:36:14 -0800
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2PIj6g01535
	for <seamoby@cdma-2000.org>; Sun, 25 Mar 2001 12:45:06 -0600 (CST)
Received: from daebh02nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T52823bc951ac12f257079@davir04nok.americas.nokia.com>;
 Sun, 25 Mar 2001 12:44:34 -0600
Received: by daebh02nok with Internet Mail Service (5.5.2652.78)
	id <GKS52JPA>; Sun, 25 Mar 2001 12:44:34 -0600
Message-ID: <B9CFA6CE8FFDD211A1FB0008C7894E4601A659BF@bseis01nok>
From: rajeev.koodli@nokia.com
To: micke@CS.Arizona.EDU, mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se,
        seamoby@cdma-2000.org
Subject: [seamoby] RE: [rohc] Compression startup behavior
Date: Sun, 25 Mar 2001 12:44:32 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


Hello Mikael,

thanks for the clarification. I have more questions below.

I get the feeling that if my text portrayed the compression initialization
behavior to be worse than the actual, your input seems to be inclining
towards the opposite! 

Regards,

-Rajeev

> 
> 
> To: mobile-ip@sunroof.eng.sun.com, seamoby@cdma-2000.org, 
> rohc@cdt.luth.se
> 
> Hi Rajeev, 
> 
> You are right that the text is a reasonable first approximation, 
> but as it portrayed the situation to be somewhat worse than it
> really is, I felt that it was prudent to help make it more accurate.
> 
> The reality of ROHC context establishment, according to the ROHC
> spec, is as follows:
> 
> 1) All new contexts MUST start out in U-mode. Thus, it is the U-mode
>    rules that govern compressor behavior until feedback reaches the
>    compressor. The ROHC spec says that the U-mode startup behavior
>    is to send a small number of IR packets, followed by periodic
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Well, the rohc draft mentions "several packets". 

Section 5.3.1.1.1
"The compressor normally obtains its confidence about decompressor
   status by sending several packets with the same information according
   to the lower compression state. If the decompressor receives any of
   these packets, it will be in sync with the compressor. The number of
   consecutive packets to send for confidence is not defined in this
   document. "

The basic problem is: how does the compressor know that the decompressor has
the Full Context ? If the answer is it need not, then you take a chance
after sending "pre-defined" number of packets, and roll-back with costly
operations when the decompressor does not have the Full Context (in the
U-mode you simply repeat the IR packets). If the answer requires that it has
to, then you wait for an ACK. 

>    repetition of IR packets. The period should be rather long. 
>    The compressor MAY use an exponential backoff until the 
>    periodic interval is reached. 
> 
>    The small number I picked, three, will be different for different
>    implementations but is not completely unrealistic. 
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

In other words, 3 is the best case with rather low probability of being
feasible in practice  ? You say here clearly that the initial number of IR
packets is implementation-dependent. Is there any consensus in rohc that
sending 3 IR packets is sufficient, especially in those links with high
error probabilities ? If yes, could you point me to any relevant document ? 


>It has nothing to do with whether an ack is received or not. This is
U-mode.
> 
> 2) Swithcing to R-mode or O-mode cannot happen until feedback 
>    indicating that a mode switch is desired is received from the 
>    decompressor. Thus, it can happen at the earliest after a
>    roundtrip time, and so can happen after 6-10 packets with a 
>    roundtrip of 120-200 milliseconds.
> 

An observation I have with your text here is that you don't mention when the
compressor transitions to FO/SO state after starting out in IR state in
U-mode. Could you please clarify ?


> 3) The decompressor will move to full-context state as soon as it
>    receives any IR packet with complete information. 
>    The default values for slopes, etc, have been picked such that
>    telephony streams only need one such packet before minimal 
> headers can 
>    be decompressed correctly. 

Could you explain to me how you can establish a slope with one packet ?


>If the actual values deviate 
> from what is
>    expected for telephony, two IR packets need to be received 
>    before minimal headers can be decompressed correctly. 
> 

Again, the problem is how does the compressor know that decompressor has the
required state ? In the rohc draft, the same is stated as "the compressor
must have sufficient confidence" or something alike.. I guess two approaches
discussed in rohc draft are

1. send several packets, transition to higher compression state, and repeat
IR packets (U-mode), or revert back to lower compression state when
compressor determines (through a NACK e.g.) that decompressor does not have
the required state (O-mode). 

2. compressor uses an ACK to gain the required confidence (R-mode). 

In both cases above, it appears that in order for the compressor to gain the
required confidence, several packets are needed, especially in a link with
higher error probabilities.
 

> 4) It *is* possible for the compressor to go to SO state after
>    sending only IR packets. Transition to SO state is governed by 
>    whether a pattern has been established, and also IR packets can
>    establish patterns as they can contain the dynamic part of the
>    header. 
>

Exactly the same point again: How does the compressor know that the IR
packets it transmitted definitively or almost certainly established the Full
Context at the decompressor ? 

I guess it is possible. I can also imagine when it is also *not* possible,
especially when you are operating under high error links such as those found
in cellular. 

 
> OK?
> 

Well somewhat.. I still have unanswered points above. Also, could you answer
the questions I had in my previous e-mail as well ?
 
> I think that the problems with the text was that it assumed that
> the compressor started out in R-mode, and that IR packets could not
> establish a pattern. Under those conditions, the text is correct.
> Those are not the actual conditions, however.
> 

Thanks for the clarification regarding every mode starting out in U-mode. 
Could you care to explain _what_ are the actual conditions (other than every
rohc implementation starting out in U-mode) ?

Do you agree with items 2 and 3 in my summary in the previous e-mail ? Here
they are again!

2. Context initialization is expensive in unreliable links. Since this has
to
be done for _each_ packet stream individually, it gets worse with multiple
packets streams (such as with multimedia streams). It further exacerbates
with
frequent handovers.

3. Context relocation, typically performed over high-speed wireline links,
provides a feasible alternative to context re-establishment during
handovers.
It provides a mechanism to _seamlessly_ continue _all_ the compression
contexts belonging to the MN, along with performance benefits. I think this
is
just right for seamoby to tackle!


> Cheers, 
> 
> Micke
> 
> 
> 
> 
> 
> 
> 
> 
> ---
> Mailing list for Robust Header Compression WG
> Archive: http://www.cdt.luth.se/rohc/
> 


From owner-seamoby@diameter.org  Mon Mar 26 11:39:25 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11792
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 11:39:24 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QEVFq24631
	for seamoby-list; Mon, 26 Mar 2001 06:31:15 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from atlsnmx1.nextel.com (atlsnmx1.nextel.com [167.20.198.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QEVCF24626
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 06:31:12 -0800
Received: from atlntgw01.nextel.com (atlntgw01.nextel.com [10.8.79.187])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id IAA16412
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 08:40:12 -0500 (EST)
Received: by atlntgw01.nextel.com with Internet Mail Service (5.5.2650.21)
	id <HKWN86D2>; Mon, 26 Mar 2001 08:40:28 -0500
Message-ID: <020A5EC56F3FD411B5230008C716D08506C9CD84@nhqntex01.nextel.com>
From: "Martin, David P" <David.P.Martin@nextel.com>
To: seamoby@diameter.org
Subject: [seamoby] L2/L3 Paging
Date: Mon, 26 Mar 2001 08:35:21 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

At the meeting in Minnesota, there was a question that basically asked
"Should seamoby paging *require* L2 Paging be present".  Consensus was no
...  I think a better question to ask would be "Should seamoby *assume* that
layer 2 has knowledge of the location of the MN".  I think (perhaps I'm
wrong), that the answer to the latter question would be yes.

I'm not sure how you can have a link without knowing where you are sending
stuff.  I am a little concerned that the paging team may be attempting to
solve a very difficult problem that will never exist.

(Administrative note - Message sent to the seamboy list due to the workgroup
consensus issue)


From owner-seamoby@diameter.org  Mon Mar 26 13:01:03 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA13264
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 13:01:03 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QH2fK25043
	for seamoby-list; Mon, 26 Mar 2001 09:02:41 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QH1OF25038
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 09:01:24 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id IAA05599;
	Mon, 26 Mar 2001 08:10:42 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADC09211;
	Mon, 26 Mar 2001 08:10:20 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id IAA02484; Mon, 26 Mar 2001 08:10:20 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15039.27116.288962.432432@thomasm-u1.cisco.com>
Date: Mon, 26 Mar 2001 08:10:20 -0800 (PST)
To: "Martin, David P" <David.P.Martin@nextel.com>
Cc: seamoby@diameter.org
Subject: [seamoby] L2/L3 Paging
In-Reply-To: <020A5EC56F3FD411B5230008C716D08506C9CD84@nhqntex01.nextel.com>
References: <020A5EC56F3FD411B5230008C716D08506C9CD84@nhqntex01.nextel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Martin, David P writes:
 > At the meeting in Minnesota, there was a question that basically asked
 > "Should seamoby paging *require* L2 Paging be present".  Consensus was no
 > ...  I think a better question to ask would be "Should seamoby *assume* that
 > layer 2 has knowledge of the location of the MN".  I think (perhaps I'm
 > wrong), that the answer to the latter question would be yes.

   I don't see why we should assume that. If a mobile
   is dormant, we probably know its last attachment 
   point, but that doesn't mean that the L2 must 
   track its movement accurately. In fact, I'd say
   that that should be an explicit *non-goal* as it
   would allow the MN to sleep for longer periods.

 > I'm not sure how you can have a link without knowing where you are sending
 > stuff.  I am a little concerned that the paging team may be attempting to
 > solve a very difficult problem that will never exist.

   This doesn't seem to hard: suppose you have a
   beacon which all dormant nodes listen too. To
   find a node, the last attachment point performs
   a search in the local paging area. When the mobile
   wakes up, it establishes a link to its current AP,
   and a tunnel to the old AP to scoop up the
   packet(s).

   What am I missing?

	   Mike


From owner-seamoby@diameter.org  Mon Mar 26 13:49:07 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA14043
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 13:49:06 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QIaWW25362
	for seamoby-list; Mon, 26 Mar 2001 10:36:32 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from atlsnmx1.nextel.com (atlsnmx1.nextel.com [167.20.198.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QIaTF25357
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 10:36:30 -0800
Received: from atlntgw01.nextel.com (atlntgw01.nextel.com [10.8.79.187])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id MAA16611;
	Mon, 26 Mar 2001 12:45:30 -0500 (EST)
Received: by atlntgw01.nextel.com with Internet Mail Service (5.5.2650.21)
	id <HKWN988N>; Mon, 26 Mar 2001 12:45:45 -0500
Message-ID: <020A5EC56F3FD411B5230008C716D085868504@nhqntex01.nextel.com>
From: "Martin, David P" <David.P.Martin@nextel.com>
To: "'Michael Thomas'" <mat@cisco.com>,
        "Martin, David P"
	 <David.P.Martin@nextel.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
Date: Mon, 26 Mar 2001 12:40:30 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

<Snipping my question on whether we should assume L2 know the location of
the MN>

>    I don't see why we should assume that. If a mobile
>    is dormant, we probably know its last attachment 
>    point, but that doesn't mean that the L2 must 
>    track its movement accurately.

OK, I agree so far, as long as the L2 tracking granularity is finer than L3.

>    In fact, I'd say
>    that that should be an explicit *non-goal* as it
>    would allow the MN to sleep for longer periods.

<snipping more of my comments concerning level of difficutly>

>    This doesn't seem to hard: suppose you have a
>    beacon which all dormant nodes listen too. To
>    find a node, the last attachment point performs
>    a search in the local paging area. When the mobile
>    wakes up, it establishes a link to its current AP,
>    and a tunnel to the old AP to scoop up the
>    packet(s).

I agree that a paging system can be designed that can work with a technology
that does not continually track a MN location.

However, a (working) paging system *cannot* be designed without a
registration mechanism.  The purpose of a registration mechanism is to
provide rough location state information on where a MN is located in a
network topology.  This location state can be of several forms, specific
access point, specific paging zone, specific network (scalability issues),
last known access point, last known access zone, etc.  But the network has
to have some type of location information to even begin to guess on how to
start paging.  In your example above, the mobile in effect registers upon
wake up, giving the network location state to work with.  Of course a
mechanism must exist (at one or more layers) to deal with stale location
information.

So, I'm trying to say that there must be some location state maintained
somewhere at layer 2, otherwise the entire network would behave as one big
LAN segment.



 


From owner-seamoby@diameter.org  Mon Mar 26 14:06:06 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA14350
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 14:06:05 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QI5Xb25255
	for seamoby-list; Mon, 26 Mar 2001 10:05:33 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QI5VF25250
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 10:05:31 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA10149;
	Mon, 26 Mar 2001 09:14:30 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA18812;
	Mon, 26 Mar 2001 09:14:30 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id JAA14295;
	Mon, 26 Mar 2001 09:14:29 -0800 (PST)
Message-Id: <200103261714.JAA14295@heliopolis.Eng.Sun.COM>
Date: Mon, 26 Mar 2001 09:14:29 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: Re: [seamoby] L2/L3 Paging
To: David.P.Martin@nextel.com, mat@cisco.com
Cc: seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 89GI7dFAaYMB7xkO/IoGOQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Dave/Mike/All,

>Martin, David P writes:
> > At the meeting in Minnesota, there was a question that basically asked
> > "Should seamoby paging *require* L2 Paging be present".  Consensus was no
> > ...  I think a better question to ask would be "Should seamoby *assume* that
> > layer 2 has knowledge of the location of the MN".  I think (perhaps I'm
> > wrong), that the answer to the latter question would be yes.
>
>   I don't see why we should assume that. If a mobile
>   is dormant, we probably know its last attachment 
>   point, but that doesn't mean that the L2 must 
>   track its movement accurately. In fact, I'd say
>   that that should be an explicit *non-goal* as it
>   would allow the MN to sleep for longer periods.
>
> > I'm not sure how you can have a link without knowing where you are sending
> > stuff.  I am a little concerned that the paging team may be attempting to
> > solve a very difficult problem that will never exist.
>
>   This doesn't seem to hard: suppose you have a
>   beacon which all dormant nodes listen too. To
>   find a node, the last attachment point performs
>   a search in the local paging area. When the mobile
>   wakes up, it establishes a link to its current AP,
>   and a tunnel to the old AP to scoop up the
>   packet(s).
>

My interpretation of the working group discussion and concensus is that an IP 
paging protocol should not require L2 paging. However, I don't think there
is any reason why it should not be designed to allow use of L2 paging
if there. To not do so would be putting unwise constraints on
implementors.

I'd like to suggest that the requirement read something like:

	The IP paging protocol shall utilize L2 paging support if available,
	but shall not require L2 paging. 
	

		jak




From owner-seamoby@diameter.org  Mon Mar 26 14:53:37 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15042
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 14:53:37 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QJ3j325448
	for seamoby-list; Mon, 26 Mar 2001 11:03:45 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QJ3hF25443
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 11:03:43 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA23676;
	Mon, 26 Mar 2001 10:12:41 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA11199;
	Mon, 26 Mar 2001 10:12:40 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id KAA15985;
	Mon, 26 Mar 2001 10:12:40 -0800 (PST)
Message-Id: <200103261812.KAA15985@heliopolis.Eng.Sun.COM>
Date: Mon, 26 Mar 2001 10:12:40 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: Registration (was RE: [seamoby] L2/L3 Paging)
To: mat@cisco.com, David.P.Martin@nextel.com
Cc: seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: zaEukLqxn12GvgXSXjNVpg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Dave,

>>    I don't see why we should assume that. If a mobile
>>    is dormant, we probably know its last attachment 
>>    point, but that doesn't mean that the L2 must 
>>    track its movement accurately.
>
>OK, I agree so far, as long as the L2 tracking granularity is finer than L3.
>

I think the whole point of paging is that the location is tracked somewhat
less accurately in dormant mode than in active mode. Otherwise, why
bother with paging? The mobile node could simply continue to do
active mode location tracking. Making it less accurate requires less
signalling, allowing the dormant mode mobile more sleep time, saving
battery.

>I agree that a paging system can be designed that can work with a technology
>that does not continually track a MN location.
>
>However, a (working) paging system *cannot* be designed without a
>registration mechanism.  The purpose of a registration mechanism is to
>provide rough location state information on where a MN is located in a
>network topology.  This location state can be of several forms, specific
>access point, specific paging zone, specific network (scalability issues),
>last known access point, last known access zone, etc.  But the network has
>to have some type of location information to even begin to guess on how to
>start paging.  In your example above, the mobile in effect registers upon
>wake up, giving the network location state to work with.  Of course a
>mechanism must exist (at one or more layers) to deal with stale location
>information.
>

So it sounds like a requirement for the mobile node to register with
the network at some point prior to going into dormant mode? The exact
point at which the registration is made may depend on whether a timeout based 
mechanism or an explicit notification mechanism is used at L2 to determine
whether the mobile node has gone into dormant mode.

>So, I'm trying to say that there must be some location state maintained
>somewhere at layer 2, otherwise the entire network would behave as one big
>LAN segment.

I don't necessarily think this needs to be at L2. MIP registration, for
example, would fill the bill.


		jak



From owner-seamoby@diameter.org  Mon Mar 26 14:56:52 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15129
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 14:56:51 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QJBTX25482
	for seamoby-list; Mon, 26 Mar 2001 11:11:29 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QJBRF25477
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 11:11:27 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id KAA21041;
	Mon, 26 Mar 2001 10:20:30 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADC12365;
	Mon, 26 Mar 2001 10:20:24 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA02505; Mon, 26 Mar 2001 10:20:24 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15039.34920.167195.403437@thomasm-u1.cisco.com>
Date: Mon, 26 Mar 2001 10:20:24 -0800 (PST)
To: "Martin, David P" <David.P.Martin@nextel.com>
Cc: "'Michael Thomas'" <mat@cisco.com>, seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
In-Reply-To: <020A5EC56F3FD411B5230008C716D085868504@nhqntex01.nextel.com>
References: <020A5EC56F3FD411B5230008C716D085868504@nhqntex01.nextel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Martin, David P writes:
 > >    This doesn't seem to hard: suppose you have a
 > >    beacon which all dormant nodes listen too. To
 > >    find a node, the last attachment point performs
 > >    a search in the local paging area. When the mobile
 > >    wakes up, it establishes a link to its current AP,
 > >    and a tunnel to the old AP to scoop up the
 > >    packet(s).
 > 
 > I agree that a paging system can be designed that can work with a technology
 > that does not continually track a MN location.
 > 
 > However, a (working) paging system *cannot* be designed without a
 > registration mechanism.

   Sure.

 > The purpose of a registration mechanism is to
 > provide rough location state information on where a MN is located in a
 > network topology.  This location state can be of several forms, specific
 > access point, specific paging zone, specific network (scalability issues),
 > last known access point, last known access zone, etc.  But the network has
 > to have some type of location information to even begin to guess on how to
 > start paging.

   Correct.

 > In your example above, the mobile in effect registers upon
 > wake up, giving the network location state to work with.  Of course a
 > mechanism must exist (at one or more layers) to deal with stale location
 > information.

   Yup.
 
 > So, I'm trying to say that there must be some location state maintained
 > somewhere at layer 2, otherwise the entire network would behave as one big
 > LAN segment.

   I don't see this as having much to do with L2. If
   I can route an IP packet to the last known point
   of attachment, it could put out the dragnet by
   sending out IP packets which eventually (or not)
   find the mobile node. L2 location information may
   or may not be involved. At a base level, I don't
   think we should count on them being there though.

	    Mike


From owner-seamoby@diameter.org  Mon Mar 26 14:58:59 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15222
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 14:58:59 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QJJRI25524
	for seamoby-list; Mon, 26 Mar 2001 11:19:27 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QJJPF25519
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 11:19:25 -0800
Received: from hoemail2.firewall.lucent.com (localhost [127.0.0.1])
	by hoemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id NAA15052
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 13:28:29 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-160-150.lucent.com [135.86.160.150])
	by hoemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id NAA15036
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 13:28:29 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2650.21)
	id <H2VDZAWH>; Mon, 26 Mar 2001 19:28:28 +0100
Message-ID: <976F7C55E3B2D111A0720008C728549C097CC21C@en0060exch001u.uk.lucent.com>
From: "Casati, Alessio (Alessio)" <acasati@lucent.com>
To: "'Martin, David P'" <David.P.Martin@nextel.com>, seamoby@diameter.org
Subject: Re: [seamoby] L2/L3 Paging
Date: Mon, 26 Mar 2001 19:28:23 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



At the meeting in Minnesota, there was a question that basically asked
"Should seamoby paging *require* L2 Paging be present".  Consensus was "no"

L2 paging is a L2 requirement (not driven by
upper layers, rather by other considerations of 
a different nature).

...  I think a better question to ask would be "Should seamoby *assume* that
layer 2 has knowledge of the location of the MN".  I think (perhaps I'm
wrong), that the answer to the latter question would be yes.

The L2 performs L3 delivery functions. This entails knowledge of the link(s)
onto which to forward the L3 PDU in Non broadcast media, or the L2 (MAC)
address in 
broadcast media. Some degree of location knowledge does come with it.




From owner-seamoby@diameter.org  Mon Mar 26 15:34:56 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA15913
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 15:34:56 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QK7oq25675
	for seamoby-list; Mon, 26 Mar 2001 12:07:50 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QK7kF25670
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 12:07:46 -0800
Received: from auemail2.firewall.lucent.com (localhost [127.0.0.1])
	by auemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id OAA27402
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 14:16:50 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-160-150.lucent.com [135.86.160.150])
	by auemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id OAA27369
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 14:16:49 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2650.21)
	id <H2VDZBPB>; Mon, 26 Mar 2001 20:16:48 +0100
Message-ID: <976F7C55E3B2D111A0720008C728549C097CC21E@en0060exch001u.uk.lucent.com>
From: "Casati, Alessio (Alessio)" <acasati@lucent.com>
To: "'Michael Thomas'" <mat@cisco.com>,
        "Martin, David P"
	 <David.P.Martin@nextel.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
Date: Mon, 26 Mar 2001 20:16:45 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk



Martin, David P writes:
 > At the meeting in Minnesota, there was a question that basically asked
 > "Should seamoby paging *require* L2 Paging be present".  Consensus was no
 > ...  I think a better question to ask would be "Should seamoby *assume*
that
 > layer 2 has knowledge of the location of the MN".  I think (perhaps I'm
 > wrong), that the answer to the latter question would be yes.

   I don't see why we should assume that. If a mobile
   is dormant, we probably know its last attachment 
   point, but that doesn't mean that the L2 must 
   track its movement accurately. In fact, I'd say
   that that should be an explicit *non-goal* as it
   would allow the MN to sleep for longer periods.

The mobile can "L2-sleep" until it gets alerted of the fact L2 would loose
track of it. Then, it sort of "L2-wakes up" (on the L2 C-Plane), 
updates the L2 about its new location
and then it can "L2-sleep" again. 


 > I'm not sure how you can have a link without knowing where you are
sending
 > stuff.  I am a little concerned that the paging team may be attempting to
 > solve a very difficult problem that will never exist.

   This doesn't seem to hard: suppose you have a
   beacon which all dormant nodes listen too. 

No L2 dormant node can listen to L3 beacons.
Unless dormant means something else here (or the beacons are not L3).

   To find a node, the last attachment point performs
   a search in the local paging area.

What if the mobile is not in that L3 paging area anymore?
Or, how would a dormant mobile know it has crossed
a L3 Paging area? L3
paging needs its applicability to be specified
with this respect (and put requirements on L2/L3 coordination,
I guess).


alessio
   


From owner-seamoby@diameter.org  Mon Mar 26 15:54:09 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA16378
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 15:54:09 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QKWON25748
	for seamoby-list; Mon, 26 Mar 2001 12:32:24 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QKWLF25743
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 12:32:21 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id LAA07990;
	Mon, 26 Mar 2001 11:41:42 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADC15111;
	Mon, 26 Mar 2001 11:41:19 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA02515; Mon, 26 Mar 2001 11:41:19 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15039.39775.207050.666123@thomasm-u1.cisco.com>
Date: Mon, 26 Mar 2001 11:41:19 -0800 (PST)
To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Cc: David.P.Martin@nextel.com, mat@cisco.com, seamoby@diameter.org
Subject: Re: [seamoby] L2/L3 Paging
In-Reply-To: <200103261714.JAA14295@heliopolis.Eng.Sun.COM>
References: <200103261714.JAA14295@heliopolis.Eng.Sun.COM>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

James Kempf writes:
 > I'd like to suggest that the requirement read something like:
 > 
 > 	The IP paging protocol shall utilize L2 paging support if available,
 > 	but shall not require L2 paging. 

   I'm hair splitting here, but we MUST use it? It 
   seems to me that what we really want is that 
   IP paging not inhibit the use of L2 paging 
   mechanisms as appropriate for that L2. Otherwise,
   we might be inhibiting the ability to develop
   native IP paging mechanisms in the future, which
   I'll guess is not your intent.

	      Mike


From owner-seamoby@diameter.org  Mon Mar 26 16:39:51 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA17074
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 16:39:51 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QKrE825839
	for seamoby-list; Mon, 26 Mar 2001 12:53:15 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QKrBF25834
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 12:53:11 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-3.cisco.com (8.9.3/8.9.1) with ESMTP id MAA13776;
	Mon, 26 Mar 2001 12:00:53 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADC15712;
	Mon, 26 Mar 2001 12:02:07 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id MAA02526; Mon, 26 Mar 2001 12:02:06 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15039.41022.749574.539986@thomasm-u1.cisco.com>
Date: Mon, 26 Mar 2001 12:02:06 -0800 (PST)
To: "Casati, Alessio (Alessio)" <acasati@lucent.com>
Cc: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>, mat@cisco.com,
        David.P.Martin@nextel.com, seamoby@diameter.org
Subject: RE: Registration (was RE: [seamoby] L2/L3 Paging)
In-Reply-To: <976F7C55E3B2D111A0720008C728549C097CC221@en0060exch001u.uk.lucent.com>
References: <976F7C55E3B2D111A0720008C728549C097CC221@en0060exch001u.uk.lucent.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Casati, Alessio (Alessio) writes:
 > 
 > I don't necessarily think this needs to be at L2. MIP registration, for
 > example, would fill the bill.
 > 
 > But MIP registration implies there is an active L3 connectivity end to end,
 > or L2 paging is in place to wake up a dormant node and then deliver
 > IP packets...

   I guess that depends on your definition of "active".
   Active in the MIP sense means that the state is
   still resident on the thing that keeps the binding.
   It doesn't imply that you move packets around.

   Also: L3 "connectivity" can be transient with respect
   to L2 connectivity. I can, for example, unplug my
   ethernet cable from my laptop and plug it back in
   only when I want service. The upper layer IP stack
   doesn't care much about this: the only time it cares
   is when it needs to send/receive a packet. I think
   the same applies here.

	      Mike


From owner-seamoby@diameter.org  Mon Mar 26 16:54:27 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA17641
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 16:54:26 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QLC6n25906
	for seamoby-list; Mon, 26 Mar 2001 13:12:06 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from alemail1.firewall.lucent.com (alemail1.lucent.com [192.11.221.161])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QLC4F25901
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 13:12:04 -0800
Received: from alemail1.firewall.lucent.com (localhost [127.0.0.1])
	by alemail1.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id PAA16098
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 15:21:08 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-160-150.lucent.com [135.86.160.150])
	by alemail1.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id PAA16077
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 15:21:08 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2650.21)
	id <H2VDZCJV>; Mon, 26 Mar 2001 21:21:07 +0100
Message-ID: <976F7C55E3B2D111A0720008C728549C097CC222@en0060exch001u.uk.lucent.com>
From: "Casati, Alessio (Alessio)" <acasati@lucent.com>
To: "'Michael Thomas'" <mat@cisco.com>
Cc: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>, David.P.Martin@nextel.com,
        seamoby@diameter.org
Subject: RE: Registration (was RE: [seamoby] L2/L3 Paging)
Date: Mon, 26 Mar 2001 21:21:01 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk

 > But MIP registration implies there is an active L3 connectivity end to
end,
 > or L2 paging is in place to wake up a dormant node and then deliver
 > IP packets...

   I guess that depends on your definition of "active".
   Active in the MIP sense means that the state is
   still resident on the thing that keeps the binding.
   It doesn't imply that you move packets around.

Exactly. But when there is no link we may have 2 cases:
the link can be re-established via L2 paging, or the packets (when they do 
need to be delivered) get dropped
for a while, and then timers will do the rest.

   Also: L3 "connectivity" can be transient with respect
   to L2 connectivity. I can, for example, unplug my
   ethernet cable from my laptop and plug it back in
   only when I want service.
   The upper layer IP stack
   doesn't care much about this: the only time it cares
   is when it needs to send/receive a packet. 

Which is a case we should quite care about :).



From owner-seamoby@diameter.org  Mon Mar 26 16:54:53 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA17659
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 16:54:52 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QKep925811
	for seamoby-list; Mon, 26 Mar 2001 12:40:51 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from hoemlsrv.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QKelF25806
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 12:40:47 -0800
Received: from hoemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id OAA03005
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 14:49:51 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-160-150.lucent.com [135.86.160.150])
	by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id OAA02965
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 14:49:51 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2650.21)
	id <H2VDZB6P>; Mon, 26 Mar 2001 20:49:49 +0100
Message-ID: <976F7C55E3B2D111A0720008C728549C097CC221@en0060exch001u.uk.lucent.com>
From: "Casati, Alessio (Alessio)" <acasati@lucent.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>, mat@cisco.com,
        David.P.Martin@nextel.com
Cc: seamoby@diameter.org
Subject: RE: Registration (was RE: [seamoby] L2/L3 Paging)
Date: Mon, 26 Mar 2001 20:49:47 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk


I don't necessarily think this needs to be at L2. MIP registration, for
example, would fill the bill.

But MIP registration implies there is an active L3 connectivity end to end,
or L2 paging is in place to wake up a dormant node and then deliver
IP packets...


From owner-seamoby@diameter.org  Mon Mar 26 17:04:07 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA18486
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 17:04:07 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QKcY725775
	for seamoby-list; Mon, 26 Mar 2001 12:38:34 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QKcVF25768
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 12:38:31 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA15748;
	Mon, 26 Mar 2001 11:47:33 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA24702;
	Mon, 26 Mar 2001 11:47:32 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id LAA18852;
	Mon, 26 Mar 2001 11:47:32 -0800 (PST)
Message-Id: <200103261947.LAA18852@heliopolis.Eng.Sun.COM>
Date: Mon, 26 Mar 2001 11:47:32 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: Re: [seamoby] L2/L3 Paging
To: mat@cisco.com
Cc: David.P.Martin@nextel.com, mat@cisco.com, seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: J/WPWPFOSV97KVoSVapYew==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

I think the wording should capture a requirement to MUST use L2 paging
if available, but that it SHOULD NOT be required to be available.

		jak

>From: Michael Thomas <mat@cisco.com>
>MIME-Version: 1.0
>Content-Transfer-Encoding: 7bit
>Date: Mon, 26 Mar 2001 11:41:19 -0800 (PST)
>To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
>Cc: David.P.Martin@nextel.com, mat@cisco.com, seamoby@diameter.org
>Subject: Re: [seamoby] L2/L3 Paging
>X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk 
@RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd 
bUcI'1!
>
>James Kempf writes:
> > I'd like to suggest that the requirement read something like:
> > 
> > 	The IP paging protocol shall utilize L2 paging support if available,
> > 	but shall not require L2 paging. 
>
>   I'm hair splitting here, but we MUST use it? It 
>   seems to me that what we really want is that 
>   IP paging not inhibit the use of L2 paging 
>   mechanisms as appropriate for that L2. Otherwise,
>   we might be inhibiting the ability to develop
>   native IP paging mechanisms in the future, which
>   I'll guess is not your intent.
>
>	      Mike



From owner-seamoby@diameter.org  Mon Mar 26 17:19:53 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA19047
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 17:19:53 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QLonL26014
	for seamoby-list; Mon, 26 Mar 2001 13:50:49 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from alemail1.firewall.lucent.com (alemail1.lucent.com [192.11.221.161])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QLokF26009
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 13:50:46 -0800
Received: from alemail1.firewall.lucent.com (localhost [127.0.0.1])
	by alemail1.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id PAA24970
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 15:59:51 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-160-150.lucent.com [135.86.160.150])
	by alemail1.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id PAA24961
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 15:59:50 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2650.21)
	id <H2VDZC7A>; Mon, 26 Mar 2001 21:59:46 +0100
Message-ID: <976F7C55E3B2D111A0720008C728549C097CC225@en0060exch001u.uk.lucent.com>
From: "Casati, Alessio (Alessio)" <acasati@lucent.com>
To: "'Michael Thomas'" <mat@cisco.com>
Cc: seamoby@diameter.org
Subject: RE: Registration (was RE: [seamoby] L2/L3 Paging)
Date: Mon, 26 Mar 2001 21:59:37 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk


 > 
 > Exactly. But when there is no link we may have 2 cases:
 > the link can be re-established via L2 paging, or the packets (when they
do 
 > need to be delivered) get dropped
 > for a while, and then timers will do the rest.
 
   I believe that there is a third possibility:
   The paging interface allows delivery of IP 
   datagrams. None of these exist, as far as I 
   know, but that doesn't preclude some clever
   radio-heads from doing so :-)

		   Mike


The 2 I mentioned (packet drop or link re-establishments) do exist.
I agree the third way may not exist (ever).


alessio


From owner-seamoby@diameter.org  Mon Mar 26 17:45:17 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA19737
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 17:45:17 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QM6Tw26071
	for seamoby-list; Mon, 26 Mar 2001 14:06:29 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QM6QF26065
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 14:06:26 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id NAA03603;
	Mon, 26 Mar 2001 13:15:29 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADC17860;
	Mon, 26 Mar 2001 13:15:23 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id NAA02554; Mon, 26 Mar 2001 13:15:23 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15039.45419.182234.602445@thomasm-u1.cisco.com>
Date: Mon, 26 Mar 2001 13:15:23 -0800 (PST)
To: "Casati, Alessio (Alessio)" <acasati@lucent.com>
Cc: "'Michael Thomas'" <mat@cisco.com>, seamoby@diameter.org
Subject: RE: Registration (was RE: [seamoby] L2/L3 Paging)
In-Reply-To: <976F7C55E3B2D111A0720008C728549C097CC225@en0060exch001u.uk.lucent.com>
References: <976F7C55E3B2D111A0720008C728549C097CC225@en0060exch001u.uk.lucent.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Casati, Alessio (Alessio) writes:
 > 
 >  > 
 >  > Exactly. But when there is no link we may have 2 cases:
 >  > the link can be re-established via L2 paging, or the packets (when they
 > do 
 >  > need to be delivered) get dropped
 >  > for a while, and then timers will do the rest.
 >  
 >    I believe that there is a third possibility:
 >    The paging interface allows delivery of IP 
 >    datagrams. None of these exist, as far as I 
 >    know, but that doesn't preclude some clever
 >    radio-heads from doing so :-)
 > 
 > 		   Mike
 > 
 > 
 > The 2 I mentioned (packet drop or link re-establishments) do exist.
 > I agree the third way may not exist (ever).

   _Ever_? That's a pretty strong statement.
   That implies that shipping IP packets down
   some sort of paging interface is just a
   generally bad idea. I haven't heard anybody
   give any reasoning of why that might be.

	Mike


From owner-seamoby@diameter.org  Mon Mar 26 18:25:50 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20222
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 18:25:49 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2QLObP25942
	for seamoby-list; Mon, 26 Mar 2001 13:24:37 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2QLOYF25937
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 13:24:34 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id MAA04543;
	Mon, 26 Mar 2001 12:33:37 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADC16655;
	Mon, 26 Mar 2001 12:33:31 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id MAA02540; Mon, 26 Mar 2001 12:33:31 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15039.42907.639326.11360@thomasm-u1.cisco.com>
Date: Mon, 26 Mar 2001 12:33:31 -0800 (PST)
To: "Casati, Alessio (Alessio)" <acasati@lucent.com>
Cc: "'Michael Thomas'" <mat@cisco.com>,
        "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        David.P.Martin@nextel.com, seamoby@diameter.org
Subject: RE: Registration (was RE: [seamoby] L2/L3 Paging)
In-Reply-To: <976F7C55E3B2D111A0720008C728549C097CC222@en0060exch001u.uk.lucent.com>
References: <976F7C55E3B2D111A0720008C728549C097CC222@en0060exch001u.uk.lucent.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Casati, Alessio (Alessio) writes:
 >  > But MIP registration implies there is an active L3 connectivity end to
 > end,
 >  > or L2 paging is in place to wake up a dormant node and then deliver
 >  > IP packets...
 > 
 >    I guess that depends on your definition of "active".
 >    Active in the MIP sense means that the state is
 >    still resident on the thing that keeps the binding.
 >    It doesn't imply that you move packets around.
 > 
 > Exactly. But when there is no link we may have 2 cases:
 > the link can be re-established via L2 paging, or the packets (when they do 
 > need to be delivered) get dropped
 > for a while, and then timers will do the rest.
 
   I believe that there is a third possibility:
   The paging interface allows delivery of IP 
   datagrams. None of these exist, as far as I 
   know, but that doesn't preclude some clever
   radio-heads from doing so :-)

		   Mike


From owner-seamoby@diameter.org  Mon Mar 26 19:55:10 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA23181
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 19:55:10 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2R0bnO26595
	for seamoby-list; Mon, 26 Mar 2001 16:37:49 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2R0blF26590
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 16:37:47 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA06088
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 15:46:52 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA25606
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 15:46:51 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id PAA24916
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 15:46:51 -0800 (PST)
Message-Id: <200103262346.PAA24916@heliopolis.Eng.Sun.COM>
Date: Mon, 26 Mar 2001 15:46:51 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: [seamoby] Confusion about Seamoby Goals
Cc: seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: G/DzKRMi4T/QwYC+JZTgZw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Kulwinder,


>What is the compelling reason to link a WAN Cellular Paging protocol to a
>general IP Context Transfer 'toolkit'?
>

Nobody is proposing to link paging to context transfer. These two
topics were just thrown together into Seamoby because there was too
much work in mobile IP to handle them. As far as I am concerned, they
are completely unrelated.

Your comment is the second time today somebody has brought this up.

		jak



From owner-seamoby@diameter.org  Mon Mar 26 20:19:42 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23776
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 20:19:42 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2R0SrY26569
	for seamoby-list; Mon, 26 Mar 2001 16:28:53 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2R0SpF26564
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 16:28:52 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4SYHA>; Mon, 26 Mar 2001 18:37:56 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A91@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Michael Thomas'" <mat@cisco.com>,
        "Casati, Alessio (Alessio)"
	 <acasati@lucent.com>
Cc: seamoby@diameter.org
Subject: RE: Registration (was RE: [seamoby] L2/L3 Paging)
Date: Mon, 26 Mar 2001 18:37:46 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Michael Thomas [mailto:mat@cisco.com]
> Sent: Monday, March 26, 2001 4:15 PM
> To: Casati, Alessio (Alessio)
> Cc: 'Michael Thomas'; seamoby@diameter.org
> Subject: RE: Registration (was RE: [seamoby] L2/L3 Paging)
> 
> 
> Casati, Alessio (Alessio) writes:
>  > 
>  >  > 
>  >  > Exactly. But when there is no link we may have 2 cases:
>  >  > the link can be re-established via L2 paging, or the 
> packets (when they
>  > do 
>  >  > need to be delivered) get dropped
>  >  > for a while, and then timers will do the rest.
>  >  
>  >    I believe that there is a third possibility:
>  >    The paging interface allows delivery of IP 
>  >    datagrams. None of these exist, as far as I 
>  >    know, but that doesn't preclude some clever
>  >    radio-heads from doing so :-)
>  > 
>  > 		   Mike
>  > 
>  > 
>  > The 2 I mentioned (packet drop or link re-establishments) do exist.
>  > I agree the third way may not exist (ever).
> 

Not only can it exist.  It does exist.  Take a look at how Piconet Broadcast
works for dormant devices (parked) in Bluetooth.  Further, a device may
power down everything but a small portion of the reciever.  The reciever can
trigger on the L2 address to wake up the rest of the chip/device.

It is clear that a paging protocol is only useful for Commercial Cellular
technologies that:

1. Use Paging as a substitute for routing.

2. Use Paging as a substitute for a power efficient hardware design.

Bluetooth transmissions are timer driven and based on QoS policy.  An
asynchronous paging protocol has no value.  

What is the compelling reason to link a WAN Cellular Paging protocol to a
general IP Context Transfer 'toolkit'?

- Kulwinder.

>    _Ever_? That's a pretty strong statement.
>    That implies that shipping IP packets down
>    some sort of paging interface is just a
>    generally bad idea. I haven't heard anybody
>    give any reasoning of why that might be.
> 
> 	Mike
> 


From owner-seamoby@diameter.org  Mon Mar 26 20:46:59 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA24406
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 20:46:59 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2R0nGY26625
	for seamoby-list; Mon, 26 Mar 2001 16:49:16 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2R0nEF26620
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 16:49:14 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA10810;
	Mon, 26 Mar 2001 15:58:16 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA28338;
	Mon, 26 Mar 2001 15:58:15 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id PAA25314;
	Mon, 26 Mar 2001 15:58:15 -0800 (PST)
Message-Id: <200103262358.PAA25314@heliopolis.Eng.Sun.COM>
Date: Mon, 26 Mar 2001 15:58:15 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: [seamoby] Bluetooth Paging v.s. Cellular Paging
To: mat@cisco.com, acasati@lucent.com, kulwinder.atwal@zucotto.com
Cc: seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: SLYCGWOK3d8TpUN3GVlkcw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Kulwinder,


>Not only can it exist.  It does exist.  Take a look at how Piconet Broadcast
>works for dormant devices (parked) in Bluetooth.  Further, a device may
>power down everything but a small portion of the reciever.  The reciever can
>trigger on the L2 address to wake up the rest of the chip/device.
>
>It is clear that a paging protocol is only useful for Commercial Cellular
>technologies that:
>
>1. Use Paging as a substitute for routing.
>
>2. Use Paging as a substitute for a power efficient hardware design.
>
>Bluetooth transmissions are timer driven and based on QoS policy.  An
>asynchronous paging protocol has no value.  
>

The requirements should be written such that timer-based dormant mode
is supported. I believe we agreed on that. However, they also must support
cellular networks were paging is done over a specific broadcast channel.
It turns out that in wCDMA networks, it is possible to send user data
over certain paging channels. SMS works this way. So it is by no means
impossible for a commercial cellular network to send IP packets
during paging, it would just mean that the IP stack would have to deal
with sending it over a separate channel. The requirements should accommodate
both, and they should accommodate L2 protocols that do not allow 
L3 data to be sent over paging channels nor will they ever, which I believe 
means GSM, as Alissio was I think talking about.

However, I disagree with your characterization of paging as not a routing
function. In the case of Bluetooth, it may be possible that routes to
the piconet have timed out, in which case, paging may be essential  to
reestablish the routes. The reestablishment of the routes may simply
go over the same L2 channel as user data rather than over a special
paging channel, but the effect may be the same.  Important semantic note:
when I say "routes" here I do not necessarily mean standard wired routing
protocols or host routes, a mobile IP HA registration that times out is another
possibility.

The whole point of IP, and it's elegance IMHO, is that it does unify
network access for all kinds of really disparate L2s. I think we can
do the same for paging. If we don't, there is really no point in doing it.

		jak



From owner-seamoby@diameter.org  Mon Mar 26 21:05:24 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA25012
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 21:05:23 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2R1IST26759
	for seamoby-list; Mon, 26 Mar 2001 17:18:28 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2R1IPF26754
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 17:18:25 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id QAA28501;
	Mon, 26 Mar 2001 16:27:34 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADE00098;
	Mon, 26 Mar 2001 16:27:27 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id QAA02607; Mon, 26 Mar 2001 16:27:27 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15039.56943.630081.707331@thomasm-u1.cisco.com>
Date: Mon, 26 Mar 2001 16:27:27 -0800 (PST)
To: "Martin, David P" <David.P.Martin@nextel.com>
Cc: "'Michael Thomas'" <mat@cisco.com>, seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
In-Reply-To: <020A5EC56F3FD411B5230008C716D085868511@nhqntex01.nextel.com>
References: <020A5EC56F3FD411B5230008C716D085868511@nhqntex01.nextel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Martin, David P writes:
 > * Do we assume that location information is known to layer below IP?
 > _Yes_ implies that there could be a trigger or some other mechanism to give
 > hints or direction on how to contact the MN, and would greatly simplify the
 > work for an initial protocol.
 > 
 > _No_ implies that location state would have to be developed (at the network
 > layer since that is where the IETF lives) and would mean that some location
 > state engine would have to be developed to allow paging or packet delivery.
 > This will require a lot of work.

   I don't see what needs to be developed per se:
   we already have two candidate places where
   location information is already stored: the HA
   and the edge access router in visited network.
   Both know how the MN was last reachable (via
   home address in the HA case, via CoA for the
   AR).

 > <rant>
 > Now, all mobility based technologies that I know maintain the state
 > information below IP.  So for all existing technologies, we would be
 > designing a redundant location mechanism into the system.  This leads to
 > interesting issues ...
 > If you have to choose between optimizing the protocol for paging systems vs
 > non-paging systems, which do you choose?  Which location mechanism do you
 > use?  Do you have a choice?  You will probably be forced to at least use the
 > lower layer location mechanism.  If I have to use it, what added benefit is
 > an upper layer location mechanism?  

   How would you page a MN with an 802.11
   radio, say, if you don't have an 802.11
   interface? This seems like a pretty likely
   scenario with cellular base stations and
   dual mode cellular/802.11 widgets, even within
   a single provider's network.

   I look at this very simplistically: if you
   can't find the mobile on a local L2 and you
   have reason to believe that it still may be
   attached (pageable) elsewhere, you need a
   L3 mechanism to trigger the other routers
   to find it. That means that you're going to
   have to send out a page to some collection of
   neighboring routers (neighboring in the paging
   area sense) to find it. Conceptually, this 
   doesn't seem all that hard to me. How best to
   utilize bandwidth and avoid dumb flood fill
   kinds of searches, of course, will be a
   challenge. With some L2 hints, however the
   latter could certainly be helped.

		Mike


From owner-seamoby@diameter.org  Mon Mar 26 21:15:56 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA25184
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 21:15:56 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2R0qnW26652
	for seamoby-list; Mon, 26 Mar 2001 16:52:49 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from atlsnmx1.nextel.com (atlsnmx1.nextel.com [167.20.198.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2R0qgF26647
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 16:52:46 -0800
Received: from atlntgw02.nextel.com (atlntgw02.nextel.com [10.8.79.186])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id TAA19002;
	Mon, 26 Mar 2001 19:01:39 -0500 (EST)
Received: by atlntgw02.nextel.com with Internet Mail Service (5.5.2650.21)
	id <HKW3RWC9>; Mon, 26 Mar 2001 19:02:11 -0500
Message-ID: <020A5EC56F3FD411B5230008C716D085868511@nhqntex01.nextel.com>
From: "Martin, David P" <David.P.Martin@nextel.com>
To: "'Michael Thomas'" <mat@cisco.com>,
        "Martin, David P"
	 <David.P.Martin@nextel.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
Date: Mon, 26 Mar 2001 18:56:50 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Since I started this, I feel some obligation to help reach closure ... 

First, I think we've reached consensus that in order to deliver a packet or
page that some type of location information must be maintained somewhere in
order to effect delivery. 

Second, is that location information is needed to support a delivery
mechanism (paging or direct delivery).

I think where we diverge is on whether should seamoby take on this problem
...

So this leads to the following questions:
* Do we assume that location information is known to layer below IP?
_Yes_ implies that there could be a trigger or some other mechanism to give
hints or direction on how to contact the MN, and would greatly simplify the
work for an initial protocol.

_No_ implies that location state would have to be developed (at the network
layer since that is where the IETF lives) and would mean that some location
state engine would have to be developed to allow paging or packet delivery.
This will require a lot of work.

I would think that it would be more efficient to focus on known mobility
systems, and solve the more esoteric cases later ... but will yield to the
group's consensus.



<rant>
Now, all mobility based technologies that I know maintain the state
information below IP.  So for all existing technologies, we would be
designing a redundant location mechanism into the system.  This leads to
interesting issues ...
If you have to choose between optimizing the protocol for paging systems vs
non-paging systems, which do you choose?  Which location mechanism do you
use?  Do you have a choice?  You will probably be forced to at least use the
lower layer location mechanism.  If I have to use it, what added benefit is
an upper layer location mechanism?  
My sense is that the problems/requirements/solutions for systems that
inherently support paging at layers below IP are more defined, and that work
could proceed more quickly in that space.  General IP paging would be a
complex solution to a problem of unknown proportions, and it will probably
take more time to scope.
</rant>

> 
> 
> Martin, David P writes:
>  > >    This doesn't seem to hard: suppose you have a
>  > >    beacon which all dormant nodes listen too. To
>  > >    find a node, the last attachment point performs
>  > >    a search in the local paging area. When the mobile
>  > >    wakes up, it establishes a link to its current AP,
>  > >    and a tunnel to the old AP to scoop up the
>  > >    packet(s).
>  > 
>  > I agree that a paging system can be designed that can work 
> with a technology
>  > that does not continually track a MN location.
>  > 
>  > However, a (working) paging system *cannot* be designed without a
>  > registration mechanism.
> 
>    Sure.
> 
>  > The purpose of a registration mechanism is to
>  > provide rough location state information on where a MN is 
> located in a
>  > network topology.  This location state can be of several 
> forms, specific
>  > access point, specific paging zone, specific network 
> (scalability issues),
>  > last known access point, last known access zone, etc.  But 
> the network has
>  > to have some type of location information to even begin to 
> guess on how to
>  > start paging.
> 
>    Correct.
> 
>  > In your example above, the mobile in effect registers upon
>  > wake up, giving the network location state to work with.  
> Of course a
>  > mechanism must exist (at one or more layers) to deal with 
> stale location
>  > information.
> 
>    Yup.
>  
>  > So, I'm trying to say that there must be some location 
> state maintained
>  > somewhere at layer 2, otherwise the entire network would 
> behave as one big
>  > LAN segment.
> 
>    I don't see this as having much to do with L2. If
>    I can route an IP packet to the last known point
>    of attachment, it could put out the dragnet by
>    sending out IP packets which eventually (or not)
>    find the mobile node. L2 location information may
>    or may not be involved. At a base level, I don't
>    think we should count on them being there though.
> 
> 	    Mike
> 


From owner-seamoby@diameter.org  Mon Mar 26 21:18:53 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA25257
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 21:18:52 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2R2JYJ26927
	for seamoby-list; Mon, 26 Mar 2001 18:19:34 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2R2JVF26922
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 18:19:31 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4SY20>; Mon, 26 Mar 2001 20:28:36 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A92@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>, mat@cisco.com,
        acasati@lucent.com, Kulwinder Atwal <kulwinder.atwal@zucotto.com>
Cc: seamoby@diameter.org
Subject: [seamoby] RE: Bluetooth Paging v.s. Cellular Paging
Date: Mon, 26 Mar 2001 20:28:36 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
> Sent: Monday, March 26, 2001 6:58 PM
> To: mat@cisco.com; acasati@lucent.com; kulwinder.atwal@zucotto.com
> Cc: seamoby@diameter.org
> Subject: Bluetooth Paging v.s. Cellular Paging
> 
> 
> Kulwinder,
> 
> The requirements should be written such that timer-based dormant mode
> is supported. I believe we agreed on that. However, they also 
> must support
> cellular networks were paging is done over a specific 
> broadcast channel.
> It turns out that in wCDMA networks, it is possible to send user data
> over certain paging channels. SMS works this way. So it is by no means
> impossible for a commercial cellular network to send IP packets
> during paging, it would just mean that the IP stack would have to deal
> with sending it over a separate channel. The requirements 
> should accommodate
> both, and they should accommodate L2 protocols that do not allow 
> L3 data to be sent over paging channels nor will they ever, 
> which I believe 
> means GSM, as Alissio was I think talking about.
> 
> However, I disagree with your characterization of paging as 
> not a routing
> function. 

> In the case of Bluetooth, it may be possible that routes to
> the piconet have timed out, in which case, paging may be essential  to
> reestablish the routes. 

A dormant mode (parked) device does not timeout.  Do you have any other
possible reasons for suggesting that Bluetooth needs a paging protocol?  

- Kulwinder.

> 		jak
> 


From owner-seamoby@diameter.org  Mon Mar 26 22:11:58 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA26877
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 22:11:57 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2R1b3s26806
	for seamoby-list; Mon, 26 Mar 2001 17:37:03 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2R1b1F26801
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 17:37:02 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA28006
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 16:46:06 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA29171
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 16:46:04 -0800 (PST)
Received: from darius (darius [10.6.84.105])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id QAA04667;
	Mon, 26 Mar 2001 16:46:02 -0800 (PST)
Date: Mon, 26 Mar 2001 16:46:01 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: Re: [seamoby] Confusion about Seamoby Goals
To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Cc: seamoby@diameter.org
In-Reply-To: "Your message with ID" <200103262346.PAA24916@heliopolis.Eng.Sun.COM>
Message-ID: <Roam.SIMC.2.0.6.985653961.11478.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

Perhaps I should ask what led you to this conclusion, so we can make sure that
we nip this one in the bud.

PatC
> Kulwinder,
> 
> 
> >What is the compelling reason to link a WAN Cellular Paging protocol to a
> >general IP Context Transfer 'toolkit'?
> >
> 
> Nobody is proposing to link paging to context transfer. These two
> topics were just thrown together into Seamoby because there was too
> much work in mobile IP to handle them. As far as I am concerned, they
> are completely unrelated.
> 
> Your comment is the second time today somebody has brought this up.
> 
> 		jak
> 




From owner-seamoby@diameter.org  Mon Mar 26 23:02:28 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA28296
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 23:02:27 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2R2qtG27047
	for seamoby-list; Mon, 26 Mar 2001 18:52:55 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2R2qfF27041
	for <seamoby@cdma-2000.org>; Mon, 26 Mar 2001 18:52:41 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4SYJJ>; Mon, 26 Mar 2001 21:01:46 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A93@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'pcalhoun@eng.sun.com'" <pcalhoun@eng.sun.com>, seamoby@cdma-2000.org
Subject: RE: [seamoby] An MM update from IETF 50
Date: Mon, 26 Mar 2001 21:01:36 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Patrice Calhoun [mailto:pcalhoun@nasnfs.eng.sun.com]
> Sent: Wednesday, March 21, 2001 5:32 PM
> To: seamoby@cdma-2000.org
> Subject: [seamoby] An MM update from IETF 50
> 
> 
> All,
>
> So, for all three above points, the following was decided, 
> and discussed at
> the meeting:
> 
> 	1. The MM DT will write a requirements draft for Mobile 
> IP to understand
> 	   the seamoby requirements. This will be used by the MIP WG to
> 	   know how Mobile IP needs to be changed.
> 	2. The IRTF has agreed to take the new local mobility 
> protocol, and
> 	   as with many other IRTF efforts, the work will move 
> back into the
> 	   IETF once it is ready.


> 	3. The MM DT will begin to write the requirements for a 
> new protocol that allows for AP discovery to be done. 

If the point of this protocol is to locate/discover the
services/capabilities of an AP, could we not just use the Service Locator
Protocol to locate such things as the Quality of Service available on
candidate AP?

Just a thought.

- Kulwinder.

> If anyone has issues with the above decisions, please contact me.
> 
> Thanks,
> 
> PatC
> 


From owner-seamoby@diameter.org  Mon Mar 26 23:03:01 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA28309
	for <seamoby-archive@odin.ietf.org>; Mon, 26 Mar 2001 23:03:00 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2R33bY27087
	for seamoby-list; Mon, 26 Mar 2001 19:03:37 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2R33ZF27082
	for <seamoby@cdma-2000.org>; Mon, 26 Mar 2001 19:03:35 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA23536;
	Mon, 26 Mar 2001 18:12:40 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA26440;
	Mon, 26 Mar 2001 18:12:39 -0800 (PST)
Received: from darius (darius [10.6.84.105])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id SAA06158;
	Mon, 26 Mar 2001 18:12:33 -0800 (PST)
Date: Mon, 26 Mar 2001 18:12:32 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: RE: [seamoby] An MM update from IETF 50
To: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
Cc: "'pcalhoun@eng.sun.com'" <pcalhoun@eng.sun.com>, seamoby@cdma-2000.org
In-Reply-To: "Your message with ID" <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A93@NEPTUNE.zucotto.com>
Message-ID: <Roam.SIMC.2.0.6.985659152.10003.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk


> If the point of this protocol is to locate/discover the
> services/capabilities of an AP, could we not just use the Service Locator
> Protocol to locate such things as the Quality of Service available on
> candidate AP?
> 

I think that the protocol selection should probably wait until we have an idea
of what we need. Once the requirements are done, the answer may become obvious
(although I am not sure that SLP was designed for very dynamic environments).

PatC



From owner-seamoby@diameter.org  Tue Mar 27 01:17:19 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA02007
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Mar 2001 01:17:19 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2R5NNU27393
	for seamoby-list; Mon, 26 Mar 2001 21:23:23 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2R5NLF27388
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 21:23:21 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4SYK3>; Mon, 26 Mar 2001 23:32:27 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A94@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Patrice Calhoun'" <pcalhoun@nasnfs.eng.sun.com>,
        James Kempf
	 <kempf@heliopolis.Eng.Sun.COM>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Confusion about Seamoby Goals
Date: Mon, 26 Mar 2001 23:32:25 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


Are both of you willing to admit that not all wireless technologies need a
paging protocol?

- Kulwinder.

> -----Original Message-----
> From: Patrice Calhoun [mailto:pcalhoun@nasnfs.eng.sun.com]
> Sent: Monday, March 26, 2001 7:46 PM
> To: James Kempf
> Cc: seamoby@diameter.org
> Subject: Re: [seamoby] Confusion about Seamoby Goals
> 
> 
> Perhaps I should ask what led you to this conclusion, so we 
> can make sure that
> we nip this one in the bud.
> 
> PatC
> > Kulwinder,
> > 
> > 
> > >What is the compelling reason to link a WAN Cellular 
> Paging protocol to a
> > >general IP Context Transfer 'toolkit'?
> > >
> > 
> > Nobody is proposing to link paging to context transfer. These two
> > topics were just thrown together into Seamoby because there was too
> > much work in mobile IP to handle them. As far as I am 
> concerned, they
> > are completely unrelated.
> > 
> > Your comment is the second time today somebody has brought this up.
> > 
> > 		jak
> > 
> 
> 


From owner-seamoby@diameter.org  Tue Mar 27 01:22:28 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA02724
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Mar 2001 01:22:27 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2R5YYD27424
	for seamoby-list; Mon, 26 Mar 2001 21:34:34 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2R5YWF27419
	for <seamoby@diameter.org>; Mon, 26 Mar 2001 21:34:32 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4SYKP>; Mon, 26 Mar 2001 23:43:37 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A95@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Michael Thomas'" <mat@cisco.com>,
        "Martin, David P"
	 <David.P.Martin@nextel.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
Date: Mon, 26 Mar 2001 23:43:27 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Michael Thomas [mailto:mat@cisco.com]
> Sent: Monday, March 26, 2001 7:27 PM
> To: Martin, David P
> Cc: 'Michael Thomas'; seamoby@diameter.org
> Subject: RE: [seamoby] L2/L3 Paging
> 
> 
> Martin, David P writes:
>  > * Do we assume that location information is known to layer 
> below IP?
>  > _Yes_ implies that there could be a trigger or some other 
> mechanism to give
>  > hints or direction on how to contact the MN, and would 
> greatly simplify the
>  > work for an initial protocol.
>  > 
>  > _No_ implies that location state would have to be 
> developed (at the network
>  > layer since that is where the IETF lives) and would mean 
> that some location
>  > state engine would have to be developed to allow paging or 
> packet delivery.
>  > This will require a lot of work.
> 
>    I don't see what needs to be developed per se:
>    we already have two candidate places where
>    location information is already stored: the HA
>    and the edge access router in visited network.
>    Both know how the MN was last reachable (via
>    home address in the HA case, via CoA for the
>    AR).
> 
>  > <rant>
>  > Now, all mobility based technologies that I know maintain the state
>  > information below IP.  So for all existing technologies, 
> we would be
>  > designing a redundant location mechanism into the system.  
> This leads to
>  > interesting issues ...
>  > If you have to choose between optimizing the protocol for 
> paging systems vs
>  > non-paging systems, which do you choose?  Which location 
> mechanism do you
>  > use?  Do you have a choice?  You will probably be forced 
> to at least use the
>  > lower layer location mechanism.  If I have to use it, what 
> added benefit is
>  > an upper layer location mechanism?  
> 
>    How would you page a MN with an 802.11
>    radio, say, if you don't have an 802.11
>    interface? This seems like a pretty likely
>    scenario with cellular base stations and
>    dual mode cellular/802.11 widgets, even within
>    a single provider's network.

What if the MN registers its interfaces with the COA router.
If an AR/AP is unable to route on its interface, it can forward to the COA
router.
The COA router can check its MN registery for other intefaces and route
accordingly.

- Kulwinder.

> 
>    I look at this very simplistically: if you
>    can't find the mobile on a local L2 and you
>    have reason to believe that it still may be
>    attached (pageable) elsewhere, you need a
>    L3 mechanism to trigger the other routers
>    to find it. That means that you're going to
>    have to send out a page to some collection of
>    neighboring routers (neighboring in the paging
>    area sense) to find it. Conceptually, this 
>    doesn't seem all that hard to me. How best to
>    utilize bandwidth and avoid dumb flood fill
>    kinds of searches, of course, will be a
>    challenge. With some L2 hints, however the
>    latter could certainly be helped.
> 
> 		Mike
> 


From owner-seamoby@diameter.org  Tue Mar 27 05:55:56 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA16615
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Mar 2001 05:55:55 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2RA37P28091
	for seamoby-list; Tue, 27 Mar 2001 02:03:07 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from m1.bezeqint.net (m1.bezeqint.net [192.115.106.45])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2RA34F28086
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 02:03:04 -0800
Received: from nana (clnt-7163.bezeqint.net [212.179.7.163] (may be forged))
	by m1.bezeqint.net (Mirapoint)
	with SMTP id AAW06122;
	Tue, 27 Mar 2001 11:12:17 GMT
From: "Yaniv Bargury" <yaniv@packetmachine.com>
To: "Michael Thomas" <mat@cisco.com>,
        "Casati, Alessio \(Alessio\)" <acasati@lucent.com>
Cc: <seamoby@diameter.org>
Subject: RE: Registration (was RE: [seamoby] L2/L3 Paging)
Date: Tue, 27 Mar 2001 11:14:14 +0200
Message-ID: <LFEOJFEPOOJACFMDIIHPGEBCCDAA.yaniv@packetmachine.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-reply-to: <15039.45419.182234.602445@thomasm-u1.cisco.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The process of paging a mobile, and sending one packet to it over the paging
channel, is called SMS...

-----Original Message-----
From: owner-seamoby@diameter.org [mailto:owner-seamoby@diameter.org]On
Behalf Of Michael Thomas
Sent: Mon, March 26, 2001 11:15 PM
To: Casati, Alessio (Alessio)
Cc: 'Michael Thomas'; seamoby@diameter.org
Subject: RE: Registration (was RE: [seamoby] L2/L3 Paging)


Casati, Alessio (Alessio) writes:
 >
 >  >
 >  > Exactly. But when there is no link we may have 2 cases:
 >  > the link can be re-established via L2 paging, or the packets (when
they
 > do
 >  > need to be delivered) get dropped
 >  > for a while, and then timers will do the rest.
 >
 >    I believe that there is a third possibility:
 >    The paging interface allows delivery of IP
 >    datagrams. None of these exist, as far as I
 >    know, but that doesn't preclude some clever
 >    radio-heads from doing so :-)
 >
 > 		   Mike
 >
 >
 > The 2 I mentioned (packet drop or link re-establishments) do exist.
 > I agree the third way may not exist (ever).

   _Ever_? That's a pretty strong statement.
   That implies that shipping IP packets down
   some sort of paging interface is just a
   generally bad idea. I haven't heard anybody
   give any reasoning of why that might be.

	Mike



From owner-seamoby@diameter.org  Tue Mar 27 06:26:07 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA16793
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Mar 2001 06:26:07 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2R9uO428060
	for seamoby-list; Tue, 27 Mar 2001 01:56:24 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2R9uMF28055
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 01:56:22 -0800
Received: from ihemail2.firewall.lucent.com (localhost [127.0.0.1])
	by ihemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id EAA18508
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 04:05:28 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-160-150.lucent.com [135.86.160.150])
	by ihemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id EAA18479
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 04:05:27 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2650.21)
	id <H2VDZ31P>; Tue, 27 Mar 2001 10:05:26 +0100
Message-ID: <976F7C55E3B2D111A0720008C728549C097CC22C@en0060exch001u.uk.lucent.com>
From: "Casati, Alessio (Alessio)" <acasati@lucent.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>, mat@cisco.com,
        "Casati, Alessio (Alessio)" <acasati@lucent.com>,
        kulwinder.atwal@zucotto.com
Cc: seamoby@diameter.org
Subject: [seamoby] RE: Bluetooth Paging v.s. Cellular Paging
Date: Tue, 27 Mar 2001 10:05:18 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk

It turns out that in wCDMA networks, it is possible to send user data
over certain paging channels. SMS works this way. So it is by no means
impossible for a commercial cellular network to send IP packets
during paging, it would just mean that the IP stack would have to deal
with sending it over a separate channel. 

One thing is saying it is possible to do something, another is
actually doing it in commercial networks. It may turn out that
there is no money associated to sending a paging IP packet over a 
paging L2 channel (the complexity does not justify the benefits). 
Hence my strong statement.


alessio


From owner-seamoby@diameter.org  Tue Mar 27 08:45:38 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA17988
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Mar 2001 08:45:37 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2RCcsu28698
	for seamoby-list; Tue, 27 Mar 2001 04:38:54 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2RCcqF28693
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 04:38:52 -0800
Received: from auemail2.firewall.lucent.com (localhost [127.0.0.1])
	by auemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id GAA17542
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 06:47:58 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-160-150.lucent.com [135.86.160.150])
	by auemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id GAA17518
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 06:47:58 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2650.21)
	id <H2VDZX0G>; Tue, 27 Mar 2001 12:47:56 +0100
Message-ID: <976F7C55E3B2D111A0720008C728549C097CC231@en0060exch001u.uk.lucent.com>
From: "Casati, Alessio (Alessio)" <acasati@lucent.com>
To: "'Yaniv Bargury'" <yaniv@packetmachine.com>
Cc: seamoby@diameter.org
Subject: RE: Registration (was RE: [seamoby] L2/L3 Paging)
Date: Tue, 27 Mar 2001 12:47:48 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk


The process of paging a mobile, and sending one packet to it over the paging
channel, is called SMS...

Point to point SMS is not sent over the paging channel in GSM/UMTS.
Paging can be used to trigger the reception of the ptp SMS data over other
channels.
Besides, SMSCB (Cell Broadcast) is sent over the CBCH channel in GSM
and over the CTCH in UMTS (TS 25.041 ; TS 24.012 ; TS 25.324; TS 25.301).

Using the paging mechanism to piggyback IP packets seems a bit stretched.
Using
a broadcast or common transport channel, when available, is more feasible,
instead.
On whether this is useful for the things the WG want to do, I'm agnostic...


alessio


From owner-seamoby@diameter.org  Tue Mar 27 12:19:31 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA23395
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Mar 2001 12:19:31 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2RGCw729315
	for seamoby-list; Tue, 27 Mar 2001 08:12:58 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2RGCuF29310
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 08:12:56 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA19790;
	Tue, 27 Mar 2001 07:22:02 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA13396;
	Tue, 27 Mar 2001 07:22:01 -0800 (PST)
Received: from darius (darius [10.6.84.105])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id HAA11538;
	Tue, 27 Mar 2001 07:21:59 -0800 (PST)
Date: Tue, 27 Mar 2001 07:21:58 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: RE: [seamoby] Confusion about Seamoby Goals
To: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
Cc: "'Patrice Calhoun'" <pcalhoun@nasnfs.eng.sun.com>,
        James Kempf <kempf@heliopolis.Eng.Sun.COM>, seamoby@diameter.org
In-Reply-To: "Your message with ID" <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A94@NEPTUNE.zucotto.com>
Message-ID: <Roam.SIMC.2.0.6.985706518.5353.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> 
> Are both of you willing to admit that not all wireless technologies need a
> paging protocol?

I am not ready to answer this question. I wanted to know what led you to
believe that paging would be linked to context transfer. If there is something
out there that is causing this confusion, we need to fix it.

PatC

> 
> - Kulwinder.
> 
> > -----Original Message-----
> > From: Patrice Calhoun [mailto:pcalhoun@nasnfs.eng.sun.com]
> > Sent: Monday, March 26, 2001 7:46 PM
> > To: James Kempf
> > Cc: seamoby@diameter.org
> > Subject: Re: [seamoby] Confusion about Seamoby Goals
> > 
> > 
> > Perhaps I should ask what led you to this conclusion, so we 
> > can make sure that
> > we nip this one in the bud.
> > 
> > PatC
> > > Kulwinder,
> > > 
> > > 
> > > >What is the compelling reason to link a WAN Cellular 
> > Paging protocol to a
> > > >general IP Context Transfer 'toolkit'?
> > > >
> > > 
> > > Nobody is proposing to link paging to context transfer. These two
> > > topics were just thrown together into Seamoby because there was too
> > > much work in mobile IP to handle them. As far as I am 
> > concerned, they
> > > are completely unrelated.
> > > 
> > > Your comment is the second time today somebody has brought this up.
> > > 
> > > 		jak
> > > 
> > 
> > 




From owner-seamoby@diameter.org  Tue Mar 27 14:50:02 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA27593
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Mar 2001 14:50:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2RGxZg29420
	for seamoby-list; Tue, 27 Mar 2001 08:59:35 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2RGxUF29415
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 08:59:30 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA00305;
	Tue, 27 Mar 2001 08:08:28 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA04132;
	Tue, 27 Mar 2001 08:08:18 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id IAA05915;
	Tue, 27 Mar 2001 08:08:18 -0800 (PST)
Message-Id: <200103271608.IAA05915@heliopolis.Eng.Sun.COM>
Date: Tue, 27 Mar 2001 08:08:18 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: [seamoby] RE: Bluetooth Paging v.s. Cellular Paging
To: kempf@heliopolis.Eng.Sun.COM, mat@cisco.com, acasati@lucent.com,
        kulwinder.atwal@zucotto.com
Cc: seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 8lvU7CwE263ZdGs2+1f9YQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk


>A dormant mode (parked) device does not timeout.  Do you have any other
>possible reasons for suggesting that Bluetooth needs a paging protocol?  
>

I wasn't implying that the device timed out, I was stating that
the routes to the device might time out.

And I was under the impression that Bluetooth already *has* an L2
paging protocol. Is that not so?

		jak



From owner-seamoby@diameter.org  Tue Mar 27 15:01:24 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA27884
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Mar 2001 15:01:24 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2RINYQ29680
	for seamoby-list; Tue, 27 Mar 2001 10:23:34 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from atlsnmx1.nextel.com (atlsnmx1.nextel.com [167.20.198.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2RINTF29675
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 10:23:29 -0800
Received: from atlntgw02.nextel.com (atlntgw02.nextel.com [10.8.79.186])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id MAA05334;
	Tue, 27 Mar 2001 12:32:23 -0500 (EST)
Received: by atlntgw02.nextel.com with Internet Mail Service (5.5.2650.21)
	id <HKW3S1DM>; Tue, 27 Mar 2001 12:32:54 -0500
Message-ID: <020A5EC56F3FD411B5230008C716D085868515@nhqntex01.nextel.com>
From: "Martin, David P" <David.P.Martin@nextel.com>
To: "'Michael Thomas'" <mat@cisco.com>,
        "Martin, David P"
	 <David.P.Martin@nextel.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
Date: Tue, 27 Mar 2001 12:27:31 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

<snip> 
>    I don't see what needs to be developed per se:
>    we already have two candidate places where
>    location information is already stored: the HA
>    and the edge access router in visited network.
>    Both know how the MN was last reachable (via
>    home address in the HA case, via CoA for the
>    AR).

Agree that location information exists at the network layer, but how do you
use this information to get to the MN? Say a packet comes in to the edge
access router destined for a dormant MN (via the COA) that was last
associated with that router.  A mechanism must exist to deliver the packet
to the MN.  One avenue is to assume a lower layer system exists to resolve
this, and a trigger is used to kick off this system, this is the easy case.
For the case where the lower layer system does not have a mechanism for
finding the MN, a mechanism must be built.  So how could one do this?

One option would be to put the packet on the last known interface, but the
mobile is dormant, how does the mobile know to listen to this interface?  

Another option is to broadcast to the mobiles on a specific broadcast
channel (to save power, but this requires lower layer modifications to the
mobile) a list of MN addresses that need to wake up because they have
traffic, for this case you need mobiles that need to understand how to
listen to broadcast traffic ... in other words you have a system that
supports paging such that a packet arriving at a router can trigger a page
(see first option).  However, since broadcasting a list of all mobiles does
not scale, a mechansim must be built to partition the list (via time,
geography, or some other method) to allow the broadcast channel to scale.
So you either have to scale the edge routers to accommodate the broadcast
channel, or you have to develop a location mechanism "underneath" the edge
router.  In my mind this system is nothing more than designing a paging
system that lives below the network layer, and if I have to design this type
of system, doesn't this mean we can assume that a mechanism exists at a
layer below IP for delivering packets (and a seperate effort can actually
design the mechanism, sort of like the PPP work in IETF).  

Additionally, thought has to be given for the case where the mobile is
unreachable at the current interface, either the packets have to be dropped,
or mechanisms have to be developed to try and find where the mobile might
be.

<<Snipped rant>

>    How would you page a MN with an 802.11
>    radio, say, if you don't have an 802.11
>    interface? This seems like a pretty likely
>    scenario with cellular base stations and
>    dual mode cellular/802.11 widgets, even within
>    a single provider's network.

I think your question is I have a cellular base station and I want to reach
a MN with dual mode cellular/802.11 access, and I assume by the question
that there is no mechanism to indicate when the MN has switched access
networks.  The edge router would have to send a packet to the "right"
interface, so in the context of paging, I can page the mobile on both
interfaces.  But I am assuming that a mechanism exists below the network to
deliver these pages.  802.11 and cellular both have (different) location
determination mechanisms below (unseen by) IP, it would be useful for an IP
paging protocol to leverage off of this information.

> 
>    I look at this very simplistically: if you
>    can't find the mobile on a local L2 and you
>    have reason to believe that it still may be
>    attached (pageable) elsewhere, you need a
>    L3 mechanism to trigger the other routers
>    to find it.

I agree.

>    That means that you're going to
>    have to send out a page to some collection of
>    neighboring routers (neighboring in the paging
>    area sense) to find it. Conceptually, this 
>    doesn't seem all that hard to me. How best to
>    utilize bandwidth and avoid dumb flood fill
>    kinds of searches, of course, will be a
>    challenge. With some L2 hints, however the
>    latter could certainly be helped.

I agree here as well, but sending network pages to routers is orthogonal to
whether a L2 mechanism exists to deliver those packets to the mobile.

It is not clear to me how to develop a paging design at the network layer,
without support from an underlying protocol ... and I see these as two
distinct issues.


From owner-seamoby@diameter.org  Tue Mar 27 15:06:49 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA28029
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Mar 2001 15:06:49 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2RHFR129511
	for seamoby-list; Tue, 27 Mar 2001 09:15:27 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2RHFOF29506
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 09:15:24 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4SYXB>; Tue, 27 Mar 2001 11:24:31 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A97@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        pcalhoun@nasnfs.eng.sun.com,
        Kulwinder Atwal
	 <kulwinder.atwal@zucotto.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] Confusion about Seamoby Goals
Date: Tue, 27 Mar 2001 11:24:21 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
> Sent: Tuesday, March 27, 2001 11:13 AM
> To: pcalhoun@nasnfs.Eng.Sun.COM; kempf@heliopolis.Eng.Sun.COM;
> kulwinder.atwal@zucotto.com
> Cc: seamoby@diameter.org
> Subject: RE: [seamoby] Confusion about Seamoby Goals
> 
> 
> 
> >Are both of you willing to admit that not all wireless 
> technologies need a
> >paging protocol?
> >
> 
> Sure! If you read the problem statement, you'll see that a 
> paging protocol
> does not make sense for 802.11 style L2s that do reassociation.
> 
> If Bluetooth doesn't have one (actually, I mistakenly thought 
> it did) and
> it does 802.11 style reassociation, then an L3 protocol won't help.

I wanted to be certain.  Thanks.

- Kulwinder.

> 
> 		jak
> 


From owner-seamoby@diameter.org  Tue Mar 27 15:08:24 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA28075
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Mar 2001 15:08:24 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2RH43c29465
	for seamoby-list; Tue, 27 Mar 2001 09:04:03 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2RH40F29460
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 09:04:00 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA02933;
	Tue, 27 Mar 2001 08:13:06 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA05055;
	Tue, 27 Mar 2001 08:13:05 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id IAA06018;
	Tue, 27 Mar 2001 08:13:04 -0800 (PST)
Message-Id: <200103271613.IAA06018@heliopolis.Eng.Sun.COM>
Date: Tue, 27 Mar 2001 08:13:04 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] Confusion about Seamoby Goals
To: pcalhoun@nasnfs.eng.sun.com, kempf@heliopolis.Eng.Sun.COM,
        kulwinder.atwal@zucotto.com
Cc: seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Re3hDXLwVx8xour4RlXOBA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk


>Are both of you willing to admit that not all wireless technologies need a
>paging protocol?
>

Sure! If you read the problem statement, you'll see that a paging protocol
does not make sense for 802.11 style L2s that do reassociation.

If Bluetooth doesn't have one (actually, I mistakenly thought it did) and
it does 802.11 style reassociation, then an L3 protocol won't help.

		jak



From owner-seamoby@diameter.org  Tue Mar 27 15:28:44 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA28641
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Mar 2001 15:28:43 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2RHDc129500
	for seamoby-list; Tue, 27 Mar 2001 09:13:38 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2RHDYF29495
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 09:13:34 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4SYXA>; Tue, 27 Mar 2001 11:22:41 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2A96@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>, mat@cisco.com,
        acasati@lucent.com, Kulwinder Atwal <kulwinder.atwal@zucotto.com>
Cc: seamoby@diameter.org
Subject: [seamoby] RE: Bluetooth Paging v.s. Cellular Paging
Date: Tue, 27 Mar 2001 11:22:37 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
> Sent: Tuesday, March 27, 2001 11:08 AM
> To: kempf@heliopolis.Eng.Sun.COM; mat@cisco.com; acasati@lucent.com;
> kulwinder.atwal@zucotto.com
> Cc: seamoby@diameter.org
> Subject: RE: Bluetooth Paging v.s. Cellular Paging
> 
> 
> 
> >A dormant mode (parked) device does not timeout.  Do you 
> have any other
> >possible reasons for suggesting that Bluetooth needs a 
> paging protocol?  
> >
> 
> I wasn't implying that the device timed out, I was stating that
> the routes to the device might time out.

Sounds like a flaw in a routing protocol.  Maybe a mobile wireless routing
protocol needs to change routes based on L2 triggers instead of arbitrary
timers.

> 
> And I was under the impression that Bluetooth already *has* an L2
> paging protocol. Is that not so?

There is a point-to-point method used to discover a new device and associate
it to the network for the first time.  Once a device is discovered it may be
placed into a dormant state.  There is no relation between dormant mode and
paging.

- Kulwinder.

> 
> 		jak
> 


From owner-seamoby@diameter.org  Tue Mar 27 20:44:56 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA07283
	for <seamoby-archive@odin.ietf.org>; Tue, 27 Mar 2001 20:44:56 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2RMtCV30340
	for seamoby-list; Tue, 27 Mar 2001 14:55:12 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2RMt7F30335
	for <seamoby@diameter.org>; Tue, 27 Mar 2001 14:55:07 -0800
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA21444;
	Tue, 27 Mar 2001 14:04:11 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA25440;
	Tue, 27 Mar 2001 14:04:07 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id OAA15046;
	Tue, 27 Mar 2001 14:04:07 -0800 (PST)
Message-Id: <200103272204.OAA15046@heliopolis.Eng.Sun.COM>
Date: Tue, 27 Mar 2001 14:04:07 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] L2/L3 Paging
To: mat@cisco.com, David.P.Martin@nextel.com
Cc: seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: FC1m6imkrCiy4RXrruqg5w==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Dave,

>
>Since I started this, I feel some obligation to help reach closure ... 
>
>First, I think we've reached consensus that in order to deliver a packet or
>page that some type of location information must be maintained somewhere in
>order to effect delivery. 
>
>Second, is that location information is needed to support a delivery
>mechanism (paging or direct delivery).
>
>I think where we diverge is on whether should seamoby take on this problem
>...
>
>So this leads to the following questions:
>* Do we assume that location information is known to layer below IP?
>_Yes_ implies that there could be a trigger or some other mechanism to give
>hints or direction on how to contact the MN, and would greatly simplify the
>work for an initial protocol.
>
>_No_ implies that location state would have to be developed (at the network
>layer since that is where the IETF lives) and would mean that some location
>state engine would have to be developed to allow paging or packet delivery.
>This will require a lot of work.
>

The issue isn't this simple. The location information available at L2
may not be sufficient to effect location. Or there may be more L2
involved. In either case, location information available at L3
may be important in making the connection with a dormant mode mobile
node that will allow routing to be updated and the packet to be delivered.

I also don't think it is as much work as you may think. There are
already several prototypes (Cellular IP, Hawaii, the Columbia MIPv4
paging protocol, etc.) that have examined this issue. I think it is
primarily a matter of getting the architecture and requirements sorted
out, then getting the people with some design and implementation expertise
in the same room to agree on a protocol.


>I would think that it would be more efficient to focus on known mobility
>systems, and solve the more esoteric cases later ... but will yield to the
>group's consensus.
>
>
>
><rant>
>Now, all mobility based technologies that I know maintain the state
>information below IP.  So for all existing technologies, we would be
>designing a redundant location mechanism into the system.  This leads to
>interesting issues ...
>If you have to choose between optimizing the protocol for paging systems vs
>non-paging systems, which do you choose?  Which location mechanism do you
>use?  Do you have a choice?  You will probably be forced to at least use the
>lower layer location mechanism.  If I have to use it, what added benefit is
>an upper layer location mechanism?  

I guess I don't follow this. L2 mechanisms are used for intrasubnet movement
but that doesn't preclude the need for something at L3 to track mobility,
mobile IP being the current solution. L2 mechanisms only work for a
particular L2. And, as the problem statement states (clearly I hope),
even for the same L2 there are difficulties depending on the mapping
between paging areas and subnets.


>My sense is that the problems/requirements/solutions for systems that
>inherently support paging at layers below IP are more defined, and that work
>could proceed more quickly in that space.  General IP paging would be a
>complex solution to a problem of unknown proportions, and it will probably
>take more time to scope.
></rant>
>

Actually, I think it is just good design to try to factor the problem into
the part that is independent of L2 and the part that is not. IPv6
does this quite nicely. There is a requirement for a minimum frame
size from L2,  if the L2 doesn't supply it, then a shim layer needs to
be written to do segmentation and reassembly. Granted, this requirement
is considerably simpler than paging, but I suspect the people who have
had experience doing prototypes will have some idea about where to 
cut the design.

		jak



From owner-seamoby@diameter.org  Wed Mar 28 09:59:26 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29693
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 09:59:25 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SESHC32733
	for seamoby-list; Wed, 28 Mar 2001 06:28:17 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SEQuF32728
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 06:26:56 -0800
Received: from ORANLT (oran-home-ss20.cisco.com [171.69.210.4])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id FAA28792;
	Wed, 28 Mar 2001 05:36:03 -0800 (PST)
From: "David R. Oran" <oran@cisco.com>
To: "'Martin, David P'" <David.P.Martin@nextel.com>,
        "'Michael Thomas'" <mat@cisco.com>
Cc: <seamoby@diameter.org>
Subject: RE: [seamoby] L2/L3 Paging
Date: Wed, 28 Mar 2001 08:35:57 -0500
Organization: Cisco Systems
Message-ID: <006901c0b78c$05cba330$04d245ab@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2511
In-Reply-To: <020A5EC56F3FD411B5230008C716D085868511@nhqntex01.nextel.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

If the L2 knows where the node is, then all paging does is force a
wakeup, right? Seems like you could invoke whatever mechanism is needed
for the wakeup (which somehow *has* to have components below L3 it seems
to me) when IP packets arrive for the host.

If the L2 does not know where the node is, then it has to find it. Is
this the mechanism you say always has L2 state? It would be helpful if
we L3 babes-in-the-woods could get a better understanding of just what
this state is, how quickly it degrades, and how a L3 could conveivably
make use of it (e.g. to keep routing tables correct), rather than
arguing about whether the function belongs exclusively in L2 or L3.

Here's a puzzler though. Maybe it will help illuminate why us L3 crazies
keep raining on the paging-is-done-just-fine-at-L2 parade. Let's say I
have a host with two radios, an 802.11 and a WCDMA. At some time it is
reachable through both of them but is receiving IP traffic through the
802.11 radio. Then it goes to sleep. New traffic arrives for it. Which
radio gets paged? Both? What if after going to sleep it wanders into a
multipath null for the 802.11. What causes the WCDMA to decide it needs
to page the node and wake it up?

There's *got* to be an interaction with L3 here somewhere, at least for
routing.

Donning my asbestos suit...

Dave.

> -----Original Message-----
> From: owner-seamoby@diameter.org 
> [mailto:owner-seamoby@diameter.org] On Behalf Of Martin, David P
> Sent: Monday, March 26, 2001 6:57 PM
> To: 'Michael Thomas'; Martin, David P
> Cc: seamoby@diameter.org
> Subject: RE: [seamoby] L2/L3 Paging
> 
> 
> Since I started this, I feel some obligation to help reach 
> closure ... 
> 
> First, I think we've reached consensus that in order to 
> deliver a packet or page that some type of location 
> information must be maintained somewhere in order to effect delivery. 
> 
> Second, is that location information is needed to support a 
> delivery mechanism (paging or direct delivery).
> 
> I think where we diverge is on whether should seamoby take on 
> this problem ...
> 
> So this leads to the following questions:
> * Do we assume that location information is known to layer 
> below IP? _Yes_ implies that there could be a trigger or some 
> other mechanism to give hints or direction on how to contact 
> the MN, and would greatly simplify the work for an initial protocol.
> 
> _No_ implies that location state would have to be developed 
> (at the network layer since that is where the IETF lives) and 
> would mean that some location state engine would have to be 
> developed to allow paging or packet delivery. This will 
> require a lot of work.
> 
> I would think that it would be more efficient to focus on 
> known mobility systems, and solve the more esoteric cases 
> later ... but will yield to the group's consensus.
> 
> 
> 
> <rant>
> Now, all mobility based technologies that I know maintain the 
> state information below IP.  So for all existing 
> technologies, we would be designing a redundant location 
> mechanism into the system.  This leads to interesting issues 
> ... If you have to choose between optimizing the protocol for 
> paging systems vs non-paging systems, which do you choose?  
> Which location mechanism do you use?  Do you have a choice?  
> You will probably be forced to at least use the lower layer 
> location mechanism.  If I have to use it, what added benefit 
> is an upper layer location mechanism?  
> My sense is that the problems/requirements/solutions for 
> systems that inherently support paging at layers below IP are 
> more defined, and that work could proceed more quickly in 
> that space.  General IP paging would be a complex solution to 
> a problem of unknown proportions, and it will probably take 
> more time to scope. </rant>
> 
> > 
> > 
> > Martin, David P writes:
> >  > >    This doesn't seem to hard: suppose you have a
> >  > >    beacon which all dormant nodes listen too. To
> >  > >    find a node, the last attachment point performs
> >  > >    a search in the local paging area. When the mobile
> >  > >    wakes up, it establishes a link to its current AP,
> >  > >    and a tunnel to the old AP to scoop up the
> >  > >    packet(s).
> >  >
> >  > I agree that a paging system can be designed that can work 
> > with a technology
> >  > that does not continually track a MN location.
> >  > 
> >  > However, a (working) paging system *cannot* be designed without a
> >  > registration mechanism.
> > 
> >    Sure.
> > 
> >  > The purpose of a registration mechanism is to
> >  > provide rough location state information on where a MN is
> > located in a
> >  > network topology.  This location state can be of several 
> > forms, specific
> >  > access point, specific paging zone, specific network 
> > (scalability issues),
> >  > last known access point, last known access zone, etc.  But 
> > the network has
> >  > to have some type of location information to even begin to 
> > guess on how to
> >  > start paging.
> > 
> >    Correct.
> > 
> >  > In your example above, the mobile in effect registers 
> upon  > wake 
> > up, giving the network location state to work with.
> > Of course a
> >  > mechanism must exist (at one or more layers) to deal with 
> > stale location
> >  > information.
> > 
> >    Yup.
> >  
> >  > So, I'm trying to say that there must be some location
> > state maintained
> >  > somewhere at layer 2, otherwise the entire network would 
> > behave as one big
> >  > LAN segment.
> > 
> >    I don't see this as having much to do with L2. If
> >    I can route an IP packet to the last known point
> >    of attachment, it could put out the dragnet by
> >    sending out IP packets which eventually (or not)
> >    find the mobile node. L2 location information may
> >    or may not be involved. At a base level, I don't
> >    think we should count on them being there though.
> > 
> > 	    Mike
> > 
> 



From owner-seamoby@diameter.org  Wed Mar 28 11:23:38 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03909
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 11:23:38 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SFSww00445
	for seamoby-list; Wed, 28 Mar 2001 07:28:58 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from atlsnmx1.nextel.com (atlsnmx1.nextel.com [167.20.198.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SFSrF00440
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 07:28:53 -0800
Received: from atlntgw01.nextel.com (atlntgw01.nextel.com [10.8.79.187])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id JAA20184;
	Wed, 28 Mar 2001 09:37:59 -0500 (EST)
Received: by atlntgw01.nextel.com with Internet Mail Service (5.5.2650.21)
	id <HKW3FQP9>; Wed, 28 Mar 2001 09:33:00 -0500
Message-ID: <020A5EC56F3FD411B5230008C716D08586852E@nhqntex01.nextel.com>
From: "Martin, David P" <David.P.Martin@nextel.com>
To: "'David R. Oran'" <oran@cisco.com>,
        "Martin, David P"
	 <David.P.Martin@nextel.com>,
        "'Michael Thomas'" <mat@cisco.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
Date: Wed, 28 Mar 2001 09:27:50 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

> Here's a puzzler though. Maybe it will help illuminate why us 
> L3 crazies
> keep raining on the paging-is-done-just-fine-at-L2 parade. Let's say I
> have a host with two radios, an 802.11 and a WCDMA. At some time it is
> reachable through both of them but is receiving IP traffic through the
> 802.11 radio. Then it goes to sleep. New traffic arrives for it. Which
> radio gets paged? Both? What if after going to sleep it wanders into a
> multipath null for the 802.11. What causes the WCDMA to 
> decide it needs
> to page the node and wake it up?

I agree that layer 3 paging is useful ... and I agree that layer 3 paging
would assist in the above scenario.  My concern is when layer 3 begins to
get involved in the assured delivery of packets between the edge router and
the end-point (AR-MN in this case).  In the example above, what if the MN
was in a deep fade for both technologies, do we buffer packets? for how
long?  What if the MN battery died or was removed for an extended period of
time (days)?  I realize these questions are in the solution space and we
have not yet entered the requirements phase.  But I am not clear if solving
these types of issues (assured delivery) would be part of the layer3 paging
protocol.  If we decide to take these issues on, I want it to be with eyes
wide open on the amount of work that will be required to address these
issues.  Otherwise, we can assume that the layer 2 interface(s) will handle
(or not) the delivery of the packet, and that the only thing we do with the
layer3 paging protocol is determine which interface(s) to deliver packets
to, which has substantial benefit in and of itself.





From owner-seamoby@diameter.org  Wed Mar 28 12:59:51 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA06516
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 12:59:49 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SHc8k00874
	for seamoby-list; Wed, 28 Mar 2001 09:38:08 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SHc3F00869
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 09:38:03 -0800
Received: from zrchb200.us.nortel.com by smtprch1.nortel.com;
          Wed, 28 Mar 2001 09:48:20 -0600
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <H3HYFFXP>; Wed, 28 Mar 2001 09:48:06 -0600
Message-ID: <85AA7486A2C1D411BCA20000F8073E4301AD1286@crchy271.us.nortel.com>
From: "Glenn Morrow" <gmorrow@nortelnetworks.com>
To: "David R. Oran" <oran@cisco.com>,
        "'Martin, David P'" <David.P.Martin@nextel.com>,
        "'Michael Thomas'" <mat@cisco.com>
Cc: seamoby <seamoby@diameter.org>
Subject: RE: [seamoby] L2/L3 Paging
Date: Wed, 28 Mar 2001 09:48:02 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0B79E.78FA28B0"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0B79E.78FA28B0
Content-Type: text/plain;
	charset="iso-8859-1"

Actually these are some good points and questions. Here are some of my
thoughts on this concept. Currently there is no method of representing the
concept of "paging areas/zones" in the IETF world. It seems evident to me
that L2 has to be involved in paging as the benefits in terms of reduced
power consumption is dependent on the L1/L2 as well. So if one did somehow
change IP routing to include the concept of a "paging zone" that could cross
subnets, sites, autonomous systems (roaming agreements) etc.. one could
conceivably create some sort of access independent L3 paging signaling that
each L2 could pay attention to i.e. wake up the mobile nodes via L2
mechanisms. 

Now in terms of "what that signaling should be" I see two possibilities.
Re-invent the wheel i.e. do something similar to what is done for cellular
today or just deliver multiple copies of IP packets to the subnets in this
new concept of a paging area/zone. Note: some cellular technologies call
this a routing area but please do not confuse this with the IETF concept of
routing area. The next paragraph explains how one might go about doing it
with multiple copies.

A set of COAs could be used by say a mobile's home subnet to perhaps tunnel
multiple copies of packets received to each subnet address indicated via
each COA the mobile had recently visited and binded with.

These recently visited subnets themselves may have configured routing
information indicating adjacent subnets for the "paging area/zone". This
would allow each subnet indicated via the COA to furthur copy and send the
packet to these adjacent subnets. Once received on each copied subnet the L2
mechanisms of paging that are access specific can attempt to "wake up" the
mobile and diliver the packet. In some cases the packet can be delivered at
the same time as the wakeup. We should probably change this home subnet
forwarding function to enable the smarts to know when the send an ICMP
unreachable message. I do not see a need to have the visited subnets to send
unreachables back to the home subnet's if they cannot deliver the packet or
successfully page the mobile. This approach simply relies on the delivery of
the packets as the L3 paging mechanism.

I'm sure there are other approaches as well with more detail of each level
or macro/micro point of view. The micros will tend to employ an anchor. 

The reinvention method would tend to employ SIP or something similar for
this function. I can definitely understand the pull in this direction as
well - i.e. that's how cellular works for circuit-based calls today. To
achieve the general solution, SIP will have to be built into every router
and SIP must begin paying attention to PIBs, FIBs, AS boundaries (roaming
agreements) etc.. IMHO. A counter argument to this might be that this stuff
will likely have to change with the other approach as well - some things to
think about as we forge forward. I believe both mechanisms would work. 

I think the "babes-in-the-woods" as you say should definitely understand
these issues and help make the decisions as we move forward. They have some
good experience and insight into "changing the IP world". 

I'm hoping these "babes" as you say are not bellheads in disguise posing as
IP fanatics (this is not directed to anyone personally. The motivation of
this "shock treatment" is to make people set back and really take a hard
look at how it should work for the long term).

Anyway these are my thoughts on the L2/L3 ying and yang and the upcoming
battle of approaches or rather assumptions. Hope this helps illuminate, at
least, some of the differing points of view.

Glenn

-----Original Message-----
From: David R. Oran [mailto:oran@cisco.com]
Sent: Wednesday, March 28, 2001 7:36 AM
To: 'Martin, David P'; 'Michael Thomas'
Cc: seamoby
Subject: RE: [seamoby] L2/L3 Paging


If the L2 knows where the node is, then all paging does is force a
wakeup, right? Seems like you could invoke whatever mechanism is needed
for the wakeup (which somehow *has* to have components below L3 it seems
to me) when IP packets arrive for the host.

If the L2 does not know where the node is, then it has to find it. Is
this the mechanism you say always has L2 state? It would be helpful if
we L3 babes-in-the-woods could get a better understanding of just what
this state is, how quickly it degrades, and how a L3 could conveivably
make use of it (e.g. to keep routing tables correct), rather than
arguing about whether the function belongs exclusively in L2 or L3.

Here's a puzzler though. Maybe it will help illuminate why us L3 crazies
keep raining on the paging-is-done-just-fine-at-L2 parade. Let's say I
have a host with two radios, an 802.11 and a WCDMA. At some time it is
reachable through both of them but is receiving IP traffic through the
802.11 radio. Then it goes to sleep. New traffic arrives for it. Which
radio gets paged? Both? What if after going to sleep it wanders into a
multipath null for the 802.11. What causes the WCDMA to decide it needs
to page the node and wake it up?

There's *got* to be an interaction with L3 here somewhere, at least for
routing.

Donning my asbestos suit...

Dave.

> -----Original Message-----
> From: owner-seamoby@diameter.org 
> [mailto:owner-seamoby@diameter.org] On Behalf Of Martin, David P
> Sent: Monday, March 26, 2001 6:57 PM
> To: 'Michael Thomas'; Martin, David P
> Cc: seamoby@diameter.org
> Subject: RE: [seamoby] L2/L3 Paging
> 
> 
> Since I started this, I feel some obligation to help reach 
> closure ... 
> 
> First, I think we've reached consensus that in order to 
> deliver a packet or page that some type of location 
> information must be maintained somewhere in order to effect delivery. 
> 
> Second, is that location information is needed to support a 
> delivery mechanism (paging or direct delivery).
> 
> I think where we diverge is on whether should seamoby take on 
> this problem ...
> 
> So this leads to the following questions:
> * Do we assume that location information is known to layer 
> below IP? _Yes_ implies that there could be a trigger or some 
> other mechanism to give hints or direction on how to contact 
> the MN, and would greatly simplify the work for an initial protocol.
> 
> _No_ implies that location state would have to be developed 
> (at the network layer since that is where the IETF lives) and 
> would mean that some location state engine would have to be 
> developed to allow paging or packet delivery. This will 
> require a lot of work.
> 
> I would think that it would be more efficient to focus on 
> known mobility systems, and solve the more esoteric cases 
> later ... but will yield to the group's consensus.
> 
> 
> 
> <rant>
> Now, all mobility based technologies that I know maintain the 
> state information below IP.  So for all existing 
> technologies, we would be designing a redundant location 
> mechanism into the system.  This leads to interesting issues 
> ... If you have to choose between optimizing the protocol for 
> paging systems vs non-paging systems, which do you choose?  
> Which location mechanism do you use?  Do you have a choice?  
> You will probably be forced to at least use the lower layer 
> location mechanism.  If I have to use it, what added benefit 
> is an upper layer location mechanism?  
> My sense is that the problems/requirements/solutions for 
> systems that inherently support paging at layers below IP are 
> more defined, and that work could proceed more quickly in 
> that space.  General IP paging would be a complex solution to 
> a problem of unknown proportions, and it will probably take 
> more time to scope. </rant>
> 
> > 
> > 
> > Martin, David P writes:
> >  > >    This doesn't seem to hard: suppose you have a
> >  > >    beacon which all dormant nodes listen too. To
> >  > >    find a node, the last attachment point performs
> >  > >    a search in the local paging area. When the mobile
> >  > >    wakes up, it establishes a link to its current AP,
> >  > >    and a tunnel to the old AP to scoop up the
> >  > >    packet(s).
> >  >
> >  > I agree that a paging system can be designed that can work 
> > with a technology
> >  > that does not continually track a MN location.
> >  > 
> >  > However, a (working) paging system *cannot* be designed without a
> >  > registration mechanism.
> > 
> >    Sure.
> > 
> >  > The purpose of a registration mechanism is to
> >  > provide rough location state information on where a MN is
> > located in a
> >  > network topology.  This location state can be of several 
> > forms, specific
> >  > access point, specific paging zone, specific network 
> > (scalability issues),
> >  > last known access point, last known access zone, etc.  But 
> > the network has
> >  > to have some type of location information to even begin to 
> > guess on how to
> >  > start paging.
> > 
> >    Correct.
> > 
> >  > In your example above, the mobile in effect registers 
> upon  > wake 
> > up, giving the network location state to work with.
> > Of course a
> >  > mechanism must exist (at one or more layers) to deal with 
> > stale location
> >  > information.
> > 
> >    Yup.
> >  
> >  > So, I'm trying to say that there must be some location
> > state maintained
> >  > somewhere at layer 2, otherwise the entire network would 
> > behave as one big
> >  > LAN segment.
> > 
> >    I don't see this as having much to do with L2. If
> >    I can route an IP packet to the last known point
> >    of attachment, it could put out the dragnet by
> >    sending out IP packets which eventually (or not)
> >    find the mobile node. L2 location information may
> >    or may not be involved. At a base level, I don't
> >    think we should count on them being there though.
> > 
> > 	    Mike
> > 
> 


------_=_NextPart_001_01C0B79E.78FA28B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: [seamoby] L2/L3 Paging</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Actually these are some good points and questions. =
Here are some of my thoughts on this concept. Currently there is no =
method of representing the concept of &quot;paging areas/zones&quot; in =
the IETF world. It seems evident to me that L2 has to be involved in =
paging as the benefits in terms of reduced power consumption is =
dependent on the L1/L2 as well. So if one did somehow change IP routing =
to include the concept of a &quot;paging zone&quot; that could cross =
subnets, sites, autonomous systems (roaming agreements) etc.. one could =
conceivably create some sort of access independent L3 paging signaling =
that each L2 could pay attention to i.e. wake up the mobile nodes via =
L2 mechanisms. </FONT></P>

<P><FONT SIZE=3D2>Now in terms of &quot;what that signaling should =
be&quot; I see two possibilities. Re-invent the wheel i.e. do something =
similar to what is done for cellular today or just deliver multiple =
copies of IP packets to the subnets in this new concept of a paging =
area/zone. Note: some cellular technologies call this a routing area =
but please do not confuse this with the IETF concept of routing area. =
The next paragraph explains how one might go about doing it with =
multiple copies.</FONT></P>

<P><FONT SIZE=3D2>A set of COAs could be used by say a mobile's home =
subnet to perhaps tunnel multiple copies of packets received to each =
subnet address indicated via each COA the mobile had recently visited =
and binded with.</FONT></P>

<P><FONT SIZE=3D2>These recently visited subnets themselves may have =
configured routing&nbsp; information indicating adjacent subnets for =
the &quot;paging area/zone&quot;. This would allow each subnet =
indicated via the COA to furthur copy and send the packet to these =
adjacent subnets. Once received on each copied subnet the L2 mechanisms =
of paging that are access specific can attempt to &quot;wake up&quot; =
the mobile and diliver the packet. In some cases the packet can be =
delivered at the same time as the wakeup. We should probably change =
this home subnet forwarding function to enable the smarts to know when =
the send an ICMP unreachable message. I do not see a need to have the =
visited subnets to send unreachables back to the home subnet's if they =
cannot deliver the packet or successfully page the mobile. This =
approach simply relies on the delivery of the packets as the L3 paging =
mechanism.</FONT></P>

<P><FONT SIZE=3D2>I'm sure there are other approaches as well with more =
detail of each level or macro/micro point of view. The micros will tend =
to employ an anchor. </FONT></P>

<P><FONT SIZE=3D2>The reinvention method would tend to employ SIP or =
something similar for this function. I can definitely understand the =
pull in this direction as well - i.e. that's how cellular works for =
circuit-based calls today. To achieve the general solution, SIP will =
have to be built into every router and SIP must begin paying attention =
to PIBs, FIBs, AS boundaries (roaming agreements) etc.. IMHO. A counter =
argument to this might be that this stuff will likely have to change =
with the other approach as well - some things to think about as we =
forge forward. I believe both mechanisms would work. </FONT></P>

<P><FONT SIZE=3D2>I think the &quot;babes-in-the-woods&quot; as you say =
should definitely understand these issues and help make the decisions =
as we move forward. They have some good experience and insight into =
&quot;changing the IP world&quot;. </FONT></P>

<P><FONT SIZE=3D2>I'm hoping these &quot;babes&quot; as you say are not =
bellheads in disguise posing as IP fanatics (this is not directed to =
anyone personally. The motivation of this &quot;shock treatment&quot; =
is to make people set back and really take a hard look at how it should =
work for the long term).</FONT></P>

<P><FONT SIZE=3D2>Anyway these are my thoughts on the L2/L3 ying and =
yang and the upcoming battle of approaches or rather assumptions. Hope =
this helps illuminate, at least, some of the differing points of =
view.</FONT></P>

<P><FONT SIZE=3D2>Glenn</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: David R. Oran [<A =
HREF=3D"mailto:oran@cisco.com">mailto:oran@cisco.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, March 28, 2001 7:36 AM</FONT>
<BR><FONT SIZE=3D2>To: 'Martin, David P'; 'Michael Thomas'</FONT>
<BR><FONT SIZE=3D2>Cc: seamoby</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [seamoby] L2/L3 Paging</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>If the L2 knows where the node is, then all paging =
does is force a</FONT>
<BR><FONT SIZE=3D2>wakeup, right? Seems like you could invoke whatever =
mechanism is needed</FONT>
<BR><FONT SIZE=3D2>for the wakeup (which somehow *has* to have =
components below L3 it seems</FONT>
<BR><FONT SIZE=3D2>to me) when IP packets arrive for the host.</FONT>
</P>

<P><FONT SIZE=3D2>If the L2 does not know where the node is, then it =
has to find it. Is</FONT>
<BR><FONT SIZE=3D2>this the mechanism you say always has L2 state? It =
would be helpful if</FONT>
<BR><FONT SIZE=3D2>we L3 babes-in-the-woods could get a better =
understanding of just what</FONT>
<BR><FONT SIZE=3D2>this state is, how quickly it degrades, and how a L3 =
could conveivably</FONT>
<BR><FONT SIZE=3D2>make use of it (e.g. to keep routing tables =
correct), rather than</FONT>
<BR><FONT SIZE=3D2>arguing about whether the function belongs =
exclusively in L2 or L3.</FONT>
</P>

<P><FONT SIZE=3D2>Here's a puzzler though. Maybe it will help =
illuminate why us L3 crazies</FONT>
<BR><FONT SIZE=3D2>keep raining on the paging-is-done-just-fine-at-L2 =
parade. Let's say I</FONT>
<BR><FONT SIZE=3D2>have a host with two radios, an 802.11 and a WCDMA. =
At some time it is</FONT>
<BR><FONT SIZE=3D2>reachable through both of them but is receiving IP =
traffic through the</FONT>
<BR><FONT SIZE=3D2>802.11 radio. Then it goes to sleep. New traffic =
arrives for it. Which</FONT>
<BR><FONT SIZE=3D2>radio gets paged? Both? What if after going to sleep =
it wanders into a</FONT>
<BR><FONT SIZE=3D2>multipath null for the 802.11. What causes the WCDMA =
to decide it needs</FONT>
<BR><FONT SIZE=3D2>to page the node and wake it up?</FONT>
</P>

<P><FONT SIZE=3D2>There's *got* to be an interaction with L3 here =
somewhere, at least for</FONT>
<BR><FONT SIZE=3D2>routing.</FONT>
</P>

<P><FONT SIZE=3D2>Donning my asbestos suit...</FONT>
</P>

<P><FONT SIZE=3D2>Dave.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: owner-seamoby@diameter.org </FONT>
<BR><FONT SIZE=3D2>&gt; [<A =
HREF=3D"mailto:owner-seamoby@diameter.org">mailto:owner-seamoby@diameter=
.org</A>] On Behalf Of Martin, David P</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Monday, March 26, 2001 6:57 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Michael Thomas'; Martin, David P</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: seamoby@diameter.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [seamoby] L2/L3 Paging</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Since I started this, I feel some obligation to =
help reach </FONT>
<BR><FONT SIZE=3D2>&gt; closure ... </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; First, I think we've reached consensus that in =
order to </FONT>
<BR><FONT SIZE=3D2>&gt; deliver a packet or page that some type of =
location </FONT>
<BR><FONT SIZE=3D2>&gt; information must be maintained somewhere in =
order to effect delivery. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Second, is that location information is needed =
to support a </FONT>
<BR><FONT SIZE=3D2>&gt; delivery mechanism (paging or direct =
delivery).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I think where we diverge is on whether should =
seamoby take on </FONT>
<BR><FONT SIZE=3D2>&gt; this problem ...</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; So this leads to the following =
questions:</FONT>
<BR><FONT SIZE=3D2>&gt; * Do we assume that location information is =
known to layer </FONT>
<BR><FONT SIZE=3D2>&gt; below IP? _Yes_ implies that there could be a =
trigger or some </FONT>
<BR><FONT SIZE=3D2>&gt; other mechanism to give hints or direction on =
how to contact </FONT>
<BR><FONT SIZE=3D2>&gt; the MN, and would greatly simplify the work for =
an initial protocol.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; _No_ implies that location state would have to =
be developed </FONT>
<BR><FONT SIZE=3D2>&gt; (at the network layer since that is where the =
IETF lives) and </FONT>
<BR><FONT SIZE=3D2>&gt; would mean that some location state engine =
would have to be </FONT>
<BR><FONT SIZE=3D2>&gt; developed to allow paging or packet delivery. =
This will </FONT>
<BR><FONT SIZE=3D2>&gt; require a lot of work.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I would think that it would be more efficient =
to focus on </FONT>
<BR><FONT SIZE=3D2>&gt; known mobility systems, and solve the more =
esoteric cases </FONT>
<BR><FONT SIZE=3D2>&gt; later ... but will yield to the group's =
consensus.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;rant&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Now, all mobility based technologies that I =
know maintain the </FONT>
<BR><FONT SIZE=3D2>&gt; state information below IP.&nbsp; So for all =
existing </FONT>
<BR><FONT SIZE=3D2>&gt; technologies, we would be designing a redundant =
location </FONT>
<BR><FONT SIZE=3D2>&gt; mechanism into the system.&nbsp; This leads to =
interesting issues </FONT>
<BR><FONT SIZE=3D2>&gt; ... If you have to choose between optimizing =
the protocol for </FONT>
<BR><FONT SIZE=3D2>&gt; paging systems vs non-paging systems, which do =
you choose?&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; Which location mechanism do you use?&nbsp; Do =
you have a choice?&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; You will probably be forced to at least use the =
lower layer </FONT>
<BR><FONT SIZE=3D2>&gt; location mechanism.&nbsp; If I have to use it, =
what added benefit </FONT>
<BR><FONT SIZE=3D2>&gt; is an upper layer location mechanism?&nbsp; =
</FONT>
<BR><FONT SIZE=3D2>&gt; My sense is that the =
problems/requirements/solutions for </FONT>
<BR><FONT SIZE=3D2>&gt; systems that inherently support paging at =
layers below IP are </FONT>
<BR><FONT SIZE=3D2>&gt; more defined, and that work could proceed more =
quickly in </FONT>
<BR><FONT SIZE=3D2>&gt; that space.&nbsp; General IP paging would be a =
complex solution to </FONT>
<BR><FONT SIZE=3D2>&gt; a problem of unknown proportions, and it will =
probably take </FONT>
<BR><FONT SIZE=3D2>&gt; more time to scope. &lt;/rant&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Martin, David P writes:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; This =
doesn't seem to hard: suppose you have a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; beacon =
which all dormant nodes listen too. To</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; find a =
node, the last attachment point performs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; a search =
in the local paging area. When the mobile</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; wakes =
up, it establishes a link to its current AP,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; and a =
tunnel to the old AP to scoop up the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; =
packet(s).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; I agree that a paging system =
can be designed that can work </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; with a technology</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; that does not continually track =
a MN location.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; However, a (working) paging =
system *cannot* be designed without a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; registration mechanism.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; Sure.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; The purpose of a registration =
mechanism is to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; provide rough location state =
information on where a MN is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; located in a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; network topology.&nbsp; This =
location state can be of several </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; forms, specific</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; access point, specific paging =
zone, specific network </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (scalability issues),</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; last known access point, last =
known access zone, etc.&nbsp; But </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the network has</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; to have some type of location =
information to even begin to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; guess on how to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; start paging.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; Correct.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; In your example above, the =
mobile in effect registers </FONT>
<BR><FONT SIZE=3D2>&gt; upon&nbsp; &gt; wake </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; up, giving the network location state to =
work with.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Of course a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; mechanism must exist (at one or =
more layers) to deal with </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; stale location</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; information.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; Yup.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; So, I'm trying to say that =
there must be some location</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; state maintained</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; somewhere at layer 2, otherwise =
the entire network would </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; behave as one big</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; LAN segment.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; I don't see this as =
having much to do with L2. If</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; I can route an IP packet =
to the last known point</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; of attachment, it could =
put out the dragnet by</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; sending out IP packets =
which eventually (or not)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; find the mobile node. L2 =
location information may</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; or may not be involved. =
At a base level, I don't</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; think we should count on =
them being there though.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
Mike</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0B79E.78FA28B0--


From owner-seamoby@diameter.org  Wed Mar 28 13:36:28 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA07151
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 13:36:28 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SHlpb00916
	for seamoby-list; Wed, 28 Mar 2001 09:47:51 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SHllF00911
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 09:47:48 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA17204;
	Wed, 28 Mar 2001 08:56:53 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA25867;
	Wed, 28 Mar 2001 08:56:52 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id IAA29332;
	Wed, 28 Mar 2001 08:56:52 -0800 (PST)
Message-Id: <200103281656.IAA29332@heliopolis.Eng.Sun.COM>
Date: Wed, 28 Mar 2001 08:56:52 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: Please Read the Problem Statement! (was: RE: [seamoby] L2/L3 Paging)
To: oran@cisco.com, David.P.Martin@nextel.com, mat@cisco.com,
        acasati@lucent.com
Cc: seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: C7MEZe3Fvlgfze3DeG3LHg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Folks,

I've seen a lot of arguments about L2 v.s. L3 paging, but I've the impression 
that some people making the arguments haven't read the problem statement.
The problem statement clearly outlines the problems an IP paging protocol 
could solve. Most of these problems are solvable without IP paging (with
perhaps the exception of unifying access to paging across disparate L2) but in
a very convoluted manner. IP paging would simplify them. Nothing in
the problem statement either precludes or requires L2 paging, but it
does explain why L2 paging may not be enough. Figuring out how to
get the requirements to reflect the role of L2 paging is necessary,
excluding L2 paging or rejecting L3 paging in favor of L2 only is not.

We are not going to be able to come up with a coherent set of requirements
if we are not all on the same page (so to speak :-) about the problems
we are trying to solve.  

		jak



From owner-seamoby@diameter.org  Wed Mar 28 13:50:04 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA07573
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 13:50:03 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SI2kN00973
	for seamoby-list; Wed, 28 Mar 2001 10:02:46 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SI2eF00968
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 10:02:41 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA26896;
	Wed, 28 Mar 2001 09:11:12 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA28909;
	Wed, 28 Mar 2001 09:11:12 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id JAA29684;
	Wed, 28 Mar 2001 09:11:11 -0800 (PST)
Message-Id: <200103281711.JAA29684@heliopolis.Eng.Sun.COM>
Date: Wed, 28 Mar 2001 09:11:11 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: Paging Functional Architecture ( was: RE: [seamoby] L2/L3 Paging)
To: oran@cisco.com, David.P.Martin@nextel.com, mat@cisco.com,
        gmorrow@nortelnetworks.com
Cc: seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: zXt5698BGZgP/ZHH6q6jUw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Glenn,

Your note follows along some of what I have been thinking about, except
in a more functional architectural way, which is more appropriate
for the requirements phase, I think.

Basically, the idea is to have 4 functional entities:

	- A paging agent at the edge which handles paging interaction
	between the mobile node and the network and between the tracking
	agent and mobile node (if necessary). This would also be the
	place for any interaction between L2 paging and L3 paging.
	
	- A tracking agent which is keeping track of the mobile node
	as it moves in dormant mode across areas controlled by
	paging agents.
	
	- An access router which is the last hop router before the air
	link.
	
	- The mobile node.
	
Note that these are functional entities, there is *absolutely no* committment
in their definition to any physical representation. For example, it is
entirely concevable that the paging agent and access router may be fused
in a final physical implementation. 

I have yet to fully think out what the functions are that each of these
entities would have in a paging architecture, but I am planning on
coming up with a section for the requirements draft that contains this
material, unless somebody else beats me to it. :-)

I find this kind of functional architectural process to be extremely helpful in
teasing out the basic issues without committing early to an implementation.
Much of the discussion on this thread has assumed various implementations,
which I think is entirely premature.

		jak
		
>Actually these are some good points and questions. Here are some of my
>thoughts on this concept. Currently there is no method of representing the
>concept of "paging areas/zones" in the IETF world. It seems evident to me
>that L2 has to be involved in paging as the benefits in terms of reduced
>power consumption is dependent on the L1/L2 as well. So if one did somehow
>change IP routing to include the concept of a "paging zone" that could cross
>subnets, sites, autonomous systems (roaming agreements) etc.. one could
>conceivably create some sort of access independent L3 paging signaling that
>each L2 could pay attention to i.e. wake up the mobile nodes via L2
>mechanisms. 
>
>Now in terms of "what that signaling should be" I see two possibilities.
>Re-invent the wheel i.e. do something similar to what is done for cellular
>today or just deliver multiple copies of IP packets to the subnets in this
>new concept of a paging area/zone. Note: some cellular technologies call
>this a routing area but please do not confuse this with the IETF concept of
>routing area. The next paragraph explains how one might go about doing it
>with multiple copies.
>
>A set of COAs could be used by say a mobile's home subnet to perhaps tunnel
>multiple copies of packets received to each subnet address indicated via
>each COA the mobile had recently visited and binded with.
>
>These recently visited subnets themselves may have configured routing
>information indicating adjacent subnets for the "paging area/zone". This
>would allow each subnet indicated via the COA to furthur copy and send the
>packet to these adjacent subnets. Once received on each copied subnet the L2
>mechanisms of paging that are access specific can attempt to "wake up" the
>mobile and diliver the packet. In some cases the packet can be delivered at
>the same time as the wakeup. We should probably change this home subnet
>forwarding function to enable the smarts to know when the send an ICMP
>unreachable message. I do not see a need to have the visited subnets to send
>unreachables back to the home subnet's if they cannot deliver the packet or
>successfully page the mobile. This approach simply relies on the delivery of
>the packets as the L3 paging mechanism.
>
>I'm sure there are other approaches as well with more detail of each level
>or macro/micro point of view. The micros will tend to employ an anchor. 
>
>The reinvention method would tend to employ SIP or something similar for
>this function. I can definitely understand the pull in this direction as
>well - i.e. that's how cellular works for circuit-based calls today. To
>achieve the general solution, SIP will have to be built into every router
>and SIP must begin paying attention to PIBs, FIBs, AS boundaries (roaming
>agreements) etc.. IMHO. A counter argument to this might be that this stuff
>will likely have to change with the other approach as well - some things to
>think about as we forge forward. I believe both mechanisms would work. 
>
>I think the "babes-in-the-woods" as you say should definitely understand
>these issues and help make the decisions as we move forward. They have some
>good experience and insight into "changing the IP world". 
>
>I'm hoping these "babes" as you say are not bellheads in disguise posing as
>IP fanatics (this is not directed to anyone personally. The motivation of
>this "shock treatment" is to make people set back and really take a hard
>look at how it should work for the long term).
>
>Anyway these are my thoughts on the L2/L3 ying and yang and the upcoming
>battle of approaches or rather assumptions. Hope this helps illuminate, at
>least, some of the differing points of view.
>
>Glenn
>
>-----Original Message-----
>From: David R. Oran [mailto:oran@cisco.com]
>Sent: Wednesday, March 28, 2001 7:36 AM
>To: 'Martin, David P'; 'Michael Thomas'
>Cc: seamoby
>Subject: RE: [seamoby] L2/L3 Paging
>
>
>If the L2 knows where the node is, then all paging does is force a
>wakeup, right? Seems like you could invoke whatever mechanism is needed
>for the wakeup (which somehow *has* to have components below L3 it seems
>to me) when IP packets arrive for the host.
>
>If the L2 does not know where the node is, then it has to find it. Is
>this the mechanism you say always has L2 state? It would be helpful if
>we L3 babes-in-the-woods could get a better understanding of just what
>this state is, how quickly it degrades, and how a L3 could conveivably
>make use of it (e.g. to keep routing tables correct), rather than
>arguing about whether the function belongs exclusively in L2 or L3.
>
>Here's a puzzler though. Maybe it will help illuminate why us L3 crazies
>keep raining on the paging-is-done-just-fine-at-L2 parade. Let's say I
>have a host with two radios, an 802.11 and a WCDMA. At some time it is
>reachable through both of them but is receiving IP traffic through the
>802.11 radio. Then it goes to sleep. New traffic arrives for it. Which
>radio gets paged? Both? What if after going to sleep it wanders into a
>multipath null for the 802.11. What causes the WCDMA to decide it needs
>to page the node and wake it up?
>
>There's *got* to be an interaction with L3 here somewhere, at least for
>routing.
>
>Donning my asbestos suit...
>
>Dave.
>
>> -----Original Message-----
>> From: owner-seamoby@diameter.org 
>> [mailto:owner-seamoby@diameter.org] On Behalf Of Martin, David P
>> Sent: Monday, March 26, 2001 6:57 PM
>> To: 'Michael Thomas'; Martin, David P
>> Cc: seamoby@diameter.org
>> Subject: RE: [seamoby] L2/L3 Paging
>> 
>> 
>> Since I started this, I feel some obligation to help reach 
>> closure ... 
>> 
>> First, I think we've reached consensus that in order to 
>> deliver a packet or page that some type of location 
>> information must be maintained somewhere in order to effect delivery. 
>> 
>> Second, is that location information is needed to support a 
>> delivery mechanism (paging or direct delivery).
>> 
>> I think where we diverge is on whether should seamoby take on 
>> this problem ...
>> 
>> So this leads to the following questions:
>> * Do we assume that location information is known to layer 
>> below IP? _Yes_ implies that there could be a trigger or some 
>> other mechanism to give hints or direction on how to contact 
>> the MN, and would greatly simplify the work for an initial protocol.
>> 
>> _No_ implies that location state would have to be developed 
>> (at the network layer since that is where the IETF lives) and 
>> would mean that some location state engine would have to be 
>> developed to allow paging or packet delivery. This will 
>> require a lot of work.
>> 
>> I would think that it would be more efficient to focus on 
>> known mobility systems, and solve the more esoteric cases 
>> later ... but will yield to the group's consensus.
>> 
>> 
>> 
>> <rant>
>> Now, all mobility based technologies that I know maintain the 
>> state information below IP.  So for all existing 
>> technologies, we would be designing a redundant location 
>> mechanism into the system.  This leads to interesting issues 
>> ... If you have to choose between optimizing the protocol for 
>> paging systems vs non-paging systems, which do you choose?  
>> Which location mechanism do you use?  Do you have a choice?  
>> You will probably be forced to at least use the lower layer 
>> location mechanism.  If I have to use it, what added benefit 
>> is an upper layer location mechanism?  
>> My sense is that the problems/requirements/solutions for 
>> systems that inherently support paging at layers below IP are 
>> more defined, and that work could proceed more quickly in 
>> that space.  General IP paging would be a complex solution to 
>> a problem of unknown proportions, and it will probably take 
>> more time to scope. </rant>
>> 
>> > 
>> > 
>> > Martin, David P writes:
>> >  > >    This doesn't seem to hard: suppose you have a
>> >  > >    beacon which all dormant nodes listen too. To
>> >  > >    find a node, the last attachment point performs
>> >  > >    a search in the local paging area. When the mobile
>> >  > >    wakes up, it establishes a link to its current AP,
>> >  > >    and a tunnel to the old AP to scoop up the
>> >  > >    packet(s).
>> >  >
>> >  > I agree that a paging system can be designed that can work 
>> > with a technology
>> >  > that does not continually track a MN location.
>> >  > 
>> >  > However, a (working) paging system *cannot* be designed without a
>> >  > registration mechanism.
>> > 
>> >    Sure.
>> > 
>> >  > The purpose of a registration mechanism is to
>> >  > provide rough location state information on where a MN is
>> > located in a
>> >  > network topology.  This location state can be of several 
>> > forms, specific
>> >  > access point, specific paging zone, specific network 
>> > (scalability issues),
>> >  > last known access point, last known access zone, etc.  But 
>> > the network has
>> >  > to have some type of location information to even begin to 
>> > guess on how to
>> >  > start paging.
>> > 
>> >    Correct.
>> > 
>> >  > In your example above, the mobile in effect registers 
>> upon  > wake 
>> > up, giving the network location state to work with.
>> > Of course a
>> >  > mechanism must exist (at one or more layers) to deal with 
>> > stale location
>> >  > information.
>> > 
>> >    Yup.
>> >  
>> >  > So, I'm trying to say that there must be some location
>> > state maintained
>> >  > somewhere at layer 2, otherwise the entire network would 
>> > behave as one big
>> >  > LAN segment.
>> > 
>> >    I don't see this as having much to do with L2. If
>> >    I can route an IP packet to the last known point
>> >    of attachment, it could put out the dragnet by
>> >    sending out IP packets which eventually (or not)
>> >    find the mobile node. L2 location information may
>> >    or may not be involved. At a base level, I don't
>> >    think we should count on them being there though.
>> > 
>> > 	    Mike
>> > 
>> 
>



From owner-seamoby@diameter.org  Wed Mar 28 14:22:13 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA08609
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 14:22:12 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SIgvD01119
	for seamoby-list; Wed, 28 Mar 2001 10:42:57 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SIgnF01113
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 10:42:50 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id JAA11820;
	Wed, 28 Mar 2001 09:51:56 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADF01570;
	Wed, 28 Mar 2001 09:51:51 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id JAA03271; Wed, 28 Mar 2001 09:51:51 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15042.9399.74528.166906@thomasm-u1.cisco.com>
Date: Wed, 28 Mar 2001 09:51:51 -0800 (PST)
To: "Martin, David P" <David.P.Martin@nextel.com>
Cc: "'David R. Oran'" <oran@cisco.com>, "'Michael Thomas'" <mat@cisco.com>,
        seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
In-Reply-To: <020A5EC56F3FD411B5230008C716D08586852E@nhqntex01.nextel.com>
References: <020A5EC56F3FD411B5230008C716D08586852E@nhqntex01.nextel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Martin, David P writes:
 > I agree that layer 3 paging is useful ... and I agree that layer 3 paging
 > would assist in the above scenario.  My concern is when layer 3 begins to
 > get involved in the assured delivery of packets between the edge router and
 > the end-point (AR-MN in this case).  In the example above, what if the MN
 > was in a deep fade for both technologies, do we buffer packets? for how
 > long?  What if the MN battery died or was removed for an extended period of
 > time (days)?  I realize these questions are in the solution space and we
 > have not yet entered the requirements phase.  But I am not clear if solving
 > these types of issues (assured delivery) would be part of the layer3 paging
 > protocol.

David,

I hate to keep harping on this, but this sure
seems to me to be familar ground. The problems you
point out also would come up with a demand dialer
type of interface, like say an ISDN line which
isn't up all of the time. While the solutions may
not be entirely algorithmic, the parameters are
certainly well understood by now.

	Mike


From owner-seamoby@diameter.org  Wed Mar 28 14:28:43 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA08979
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 14:28:43 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SI5qY00985
	for seamoby-list; Wed, 28 Mar 2001 10:05:52 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SI5mF00980
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 10:05:48 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA29799;
	Wed, 28 Mar 2001 09:14:54 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA23127;
	Wed, 28 Mar 2001 09:14:54 -0800 (PST)
Received: from darius (darius [10.6.84.105])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id JAA29091;
	Wed, 28 Mar 2001 09:14:50 -0800 (PST)
Date: Wed, 28 Mar 2001 09:14:46 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: Re: Please Read the Problem Statement! (was: RE: [seamoby] L2/L3 Paging)
To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Cc: oran@cisco.com, David.P.Martin@nextel.com, mat@cisco.com,
        acasati@lucent.com, seamoby@diameter.org
In-Reply-To: "Your message with ID" <200103281656.IAA29332@heliopolis.Eng.Sun.COM>
Message-ID: <Roam.SIMC.2.0.6.985799686.14792.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> We are not going to be able to come up with a coherent set of requirements
> if we are not all on the same page (so to speak :-) about the problems
> we are trying to solve.  

So perhaps a more constructive method would be for people to comment on the
draft, and state their objection with specific text.

PatC



From owner-seamoby@diameter.org  Wed Mar 28 14:40:08 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA09430
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 14:40:08 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SHRgW00844
	for seamoby-list; Wed, 28 Mar 2001 09:27:42 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SHRbF00839
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 09:27:37 -0800
Received: from hoemail2.firewall.lucent.com (localhost [127.0.0.1])
	by hoemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id LAA05152
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 11:36:47 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-160-150.lucent.com [135.86.160.150])
	by hoemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id LAA05119
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 11:36:47 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2650.21)
	id <HYP11HDN>; Wed, 28 Mar 2001 17:36:46 +0100
Message-ID: <976F7C55E3B2D111A0720008C728549C097CC25F@en0060exch001u.uk.lucent.com>
From: "Casati, Alessio (Alessio)" <acasati@lucent.com>
To: "'David R. Oran'" <oran@cisco.com>,
        "'Martin, David P'"
	 <David.P.Martin@nextel.com>,
        "'Michael Thomas'" <mat@cisco.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
Date: Wed, 28 Mar 2001 17:36:43 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk


Here's a puzzler though. Maybe it will help illuminate why us L3 crazies
keep raining on the paging-is-done-just-fine-at-L2 parade. Let's say I
have a host with two radios, an 802.11 and a WCDMA. At some time it is
reachable through both of them but is receiving IP traffic through the
802.11 radio. 

IP reachability on 2 interfaces: Same IP address? Or not?

If "Yes" then I assume you are using a mobile IP arrangement which
allows for simultaneous transmission to the 2 distinct APs (I'm not
considering/implying the case the 2 APs advertise the same (host)routes-
in which case similar things would hold). 

If "Not", the answer to the following is obvious.

Then it goes to sleep. New traffic arrives for it. Which
radio gets paged? Both? What if after going to sleep it wanders into a
multipath null for the 802.11. 

I assume, in the ensuing discussion, the answer 
was "yes".
So, what happens when traffic comes in? Bot interfaces will deliver
so WCDMA will page, and 802.11 will do the equivalent thing.
If on one of the two or none there is no coverage, then packets
will be lost (and ICMP dest unreachable maybe sent back )
on the AP that has lost the MN connectivity.

We also don't need L3 paging.

What causes the WCDMA to decide it needs
to page the node and wake it up?


Incoming packets.





From owner-seamoby@diameter.org  Wed Mar 28 15:34:52 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA10640
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 15:34:51 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SJPwE01228
	for seamoby-list; Wed, 28 Mar 2001 11:25:58 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SJPrF01223
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 11:25:54 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA03770;
	Wed, 28 Mar 2001 10:34:59 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f2SIYvo23546;
	Wed, 28 Mar 2001 10:34:57 -0800
X-mProtect:  Wed, 28 Mar 2001 10:34:57 -0800 Nokia Silicon Valley Messaging Protection
Received: from tpagtzis.iprg.nokia.com (205.226.2.115, claiming to be "cs.ucl.ac.uk")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdEqbZSb; Wed, 28 Mar 2001 10:31:43 PST
Message-ID: <3AC22E10.AD9BE00C@cs.ucl.ac.uk>
Date: Wed, 28 Mar 2001 10:31:44 -0800
From: Theo Pagtzis <t.pagtzis@cs.ucl.ac.uk>
Reply-To: tpagtzis@iprg.nokia.com
Organization: UCL/NOKIA
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1-STABLE i386)
X-Accept-Language: el, en
MIME-Version: 1.0
To: "David R. Oran" <oran@cisco.com>
CC: "'Martin, David P'" <David.P.Martin@nextel.com>,
        "'Michael Thomas'" <mat@cisco.com>, seamoby <seamoby@diameter.org>
Subject: Re: [seamoby] L2/L3 Paging
References: <006901c0b78c$05cba330$04d245ab@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

"David R. Oran" wrote:

> If the L2 knows where the node is, then all paging does is force a
> wakeup, right? Seems like you could invoke whatever mechanism is needed
> for the wakeup (which somehow *has* to have components below L3 it seems
> to me) when IP packets arrive for the host.
>
> If the L2 does not know where the node is, then it has to find it. Is
> this the mechanism you say always has L2 state? It would be helpful if
> we L3 babes-in-the-woods could get a better understanding of just what
> this state is, how quickly it degrades, and how a L3 could conveivably
> make use of it (e.g. to keep routing tables correct), rather than
> arguing about whether the function belongs exclusively in L2 or L3.
>
> Here's a puzzler though. Maybe it will help illuminate why us L3 crazies
> keep raining on the paging-is-done-just-fine-at-L2 parade. Let's say I
> have a host with two radios, an 802.11 and a WCDMA. At some time it is
> reachable through both of them but is receiving IP traffic through the
> 802.11 radio. Then it goes to sleep. New traffic arrives for it. Which
> radio gets paged? Both? What if after going to sleep it wanders into a
> multipath null for the 802.11. What causes the WCDMA to decide it needs
> to page the node and wake it up?

I am not sure I follow the argument here..perhaps you could illuminate a
little more here..

First a Mobile Node does not go to sleep. It is the interface that goes to
sleep. The timing between which 802.11 and WCDMA interfaces
will go to sleep if power control is effected will/must be different for
the two interfaces.

If traffic is being sent to the 802.11 the MAC protocol has got a period
over which it checks the NAV for pending traffic delivery

With respect to WCDMA the spec mentions that although it is possible to
trigger gated DPCCH transmission from a higher layer, the downlink
or uplink can operate at gated mode with either embedding DPDCH or with the
DPDCH always off and the DPCCH toggling between on/off states according to
the gating rate, so that the UE can check (by TPC commands) which timeslot
it need to turn on (DPDCH) and receive data frames on the DPDCH

I thus do not see why it would require an extra IP packet to be sent to
trigger L2 in both technologies so that the UE would get paged...

Traffic would always come on a particular interface so that interface need
wake up by its MAC upon pending traffic..

Don't you agree?


Theo


UCL / Mobile Systems




>
> There's *got* to be an interaction with L3 here somewhere, at least for
> routing.
>
> Donning my asbestos suit...
>
> Dave.



From owner-seamoby@diameter.org  Wed Mar 28 15:45:04 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA10856
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 15:45:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SJvuH01298
	for seamoby-list; Wed, 28 Mar 2001 11:57:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from smtprch2.nortel.com (smtprch2.nortelnetworks.com [192.135.215.15])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SJvBF01293
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 11:57:15 -0800
Received: from zrchb200.us.nortel.com by smtprch2.nortel.com;
          Wed, 28 Mar 2001 12:48:58 -0600
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <H3HYFMZ6>; Wed, 28 Mar 2001 12:54:07 -0600
Message-ID: <85AA7486A2C1D411BCA20000F8073E4301AD15CB@crchy271.us.nortel.com>
From: "Glenn Morrow" <gmorrow@nortelnetworks.com>
To: James Kempf <kempf@heliopolis.Eng.Sun.COM>, oran@cisco.com,
        David.P.Martin@nextel.com, mat@cisco.com
Cc: seamoby@diameter.org
Subject: RE: Paging Functional Architecture ( was: RE: [seamoby] L2/L3 Pag ing)
Date: Wed, 28 Mar 2001 12:54:04 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0B7B8.75BB2B80"
X-Orig: <gmorrow@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0B7B8.75BB2B80
Content-Type: text/plain;
	charset="iso-8859-1"

James,

I agree it is premature to discuss solutions. I just wanted to get across
some of the main approaches I have heard over the years.

Thanks,

Glenn

-----Original Message-----
From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
Sent: Wednesday, March 28, 2001 11:11 AM
To: oran@cisco.com; David.P.Martin@nextel.com; mat@cisco.com; Morrow,
Glenn [RICH2:C330:EXCH]
Cc: seamoby@diameter.org
Subject: Paging Functional Architecture ( was: RE: [seamoby] L2/L3
Paging)


Glenn,

Your note follows along some of what I have been thinking about, except
in a more functional architectural way, which is more appropriate
for the requirements phase, I think.

Basically, the idea is to have 4 functional entities:

	- A paging agent at the edge which handles paging interaction
	between the mobile node and the network and between the tracking
	agent and mobile node (if necessary). This would also be the
	place for any interaction between L2 paging and L3 paging.
	
	- A tracking agent which is keeping track of the mobile node
	as it moves in dormant mode across areas controlled by
	paging agents.
	
	- An access router which is the last hop router before the air
	link.
	
	- The mobile node.
	
Note that these are functional entities, there is *absolutely no*
committment
in their definition to any physical representation. For example, it is
entirely concevable that the paging agent and access router may be fused
in a final physical implementation. 

I have yet to fully think out what the functions are that each of these
entities would have in a paging architecture, but I am planning on
coming up with a section for the requirements draft that contains this
material, unless somebody else beats me to it. :-)

I find this kind of functional architectural process to be extremely helpful
in
teasing out the basic issues without committing early to an implementation.
Much of the discussion on this thread has assumed various implementations,
which I think is entirely premature.

		jak
		
>Actually these are some good points and questions. Here are some of my
>thoughts on this concept. Currently there is no method of representing the
>concept of "paging areas/zones" in the IETF world. It seems evident to me
>that L2 has to be involved in paging as the benefits in terms of reduced
>power consumption is dependent on the L1/L2 as well. So if one did somehow
>change IP routing to include the concept of a "paging zone" that could
cross
>subnets, sites, autonomous systems (roaming agreements) etc.. one could
>conceivably create some sort of access independent L3 paging signaling that
>each L2 could pay attention to i.e. wake up the mobile nodes via L2
>mechanisms. 
>
>Now in terms of "what that signaling should be" I see two possibilities.
>Re-invent the wheel i.e. do something similar to what is done for cellular
>today or just deliver multiple copies of IP packets to the subnets in this
>new concept of a paging area/zone. Note: some cellular technologies call
>this a routing area but please do not confuse this with the IETF concept of
>routing area. The next paragraph explains how one might go about doing it
>with multiple copies.
>
>A set of COAs could be used by say a mobile's home subnet to perhaps tunnel
>multiple copies of packets received to each subnet address indicated via
>each COA the mobile had recently visited and binded with.
>
>These recently visited subnets themselves may have configured routing
>information indicating adjacent subnets for the "paging area/zone". This
>would allow each subnet indicated via the COA to furthur copy and send the
>packet to these adjacent subnets. Once received on each copied subnet the
L2
>mechanisms of paging that are access specific can attempt to "wake up" the
>mobile and diliver the packet. In some cases the packet can be delivered at
>the same time as the wakeup. We should probably change this home subnet
>forwarding function to enable the smarts to know when the send an ICMP
>unreachable message. I do not see a need to have the visited subnets to
send
>unreachables back to the home subnet's if they cannot deliver the packet or
>successfully page the mobile. This approach simply relies on the delivery
of
>the packets as the L3 paging mechanism.
>
>I'm sure there are other approaches as well with more detail of each level
>or macro/micro point of view. The micros will tend to employ an anchor. 
>
>The reinvention method would tend to employ SIP or something similar for
>this function. I can definitely understand the pull in this direction as
>well - i.e. that's how cellular works for circuit-based calls today. To
>achieve the general solution, SIP will have to be built into every router
>and SIP must begin paying attention to PIBs, FIBs, AS boundaries (roaming
>agreements) etc.. IMHO. A counter argument to this might be that this stuff
>will likely have to change with the other approach as well - some things to
>think about as we forge forward. I believe both mechanisms would work. 
>
>I think the "babes-in-the-woods" as you say should definitely understand
>these issues and help make the decisions as we move forward. They have some
>good experience and insight into "changing the IP world". 
>
>I'm hoping these "babes" as you say are not bellheads in disguise posing as
>IP fanatics (this is not directed to anyone personally. The motivation of
>this "shock treatment" is to make people set back and really take a hard
>look at how it should work for the long term).
>
>Anyway these are my thoughts on the L2/L3 ying and yang and the upcoming
>battle of approaches or rather assumptions. Hope this helps illuminate, at
>least, some of the differing points of view.
>
>Glenn
>
>-----Original Message-----
>From: David R. Oran [mailto:oran@cisco.com]
>Sent: Wednesday, March 28, 2001 7:36 AM
>To: 'Martin, David P'; 'Michael Thomas'
>Cc: seamoby
>Subject: RE: [seamoby] L2/L3 Paging
>
>
>If the L2 knows where the node is, then all paging does is force a
>wakeup, right? Seems like you could invoke whatever mechanism is needed
>for the wakeup (which somehow *has* to have components below L3 it seems
>to me) when IP packets arrive for the host.
>
>If the L2 does not know where the node is, then it has to find it. Is
>this the mechanism you say always has L2 state? It would be helpful if
>we L3 babes-in-the-woods could get a better understanding of just what
>this state is, how quickly it degrades, and how a L3 could conveivably
>make use of it (e.g. to keep routing tables correct), rather than
>arguing about whether the function belongs exclusively in L2 or L3.
>
>Here's a puzzler though. Maybe it will help illuminate why us L3 crazies
>keep raining on the paging-is-done-just-fine-at-L2 parade. Let's say I
>have a host with two radios, an 802.11 and a WCDMA. At some time it is
>reachable through both of them but is receiving IP traffic through the
>802.11 radio. Then it goes to sleep. New traffic arrives for it. Which
>radio gets paged? Both? What if after going to sleep it wanders into a
>multipath null for the 802.11. What causes the WCDMA to decide it needs
>to page the node and wake it up?
>
>There's *got* to be an interaction with L3 here somewhere, at least for
>routing.
>
>Donning my asbestos suit...
>
>Dave.
>
>> -----Original Message-----
>> From: owner-seamoby@diameter.org 
>> [mailto:owner-seamoby@diameter.org] On Behalf Of Martin, David P
>> Sent: Monday, March 26, 2001 6:57 PM
>> To: 'Michael Thomas'; Martin, David P
>> Cc: seamoby@diameter.org
>> Subject: RE: [seamoby] L2/L3 Paging
>> 
>> 
>> Since I started this, I feel some obligation to help reach 
>> closure ... 
>> 
>> First, I think we've reached consensus that in order to 
>> deliver a packet or page that some type of location 
>> information must be maintained somewhere in order to effect delivery. 
>> 
>> Second, is that location information is needed to support a 
>> delivery mechanism (paging or direct delivery).
>> 
>> I think where we diverge is on whether should seamoby take on 
>> this problem ...
>> 
>> So this leads to the following questions:
>> * Do we assume that location information is known to layer 
>> below IP? _Yes_ implies that there could be a trigger or some 
>> other mechanism to give hints or direction on how to contact 
>> the MN, and would greatly simplify the work for an initial protocol.
>> 
>> _No_ implies that location state would have to be developed 
>> (at the network layer since that is where the IETF lives) and 
>> would mean that some location state engine would have to be 
>> developed to allow paging or packet delivery. This will 
>> require a lot of work.
>> 
>> I would think that it would be more efficient to focus on 
>> known mobility systems, and solve the more esoteric cases 
>> later ... but will yield to the group's consensus.
>> 
>> 
>> 
>> <rant>
>> Now, all mobility based technologies that I know maintain the 
>> state information below IP.  So for all existing 
>> technologies, we would be designing a redundant location 
>> mechanism into the system.  This leads to interesting issues 
>> ... If you have to choose between optimizing the protocol for 
>> paging systems vs non-paging systems, which do you choose?  
>> Which location mechanism do you use?  Do you have a choice?  
>> You will probably be forced to at least use the lower layer 
>> location mechanism.  If I have to use it, what added benefit 
>> is an upper layer location mechanism?  
>> My sense is that the problems/requirements/solutions for 
>> systems that inherently support paging at layers below IP are 
>> more defined, and that work could proceed more quickly in 
>> that space.  General IP paging would be a complex solution to 
>> a problem of unknown proportions, and it will probably take 
>> more time to scope. </rant>
>> 
>> > 
>> > 
>> > Martin, David P writes:
>> >  > >    This doesn't seem to hard: suppose you have a
>> >  > >    beacon which all dormant nodes listen too. To
>> >  > >    find a node, the last attachment point performs
>> >  > >    a search in the local paging area. When the mobile
>> >  > >    wakes up, it establishes a link to its current AP,
>> >  > >    and a tunnel to the old AP to scoop up the
>> >  > >    packet(s).
>> >  >
>> >  > I agree that a paging system can be designed that can work 
>> > with a technology
>> >  > that does not continually track a MN location.
>> >  > 
>> >  > However, a (working) paging system *cannot* be designed without a
>> >  > registration mechanism.
>> > 
>> >    Sure.
>> > 
>> >  > The purpose of a registration mechanism is to
>> >  > provide rough location state information on where a MN is
>> > located in a
>> >  > network topology.  This location state can be of several 
>> > forms, specific
>> >  > access point, specific paging zone, specific network 
>> > (scalability issues),
>> >  > last known access point, last known access zone, etc.  But 
>> > the network has
>> >  > to have some type of location information to even begin to 
>> > guess on how to
>> >  > start paging.
>> > 
>> >    Correct.
>> > 
>> >  > In your example above, the mobile in effect registers 
>> upon  > wake 
>> > up, giving the network location state to work with.
>> > Of course a
>> >  > mechanism must exist (at one or more layers) to deal with 
>> > stale location
>> >  > information.
>> > 
>> >    Yup.
>> >  
>> >  > So, I'm trying to say that there must be some location
>> > state maintained
>> >  > somewhere at layer 2, otherwise the entire network would 
>> > behave as one big
>> >  > LAN segment.
>> > 
>> >    I don't see this as having much to do with L2. If
>> >    I can route an IP packet to the last known point
>> >    of attachment, it could put out the dragnet by
>> >    sending out IP packets which eventually (or not)
>> >    find the mobile node. L2 location information may
>> >    or may not be involved. At a base level, I don't
>> >    think we should count on them being there though.
>> > 
>> > 	    Mike
>> > 
>> 
>


------_=_NextPart_001_01C0B7B8.75BB2B80
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: Paging Functional Architecture ( was: RE: [seamoby] L2/L3 =
Paging)</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>James,</FONT>
</P>

<P><FONT SIZE=3D2>I agree it is premature to discuss solutions. I just =
wanted to get across some of the main approaches I have heard over the =
years.</FONT></P>

<P><FONT SIZE=3D2>Thanks,</FONT>
</P>

<P><FONT SIZE=3D2>Glenn</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: James Kempf [<A =
HREF=3D"mailto:kempf@heliopolis.Eng.Sun.COM">mailto:kempf@heliopolis.Eng=
.Sun.COM</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, March 28, 2001 11:11 AM</FONT>
<BR><FONT SIZE=3D2>To: oran@cisco.com; David.P.Martin@nextel.com; =
mat@cisco.com; Morrow,</FONT>
<BR><FONT SIZE=3D2>Glenn [RICH2:C330:EXCH]</FONT>
<BR><FONT SIZE=3D2>Cc: seamoby@diameter.org</FONT>
<BR><FONT SIZE=3D2>Subject: Paging Functional Architecture ( was: RE: =
[seamoby] L2/L3</FONT>
<BR><FONT SIZE=3D2>Paging)</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Glenn,</FONT>
</P>

<P><FONT SIZE=3D2>Your note follows along some of what I have been =
thinking about, except</FONT>
<BR><FONT SIZE=3D2>in a more functional architectural way, which is =
more appropriate</FONT>
<BR><FONT SIZE=3D2>for the requirements phase, I think.</FONT>
</P>

<P><FONT SIZE=3D2>Basically, the idea is to have 4 functional =
entities:</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>- A paging =
agent at the edge which handles paging interaction</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>between =
the mobile node and the network and between the tracking</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>agent and =
mobile node (if necessary). This would also be the</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>place for =
any interaction between L2 paging and L3 paging.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>- A =
tracking agent which is keeping track of the mobile node</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>as it =
moves in dormant mode across areas controlled by</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>paging =
agents.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>- An =
access router which is the last hop router before the air</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>link.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>- The =
mobile node.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR><FONT SIZE=3D2>Note that these are functional entities, there is =
*absolutely no* committment</FONT>
<BR><FONT SIZE=3D2>in their definition to any physical representation. =
For example, it is</FONT>
<BR><FONT SIZE=3D2>entirely concevable that the paging agent and access =
router may be fused</FONT>
<BR><FONT SIZE=3D2>in a final physical implementation. </FONT>
</P>

<P><FONT SIZE=3D2>I have yet to fully think out what the functions are =
that each of these</FONT>
<BR><FONT SIZE=3D2>entities would have in a paging architecture, but I =
am planning on</FONT>
<BR><FONT SIZE=3D2>coming up with a section for the requirements draft =
that contains this</FONT>
<BR><FONT SIZE=3D2>material, unless somebody else beats me to it. =
:-)</FONT>
</P>

<P><FONT SIZE=3D2>I find this kind of functional architectural process =
to be extremely helpful in</FONT>
<BR><FONT SIZE=3D2>teasing out the basic issues without committing =
early to an implementation.</FONT>
<BR><FONT SIZE=3D2>Much of the discussion on this thread has assumed =
various implementations,</FONT>
<BR><FONT SIZE=3D2>which I think is entirely premature.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>jak</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR><FONT SIZE=3D2>&gt;Actually these are some good points and =
questions. Here are some of my</FONT>
<BR><FONT SIZE=3D2>&gt;thoughts on this concept. Currently there is no =
method of representing the</FONT>
<BR><FONT SIZE=3D2>&gt;concept of &quot;paging areas/zones&quot; in the =
IETF world. It seems evident to me</FONT>
<BR><FONT SIZE=3D2>&gt;that L2 has to be involved in paging as the =
benefits in terms of reduced</FONT>
<BR><FONT SIZE=3D2>&gt;power consumption is dependent on the L1/L2 as =
well. So if one did somehow</FONT>
<BR><FONT SIZE=3D2>&gt;change IP routing to include the concept of a =
&quot;paging zone&quot; that could cross</FONT>
<BR><FONT SIZE=3D2>&gt;subnets, sites, autonomous systems (roaming =
agreements) etc.. one could</FONT>
<BR><FONT SIZE=3D2>&gt;conceivably create some sort of access =
independent L3 paging signaling that</FONT>
<BR><FONT SIZE=3D2>&gt;each L2 could pay attention to i.e. wake up the =
mobile nodes via L2</FONT>
<BR><FONT SIZE=3D2>&gt;mechanisms. </FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;Now in terms of &quot;what that signaling should =
be&quot; I see two possibilities.</FONT>
<BR><FONT SIZE=3D2>&gt;Re-invent the wheel i.e. do something similar to =
what is done for cellular</FONT>
<BR><FONT SIZE=3D2>&gt;today or just deliver multiple copies of IP =
packets to the subnets in this</FONT>
<BR><FONT SIZE=3D2>&gt;new concept of a paging area/zone. Note: some =
cellular technologies call</FONT>
<BR><FONT SIZE=3D2>&gt;this a routing area but please do not confuse =
this with the IETF concept of</FONT>
<BR><FONT SIZE=3D2>&gt;routing area. The next paragraph explains how =
one might go about doing it</FONT>
<BR><FONT SIZE=3D2>&gt;with multiple copies.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;A set of COAs could be used by say a mobile's =
home subnet to perhaps tunnel</FONT>
<BR><FONT SIZE=3D2>&gt;multiple copies of packets received to each =
subnet address indicated via</FONT>
<BR><FONT SIZE=3D2>&gt;each COA the mobile had recently visited and =
binded with.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;These recently visited subnets themselves may =
have configured routing</FONT>
<BR><FONT SIZE=3D2>&gt;information indicating adjacent subnets for the =
&quot;paging area/zone&quot;. This</FONT>
<BR><FONT SIZE=3D2>&gt;would allow each subnet indicated via the COA to =
furthur copy and send the</FONT>
<BR><FONT SIZE=3D2>&gt;packet to these adjacent subnets. Once received =
on each copied subnet the L2</FONT>
<BR><FONT SIZE=3D2>&gt;mechanisms of paging that are access specific =
can attempt to &quot;wake up&quot; the</FONT>
<BR><FONT SIZE=3D2>&gt;mobile and diliver the packet. In some cases the =
packet can be delivered at</FONT>
<BR><FONT SIZE=3D2>&gt;the same time as the wakeup. We should probably =
change this home subnet</FONT>
<BR><FONT SIZE=3D2>&gt;forwarding function to enable the smarts to know =
when the send an ICMP</FONT>
<BR><FONT SIZE=3D2>&gt;unreachable message. I do not see a need to have =
the visited subnets to send</FONT>
<BR><FONT SIZE=3D2>&gt;unreachables back to the home subnet's if they =
cannot deliver the packet or</FONT>
<BR><FONT SIZE=3D2>&gt;successfully page the mobile. This approach =
simply relies on the delivery of</FONT>
<BR><FONT SIZE=3D2>&gt;the packets as the L3 paging mechanism.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;I'm sure there are other approaches as well with =
more detail of each level</FONT>
<BR><FONT SIZE=3D2>&gt;or macro/micro point of view. The micros will =
tend to employ an anchor. </FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;The reinvention method would tend to employ SIP =
or something similar for</FONT>
<BR><FONT SIZE=3D2>&gt;this function. I can definitely understand the =
pull in this direction as</FONT>
<BR><FONT SIZE=3D2>&gt;well - i.e. that's how cellular works for =
circuit-based calls today. To</FONT>
<BR><FONT SIZE=3D2>&gt;achieve the general solution, SIP will have to =
be built into every router</FONT>
<BR><FONT SIZE=3D2>&gt;and SIP must begin paying attention to PIBs, =
FIBs, AS boundaries (roaming</FONT>
<BR><FONT SIZE=3D2>&gt;agreements) etc.. IMHO. A counter argument to =
this might be that this stuff</FONT>
<BR><FONT SIZE=3D2>&gt;will likely have to change with the other =
approach as well - some things to</FONT>
<BR><FONT SIZE=3D2>&gt;think about as we forge forward. I believe both =
mechanisms would work. </FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;I think the &quot;babes-in-the-woods&quot; as =
you say should definitely understand</FONT>
<BR><FONT SIZE=3D2>&gt;these issues and help make the decisions as we =
move forward. They have some</FONT>
<BR><FONT SIZE=3D2>&gt;good experience and insight into &quot;changing =
the IP world&quot;. </FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;I'm hoping these &quot;babes&quot; as you say =
are not bellheads in disguise posing as</FONT>
<BR><FONT SIZE=3D2>&gt;IP fanatics (this is not directed to anyone =
personally. The motivation of</FONT>
<BR><FONT SIZE=3D2>&gt;this &quot;shock treatment&quot; is to make =
people set back and really take a hard</FONT>
<BR><FONT SIZE=3D2>&gt;look at how it should work for the long =
term).</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;Anyway these are my thoughts on the L2/L3 ying =
and yang and the upcoming</FONT>
<BR><FONT SIZE=3D2>&gt;battle of approaches or rather assumptions. Hope =
this helps illuminate, at</FONT>
<BR><FONT SIZE=3D2>&gt;least, some of the differing points of =
view.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;Glenn</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt;From: David R. Oran [<A =
HREF=3D"mailto:oran@cisco.com">mailto:oran@cisco.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt;Sent: Wednesday, March 28, 2001 7:36 AM</FONT>
<BR><FONT SIZE=3D2>&gt;To: 'Martin, David P'; 'Michael Thomas'</FONT>
<BR><FONT SIZE=3D2>&gt;Cc: seamoby</FONT>
<BR><FONT SIZE=3D2>&gt;Subject: RE: [seamoby] L2/L3 Paging</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;If the L2 knows where the node is, then all =
paging does is force a</FONT>
<BR><FONT SIZE=3D2>&gt;wakeup, right? Seems like you could invoke =
whatever mechanism is needed</FONT>
<BR><FONT SIZE=3D2>&gt;for the wakeup (which somehow *has* to have =
components below L3 it seems</FONT>
<BR><FONT SIZE=3D2>&gt;to me) when IP packets arrive for the =
host.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;If the L2 does not know where the node is, then =
it has to find it. Is</FONT>
<BR><FONT SIZE=3D2>&gt;this the mechanism you say always has L2 state? =
It would be helpful if</FONT>
<BR><FONT SIZE=3D2>&gt;we L3 babes-in-the-woods could get a better =
understanding of just what</FONT>
<BR><FONT SIZE=3D2>&gt;this state is, how quickly it degrades, and how =
a L3 could conveivably</FONT>
<BR><FONT SIZE=3D2>&gt;make use of it (e.g. to keep routing tables =
correct), rather than</FONT>
<BR><FONT SIZE=3D2>&gt;arguing about whether the function belongs =
exclusively in L2 or L3.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;Here's a puzzler though. Maybe it will help =
illuminate why us L3 crazies</FONT>
<BR><FONT SIZE=3D2>&gt;keep raining on the =
paging-is-done-just-fine-at-L2 parade. Let's say I</FONT>
<BR><FONT SIZE=3D2>&gt;have a host with two radios, an 802.11 and a =
WCDMA. At some time it is</FONT>
<BR><FONT SIZE=3D2>&gt;reachable through both of them but is receiving =
IP traffic through the</FONT>
<BR><FONT SIZE=3D2>&gt;802.11 radio. Then it goes to sleep. New traffic =
arrives for it. Which</FONT>
<BR><FONT SIZE=3D2>&gt;radio gets paged? Both? What if after going to =
sleep it wanders into a</FONT>
<BR><FONT SIZE=3D2>&gt;multipath null for the 802.11. What causes the =
WCDMA to decide it needs</FONT>
<BR><FONT SIZE=3D2>&gt;to page the node and wake it up?</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;There's *got* to be an interaction with L3 here =
somewhere, at least for</FONT>
<BR><FONT SIZE=3D2>&gt;routing.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;Donning my asbestos suit...</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;Dave.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; From: owner-seamoby@diameter.org </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; [<A =
HREF=3D"mailto:owner-seamoby@diameter.org">mailto:owner-seamoby@diameter=
.org</A>] On Behalf Of Martin, David P</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; Sent: Monday, March 26, 2001 6:57 PM</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; To: 'Michael Thomas'; Martin, David =
P</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; Cc: seamoby@diameter.org</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; Subject: RE: [seamoby] L2/L3 Paging</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; Since I started this, I feel some =
obligation to help reach </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; closure ... </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; First, I think we've reached consensus that =
in order to </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; deliver a packet or page that some type of =
location </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; information must be maintained somewhere in =
order to effect delivery. </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; Second, is that location information is =
needed to support a </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; delivery mechanism (paging or direct =
delivery).</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; I think where we diverge is on whether =
should seamoby take on </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; this problem ...</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; So this leads to the following =
questions:</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; * Do we assume that location information is =
known to layer </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; below IP? _Yes_ implies that there could be =
a trigger or some </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; other mechanism to give hints or direction =
on how to contact </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; the MN, and would greatly simplify the work =
for an initial protocol.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; _No_ implies that location state would have =
to be developed </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; (at the network layer since that is where =
the IETF lives) and </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; would mean that some location state engine =
would have to be </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; developed to allow paging or packet =
delivery. This will </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; require a lot of work.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; I would think that it would be more =
efficient to focus on </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; known mobility systems, and solve the more =
esoteric cases </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; later ... but will yield to the group's =
consensus.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &lt;rant&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; Now, all mobility based technologies that I =
know maintain the </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; state information below IP.&nbsp; So for =
all existing </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; technologies, we would be designing a =
redundant location </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; mechanism into the system.&nbsp; This leads =
to interesting issues </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; ... If you have to choose between =
optimizing the protocol for </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; paging systems vs non-paging systems, which =
do you choose?&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; Which location mechanism do you use?&nbsp; =
Do you have a choice?&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; You will probably be forced to at least use =
the lower layer </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; location mechanism.&nbsp; If I have to use =
it, what added benefit </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; is an upper layer location mechanism?&nbsp; =
</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; My sense is that the =
problems/requirements/solutions for </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; systems that inherently support paging at =
layers below IP are </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; more defined, and that work could proceed =
more quickly in </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; that space.&nbsp; General IP paging would =
be a complex solution to </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; a problem of unknown proportions, and it =
will probably take </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; more time to scope. &lt;/rant&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; Martin, David P writes:</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; This =
doesn't seem to hard: suppose you have a</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; =
beacon which all dormant nodes listen too. To</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; find =
a node, the last attachment point performs</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; a =
search in the local paging area. When the mobile</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; =
wakes up, it establishes a link to its current AP,</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; and =
a tunnel to the old AP to scoop up the</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; &gt;&nbsp;&nbsp;&nbsp; =
packet(s).</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; I agree that a paging =
system can be designed that can work </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; with a technology</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; that does not continually =
track a MN location.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; However, a (working) paging =
system *cannot* be designed without a</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; registration =
mechanism.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp;&nbsp;&nbsp; Sure.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; The purpose of a =
registration mechanism is to</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; provide rough location =
state information on where a MN is</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; located in a</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; network topology.&nbsp; =
This location state can be of several </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; forms, specific</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; access point, specific =
paging zone, specific network </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; (scalability issues),</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; last known access point, =
last known access zone, etc.&nbsp; But </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; the network has</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; to have some type of =
location information to even begin to </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; guess on how to</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; start paging.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp;&nbsp;&nbsp; Correct.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; In your example above, the =
mobile in effect registers </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; upon&nbsp; &gt; wake </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; up, giving the network location state =
to work with.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; Of course a</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; mechanism must exist (at =
one or more layers) to deal with </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; stale location</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; information.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp;&nbsp;&nbsp; Yup.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; So, I'm trying to say that =
there must be some location</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; state maintained</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; somewhere at layer 2, =
otherwise the entire network would </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; behave as one big</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp; &gt; LAN segment.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp;&nbsp;&nbsp; I don't see this as =
having much to do with L2. If</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp;&nbsp;&nbsp; I can route an IP =
packet to the last known point</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp;&nbsp;&nbsp; of attachment, it =
could put out the dragnet by</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp;&nbsp;&nbsp; sending out IP =
packets which eventually (or not)</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp;&nbsp;&nbsp; find the mobile =
node. L2 location information may</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp;&nbsp;&nbsp; or may not be =
involved. At a base level, I don't</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt;&nbsp;&nbsp;&nbsp; think we should =
count on them being there though.</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
Mike</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0B7B8.75BB2B80--


From owner-seamoby@diameter.org  Wed Mar 28 16:10:12 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11550
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 16:10:11 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SKFLT01349
	for seamoby-list; Wed, 28 Mar 2001 12:15:21 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from hoemlsrv.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SKE2F01344
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 12:14:02 -0800
Received: from hoemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id OAA00582
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 14:23:12 -0500 (EST)
Received: from nwmail.wh.lucent.com (h135-5-40-100.lucent.com [135.5.40.100])
	by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with SMTP id OAA00572
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 14:23:12 -0500 (EST)
Received: by nwmail.wh.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id OAA21932; Wed, 28 Mar 2001 14:23:10 -0500
Received: from lucent.com by nwmail.wh.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id OAA21925; Wed, 28 Mar 2001 14:23:09 -0500
Message-ID: <3AC23A1C.4C3C87E8@lucent.com>
Date: Wed, 28 Mar 2001 14:23:08 -0500
From: Erik Anderlind <eanderlind@lucent.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: seamoby@diameter.org
Subject: Re: Paging Functional Architecture ( was: RE: [seamoby] L2/L3 Paging)
References: <200103281711.JAA29684@heliopolis.Eng.Sun.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Glenn,
We need to be careful in defining functional entities such as the paging
and 
tracking agent - we do not want to preclude that these functions could
be 
provided in a distributed way (e.g. a subset of routers all implement
the function.)

I also disagree that it is a requirement that the paging agent has to be
at 
the "last hop" edge in all cases.

Another useful entity is correspondent node/application that initiates
the higher level 
need for paging. It will help identify requiremnts around how the other
different 
entities are located and addressed (if needed).
..Erik


James Kempf wrote:
> 
> Glenn,
> 
> Your note follows along some of what I have been thinking about, except
> in a more functional architectural way, which is more appropriate
> for the requirements phase, I think.
> 
> Basically, the idea is to have 4 functional entities:
> 
>         - A paging agent at the edge which handles paging interaction
>         between the mobile node and the network and between the tracking
>         agent and mobile node (if necessary). This would also be the
>         place for any interaction between L2 paging and L3 paging.
> 
>         - A tracking agent which is keeping track of the mobile node
>         as it moves in dormant mode across areas controlled by
>         paging agents.
> 
>         - An access router which is the last hop router before the air
>         link.
> 
>         - The mobile node.
> 
> Note that these are functional entities, there is *absolutely no* committment
> in their definition to any physical representation. For example, it is
> entirely concevable that the paging agent and access router may be fused
> in a final physical implementation.
> 
> I have yet to fully think out what the functions are that each of these
> entities would have in a paging architecture, but I am planning on
> coming up with a section for the requirements draft that contains this
> material, unless somebody else beats me to it. :-)
> 
> I find this kind of functional architectural process to be extremely helpful in
> teasing out the basic issues without committing early to an implementation.
> Much of the discussion on this thread has assumed various implementations,
> which I think is entirely premature.
> 
>                 jak
> 
> >Actually these are some good points and questions. Here are some of my
> >thoughts on this concept. Currently there is no method of representing the
> >concept of "paging areas/zones" in the IETF world. It seems evident to me
> >that L2 has to be involved in paging as the benefits in terms of reduced
> >power consumption is dependent on the L1/L2 as well. So if one did somehow
> >change IP routing to include the concept of a "paging zone" that could cross
> >subnets, sites, autonomous systems (roaming agreements) etc.. one could
> >conceivably create some sort of access independent L3 paging signaling that
> >each L2 could pay attention to i.e. wake up the mobile nodes via L2
> >mechanisms.
> >
> >Now in terms of "what that signaling should be" I see two possibilities.
> >Re-invent the wheel i.e. do something similar to what is done for cellular
> >today or just deliver multiple copies of IP packets to the subnets in this
> >new concept of a paging area/zone. Note: some cellular technologies call
> >this a routing area but please do not confuse this with the IETF concept of
> >routing area. The next paragraph explains how one might go about doing it
> >with multiple copies.
> >
> >A set of COAs could be used by say a mobile's home subnet to perhaps tunnel
> >multiple copies of packets received to each subnet address indicated via
> >each COA the mobile had recently visited and binded with.
> >
> >These recently visited subnets themselves may have configured routing
> >information indicating adjacent subnets for the "paging area/zone". This
> >would allow each subnet indicated via the COA to furthur copy and send the
> >packet to these adjacent subnets. Once received on each copied subnet the L2
> >mechanisms of paging that are access specific can attempt to "wake up" the
> >mobile and diliver the packet. In some cases the packet can be delivered at
> >the same time as the wakeup. We should probably change this home subnet
> >forwarding function to enable the smarts to know when the send an ICMP
> >unreachable message. I do not see a need to have the visited subnets to send
> >unreachables back to the home subnet's if they cannot deliver the packet or
> >successfully page the mobile. This approach simply relies on the delivery of
> >the packets as the L3 paging mechanism.
> >
> >I'm sure there are other approaches as well with more detail of each level
> >or macro/micro point of view. The micros will tend to employ an anchor.
> >
> >The reinvention method would tend to employ SIP or something similar for
> >this function. I can definitely understand the pull in this direction as
> >well - i.e. that's how cellular works for circuit-based calls today. To
> >achieve the general solution, SIP will have to be built into every router
> >and SIP must begin paying attention to PIBs, FIBs, AS boundaries (roaming
> >agreements) etc.. IMHO. A counter argument to this might be that this stuff
> >will likely have to change with the other approach as well - some things to
> >think about as we forge forward. I believe both mechanisms would work.
> >
> >I think the "babes-in-the-woods" as you say should definitely understand
> >these issues and help make the decisions as we move forward. They have some
> >good experience and insight into "changing the IP world".
> >
> >I'm hoping these "babes" as you say are not bellheads in disguise posing as
> >IP fanatics (this is not directed to anyone personally. The motivation of
> >this "shock treatment" is to make people set back and really take a hard
> >look at how it should work for the long term).
> >
> >Anyway these are my thoughts on the L2/L3 ying and yang and the upcoming
> >battle of approaches or rather assumptions. Hope this helps illuminate, at
> >least, some of the differing points of view.
> >
> >Glenn
> >
> >-----Original Message-----
> >From: David R. Oran [mailto:oran@cisco.com]
> >Sent: Wednesday, March 28, 2001 7:36 AM
> >To: 'Martin, David P'; 'Michael Thomas'
> >Cc: seamoby
> >Subject: RE: [seamoby] L2/L3 Paging
> >
> >
> >If the L2 knows where the node is, then all paging does is force a
> >wakeup, right? Seems like you could invoke whatever mechanism is needed
> >for the wakeup (which somehow *has* to have components below L3 it seems
> >to me) when IP packets arrive for the host.
> >
> >If the L2 does not know where the node is, then it has to find it. Is
> >this the mechanism you say always has L2 state? It would be helpful if
> >we L3 babes-in-the-woods could get a better understanding of just what
> >this state is, how quickly it degrades, and how a L3 could conveivably
> >make use of it (e.g. to keep routing tables correct), rather than
> >arguing about whether the function belongs exclusively in L2 or L3.
> >
> >Here's a puzzler though. Maybe it will help illuminate why us L3 crazies
> >keep raining on the paging-is-done-just-fine-at-L2 parade. Let's say I
> >have a host with two radios, an 802.11 and a WCDMA. At some time it is
> >reachable through both of them but is receiving IP traffic through the
> >802.11 radio. Then it goes to sleep. New traffic arrives for it. Which
> >radio gets paged? Both? What if after going to sleep it wanders into a
> >multipath null for the 802.11. What causes the WCDMA to decide it needs
> >to page the node and wake it up?
> >
> >There's *got* to be an interaction with L3 here somewhere, at least for
> >routing.
> >
> >Donning my asbestos suit...
> >
> >Dave.
> >
> >> -----Original Message-----
> >> From: owner-seamoby@diameter.org
> >> [mailto:owner-seamoby@diameter.org] On Behalf Of Martin, David P
> >> Sent: Monday, March 26, 2001 6:57 PM
> >> To: 'Michael Thomas'; Martin, David P
> >> Cc: seamoby@diameter.org
> >> Subject: RE: [seamoby] L2/L3 Paging
> >>
> >>
> >> Since I started this, I feel some obligation to help reach
> >> closure ...
> >>
> >> First, I think we've reached consensus that in order to
> >> deliver a packet or page that some type of location
> >> information must be maintained somewhere in order to effect delivery.
> >>
> >> Second, is that location information is needed to support a
> >> delivery mechanism (paging or direct delivery).
> >>
> >> I think where we diverge is on whether should seamoby take on
> >> this problem ...
> >>
> >> So this leads to the following questions:
> >> * Do we assume that location information is known to layer
> >> below IP? _Yes_ implies that there could be a trigger or some
> >> other mechanism to give hints or direction on how to contact
> >> the MN, and would greatly simplify the work for an initial protocol.
> >>
> >> _No_ implies that location state would have to be developed
> >> (at the network layer since that is where the IETF lives) and
> >> would mean that some location state engine would have to be
> >> developed to allow paging or packet delivery. This will
> >> require a lot of work.
> >>
> >> I would think that it would be more efficient to focus on
> >> known mobility systems, and solve the more esoteric cases
> >> later ... but will yield to the group's consensus.
> >>
> >>
> >>
> >> <rant>
> >> Now, all mobility based technologies that I know maintain the
> >> state information below IP.  So for all existing
> >> technologies, we would be designing a redundant location
> >> mechanism into the system.  This leads to interesting issues
> >> ... If you have to choose between optimizing the protocol for
> >> paging systems vs non-paging systems, which do you choose?
> >> Which location mechanism do you use?  Do you have a choice?
> >> You will probably be forced to at least use the lower layer
> >> location mechanism.  If I have to use it, what added benefit
> >> is an upper layer location mechanism?
> >> My sense is that the problems/requirements/solutions for
> >> systems that inherently support paging at layers below IP are
> >> more defined, and that work could proceed more quickly in
> >> that space.  General IP paging would be a complex solution to
> >> a problem of unknown proportions, and it will probably take
> >> more time to scope. </rant>
> >>
> >> >
> >> >
> >> > Martin, David P writes:
> >> >  > >    This doesn't seem to hard: suppose you have a
> >> >  > >    beacon which all dormant nodes listen too. To
> >> >  > >    find a node, the last attachment point performs
> >> >  > >    a search in the local paging area. When the mobile
> >> >  > >    wakes up, it establishes a link to its current AP,
> >> >  > >    and a tunnel to the old AP to scoop up the
> >> >  > >    packet(s).
> >> >  >
> >> >  > I agree that a paging system can be designed that can work
> >> > with a technology
> >> >  > that does not continually track a MN location.
> >> >  >
> >> >  > However, a (working) paging system *cannot* be designed without a
> >> >  > registration mechanism.
> >> >
> >> >    Sure.
> >> >
> >> >  > The purpose of a registration mechanism is to
> >> >  > provide rough location state information on where a MN is
> >> > located in a
> >> >  > network topology.  This location state can be of several
> >> > forms, specific
> >> >  > access point, specific paging zone, specific network
> >> > (scalability issues),
> >> >  > last known access point, last known access zone, etc.  But
> >> > the network has
> >> >  > to have some type of location information to even begin to
> >> > guess on how to
> >> >  > start paging.
> >> >
> >> >    Correct.
> >> >
> >> >  > In your example above, the mobile in effect registers
> >> upon  > wake
> >> > up, giving the network location state to work with.
> >> > Of course a
> >> >  > mechanism must exist (at one or more layers) to deal with
> >> > stale location
> >> >  > information.
> >> >
> >> >    Yup.
> >> >
> >> >  > So, I'm trying to say that there must be some location
> >> > state maintained
> >> >  > somewhere at layer 2, otherwise the entire network would
> >> > behave as one big
> >> >  > LAN segment.
> >> >
> >> >    I don't see this as having much to do with L2. If
> >> >    I can route an IP packet to the last known point
> >> >    of attachment, it could put out the dragnet by
> >> >    sending out IP packets which eventually (or not)
> >> >    find the mobile node. L2 location information may
> >> >    or may not be involved. At a base level, I don't
> >> >    think we should count on them being there though.
> >> >
> >> >        Mike
> >> >
> >>
> >


From owner-seamoby@diameter.org  Wed Mar 28 16:33:08 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA12455
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 16:33:07 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SKVN201397
	for seamoby-list; Wed, 28 Mar 2001 12:31:23 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SKVIF01392
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 12:31:18 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id LAA06615;
	Wed, 28 Mar 2001 11:40:30 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADF04672;
	Wed, 28 Mar 2001 11:40:24 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA03287; Wed, 28 Mar 2001 11:40:24 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15042.15911.963421.823296@thomasm-u1.cisco.com>
Date: Wed, 28 Mar 2001 11:40:23 -0800 (PST)
To: Erik Anderlind <eanderlind@lucent.com>
Cc: seamoby@diameter.org
Subject: Re: Paging Functional Architecture ( was: RE: [seamoby] L2/L3 Paging)
In-Reply-To: <3AC23A1C.4C3C87E8@lucent.com>
References: <200103281711.JAA29684@heliopolis.Eng.Sun.COM>
	<3AC23A1C.4C3C87E8@lucent.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Erik Anderlind writes:
 > Another useful entity is correspondent node/application that initiates
 > the higher level 
 > need for paging. It will help identify requiremnts around how the other
 > different 
 > entities are located and addressed (if needed).

   Can you describe a use for such a user controlled
   paging mechanism? I can see a lot of security 
   problems inherent with allowing that; it would
   be nice to know what useful things that can't
   be done with a more controlled form of paging
   before we make it a requirement and hence have
   to tackle the harder security requirements.

	     Mike


From owner-seamoby@diameter.org  Wed Mar 28 16:39:39 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA12604
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 16:39:39 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SKYfv01408
	for seamoby-list; Wed, 28 Mar 2001 12:34:41 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SKYbF01403
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 12:34:37 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id LAA25369;
	Wed, 28 Mar 2001 11:43:46 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADF04793;
	Wed, 28 Mar 2001 11:43:41 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA03290; Wed, 28 Mar 2001 11:43:41 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15042.16109.19775.299619@thomasm-u1.cisco.com>
Date: Wed, 28 Mar 2001 11:43:41 -0800 (PST)
To: Erik Anderlind <eanderlind@lucent.com>
Cc: seamoby@diameter.org
Subject: Re: Paging Functional Architecture ( was: RE: [seamoby] L2/L3 Paging)
In-Reply-To: <3AC23A1C.4C3C87E8@lucent.com>
References: <200103281711.JAA29684@heliopolis.Eng.Sun.COM>
	<3AC23A1C.4C3C87E8@lucent.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Erik Anderlind writes:
 > I also disagree that it is a requirement that the paging agent has to be
 > at 
 > the "last hop" edge in all cases.

   One thing that I would attach to this requirement is
   that routers must be able to recognize that a page
   is necessary without having to rely on packet
   inspection. Ie, it must use the ordinary
   routing infrastructure (its FIB typically) to
   determine that a page is necesasry.

		  Mike


From owner-seamoby@diameter.org  Wed Mar 28 17:43:08 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA14287
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 17:43:08 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SL80Z01536
	for seamoby-list; Wed, 28 Mar 2001 13:08:00 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SL7tF01531
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 13:07:55 -0800
Received: from ihemail2.firewall.lucent.com (localhost [127.0.0.1])
	by ihemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id PAA03034
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 15:17:06 -0500 (EST)
Received: from nwmail.wh.lucent.com (h135-5-40-100.lucent.com [135.5.40.100])
	by ihemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with SMTP id PAA03018
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 15:17:06 -0500 (EST)
Received: by nwmail.wh.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id PAA04879; Wed, 28 Mar 2001 15:17:04 -0500
Received: from lucent.com by nwmail.wh.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id PAA04874; Wed, 28 Mar 2001 15:17:03 -0500
Message-ID: <3AC246BE.A209494C@lucent.com>
Date: Wed, 28 Mar 2001 15:17:02 -0500
From: Erik Anderlind <eanderlind@lucent.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: seamoby@diameter.org
Subject: [seamoby] Re: Paging Functional Architecture
References: <200103281711.JAA29684@heliopolis.Eng.Sun.COM>
		<3AC23A1C.4C3C87E8@lucent.com> <15042.15911.963421.823296@thomasm-u1.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Mike,

Michael Thomas wrote:
> 
> Erik Anderlind writes:
>  > Another useful entity is correspondent node/application that initiates
>  > the higher level
>  > need for paging. It will help identify requiremnts around how the other
>  > different
>  > entities are located and addressed (if needed).
> 
>    Can you describe a use for such a user controlled
>    paging mechanism? I can see a lot of security
>    problems inherent with allowing that; it would
>    be nice to know what useful things that can't
>    be done with a more controlled form of paging
>    before we make it a requirement and hence have
>    to tackle the harder security requirements.
> 
>              Mike

The IP traffic that eventually results in a page has to be initiated
from somewhere. (Just like a voice call in cellular eventually causes
the HLR to initiate a paging action that is executed by the MSC and one
or several 
base stations.) We need to properly abstract this entity and see it as
an IP packet source.
Is it always the MIP HA? (Don't think so.)

Imagine a SIP call - we want to ensure the INVITE (I think this is the
msg name) 
is forwarded to the mobile in a 
timely manner. For other types of traffic, timeliness is not an issue
and 
a page perhaps shouldn't be sent. (The policy itself is of course out of
scope 
from protocol design, but I feel being able to implement a policy
somewhere otside of 
the mobile should be a requirement.) Paging a mobile vending machine to
update its 
SW probably doesn't need as timely delivery of the page. Polling of
reachability
using ICMP doesn't seem like a good solution, so I think there is
something to do.

Any paging brings out the security issue of who may use it. Simple
approaches
are to use e.g. firewalls to filter all but certain source addresses.
Anything
beyond that we probably need to look at security mechnisms. (Use one 
of the available security mechanisms - don't design a new one.) Except
for
802.11, most wireless networks charge per minute or per packet for
access - it wouldn't
be acceptable if anyone could run down a user's account by sending
spurious
packets that result in pages.

User control over this mechanism is a seperate requirement. Not sure yet
that it 
needs to be part of the protocol (e.g. having an HTTP config interface
seems like a 
better alternative.)
...Erik


From owner-seamoby@diameter.org  Wed Mar 28 17:44:02 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA14322
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 17:44:01 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SLQvf01583
	for seamoby-list; Wed, 28 Mar 2001 13:26:57 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SLQrF01578
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 13:26:53 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id MAA11303;
	Wed, 28 Mar 2001 12:36:19 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADF06185;
	Wed, 28 Mar 2001 12:35:58 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id MAA03296; Wed, 28 Mar 2001 12:35:57 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15042.19245.828315.338037@thomasm-u1.cisco.com>
Date: Wed, 28 Mar 2001 12:35:57 -0800 (PST)
To: Erik Anderlind <eanderlind@lucent.com>
Cc: seamoby@diameter.org
Subject: [seamoby] what stimulates a page?
In-Reply-To: <3AC246BE.A209494C@lucent.com>
References: <200103281711.JAA29684@heliopolis.Eng.Sun.COM>
	<3AC23A1C.4C3C87E8@lucent.com>
	<15042.15911.963421.823296@thomasm-u1.cisco.com>
	<3AC246BE.A209494C@lucent.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


[I wanted to break out this out because there are
 some important requirements you've touched on]

Erik Anderlind writes:
 > Any paging brings out the security issue of who may use it. Simple
 > approaches
 > are to use e.g. firewalls to filter all but certain source addresses.
 > Anything
 > beyond that we probably need to look at security mechnisms. (Use one 
 > of the available security mechanisms - don't design a new one.) Except
 > for
 > 802.11, most wireless networks charge per minute or per packet for
 > access - it wouldn't
 > be acceptable if anyone could run down a user's account by sending
 > spurious
 > packets that result in pages.

   Yes, indeed. In fact there is fairly trivial
   DoS attack to drain somebody's battery or wallet
   just by sending a slow trickle of IP packets to
   the mobile node. To some extent these may be
   unavoidable for a determined attacker, but it
   seems to me that a useful requirement for paging
   is that the mobile be able to set up access control
   lists at some inside router -- I think it must be at
   the access router -- to prevent spurious or malicious
   packets to cause the mobile node to wake and possibly
   bring up a traffic channel.

   I'm conflicted how this should be announced by the
   mobile node to the AR and/or Pager. My gut level
   feeling is that this really ought to be dealt
   with by BURP, as in we feed our requirements to
   them for paging, but not try to solve this part 
   of the problem in isolation.

	  Mike


From owner-seamoby@diameter.org  Wed Mar 28 19:51:24 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA15952
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 19:51:24 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2T0KX702053
	for seamoby-list; Wed, 28 Mar 2001 16:20:33 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2T0KCF02046
	for <seamoby@cdma-2000.org>; Wed, 28 Mar 2001 16:20:12 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA18206
	for <seamoby@cdma-2000.org>; Wed, 28 Mar 2001 15:29:24 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA08294
	for <seamoby@cdma-2000.org>; Wed, 28 Mar 2001 15:29:23 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id PAA09317;
	Wed, 28 Mar 2001 15:29:22 -0800 (PST)
Message-Id: <200103282329.PAA09317@heliopolis.Eng.Sun.COM>
Date: Wed, 28 Mar 2001 15:29:22 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: Re: [seamoby] To page, or not to page
To: seamoby@cdma-2000.org, pcalhoun@nasnfs.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: VrzMbJl/gfGsJssIfbdlcg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Pat,

My interpretation of the traffic on the list regarding paging is the following:

1) Some people haven't read the problem statement and therefore don't
have an understanding of what led the design team to conclude that
support for L3 paging was desirable and even necessary in the multitechnology
case.

2) There is a disagreement with the working group concensus expressed at IETF 50
that the design team should not require L2 paging. This seems to
break down into the following areas:

	a) Some people seem to feel that it is simply not possible to
	define an L3 paging protocol without L2 support, and want the
	requirements to reflect that.
	
	b) Some people want to make sure that saying that L2 is not
	required does not rule out using L2 support when you have it
	and want the requirements to reflect that.
	
	c) Some people would like to define an L3 paging protocol completely
	independent of L2, and therefore say nothing about L2 in the
	requirements or in the design.
	
Did I miss anything?

		jak
		

>X-Authentication-Warning: charizard.diameter.org: majordomo set sender to 
owner-seamoby@diameter.org using -f
>Date: Wed, 28 Mar 2001 15:07:23 -0800 (PST)
>From: Patrice Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
>Subject: [seamoby] To page, or not to page
>To: seamoby@cdma-2000.org
>MIME-Version: 1.0
>
>All,
>
>At the IETF meeting, there were some agreements on wether paging is a useful
>Layer 3 function. There seemed to be some concensus that it was, however I am
>now seeing quite a bit of controversy, even though the problem statement has
>passed last call (yes, last call expired on March 12th). The document is about
>to go to IESG for IETF last call and publication.
>
>So I am now confused that there seems to be so much going on in this area, now
>that the time is past. Could someone enlighten me? (btw, please do not bother
>responding if you haven't read the I-D).
>
>Thanks,
>
>PatC
>



From owner-seamoby@diameter.org  Wed Mar 28 20:02:53 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA16126
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 20:02:52 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2T0OFB02066
	for seamoby-list; Wed, 28 Mar 2001 16:24:15 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from atlsnmx1.nextel.com (atlsnmx1.nextel.com [167.20.198.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2T0OBF02061
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 16:24:12 -0800
Received: from atlntgw02.nextel.com (atlntgw02.nextel.com [10.8.79.186])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id SAA29208;
	Wed, 28 Mar 2001 18:33:20 -0500 (EST)
Received: by atlntgw02.nextel.com with Internet Mail Service (5.5.2650.21)
	id <HKW3TNXR>; Wed, 28 Mar 2001 18:33:21 -0500
Message-ID: <020A5EC56F3FD411B5230008C716D085868546@nhqntex01.nextel.com>
From: "Martin, David P" <David.P.Martin@nextel.com>
To: "'Michael Thomas'" <mat@cisco.com>,
        "Martin, David P"
	 <David.P.Martin@nextel.com>
Cc: "'David R. Oran'" <oran@cisco.com>, seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
Date: Wed, 28 Mar 2001 18:27:58 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

I am trying to understand the scope of the first recommended charter item in
the problem statement (I should have made that clear earlier in this
thread).  It states ...

      1) Since the design group has identified several network
      deployment scenerios where existing Mobile IP technology cannot
      find a mobile in dormant mode, protocol work is necessary to
      define a way for the network to find a mobile that is currently in
      dormant mode.

I'm trying to understand which non-reachability problems we will attempt to
address.  If the only problem we are trying to solve is reaching a dormant
mode, I am in full agreement with the problem statement.  

However, if we want a protocol that we deal with *all* non-reachability
issues (link failures, mobile left town, battery died, etc) then I think
that is two distinct problems.  One problem is which interface(s) to deliver
packets to, the other problem is what to do if the mobile doesn't respond in
a timely fashion.

The problem of which interface to deliver packets is the problem that has to
be solved regardless, and I a fully agree that should be part of the
charter.

The second problem of what to do if the mobile is not reachable is a
separate issue.  I feel that it probably *is* a worthwhile problem to solve.
However, the reachability issue is usually dealt with at a lower layers and
(if the lower layer solutions can be any guide) the appropriate solution
will be dependent upon a host of factors.  Which may lead to this particular
problem requiring the vast majority of the effort of the group.

If we want to include the general case of non-reachability in the WG scope,
my recommendation would be to at least update the problem statement to
reflect the two different problems.

A later step would be to see if it makes sense to develop one protocol
solving both issues, or two protocols each solving the respective problem.


> 
> I hate to keep harping on this, but this sure
> seems to me to be familar ground. The problems you
> point out also would come up with a demand dialer
> type of interface, like say an ISDN line which
> isn't up all of the time. While the solutions may
> not be entirely algorithmic, the parameters are
> certainly well understood by now.
> 
The solutions for this problem to date have been optimized for particular
applications that were likely to be running (i.e. phone calls).  Different
applications would have different optimizations.  If its any consolation, I
have been convinced that it would be possible to solve this problem on an
application by application basis ... but I still think a good solution will
take a lot of work.



From owner-seamoby@diameter.org  Wed Mar 28 20:20:13 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA16320
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 20:20:13 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SNxaP01987
	for seamoby-list; Wed, 28 Mar 2001 15:59:36 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SNwHF01982
	for <seamoby@cdma-2000.org>; Wed, 28 Mar 2001 15:58:17 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA01657
	for <seamoby@cdma-2000.org>; Wed, 28 Mar 2001 15:07:28 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA17158
	for <seamoby@cdma-2000.org>; Wed, 28 Mar 2001 15:07:28 -0800 (PST)
Received: from darius (darius [10.6.84.105])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id PAA05163
	for <seamoby@cdma-2000.org>; Wed, 28 Mar 2001 15:07:25 -0800 (PST)
Date: Wed, 28 Mar 2001 15:07:23 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] To page, or not to page
To: seamoby@cdma-2000.org
Message-ID: <Roam.SIMC.2.0.6.985820843.17053.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

All,

At the IETF meeting, there were some agreements on wether paging is a useful
Layer 3 function. There seemed to be some concensus that it was, however I am
now seeing quite a bit of controversy, even though the problem statement has
passed last call (yes, last call expired on March 12th). The document is about
to go to IESG for IETF last call and publication.

So I am now confused that there seems to be so much going on in this area, now
that the time is past. Could someone enlighten me? (btw, please do not bother
responding if you haven't read the I-D).

Thanks,

PatC



From owner-seamoby@diameter.org  Wed Mar 28 20:28:08 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA16475
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 20:28:07 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2SNYFY01935
	for seamoby-list; Wed, 28 Mar 2001 15:34:15 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2SNWuF01930
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 15:32:56 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id OAA01266
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 14:42:03 -0800 (PST)
X-Delivered-For: <seamoby@diameter.org>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f2SMg0A11819
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 14:42:00 -0800
X-mProtect:  Wed, 28 Mar 2001 14:42:00 -0800 Nokia Silicon Valley Messaging Protection
Received: from tpagtzis.iprg.nokia.com (205.226.2.115, claiming to be "cs.ucl.ac.uk")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdMjXtG3; Wed, 28 Mar 2001 14:41:21 PST
Message-ID: <3AC26893.C5D2AE77@cs.ucl.ac.uk>
Date: Wed, 28 Mar 2001 14:41:23 -0800
From: Theo Pagtzis <t.pagtzis@cs.ucl.ac.uk>
Reply-To: tpagtzis@iprg.nokia.com
Organization: UCL/NOKIA
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1-STABLE i386)
X-Accept-Language: el, en
MIME-Version: 1.0
To: seamoby@diameter.org
Subject: Re: [seamoby] what stimulates a page?
References: <200103281711.JAA29684@heliopolis.Eng.Sun.COM> <3AC23A1C.4C3C87E8@lucent.com> <15042.15911.963421.823296@thomasm-u1.cisco.com> <3AC246BE.A209494C@lucent.com> <15042.19245.828315.338037@thomasm-u1.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Mike

   In the case of spurious packets/ or spurious paging packets, why couldn't
there be a one time nonce,
  generated by the MN  and effected at the domain during registration   (one
time per realm/zone/domain registration)
that is encrypted in the page message when effected by the network.

Any message that does not have the correct nonce is discarded

Incoming signalling packets should be marked for no charging. There must be
some distinctive for signalling as opposed to data.
So the some packet market at the edge router should do that.
Or even set a packet classifier to do the check on behalf of the MN so that
the packet is set into a no-go queue (penalised) if the nonce does not come
clean


The nonce is made available by the MN only for specific connection requests
(chargeable accurately)

I don't think that signalling packets should be chargeable...but probably a
fixed cost of the service. Data packet should be chargeable...

If it happens that you move too often so you upset you signalling load curve
profile...just  ensure that the packt classifier penalizes your flows to
compensate for the extra operational charges
(somewhat proportional fairness.... that is a measure of mobility.... :)

Theo


UCL/ Mobile Systems


Michael Thomas wrote:

> [I wanted to break out this out because there are
>  some important requirements you've touched on]
>
> Erik Anderlind writes:
>  > Any paging brings out the security issue of who may use it. Simple
>  > approaches
>  > are to use e.g. firewalls to filter all but certain source addresses.
>  > Anything
>  > beyond that we probably need to look at security mechnisms. (Use one
>  > of the available security mechanisms - don't design a new one.) Except
>  > for
>  > 802.11, most wireless networks charge per minute or per packet for
>  > access - it wouldn't
>  > be acceptable if anyone could run down a user's account by sending
>  > spurious
>  > packets that result in pages.
>
>    Yes, indeed. In fact there is fairly trivial
>    DoS attack to drain somebody's battery or wallet
>    just by sending a slow trickle of IP packets to
>    the mobile node. To some extent these may be
>    unavoidable for a determined attacker, but it
>    seems to me that a useful requirement for paging
>    is that the mobile be able to set up access control
>    lists at some inside router -- I think it must be at
>    the access router -- to prevent spurious or malicious
>    packets to cause the mobile node to wake and possibly
>    bring up a traffic channel.
>
>    I'm conflicted how this should be announced by the
>    mobile node to the AR and/or Pager. My gut level
>    feeling is that this really ought to be dealt
>    with by BURP, as in we feed our requirements to
>    them for paging, but not try to solve this part
>    of the problem in isolation.
>
>           Mike



From owner-seamoby@diameter.org  Wed Mar 28 21:22:16 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA17738
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 21:22:15 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2T1s7C02277
	for seamoby-list; Wed, 28 Mar 2001 17:54:08 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2T1s2F02272
	for <seamoby@cdma-2000.org>; Wed, 28 Mar 2001 17:54:02 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA23832
	for <seamoby@cdma-2000.org>; Wed, 28 Mar 2001 17:03:14 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA28082
	for <seamoby@cdma-2000.org>; Wed, 28 Mar 2001 17:03:13 -0800 (PST)
Received: from darius (darius [10.6.84.105])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id RAA06982;
	Wed, 28 Mar 2001 17:03:08 -0800 (PST)
Date: Wed, 28 Mar 2001 17:03:02 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: Re: [seamoby] To page, or not to page
To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Cc: seamoby@cdma-2000.org, pcalhoun@nasnfs.eng.sun.com
In-Reply-To: "Your message with ID" <200103282329.PAA09317@heliopolis.Eng.Sun.COM>
Message-ID: <Roam.SIMC.2.0.6.985827782.18011.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

> My interpretation of the traffic on the list regarding paging is the
> following:
> 
> 1) Some people haven't read the problem statement and therefore don't
> have an understanding of what led the design team to conclude that
> support for L3 paging was desirable and even necessary in the multitechnology
> case.

ok. So I will not attempt to gauge concensus from people that haven't bothered
to read the draft.

> 
> 2) There is a disagreement with the working group concensus expressed at
> IETF 50 that the design team should not require L2 paging.

which is ok because we need to gauge concensus on the list, regardless of what
happened at the meeting.

> This seems to
> break down into the following areas:
> 
> 	a) Some people seem to feel that it is simply not possible to
> 	define an L3 paging protocol without L2 support, and want the
> 	requirements to reflect that.
> 	
> 	b) Some people want to make sure that saying that L2 is not
> 	required does not rule out using L2 support when you have it
> 	and want the requirements to reflect that.
> 	
> 	c) Some people would like to define an L3 paging protocol completely
> 	independent of L2, and therefore say nothing about L2 in the
> 	requirements or in the design.

ok. Can we agree that these issues can be addressed during the requirements
phase?

PatC



From owner-seamoby@diameter.org  Wed Mar 28 22:12:20 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA20938
	for <seamoby-archive@odin.ietf.org>; Wed, 28 Mar 2001 22:12:19 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2T2eCw02386
	for seamoby-list; Wed, 28 Mar 2001 18:40:12 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2T2e7F02379
	for <seamoby@cdma-2000.org>; Wed, 28 Mar 2001 18:40:07 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4S5N6>; Wed, 28 Mar 2001 20:49:14 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2AA6@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>, seamoby@cdma-2000.org,
        pcalhoun@nasnfs.eng.sun.com
Subject: RE: [seamoby] To page, or not to page
Date: Wed, 28 Mar 2001 20:49:14 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
> Sent: Wednesday, March 28, 2001 6:29 PM
> To: seamoby@cdma-2000.org; pcalhoun@nasnfs.eng.sun.com
> Subject: Re: [seamoby] To page, or not to page
> 
> 
> Pat,
> 
> My interpretation of the traffic on the list regarding paging 
> is the following:
> 
> 1) Some people haven't read the problem statement and therefore don't
> have an understanding of what led the design team to conclude that
> support for L3 paging was desirable and even necessary in the 
> multitechnology
> case.
> 
> 2) There is a disagreement with the working group concensus 
> expressed at IETF 50
> that the design team should not require L2 paging. This seems to
> break down into the following areas:
> 
> 	a) Some people seem to feel that it is simply not possible to
> 	define an L3 paging protocol without L2 support, and want the
> 	requirements to reflect that.

How does a Paging Area differ from an IP Multicast Group?
For Paging optimized technologies would IP Multicast not suffice?

- Kulwinder.

> 	
> 	b) Some people want to make sure that saying that L2 is not
> 	required does not rule out using L2 support when you have it
> 	and want the requirements to reflect that.
> 	
> 	c) Some people would like to define an L3 paging 
> protocol completely
> 	independent of L2, and therefore say nothing about L2 in the
> 	requirements or in the design.
> 	
> Did I miss anything?
> 
> 		jak
> 		
> 
> >X-Authentication-Warning: charizard.diameter.org: majordomo 
> set sender to 
> owner-seamoby@diameter.org using -f
> >Date: Wed, 28 Mar 2001 15:07:23 -0800 (PST)
> >From: Patrice Calhoun <pcalhoun@nasnfs.Eng.Sun.COM>
> >Subject: [seamoby] To page, or not to page
> >To: seamoby@cdma-2000.org
> >MIME-Version: 1.0
> >
> >All,
> >
> >At the IETF meeting, there were some agreements on wether 
> paging is a useful
> >Layer 3 function. There seemed to be some concensus that it 
> was, however I am
> >now seeing quite a bit of controversy, even though the 
> problem statement has
> >passed last call (yes, last call expired on March 12th). The 
> document is about
> >to go to IESG for IETF last call and publication.
> >
> >So I am now confused that there seems to be so much going on 
> in this area, now
> >that the time is past. Could someone enlighten me? (btw, 
> please do not bother
> >responding if you haven't read the I-D).
> >
> >Thanks,
> >
> >PatC
> >
> 


From owner-seamoby@diameter.org  Thu Mar 29 13:24:36 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00272
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 13:24:36 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TI5EQ04667
	for seamoby-list; Thu, 29 Mar 2001 10:05:14 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from atlsnmx1.nextel.com (atlsnmx1.nextel.com [167.20.198.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TI5AF04662
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 10:05:10 -0800
Received: from atlntgw01.nextel.com (atlntgw01.nextel.com [10.8.79.187])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id IAA25508;
	Thu, 29 Mar 2001 08:24:44 -0500 (EST)
Received: by atlntgw01.nextel.com with Internet Mail Service (5.5.2650.21)
	id <HKW325VV>; Thu, 29 Mar 2001 08:25:02 -0500
Message-ID: <020A5EC56F3FD411B5230008C716D08586854A@nhqntex01.nextel.com>
From: "Martin, David P" <David.P.Martin@nextel.com>
To: "'Patrice Calhoun'" <pcalhoun@nasnfs.eng.sun.com>, seamoby@cdma-2000.org
Subject: RE: [seamoby] To page, or not to page
Date: Thu, 29 Mar 2001 08:19:53 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Before the Minneapolis meeting I was in agreement with the problem
statement, however some statements were made at the meeting that concerned
me (if you trace back the thread I started you will see my original post
occurred just after the meeting in Minneapolis).

I interpreted the problem statement to mean that our charter would be to
utilize paging if it existed in layer 2, and if not, that a best-effort IP
paging type of protocol would be developed to try and deliver packets for
those cases where paging was not supported at layer 2.  What I heard at the
meeting and later is that there is a strong desire to build a layer 3
protocol that incorporates substantial layer 2 functionality.  I am not
against this, I just want clarity on the scope of the problem that we are
going to solve.  If as a group we feel that we want to take on all or a
majority of layer 2 functionality (because no assumptions are being made
about what exists at layer 2), I would like to see this as a seperate effort
(at least initially) than the case where we can (or do) make assumptions
about layer 2.  Maybe the effort becomes the same protocol, but then again
there may be good reasons to have two different (but complimentary,
non-overlapping protocols).  I don't know what the best solution is, but I
feel it is premature to assume that one protocol may be the answer, which
was where the discussion in Minneapolis, and some of the discussion on the
list seemed to lead.

Again, my concerns arise because my interpretation of the problem statement
differed from others, perhaps I am the only one, if so I apologize for not
catching on to the subtleties until now.




> -----Original Message-----
> From: Patrice Calhoun [mailto:pcalhoun@nasnfs.eng.sun.com]
> Sent: Wednesday, March 28, 2001 6:07 PM
> To: seamoby@cdma-2000.org
> Subject: [seamoby] To page, or not to page
> 
> 
> All,
> 
> At the IETF meeting, there were some agreements on wether 
> paging is a useful
> Layer 3 function. There seemed to be some concensus that it 
> was, however I am
> now seeing quite a bit of controversy, even though the 
> problem statement has
> passed last call (yes, last call expired on March 12th). The 
> document is about
> to go to IESG for IETF last call and publication.
> 
> So I am now confused that there seems to be so much going on 
> in this area, now
> that the time is past. Could someone enlighten me? (btw, 
> please do not bother
> responding if you haven't read the I-D).
> 
> Thanks,
> 
> PatC
> 


From owner-seamoby@diameter.org  Thu Mar 29 13:27:26 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00419
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 13:27:26 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2THieM04598
	for seamoby-list; Thu, 29 Mar 2001 09:44:40 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2THiDF04593
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 09:44:14 -0800
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f2TEQPI25089
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 16:29:05 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Thu Mar 29 16:26:25 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <G9WJB665>; Thu, 29 Mar 2001 16:26:25 +0200
Message-ID: <A943FD84BD9ED41193460008C7918050017AF968@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'rajeev.koodli@nokia.com'" <rajeev.koodli@nokia.com>,
        micke@CS.Arizona.EDU, mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se,
        seamoby@cdma-2000.org
Subject: [seamoby] RE: [rohc] Compression startup behavior
Date: Thu, 29 Mar 2001 16:26:23 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Some comments below...


> >    The small number I picked, three, will be different for different
> >    implementations but is not completely unrealistic. 
>                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> In other words, 3 is the best case with rather low 
> probability of being
> feasible in practice  ?

No, the best case would be 1, while 3 probably would be a good candidate for realistic conditions and VERY FEASIBLE IN PRACTICE. If the systems are providing acceptable service quality, higher numbers should not be needed. 


 
> Exactly the same point again: How does the compressor know that the IR
> packets it transmitted definitively or almost certainly 
> established the Full
> Context at the decompressor ? 
> 
> I guess it is possible. I can also imagine when it is also 
> *not* possible,
> especially when you are operating under high error links such 
> as those found
> in cellular. 

We are talking about consecutive losses, and for such losses 3 is a high number. Further, the compressor does not need to know. It can be optimistic, as ROHC states. There is a trade-off between efficiency and robustness, and with a sufficiently high number (3 could be that number), optimal efficiency can be achieved without affecting the performance experienced by users.

We could probably argue about this for months (see ROHC mailing list from April 2000), so I will try not to continue this discussion. I guess that context transfer is a mechanism that will be developed and some people will think it is usable while others will not. That is something we must accept...


Rgds,
/L-E


From owner-seamoby@diameter.org  Thu Mar 29 13:46:19 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA02273
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 13:46:19 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TIQ2P04742
	for seamoby-list; Thu, 29 Mar 2001 10:26:02 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TIPwF04737
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 10:25:58 -0800
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2THZEg25216
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 11:35:14 -0600 (CST)
Received: from daebh01nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T529695461eac12f257079@davir04nok.americas.nokia.com>;
 Thu, 29 Mar 2001 11:34:43 -0600
Received: by daebh01nok with Internet Mail Service (5.5.2652.78)
	id <GKQMHDDJ>; Thu, 29 Mar 2001 11:34:43 -0600
Message-ID: <8572CF1E2A95D211A1190008C7EAA2460213BB72@daeis05nok>
From: zhigang.liu@nokia.com
To: Lars-Erik.Jonsson@epl.ericsson.se, rajeev.koodli@nokia.com,
        micke@CS.Arizona.EDU, mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se,
        seamoby@cdma-2000.org
Subject: [seamoby] RE: [rohc] Compression startup behavior
Date: Thu, 29 Mar 2001 11:34:41 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

> No, the best case would be 1, 

... if there are no transmission errors and the compressor knows
this.

> while 3 probably would be a 
> good candidate for realistic conditions and VERY FEASIBLE IN 
> PRACTICE. If the systems are providing acceptable service 
> quality, higher numbers should not be needed. 

3 may or may not work. It depends. In cellular, "acceptable 
service quality" means different thing at different time and 
location (of the mobile node). When you are driving in your car 
in a traffic jam at 5pm, a higher packet loss rate is acceptable 
(to the operator, not you). The very reason that a handover
occurs is due to poor radio conditions at the edge of a cell,
which means you are also at the edge of the new cell after
handover, which means the condition of the new channel probably
will not be very good either. Those factors have to be 
considered.

> We could probably argue about this for months (see ROHC 
> mailing list from April 2000), so I will try not to continue 
> this discussion. 

Oops, I just did. 

> I guess that context transfer is a mechanism 
> that will be developed (snip)

Good, at least we agree on one thing.

Br,
Zhigang
 
 
> Rgds,
> /L-E
> ---
> Mailing list for Robust Header Compression WG
> Archive: http://www.cdt.luth.se/rohc/
> 


From owner-seamoby@diameter.org  Thu Mar 29 13:58:08 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03539
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 13:58:08 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TI7Zb04687
	for seamoby-list; Thu, 29 Mar 2001 10:07:35 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from atlsnmx1.nextel.com (atlsnmx1.nextel.com [167.20.198.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TI7UF04682
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 10:07:31 -0800
Received: from atlntgw02.nextel.com (atlntgw02.nextel.com [10.8.79.186])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id IAA27217;
	Thu, 29 Mar 2001 08:29:04 -0500 (EST)
Received: by atlntgw02.nextel.com with Internet Mail Service (5.5.2650.21)
	id <HKW3TW42>; Thu, 29 Mar 2001 08:29:36 -0500
Message-ID: <020A5EC56F3FD411B5230008C716D08586854B@nhqntex01.nextel.com>
From: "Martin, David P" <David.P.Martin@nextel.com>
To: "'Patrice Calhoun'" <pcalhoun@nasnfs.eng.sun.com>,
        James Kempf
	 <kempf@heliopolis.Eng.Sun.COM>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] To page, or not to page
Date: Thu, 29 Mar 2001 08:24:14 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

> > This seems to
> > break down into the following areas:
> > 
> > 	a) Some people seem to feel that it is simply not possible to
> > 	define an L3 paging protocol without L2 support, and want the
> > 	requirements to reflect that.
> > 	
> > 	b) Some people want to make sure that saying that L2 is not
> > 	required does not rule out using L2 support when you have it
> > 	and want the requirements to reflect that.
> > 	
> > 	c) Some people would like to define an L3 paging 
> protocol completely
> > 	independent of L2, and therefore say nothing about L2 in the
> > 	requirements or in the design.
> 
> ok. Can we agree that these issues can be addressed during 
> the requirements
> phase?
> 

I essentially agree with all the above statements, and agree that these can
be done during the requirments phase.

However, I do have clarifying question on c) - When we say nothing about
layer 2, does this mean that we will 1) Not deal with layer 2 issues, or 2)
Attempt to solve layer 2 issues in the protocol.


From owner-seamoby@diameter.org  Thu Mar 29 14:01:14 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA03858
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 14:01:14 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2T3idh02538
	for seamoby-list; Wed, 28 Mar 2001 19:44:39 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2T3iYF02533
	for <seamoby@diameter.org>; Wed, 28 Mar 2001 19:44:34 -0800
Received: from tari.research.telcordia.com (tari [207.3.232.66])
	by thumper.research.telcordia.com (8.10.1/8.10.1) with ESMTP id f2T2rQO27835;
	Wed, 28 Mar 2001 21:53:28 -0500 (EST)
Received: from tuna.research.telcordia.com (ohba@tari-dhcp11.research.telcordia.com [207.3.232.125])
	by tari.research.telcordia.com (8.8.8/8.8.8) with ESMTP id VAA15037;
	Wed, 28 Mar 2001 21:54:54 -0500 (EST)
Date: Wed, 28 Mar 2001 21:56:41 -0500
Message-ID: <87n1a5nuza.wl@research.telcordia.com>
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: mat@cisco.com
Cc: eanderlind@lucent.com, seamoby@diameter.org
Subject: Re: [seamoby] what stimulates a page?
In-Reply-To: In your message of "Wed, 28 Mar 2001 12:35:57 -0800 (PST)"
	<15042.19245.828315.338037@thomasm-u1.cisco.com>
References: <200103281711.JAA29684@heliopolis.Eng.Sun.COM>
	<3AC23A1C.4C3C87E8@lucent.com>
	<15042.15911.963421.823296@thomasm-u1.cisco.com>
	<3AC246BE.A209494C@lucent.com>
	<15042.19245.828315.338037@thomasm-u1.cisco.com>
User-Agent: Wanderlust/2.2.15 (More Than Words) WEMI/1.13.7 (Shimada) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386-debian-linux)
MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi,

At Wed, 28 Mar 2001 12:35:57 -0800 (PST),
Michael Thomas <mat@cisco.com> wrote:
> 
> 
> [I wanted to break out this out because there are
>  some important requirements you've touched on]
> 
> Erik Anderlind writes:
>  > Any paging brings out the security issue of who may use it. Simple
>  > approaches
>  > are to use e.g. firewalls to filter all but certain source addresses.
>  > Anything
>  > beyond that we probably need to look at security mechnisms. (Use one 
>  > of the available security mechanisms - don't design a new one.) Except
>  > for
>  > 802.11, most wireless networks charge per minute or per packet for
>  > access - it wouldn't
>  > be acceptable if anyone could run down a user's account by sending
>  > spurious
>  > packets that result in pages.
> 
>    Yes, indeed. In fact there is fairly trivial
>    DoS attack to drain somebody's battery or wallet
>    just by sending a slow trickle of IP packets to
>    the mobile node. To some extent these may be
>    unavoidable for a determined attacker, but it
>    seems to me that a useful requirement for paging
>    is that the mobile be able to set up access control
>    lists at some inside router -- I think it must be at
>    the access router -- to prevent spurious or malicious
>    packets to cause the mobile node to wake and possibly
>    bring up a traffic channel.
> 
>    I'm conflicted how this should be announced by the
>    mobile node to the AR and/or Pager. My gut level
>    feeling is that this really ought to be dealt
>    with by BURP, as in we feed our requirements to
>    them for paging, but not try to solve this part 
>    of the problem in isolation.
> 

It may be possible to use BURP for such purpose if the attacker and
mobile node are not in the same subnet.  On the other hand, attacks
from the same subnet may be more likely for network access in public
area, but I'm not sure how BURP could be used in that case.

Regards,
Yoshihiro Ohba


> 	  Mike
> 


From owner-seamoby@diameter.org  Thu Mar 29 14:15:25 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA04998
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 14:15:25 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TIvfx04832
	for seamoby-list; Thu, 29 Mar 2001 10:57:41 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TIvZF04827
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 10:57:36 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA29069;
	Thu, 29 Mar 2001 08:05:32 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA06760;
	Thu, 29 Mar 2001 08:05:32 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id IAA22329;
	Thu, 29 Mar 2001 08:05:31 -0800 (PST)
Message-Id: <200103291605.IAA22329@heliopolis.Eng.Sun.COM>
Date: Thu, 29 Mar 2001 08:05:31 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] To page, or not to page
To: kempf@heliopolis.Eng.Sun.COM, seamoby@cdma-2000.org,
        pcalhoun@nasnfs.eng.sun.com, kulwinder.atwal@zucotto.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: yglrBdYtwIax5qhoZ2iHuw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Kulwinder,


>How does a Paging Area differ from an IP Multicast Group?
>For Paging optimized technologies would IP Multicast not suffice?
>

That's a possible implementation, not a requirement. We are currently in
the requirements/architecture phase.

		jak



From owner-seamoby@diameter.org  Thu Mar 29 14:23:30 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA05346
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 14:23:29 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TIRkk04751
	for seamoby-list; Thu, 29 Mar 2001 10:27:46 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from smtprch2.nortel.com (smtprch2.nortelnetworks.com [192.135.215.15])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TIRgF04746
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 10:27:42 -0800
Received: from zrchb200.us.nortel.com by smtprch2.nortel.com;
          Thu, 29 Mar 2001 11:23:52 -0600
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <H6KSXXSQ>; Thu, 29 Mar 2001 11:29:01 -0600
Message-ID: <85AA7486A2C1D411BCA20000F8073E4301B282F2@crchy271.us.nortel.com>
From: "Glenn Morrow" <gmorrow@nortelnetworks.com>
To: Erik Anderlind <eanderlind@lucent.com>, seamoby@diameter.org
Subject: RE: Paging Functional Architecture ( was: RE: [seamoby] L2/L3 Pag ing)
Date: Thu, 29 Mar 2001 11:28:58 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0B875.BCEAC200"
X-Orig: <gmorrow@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0B875.BCEAC200
Content-Type: text/plain;
	charset="iso-8859-1"

Erik,

Comments below.

-----Original Message-----
From: Erik Anderlind [mailto:eanderlind@lucent.com]
Sent: Wednesday, March 28, 2001 1:23 PM
To: seamoby@diameter.org
Subject: Re: Paging Functional Architecture ( was: RE: [seamoby] L2/L3
Paging)


Glenn,
We need to be careful in defining functional entities such as the paging
and 
tracking agent - we do not want to preclude that these functions could
be 
provided in a distributed way (e.g. a subset of routers all implement
the function.)

GM] Yes to some extent - if we ever want to get rid of single point of
failure and true mobile routing within specific sites this is immanent. 

I also disagree that it is a requirement that the paging agent has to be
at 
the "last hop" edge in all cases.

GM] Sounds more like a good suggestion than a disagreement really. Seems to
me that some technologies which are considered MAC/LAC etc.. are beginning
to use IP transports - makes sense. The blur between L2/L3 is dependent on
what the L2 in question can do. This is mainly due to the fact some some
L1/L2s do more than others. I'm not sure what the reaction will be on this,
though. It seems that the mobies want to go all the way here. Tell me your
opinion on this question. If the IETF defines IP-based PDUs that essentially
implements, in some generic access independent manner, the power control
mechanisms such as paging that used to be considered L2 functions on
particular access technologies, will they have simply defined a new L2 or
will they have built some generic form of these functions into IP(L3)? This
has been racking my brain a bit over the years. It seems to me that even
wireline NIC cards might benefit from such power control mechanisms -
especially in blackout land. I do agree personally that there should be an
option to remote the paging agent. I think some will argue that we might be
designing an L2 technology that uses IP transport in that case. I'm
personally O.K. with it and still see the benefits from an L3 mechanisms
point of view - assuming it does not force us into a single point of
failure. 


Another useful entity is correspondent node/application that initiates
the higher level 
need for paging. It will help identify requiremnts around how the other
different 
entities are located and addressed (if needed).
..Erik

GM] It would be good to explain that paging is a geographic node mobility
problem and explain the interactions with: applications which provide user
mobility, location services, network resolution services, etc.. How the
addressing of user differs from nodes, etc.. I think that is what you were
trying to say. I think we might hear from some "scope" police on this,
though.  Clearly, somewhere this information should be documented in at
least an informational RFC. Perhaps the "why" questions should be answered
in such a document as well. If I have misinterpreted, please let me know.

Thanks,

Glenn


------_=_NextPart_001_01C0B875.BCEAC200
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>RE: Paging Functional Architecture ( was: RE: [seamoby] L2/L3 =
Paging)</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Erik,</FONT>
</P>

<P><FONT SIZE=3D2>Comments below.</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Erik Anderlind [<A =
HREF=3D"mailto:eanderlind@lucent.com">mailto:eanderlind@lucent.com</A>]<=
/FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, March 28, 2001 1:23 PM</FONT>
<BR><FONT SIZE=3D2>To: seamoby@diameter.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: Paging Functional Architecture ( was: =
RE: [seamoby] L2/L3</FONT>
<BR><FONT SIZE=3D2>Paging)</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Glenn,</FONT>
<BR><FONT SIZE=3D2>We need to be careful in defining functional =
entities such as the paging</FONT>
<BR><FONT SIZE=3D2>and </FONT>
<BR><FONT SIZE=3D2>tracking agent - we do not want to preclude that =
these functions could</FONT>
<BR><FONT SIZE=3D2>be </FONT>
<BR><FONT SIZE=3D2>provided in a distributed way (e.g. a subset of =
routers all implement</FONT>
<BR><FONT SIZE=3D2>the function.)</FONT>
</P>

<P><FONT SIZE=3D2>GM] Yes to some extent - if we ever want to get rid =
of single point of failure and true mobile routing within specific =
sites this is immanent. </FONT></P>

<P><FONT SIZE=3D2>I also disagree that it is a requirement that the =
paging agent has to be</FONT>
<BR><FONT SIZE=3D2>at </FONT>
<BR><FONT SIZE=3D2>the &quot;last hop&quot; edge in all cases.</FONT>
</P>

<P><FONT SIZE=3D2>GM] Sounds more like a good suggestion than a =
disagreement really. Seems to me that some technologies which are =
considered MAC/LAC etc.. are beginning to use IP transports - makes =
sense. The blur between L2/L3 is dependent on what the L2 in question =
can do. This is mainly due to the fact some some L1/L2s do more than =
others. I'm not sure what the reaction will be on this, though. It =
seems that the mobies want to go all the way here. Tell me your opinion =
on this question. If the IETF defines IP-based PDUs that essentially =
implements, in some generic access independent manner, the power =
control mechanisms such as paging that used to be considered L2 =
functions on particular access technologies, will they have simply =
defined a new L2 or will they have built some generic form of these =
functions into IP(L3)? This has been racking my brain a bit over the =
years. It seems to me that even wireline NIC cards might benefit from =
such power control mechanisms - especially in blackout land. I do agree =
personally that there should be an option to remote the paging agent. I =
think some will argue that we might be designing an L2 technology that =
uses IP transport in that case. I'm personally O.K. with it and still =
see the benefits from an L3 mechanisms point of view - assuming it does =
not force us into a single point of failure. </FONT></P>
<BR>

<P><FONT SIZE=3D2>Another useful entity is correspondent =
node/application that initiates</FONT>
<BR><FONT SIZE=3D2>the higher level </FONT>
<BR><FONT SIZE=3D2>need for paging. It will help identify requiremnts =
around how the other</FONT>
<BR><FONT SIZE=3D2>different </FONT>
<BR><FONT SIZE=3D2>entities are located and addressed (if =
needed).</FONT>
<BR><FONT SIZE=3D2>..Erik</FONT>
</P>

<P><FONT SIZE=3D2>GM] It would be good to explain that paging is a =
geographic node mobility problem and explain the interactions with: =
applications which provide user mobility, location services, network =
resolution services, etc.. How the addressing of user differs from =
nodes, etc.. I think that is what you were trying to say. I think we =
might hear from some &quot;scope&quot; police on this, though.&nbsp; =
Clearly, somewhere this information should be documented in at least an =
informational RFC. Perhaps the &quot;why&quot; questions should be =
answered in such a document as well. If I have misinterpreted, please =
let me know.</FONT></P>

<P><FONT SIZE=3D2>Thanks,</FONT>
</P>

<P><FONT SIZE=3D2>Glenn</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0B875.BCEAC200--


From owner-seamoby@diameter.org  Thu Mar 29 14:59:36 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA07347
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 14:59:35 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TIAXK04713
	for seamoby-list; Thu, 29 Mar 2001 10:10:33 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from auemlsrv.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TIATF04708
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 10:10:29 -0800
Received: from auemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id MAA23229
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 12:19:43 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-160-150.lucent.com [135.86.160.150])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id MAA23199
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 12:19:42 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2650.21)
	id <HYP1FRVG>; Thu, 29 Mar 2001 18:19:41 +0100
Message-ID: <976F7C55E3B2D111A0720008C728549C097CC290@en0060exch001u.uk.lucent.com>
From: "Casati, Alessio (Alessio)" <acasati@lucent.com>
To: "'Patrice Calhoun'" <pcalhoun@nasnfs.eng.sun.com>,
        James Kempf
	 <kempf@heliopolis.Eng.Sun.COM>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] To page, or not to page
Date: Thu, 29 Mar 2001 18:19:40 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk

I did bother (yesterday) to read the draft.
So I'm not sure any of my comments might be used to 
gauge consensus.
What bothers me is that people decide that L3
paging is required without saying what it is
(unless I missed something):

Is it based on multicast? is it unicast? These two
options make it a completely different thing

Multicast would more fit what today's L2 paging definition is,
however this would imply that a paging would wake up all the
terminals (not acceptable). 
On the other hand, if it is unicast, the page would be replaced most 
conveniently by user data. the link over which data are received
will tell where to send any agent solicitation... If more than one link,
guess what, pick one you like most. What would be nedeed is only
a location update protocol. A location update protocol is
already available and it is mobile IP (or an extention of it,
if at all needed).

as such, I'd support to take a step back and
re-consider the soundness of the reqs (OK, the IESG may do that instead,
if we want an analogy with what has happened with MIPv6 ;).

Also, maybe what I described now cannot quite be defined as paging
(although I truly believe paging may gain more cookie points,
in a marketing setting).


alessio

-----Original Message-----
From: Patrice Calhoun [mailto:pcalhoun@nasnfs.eng.sun.com]
Sent: 29 March 2001 02:03
To: James Kempf
Cc: seamoby@cdma-2000.org; pcalhoun@nasnfs.eng.sun.com
Subject: Re: [seamoby] To page, or not to page


> My interpretation of the traffic on the list regarding paging is the
> following:
> 
> 1) Some people haven't read the problem statement and therefore don't
> have an understanding of what led the design team to conclude that
> support for L3 paging was desirable and even necessary in the
multitechnology
> case.

ok. So I will not attempt to gauge concensus from people that haven't
bothered
to read the draft.

> 
> 2) There is a disagreement with the working group concensus expressed at
> IETF 50 that the design team should not require L2 paging.

which is ok because we need to gauge concensus on the list, regardless of
what
happened at the meeting.

> This seems to
> break down into the following areas:
> 
> 	a) Some people seem to feel that it is simply not possible to
> 	define an L3 paging protocol without L2 support, and want the
> 	requirements to reflect that.
> 	
> 	b) Some people want to make sure that saying that L2 is not
> 	required does not rule out using L2 support when you have it
> 	and want the requirements to reflect that.
> 	
> 	c) Some people would like to define an L3 paging protocol completely
> 	independent of L2, and therefore say nothing about L2 in the
> 	requirements or in the design.

ok. Can we agree that these issues can be addressed during the requirements
phase?

PatC


From owner-seamoby@diameter.org  Thu Mar 29 15:10:13 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA08082
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 15:10:13 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TJNBc04907
	for seamoby-list; Thu, 29 Mar 2001 11:23:11 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TJN6F04902
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 11:23:07 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Thu, 29 Mar 2001 13:13:15 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <HSTBXLM7>; Thu, 29 Mar 2001 13:13:16 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8E80@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'seamoby'" <seamoby@diameter.org>
Cc: "'zhigang.liu@nokia.com'" <zhigang.liu@nokia.com>,
        "'Lars-Erik.Jonsson@epl.ericsson.se'" <Lars-Erik.Jonsson@epl.ericsson.se>,
        "'rajeev.koodli@nokia.com'" <rajeev.koodli@nokia.com>
Subject: RE: [seamoby] RE: [ROHC] Compression startup behaviour
Date: Thu, 29 Mar 2001 13:13:10 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

Having only skimmed the evolution of this thread, I have apparently
lost the train of thought . . . 

What does context transfer have to do with packet losses over the
air? No one is proposing context transfer to or from the mobile. All
context transfer being discussed in this wg is within the wireline
network.

Gary


> -----Original Message-----
> From: zhigang.liu@nokia.com [mailto:zhigang.liu@nokia.com]
> Sent: Thursday, March 29, 2001 12:35 PM
> To: Lars-Erik.Jonsson@epl.ericsson.se; rajeev.koodli@nokia.com;
> micke@CS.Arizona.EDU; mobile-ip@sunroof.eng.sun.com; rohc@cdt.luth.se;
> seamoby@cdma-2000.org
> Subject: [seamoby] RE: [rohc] Compression startup behavior
> 
> 
> > No, the best case would be 1, 
> 
> ... if there are no transmission errors and the compressor knows
> this.
> 
> > while 3 probably would be a 
> > good candidate for realistic conditions and VERY FEASIBLE IN 
> > PRACTICE. If the systems are providing acceptable service 
> > quality, higher numbers should not be needed. 
> 
> 3 may or may not work. It depends. In cellular, "acceptable 
> service quality" means different thing at different time and 
> location (of the mobile node). When you are driving in your car 
> in a traffic jam at 5pm, a higher packet loss rate is acceptable 
> (to the operator, not you). The very reason that a handover
> occurs is due to poor radio conditions at the edge of a cell,
> which means you are also at the edge of the new cell after
> handover, which means the condition of the new channel probably
> will not be very good either. Those factors have to be 
> considered.
> 
> > We could probably argue about this for months (see ROHC 
> > mailing list from April 2000), so I will try not to continue 
> > this discussion. 
> 
> Oops, I just did. 
> 
> > I guess that context transfer is a mechanism 
> > that will be developed (snip)
> 
> Good, at least we agree on one thing.
> 
> Br,
> Zhigang
>  
>  
> > Rgds,
> > /L-E
> > ---
> > Mailing list for Robust Header Compression WG
> > Archive: http://www.cdt.luth.se/rohc/
> > 
> 


From owner-seamoby@diameter.org  Thu Mar 29 15:10:32 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA08102
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 15:10:31 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TI7DE04678
	for seamoby-list; Thu, 29 Mar 2001 10:07:13 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TI79F04673
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 10:07:09 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-3.cisco.com (8.9.3/8.9.1) with ESMTP id JAA19504
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 09:15:02 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADF20686;
	Thu, 29 Mar 2001 07:39:59 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id HAA03672; Thu, 29 Mar 2001 07:39:59 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15043.22351.137265.235463@thomasm-u1.cisco.com>
Date: Thu, 29 Mar 2001 07:39:59 -0800 (PST)
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: mat@cisco.com, eanderlind@lucent.com, seamoby@diameter.org
Subject: Re: [seamoby] what stimulates a page?
In-Reply-To: <87n1a5nuza.wl@research.telcordia.com>
References: <200103281711.JAA29684@heliopolis.Eng.Sun.COM>
	<3AC23A1C.4C3C87E8@lucent.com>
	<15042.15911.963421.823296@thomasm-u1.cisco.com>
	<3AC246BE.A209494C@lucent.com>
	<15042.19245.828315.338037@thomasm-u1.cisco.com>
	<87n1a5nuza.wl@research.telcordia.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Yoshihiro Ohba writes:
 > Michael Thomas <mat@cisco.com> wrote:
 > >    Yes, indeed. In fact there is fairly trivial
 > >    DoS attack to drain somebody's battery or wallet
 > >    just by sending a slow trickle of IP packets to
 > >    the mobile node. To some extent these may be
 > >    unavoidable for a determined attacker, but it
 > >    seems to me that a useful requirement for paging
 > >    is that the mobile be able to set up access control
 > >    lists at some inside router -- I think it must be at
 > >    the access router -- to prevent spurious or malicious
 > >    packets to cause the mobile node to wake and possibly
 > >    bring up a traffic channel.
 > > 
 > >    I'm conflicted how this should be announced by the
 > >    mobile node to the AR and/or Pager. My gut level
 > >    feeling is that this really ought to be dealt
 > >    with by BURP, as in we feed our requirements to
 > >    them for paging, but not try to solve this part 
 > >    of the problem in isolation.
 > > 
 > 
 > It may be possible to use BURP for such purpose if the attacker and
 > mobile node are not in the same subnet.  On the other hand, attacks
 > from the same subnet may be more likely for network access in public
 > area, but I'm not sure how BURP could be used in that case.

   If you have a true bus-like L1, this is correct;
   otherwise, the AP/AR can do filtering regardless
   of whether it's in the same subnet.
   However, I don't know of any wireless L1's that
   actually are buses, nor am I sure that there will
   be any soon given the inherent issues with 
   spectrum efficiency and QoS.

		       Mike
   


From owner-seamoby@diameter.org  Thu Mar 29 15:12:34 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA08216
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 15:12:33 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TJfQS04965
	for seamoby-list; Thu, 29 Mar 2001 11:41:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TJfLF04960
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 11:41:21 -0800
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2TIocg06711
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 12:50:38 -0600 (CST)
Received: from daebh01nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5296da9a8fac12f257079@davir04nok.americas.nokia.com>;
 Thu, 29 Mar 2001 12:50:27 -0600
Received: by daebh01nok with Internet Mail Service (5.5.2652.78)
	id <GKQMH1RG>; Thu, 29 Mar 2001 12:50:26 -0600
Message-ID: <8572CF1E2A95D211A1190008C7EAA2460213BB73@daeis05nok>
From: zhigang.liu@nokia.com
To: Hesham.Soliman@era.ericsson.se
Cc: mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se, seamoby@diameter.org
Subject: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6 Handover
Date: Thu, 29 Mar 2001 12:50:26 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Hesham,

Please see my comments inline.

Br,
Zhigang
 
> Hello Zhiang, 
> 
> So it seems ot me that there is no clear consensus in ROHC
> on context relocation. Is that because the need is not proven ?

To be fair, both sides gave their arguments for and against
HC context relocation. There is nothing proven yet (and so is 
the whole ideal of Wireless Mobile IP). In fact, people in ROHC
WG haven't spent much time debating on this because we didn't
want this debate to delay the delivery of the basic ROHC (we
had a very tight schedule).

Whether it is needed or not is a cost-benefit issue. From my 
point of view, the cost is small and the benefit is large. I
don't see reasons why we should not do it. But I'm willing to 
hear the arguments from the other side.

> I guess we need to know how bad a channel can be. I might 
> be completely wrong here but if we're only talking about 
> a couple of packets to sync the compressor, then context
> relocation seems to be an overkill. However, if the amount 
> of packets sent with full headers is significant, then I can 
> understand the need. 

As I mentioned in my previous email, the issue is not only
the number of IR packets, it's the size of those IR packets.
Even if we are talking about 3 IR packets, the surge of bandwidth
required (e.g. 3*60 bytes vs. 3*5 bytes) is a heavy burden on
the radio links. If the HC context relocation can avoid this with
little cost, I don't see why we shouldn't do that.

(Side note: for hisorical and technical reasons, dealing with 
realtime VBR over radio links is much a headache than over wired 
links. )


> But either way it doesn't seem to be a problem since you 
> said that context relocation (if needed) will solve this. Right ?

I would say the huge (don't laugh at me, it's true) spike in
throughput over the radio link could be a problem. HC context 
relocation avoids it.

> So I don't know why we (MIP WG) should be involved. 
> It seems to be a ROHC/SEAMOBY issue. 

I'm not sure. The start of this thread seems to indicate the
opposite. But, I agree the context relocation is an issue 
dealt with in SEAMOBY (if I understand correctly).

> Regards,
> Hesham
> 
> > -----Original Message-----
> > From:	zhigang.liu@nokia.com [SMTP:zhigang.liu@nokia.com]
> > Sent:	Friday, 30 March 2001 2:53
> > To:	claude.castelluccia@inrialpes.fr; zhigang.liu@nokia.com
> > Cc:	Hesham.Soliman@era.ericsson.se; 
> kempf@heliopolis.Eng.Sun.COM; micke@sm.luth.se; cabo@tzi.org; 
> mobile-ip@sunroof.eng.sun.com; rohc@cdt.luth.se
> > Subject:	RE: [rohc] RE: Restarting Compressor on Mobile 
> IPv6 Handover
> > 
> > Hi Claude,
> > 
> > Context relocation is useful regardless of the loss of 
> packets during 
> > handover as the bulk of the saving (of bytes over the radio 
> links) comes 
> > from the static header fields. For example, the new compressor (for
> > downlink) 
> > can jump start in FO state in stead of going through IR 
> state all over
> > again.
> > 
> > We have been studying HC context relocation since spring 
> 1999 (when we 
> > started ACE). Khiem has proposed text to ROHC list in June 2000 
> > (http://www.cdt.luth.se/robhc/msg00508.html). 
> Unfortunately, that item was 
> > not included in ROHC I-D, partially due to the urgency to 
> finish the basic
> > ROHC scheme (plus objections from some of the ROHC authors). 
> > 
> > Now, it's time we give it a serious look.
> > 
> > Br,
> > Zhigang
> > 
> > -----Original Message-----
> > From: ext Claude Castelluccia 
[mailto:claude.castelluccia@inrialpes.fr]
> Sent: Thursday, March 29, 2001 1:40 AM
> To: zhigang.liu@nokia.com
> Cc: Hesham.Soliman@era.ericsson.se; kempf@heliopolis.Eng.Sun.COM;
> micke@sm.luth.se; cabo@tzi.org; mobile-ip@sunroof.eng.sun.com;
> rohc@cdt.luth.se
> Subject: Re: [rohc] RE: Restarting Compressor on Mobile IPv6 Handover
> 
> 
>   
> Hello Zhigang, 
> I seems from your email that context relocation will be very useful for
> RoHC. 
> Is istalso the case if some packets are lost  when a MN moves from one
base
> station 
> to another one? 
> In this case it is better to restart the context or relocate it? 
> Do you know of any studies on this topic? 
> thanks a lot! 
> Claude. 
> zhigang.liu@nokia.com wrote: 
> Hi, 
>   
>   
> There are some guessing/assumptions behind the number (3-4). 
> I'm not so sure that's always the case. The radio link condition 
> before/after handover is likely be worse than normal condition. 
> That may mean more packets could be lost (in this case, IR packets). 
> That will has impacts on the guessing of the number. 
> Although we're talking about "very few" packets (be it 3-4 or 5-6), 
> they are LARGE (40+ bytes for RTP/UDP/IPv4 headers and 60+ bytes 
> for RTP/UDP/IPv6 headers). And most of the header fields are static. 
> That is the issue. With HC context relocation, there is no need to 
> send the static fields over the air. The reduced overhead means 
> less pain (e.g. delay, possible stealing or blanking of voice payload). 
> Note that smaller packets have lower chance to be hit by transmission 
> errors (even just one bit) and thus lost, assuming no link layer 
> retransmission (which makes sense for real-time multimedia). 
>  
> -- 
> 
> ----------------------------------------
> Claude CASTELLUCCIA, INRIA Rhone-Alpes  
> ph:  +33 4.76.61.52.15 (fax: 52.52)
> http://www.inrialpes.fr/planete/
>   


From owner-seamoby@diameter.org  Thu Mar 29 15:34:32 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA09327
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 15:34:32 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TIxFS04843
	for seamoby-list; Thu, 29 Mar 2001 10:59:15 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TIx9F04838
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 10:59:09 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA12648;
	Thu, 29 Mar 2001 08:21:39 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA09367;
	Thu, 29 Mar 2001 08:21:39 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id IAA22643;
	Thu, 29 Mar 2001 08:21:38 -0800 (PST)
Message-Id: <200103291621.IAA22643@heliopolis.Eng.Sun.COM>
Date: Thu, 29 Mar 2001 08:21:38 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] To page, or not to page
To: pcalhoun@nasnfs.eng.sun.com, kempf@heliopolis.Eng.Sun.COM,
        David.P.Martin@nextel.com
Cc: seamoby@cdma-2000.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 8fFT6J5Nh8N81fnuVQVk+A==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Dave,

>However, I do have clarifying question on c) - When we say nothing about
>layer 2, does this mean that we will 1) Not deal with layer 2 issues, or 2)
>Attempt to solve layer 2 issues in the protocol.

The protocol design should reflect whatever the requirements say, because
the requirements guide the protocol design. So if the requirements
say something about layer 2, then the design should reflect those
requirements, and vice versa.

In any case, I don't think a layer 3 protocol can solve any layer 2 issues.
The best we could do is require layer 2 support be used
when available, and have the protocol structured to reflect that. 
Assuming, of course, concensus is there for using layer 2 support
when available.

		jak



From owner-seamoby@diameter.org  Thu Mar 29 16:55:57 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA13152
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 16:55:56 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TJvBP04998
	for seamoby-list; Thu, 29 Mar 2001 11:57:11 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TJv6F04992
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 11:57:06 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id LAA08717;
	Thu, 29 Mar 2001 11:06:12 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADF25815;
	Thu, 29 Mar 2001 11:06:06 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA03709; Thu, 29 Mar 2001 11:06:06 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15043.34717.849084.517703@thomasm-u1.cisco.com>
Date: Thu, 29 Mar 2001 11:06:05 -0800 (PST)
To: zhigang.liu@nokia.com
Cc: Hesham.Soliman@era.ericsson.se, mobile-ip@sunroof.eng.sun.com,
        rohc@cdt.luth.se, seamoby@diameter.org
Subject: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6 Handover
In-Reply-To: <8572CF1E2A95D211A1190008C7EAA2460213BB73@daeis05nok>
References: <8572CF1E2A95D211A1190008C7EAA2460213BB73@daeis05nok>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

zhigang.liu@nokia.com writes:
 > (Side note: for hisorical and technical reasons, dealing with 
 > realtime VBR over radio links is much a headache than over wired 
 > links. )

   A-ha! That's one of the reasons I question whether
   ROHC is even appropriate on the air except in a
   very small subset of cases (usually long lived streams
   like RTP for which it was originally intended) As
   a general purpose tunnel/header compressor, I suspect it is going
   to have severe thrashing with the way that radio
   resources are doled out by the AP.

	     Mike


From owner-seamoby@diameter.org  Thu Mar 29 17:17:36 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA14098
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 17:17:36 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TLAjr05228
	for seamoby-list; Thu, 29 Mar 2001 13:10:45 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TLAfF05223
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 13:10:41 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA08933;
	Thu, 29 Mar 2001 12:19:51 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA12917;
	Thu, 29 Mar 2001 12:19:47 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id MAA29137;
	Thu, 29 Mar 2001 12:19:46 -0800 (PST)
Message-Id: <200103292019.MAA29137@heliopolis.Eng.Sun.COM>
Date: Thu, 29 Mar 2001 12:19:46 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] To page, or not to page
To: pcalhoun@nasnfs.eng.sun.com, kempf@heliopolis.Eng.Sun.COM,
        acasati@lucent.com
Cc: seamoby@cdma-2000.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 9Yd31/J6AXXGbbKuIYkMcA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Alessio,

>I did bother (yesterday) to read the draft.
>So I'm not sure any of my comments might be used to 
>gauge consensus.
>What bothers me is that people decide that L3
>paging is required without saying what it is
>(unless I missed something):
>

Well, the requirements (which we are currently defining) should
do that.

>Is it based on multicast? is it unicast? These two
>options make it a completely different thing
>
>Multicast would more fit what today's L2 paging definition is,
>however this would imply that a paging would wake up all the
>terminals (not acceptable). 
>On the other hand, if it is unicast, the page would be replaced most 
>conveniently by user data. the link over which data are received
>will tell where to send any agent solicitation... If more than one link,
>guess what, pick one you like most. What would be nedeed is only
>a location update protocol. A location update protocol is
>already available and it is mobile IP (or an extention of it,
>if at all needed).
>

You are talking here about what goes over the air, correct? That is only
one small part of what is needed for paging.

If the L2 paging protocol is used over the air, then all  that is needed
is for a wired backbone protocol to handle location updating when
the mobile goes into dormant mode and crosses paging area boundaries,
and to trigger a page when a packet comes in. As you indicate, it
will need to be integrated with mobile IP, but it should not be
bound exclusively to mobile IP because the IRTF will be working on
a micromobility routing protocol and the wired backbone part may
be useful for that as well. 

And, I think we should also be clear that something in addition to mobile IP as 
it exists today is needed. The way 3GPP2 handles mobile IP location updating for
dormant mode mobiles today is the mobile comes out of dormant mode,
brings up a traffic channel, does a mobile IP registration, and goes
back into dormant mode. This is not very efficient.

Of course, this is all implementation. The requirements that would come
out of this are:

	The IP paging protocol shall be efficient with respect to
	mobile power use.
	
	The IP paging protocol shall be designed to allow a binding
	with mobility protocols for location update purposes, including
	mobile IP.
	
	The IP paging protocol shall utiliize L2 paging support if
	available, but shall not require such support.

>as such, I'd support to take a step back and
>re-consider the soundness of the reqs (OK, the IESG may do that instead,
>if we want an analogy with what has happened with MIPv6 ;).

Actually, Alissio, that is precisely what we are doing. If you have
some requirements you would like to propose, please, by all means,
propose them.

>Also, maybe what I described now cannot quite be defined as paging
>(although I truly believe paging may gain more cookie points,
>in a marketing setting).
>

IS-41 has messages associated with paging and it goes over the SS7 backbone.
So I don't see any problem calling support for paging in the wired
network as paging. Paging isn't only about what goes over the air, IMHO.

		jak



From owner-seamoby@diameter.org  Thu Mar 29 17:19:33 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA14177
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 17:19:33 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TKEP005064
	for seamoby-list; Thu, 29 Mar 2001 12:14:25 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TKEKF05059
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 12:14:20 -0800
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2TJNbg11149
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 13:23:37 -0600 (CST)
Received: from daebh02nok.americas.nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5296f8aa80ac12f255079@davir02nok.americas.nokia.com>;
 Thu, 29 Mar 2001 13:23:17 -0600
Received: by daebh02nok with Internet Mail Service (5.5.2652.78)
	id <GKS5J06K>; Thu, 29 Mar 2001 13:23:17 -0600
Message-ID: <8572CF1E2A95D211A1190008C7EAA2460213BB74@daeis05nok>
From: zhigang.liu@nokia.com
To: gkenward@nortelnetworks.com, seamoby@diameter.org
Cc: Lars-Erik.Jonsson@epl.ericsson.se, rajeev.koodli@nokia.com
Subject: RE: [seamoby] RE: [ROHC] Compression startup behaviour
Date: Thu, 29 Mar 2001 13:23:16 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Gary,

You're right. The discussion is indeed confusing for anyone 
who hasn't followed the ROHC list. In short, the argument on the 
packet losses (more accurately, the consecutive losses)
is about how much is the benefit of HC context relocation,
and thus whether it is needed.

The logic is: without context relocation, an estimate of consecutive
packet losses determines how many IR packets are needed to establish 
the context over the air after handover. With context relocation,
those IR packets can be avoided.

To me, the benefit outweighs the cost (if any).

Br,
Zhigang

-----Original Message-----
From: ext Gary Kenward [mailto:gkenward@nortelnetworks.com]
Sent: Thursday, March 29, 2001 12:13 PM
To: 'seamoby'
Cc: 'zhigang.liu@nokia.com'; 'Lars-Erik.Jonsson@epl.ericsson.se';
'rajeev.koodli@nokia.com'
Subject: RE: [seamoby] RE: [ROHC] Compression startup behaviour


Having only skimmed the evolution of this thread, I have apparently 
lost the train of thought . . . 
What does context transfer have to do with packet losses over the 
air? No one is proposing context transfer to or from the mobile. All 
context transfer being discussed in this wg is within the wireline 
network. 
Gary 


> -----Original Message----- 
> From: zhigang.liu@nokia.com [mailto:zhigang.liu@nokia.com] 
> Sent: Thursday, March 29, 2001 12:35 PM 
> To: Lars-Erik.Jonsson@epl.ericsson.se; rajeev.koodli@nokia.com; 
> micke@CS.Arizona.EDU; mobile-ip@sunroof.eng.sun.com; rohc@cdt.luth.se; 
> seamoby@cdma-2000.org 
> Subject: [seamoby] RE: [rohc] Compression startup behavior 
> 
> 
> > No, the best case would be 1, 
> 
> ... if there are no transmission errors and the compressor knows 
> this. 
> 
> > while 3 probably would be a 
> > good candidate for realistic conditions and VERY FEASIBLE IN 
> > PRACTICE. If the systems are providing acceptable service 
> > quality, higher numbers should not be needed. 
> 
> 3 may or may not work. It depends. In cellular, "acceptable 
> service quality" means different thing at different time and 
> location (of the mobile node). When you are driving in your car 
> in a traffic jam at 5pm, a higher packet loss rate is acceptable 
> (to the operator, not you). The very reason that a handover 
> occurs is due to poor radio conditions at the edge of a cell, 
> which means you are also at the edge of the new cell after 
> handover, which means the condition of the new channel probably 
> will not be very good either. Those factors have to be 
> considered. 
> 
> > We could probably argue about this for months (see ROHC 
> > mailing list from April 2000), so I will try not to continue 
> > this discussion. 
> 
> Oops, I just did. 
> 
> > I guess that context transfer is a mechanism 
> > that will be developed (snip) 
> 
> Good, at least we agree on one thing. 
> 
> Br, 
> Zhigang 
>  
>  
> > Rgds, 
> > /L-E 
> > --- 
> > Mailing list for Robust Header Compression WG 
> > Archive: http://www.cdt.luth.se/rohc/ 
> > 
> 


From owner-seamoby@diameter.org  Thu Mar 29 17:20:08 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA14227
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 17:20:07 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TKVca05117
	for seamoby-list; Thu, 29 Mar 2001 12:31:38 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TKVYF05112
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 12:31:34 -0800
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2TJepg13211
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 13:40:51 -0600 (CST)
Received: from daebh02nok.americas.nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5297084ec5ac12f255079@davir02nok.americas.nokia.com>;
 Thu, 29 Mar 2001 13:40:22 -0600
Received: by daebh02nok with Internet Mail Service (5.5.2652.78)
	id <GKS5KA1D>; Thu, 29 Mar 2001 13:40:22 -0600
Message-ID: <B9CFA6CE8FFDD211A1FB0008C7894E4601A659D4@bseis01nok>
From: rajeev.koodli@nokia.com
To: zhigang.liu@nokia.com, Lars-Erik.Jonsson@epl.ericsson.se,
        micke@CS.Arizona.EDU, mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se,
        seamoby@cdma-2000.org
Subject: [seamoby] RE: [rohc] Compression startup behavior
Date: Thu, 29 Mar 2001 13:40:21 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

> -----Original Message-----
> From: Liu Zhigang (NRC/Dallas) 
> Sent: Thursday, March 29, 2001 9:35 AM
> To: 'ext Lars-Erik Jonsson (EPL)'; Koodli Rajeev (NRC/MtView);
> micke@cs.arizona.edu; mobile-ip@sunroof.eng.sun.com; rohc@cdt.luth.se;
> seamoby@cdma-2000.org
> Subject: RE: [rohc] Compression startup behavior
> 
> 
> > No, the best case would be 1, 
> 
> ... if there are no transmission errors and the compressor knows
> this.
> 
> > while 3 probably would be a 
> > good candidate for realistic conditions and VERY FEASIBLE IN 
> > PRACTICE. If the systems are providing acceptable service 
> > quality, higher numbers should not be needed. 
> 
> 3 may or may not work. It depends. In cellular, "acceptable 
> service quality" means different thing at different time and 
> location (of the mobile node). When you are driving in your car 
> in a traffic jam at 5pm, a higher packet loss rate is acceptable 
> (to the operator, not you). The very reason that a handover
> occurs is due to poor radio conditions at the edge of a cell,
> which means you are also at the edge of the new cell after
> handover, which means the condition of the new channel probably
> will not be very good either. Those factors have to be 
> considered.
> 
> > We could probably argue about this for months (see ROHC 
> > mailing list from April 2000), so I will try not to continue 
> > this discussion. 
> 
> Oops, I just did. 
> 
> > I guess that context transfer is a mechanism 
> > that will be developed (snip)
> 
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a good starting position.

Regards,

-Rajeev

> Good, at least we agree on one thing.
> 
    


> Br,
> Zhigang
>  
>  
> > Rgds,
> > /L-E
> > ---
> > Mailing list for Robust Header Compression WG
> > Archive: http://www.cdt.luth.se/rohc/
> > 
> 


From owner-seamoby@diameter.org  Thu Mar 29 18:20:32 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA17313
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 18:20:31 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TKCA905053
	for seamoby-list; Thu, 29 Mar 2001 12:12:10 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TKC6F05048
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 12:12:06 -0800
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2TJLMg10852
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 13:21:22 -0600 (CST)
Received: from daebh01nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5296f69a87ac12f257079@davir04nok.americas.nokia.com>;
 Thu, 29 Mar 2001 13:21:02 -0600
Received: by daebh01nok with Internet Mail Service (5.5.2652.78)
	id <GKQMHFDQ>; Thu, 29 Mar 2001 13:21:01 -0600
Message-ID: <B9CFA6CE8FFDD211A1FB0008C7894E4601A659D1@bseis01nok>
From: rajeev.koodli@nokia.com
To: gkenward@nortelnetworks.com, seamoby@diameter.org
Cc: zhigang.liu@nokia.com, Lars-Erik.Jonsson@epl.ericsson.se,
        rajeev.koodli@nokia.com
Subject: RE: [seamoby] RE: [ROHC] Compression startup behaviour
Date: Thu, 29 Mar 2001 13:21:00 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0B885.634EBE80"
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0B885.634EBE80
Content-Type: text/plain;
	charset="iso-8859-1"

 
Hello Gary,
 

 

Having only skimmed the evolution of this thread, I have apparently 
lost the train of thought . . . 
[Rajeev]  Happens sometimes :-)

What does context transfer have to do with packet losses over the 
air? 
[Rajeev]  Header compression context initialization is done over the air
interface. The packet losses over the air need to be considered here since a
compressor has to obtain sufficient confidence that the decompressor has the
required state to conduct operation in a spectrally efficient manner. Packet
losses, higher link latencies could exacerbate context initialization,
leading to wasted bandwidth over air interface. 

When we do context transfer, we can provide a useful alternative to context
re-initialization (where packets losses over air could occur) during
handovers. 

In summary, since context transfer alleviates the need for context
re-initialization, it also helps avoid packets losses  during compression
context re-initialization!

 No one is proposing context transfer to or from the mobile. All 
context transfer being discussed in this wg is within the wireline 
network. 
[Rajeev]  Right. 

Regards,

-Rajeev

 

Gary 


> -----Original Message----- 
> From: zhigang.liu@nokia.com [ mailto:zhigang.liu@nokia.com
<mailto:zhigang.liu@nokia.com> ] 
> Sent: Thursday, March 29, 2001 12:35 PM 
> To: Lars-Erik.Jonsson@epl.ericsson.se; rajeev.koodli@nokia.com; 
> micke@CS.Arizona.EDU; mobile-ip@sunroof.eng.sun.com; rohc@cdt.luth.se; 
> seamoby@cdma-2000.org 
> Subject: [seamoby] RE: [rohc] Compression startup behavior 
> 
> 
> > No, the best case would be 1, 
> 
> ... if there are no transmission errors and the compressor knows 
> this. 
> 
> > while 3 probably would be a 
> > good candidate for realistic conditions and VERY FEASIBLE IN 
> > PRACTICE. If the systems are providing acceptable service 
> > quality, higher numbers should not be needed. 
> 
> 3 may or may not work. It depends. In cellular, "acceptable 
> service quality" means different thing at different time and 
> location (of the mobile node). When you are driving in your car 
> in a traffic jam at 5pm, a higher packet loss rate is acceptable 
> (to the operator, not you). The very reason that a handover 
> occurs is due to poor radio conditions at the edge of a cell, 
> which means you are also at the edge of the new cell after 
> handover, which means the condition of the new channel probably 
> will not be very good either. Those factors have to be 
> considered. 
> 
> > We could probably argue about this for months (see ROHC 
> > mailing list from April 2000), so I will try not to continue 
> > this discussion. 
> 
> Oops, I just did. 
> 
> > I guess that context transfer is a mechanism 
> > that will be developed (snip) 
> 
> Good, at least we agree on one thing. 
> 
> Br, 
> Zhigang 
>  
>  
> > Rgds, 
> > /L-E 
> > --- 
> > Mailing list for Robust Header Compression WG 
> > Archive: http://www.cdt.luth.se/rohc/ <http://www.cdt.luth.se/rohc/>  
> > 
> 


------_=_NextPart_001_01C0B885.634EBE80
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [seamoby] RE: [ROHC] Compression startup behaviour</TITLE>

<META content="MSHTML 5.00.3013.2600" name=GENERATOR></HEAD>
<BODY>
<DIV>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=620395218-29032001>Hello 
Gary,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=620395218-29032001></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>&nbsp;</DIV></FONT>
  <P><FONT size=2>Having only skimmed the evolution of this thread, I have 
  apparently</FONT> <BR><FONT size=2>lost the train of thought . . . 
  <BR></FONT><FONT size=2><FONT color=#0000ff face=Arial><SPAN 
  class=620395218-29032001>[Rajeev]&nbsp;&nbsp;Happens sometimes 
  :-)</SPAN></FONT></FONT></P>
  <P><FONT size=2>What does context transfer have to do with packet losses over 
  the</FONT> <BR><FONT size=2>air? <BR><SPAN class=620395218-29032001><FONT 
  color=#0000ff face=Arial>[Rajeev]&nbsp; Header compression context 
  initialization is done over the air interface. The packet losses over the air 
  need to be considered here since a compressor has to obtain sufficient 
  confidence that the decompressor has the required state to conduct operation 
  in&nbsp;a spectrally efficient manner.  Packet losses, higher link latencies 
  could exacerbate context initialization, leading to wasted bandwidth over air 
  interface. </FONT></SPAN></FONT></P>
  <P><FONT color=#0000ff face=Arial size=2><SPAN class=620395218-29032001>When 
  we do context transfer, we can provide a useful alternative to context 
  re-initialization (where packets losses over air could occur) during 
  handovers. </SPAN></FONT><FONT color=#0000ff face=Arial size=2><SPAN 
  class=620395218-29032001></SPAN></FONT></P>
  <P><FONT color=#0000ff face=Arial size=2><SPAN class=620395218-29032001>In 
  summary, since context transfer alleviates the need for context 
  re-initialization, it also helps avoid packets losses&nbsp; during compression 
  context re-initialization!</SPAN></FONT></P>
  <P><FONT size=2><SPAN class=620395218-29032001>&nbsp;</SPAN>No one is 
  proposing context transfer to or from the mobile. All</FONT> <BR><FONT 
  size=2>context transfer being discussed in this wg is within the 
  wireline</FONT> <BR><FONT size=2>network.</FONT> <BR><FONT color=#0000ff 
  face=Arial size=2><SPAN class=620395218-29032001>[Rajeev]&nbsp;&nbsp;Right. 
  </SPAN></FONT></P>
  <P><FONT color=#0000ff face=Arial size=2><SPAN 
  class=620395218-29032001>Regards,</SPAN></FONT></P>
  <P><FONT color=#0000ff face=Arial size=2><SPAN 
  class=620395218-29032001>-Rajeev</SPAN></FONT></P>
  <P><FONT color=#0000ff face=Arial size=2><SPAN 
  class=620395218-29032001></SPAN></FONT>&nbsp;</P>
  <P><FONT size=2>Gary</FONT> </P><BR>
  <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
  From: zhigang.liu@nokia.com [<A 
  href="mailto:zhigang.liu@nokia.com">mailto:zhigang.liu@nokia.com</A>]</FONT> 
  <BR><FONT size=2>&gt; Sent: Thursday, March 29, 2001 12:35 PM</FONT> <BR><FONT 
  size=2>&gt; To: Lars-Erik.Jonsson@epl.ericsson.se; 
  rajeev.koodli@nokia.com;</FONT> <BR><FONT size=2>&gt; micke@CS.Arizona.EDU; 
  mobile-ip@sunroof.eng.sun.com; rohc@cdt.luth.se;</FONT> <BR><FONT size=2>&gt; 
  seamoby@cdma-2000.org</FONT> <BR><FONT size=2>&gt; Subject: [seamoby] RE: 
  [rohc] Compression startup behavior</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; No, the best 
  case would be 1, </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; ... 
  if there are no transmission errors and the compressor knows</FONT> <BR><FONT 
  size=2>&gt; this.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  &gt; while 3 probably would be a </FONT><BR><FONT size=2>&gt; &gt; good 
  candidate for realistic conditions and VERY FEASIBLE IN </FONT><BR><FONT 
  size=2>&gt; &gt; PRACTICE. If the systems are providing acceptable service 
  </FONT><BR><FONT size=2>&gt; &gt; quality, higher numbers should not be 
  needed. </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 3 may or may 
  not work. It depends. In cellular, "acceptable </FONT><BR><FONT size=2>&gt; 
  service quality" means different thing at different time and </FONT><BR><FONT 
  size=2>&gt; location (of the mobile node). When you are driving in your car 
  </FONT><BR><FONT size=2>&gt; in a traffic jam at 5pm, a higher packet loss 
  rate is acceptable </FONT><BR><FONT size=2>&gt; (to the operator, not you). 
  The very reason that a handover</FONT> <BR><FONT size=2>&gt; occurs is due to 
  poor radio conditions at the edge of a cell,</FONT> <BR><FONT size=2>&gt; 
  which means you are also at the edge of the new cell after</FONT> <BR><FONT 
  size=2>&gt; handover, which means the condition of the new channel 
  probably</FONT> <BR><FONT size=2>&gt; will not be very good either. Those 
  factors have to be </FONT><BR><FONT size=2>&gt; considered.</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; We could probably argue about 
  this for months (see ROHC </FONT><BR><FONT size=2>&gt; &gt; mailing list from 
  April 2000), so I will try not to continue </FONT><BR><FONT size=2>&gt; &gt; 
  this discussion. </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  Oops, I just did. </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  &gt; I guess that context transfer is a mechanism </FONT><BR><FONT size=2>&gt; 
  &gt; that will be developed (snip)</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; Good, at least we agree on one thing.</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Br,</FONT> <BR><FONT 
  size=2>&gt; Zhigang</FONT> <BR><FONT size=2>&gt;&nbsp; </FONT><BR><FONT 
  size=2>&gt;&nbsp; </FONT><BR><FONT size=2>&gt; &gt; Rgds,</FONT> <BR><FONT 
  size=2>&gt; &gt; /L-E</FONT> <BR><FONT size=2>&gt; &gt; ---</FONT> <BR><FONT 
  size=2>&gt; &gt; Mailing list for Robust Header Compression WG</FONT> 
  <BR><FONT size=2>&gt; &gt; Archive: <A href="http://www.cdt.luth.se/rohc/" 
  target=_blank>http://www.cdt.luth.se/rohc/</A></FONT> <BR><FONT size=2>&gt; 
  &gt; </FONT><BR><FONT size=2>&gt; </FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C0B885.634EBE80--


From owner-seamoby@diameter.org  Thu Mar 29 19:06:00 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA19601
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 19:05:59 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TLvON05353
	for seamoby-list; Thu, 29 Mar 2001 13:57:24 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TLvIF05347
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 13:57:18 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Thu, 29 Mar 2001 15:48:17 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <HSTBXQR0>; Thu, 29 Mar 2001 15:48:18 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8E8A@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'zhigang.liu@nokia.com'" <zhigang.liu@nokia.com>, seamoby@diameter.org
Cc: Lars-Erik.Jonsson@epl.ericsson.se, rajeev.koodli@nokia.com
Subject: RE: [seamoby] RE: [ROHC] Compression startup behaviour
Date: Thu, 29 Mar 2001 15:48:15 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0B891.938FFDF0"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0B891.938FFDF0
Content-Type: text/plain;
	charset="iso-8859-1"

Zhigang:

  Thanks for the clarification. If I understand you, I agree that the
benefits of CT outweigh the costs. The primary application of header
compression as far as I know is VoIP. I find it hard to believe that
3 packets can be sent over the air in time to prevent noticeable artifacts
from being introduced at the decoder.

Gary

> -----Original Message-----
> From: zhigang.liu@nokia.com [mailto:zhigang.liu@nokia.com]
> Sent: Thursday, March 29, 2001 2:23 PM
> To: Kenward, Gary [WDLN2:AN10:EXCH]; seamoby@diameter.org
> Cc: Lars-Erik.Jonsson@epl.ericsson.se; rajeev.koodli@nokia.com
> Subject: RE: [seamoby] RE: [ROHC] Compression startup behaviour
> 
> 
> Hi Gary,
> 
> You're right. The discussion is indeed confusing for anyone 
> who hasn't followed the ROHC list. In short, the argument on the 
> packet losses (more accurately, the consecutive losses)
> is about how much is the benefit of HC context relocation,
> and thus whether it is needed.
> 
> The logic is: without context relocation, an estimate of consecutive
> packet losses determines how many IR packets are needed to establish 
> the context over the air after handover. With context relocation,
> those IR packets can be avoided.
> 
> To me, the benefit outweighs the cost (if any).
> 
> Br,
> Zhigang
> 
> -----Original Message-----
> From: ext Gary Kenward [mailto:gkenward@nortelnetworks.com]
> Sent: Thursday, March 29, 2001 12:13 PM
> To: 'seamoby'
> Cc: 'zhigang.liu@nokia.com'; 'Lars-Erik.Jonsson@epl.ericsson.se';
> 'rajeev.koodli@nokia.com'
> Subject: RE: [seamoby] RE: [ROHC] Compression startup behaviour
> 
> 
> Having only skimmed the evolution of this thread, I have apparently 
> lost the train of thought . . . 
> What does context transfer have to do with packet losses over the 
> air? No one is proposing context transfer to or from the mobile. All 
> context transfer being discussed in this wg is within the wireline 
> network. 
> Gary 
> 
> 
> > -----Original Message----- 
> > From: zhigang.liu@nokia.com [mailto:zhigang.liu@nokia.com] 
> > Sent: Thursday, March 29, 2001 12:35 PM 
> > To: Lars-Erik.Jonsson@epl.ericsson.se; rajeev.koodli@nokia.com; 
> > micke@CS.Arizona.EDU; mobile-ip@sunroof.eng.sun.com; 
> rohc@cdt.luth.se; 
> > seamoby@cdma-2000.org 
> > Subject: [seamoby] RE: [rohc] Compression startup behavior 
> > 
> > 
> > > No, the best case would be 1, 
> > 
> > ... if there are no transmission errors and the compressor knows 
> > this. 
> > 
> > > while 3 probably would be a 
> > > good candidate for realistic conditions and VERY FEASIBLE IN 
> > > PRACTICE. If the systems are providing acceptable service 
> > > quality, higher numbers should not be needed. 
> > 
> > 3 may or may not work. It depends. In cellular, "acceptable 
> > service quality" means different thing at different time and 
> > location (of the mobile node). When you are driving in your car 
> > in a traffic jam at 5pm, a higher packet loss rate is acceptable 
> > (to the operator, not you). The very reason that a handover 
> > occurs is due to poor radio conditions at the edge of a cell, 
> > which means you are also at the edge of the new cell after 
> > handover, which means the condition of the new channel probably 
> > will not be very good either. Those factors have to be 
> > considered. 
> > 
> > > We could probably argue about this for months (see ROHC 
> > > mailing list from April 2000), so I will try not to continue 
> > > this discussion. 
> > 
> > Oops, I just did. 
> > 
> > > I guess that context transfer is a mechanism 
> > > that will be developed (snip) 
> > 
> > Good, at least we agree on one thing. 
> > 
> > Br, 
> > Zhigang 
> >  
> >  
> > > Rgds, 
> > > /L-E 
> > > --- 
> > > Mailing list for Robust Header Compression WG 
> > > Archive: http://www.cdt.luth.se/rohc/ 
> > > 
> > 
> 

------_=_NextPart_001_01C0B891.938FFDF0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>RE: [seamoby] RE: [ROHC] Compression startup behaviour</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Zhigang:</FONT>
</P>

<P><FONT SIZE=2>&nbsp; Thanks for the clarification. If I understand you, I agree that the</FONT>
<BR><FONT SIZE=2>benefits of CT outweigh the costs. The primary application of header</FONT>
<BR><FONT SIZE=2>compression as far as I know is VoIP. I find it hard to believe that</FONT>
<BR><FONT SIZE=2>3 packets can be sent over the air in time to prevent noticeable artifacts</FONT>
<BR><FONT SIZE=2>from being introduced at the decoder.</FONT>
</P>

<P><FONT SIZE=2>Gary</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: zhigang.liu@nokia.com [<A HREF="mailto:zhigang.liu@nokia.com">mailto:zhigang.liu@nokia.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Thursday, March 29, 2001 2:23 PM</FONT>
<BR><FONT SIZE=2>&gt; To: Kenward, Gary [WDLN2:AN10:EXCH]; seamoby@diameter.org</FONT>
<BR><FONT SIZE=2>&gt; Cc: Lars-Erik.Jonsson@epl.ericsson.se; rajeev.koodli@nokia.com</FONT>
<BR><FONT SIZE=2>&gt; Subject: RE: [seamoby] RE: [ROHC] Compression startup behaviour</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Hi Gary,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; You're right. The discussion is indeed confusing for anyone </FONT>
<BR><FONT SIZE=2>&gt; who hasn't followed the ROHC list. In short, the argument on the </FONT>
<BR><FONT SIZE=2>&gt; packet losses (more accurately, the consecutive losses)</FONT>
<BR><FONT SIZE=2>&gt; is about how much is the benefit of HC context relocation,</FONT>
<BR><FONT SIZE=2>&gt; and thus whether it is needed.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; The logic is: without context relocation, an estimate of consecutive</FONT>
<BR><FONT SIZE=2>&gt; packet losses determines how many IR packets are needed to establish </FONT>
<BR><FONT SIZE=2>&gt; the context over the air after handover. With context relocation,</FONT>
<BR><FONT SIZE=2>&gt; those IR packets can be avoided.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; To me, the benefit outweighs the cost (if any).</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Br,</FONT>
<BR><FONT SIZE=2>&gt; Zhigang</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: ext Gary Kenward [<A HREF="mailto:gkenward@nortelnetworks.com">mailto:gkenward@nortelnetworks.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Thursday, March 29, 2001 12:13 PM</FONT>
<BR><FONT SIZE=2>&gt; To: 'seamoby'</FONT>
<BR><FONT SIZE=2>&gt; Cc: 'zhigang.liu@nokia.com'; 'Lars-Erik.Jonsson@epl.ericsson.se';</FONT>
<BR><FONT SIZE=2>&gt; 'rajeev.koodli@nokia.com'</FONT>
<BR><FONT SIZE=2>&gt; Subject: RE: [seamoby] RE: [ROHC] Compression startup behaviour</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Having only skimmed the evolution of this thread, I have apparently </FONT>
<BR><FONT SIZE=2>&gt; lost the train of thought . . . </FONT>
<BR><FONT SIZE=2>&gt; What does context transfer have to do with packet losses over the </FONT>
<BR><FONT SIZE=2>&gt; air? No one is proposing context transfer to or from the mobile. All </FONT>
<BR><FONT SIZE=2>&gt; context transfer being discussed in this wg is within the wireline </FONT>
<BR><FONT SIZE=2>&gt; network. </FONT>
<BR><FONT SIZE=2>&gt; Gary </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; -----Original Message----- </FONT>
<BR><FONT SIZE=2>&gt; &gt; From: zhigang.liu@nokia.com [<A HREF="mailto:zhigang.liu@nokia.com">mailto:zhigang.liu@nokia.com</A>] </FONT>
<BR><FONT SIZE=2>&gt; &gt; Sent: Thursday, March 29, 2001 12:35 PM </FONT>
<BR><FONT SIZE=2>&gt; &gt; To: Lars-Erik.Jonsson@epl.ericsson.se; rajeev.koodli@nokia.com; </FONT>
<BR><FONT SIZE=2>&gt; &gt; micke@CS.Arizona.EDU; mobile-ip@sunroof.eng.sun.com; </FONT>
<BR><FONT SIZE=2>&gt; rohc@cdt.luth.se; </FONT>
<BR><FONT SIZE=2>&gt; &gt; seamoby@cdma-2000.org </FONT>
<BR><FONT SIZE=2>&gt; &gt; Subject: [seamoby] RE: [rohc] Compression startup behavior </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; No, the best case would be 1, </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; ... if there are no transmission errors and the compressor knows </FONT>
<BR><FONT SIZE=2>&gt; &gt; this. </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; while 3 probably would be a </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; good candidate for realistic conditions and VERY FEASIBLE IN </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; PRACTICE. If the systems are providing acceptable service </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; quality, higher numbers should not be needed. </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; 3 may or may not work. It depends. In cellular, &quot;acceptable </FONT>
<BR><FONT SIZE=2>&gt; &gt; service quality&quot; means different thing at different time and </FONT>
<BR><FONT SIZE=2>&gt; &gt; location (of the mobile node). When you are driving in your car </FONT>
<BR><FONT SIZE=2>&gt; &gt; in a traffic jam at 5pm, a higher packet loss rate is acceptable </FONT>
<BR><FONT SIZE=2>&gt; &gt; (to the operator, not you). The very reason that a handover </FONT>
<BR><FONT SIZE=2>&gt; &gt; occurs is due to poor radio conditions at the edge of a cell, </FONT>
<BR><FONT SIZE=2>&gt; &gt; which means you are also at the edge of the new cell after </FONT>
<BR><FONT SIZE=2>&gt; &gt; handover, which means the condition of the new channel probably </FONT>
<BR><FONT SIZE=2>&gt; &gt; will not be very good either. Those factors have to be </FONT>
<BR><FONT SIZE=2>&gt; &gt; considered. </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; We could probably argue about this for months (see ROHC </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; mailing list from April 2000), so I will try not to continue </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; this discussion. </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Oops, I just did. </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; I guess that context transfer is a mechanism </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; that will be developed (snip) </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Good, at least we agree on one thing. </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Br, </FONT>
<BR><FONT SIZE=2>&gt; &gt; Zhigang </FONT>
<BR><FONT SIZE=2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Rgds, </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; /L-E </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; --- </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Mailing list for Robust Header Compression WG </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Archive: <A HREF="http://www.cdt.luth.se/rohc/" TARGET="_blank">http://www.cdt.luth.se/rohc/</A> </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0B891.938FFDF0--


From owner-seamoby@diameter.org  Thu Mar 29 19:06:13 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA19615
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 19:06:12 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TKwpG05179
	for seamoby-list; Thu, 29 Mar 2001 12:58:51 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TKwUF05174
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 12:58:30 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA28444;
	Thu, 29 Mar 2001 12:07:45 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA10533;
	Thu, 29 Mar 2001 12:07:39 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id MAA28879;
	Thu, 29 Mar 2001 12:07:38 -0800 (PST)
Message-Id: <200103292007.MAA28879@heliopolis.Eng.Sun.COM>
Date: Thu, 29 Mar 2001 12:07:38 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] To page, or not to page
To: pcalhoun@nasnfs.eng.sun.com, seamoby@cdma-2000.org,
        David.P.Martin@nextel.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: SRjgiiiVBRwryLu21pD9qQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Dave,

>Before the Minneapolis meeting I was in agreement with the problem
>statement, however some statements were made at the meeting that concerned
>me (if you trace back the thread I started you will see my original post
>occurred just after the meeting in Minneapolis).
>
>I interpreted the problem statement to mean that our charter would be to
>utilize paging if it existed in layer 2, and if not, that a best-effort IP
>paging type of protocol would be developed to try and deliver packets for
>those cases where paging was not supported at layer 2.  What I heard at the
>meeting and later is that there is a strong desire to build a layer 3
>protocol that incorporates substantial layer 2 functionality.  I am not
>against this, I just want clarity on the scope of the problem that we are

I disagree with this analysis. My interpretation of the WG concensus probe
is that the WG doesn't want the protocol to be designed with a requirement
for L2 paging. This does not preclude using L2 paging when available.

That said, the problem statement addresses the issue of systems such
as 802.11 that use reassociation at L2, and how they will not benefit from
L3 paging.

>going to solve.  If as a group we feel that we want to take on all or a
>majority of layer 2 functionality (because no assumptions are being made
>about what exists at layer 2), I would like to see this as a seperate effort
>(at least initially) than the case where we can (or do) make assumptions
>about layer 2.  Maybe the effort becomes the same protocol, but then again
>there may be good reasons to have two different (but complimentary,
>non-overlapping protocols).  I don't know what the best solution is, but I
>feel it is premature to assume that one protocol may be the answer, which
>was where the discussion in Minneapolis, and some of the discussion on the
>list seemed to lead.

The issue here is a hypothetical dormant mode (or maybe not so hypothetical, 
Kluwinder's comments on Bluetooth lead me to believe that Bluetooth may behave 
this way) where the mobile node periodically comes out of dormant mode to listen
to L2, but it does NOT reassociate with an access point. For this kind
of an L2, a periodically broadcast paging message at L3 would work like
an L2 page in a cellular system.

I don't think we need to have two protocols, I think we need to firstly
agree what the requirements should say, then secondly, make sure the 
protocol reflects the requirements. 

Can you tell me what you think the requirements should say? I put out
a list of possible requirements regarding L2 (duplicated below), which
do you think should be included?

		jak
		
>         a) Some people seem to feel that it is simply not possible to
>         define an L3 paging protocol without L2 support, and want the
>         requirements to reflect that.
> 
>         b) Some people want to make sure that saying that L2 is not
>         required does not rule out using L2 support when you have it
>         and want the requirements to reflect that.
> 
>         c) Some people would like to define an L3 paging protocol completely
>         independent of L2, and therefore say nothing about L2 in the
>         requirements or in the design.
		



From owner-seamoby@diameter.org  Thu Mar 29 19:16:52 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA20242
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 19:16:51 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TLet705310
	for seamoby-list; Thu, 29 Mar 2001 13:40:55 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TLepF05305
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 13:40:52 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4S6DY>; Thu, 29 Mar 2001 15:50:06 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2AA9@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Casati, Alessio (Alessio)'" <acasati@lucent.com>,
        "'Patrice Calhoun'"
	 <pcalhoun@nasnfs.eng.sun.com>,
        James Kempf
	 <kempf@heliopolis.Eng.Sun.COM>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] To page, or not to page
Date: Thu, 29 Mar 2001 15:50:05 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Casati, Alessio (Alessio) [mailto:acasati@lucent.com]
> Sent: Thursday, March 29, 2001 12:20 PM
> To: 'Patrice Calhoun'; James Kempf
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] To page, or not to page
> 
> 
> I did bother (yesterday) to read the draft.
> So I'm not sure any of my comments might be used to 
> gauge consensus.
> What bothers me is that people decide that L3
> paging is required without saying what it is
> (unless I missed something):
> 
> Is it based on multicast? is it unicast? These two
> options make it a completely different thing
> 
> Multicast would more fit what today's L2 paging definition is,
> however this would imply that a paging would wake up all the
> terminals (not acceptable). 


First, I agree that a paging protocol is not neccesary.

What I was suggesting is:

1. Timely Message enters Paging Area.
2. An AR takes Message places it in a Multicast packet destined for all
AP/ARs in the Paging Area.
3. Upon an AP/AR recieving the Multicast packet it removes the unicast
message and sends it over the air to the one intended Mobile. 

- Kulwinder.

> On the other hand, if it is unicast, the page would be replaced most 
> conveniently by user data. the link over which data are received
> will tell where to send any agent solicitation... If more 
> than one link,
> guess what, pick one you like most. What would be nedeed is only
> a location update protocol. A location update protocol is
> already available and it is mobile IP (or an extention of it,
> if at all needed).
> 
> as such, I'd support to take a step back and
> re-consider the soundness of the reqs (OK, the IESG may do 
> that instead,
> if we want an analogy with what has happened with MIPv6 ;).
> 
> Also, maybe what I described now cannot quite be defined as paging
> (although I truly believe paging may gain more cookie points,
> in a marketing setting).
> 
> 
> alessio
> 
> -----Original Message-----
> From: Patrice Calhoun [mailto:pcalhoun@nasnfs.eng.sun.com]
> Sent: 29 March 2001 02:03
> To: James Kempf
> Cc: seamoby@cdma-2000.org; pcalhoun@nasnfs.eng.sun.com
> Subject: Re: [seamoby] To page, or not to page
> 
> 
> > My interpretation of the traffic on the list regarding paging is the
> > following:
> > 
> > 1) Some people haven't read the problem statement and 
> therefore don't
> > have an understanding of what led the design team to conclude that
> > support for L3 paging was desirable and even necessary in the
> multitechnology
> > case.
> 
> ok. So I will not attempt to gauge concensus from people that haven't
> bothered
> to read the draft.
> 
> > 
> > 2) There is a disagreement with the working group concensus 
> expressed at
> > IETF 50 that the design team should not require L2 paging.
> 
> which is ok because we need to gauge concensus on the list, 
> regardless of
> what
> happened at the meeting.
> 
> > This seems to
> > break down into the following areas:
> > 
> > 	a) Some people seem to feel that it is simply not possible to
> > 	define an L3 paging protocol without L2 support, and want the
> > 	requirements to reflect that.
> > 	
> > 	b) Some people want to make sure that saying that L2 is not
> > 	required does not rule out using L2 support when you have it
> > 	and want the requirements to reflect that.
> > 	
> > 	c) Some people would like to define an L3 paging 
> protocol completely
> > 	independent of L2, and therefore say nothing about L2 in the
> > 	requirements or in the design.
> 
> ok. Can we agree that these issues can be addressed during 
> the requirements
> phase?
> 
> PatC
> 


From owner-seamoby@diameter.org  Thu Mar 29 19:23:33 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA20688
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 19:23:32 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TLXEv05282
	for seamoby-list; Thu, 29 Mar 2001 13:33:14 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TLXAF05277
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 13:33:10 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4S5P9>; Thu, 29 Mar 2001 01:55:49 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2AA8@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'David R. Oran'" <oran@cisco.com>,
        "'Martin, David P'"
	 <David.P.Martin@nextel.com>,
        "'Michael Thomas'" <mat@cisco.com>
Cc: seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
Date: Thu, 29 Mar 2001 01:55:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: David R. Oran [mailto:oran@cisco.com]
> Sent: Wednesday, March 28, 2001 8:36 AM
> To: 'Martin, David P'; 'Michael Thomas'
> Cc: seamoby@diameter.org
> Subject: RE: [seamoby] L2/L3 Paging
> 
> 
> If the L2 knows where the node is, then all paging does is force a
> wakeup, right? Seems like you could invoke whatever mechanism 
> is needed
> for the wakeup (which somehow *has* to have components below 
> L3 it seems
> to me) when IP packets arrive for the host.
> 
> If the L2 does not know where the node is, then it has to find it. Is
> this the mechanism you say always has L2 state? It would be helpful if
> we L3 babes-in-the-woods could get a better understanding of just what
> this state is, how quickly it degrades, and how a L3 could conveivably
> make use of it (e.g. to keep routing tables correct), rather than
> arguing about whether the function belongs exclusively in L2 or L3.
> 
> Here's a puzzler though. Maybe it will help illuminate why us 
> L3 crazies
> keep raining on the paging-is-done-just-fine-at-L2 parade. Let's say I
> have a host with two radios, an 802.11 and a WCDMA. At some time it is
> reachable through both of them but is receiving IP traffic through the
> 802.11 radio. Then it goes to sleep. New traffic arrives for it. Which
> radio gets paged? Both? What if after going to sleep it wanders into a
> multipath null for the 802.11. What causes the WCDMA to 
> decide it needs
> to page the node and wake it up?

I would think End-User Preferences would guide the network decision making
as stated in a Paging Policy.  Similiar to a Calling Forwarding Policy for a
landline phone. 

- Kulwinder.

> 
> There's *got* to be an interaction with L3 here somewhere, at 
> least for
> routing.
> 
> Donning my asbestos suit...
> 
> Dave.
> 
> > -----Original Message-----
> > From: owner-seamoby@diameter.org 
> > [mailto:owner-seamoby@diameter.org] On Behalf Of Martin, David P
> > Sent: Monday, March 26, 2001 6:57 PM
> > To: 'Michael Thomas'; Martin, David P
> > Cc: seamoby@diameter.org
> > Subject: RE: [seamoby] L2/L3 Paging
> > 
> > 
> > Since I started this, I feel some obligation to help reach 
> > closure ... 
> > 
> > First, I think we've reached consensus that in order to 
> > deliver a packet or page that some type of location 
> > information must be maintained somewhere in order to effect 
> delivery. 
> > 
> > Second, is that location information is needed to support a 
> > delivery mechanism (paging or direct delivery).
> > 
> > I think where we diverge is on whether should seamoby take on 
> > this problem ...
> > 
> > So this leads to the following questions:
> > * Do we assume that location information is known to layer 
> > below IP? _Yes_ implies that there could be a trigger or some 
> > other mechanism to give hints or direction on how to contact 
> > the MN, and would greatly simplify the work for an initial protocol.
> > 
> > _No_ implies that location state would have to be developed 
> > (at the network layer since that is where the IETF lives) and 
> > would mean that some location state engine would have to be 
> > developed to allow paging or packet delivery. This will 
> > require a lot of work.
> > 
> > I would think that it would be more efficient to focus on 
> > known mobility systems, and solve the more esoteric cases 
> > later ... but will yield to the group's consensus.
> > 
> > 
> > 
> > <rant>
> > Now, all mobility based technologies that I know maintain the 
> > state information below IP.  So for all existing 
> > technologies, we would be designing a redundant location 
> > mechanism into the system.  This leads to interesting issues 
> > ... If you have to choose between optimizing the protocol for 
> > paging systems vs non-paging systems, which do you choose?  
> > Which location mechanism do you use?  Do you have a choice?  
> > You will probably be forced to at least use the lower layer 
> > location mechanism.  If I have to use it, what added benefit 
> > is an upper layer location mechanism?  
> > My sense is that the problems/requirements/solutions for 
> > systems that inherently support paging at layers below IP are 
> > more defined, and that work could proceed more quickly in 
> > that space.  General IP paging would be a complex solution to 
> > a problem of unknown proportions, and it will probably take 
> > more time to scope. </rant>
> > 
> > > 
> > > 
> > > Martin, David P writes:
> > >  > >    This doesn't seem to hard: suppose you have a
> > >  > >    beacon which all dormant nodes listen too. To
> > >  > >    find a node, the last attachment point performs
> > >  > >    a search in the local paging area. When the mobile
> > >  > >    wakes up, it establishes a link to its current AP,
> > >  > >    and a tunnel to the old AP to scoop up the
> > >  > >    packet(s).
> > >  >
> > >  > I agree that a paging system can be designed that can work 
> > > with a technology
> > >  > that does not continually track a MN location.
> > >  > 
> > >  > However, a (working) paging system *cannot* be 
> designed without a
> > >  > registration mechanism.
> > > 
> > >    Sure.
> > > 
> > >  > The purpose of a registration mechanism is to
> > >  > provide rough location state information on where a MN is
> > > located in a
> > >  > network topology.  This location state can be of several 
> > > forms, specific
> > >  > access point, specific paging zone, specific network 
> > > (scalability issues),
> > >  > last known access point, last known access zone, etc.  But 
> > > the network has
> > >  > to have some type of location information to even begin to 
> > > guess on how to
> > >  > start paging.
> > > 
> > >    Correct.
> > > 
> > >  > In your example above, the mobile in effect registers 
> > upon  > wake 
> > > up, giving the network location state to work with.
> > > Of course a
> > >  > mechanism must exist (at one or more layers) to deal with 
> > > stale location
> > >  > information.
> > > 
> > >    Yup.
> > >  
> > >  > So, I'm trying to say that there must be some location
> > > state maintained
> > >  > somewhere at layer 2, otherwise the entire network would 
> > > behave as one big
> > >  > LAN segment.
> > > 
> > >    I don't see this as having much to do with L2. If
> > >    I can route an IP packet to the last known point
> > >    of attachment, it could put out the dragnet by
> > >    sending out IP packets which eventually (or not)
> > >    find the mobile node. L2 location information may
> > >    or may not be involved. At a base level, I don't
> > >    think we should count on them being there though.
> > > 
> > > 	    Mike
> > > 
> > 
> 


From owner-seamoby@diameter.org  Thu Mar 29 19:41:07 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA21348
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 19:41:06 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TNVlg05771
	for seamoby-list; Thu, 29 Mar 2001 15:31:47 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TNVgF05766
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 15:31:42 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA28818;
	Thu, 29 Mar 2001 14:39:38 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA09442;
	Thu, 29 Mar 2001 14:39:36 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id OAA02900;
	Thu, 29 Mar 2001 14:39:36 -0800 (PST)
Message-Id: <200103292239.OAA02900@heliopolis.Eng.Sun.COM>
Date: Thu, 29 Mar 2001 14:39:36 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: Paging Functional Architecture ( was: RE: [seamoby] L2/L3 Pag ing)
To: gmorrow@nortelnetworks.com, yohba@tari.toshiba.com
Cc: eanderlind@lucent.com, seamoby@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: /S6XTurAzRG2XeWVHb9W8w==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Yoshihiro,


>When we talk about power control mechanisms for wireline NIC cards,
>the wirelined host may not necessarily be a mobile node.  On the other
>hand, it seems to me that the paging discussed in this WG is tightly
>coupled with mobility (Mobile IP).  Is it out of scope to discuss a
>generic paging mechanism which can be used for both mobile and stable
>nodes?
>

I wouldn't say mobility, I would say routing. The kind of paging
we are looking at is concerned with getting a dormant mode host
to reestablish an active route back into the network. The problem
is most acute with mobile hosts because one can't simply depend
on the routes that were there before the host went dormant to be
valid.

With regard to a wired host, the Intel Wired for Management protocol
defines a kind of paging where a certain L2 frame causes a dormant
mode wired host to wake up (sorry, I don't know any more details).
One could view this as a kind of wired host paging. Note that it
is not sufficient to simply send a packet to the host because
the wakeup is triggered by a special L2 packet, if I am right about
the need for a special L2 frame. If it were the case
(as apparently it is with Bluetooth) that the host could be reawakened
without any special protocol, then one could simply send the packet
and let the host wake up to take it. No paging protocol is needed
in this case.

		jak




From owner-seamoby@diameter.org  Thu Mar 29 20:08:31 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA22457
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 20:08:30 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TMQuG05554
	for seamoby-list; Thu, 29 Mar 2001 14:26:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from nmh.informatik.uni-bremen.de (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TMQpF05549
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 14:26:52 -0800
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id f2TLZiG09606;
	Thu, 29 Mar 2001 23:35:45 +0200 (MEST)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: <rajeev.koodli@nokia.com>, <Hesham.Soliman@era.ericsson.se>,
        <zhigang.liu@nokia.com>
Cc: <mobile-ip@sunroof.eng.sun.com>, <rohc@cdt.luth.se>,
        <seamoby@diameter.org>
Subject: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6 Handover
Date: Thu, 29 Mar 2001 23:35:40 +0200
Message-ID: <NEBBJFHFCKHKFCNLJJBPAEKBEOAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
In-Reply-To: <B9CFA6CE8FFDD211A1FB0008C7894E4601A659D0@bseis01nok>
Importance: Normal
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Well, I think header compression context relocation is doable in
> seamoby. We
> need some help from rohc in defining what a context is, say e.g.,
> IPv6/UDP/RTP/voice-G.723.1.

Rajeev,

while this is only a rough overview of the information set, you might want
to start with section 6.5 of the ROHC RTP document.  I tend to believe that
for most applications, just transferring the static chain will be fine,
though; this is resilient to race conditions and can simply use the data
format already defined in section 5.7.7.

One thing that needs to be defined as well is the signaling between the old
compressor and the new decompressor (and v.v.) so they know context transfer
is in use and contexts have been successfully transferred.  This may be
implicit in the handover or explicitly signalled *).  This signalling may
also be a good place to fix the apparent deficiency in ROHC that there is no
good way to update an address in the outermost IP header (needed for Mobile
IPv6).

*) ROHCers: maybe we need to reserve some bit combinations for ROHC-over-X
signalling...

Gruesse, Carsten



From owner-seamoby@diameter.org  Thu Mar 29 20:19:31 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA22955
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 20:19:30 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TNiL705825
	for seamoby-list; Thu, 29 Mar 2001 15:44:21 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from atlsnmx1.nextel.com (atlsnmx1.nextel.com [167.20.198.200])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TNiHF05820
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 15:44:17 -0800
Received: from atlntgw02.nextel.com (atlntgw02.nextel.com [10.8.79.186])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id RAA16232;
	Thu, 29 Mar 2001 17:53:29 -0500 (EST)
Received: by atlntgw02.nextel.com with Internet Mail Service (5.5.2650.21)
	id <HKW34NMT>; Thu, 29 Mar 2001 17:54:01 -0500
Message-ID: <020A5EC56F3FD411B5230008C716D08586855D@nhqntex01.nextel.com>
From: "Martin, David P" <David.P.Martin@nextel.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        pcalhoun@nasnfs.eng.sun.com,
        "Martin, David P"
	 <David.P.Martin@nextel.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] The last page [Was... To page, or not to page)
Date: Thu, 29 Mar 2001 17:48:31 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk


> In any case, I don't think a layer 3 protocol can solve any 
> layer 2 issues.

I agree.


> The best we could do is require layer 2 support be used
> when available, and have the protocol structured to reflect that. 
> Assuming, of course, concensus is there for using layer 2 support
> when available.

I agree that existing layer 2 features should be leveraged whenever
possible.

On to the requirements! ...


From owner-seamoby@diameter.org  Thu Mar 29 20:21:25 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23112
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 20:21:25 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TM2fB05399
	for seamoby-list; Thu, 29 Mar 2001 14:02:41 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TM2bF05394
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 14:02:37 -0800
Received: from tari.research.telcordia.com (tari [207.3.232.66])
	by thumper.research.telcordia.com (8.10.1/8.10.1) with ESMTP id f2TKjSO11643;
	Thu, 29 Mar 2001 15:45:30 -0500 (EST)
Received: from tuna.research.telcordia.com (ohba@tari-dhcp11.research.telcordia.com [207.3.232.125])
	by tari.research.telcordia.com (8.8.8/8.8.8) with ESMTP id PAA16493;
	Thu, 29 Mar 2001 15:46:56 -0500 (EST)
Date: Thu, 29 Mar 2001 15:48:42 -0500
Message-ID: <87itks8fo5.wl@research.telcordia.com>
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: gmorrow@nortelnetworks.com
Cc: eanderlind@lucent.com, seamoby@diameter.org
Subject: RE: Paging Functional Architecture ( was: RE: [seamoby] L2/L3 Pag ing)
In-Reply-To: In your message of "Thu, 29 Mar 2001 11:28:58 -0600"
	<85AA7486A2C1D411BCA20000F8073E4301B282F2@crchy271.us.nortel.com>
References: <85AA7486A2C1D411BCA20000F8073E4301B282F2@crchy271.us.nortel.com>
User-Agent: Wanderlust/2.2.15 (More Than Words) WEMI/1.13.7 (Shimada) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386-debian-linux)
MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada")
Content-Type: text/plain; charset=ISO-8859-1
X-MIME-Autoconverted: from quoted-printable to 8bit by charizard.diameter.org id f2TM2bF05395
Sender: owner-seamoby@diameter.org
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by charizard.diameter.org id f2TM2fB05399
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA23112



At Thu, 29 Mar 2001 11:28:58 -0600,
Glenn Morrow <gmorrow@nortelnetworks.com> wrote:
> 
> [1  <text/plain; iso-8859-1 (7bit)>]
> 
> [2  <text/html; iso-8859-1 (quoted-printable)>]
> 
> 
> Erik,
> 
> Comments below.
> 
> -----Original Message-----
> From: Erik Anderlind [mailto:eanderlind@lucent.com]
> Sent: Wednesday, March 28, 2001 1:23 PM
> To: seamoby@diameter.org
> Subject: Re: Paging Functional Architecture ( was: RE: [seamoby] L2/L3
> Paging)
> 
> 
> Glenn,
> We need to be careful in defining functional entities such as the paging
> and
> tracking agent - we do not want to preclude that these functions could
> be
> provided in a distributed way (e.g. a subset of routers all implement
> the function.)
> 
> GM] Yes to some extent - if we ever want to get rid of single point of failure
> and true mobile routing within specific sites this is immanent.
> 
> I also disagree that it is a requirement that the paging agent has to be
> at
> the "last hop" edge in all cases.
> 
> GM] Sounds more like a good suggestion than a disagreement really. Seems to me
> that some technologies which are considered MAC/LAC etc.. are beginning to use
> IP transports - makes sense. The blur between L2/L3 is dependent on what the
> L2 in question can do. This is mainly due to the fact some some L1/L2s do more
> than others. I'm not sure what the reaction will be on this, though. It seems
> that the mobies want to go all the way here. Tell me your opinion on this
> question. If the IETF defines IP-based PDUs that essentially implements, in
> some generic access independent manner, the power control mechanisms such as
> paging that used to be considered L2 functions on particular access
> technologies, will they have simply defined a new L2 or will they have built
> some generic form of these functions into IP(L3)? This has been racking my
> brain a bit over the years. It seems to me that even wireline NIC cards might
> benefit from such power control mechanisms - especially in blackout land. I do

When we talk about power control mechanisms for wireline NIC cards,
the wirelined host may not necessarily be a mobile node.  On the other
hand, it seems to me that the paging discussed in this WG is tightly
coupled with mobility (Mobile IP).  Is it out of scope to discuss a
generic paging mechanism which can be used for both mobile and stable
nodes?

Regards,
Yoshihiro Ohba

> agree personally that there should be an option to remote the paging agent. I
> think some will argue that we might be designing an L2 technology that uses IP
> transport in that case. I'm personally O.K. with it and still see the benefits
> from an L3 mechanisms point of view - assuming it does not force us into a
> single point of failure.
> 
> 
> Another useful entity is correspondent node/application that initiates
> the higher level
> need for paging. It will help identify requiremnts around how the other
> different
> entities are located and addressed (if needed).
> ..Erik
> 
> GM] It would be good to explain that paging is a geographic node mobility
> problem and explain the interactions with: applications which provide user
> mobility, location services, network resolution services, etc.. How the
> addressing of user differs from nodes, etc.. I think that is what you were
> trying to say. I think we might hear from some "scope" police on this,
> though.  Clearly, somewhere this information should be documented in at least
> an informational RFC. Perhaps the "why" questions should be answered in such a
> document as well. If I have misinterpreted, please let me know.
> 
> Thanks,
> 
> Glenn
> 


From owner-seamoby@diameter.org  Thu Mar 29 20:29:20 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23559
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 20:29:20 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TMUEp05580
	for seamoby-list; Thu, 29 Mar 2001 14:30:14 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from nmh.informatik.uni-bremen.de (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TMU9F05573
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 14:30:09 -0800
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id f2TLd5G10009;
	Thu, 29 Mar 2001 23:39:05 +0200 (MEST)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Michael Thomas" <mat@cisco.com>
Cc: <Hesham.Soliman@era.ericsson.se>, <mobile-ip@sunroof.eng.sun.com>,
        <rohc@cdt.luth.se>, <seamoby@diameter.org>, <zhigang.liu@nokia.com>
Subject: RE: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6 Handover
Date: Thu, 29 Mar 2001 23:38:59 +0200
Message-ID: <NEBBJFHFCKHKFCNLJJBPKEKBEOAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
In-Reply-To: <15043.34717.849084.517703@thomasm-u1.cisco.com>
Importance: Normal
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>  > (Side note: for hisorical and technical reasons, dealing with
>  > realtime VBR over radio links is much a headache than over wired
>  > links. )
>
>    A-ha! That's one of the reasons I question whether
>    ROHC is even appropriate on the air except in a
>    very small subset of cases (usually long lived streams
>    like RTP for which it was originally intended) As
>    a general purpose tunnel/header compressor, I suspect it is going
>    to have severe thrashing with the way that radio
>    resources are doled out by the AP.

I'm not sure why you are saying that (apart from the fact that we haven't
really done anything else but ROHC RTP yet).  How is ROHC worse than
uncompressed IP or 2507-compressed IP?

Gruesse, Carsten



From owner-seamoby@diameter.org  Thu Mar 29 20:45:53 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA24413
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 20:45:52 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TNJQ105718
	for seamoby-list; Thu, 29 Mar 2001 15:19:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TNJLF05713
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 15:19:21 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA09109;
	Thu, 29 Mar 2001 14:27:59 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA06193;
	Thu, 29 Mar 2001 14:27:37 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id OAA02452;
	Thu, 29 Mar 2001 14:27:37 -0800 (PST)
Message-Id: <200103292227.OAA02452@heliopolis.Eng.Sun.COM>
Date: Thu, 29 Mar 2001 14:27:37 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] To page, or not to page
To: acasati@lucent.com, pcalhoun@nasnfs.eng.sun.com,
        kempf@heliopolis.Eng.Sun.COM, kulwinder.atwal@zucotto.com
Cc: seamoby@cdma-2000.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: SmqihzT5Qfg6pklj8bRn9A==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Kulwinder,


>First, I agree that a paging protocol is not neccesary.
>
>What I was suggesting is:
>
>1. Timely Message enters Paging Area.
>2. An AR takes Message places it in a Multicast packet destined for all
>AP/ARs in the Paging Area.
>3. Upon an AP/AR recieving the Multicast packet it removes the unicast
>message and sends it over the air to the one intended Mobile. 
>

What you have defined here is a paging protocol, regardless
of whether there are special messages or not. Also, it may not
be sufficient for all radio L2, IHMO.


		jak




From owner-seamoby@diameter.org  Thu Mar 29 20:55:05 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA24920
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 20:55:04 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2U0VQ405980
	for seamoby-list; Thu, 29 Mar 2001 16:31:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2U0VLF05975
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 16:31:21 -0800
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2TNgbw05862
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 17:42:37 -0600 (CST)
Received: from daebh01nok.americas.nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5297e40900ac12f254079@davir01nok.americas.nokia.com>;
 Thu, 29 Mar 2001 17:40:22 -0600
Received: by daebh01nok with Internet Mail Service (5.5.2652.78)
	id <GKQMHJNF>; Thu, 29 Mar 2001 17:40:22 -0600
Message-ID: <8572CF1E2A95D211A1190008C7EAA2460213BB77@daeis05nok>
From: zhigang.liu@nokia.com
To: mat@cisco.com, cabo@tzi.org
Cc: Hesham.Soliman@era.ericsson.se, mobile-ip@sunroof.eng.sun.com,
        rohc@cdt.luth.se, seamoby@diameter.org, zhigang.liu@nokia.com
Subject: RE: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6
	 Handover
Date: Thu, 29 Mar 2001 17:40:20 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi Mike,

Your concern is very valid and has been looked into by ROHC WG.
Just a few clarifications:

1) The compressed header size will likely be 1 byte most of the time
(>90%). Then, some first order headers (3~5 bytes). Then, few full
header. As you said, how to send the last two types of packets is
non-trivial. But it is doable. For example, very large headers can
be handled by segmentation either at link layer of by ROHC itself
(see section 5.2.5 of ROHC-09).

2) I guess you're referring to TDMA radio. My understanding is that
CDMA may have a better handle on (slight) VBR.

IMHO, ROHC has done a good job to achieve both robustness and
efficiency. Let me rephrase Carsten's question this way: if 
ROHC is not "appropriate on the air", do you have better approaches
in mind?

Br,
Zhigang

> -----Original Message-----
> From: ext Michael Thomas [mailto:mat@cisco.com]
> Sent: Thursday, March 29, 2001 5:02 PM
> To: Dr. Carsten Bormann
> Cc: Michael Thomas; Hesham.Soliman@era.ericsson.se;
> mobile-ip@sunroof.eng.sun.com; rohc@cdt.luth.se; seamoby@diameter.org;
> zhigang.liu@nokia.com
> Subject: RE: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile
> IPv6 Handover
> 
> 
> Dr. Carsten Bormann writes:
>  > >  > (Side note: for hisorical and technical reasons, dealing with
>  > >  > realtime VBR over radio links is much a headache than 
> over wired
>  > >  > links. )
>  > >
>  > >    A-ha! That's one of the reasons I question whether
>  > >    ROHC is even appropriate on the air except in a
>  > >    very small subset of cases (usually long lived streams
>  > >    like RTP for which it was originally intended) As
>  > >    a general purpose tunnel/header compressor, I suspect 
> it is going
>  > >    to have severe thrashing with the way that radio
>  > >    resources are doled out by the AP.
>  > 
>  > I'm not sure why you are saying that (apart from the fact 
> that we haven't
>  > really done anything else but ROHC RTP yet).  How is ROHC 
> worse than
>  > uncompressed IP or 2507-compressed IP?
> 
> Carsten,
> 
> My understanding about cellular traffic channels
> -- and I would be happy to find out differently --
> is that they do not deal well with variable rate
> traffic well. This is unsurprising since they are
> heavily optimized for voice traffic which has very
> regular periodicity and payload sizes. DOCSIS
> cable is somewhat similar (with which I'm much
> more familar), and the fixed size slots cause
> variable rate coders like CRTP and ROHC much grief
> because the MAC scheduler does not have the
> ability to occassionally allow larger packets in
> real time on an unsolicited grant SID; if you
> start a session with packets every 20ms with 80
> bytes of payload, that's exactly what you get. If
> you occasionally need to send 81 bytes, you cannot
> send it on that traffic channel.
> 
> This presents a real problem for CRTP and ROHC
> when they need to send full headers or first order
> changes.  For this reason, the cable folks perform
> what they call Payload Header Suppression instead.
> Basically, it's just a first order compressor
> which is always on (sorry, if I've got your
> nomenclature mixed up). This obviously works, but
> is not as efficient. Also, I have no idea how it
> compares in robustness.
> 
> Now, it may be that the cellular MAC's and PHY's
> need some retooling in the long run in which case
> ROHC will work better, but if they work like I
> think they do, it's going to be problematic in the
> intervening time.
> 
> 		Mike
> 


From owner-seamoby@diameter.org  Thu Mar 29 20:57:47 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA25127
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 20:57:46 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2TNrS405853
	for seamoby-list; Thu, 29 Mar 2001 15:53:28 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2TNrOF05848
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 15:53:24 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id PAA14680;
	Thu, 29 Mar 2001 15:02:28 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADF32227;
	Thu, 29 Mar 2001 15:02:22 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id PAA03731; Thu, 29 Mar 2001 15:02:22 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15043.48894.645943.523182@thomasm-u1.cisco.com>
Date: Thu, 29 Mar 2001 15:02:22 -0800 (PST)
To: "Dr. Carsten Bormann" <cabo@tzi.org>
Cc: "Michael Thomas" <mat@cisco.com>, <Hesham.Soliman@era.ericsson.se>,
        <mobile-ip@sunroof.eng.sun.com>, <rohc@cdt.luth.se>,
        <seamoby@diameter.org>, <zhigang.liu@nokia.com>
Subject: RE: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6 Handover
In-Reply-To: <NEBBJFHFCKHKFCNLJJBPKEKBEOAA.cabo@tzi.org>
References: <15043.34717.849084.517703@thomasm-u1.cisco.com>
	<NEBBJFHFCKHKFCNLJJBPKEKBEOAA.cabo@tzi.org>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dr. Carsten Bormann writes:
 > >  > (Side note: for hisorical and technical reasons, dealing with
 > >  > realtime VBR over radio links is much a headache than over wired
 > >  > links. )
 > >
 > >    A-ha! That's one of the reasons I question whether
 > >    ROHC is even appropriate on the air except in a
 > >    very small subset of cases (usually long lived streams
 > >    like RTP for which it was originally intended) As
 > >    a general purpose tunnel/header compressor, I suspect it is going
 > >    to have severe thrashing with the way that radio
 > >    resources are doled out by the AP.
 > 
 > I'm not sure why you are saying that (apart from the fact that we haven't
 > really done anything else but ROHC RTP yet).  How is ROHC worse than
 > uncompressed IP or 2507-compressed IP?

Carsten,

My understanding about cellular traffic channels
-- and I would be happy to find out differently --
is that they do not deal well with variable rate
traffic well. This is unsurprising since they are
heavily optimized for voice traffic which has very
regular periodicity and payload sizes. DOCSIS
cable is somewhat similar (with which I'm much
more familar), and the fixed size slots cause
variable rate coders like CRTP and ROHC much grief
because the MAC scheduler does not have the
ability to occassionally allow larger packets in
real time on an unsolicited grant SID; if you
start a session with packets every 20ms with 80
bytes of payload, that's exactly what you get. If
you occasionally need to send 81 bytes, you cannot
send it on that traffic channel.

This presents a real problem for CRTP and ROHC
when they need to send full headers or first order
changes.  For this reason, the cable folks perform
what they call Payload Header Suppression instead.
Basically, it's just a first order compressor
which is always on (sorry, if I've got your
nomenclature mixed up). This obviously works, but
is not as efficient. Also, I have no idea how it
compares in robustness.

Now, it may be that the cellular MAC's and PHY's
need some retooling in the long run in which case
ROHC will work better, but if they work like I
think they do, it's going to be problematic in the
intervening time.

		Mike


From owner-seamoby@diameter.org  Thu Mar 29 22:10:04 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA00437
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 22:10:03 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2U0v0u06032
	for seamoby-list; Thu, 29 Mar 2001 16:57:00 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2U0utF06027
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 16:56:55 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA24325
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 16:06:10 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA12142
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 16:06:09 -0800 (PST)
Received: from darius (darius [10.6.84.105])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id QAA20402
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 16:06:03 -0800 (PST)
Date: Thu, 29 Mar 2001 16:06:01 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: [seamoby] Seamoby Minutes - Please Review
To: seamoby@cdma-2000.org
Message-ID: <Roam.SIMC.2.0.6.985910761.30772.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

All,

Please review the following minutes, and provide comments by April 6th.

I'd like to thank La Monte again for the great minutes!

PatC
----

SEAMOBY Working Group Meeting at IETF50
Minneapolis, Minn.
March 21st, 2001


Minutes taken by La Monte H.P. Yarroll <piggy@acm.org>



AGENDA BASHING
1. Milestone review
2. Update on Paging Problem Statement
3. Update on Context Transfer Problem Statement
4. Update on Micro-Mobility Problem Statement
5. Update on any requirements work
6. Next Steps

No changes to Agenda.  Chair bashed the agenda physically



1. MILESTONE REVIEW
-- We're about 3 months behind original agenda
-- Paging completed WG last call and will go to IESG next week
-- Context transfer comments did come in--there will be another revision
   Significant comments were receive from WG Last Call, so need a new
   WG Last Call will be required. Design Team has started work on
   requirements.
-- MM-01 needs another revision
-- New goals and milestones will go to Secretariat next week.  Watch web site.



2. UPDATE ON PAGING, Jim Kempf

- Draft is complete, but some issues have been raised.
- Should the WG change its name to include paging?

Issue 1)
Some L2's have no paging support (no paging channel), and there doesn't seem
to be any benefit having a L3 paging protocol without any L2 support. The
conclusion is that paging is only needed when the network has a rough idea
of where the device is.

The group was asked whether the Design Team whether it is OK to assume
L2 paging for support of L3 paging?.  Consensus shows the group disagrees, and
L2 paging MUST NOT be assumed.

Issue 2)
There were some discussions on hypothetical L2s that do not support paging
mechanisms, and how they could be supported, but this is a difficult question
to answer, since we do not know what the future has in store for us.

Issue 3)
It was asked whether paging should only support Mobile IP, or some
other (yet undefined) micro-mobility protocol. The AD stated that it is too
early to answer this question at this time.

Jim detailed the process for the design team, which will be made
available on the mailing list. To subscribe to the list, see
www.diameter.org/seamoby.html.

Finally, Jim proposed a Design Team interim meeting in Menlo Park between
June 18th and the 20th, to discuss the requirements work. There is a process
involved in establishing an interim meeting, and the chair has the action item
to work this out with the Area Director. 

There were questions about whether a meeting was really necessary, and it
was noted that it helps get lots of work done in a short time frame. This is
important to Seamoby, given our aggressive deadlines.



3. UPDATE ON CONTEXT TRANSFER, Madjid Nakhjiri

The problem expressed is "In networks where hosts are mobile, the success
of real-time sensitive services like voice, video, etc. over IP networks
rests heavily the quality etc...

The things that Context Transfer operates on are properties (features)
and are measured as microflows. The state is held in what is called a
feature context. A feature context can be more general than just an
IP-layer feature (e.g. header compression).

The types of contexts mentioned in the problem statement Internet-Drafts
include Security, AAA, Header Compression state, Diffserv/Intserv, QOS
policy management, buffered data, sub network-layer state, and others. Note
that the list in the draft is not intended to be complete.

There were some comments on buffered data, which does not appear to be
a "feature", but this topic falls in the solution space, and was out of
scope for the meeting.

It was noted that the problem statements are just to establish the
assertion that there are problems that can be clearly described and
that it is worthwhile continuing the work.

There were comments from participants that context transfer should be done
for things other than mobility.



4. UPDATE ON MICRO MOBILITY, John Loughney

Prior to this discussion, the chair stated that there have been recent
developments on the charter, which will be discussed afterwards.

The problem statement expressed is "The general effort is to do as much
work locally to avoid having to cause effects deeper into the network." See
section 1.2 of the Micro-Mobility problem statement for more info.

The Design Team expressed the desire to create requirements, analyze solutions
and recommend a micro-mobility solution.

The goals of micro-mobility is to provide mobility w/o changing the mobile's
routable IP address. Reuse of Mobile IP WG protocols for mobility between
local mobility domains is also a goal. The work should be IP version neutral,
and scale well within the size of a local mobility domain.

There were some concerns in regards to how scalable a micro-mobility solution
could be, since it could be used across the Internet. This will be
addressed in the requirements phase.

The micro-mobility solution should be designed for inter-technology
heterogeneous networks, and use Mobile IP for signaling from the Mobile Node.
It should enable optionalized routing for mobile to mobile communication,
and not require triangular or trombone routing. The micro-mobility solution
should be optimized for bandwidth, provide user location confidentiality,
support connectivity to multiple AR's simultaneously and support simple
ad-hoc.

There was also a desire for this new solution to be "plug and play", but
this is out of the WG charter.

It was stated that it is very important for Mobile IP and the Seamoby MM
protocol to work together.
	  
The design team also listed the following drafts, which they
found informative for people interested in this space:
    - IPv6 MIP has many security requirements which are fulfilled by IPsec.
	-- draft-dupont-mipv6-aaa-00.txt
    - Mobile network support
	-- draft-ernst-mobileip-v6-network-01.txt
    - Mobility-aware IPsec ESP tunnels points out possible conflicts
      Mobility/Security.
	-- draft-dupont-movesptun-00.txt

It was stated that the Micro-Mobility and Context Transfer folks should
work together to make sure that their solution works together.



5. NEXT STEPS

The following points have been identified by the Micro-Mobility
design team:
	- There are MIP shortcomings for seamless hand-offs.
	- A possible new local edge mobility protocol.
	- Seamless hand-offs to access points that have the capabilities
	  required to support a given mobile.

After a meeting between the chair, ADs, and other interested parties, the
following actions will be taken:
	1) An I-D will be written that will describe the requirements
	   needed in the Mobile IP protocol to provide seamlessness. This
	   document will be sent to the Mobile IP WG.
	2) If the Design Team believes that a new routing protocol is
	   needed, the IRTF is very interested in taking over the work.
	3) The MM Design Team will write a requirements I-D for discovering
	   the best AP to hand-off a mobile to (e.g. CNP).

Item 1 is a short term work item that interested parties could work on, 
perhaps the design team itself, while item 3 would be the primary focus of
SEAMOBY.

There were some questions on whether context transfer and the new MM work
item are one and the same. These two items should be worked on separately.

There was some concern about seamoby writing a Mobile IP document, but
this document will only contain requirements, and will be given to the
Mobile IP WG to perform the necessary protocol enhancements.

The new work item (item 3) must work in conjunction with Mobile IP
fast hand-off, or any other future mobility protocol. There were also
some comments that selecting the right AP based on some properties, MAY
require that some non layer 3 criterias be used.

A question was raised on whether the paging work should take into
consideration the work that may be coming back from the IRTF, but
a well designed protocol should be designed to support a wide variety
of mobility protocols.

A context transfer question was raised about whether the context transfer
work should be applied to network failures [ed: read replication]. This
is outside the scope of the WG, but someone mentioned that one may end
up with a solution without trying.

There was also concern about the new discovery work in scenarios where 
L2 triggers are received after the hand-off occurs. This is an issue that
needs to be resolved by the WG.

Finally, a statement was made that someone didn't feel that consensus was
reached on whether there is a clean problem statement for paging.

The chair stated that the design teams are open to anyone, and the
mailing list information can be found at www.diameter.org/seamoby.html.




From owner-seamoby@diameter.org  Thu Mar 29 22:24:41 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA01761
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 22:24:41 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2U2RO606290
	for seamoby-list; Thu, 29 Mar 2001 18:27:24 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2U2RKF06285
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 18:27:20 -0800
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2U1abg19138
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 19:36:37 -0600 (CST)
Received: from daebh02nok.americas.nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T52984df7b0ac12f257079@davir04nok.americas.nokia.com>;
 Thu, 29 Mar 2001 19:36:04 -0600
Received: by daebh02nok with Internet Mail Service (5.5.2652.78)
	id <GKS5K18R>; Thu, 29 Mar 2001 19:36:04 -0600
Message-ID: <8572CF1E2A95D211A1190008C7EAA2460213BB7A@daeis05nok>
From: zhigang.liu@nokia.com
To: kempf@heliopolis.Eng.Sun.COM
Cc: mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se, seamoby@diameter.org
Subject: RE: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6
	  Handover
Date: Thu, 29 Mar 2001 19:36:03 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hi James,

Using the flow label (to identify a context) is certainly a good 
idea. I'm wondering if the ROHC CID (may need re-mapping during 
handover) can achieve the same goal. The former hinges on that the 
flow label is unique between the Access Router (AR) and the mobile 
node (MN) and remains constant when the MN attaches to a new AR 
(need re-negotiation if clashes with flow from other IP address?). 
The latter requires the mapping of old COA and the new one (details
unclear).

Somehow, I feel further thinking might be needed. On the other hand, 
they're not in conflict since the ROHC CID can be viewed as the 
result of hash function of the flow label. In addition, it could be 
a zero-bye CID (just for one flow) under the ROHC framework.

Br,
Zhigang

> -----Original Message-----
> From: ext James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
> Sent: Thursday, March 29, 2001 6:15 PM
> To: zhigang.liu@nokia.com
> Cc: mobile-ip@sunroof.eng.sun.com; rohc@cdt.luth.se;
> seamoby@diameter.org; zhigang.liu@nokia.com
> Subject: RE: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile
> IPv6 Handover
> 
> 
> Zhigang,
> 
> >IMHO, ROHC has done a good job to achieve both robustness and
> >efficiency. Let me rephrase Carsten's question this way: if 
> >ROHC is not "appropriate on the air", do you have better approaches
> >in mind?
> >
> 
> I agree that ROHC has done a good job and I don't want to imply by the
> following proposal that ROHC, perhaps modified to deal with context
> transfer and parameterized restart in IPv6, could not handle the
> problems with IPv6. This is just something I've been thinking about
> that might work if modifying ROHC is too difficult, or if the ROHC
> group has other priorities, like completing compression work on IPv4
> algorithms. Maybe it is completely unworkable in the end.
> 
> Assume that the Access Router and the mobile node could set up a 
> unique IPv6 flow label between them. This could also be done end to
> end with the corresponding node, if one wanted to preserve end to end
> semantics on the flow label.
> 
> Now, the Access Router can send exactly one packet with full header.
> The mobile node records the header and notes the flow label, as does
> the Access Router. After that, the Access Router strips the header and
> substitutes the flow label. Similarly in the uplink direction from
> the mobile node to the Access Router. If the flow label were 
> negotiated end to
> end, it might take more than one packet, but the negotiation only
> needs to be done once, and not every time the mobile node moves.
> 
> Since the flow label is 20 bits, the Access Router might want to hash
> the flow label to one byte rather than send the full flow 
> label across,
> since the Access Router knows the mobile node that is to get the flow.
> 
> When the mobile node moves to a new Access Router, the flow 
> label/header
> context is transferred via context transfer. The mobile node maintains
> the mapping. The new Access Router performs the same 
> stripping function, even 
> though the care of address has changed, as does the mobile node. 
> 
> Note that the compressor would still be needed for UDP/RTP headers.
> 
> If one doesn't want to use the flow label, a separately computed tag
> (like an MPLS label) could be used, based on the source address, but
> this would have to be recomputed if the corresponding node 
> were a mobile
> node and was changing its care of address. A flow label would remain
> constant.
> 
> Comments?
> 
> 		jak
> 


From owner-seamoby@diameter.org  Thu Mar 29 22:49:10 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA06273
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 22:49:09 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2U15o006073
	for seamoby-list; Thu, 29 Mar 2001 17:05:50 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2U15jF06068
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 17:05:46 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA27800;
	Thu, 29 Mar 2001 16:14:53 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA29791;
	Thu, 29 Mar 2001 16:14:52 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id QAA05556;
	Thu, 29 Mar 2001 16:14:52 -0800 (PST)
Message-Id: <200103300014.QAA05556@heliopolis.Eng.Sun.COM>
Date: Thu, 29 Mar 2001 16:14:52 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6  Handover
To: zhigang.liu@nokia.com
Cc: mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se, seamoby@diameter.org,
        zhigang.liu@nokia.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: WiAlF8F+JoX2JZd5z24fcQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Zhigang,

>IMHO, ROHC has done a good job to achieve both robustness and
>efficiency. Let me rephrase Carsten's question this way: if 
>ROHC is not "appropriate on the air", do you have better approaches
>in mind?
>

I agree that ROHC has done a good job and I don't want to imply by the
following proposal that ROHC, perhaps modified to deal with context
transfer and parameterized restart in IPv6, could not handle the
problems with IPv6. This is just something I've been thinking about
that might work if modifying ROHC is too difficult, or if the ROHC
group has other priorities, like completing compression work on IPv4
algorithms. Maybe it is completely unworkable in the end.

Assume that the Access Router and the mobile node could set up a 
unique IPv6 flow label between them. This could also be done end to
end with the corresponding node, if one wanted to preserve end to end
semantics on the flow label.

Now, the Access Router can send exactly one packet with full header.
The mobile node records the header and notes the flow label, as does
the Access Router. After that, the Access Router strips the header and
substitutes the flow label. Similarly in the uplink direction from
the mobile node to the Access Router. If the flow label were negotiated end to
end, it might take more than one packet, but the negotiation only
needs to be done once, and not every time the mobile node moves.

Since the flow label is 20 bits, the Access Router might want to hash
the flow label to one byte rather than send the full flow label across,
since the Access Router knows the mobile node that is to get the flow.

When the mobile node moves to a new Access Router, the flow label/header
context is transferred via context transfer. The mobile node maintains
the mapping. The new Access Router performs the same stripping function, even 
though the care of address has changed, as does the mobile node. 

Note that the compressor would still be needed for UDP/RTP headers.

If one doesn't want to use the flow label, a separately computed tag
(like an MPLS label) could be used, based on the source address, but
this would have to be recomputed if the corresponding node were a mobile
node and was changing its care of address. A flow label would remain
constant.

Comments?

		jak



From owner-seamoby@diameter.org  Thu Mar 29 23:15:49 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA08829
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 23:15:48 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2U2Chm06242
	for seamoby-list; Thu, 29 Mar 2001 18:12:43 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2U2CcF06237
	for <seamoby@diameter.org>; Thu, 29 Mar 2001 18:12:38 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id RAA22517;
	Thu, 29 Mar 2001 17:21:47 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f2U1LjT05305;
	Thu, 29 Mar 2001 17:21:45 -0800
X-mProtect:  Thu, 29 Mar 2001 17:21:45 -0800 Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14166.americas.nokia.com (172.18.141.66, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdpiGLCd; Thu, 29 Mar 2001 17:21:23 PST
Message-ID: <3AC3DF76.E6DA14D4@iprg.nokia.com>
Date: Thu, 29 Mar 2001 17:20:54 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Reply-To: Rajeev.Koodli@nokia.com
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Dr. Carsten Bormann" <cabo@tzi.org>
CC: rajeev.koodli@nokia.com, Hesham.Soliman@era.ericsson.se,
        zhigang.liu@nokia.com, mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se,
        seamoby@diameter.org
Subject: Re: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6 
 Handover
References: <NEBBJFHFCKHKFCNLJJBPAEKBEOAA.cabo@tzi.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello Carsten,


"Dr. Carsten Bormann" wrote:

> > Well, I think header compression context relocation is doable in
> > seamoby. We
> > need some help from rohc in defining what a context is, say e.g.,
> > IPv6/UDP/RTP/voice-G.723.1.
>
> Rajeev,
>
> while this is only a rough overview of the information set, you might want
> to start with section 6.5 of the ROHC RTP document.  I tend to believe that
> for most applications, just transferring the static chain will be fine,
> though; this is resilient to race conditions and can simply use the data
> format already defined in section 5.7.7.
>

Ok. I agree this is a good start.

Regards,

-Rajeev



>
> One thing that needs to be defined as well is the signaling between the old
> compressor and the new decompressor (and v.v.) so they know context transfer
> is in use and contexts have been successfully transferred.  This may be
> implicit in the handover or explicitly signalled *).  This signalling may
> also be a good place to fix the apparent deficiency in ROHC that there is no
> good way to update an address in the outermost IP header (needed for Mobile
> IPv6).

> *) ROHCers: maybe we need to reserve some bit combinations for ROHC-over-X
> signalling...
>
> Gruesse, Carsten



From owner-seamoby@diameter.org  Thu Mar 29 23:54:49 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA12591
	for <seamoby-archive@odin.ietf.org>; Thu, 29 Mar 2001 23:54:48 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2U3Fqs06407
	for seamoby-list; Thu, 29 Mar 2001 19:15:52 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2U3EXF06402
	for <seamoby@cdma-2000.org>; Thu, 29 Mar 2001 19:14:33 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4S6MY>; Thu, 29 Mar 2001 21:23:48 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2AAB@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>, acasati@lucent.com,
        pcalhoun@nasnfs.eng.sun.com,
        Kulwinder Atwal
	 <kulwinder.atwal@zucotto.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] To page, or not to page
Date: Thu, 29 Mar 2001 21:23:41 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
> Sent: Thursday, March 29, 2001 5:28 PM
> To: acasati@lucent.com; pcalhoun@nasnfs.eng.sun.com;
> kempf@heliopolis.Eng.Sun.COM; kulwinder.atwal@zucotto.com
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] To page, or not to page
> 
> 
> Kulwinder,
> 
> 
> >First, I agree that a paging protocol is not neccesary.
> >
> >What I was suggesting is:
> >
> >1. Timely Message enters Paging Area.
> >2. An AR takes Message places it in a Multicast packet 
> destined for all
> >AP/ARs in the Paging Area.
> >3. Upon an AP/AR recieving the Multicast packet it removes 
> the unicast
> >message and sends it over the air to the one intended Mobile. 
> >
> 
> What you have defined here is a paging protocol, regardless
> of whether there are special messages or not. Also, it may not
> be sufficient for all radio L2, IHMO.

Creation is not endorsement.  I still don't think it is a _neccesary_
protocol.  A router based location update protocol, I believe is a
_necessary_ protocol.  If a Paging protocol is meant to serve as a drop-in
replacement in a leagacy GSM system it should be stated as a requirement.

- Kulwinder.

> 
> 
> 		jak
> 
> 


From owner-seamoby@diameter.org  Fri Mar 30 04:08:41 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA25962
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 04:08:41 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2U8FhE07104
	for seamoby-list; Fri, 30 Mar 2001 00:15:43 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2U8EIF07099
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 00:14:19 -0800
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f2U7NWs01766
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 09:23:33 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Fri Mar 30 09:23:31 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <G9XA839P>; Fri, 30 Mar 2001 09:19:00 +0200
Message-ID: <A943FD84BD9ED41193460008C7918050017AF96B@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'rajeev.koodli@nokia.com'" <rajeev.koodli@nokia.com>,
        zhigang.liu@nokia.com,
        "Lars-Erik Jonsson (EPL)"
	 <Lars-Erik.Jonsson@epl.ericsson.se>,
        micke@CS.Arizona.EDU, mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se,
        seamoby@cdma-2000.org
Subject: [seamoby] RE: [rohc] Compression startup behavior
Date: Fri, 30 Mar 2001 09:23:13 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Sorry that I forgot to say "unfortunately" in the beginning of the sentence below...

Anyway, I do not care if someone wants to do context transfer as part of the handover procedures used for certain environments. Personally, I think it is overkill and makes things more complicated, but that is not up to me to judge. However, it is not a header compression issue.

/L-E


> > > I guess that context transfer is a mechanism 
> > > that will be developed (snip)
> > 
>     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> This is a good starting position.
> 
> Regards,
> 
> -Rajeev


From owner-seamoby@diameter.org  Fri Mar 30 04:10:15 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA25963
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 04:08:41 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2U8A5i07067
	for seamoby-list; Fri, 30 Mar 2001 00:10:05 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2U88kF07062
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 00:08:46 -0800
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f2U7I1I06029
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 09:18:01 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Fri Mar 30 09:17:44 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <G9WJCLN8>; Fri, 30 Mar 2001 09:17:45 +0200
Message-ID: <A943FD84BD9ED41193460008C7918050017AF96A@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'zhigang.liu@nokia.com'" <zhigang.liu@nokia.com>,
        "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
Cc: mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se, seamoby@diameter.org
Subject: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6 Handover
Date: Fri, 30 Mar 2001 09:17:37 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

> In fact, people in ROHC
> WG haven't spent much time debating on this because we didn't
> want this debate to delay the delivery of the basic ROHC (we
> had a very tight schedule).

To be honest, we defined what is included in the context with the purpose to make context transfer easier. However, since context transfer is out of scope for header compression development (more of an issue for the environment where header compression is implemented), we did not do it in ROHC. It must be up to those implementing header compression in various environments to decide if it makes sense to them or not and, if it is desirable, to define how it should be done there.


/L-E


From owner-seamoby@diameter.org  Fri Mar 30 04:48:57 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA00508
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 04:48:56 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2U8pQ007190
	for seamoby-list; Fri, 30 Mar 2001 00:51:26 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2U8o6F07185
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 00:50:06 -0800
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f2U7xLI13861
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 09:59:21 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Fri Mar 30 09:59:12 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <G9WJCN95>; Fri, 30 Mar 2001 09:59:13 +0200
Message-ID: <A943FD84BD9ED41193460008C7918050017AF96E@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Michael Thomas'" <mat@cisco.com>
Cc: rohc@cdt.luth.se, seamoby@diameter.org
Subject: RE: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6
	 Handover
Date: Fri, 30 Mar 2001 09:59:11 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

Michael,

> My understanding about cellular traffic channels
> -- and I would be happy to find out differently --
> is that they do not deal well with variable rate
> traffic well. This is unsurprising since they are
> heavily optimized for voice traffic which has very
> regular periodicity and payload sizes. 

This basically means that these links are not that capable of handling IP traffic. I think it is better to say that these links are not that good at utilizing the advantages of header compression, than to say that there are problems with header compression since not all compressed headers have a small, fixed size. The default headers are the uncompressed headers and with header compression most of them are almost completely removed, but not all of them because of natural causes. You must be prepared to pay the price, nothing is for free.

> Now, it may be that the cellular MAC's and PHY's
> need some retooling in the long run in which case
> ROHC will work better,

I agree with you that future cellular link technologies must be better at handling real general data traffic (including speech traffic as one kind of data). 


/L-E


From owner-seamoby@diameter.org  Fri Mar 30 08:02:56 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA12724
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 08:02:56 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UCD2O07832
	for seamoby-list; Fri, 30 Mar 2001 04:13:02 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UCBgF07827
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 04:11:43 -0800
Received: from ihemail2.firewall.lucent.com (localhost [127.0.0.1])
	by ihemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id GAA14576
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 06:20:59 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-160-150.lucent.com [135.86.160.150])
	by ihemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id GAA14560
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 06:20:58 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2650.21)
	id <HYP1GJ63>; Fri, 30 Mar 2001 12:20:58 +0100
Message-ID: <976F7C55E3B2D111A0720008C728549C097CC2A4@en0060exch001u.uk.lucent.com>
From: "Casati, Alessio (Alessio)" <acasati@lucent.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        pcalhoun@nasnfs.eng.sun.com,
        "Casati, Alessio (Alessio)"
	 <acasati@lucent.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] To page, or not to page
Date: Fri, 30 Mar 2001 12:20:52 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk



You are talking here about what goes over the air, correct? That is only
one small part of what is needed for paging.

Maybe it is a small part of what is needed to send data to the MN

If the L2 paging protocol is used over the air, then all  that is needed
is for a wired backbone protocol to handle location updating when
the mobile goes into dormant mode and crosses paging area boundaries,
and to trigger a page when a packet comes in. As you indicate, it
will need to be integrated with mobile IP, but it should not be
bound exclusively to mobile IP because the IRTF will be working on
a micromobility routing protocol and the wired backbone part may
be useful for that as well. 


But there is a disconnect here: if the mobile goes dormant, no way you can
do
a L3 thing, whatever you could do is a L2/L3 coordination. as such, this
becomes
a technology dependent work. 

And, I think we should also be clear that something in addition to mobile IP
as 
it exists today is needed. The way 3GPP2 handles mobile IP location updating
for
dormant mode mobiles today is the mobile comes out of dormant mode,
brings up a traffic channel, does a mobile IP registration, and goes
back into dormant mode. This is not very efficient.


 it depends on what you want to do. If you do that to handle the 
100m coverage radius antennas in licenced spectrum, that may be a problem.
If it is only
for inter RAN handoff, it may not be a problem, depending on the size of the
RAN.

Of course, this is all implementation. The requirements that would come
out of this are:

	The IP paging protocol shall be efficient with respect to
	mobile power use.
	
The requirement should be: the IP location update protocol
shall be efficient with respect to mobile Power use.

	The IP paging protocol shall be designed to allow a binding
	with mobility protocols for location update purposes, including
	mobile IP.
	
That is acceptable, but I dont see the need for a paging protocol. Just send
data.
the APs where the MN is not attached, will drop packet, and you are set.

	The IP paging protocol shall utiliize L2 paging support if
	available, but shall not require such support.

This is a seamoby centric view of the world... No matter what,
you will do what the L2 is expected to work. More acceptable statement
would be " the protocol location update protocol shall work withhout
requiring
L2 operation changes" Or something along the lines of this.

>as such, I'd support to take a step back and
>re-consider the soundness of the reqs (OK, the IESG may do that instead,
>if we want an analogy with what has happened with MIPv6 ;).

Actually, Alissio, that is precisely what we are doing. If you have
some requirements you would like to propose, please, by all means,
propose them.

The requirement on the paging protocol I have are Non existent, consistently
with the fact that I do not recognize the need for such protocol.
That req document is not really a requirement document, it is a document
saying "we require paging, and here is why". However it steers clear from
defining
what paging is... Not much agreeable. It is a metarequirement documet on
some
Yet to be defined or conceived thing. 

>Also, maybe what I described now cannot quite be defined as paging
>(although I truly believe paging may gain more cookie points,
>in a marketing setting).
>

IS-41 has messages associated with paging and it goes over the SS7 backbone.
So I don't see any problem calling support for paging in the wired
network as paging. Paging isn't only about what goes over the air, IMHO.

In my opinon, paging is over the air, the rest is call set-up or
session managenet, or user traffic...


regards.


alessio
	


From owner-seamoby@diameter.org  Fri Mar 30 10:08:37 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA19582
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 10:08:37 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UEWXC08185
	for seamoby-list; Fri, 30 Mar 2001 06:32:33 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from nmh.informatik.uni-bremen.de (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UEVDF08180
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 06:31:13 -0800
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id f2UDe4G03603;
	Fri, 30 Mar 2001 15:40:04 +0200 (MEST)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Lars-Erik Jonsson \(EPL\)" <Lars-Erik.Jonsson@epl.ericsson.se>,
        "'Michael Thomas'" <mat@cisco.com>
Cc: <rohc@cdt.luth.se>, <seamoby@diameter.org>
Subject: RE: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6 Handover
Date: Fri, 30 Mar 2001 15:40:01 +0200
Message-ID: <NEBBJFHFCKHKFCNLJJBPOEMLEOAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <A943FD84BD9ED41193460008C7918050017AF96E@ESEALNT419.al.sw.ericsson.se>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > My understanding about cellular traffic channels
> > -- and I would be happy to find out differently --
> > is that they do not deal well with variable rate
> > traffic well. This is unsurprising since they are
> > heavily optimized for voice traffic which has very
> > regular periodicity and payload sizes.
>
> This basically means that these links are not that capable of
> handling IP traffic.

Actually, they are.  They are just not good at handling traffic whose
payload already maxes out the link.

If the objective is to use only exactly as much capacity as is needed for
the payload, my humble advice would be not to run IP over the link.

(Oh, and one aspect often forgotten about wireless links is that you can
often play with the channel coding.  This gives you *some* form of VBR --
combined with variable BER, unfortunately.)

Gruesse, Carsten



From owner-seamoby@diameter.org  Fri Mar 30 11:42:53 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA24944
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 11:42:52 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UFdu508364
	for seamoby-list; Fri, 30 Mar 2001 07:39:56 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UFdqF08359
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 07:39:52 -0800
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Fri, 30 Mar 2001 09:28:42 -0500
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <HSTBXZ85>; Fri, 30 Mar 2001 09:28:43 -0500
Message-ID: <13E2EF604DE5D111B2E50000F80824E8057A8E90@zwdld001.ca.nortel.com>
From: "Gary Kenward" <gkenward@nortelnetworks.com>
To: "'Patrice Calhoun'" <pcalhoun@nasnfs.eng.sun.com>, seamoby@cdma-2000.org
Subject: RE: [seamoby] Seamoby Minutes - Please Review
Date: Fri, 30 Mar 2001 09:28:38 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0B925.B5BDFEB0"
X-Orig: <gkenward@americasm01.nt.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0B925.B5BDFEB0
Content-Type: text/plain;
	charset="iso-8859-1"

One comment:

> -----Original Message-----
> From: Patrice Calhoun [mailto:pcalhoun@nasnfs.eng.sun.com]
> Sent: Thursday, March 29, 2001 7:06 PM
> To: seamoby@cdma-2000.org
> Subject: [seamoby] Seamoby Minutes - Please Review
> 
> 
> All,
> 
> Please review the following minutes, and provide comments by 
> April 6th.
> 
> I'd like to thank La Monte again for the great minutes!
> 
> PatC
> ----
> 
> SEAMOBY Working Group Meeting at IETF50
> Minneapolis, Minn.
> March 21st, 2001
> 
> 
> Minutes taken by La Monte H.P. Yarroll <piggy@acm.org>
>
*snip*

> 
> 4. UPDATE ON MICRO MOBILITY, John Loughney
> 

*snip*

> 
> There were some concerns in regards to how scalable a 
> micro-mobility solution
> could be, since it could be used across the Internet. This will be
> addressed in the requirements phase.

This seems to be the major objection against at least some of the
concepts proposed. And yet, doesn't "micro-mobility across the 
(global) Internet" sound like an oxymoron?

Does every solution have to scale globally? In truth, I think not,
and there must be many examples of local solutions that are used
all over the globe, but do not scale to a global service.

*snip*

Gary

------_=_NextPart_001_01C0B925.B5BDFEB0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>RE: [seamoby] Seamoby Minutes - Please Review</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>One comment:</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: Patrice Calhoun [<A HREF="mailto:pcalhoun@nasnfs.eng.sun.com">mailto:pcalhoun@nasnfs.eng.sun.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Thursday, March 29, 2001 7:06 PM</FONT>
<BR><FONT SIZE=2>&gt; To: seamoby@cdma-2000.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: [seamoby] Seamoby Minutes - Please Review</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; All,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Please review the following minutes, and provide comments by </FONT>
<BR><FONT SIZE=2>&gt; April 6th.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I'd like to thank La Monte again for the great minutes!</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; PatC</FONT>
<BR><FONT SIZE=2>&gt; ----</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; SEAMOBY Working Group Meeting at IETF50</FONT>
<BR><FONT SIZE=2>&gt; Minneapolis, Minn.</FONT>
<BR><FONT SIZE=2>&gt; March 21st, 2001</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Minutes taken by La Monte H.P. Yarroll &lt;piggy@acm.org&gt;</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>*snip*</FONT>
</P>

<P><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; 4. UPDATE ON MICRO MOBILITY, John Loughney</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

<P><FONT SIZE=2>*snip*</FONT>
</P>

<P><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; There were some concerns in regards to how scalable a </FONT>
<BR><FONT SIZE=2>&gt; micro-mobility solution</FONT>
<BR><FONT SIZE=2>&gt; could be, since it could be used across the Internet. This will be</FONT>
<BR><FONT SIZE=2>&gt; addressed in the requirements phase.</FONT>
</P>

<P><FONT SIZE=2>This seems to be the major objection against at least some of the</FONT>
<BR><FONT SIZE=2>concepts proposed. And yet, doesn't &quot;micro-mobility across the </FONT>
<BR><FONT SIZE=2>(global) Internet&quot; sound like an oxymoron?</FONT>
</P>

<P><FONT SIZE=2>Does every solution have to scale globally? In truth, I think not,</FONT>
<BR><FONT SIZE=2>and there must be many examples of local solutions that are used</FONT>
<BR><FONT SIZE=2>all over the globe, but do not scale to a global service.</FONT>
</P>

<P><FONT SIZE=2>*snip*</FONT>
</P>

<P><FONT SIZE=2>Gary</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0B925.B5BDFEB0--


From owner-seamoby@diameter.org  Fri Mar 30 11:58:34 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA25935
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 11:58:34 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UFwAE08411
	for seamoby-list; Fri, 30 Mar 2001 07:58:10 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UFw5F08406
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 07:58:05 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA27895;
	Fri, 30 Mar 2001 07:06:46 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA13067;
	Fri, 30 Mar 2001 07:06:45 -0800 (PST)
Received: from darius (darius [10.6.84.105])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id HAA26580;
	Fri, 30 Mar 2001 07:06:43 -0800 (PST)
Date: Fri, 30 Mar 2001 07:06:40 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: RE: [seamoby] Seamoby Minutes - Please Review
To: Gary Kenward <gkenward@nortelnetworks.com>
Cc: "'Patrice Calhoun'" <pcalhoun@nasnfs.eng.sun.com>, seamoby@cdma-2000.org
In-Reply-To: "Your message with ID" <13E2EF604DE5D111B2E50000F80824E8057A8E90@zwdld001.ca.nortel.com>
Message-ID: <Roam.SIMC.2.0.6.985964800.17444.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk


> This seems to be the major objection against at least some of the
> concepts proposed. And yet, doesn't "micro-mobility across the 
> (global) Internet" sound like an oxymoron?
> 
> Does every solution have to scale globally? In truth, I think not,
> and there must be many examples of local solutions that are used
> all over the globe, but do not scale to a global service.

Well, the reality is that a protocol can often be mis-used. However, I am
quite certain that operators are quite a bit smarter than that, and would make
sure that no "host routes" pollute the backbone.

Having said that, this particular work item is being transfered to the IRTF,
so we can let them worry about this one.

Thanks for reading over the minutes,

PatC



From owner-seamoby@diameter.org  Fri Mar 30 12:39:36 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA28347
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 12:39:36 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UGRZ008519
	for seamoby-list; Fri, 30 Mar 2001 08:27:35 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UGRVF08514
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 08:27:31 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id HAA01179;
	Fri, 30 Mar 2001 07:36:46 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADG10382;
	Fri, 30 Mar 2001 07:36:40 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id HAA03988; Fri, 30 Mar 2001 07:36:40 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15044.43016.54843.820068@thomasm-u1.cisco.com>
Date: Fri, 30 Mar 2001 07:36:40 -0800 (PST)
To: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
Cc: "'Michael Thomas'" <mat@cisco.com>, rohc@cdt.luth.se, seamoby@diameter.org
Subject: RE: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6
	 Handover
In-Reply-To: <A943FD84BD9ED41193460008C7918050017AF96E@ESEALNT419.al.sw.ericsson.se>
References: <A943FD84BD9ED41193460008C7918050017AF96E@ESEALNT419.al.sw.ericsson.se>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Lars-Erik Jonsson (EPL) writes:
 > Michael,
 > 
 > > My understanding about cellular traffic channels
 > > -- and I would be happy to find out differently --
 > > is that they do not deal well with variable rate
 > > traffic well. This is unsurprising since they are
 > > heavily optimized for voice traffic which has very
 > > regular periodicity and payload sizes. 
 > 
 > This basically means that these links are not that capable of
> handling IP traffic.

  Ah, I can see how you drew that inference :-) What
  I meant is that they have problems with real time,
  periodic fixed sized flows like VoIP. Obviously,
  queuing solves the problem with bursty, best effort
  traffic.

>  I think it is better to say that these links are not that good at
utilizing the advantages of header compression, than to say that there
are problems with header compression since not all compressed headers
have a small, fixed size. The default headers are the uncompressed
headers and with header compression most of them are almost completely
removed, but not all of them because of natural causes. You must be
prepared to pay the price, nothing is for free.

  It's hard to assign blame here: the two things were
  optimized for two entirely different purposes. What
  we are left with is not an entirely great fit.

 > > Now, it may be that the cellular MAC's and PHY's
 > > need some retooling in the long run in which case
 > > ROHC will work better,
 > 
 > I agree with you that future cellular link technologies must be better at handling real general data traffic (including speech traffic as one kind of data). 

   I'd love to see a centralized schedular that handles
   variable rate data better but doesn't chew up lots
   of bandwidth. Fundamentally, these two design criteria
   are at odds with each other though.

       Mike


From owner-seamoby@diameter.org  Fri Mar 30 12:47:06 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA29001
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 12:47:05 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UH6AE08633
	for seamoby-list; Fri, 30 Mar 2001 09:06:10 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UH66F08628
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 09:06:06 -0800
Received: from davir03nok.americas.nokia.com (davir03nok.americas.nokia.com [172.18.242.86])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2UGFQg22426
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 10:15:26 -0600 (CST)
Received: from daebh01nok.americas.nokia.com (unverified) by davir03nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T529b727fbdac12f256079@davir03nok.americas.nokia.com>;
 Fri, 30 Mar 2001 10:14:50 -0600
Received: by daebh01nok with Internet Mail Service (5.5.2652.78)
	id <H8771NL3>; Fri, 30 Mar 2001 10:14:50 -0600
Message-ID: <8572CF1E2A95D211A1190008C7EAA2460213BB7C@daeis05nok>
From: zhigang.liu@nokia.com
To: Lars-Erik.Jonsson@epl.ericsson.se, rajeev.koodli@nokia.com,
        micke@CS.Arizona.EDU, mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se,
        seamoby@cdma-2000.org
Subject: [seamoby] RE: [rohc] Compression startup behavior
Date: Fri, 30 Mar 2001 10:14:49 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

> However, it is not a header compression issue.
> 
> /L-E

Sorry, I still don't get it after the statement has been 
repeated many times (both this and last year). Do you mean 
that the logic (e.g. not sending IR packets to reestablish
context over the air after receiving context from the old
compressor) is not a header compression issue?

Br,
Zhigang


From owner-seamoby@diameter.org  Fri Mar 30 13:05:42 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00635
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 13:05:41 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UHWoG08736
	for seamoby-list; Fri, 30 Mar 2001 09:32:50 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UHVcF08725;
	Fri, 30 Mar 2001 09:31:39 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA06814;
	Fri, 30 Mar 2001 08:40:54 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA18480;
	Fri, 30 Mar 2001 08:40:52 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id IAA17195;
	Fri, 30 Mar 2001 08:40:52 -0800 (PST)
Message-Id: <200103301640.IAA17195@heliopolis.Eng.Sun.COM>
Date: Fri, 30 Mar 2001 08:40:52 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: [seamoby] Paging or Not
To: seamoby@diameter.org, seamoby-paging@diameter.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: whvrY0hch1bUlQlPx3tsmg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Pat/Allison/All,

Behcet, the design team members, and I have committed ourselves to working
fairly intensively on the paging problem over the next months until
IETF 51. Recently, there has been some email about whether or not
paging should even be considered by IETF. I had thought that we
were beyond this point. This was in response to Pat's email of
a few days ago.

The conclusion of the design team, which I presented at IETF 50, was
that there is a problem to be solved. It is not unsolvable by
using mobile IP, but the solution is difficult.

Frankly, I am not about to spend the next 4 months waging an email battle
with bomb throwers who want to derail progress. If we
don't have agreement on doing requirements, I would like to suggest
we can this activity right now. I've got plenty of other things I could
be spending time on, and I'm sure the other paging design team
members feel the same.

Are we going forward with requirements on paging or not?

		jak




From owner-seamoby@diameter.org  Fri Mar 30 13:10:09 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00955
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 13:10:09 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UHQMh08696
	for seamoby-list; Fri, 30 Mar 2001 09:26:22 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UHQIF08691
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 09:26:18 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id IAA11586;
	Fri, 30 Mar 2001 08:15:55 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADG10947;
	Fri, 30 Mar 2001 08:15:50 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id IAA03999; Fri, 30 Mar 2001 08:15:50 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15044.45365.844598.739112@thomasm-u1.cisco.com>
Date: Fri, 30 Mar 2001 08:15:49 -0800 (PST)
To: "Gary Kenward" <gkenward@nortelnetworks.com>
Cc: "'Patrice Calhoun'" <pcalhoun@nasnfs.eng.sun.com>, seamoby@cdma-2000.org
Subject: RE: [seamoby] Seamoby Minutes - Please Review
In-Reply-To: <13E2EF604DE5D111B2E50000F80824E8057A8E90@zwdld001.ca.nortel.com>
References: <13E2EF604DE5D111B2E50000F80824E8057A8E90@zwdld001.ca.nortel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Gary Kenward writes:
 > > There were some concerns in regards to how scalable a 
 > > micro-mobility solution
 > > could be, since it could be used across the Internet. This will be
 > > addressed in the requirements phase.
 > 
 > This seems to be the major objection against at least some of the
 > concepts proposed. And yet, doesn't "micro-mobility across the 
 > (global) Internet" sound like an oxymoron?

   Yes. And a strawman too boot, because nobody's
   been claiming it should.

 > Does every solution have to scale globally? In truth, I think not,
 > and there must be many examples of local solutions that are used
 > all over the globe, but do not scale to a global service.

   Even routing makes a distinction between interior
   and exterior to autonomous systems. MM is nothing
   but another twist on an IGP.

	 Mike


From owner-seamoby@diameter.org  Fri Mar 30 13:12:50 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA01236
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 13:12:50 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UGobD08599
	for seamoby-list; Fri, 30 Mar 2001 08:50:37 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UGoXF08594
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 08:50:33 -0800
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2UFxrg20425
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 09:59:53 -0600 (CST)
Received: from daebh02nok.americas.nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T529b644192ac12f255079@davir02nok.americas.nokia.com>;
 Fri, 30 Mar 2001 09:59:17 -0600
Received: by daebh02nok with Internet Mail Service (5.5.2652.78)
	id <H88RY198>; Fri, 30 Mar 2001 09:59:17 -0600
Message-ID: <8572CF1E2A95D211A1190008C7EAA2460213BB7B@daeis05nok>
From: zhigang.liu@nokia.com
To: Lars-Erik.Jonsson@epl.ericsson.se, Hesham.Soliman@era.ericsson.se
Cc: mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se, seamoby@diameter.org
Subject: [seamoby] RE: [rohc] RE: Restarting Compressor on Mobile IPv6 Handover
Date: Fri, 30 Mar 2001 09:59:13 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

> However, since 
> context transfer is out of scope for header compression 
> development (snip)
>  
> /L-E

Why do you say that? Context transfer requires some new
signaling between the new and old compressor (decompressor).
The logic of ROHC also needs to be amended. Do you think
all of those should not be part of the protocol and just
an implementation issue? How about interoperability?

(The emails from other people seems indicating just the opposite.)

Zhigang


From owner-seamoby@diameter.org  Fri Mar 30 14:12:13 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA06290
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 14:12:12 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UHQaT08703
	for seamoby-list; Fri, 30 Mar 2001 09:26:36 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UHQWF08698
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 09:26:33 -0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA20248;
	Fri, 30 Mar 2001 08:35:48 -0800 (PST)
Received: from heliopolis.Eng.Sun.COM (heliopolis.Eng.Sun.COM [152.70.1.39])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA16681;
	Fri, 30 Mar 2001 08:32:47 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id IAA17009;
	Fri, 30 Mar 2001 08:32:47 -0800 (PST)
Message-Id: <200103301632.IAA17009@heliopolis.Eng.Sun.COM>
Date: Fri, 30 Mar 2001 08:32:47 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: RE: [seamoby] To page, or not to page
To: kempf@heliopolis.Eng.Sun.COM, pcalhoun@nasnfs.eng.sun.com,
        acasati@lucent.com
Cc: seamoby@cdma-2000.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: A41GjopdGoJR2ld6TYbIVw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-seamoby@diameter.org
Precedence: bulk

Alessio,


>But there is a disconnect here: if the mobile goes dormant, no way you can
>do
>a L3 thing, whatever you could do is a L2/L3 coordination. as such, this
>becomes
>a technology dependent work. 
>

There are a number of ways to handle this. The mobile node could
explicitly signal at L3 when it goes dormant. A timer in the network
could go off if the mobile doesn't periodically report, and send
an L3 message to the tracking agent. Neither of these involve
dependence on explicit L2, though they may involve an abstract L2
trigger (for example, a trigger on the mobile node that it is about
to go dormant).

	
>The requirement should be: the IP location update protocol
>shall be efficient with respect to mobile Power use.
>

We can get into splitting hairs here about what we call it, but
I think there is broad concensus in the working group to call it paging.

	
>That is acceptable, but I dont see the need for a paging protocol. Just send
>data.
>the APs where the MN is not attached, will drop packet, and you are set.
>

So you want to handle a defect in the routing protocol by falling
back on TCP retransmission, or, if TCP isn't used, whatever application
specific UDP retransmit protocol happens to be there? IHMO, it is
poor design practice to depend on error mechanisms to handle the
a defect in the routing design.


>This is a seamoby centric view of the world... No matter what,
>you will do what the L2 is expected to work. More acceptable statement
>would be " the protocol location update protocol shall work withhout
>requiring
>L2 operation changes" Or something along the lines of this.
>

Well, Alissio, this *does* happen to be the Seamoby working group,
at least last time I checked. We cannot, in any event, expect any
changes in L2, through we can recommend how to make future L2s
more friendly to IP. The intent here is, as with the fast handoff
work, to figure out some abstract properties of L2 paging that
are shared with a broad variety of implementations. Like paging
areas, for example. And we can then design the L3 protocol such
that, if such support is available, it gets used. 

IPv6 does this with minimum frame size. There is a minimum specified
frame size for L2 in IPv6. If L2 doesn't support it, the driver writer
must write a shim layer that does segmentation and reassembly.

>The requirement on the paging protocol I have are Non existent, consistently
>with the fact that I do not recognize the need for such protocol.
>That req document is not really a requirement document, it is a document
>saying "we require paging, and here is why". However it steers clear from
>defining
>what paging is... Not much agreeable. It is a metarequirement documet on
>some
>Yet to be defined or conceived thing. 
>

May I quote from Section 2.0 of 
draft-ietf-seamoby-paging-problem-statement-02.txt:

      Paging - As a consequence of a mobile-bound packet destined for a
      mobile currently in dormant mode, signaling by the network through
      radio access points directed to locating the mobile and
      establishing a last hop connection. This messaging is in addition
      to simply delivering the packet to the mobile, i.e. last hop
      routing of packets is NOT considered to be paging.
      
This is our definition of paging. I suggest, if you want to throw bombs,
you take it up with the IESG.  

>In my opinon, paging is over the air, the rest is call set-up or
>session managenet, or user traffic...

Position noted. Now, let's get on with the business of defining
requirements.

		jak



From owner-seamoby@diameter.org  Fri Mar 30 15:56:12 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA13762
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 15:56:11 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UJPBn09017
	for seamoby-list; Fri, 30 Mar 2001 11:25:11 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from auemlsrv.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UJP6F09012
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 11:25:07 -0800
Received: from auemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id NAA03110
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 13:34:24 -0500 (EST)
Received: from uk0006exch001h.wins.lucent.com (h135-86-160-150.lucent.com [135.86.160.150])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id NAA03087
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 13:34:23 -0500 (EST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2650.21)
	id <HYP1G6VW>; Fri, 30 Mar 2001 19:34:22 +0100
Message-ID: <976F7C55E3B2D111A0720008C728549C097CC2AA@en0060exch001u.uk.lucent.com>
From: "Casati, Alessio (Alessio)" <acasati@lucent.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        pcalhoun@nasnfs.eng.sun.com,
        "Casati, Alessio (Alessio)"
	 <acasati@lucent.com>
Cc: seamoby@cdma-2000.org
Subject: RE: [seamoby] To page, or not to page
Date: Fri, 30 Mar 2001 19:34:21 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-seamoby@diameter.org
Precedence: bulk



>But there is a disconnect here: if the mobile goes dormant, no way you can
>do
>a L3 thing, whatever you could do is a L2/L3 coordination. as such, this
>becomes
>a technology dependent work. 
>

There are a number of ways to handle this. The mobile node could
explicitly signal at L3 when it goes dormant. A timer in the network
could go off if the mobile doesn't periodically report, and send
an L3 message to the tracking agent. Neither of these involve
dependence on explicit L2, though they may involve an abstract L2
trigger (for example, a trigger on the mobile node that it is about
to go dormant).

Right, I think mobile IP can do this... Before you go to sleep, send an
update.
	
>The requirement should be: the IP location update protocol
>shall be efficient with respect to mobile Power use.
>

We can get into splitting hairs here about what we call it, but
I think there is broad concensus in the working group to call it paging.


I'd suggest there is quite a difference between location update
and paging. It is not splitting Hairs.


	
>That is acceptable, but I dont see the need for a paging protocol. Just
send
>data.
>the APs where the MN is not attached, will drop packet, and you are set.
>

So you want to handle a defect in the routing protocol by falling
back on TCP retransmission, or, if TCP isn't used, whatever application
specific UDP retransmit protocol happens to be there?

No.

 IHMO, it is
poor design practice to depend on error mechanisms to handle the
a defect in the routing design.

I think that the correct link selection will come with the location update
the node will send when it detects it is in the conditions to do so.
the routing protocol would stabilize quite quickly in the IP
based access net, upon reception of the location update...


>The requirement on the paging protocol I have are Non existent,
consistently
>with the fact that I do not recognize the need for such protocol.
>That req document is not really a requirement document, it is a document
>saying "we require paging, and here is why". However it steers clear from
>defining
>what paging is... Not much agreeable. It is a metarequirement documet on
>some
>Yet to be defined or conceived thing. 
>

May I quote from Section 2.0 of 
draft-ietf-seamoby-paging-problem-statement-02.txt:

      Paging - As a consequence of a mobile-bound packet destined for a
      mobile currently in dormant mode, signaling by the network through
      radio access points directed to locating the mobile and
      establishing a last hop connection. This messaging is in addition
      to simply delivering the packet to the mobile, i.e. last hop
      routing of packets is NOT considered to be paging.
      
This is our definition of paging. I suggest, if you want to throw bombs,
you take it up with the IESG.  


This cannot be used for both L2 and L3. I think you need two distinct
definitions.



alessio


From owner-seamoby@diameter.org  Fri Mar 30 17:33:26 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA18049
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 17:33:25 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UKllj09201
	for seamoby-list; Fri, 30 Mar 2001 12:47:47 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UKlgF09196
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 12:47:43 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA23451;
	Fri, 30 Mar 2001 11:56:23 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA17488;
	Fri, 30 Mar 2001 11:56:22 -0800 (PST)
Received: from darius (darius [10.6.84.105])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id LAA02060;
	Fri, 30 Mar 2001 11:56:18 -0800 (PST)
Date: Fri, 30 Mar 2001 11:56:16 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: RE: [seamoby] Seamoby Minutes - Please Review
To: Michael Thomas <mat@cisco.com>
Cc: Gary Kenward <gkenward@nortelnetworks.com>,
        "'Patrice Calhoun'" <pcalhoun@nasnfs.eng.sun.com>,
        seamoby@cdma-2000.org
In-Reply-To: "Your message with ID" <15044.45365.844598.739112@thomasm-u1.cisco.com>
Message-ID: <Roam.SIMC.2.0.6.985982176.19633.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

I put it in the minutes because it was a comment that was raised. It seems to
be controversial, so should I add an editor's note claiming this MM is an IGP,
and therefore not as big an issue???

PatC
> Gary Kenward writes:
>  > > There were some concerns in regards to how scalable a 
>  > > micro-mobility solution
>  > > could be, since it could be used across the Internet. This will be
>  > > addressed in the requirements phase.
>  > 
>  > This seems to be the major objection against at least some of the
>  > concepts proposed. And yet, doesn't "micro-mobility across the 
>  > (global) Internet" sound like an oxymoron?
> 
>    Yes. And a strawman too boot, because nobody's
>    been claiming it should.
> 
>  > Does every solution have to scale globally? In truth, I think not,
>  > and there must be many examples of local solutions that are used
>  > all over the globe, but do not scale to a global service.
> 
>    Even routing makes a distinction between interior
>    and exterior to autonomous systems. MM is nothing
>    but another twist on an IGP.
> 
> 	 Mike




From owner-seamoby@diameter.org  Fri Mar 30 17:58:43 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA19036
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 17:58:42 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2ULNEX09313
	for seamoby-list; Fri, 30 Mar 2001 13:23:14 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2ULN9F09308
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 13:23:09 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id MAA05331;
	Fri, 30 Mar 2001 12:32:24 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADG18026;
	Fri, 30 Mar 2001 12:32:20 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id MAA04036; Fri, 30 Mar 2001 12:32:19 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15044.60755.827751.208094@thomasm-u1.cisco.com>
Date: Fri, 30 Mar 2001 12:32:19 -0800 (PST)
To: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Cc: Michael Thomas <mat@cisco.com>, Gary Kenward <gkenward@nortelnetworks.com>,
        seamoby@cdma-2000.org
Subject: RE: [seamoby] Seamoby Minutes - Please Review
In-Reply-To: <Roam.SIMC.2.0.6.985982176.19633.pcalhoun@nasnfs>
References: <15044.45365.844598.739112@thomasm-u1.cisco.com>
	<Roam.SIMC.2.0.6.985982176.19633.pcalhoun@nasnfs>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Patrice Calhoun writes:
 > I put it in the minutes because it was a comment that was raised. It seems to
 > be controversial, so should I add an editor's note claiming this MM is an IGP,
 > and therefore not as big an issue???

   Well, I have never heard anybody on the MM team claim
   that MM would scale up to Internet. In fact, I've 
   always heard just the opposite: at some point, MM
   has to yield to interoperate with MIP because it
   *doesn't* scale to Internet proportions. I for one
   wouldn't want to be the one to bring back the news
   to our hardware guys that they need to be able 
   scale up to 2^64 unaggregated host routes.
   
		Mike

 > 
 > PatC
 > > Gary Kenward writes:
 > >  > > There were some concerns in regards to how scalable a 
 > >  > > micro-mobility solution
 > >  > > could be, since it could be used across the Internet. This will be
 > >  > > addressed in the requirements phase.
 > >  > 
 > >  > This seems to be the major objection against at least some of the
 > >  > concepts proposed. And yet, doesn't "micro-mobility across the 
 > >  > (global) Internet" sound like an oxymoron?
 > > 
 > >    Yes. And a strawman too boot, because nobody's
 > >    been claiming it should.
 > > 
 > >  > Does every solution have to scale globally? In truth, I think not,
 > >  > and there must be many examples of local solutions that are used
 > >  > all over the globe, but do not scale to a global service.
 > > 
 > >    Even routing makes a distinction between interior
 > >    and exterior to autonomous systems. MM is nothing
 > >    but another twist on an IGP.
 > > 
 > > 	 Mike
 > 
 > 


From owner-seamoby@diameter.org  Fri Mar 30 18:11:40 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA19487
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 18:11:40 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2ULTaX09328
	for seamoby-list; Fri, 30 Mar 2001 13:29:36 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2ULTWF09323
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 13:29:32 -0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA11666;
	Fri, 30 Mar 2001 12:38:18 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA25868;
	Fri, 30 Mar 2001 12:38:17 -0800 (PST)
Received: from darius (darius [10.6.84.105])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id MAA02544;
	Fri, 30 Mar 2001 12:38:15 -0800 (PST)
Date: Fri, 30 Mar 2001 12:38:13 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: RE: [seamoby] Seamoby Minutes - Please Review
To: Michael Thomas <mat@cisco.com>
Cc: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>,
        Gary Kenward <gkenward@nortelnetworks.com>, seamoby@cdma-2000.org
In-Reply-To: "Your message with ID" <15044.60755.827751.208094@thomasm-u1.cisco.com>
Message-ID: <Roam.SIMC.2.0.6.985984693.13117.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

Hey, these are minutes guys. I am just stating what was said at the meeting. I
don't think this is the right thread to worry about what will, or will not,
get created by the IRTF.

Now that I've read Michael's response, I propose we just leave the minutes
as-is. They are minutes... that's what was said... we can't go back in time
and change the meeting :(

the best I can do is add some clarifying statement, but we don't care in
seamoby anyways since this will be an IRTF activity.

PatC
> Patrice Calhoun writes:
>  > I put it in the minutes because it was a comment that was raised. It
> seems to
>  > be controversial, so should I add an editor's note claiming this MM is an
> IGP,
>  > and therefore not as big an issue???
> 
>    Well, I have never heard anybody on the MM team claim
>    that MM would scale up to Internet. In fact, I've 
>    always heard just the opposite: at some point, MM
>    has to yield to interoperate with MIP because it
>    *doesn't* scale to Internet proportions. I for one
>    wouldn't want to be the one to bring back the news
>    to our hardware guys that they need to be able 
>    scale up to 2^64 unaggregated host routes.
>    
> 		Mike
> 
>  > 
>  > PatC
>  > > Gary Kenward writes:
>  > >  > > There were some concerns in regards to how scalable a 
>  > >  > > micro-mobility solution
>  > >  > > could be, since it could be used across the Internet. This will be
>  > >  > > addressed in the requirements phase.
>  > >  > 
>  > >  > This seems to be the major objection against at least some of the
>  > >  > concepts proposed. And yet, doesn't "micro-mobility across the 
>  > >  > (global) Internet" sound like an oxymoron?
>  > > 
>  > >    Yes. And a strawman too boot, because nobody's
>  > >    been claiming it should.
>  > > 
>  > >  > Does every solution have to scale globally? In truth, I think not,
>  > >  > and there must be many examples of local solutions that are used
>  > >  > all over the globe, but do not scale to a global service.
>  > > 
>  > >    Even routing makes a distinction between interior
>  > >    and exterior to autonomous systems. MM is nothing
>  > >    but another twist on an IGP.
>  > > 
>  > > 	 Mike
>  > 
>  > 





From owner-seamoby@diameter.org  Fri Mar 30 18:15:16 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA19596
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 18:15:15 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UM6xC09429
	for seamoby-list; Fri, 30 Mar 2001 14:06:59 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UM5wF09422
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 14:05:58 -0800
Received: from tari.research.telcordia.com (tari [207.3.232.66])
	by thumper.research.telcordia.com (8.10.1/8.10.1) with ESMTP id f2ULBrO25464;
	Fri, 30 Mar 2001 16:11:58 -0500 (EST)
Received: from tuna.research.telcordia.com (ohba@tari-dhcp11.research.telcordia.com [207.3.232.125])
	by tari.research.telcordia.com (8.8.8/8.8.8) with ESMTP id QAA19467;
	Fri, 30 Mar 2001 16:13:22 -0500 (EST)
Date: Fri, 30 Mar 2001 16:15:03 -0500
Message-ID: <87ae63rmaw.wl@research.telcordia.com>
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: kempf@heliopolis.Eng.Sun.COM
Cc: gmorrow@nortelnetworks.com, yohba@tari.toshiba.com, eanderlind@lucent.com,
        seamoby@diameter.org
Subject: RE: Paging Functional Architecture ( was: RE: [seamoby] L2/L3 Pag ing)
In-Reply-To: In your message of "Thu, 29 Mar 2001 14:39:36 -0800 (PST)"
	<200103292239.OAA02900@heliopolis.Eng.Sun.COM>
References: <200103292239.OAA02900@heliopolis.Eng.Sun.COM>
User-Agent: Wanderlust/2.2.15 (More Than Words) WEMI/1.13.7 (Shimada) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386-debian-linux)
MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

At Thu, 29 Mar 2001 14:39:36 -0800 (PST),
James Kempf <kempf@heliopolis.Eng.Sun.COM> wrote:
> 
> Yoshihiro,
> 
> 
> >When we talk about power control mechanisms for wireline NIC cards,
> >the wirelined host may not necessarily be a mobile node.  On the other
> >hand, it seems to me that the paging discussed in this WG is tightly
> >coupled with mobility (Mobile IP).  Is it out of scope to discuss a
> >generic paging mechanism which can be used for both mobile and stable
> >nodes?
> >
> 
> I wouldn't say mobility, I would say routing. The kind of paging
> we are looking at is concerned with getting a dormant mode host
> to reestablish an active route back into the network. The problem
> is most acute with mobile hosts because one can't simply depend
> on the routes that were there before the host went dormant to be
> valid.
> 

I agree with you on saying routing.

> With regard to a wired host, the Intel Wired for Management protocol
> defines a kind of paging where a certain L2 frame causes a dormant
> mode wired host to wake up (sorry, I don't know any more details).
> One could view this as a kind of wired host paging. Note that it
> is not sufficient to simply send a packet to the host because
> the wakeup is triggered by a special L2 packet, if I am right about
> the need for a special L2 frame. 

It is Magic Packet technology 
(http://www.amd.com/products/npd/overview/20212.html).

A Magic Packet could be any MAC frame (even a TCP/IP data frame could
be a Magic Packet), by inserting a special paging sequence specific to
the MAC address of the paged device.  (The sender of the packet must 
know the target MAC address.)

> If it were the case
> (as apparently it is with Bluetooth) that the host could be reawakened
> without any special protocol, then one could simply send the packet
> and let the host wake up to take it. No paging protocol is needed
> in this case.

When L2 paging is triggered by L3 packet, at least some mechansim is
needed for a paging agent to retain the mapping between MAC address
and L3 address for the dormant node.  The mechanism might be just 
lengthening the ARP/neighbor cache lifetime at the paging agent, or
an explicit paging registration mechanism.

I may be stepping into requirement phase...

Regards,
Yoshihiro Ohba

> 
> 		jak
> 
> 
> 


From owner-seamoby@diameter.org  Fri Mar 30 18:17:41 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA19646
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 18:17:41 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UMmie09542
	for seamoby-list; Fri, 30 Mar 2001 14:48:45 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UMmeF09537
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 14:48:40 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id NAA21704;
	Fri, 30 Mar 2001 13:57:52 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADH00481;
	Fri, 30 Mar 2001 13:57:51 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id NAA04059; Fri, 30 Mar 2001 13:57:50 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15045.350.744410.794532@thomasm-u1.cisco.com>
Date: Fri, 30 Mar 2001 13:57:50 -0800 (PST)
To: "Martin, David P" <David.P.Martin@nextel.com>
Cc: "'Michael Thomas'" <mat@cisco.com>, "'David R. Oran'" <oran@cisco.com>,
        seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
In-Reply-To: <020A5EC56F3FD411B5230008C716D085868546@nhqntex01.nextel.com>
References: <020A5EC56F3FD411B5230008C716D085868546@nhqntex01.nextel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Martin, David P writes:
 > I'm trying to understand which non-reachability problems we will attempt to
 > address.  If the only problem we are trying to solve is reaching a dormant
 > mode, I am in full agreement with the problem statement.  

   As far as I know, this is all we're trying to
   address.
 
 > However, if we want a protocol that we deal with *all* non-reachability
 > issues (link failures, mobile left town, battery died, etc) then I think
 > that is two distinct problems.  One problem is which interface(s) to deliver
 > packets to, the other problem is what to do if the mobile doesn't respond in
 > a timely fashion.

   I believe that any paging protocol needs to face
   this possibility though.

 > The second problem of what to do if the mobile is not reachable is a
 > separate issue.  I feel that it probably *is* a worthwhile problem to solve.

   I dunno. Nothing extrordinary happens when my
   DSL line goes down right now. Do we really need
   to figure out a way backhaul my annoyance
   dotted with four letter words when that
   happens? :-)

 > > I hate to keep harping on this, but this sure
 > > seems to me to be familar ground. The problems you
 > > point out also would come up with a demand dialer
 > > type of interface, like say an ISDN line which
 > > isn't up all of the time. While the solutions may
 > > not be entirely algorithmic, the parameters are
 > > certainly well understood by now.
 > > 
 > The solutions for this problem to date have been optimized for particular
 > applications that were likely to be running (i.e. phone calls).  Different
 > applications would have different optimizations.  If its any consolation, I
 > have been convinced that it would be possible to solve this problem on an
 > application by application basis ... but I still think a good solution will
 > take a lot of work.

   Hmm. Application by application usually sets
   of the boil-the-ocean klaxon in my head. Would
   it be sufficient to set up an access control
   list on the access router to block all but, 
   say, SIP and whatever other protocols you
   wanted to listen for while you're dormant?

	     Mike


From owner-seamoby@diameter.org  Fri Mar 30 18:26:50 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20014
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 18:26:49 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UMmgI09536
	for seamoby-list; Fri, 30 Mar 2001 14:48:42 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UMmYF09530
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 14:48:34 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id NAA13526;
	Fri, 30 Mar 2001 13:57:45 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f2ULvhv19439;
	Fri, 30 Mar 2001 13:57:43 -0800
X-mProtect:  Fri, 30 Mar 2001 13:57:43 -0800 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdw9aolc; Fri, 30 Mar 2001 13:57:25 PST
Message-ID: <3AC50147.92241D92@iprg.nokia.com>
Date: Fri, 30 Mar 2001 13:57:27 -0800
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Gary Kenward <gkenward@nortelnetworks.com>, hmsyed@nortelnetworks.com
CC: seamoby@diameter.org
Subject: [seamoby] draft-hamid-seamoby-ct-reqs-00.txt
References: <13E2EF604DE5D111B2E50000F80824E8057A8D1C@zwdld001.ca.nortel.com> <3A9EAC7A.639F41EC@iprg.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello folks,

All in all, the requirements draft seems to be a very worthwhile
effort, from which good solutions are likely to be developed.  Thanks!

Here are some comments.

1. Security needs discussion.  Unsecured context transfers are
   to be avoided.  I see that the word "integrity" appears in
   section 4.2, but somehow I didn't think that the entire discussion
   about security was intended to be distilled into that single word.

2. Supporting one-to-many context transfers might be useful.
   It might also be complicated.  It almost certainly is not so
   crucial that its lack would break the protocol.  Thus, I would
   rate it no more than a "SHOULD", instead of a "MUST".

3. Conversely, reactive context transfer will sometimes be the
   only available option.  Thus, it has to be a MUST, not a SHOULD.

4. Terms like "micro-flow" and "integrity" need to be defined in the
   terminology section -- or, perhaps better, replaced by more
   specific or more common terms in the body of the text.  Specifically
   regarding "micro-flow" as you have used it, a protocol would need
   some identification mechanism.  This mechanism needs elaboration
   in the requirements draft, I think -- it is important.

5. Discussions about interworking with "the micro-mobility mechanism"
   are probably better deleted for now, although I agree with the spirit
   of that suggestion.

6. 100% reliability is impossible(*).  Furthermore, even high reliability
   may be undesirable as a requirement.  High reliability means
   retransmissions, backoff algorithms, algorithmic complexity,
   and longer time delays in case of errors.  All of these are
   opposed to the goal of context transfer as a way to get timely
   service without protracted renegotiations.  Maybe, in fact, it
   should be the case that [seamoby] should explicitly declare that
   highly reliable context transfer is "out of scope"!  I imagine
   that more than a single retransmission won't be worthwhile.
   [proof of (*): consider network partition or nuclear war]

7. I'd suggest adding the context transfer problem statement design
   team members to the acknowledgements.  There was certainly a lot of
   discussion on the mailing list from those folks, so I reckon they
   did a lot of work shaping the form of this draft.  Intuitively,
   the design team seems to have made a stronger contribution than
   those who were explicitly mentioned, but I wasn't there so I clearly
   cannot say with any certainty.

8. At the end of section 4.1, the last sentence refers to the number
   of messages being less.  Less than what?  The sentence before is
   missing a word after "simply".

9. At the top of page 5, the word "appropriate" should probably be
   "desired", because appropriateness would need a lot more definition.



Editorial:

"captured"         -->  "described"
"sustain"          -->  "preserve"
"rest of the ARs"  -->  "target ARs" (maybe worthwhile to put in terminology)
"ensure"           -->  "mean"    (in the paragraph preceding the bullet item
                                   about supporting reactive context transfer

In the sentence containing "cardinality between" -- perhaps
you meant "correspondence between the number of".  There are
some misspelled words, missing articles, missing parentheses,
and syntax errors that need proofreading, which if need be I
can type in later.  The text of the draft is too close both to
the header and to the footers.

Regards,
Charlie P.


From owner-seamoby@diameter.org  Fri Mar 30 18:30:35 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20128
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 18:30:34 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UN54u09599
	for seamoby-list; Fri, 30 Mar 2001 15:05:04 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UN4xF09594
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 15:04:59 -0800
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id OAA04736;
	Fri, 30 Mar 2001 14:13:44 -0800 (PST)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ADH00895;
	Fri, 30 Mar 2001 14:13:39 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id OAA04066; Fri, 30 Mar 2001 14:13:39 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15045.1299.593544.661275@thomasm-u1.cisco.com>
Date: Fri, 30 Mar 2001 14:13:39 -0800 (PST)
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: gmorrow@nortelnetworks.com, eanderlind@lucent.com, seamoby@diameter.org
Subject: RE: Paging Functional Architecture ( was: RE: [seamoby] L2/L3 Pag ing)
In-Reply-To: <87itks8fo5.wl@research.telcordia.com>
References: <85AA7486A2C1D411BCA20000F8073E4301B282F2@crchy271.us.nortel.com>
	<87itks8fo5.wl@research.telcordia.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Yoshihiro Ohba writes:
 > When we talk about power control mechanisms for wireline NIC cards,
 > the wirelined host may not necessarily be a mobile node.  On the other
 > hand, it seems to me that the paging discussed in this WG is tightly
 > coupled with mobility (Mobile IP).  Is it out of scope to discuss a
 > generic paging mechanism which can be used for both mobile and stable
 > nodes?

   No. I think that's an excellent requirement.

   Especially here in California.

		  Mike


From owner-seamoby@diameter.org  Fri Mar 30 19:29:42 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22485
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 19:29:41 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UNxtl09734
	for seamoby-list; Fri, 30 Mar 2001 15:59:55 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UNxnF09729
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 15:59:49 -0800
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f2UNB9w19284
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 17:11:09 -0600 (CST)
Received: from daebh01nok.americas.nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T529ced9e99ac12f254079@davir01nok.americas.nokia.com>;
 Fri, 30 Mar 2001 17:08:56 -0600
Received: by daebh01nok with Internet Mail Service (5.5.2652.78)
	id <H8771431>; Fri, 30 Mar 2001 17:08:56 -0600
Message-ID: <B9CFA6CE8FFDD211A1FB0008C7894E4601A659E1@bseis01nok>
From: rajeev.koodli@nokia.com
To: Lars-Erik.Jonsson@epl.ericsson.se, rajeev.koodli@nokia.com,
        zhigang.liu@nokia.com, micke@CS.Arizona.EDU,
        mobile-ip@sunroof.eng.sun.com, rohc@cdt.luth.se, seamoby@cdma-2000.org
Subject: [seamoby] RE: [rohc] Compression startup behavior
Date: Fri, 30 Mar 2001 17:08:55 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk

> 
> Sorry that I forgot to say "unfortunately" in the beginning 
> of the sentence below...
> 

Sorry that it is unfortunate for you..

Regards,

-Rajeev

> Anyway, I do not care if someone wants to do context transfer 
> as part of the handover procedures used for certain 
> environments. Personally, I think it is overkill and makes 
> things more complicated, but that is not up to me to judge. 
> However, it is not a header compression issue.
> 
> /L-E
> 
> 
> > > > I guess that context transfer is a mechanism 
> > > > that will be developed (snip)
> > > 
> >     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > This is a good starting position.
> > 
> > Regards,
> > 
> > -Rajeev
> 


From owner-seamoby@diameter.org  Fri Mar 30 19:37:24 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22771
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 19:37:23 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2V0BJx09791
	for seamoby-list; Fri, 30 Mar 2001 16:11:19 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2V0BFF09786
	for <seamoby@cdma-2000.org>; Fri, 30 Mar 2001 16:11:15 -0800
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA19570;
	Fri, 30 Mar 2001 15:20:33 -0800 (PST)
Received: from nasnfs.Eng.Sun.COM (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA29797;
	Fri, 30 Mar 2001 15:20:32 -0800 (PST)
Received: from darius (darius [10.6.84.105])
	by nasnfs.Eng.Sun.COM (8.9.3+Sun/8.9.1) with SMTP id PAA05477;
	Fri, 30 Mar 2001 15:20:18 -0800 (PST)
Date: Fri, 30 Mar 2001 15:20:14 -0800 (PST)
From: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Reply-To: Patrice Calhoun <pcalhoun@nasnfs.eng.sun.com>
Subject: RE: [seamoby] To page, or not to page
To: "Casati, Alessio (Alessio)" <acasati@lucent.com>
Cc: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        pcalhoun@nasnfs.eng.sun.com, seamoby@cdma-2000.org
In-Reply-To: "Your message with ID" <976F7C55E3B2D111A0720008C728549C097CC2AA@en0060exch001u.uk.lucent.com>
Message-ID: <Roam.SIMC.2.0.6.985994414.30562.pcalhoun@nasnfs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

Alessio,

First, could I kindly request that you prefix your comments to Jim. It is very
difficult for me to figure out what you are saying since it is all mixed up.

Second, it appears to me as if the problem is not with paging, but the
requirements. Again, you stated that you haven't read the problem statement,
but seem to have lots of ideas on what is needed, and what is not. Could I
convince you to read the problem statement, and then provide comments on the
spec?

Lastly, could I also encourage you to work on the requirements, following e
normal IETF process, to make sure that your needs are met?

Thanks,

PatC



From owner-seamoby@diameter.org  Fri Mar 30 20:01:30 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23972
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 20:01:28 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2UM6xC09429
	for seamoby-list; Fri, 30 Mar 2001 14:06:59 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2UM5wF09422
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 14:05:58 -0800
Received: from tari.research.telcordia.com (tari [207.3.232.66])
	by thumper.research.telcordia.com (8.10.1/8.10.1) with ESMTP id f2ULBrO25464;
	Fri, 30 Mar 2001 16:11:58 -0500 (EST)
Received: from tuna.research.telcordia.com (ohba@tari-dhcp11.research.telcordia.com [207.3.232.125])
	by tari.research.telcordia.com (8.8.8/8.8.8) with ESMTP id QAA19467;
	Fri, 30 Mar 2001 16:13:22 -0500 (EST)
Date: Fri, 30 Mar 2001 16:15:03 -0500
Message-ID: <87ae63rmaw.wl@research.telcordia.com>
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: kempf@heliopolis.Eng.Sun.COM
Cc: gmorrow@nortelnetworks.com, yohba@tari.toshiba.com, eanderlind@lucent.com,
        seamoby@diameter.org
Subject: RE: Paging Functional Architecture ( was: RE: [seamoby] L2/L3 Pag ing)
In-Reply-To: In your message of "Thu, 29 Mar 2001 14:39:36 -0800 (PST)"
	<200103292239.OAA02900@heliopolis.Eng.Sun.COM>
References: <200103292239.OAA02900@heliopolis.Eng.Sun.COM>
User-Agent: Wanderlust/2.2.15 (More Than Words) WEMI/1.13.7 (Shimada) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386-debian-linux)
MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-seamoby@diameter.org
Precedence: bulk

At Thu, 29 Mar 2001 14:39:36 -0800 (PST),
James Kempf <kempf@heliopolis.Eng.Sun.COM> wrote:
> 
> Yoshihiro,
> 
> 
> >When we talk about power control mechanisms for wireline NIC cards,
> >the wirelined host may not necessarily be a mobile node.  On the other
> >hand, it seems to me that the paging discussed in this WG is tightly
> >coupled with mobility (Mobile IP).  Is it out of scope to discuss a
> >generic paging mechanism which can be used for both mobile and stable
> >nodes?
> >
> 
> I wouldn't say mobility, I would say routing. The kind of paging
> we are looking at is concerned with getting a dormant mode host
> to reestablish an active route back into the network. The problem
> is most acute with mobile hosts because one can't simply depend
> on the routes that were there before the host went dormant to be
> valid.
> 

I agree with you on saying routing.

> With regard to a wired host, the Intel Wired for Management protocol
> defines a kind of paging where a certain L2 frame causes a dormant
> mode wired host to wake up (sorry, I don't know any more details).
> One could view this as a kind of wired host paging. Note that it
> is not sufficient to simply send a packet to the host because
> the wakeup is triggered by a special L2 packet, if I am right about
> the need for a special L2 frame. 

It is Magic Packet technology 
(http://www.amd.com/products/npd/overview/20212.html).

A Magic Packet could be any MAC frame (even a TCP/IP data frame could
be a Magic Packet), by inserting a special paging sequence specific to
the MAC address of the paged device.  (The sender of the packet must 
know the target MAC address.)

> If it were the case
> (as apparently it is with Bluetooth) that the host could be reawakened
> without any special protocol, then one could simply send the packet
> and let the host wake up to take it. No paging protocol is needed
> in this case.

When L2 paging is triggered by L3 packet, at least some mechansim is
needed for a paging agent to retain the mapping between MAC address
and L3 address for the dormant node.  The mechanism might be just 
lengthening the ARP/neighbor cache lifetime at the paging agent, or
an explicit paging registration mechanism.

I may be stepping into requirement phase...

Regards,
Yoshihiro Ohba

> 
> 		jak
> 
> 
> 


From owner-seamoby@diameter.org  Fri Mar 30 22:15:25 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA01638
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 22:15:24 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2V2g6h10169
	for seamoby-list; Fri, 30 Mar 2001 18:42:06 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from east.isi.edu (east.isi.edu [38.245.76.2])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2V2f5F10164;
	Fri, 30 Mar 2001 18:41:05 -0800
Received: from maia.east.isi.edu (maia.east.isi.edu [38.245.76.14])
	by east.isi.edu (8.9.2/8.9.2) with SMTP id UAA10769;
	Fri, 30 Mar 2001 20:50:15 -0500 (EST)
Posted-Date: Fri, 30 Mar 2001 20:54:56 -0500
Message-Id: <10103310154.AA17116@maia.east.isi.edu>
Received: from LOCALHOST.east.isi.edu by maia.east.isi.edu (4.1/4.0.3-6)
	id <AA17116>; Fri, 30 Mar 01 20:54:57 EST
To: James Kempf <kempf@heliopolis.eng.sun.com>
Cc: seamoby@diameter.org, seamoby-paging@diameter.org
Reply-To: mankin@ISI.EDU
Subject: Re: [seamoby] Paging or Not 
In-Reply-To: Your message of Fri, 30 Mar 2001 08:40:52 -0800.
             <200103301640.IAA17195@heliopolis.Eng.Sun.COM> 
Date: Fri, 30 Mar 2001 20:54:56 -0500
From: Allison Mankin <mankin@ISI.EDU>
Sender: owner-seamoby@diameter.org
Precedence: bulk

Jim,

As AD, I approved going ahead with starting on requirements work
for paging already, based on the results when Pat last called
the problem statement.

In general, my observation has agreed with Pat's that there is 
IETF-style (that is, tumultuous, but sound) consensus to go ahead.

There is a remaining step, which is the IESG review of the problem
statement, which will secure the paging task in the Seamoby charter,
and may return some specific feedback.

The IESG will review the problem statement during our telechat this
coming week, and I'll make sure to report the results to the list.

Regards,

Allison

> Pat/Allison/All,
>
> Behcet, the design team members, and I have committed ourselves to working
> fairly intensively on the paging problem over the next months until
> IETF 51. Recently, there has been some email about whether or not
> paging should even be considered by IETF. I had thought that we
> were beyond this point. This was in response to Pat's email of
> a few days ago.
> 
> The conclusion of the design team, which I presented at IETF 50, was
> that there is a problem to be solved. It is not unsolvable by
> using mobile IP, but the solution is difficult.
> 
> Frankly, I am not about to spend the next 4 months waging an email battle
> with bomb throwers who want to derail progress. If we
> don't have agreement on doing requirements, I would like to suggest
> we can this activity right now. I've got plenty of other things I could
> be spending time on, and I'm sure the other paging design team
> members feel the same.
> 
> Are we going forward with requirements on paging or not?


From owner-seamoby@diameter.org  Fri Mar 30 22:46:41 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA04616
	for <seamoby-archive@odin.ietf.org>; Fri, 30 Mar 2001 22:46:41 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2V2TnS10125
	for seamoby-list; Fri, 30 Mar 2001 18:29:49 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2V2SnF10120
	for <seamoby@diameter.org>; Fri, 30 Mar 2001 18:28:49 -0800
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2653.19)
	id <GRX4S8GK>; Fri, 30 Mar 2001 20:38:06 -0500
Message-ID: <6833D86F1B05CA4FBAB3C73DD98BD8B90D2ABB@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Michael Thomas'" <mat@cisco.com>,
        "Martin, David P"
	 <David.P.Martin@nextel.com>
Cc: "'David R. Oran'" <oran@cisco.com>, seamoby@diameter.org
Subject: RE: [seamoby] L2/L3 Paging
Date: Fri, 30 Mar 2001 20:38:02 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-seamoby@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Michael Thomas [mailto:mat@cisco.com]
> Sent: Friday, March 30, 2001 4:58 PM
> To: Martin, David P
> Cc: 'Michael Thomas'; 'David R. Oran'; seamoby@diameter.org
> Subject: RE: [seamoby] L2/L3 Paging
> 
> 
> Martin, David P writes:
>  > I'm trying to understand which non-reachability problems 
> we will attempt to
>  > address.  If the only problem we are trying to solve is 
> reaching a dormant
>  > mode, I am in full agreement with the problem statement.  
> 
>    As far as I know, this is all we're trying to
>    address.
>  
>  > However, if we want a protocol that we deal with *all* 
> non-reachability
>  > issues (link failures, mobile left town, battery died, 
> etc) then I think
>  > that is two distinct problems.  One problem is which 
> interface(s) to deliver
>  > packets to, the other problem is what to do if the mobile 
> doesn't respond in
>  > a timely fashion.
> 

Mobile left town, battery died, ... all fall under the catagory: link
failure.

It can be resolved with an implementation specific Link Timeout Timer, where
if no packets are transferred for Link Timeout seconds link failure is
assumed.  Link reliability is an L2 issue.

- Kulwinder.

>    I believe that any paging protocol needs to face
>    this possibility though.
> 
>  > The second problem of what to do if the mobile is not 
> reachable is a
>  > separate issue.  I feel that it probably *is* a worthwhile 
> problem to solve.
> 
>    I dunno. Nothing extrordinary happens when my
>    DSL line goes down right now. Do we really need
>    to figure out a way backhaul my annoyance
>    dotted with four letter words when that
>    happens? :-)
> 
>  > > I hate to keep harping on this, but this sure
>  > > seems to me to be familar ground. The problems you
>  > > point out also would come up with a demand dialer
>  > > type of interface, like say an ISDN line which
>  > > isn't up all of the time. While the solutions may
>  > > not be entirely algorithmic, the parameters are
>  > > certainly well understood by now.
>  > > 
>  > The solutions for this problem to date have been optimized 
> for particular
>  > applications that were likely to be running (i.e. phone 
> calls).  Different
>  > applications would have different optimizations.  If its 
> any consolation, I
>  > have been convinced that it would be possible to solve 
> this problem on an
>  > application by application basis ... but I still think a 
> good solution will
>  > take a lot of work.
> 
>    Hmm. Application by application usually sets
>    of the boil-the-ocean klaxon in my head. Would
>    it be sufficient to set up an access control
>    list on the access router to block all but, 
>    say, SIP and whatever other protocols you
>    wanted to listen for while you're dormant?
> 
> 	     Mike
> 


From owner-seamoby@diameter.org  Sat Mar 31 04:31:25 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA15497
	for <seamoby-archive@odin.ietf.org>; Sat, 31 Mar 2001 04:31:24 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2V8TnE10924
	for seamoby-list; Sat, 31 Mar 2001 00:29:49 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2V8TjF10919
	for <seamoby@cdma-2000.org>; Sat, 31 Mar 2001 00:29:45 -0800
Received: from ORANLT (oran-home-ss20.cisco.com [171.69.210.4])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id XAA29628;
	Fri, 30 Mar 2001 23:39:01 -0800 (PST)
From: "David R. Oran" <oran@cisco.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>,
        <pcalhoun@nasnfs.eng.sun.com>, <acasati@lucent.com>
Cc: <seamoby@cdma-2000.org>
Subject: RE: [seamoby] To page, or not to page
Date: Sat, 31 Mar 2001 02:39:14 -0500
Organization: Cisco Systems
Message-ID: <011c01c0b9b5$afd64c10$04d245ab@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2511
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <200103301632.IAA17009@heliopolis.Eng.Sun.COM>
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: owner-seamoby@diameter.org 
> [mailto:owner-seamoby@diameter.org] On Behalf Of James Kempf
> Sent: Friday, March 30, 2001 11:33 AM
> To: kempf@heliopolis.Eng.Sun.COM; 
> pcalhoun@nasnfs.eng.sun.com; acasati@lucent.com
> Cc: seamoby@cdma-2000.org
> Subject: RE: [seamoby] To page, or not to page
>
[snip] 
> >That is acceptable, but I dont see the need for a paging 
> protocol. Just 
> >send data. the APs where the MN is not attached, will drop 
> packet, and 
> >you are set.
> >
> 
> So you want to handle a defect in the routing protocol by 
> falling back on TCP retransmission, or, if TCP isn't used, 
> whatever application specific UDP retransmit protocol happens 
> to be there? IHMO, it is poor design practice to depend on 
> error mechanisms to handle the a defect in the routing design.
>
Hmmm, I believe it's called "the end-to-end principle", as opposed to
"poor design practice".

(couldn't resist, sorry. Your argument smacks of folks who over the
years believed you had to have deterministically loop-free routing and
that routing protocols which permitted transient loops were hopelessly
broken). 

Dave.




From owner-seamoby@diameter.org  Sat Mar 31 07:26:16 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA29468
	for <seamoby-archive@odin.ietf.org>; Sat, 31 Mar 2001 07:26:15 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2VBU9B11300
	for seamoby-list; Sat, 31 Mar 2001 03:30:09 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2VBTQF11295
	for <seamoby@cdma-2000.org>; Sat, 31 Mar 2001 03:29:26 -0800
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id CAA28274;
	Sat, 31 Mar 2001 02:38:41 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f2VAcda08085;
	Sat, 31 Mar 2001 02:38:39 -0800
X-mProtect:  Sat, 31 Mar 2001 02:38:39 -0800 Nokia Silicon Valley Messaging Protection
Received: from Icharliep-1.iprg.nokia.com (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(WTS.12.69) smtpdKCDZlE; Sat, 31 Mar 2001 02:37:55 PST
Message-ID: <3AC5AFF7.B714BB85@iprg.nokia.com>
Date: Sat, 31 Mar 2001 02:22:47 -0800
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "David R. Oran" <oran@cisco.com>
CC: seamoby@cdma-2000.org
Subject: Re: [seamoby] To page, or not to page
References: <011c01c0b9b5$afd64c10$04d245ab@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello Dave,

Since I fall into the camp that believes that routing protocols should
take stringent measures to avoid routing loops, I wonder if you could
characterize the times when such are acceptable.  I would not say
that a routing protocol is "hopelessly broken" if it had transient loops,
but I would say that improvements would be desirable if they didn't
cause some horrid other downside.

Regards,
Charlie P.


"David R. Oran" wrote:

> > -----Original Message-----
> > From: owner-seamoby@diameter.org
> > [mailto:owner-seamoby@diameter.org] On Behalf Of James Kempf
> > Sent: Friday, March 30, 2001 11:33 AM
> > To: kempf@heliopolis.Eng.Sun.COM;
> > pcalhoun@nasnfs.eng.sun.com; acasati@lucent.com
> > Cc: seamoby@cdma-2000.org
> > Subject: RE: [seamoby] To page, or not to page
> >
> [snip]
> > >That is acceptable, but I dont see the need for a paging
> > protocol. Just
> > >send data. the APs where the MN is not attached, will drop
> > packet, and
> > >you are set.
> > >
> >
> > So you want to handle a defect in the routing protocol by
> > falling back on TCP retransmission, or, if TCP isn't used,
> > whatever application specific UDP retransmit protocol happens
> > to be there? IHMO, it is poor design practice to depend on
> > error mechanisms to handle the a defect in the routing design.
> >
> Hmmm, I believe it's called "the end-to-end principle", as opposed to
> "poor design practice".
>
> (couldn't resist, sorry. Your argument smacks of folks who over the
> years believed you had to have deterministically loop-free routing and
> that routing protocols which permitted transient loops were hopelessly
> broken).
>
> Dave.



From owner-seamoby@diameter.org  Sat Mar 31 10:37:29 2001
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA16942
	for <seamoby-archive@odin.ietf.org>; Sat, 31 Mar 2001 10:37:28 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.11.3/8.11.3) id f2VEdJw11884
	for seamoby-list; Sat, 31 Mar 2001 06:39:19 -0800
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-seamoby@diameter.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by charizard.diameter.org (8.11.3/8.11.3) with ESMTP id f2VEdBF11879
	for <seamoby@cdma-2000.org>; Sat, 31 Mar 2001 06:39:11 -0800
Received: from ORANLT (oran-home-ss20.cisco.com [171.69.210.4])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id FAA01295;
	Sat, 31 Mar 2001 05:48:29 -0800 (PST)
From: "David R. Oran" <oran@cisco.com>
To: "'Charlie Perkins'" <charliep@iprg.nokia.com>
Cc: <seamoby@cdma-2000.org>
Subject: RE: [seamoby] To page, or not to page
Date: Sat, 31 Mar 2001 08:48:42 -0500
Organization: Cisco Systems
Message-ID: <012601c0b9e9$4ca6eb20$04d245ab@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2511
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <3AC5AFF7.B714BB85@iprg.nokia.com>
Sender: owner-seamoby@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: Charlie Perkins [mailto:charliep@iprg.nokia.com] 
> Sent: Saturday, March 31, 2001 5:23 AM
> To: David R. Oran
> Cc: seamoby@cdma-2000.org
> Subject: Re: [seamoby] To page, or not to page
> 
> 
> 
> Hello Dave,
> 
> Since I fall into the camp that believes that routing 
> protocols should take stringent measures to avoid routing 
> loops, I wonder if you could characterize the times when such 
> are acceptable.  I would not say that a routing protocol is 
> "hopelessly broken" if it had transient loops, but I would 
> say that improvements would be desirable if they didn't cause 
> some horrid other downside.
>
None of the deployed, operational, and very successful routing protocols
in the internet prohibit transient loops during topology changes. ISIS,
OSPF, RIP2, etc. all have this characteristic. 

The protocols that deterministically prevent loops tend to be much more
complex and bug-prone (e.g. Dual, Jaffe-Moss, etc.)  and have
considerably slower convergence in the presence of any lost control
packets. Some have "hidden" failure modes in which loops can still form
(e.g. Jaffe-Moss) under pathological conditions, like freeze timers
expiring.

Dave.

> Regards,
> Charlie P.
> 
> 
> "David R. Oran" wrote:
> 
> > > -----Original Message-----
> > > From: owner-seamoby@diameter.org 
> [mailto:owner-seamoby@diameter.org] 
> > > On Behalf Of James 
> Kempf
> > > Sent: Friday, March 30, 2001 11:33 AM
> > > To: kempf@heliopolis.Eng.Sun.COM; pcalhoun@nasnfs.eng.sun.com; 
> > > acasati@lucent.com
> > > Cc: seamoby@cdma-2000.org
> > > Subject: RE: [seamoby] To page, or not to page
> > >
> > [snip]
> > > >That is acceptable, but I dont see the need for a paging
> > > protocol. Just
> > > >send data. the APs where the MN is not attached, will drop
> > > packet, and
> > > >you are set.
> > > >
> > >
> > > So you want to handle a defect in the routing protocol by falling 
> > > back on TCP retransmission, or, if TCP isn't used, whatever 
> > > application specific UDP retransmit protocol happens to be there? 
> > > IHMO, it is poor design practice to depend on error mechanisms to 
> > > handle the a defect in the routing design.
> > >
> > Hmmm, I believe it's called "the end-to-end principle", as 
> opposed to 
> > "poor design practice".
> >
> > (couldn't resist, sorry. Your argument smacks of folks who over the 
> > years believed you had to have deterministically loop-free 
> routing and 
> > that routing protocols which permitted transient loops were 
> hopelessly 
> > broken).
> >
> > Dave.
> 
> 



