From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Sat Jul 1 02:18:07 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17010
for ; Sat, 1 Jul 2000 02:18:06 -0400 (EDT)
Received: from standards (47.234.32.16:1914) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7A0D4@standards.nortelnetworks.com>; Sat, 1 Jul 2000 2:07:58 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 2918 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Sat, 1 Jul 2000 02:07:58 -0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7A0D3@standards.nortelnetworks.com>; Sat, 1 Jul 2000 1:57:58
-0400
Received: from envh01.ysgear.co.jp (hi051.enshu-net.or.jp [210.154.119.51]) by
hosaka.smallworks.com (8.9.1/8.9.1) with ESMTP id BAA26701 for
; Sat, 1 Jul 2000 01:07:31 -0500 (CDT)
Received: from [207.193.0.193] by envh01.ysgear.co.jp (Post.Office MTA v3.1.2J
release 205-101-J ID# 0-0U10L2S100) with SMTP id AAA182; Sat, 1 Jul
2000 15:07:01 +0900
X-Priority: 3
X-MSMail-Priority: Normal
Errors-To: cybrmrktg@winning.com
Message-ID: <00005771382b$00002d8e$000049c1@taffar
(pool-209-138-205-92-dlls.grid.net [219.138.205.92]) by
smtp7.atl.mindspring.net (ts029d25.nil-ny.concentric.net
[216.173.24.181])>
Date: Sat, 1 Jul 2000 01:05:53 -0500
Reply-To: rlp53633@interserve.com.hk
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: rlp53633@interserve.com.hk
Subject: [MOBILE-IP] It is now here...Flat Rate Long Distance-Unlimited
Calls
18881
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
It's Finally Here!
We have all been waiting for this one!
FLAT RATE UNLIMITED LONG DISTANCE CALLING!
CALL ALL-YOU-WANT!
24 hrs/day, 7 days a week!
You are already familiar with the Fiber-Optic technology
of the three service providers for our program. Over 90%
of the long distance traffic is already handled by these
companies, in fact, you are probably already a customer
of one of them! So, you already know the quality!
We are a retail resell vendor of the largest long distance networks in
the U.S. through which our Flat Rate Long Distance service is now being
offered. Others have tried to provide a flat rate long distance service
via Internet Telephony or Prepaid Phone Card Platform but these
platforms do not give the ability to create a line connection with the
clarity of standard fiber-optic technology.
Fixed Monthly Flat Rate
Clear, commercial grade sound quality
Not VOIP or internet calling
No Hidden Charges!
No more guessing about your monthly phone bill!
No need to switch carriers with one of our plans!
In & Out of State Calling!
NO per-call time limits!
NO need to dial a pin number!
Residential & Commercial plans to choose from:
24/7 Residential $59.95
All you can talk! Call anytime from a Dedicated Registered Phone
24 hours a day, 7 days a week, 365 days a year to 100%
(including INTRAstate) of the phones in the Continental USA
Unlimited 24/7 (not for business use)
Commercial/HBB
Plan 1.) 3900 min - 1 + Dialing -- $79.95/line plus taxes
3-way calling, faxing, conference calls
5.9¢/min. spill over
Plan 2.) 5000 min - 1 + Dialing -- $99.95/line plus taxes
24/7, INTERstate calling, 48 continental states
3-way calling, faxing, conference calls
5.9¢/min. spill over
Call Us TODAY and get all the details for yourself!
1-800-242-0363....Ext 2828
Coming soon! International unlimited residential plan!
\|||/
(. .)
---oOoo---------------
(REMOVAL INSTRUCTIONS)
This is a one-time mailing, done by an independent
marketing company. We respect your online privacy and apologize
if you have received this message in error. We do respect our
remove lists! Please do not use the reply to this e-mail, e-mail reply
cannot be read! If you would like to be removed from our mailing list
just click below and send us an remove request email.
Please be aware that any disruption to our remove link prevents
those that want to be removed from our database from being removed.
mailto:nadapromos358@usa.com?subject=pleaseremovelngdstpromo
It's Finally Here!
We have all been waiting for this one!
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Sat Jul 1 14:54:40 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21602
for ; Sat, 1 Jul 2000 14:54:40 -0400 (EDT)
Received: from standards (47.234.32.16:4632) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7A2DA@standards.nortelnetworks.com>; Sat, 1 Jul 2000 14:44:12 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 3614 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Sat, 1 Jul 2000 14:44:12 -0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7A2D6@standards.nortelnetworks.com>; Sat, 1 Jul 2000 14:34:12
-0400
Received: from aomail.asahiorikomi.co.jp (aomail.asaori.co.jp [210.225.81.14])
by hosaka.smallworks.com (8.9.1/8.9.1) with ESMTP id NAA00027 for
; Sat, 1 Jul 2000 13:43:50 -0500 (CDT)
Received: from [195.179.91.129] ([207.193.2.26]) by aomail.asahiorikomi.co.jp
(Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-45575U200L2S100)
with SMTP id ABE257; Sun, 2 Jul 2000 03:17:22 +0900
MIME-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
Errors-To: cybrmrktg@winning.com
Message-ID: <000036764f96$000024fc$00007668@195.143.58.206>
Date: Sat, 1 Jul 2000 13:10:57 -0500
Reply-To: hrt355@singnet.com
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: hrt355@singnet.com
Subject: [MOBILE-IP] Your Own Pro Website For Your Business
30312
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: quoted-printable
Free Web Site Promotion!
For Continental US Residents =
Only!!!
PLEASE CLICK ONE TIME ONLY---IT MAY TAKE UP TO 30 SECONDS
Your email address will be held private for in house use only.
We will not release your email address to any other party.
<=
SCRIPT LANGUAGE=3D"JavaScript1.1">
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Sat Jul 1 22:56:00 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25369
for ; Sat, 1 Jul 2000 22:55:59 -0400 (EDT)
Received: from standards (47.234.32.16:4806) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7A393@standards.nortelnetworks.com>; Sat, 1 Jul 2000 22:45:52 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 3859 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Sat, 1 Jul 2000 22:45:52 -0400
Received: from email-broadcast.com by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7A390@standards.nortelnetworks.com>; Sat, 1 Jul 2000 22:35:52
-0400
Received: from spysguidesnet12@rocketmail.com by spysguidesnet13@rocketmail.com
(8.8.5/8.6.5) with SMTP id GAA05225 for
; Sat, 01 Jul 2000 20:15:34 -0600
(EST)
Message-ID: <200007020238.TAA02881@email-broadcast.com>
Date: Sat, 1 Jul 2000 20:15:34 EST
Reply-To: spysguidesnet12@ROCKETMAIL.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: spysguidesnet12@ROCKETMAIL.COM
Subject: [MOBILE-IP] INTERNET SPY GUIDE finds info!
X-To: spysguidesnet13@rocketmail.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
READY TO KNOW?
CONFIDENTIAL!
The SOFTWARE They Want BANNED In all 50 STATES.
Why? Because these secrets were never intended to reach your eyes...
Get the facts on anyone!
Locate Missing Persons, find Lost Relatives, obtain Addresses
and Phone Numbers of old school friends, even Skip Trace Dead
Beat Spouses. This is not a Private Investigator, but a
sophisticated SOFTWARE program DESIGNED to automatically
CRACK YOUR CASE with links to thousands of Public Record databases.
Find out SECRETS about your relatives, friends, enemies,
and everyone else! Even your spouse! With the New,
INTERNET SPY AND YOU!
It's absolutely astounding! Here's what you can learn.
License plate number!
Get anyone's name and address with just a license plate number!
(Find that girl you met in traffic!)
Driving record!
Get anyone's driving record!
Social security number!
Trace anyone by social security number!
Address!
Get anyone's address with just a name!
Unlisted phone numbers!
Get anyone's phone number with just a name even unlisted numbers!
Locate!
Long lost friends, relatives, a past lover who broke your heart!
E-mail!
Send anonymous e-mail completely untraceable!
Dirty secrets!
Discover dirty secrets your in-laws don't want you to know!
Investigate anyone!
Use the sources that private investigators use (all on the Internet)
secretly!
Ex-spouse!
Learn how to get information on an ex-spouse that will help you
win in court! (Dig up old skeletons)!
Criminal search Background check!
Find out about your daughter's boyfriend!
Find out!
If you are being investigated!
Neighbors!
Learn all about your mysterious neighbors! Find out what they
have to hide!
People you work with!
Be astonished by what you'll learn about people you work with!
Education verification!
Did he really graduate college? Find out!
Internet Spy and You!
Software will help you discover ANYTHING about anyone, with
clickable hyperlinks and no typing in Internet addresses! Just
insert the floppy disk and Go!
You will be shocked and amazed by the secrets that can be
discovered about absolutely everyone! Find out the secrets
they don't want you to know! About others, about yourself!
It's INCREDIBLE what you can find out using Internet Spy and You
and the Internet! You'll be riveted to your computer screen!
Get the software they're trying to ban! Before it's too late!
LIMITED TIME OFFER ORDER TODAY!
Only $24.95
We will RUSH YOU our Internet Spy and You SOFTWARE so you can
begin discovering all the secrets you ever wanted to know!
You can Know EVERYTHING about ANYONE with our Internet Spy and
You Software. Works with all browsers and all versions of AOL!
ORDER TODAY. SEND ONLY $24.95 US CASH, CHECK, OR CREDIT CARD
(you may also send one of your own address labels for accuracy if you have
one).
Foreign money orders must be payable on a US BANK AND IN US FUNDS!
NO EXCEPTIONS!
DON'T WAIT TO GET STARTED...It's as easy as 1, 2, 3.
STEP 1 - Print the order form text below.
STEP 2 - Type or print your order information into the order form
section.
STEP 3 - Mail order form and payment to the address below.
Send to:
INFORMATION PLUS
PO BOX 9889
PCBEACH, FL 32417
Name: ________________________________________
Address: ________________________________________
City/State/Zip: ______________________________________
FOR CREDIT CARD ORDERS ONLY!
Account Number: ____________________________________
Exp. Date: ________________________
DISCLAIMER: The seller of this powerful software resource will not be
held responsible for how the purchaser chooses to use it's resources.
To be removed from our mailing list midwest12@dcemail.com
and put remove in the subject. Thank you
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Mon Jul 3 07:53:17 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29709
for ; Mon, 3 Jul 2000 07:53:16 -0400 (EDT)
Received: from standards (47.234.32.16:1037) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7A708@standards.nortelnetworks.com>; Mon, 3 Jul 2000 7:42:43 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 5028 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 3 Jul 2000 07:42:43 -0400
Received: from sonne.darmstadt.gmd.de by standards.nortelnetworks.com (LSMTP
for Windows NT v1.1b) with SMTP id
<0.FFB7A707@standards.nortelnetworks.com>; Mon, 3 Jul 2000 7:42:40
-0400
Received: from darmstadt.gmd.de (rho [141.12.34.56]) by sonne.darmstadt.gmd.de
(8.8.8/8.8.5) with ESMTP id NAA07570; Mon, 3 Jul 2000 13:51:35 +0200
(MET DST)
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: de,en,it
MIME-Version: 1.0
References:
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <39607DD5.7D4AF77F@darmstadt.gmd.de>
Date: Mon, 3 Jul 2000 13:49:41 +0200
Reply-To: Wolfgang Schoenfeld
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Wolfgang Schoenfeld
Organization: GMD IPSI Darmstadt Deutschland
Subject: Re: [MOBILE-IP] begginers question
X-To: Noam Gonen - Israel
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit
Noam Gonen - Israel wrote:
>
> Hi,
> Where does one find the required stuff/documentation for a beginners lecture
> on IP & cellulars ?
> I mean the required stuff to make a bottom-up acquaintance with how these
> two sectors "meet" and work it from there . (not straghit into FAs, and
> PDSNs etc. but more structured)
>
> Appologies for the "beginner" tone of the question, yet if one shall not
> ask.....
>
> Noam Gonnen
> Gilat Satellite Networks LTD.
> Direct : 972-4-9939330
>
> ----------------------------------------------------------------------------
> ----------------
Noam,
As far as I know,
there is not yet a "complete" lecture on the topic in question.
I tried to address it in my lecture "mobility in communication" last winter,
but this is still very sketchy (and in German), see
http://www.darmstadt.gmd.de/mobile/teaching/courses/mobinkom/3Vermittlung.pdf .
English translation is on the way and will (has to!) be complete in September.
The colleagues in Finland are heavily working on the topic, see
http://www.cs.hut.fi/Research/Dynamics/
But I don't know of any lecture there.
I'm convinced that, if a "more structured" (abstract) approach existed,
work on UMTS ("IP to the base station") would be much easier.
Hence, I think your question is by no means a beginner's question.
Wolfgang
--
Wolfgang Schoenfeld, GMD-IPSI, +49-6151-869-865
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Mon Jul 3 10:18:28 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02434
for ; Mon, 3 Jul 2000 10:18:28 -0400 (EDT)
Received: from standards (47.234.32.16:4730) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7A7B7@standards.nortelnetworks.com>; Mon, 3 Jul 2000 10:08:09 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 5259 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 3 Jul 2000 10:08:09 -0400
Received: from mail0.u-aizu.ac.jp by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7A7B6@standards.nortelnetworks.com>; Mon, 3 Jul 2000 10:08:08
-0400
Received: from pross114.u-aizu.ac.jp (pross114 [163.143.180.102]) by
mail0.u-aizu.ac.jp (8.9.3+3.1W/3.7Winternet-gw) with ESMTP id
XAA19634; Mon, 3 Jul 2000 23:17:38 +0900 (JST)
Received: from u-aizu.ac.jp (localhost [127.0.0.1]) by pross114.u-aizu.ac.jp
(8.9.3+3.1W/3.7Wistcmx+kanji) with ESMTP id XAA18638; Mon, 3 Jul 2000
23:17:37 +0900 (JST)
X-Mailer: Mozilla 4.7 [en_jp] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
References:
Content-Type: multipart/alternative;
boundary="------------0077B70F7EFE9D3C9A962AF3"
Message-ID: <3960A080.2E762218@u-aizu.ac.jp>
Date: Mon, 3 Jul 2000 23:17:36 +0900
Reply-To: sarikaya@U-AIZU.AC.JP
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Behcet Sarikaya
Organization: University of Aizu
Subject: Re: [MOBILE-IP] beginners question
X-To: Noam Gonen - Israel
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
--------------0077B70F7EFE9D3C9A962AF3
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Hello,
Just today I posted the handouts of the tutorial entitled
Mobile IP in Cellular Networks
that I presented at IPCN 2000 that was held
on May 23/ 26, 2000 in Paris, France on my homepage at:
http://www.u-aizu.ac.jp/~sarikaya/
just follow the recent presentations link (or presentation.html).
It just may help you to start out.
Have a great summer everyone!
--
Behcet Sarikaya
Computer Communications Lab.
The University of Aizu
Tsuruga, Ikki-machi, Aizu-wakamatsu City
Fukushima, 965-8580 Japan
Tel. +81-242-37-2559 Fax. +81-242-37-2742
Home page: http://www.u-aizu.ac.jp/~sarikaya/
email: sarikaya@u-aizu.ac.jp
--------------0077B70F7EFE9D3C9A962AF3
Content-Type: text/html; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Hello,
Just today I posted the handouts of the tutorial entitled
Mobile IP in Cellular Networks
that I presented at IPCN 2000 that was held
on May 23/ 26, 2000 in Paris, France on my homepage at:
http://www.u-aizu.ac.jp/~sarikaya/
just follow the recent presentations link (or presentation.html).
It just may help you to start out.
Have a great summer everyone!
--
Behcet Sarikaya
Computer Communications Lab.
The University of Aizu
Tsuruga, Ikki-machi, Aizu-wakamatsu City
Fukushima, 965-8580 Japan
Tel. +81-242-37-2559 Fax. +81-242-37-2742
Home page: http://www.u-aizu.ac.jp/~sarikaya/
email: sarikaya@u-aizu.ac.jp
--------------0077B70F7EFE9D3C9A962AF3--
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Mon Jul 3 16:28:58 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07399
for ; Mon, 3 Jul 2000 16:28:58 -0400 (EDT)
Received: from standards (47.234.32.16:3971) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7A8B5@standards.nortelnetworks.com>; Mon, 3 Jul 2000 16:18:44 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 5599 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 3 Jul 2000 16:18:43 -0400
Received: from taurus.cs.albany.edu by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7A8B0@standards.nortelnetworks.com>; Mon, 3 Jul 2000 16:08:43
-0400
Received: from euler.cs.albany.edu (euler.cs.albany.edu [169.226.2.43]) by
taurus.cs.albany.edu (8.9.3+Sun/8.9.1) with ESMTP id QAA13639; Mon, 3
Jul 2000 16:16:33 -0400 (EDT)
Received: (from ravi@localhost) by euler.cs.albany.edu (SMI-8.6/CLI2) id
QAA15531; Mon, 3 Jul 2000 16:16:31 -0400
Message-ID: <200007032016.QAA15531@euler.cs.albany.edu>
Date: Mon, 3 Jul 2000 16:16:31 -0400
Reply-To: "S.S.Ravi"
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "S.S.Ravi"
Subject: [MOBILE-IP] DIAL M Workshop (Early Registration Deadline: July
15, 2000)
X-To: dmanet@zpr.uni-koeln.de, im-net-digest@iwr.uni-heidelberg.de,
itc@ieee.org, manet@itd.nrl.navy.mil, mobility@media.mit.edu,
opt-net@zib.de, orcs-l@listserv.okstate.edu,
podc-post@research.telcordia.com, tccc@ieee.org,
theorynt@listserv.nodak.edu
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
CALL FOR PARTICIPATION
4th International Workshop on Discrete Algorithms and
Methods for Mobile Computing & Communications
(DIALM for Mobility)
August 11, 2000 Boston, Massachusetts, USA
In conjunction with ACM MobiCom 2000
Workshop URL : http://www.eecis.udel.edu/~elloyd/dialm.d/home.html
EARLY REGISTRATION DEADLINE: July 15, 2000
SPONSORS:
(a) National Science Foundation.
(b) ACM SIGMOBILE (in cooperation with ACM SIGACT)
(c) Basic and Applied Simulation Science Group (TSA-2) of
Los Alamos National Laboratory.
SCOPE:
Mobile computing and communications devices such as portable phones,
laptops and palmtops will have an enormous impact on our lifestyle over
the next several decades. The introduction of mobility raises a number
of new research issues. This workshop is devoted to discrete algorithms
and methods in the context of mobile and wireless computing and
communications. The workshop is intended to serve as a forum for open
discussions and lively debate, and to foster cooperation among
practitioners and theoreticians. The conference program includes
three invited talks and 11 contributed papers. The list of contributed
papers and the presentation schedule are available through the workshop
URL given above.
REGISTRATION INFORMATION:
DIAL M Workshop registration is being conducted in conjunction with
the MobiCom 2000 conference registration. Please see the Mobicom 2000
home page (http://www.argreenhouse.com/mobicom2000) for registration
and related information.
STUDENT TRAVEL GRANTS:
Students attending DIAL M may apply for Student Grants to defray a
part of the cost of attending the workshop. Any student may apply
(presenting a paper is NOT a prerequisite). For further information,
please contact the DIAL M Program Chair Professor Errol Lloyd
(elloyd@udel.edu). Funding for these grants is provided by the National
Science Foundation.
INVITED TALKS:
(a) ``Data Structures for Mobile Data'', by Leonidas Guibas
(Stanford University).
(b) ``The Post-PC Era: It's about the New Services-Enabled
Internet'', by Randy Katz (University of California, Berkeley).
(c) ``Application of a Theory of Simulation to Models of
Mobile Communication Systems'', by Chris Barrett
(Los Alamos National Laboratory).
PROGRAM CHAIR: Errol L. Lloyd
Department of Computer and Information Sciences
University of Delaware
Newark, DE, USA
Email: elloyd@udel.edu
PROGRAM COMMITTEE
Amotz Bar-Noy, AT&T Labs and Tel Aviv University, Israel
Anthony Ephremides, University of Maryland, USA
Aura Ganz, University of Massachusetts, USA
Juraj Hromkovic, RWTH Aachen, Germany
Bo Li, Hong Kong University of Science and Technology, Hong Kong
Jason Yi-Bing Lin, National Chiao-Tung University, ROC
Errol Lloyd, University of Delaware,USA -- Program Chair
Madhav Marathe, Los Alamos National Lab
Marina Papatriantafilou, Chalmers Univ. of Technology, Sweden
Stephane Perennes, INRIA, France
Cynthia Phillips, Sandia National Laboratories, USA
Balaji Raghavachari, University of Texas at Dallas, USA
S. S. Ravi, SUNY Albany, USA -- Publicity Chair
Andrea Richa, Arizona State University, USA
Aravind Srinivasan, Bell Labs, USA
Martha Steenstrup, BBN, USA
Subhash Suri, Washington University, USA
Eli Upfal, Brown University, USA
Peter Widmayer, ETH Zurich, Switzerland
STEERING COMMITTEE
Ian Akyildiz, Georgia Tech, USA
Maurizio Bonuccelli, University of Pisa, Italy (Chair)
Afonso Ferreira, CNRS - I3S - INRIA - Sophia Antipolis, France
Arunabha Sen, Arizona State University, USA.
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Mon Jul 3 19:45:58 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08431
for ; Mon, 3 Jul 2000 19:45:57 -0400 (EDT)
Received: from standards (47.234.32.16:2863) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7A909@standards.nortelnetworks.com>; Mon, 3 Jul 2000 19:35:44 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 5720 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 3 Jul 2000 19:35:44 -0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7A908@standards.nortelnetworks.com>; Mon, 3 Jul 2000 19:25:43
-0400
Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net
[207.217.120.24]) by hosaka.smallworks.com (8.9.1/8.9.1) with ESMTP
id SAA14225; Mon, 3 Jul 2000 18:35:24 -0500 (CDT)
Received: from 209.178.164.237 (pool0237.cvx7-bradley.dialup.earthlink.net
[209.178.164.237]) by eagle.prod.itd.earthlink.net
(8.9.3-EL_1_3/8.9.3) with SMTP id QAA04515; Mon, 3 Jul 2000 16:35:06
-0700 (PDT)
X-Priority: 3
X-MSMail-Priority: Normal
Message-ID: <000011134e23$0000442b$00000ade@>
Date: Mon, 3 Jul 2000 16:35:11 -0700
Reply-To: boliver577@HOTMAIL.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: boliver577@HOTMAIL.COM
Subject: [MOBILE-IP] Complete Merchant Services
2782
X-To: Undisclosed.Recipients@earthlink.net
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Are you losing business and customers by not
having your very own Web presence?
Are you currently selling products in an
*Auction House Environment* on the Internet?
Are you losing business because you are unable
to process credit cards and checks over the
Internet?
IF YOU ANSWERED *YES* TO THESE QUESTIONS,
READ ON!
Have Your Online Storefront Built or Build
Your Own Site With the Following Features:
*** E-Commerce - the ability to transact
business on the Internet
*** Web design - creating your own virtual
storefront
*** Web hosting - where your store is located
on the Internet
*** Shopping cart - calculates pricing for
multiple product orders
Secure Processing:
Allows customers to pay with all major credit
cards and checks directly from your Web site
within 2-5 seconds.
*YOU can be vacationing in Hawaii and STILL
making money from your electronic storefront!*
*******************************************************
Please reply to this message with your name,
number and best time to call and we'll answer
all of your questions, and help your build
your own online presence. DOUBLE CLICK ON:
mailto:cardservices1@mailcity.com?subject=interested
*******************************************************
*** QUICK FACTS:
- 161 million people are currently online
- 510 million people are projected to be
online by 2003
- Online shopping will account for $108
billion in sales in 2000, growing from
$7.8 billion in 1998
- Online shopping will account for 6% of all
U.S. retail sales by 2003, growing from 1%
in 1998
This is your chance to have an online
storefront with a fully-integrated shopping
cart solution so that your customers can
purchase many products from your site 24
hours a day, 7 days a week making money
while you sleep!
YOU have the opportunity to be your own
boss, set your own hours and reap all the
benefits of having an electronic business.
BECOME A PART OF THE BIGGEST TRANSFER OF
WEALTH SINCE THE INDUSTRIAL REVOLUTION!
Here's what our customers have to say:
I am a single mom, divorced less than one
year ago, with three small children. I have
no formal education or job experience. I
was headed for the welfare rolls. You showed
me how to build a business on the Internet
and now I am making over $5,000 per month
from my electronic store. I am so grateful,
the Internet has changed my life.
-CG, Idaho
I was a security guard working for a large
company for a $10.00 per hour wage that was
just barely enough to provide for my family
of five. I was laid off in February 1999 and
did not know how to make ends meet. You all
helped me create a business on the Internet.
My e-store currently generates over $10,000
per month in revenue. It took me six months
to make $10,000 at my old job!
-JD, South Dakota
At 72 years old, I was concerned that we
would not have enough financial security for
our remaining years. I just purchased a
computer five months ago and became an
Internet user three months ago. It is easy
to make a profitable business on the
Internet! In just two months, I have paid
for my computer and I am already making
enough money from my referral partnerships
to cover all of my Internet business costs
plus an extra $1,000 per month. Thanks for
getting me up and running.
-JMF, Arizona
*** Do Not Waste Another Day! ***
Our friendly and knowledgeable staff will
answer any and all of your questions.
There is no obligation to buy *ANYTHING*
*******************************************************
Please reply to this message with your name,
number and best time to call and we'll answer
all of your questions, and help your build
your own online presence. DOUBLE CLICK ON:
mailto:cardservices1@mailcity.com?subject=interested
*******************************************************
This email has been delivered to you by the
OPT IN PLUS email delivery service. If you feel
that this has reached you in error please DOUBLE
CLICK ON mailto:remo31@beer.com?subject=unsubscribe
We will insure that your email address is removed
from our database immediately. Thank you for
participating in OPT IN PLUS! We value your membership.
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Tue Jul 4 22:55:42 2000
Received: from standards.nortelnetworks.com ([47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04196
for ; Tue, 4 Jul 2000 22:55:41 -0400 (EDT)
Received: from standards (47.234.32.16:3071) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7AC74@standards.nortelnetworks.com>; Tue, 4 Jul 2000 22:45:09 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 6876 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 4 Jul 2000 22:45:08 -0400
Received: from mcn.xidian.edu.cn by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7AC73@standards.nortelnetworks.com>; Tue, 4 Jul 2000 22:35:06
-0400
Received: from ns1 (jxli [192.168.1.37]) by mcn.xidian.edu.cn (8.9.3/8.8.7)
with SMTP id KAA16404 for ;
Wed, 5 Jul 2000 10:25:56 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_002D_01BFE66E.1FB35260"
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
Message-ID: <003001bfe62b$11d1af40$2501a8c0@xidian.edu.cn>
Date: Wed, 5 Jul 2000 10:45:24 +0800
Reply-To: jxli
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: jxli
Subject: [MOBILE-IP] unsubscribe
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
This is a multi-part message in MIME format.
------=_NextPart_000_002D_01BFE66E.1FB35260
Content-Type: text/plain;
charset="gb2312"
Content-Transfer-Encoding: base64
dW5zdWJzY3JpYmUNCg==
------=_NextPart_000_002D_01BFE66E.1FB35260
Content-Type: text/html;
charset="gb2312"
Content-Transfer-Encoding: base64
PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj51bnN1YnNjcmliZTwvRk9O
VD48L0RJVj48L0JPRFk+PC9IVE1MPg0K
------=_NextPart_000_002D_01BFE66E.1FB35260--
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Wed Jul 5 12:15:41 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10149
for ; Wed, 5 Jul 2000 12:15:40 -0400 (EDT)
Received: from standards (47.234.32.16:2009) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7AECF@standards.nortelnetworks.com>; Wed, 5 Jul 2000 12:05:07 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 7638 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 5 Jul 2000 12:05:07 -0400
Received: from motgate.mot.com by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7AEC6@standards.nortelnetworks.com>; Wed, 5 Jul 2000 11:55:06
-0400
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by
motgate.mot.com (motgate 2.1) with ESMTP id JAA23409 for
; Wed, 5 Jul 2000 09:04:58
-0700 (MST)]
Received: [from il75exm02.cig.mot.com (IL75EXM02.cig.mot.com [136.182.110.102])
by mothost.mot.com (MOT-mothost 2.0) with ESMTP id JAA11071 for
; Wed, 5 Jul 2000 09:04:57
-0700 (MST)]
Received: by IL75EXM02.cig.mot.com with Internet Mail Service (5.5.2650.21) id
; Wed, 5 Jul 2000 11:04:57 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:
Date: Wed, 5 Jul 2000 11:04:49 -0500
Reply-To: Roberts Phil-QA3445
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Roberts Phil-QA3445
Subject: [MOBILE-IP] my email address
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Hi,
it's come to my attention that quite a few people may have a bad email
address for me. Please note that my email address is qa3445@email.mot.com.
This address is the address listed on the web page, but some of you may have
something else through the addressing configuration of a previous email
server that I used. Sorry about the mixup.
Thanks,
Phil
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Wed Jul 5 13:37:30 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12675
for ; Wed, 5 Jul 2000 13:37:28 -0400 (EDT)
Received: from standards (47.234.32.16:4127) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7AF83@standards.nortelnetworks.com>; Wed, 5 Jul 2000 13:27:06 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 7856 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 5 Jul 2000 13:27:06 -0400
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se)
by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with
SMTP id <0.FFB7AF82@standards.nortelnetworks.com>; Wed, 5 Jul 2000
13:27:06 -0400
Received: from esealnt409.al.sw.ericsson.se (esealnt409.al.sw.ericsson.se
[153.88.251.32]) by penguin.wise.edt.ericsson.se
(8.10.1/8.10.1/WIREfire-1.9) with ESMTP id e65Havs05145 for
; Wed, 5 Jul 2000 19:36:57
+0200 (MET DST)
Received: from SMTP ([153.88.251.32]) by esealnt409.al.sw.ericsson.se with
Microsoft SMTPSVC(5.0.2172.1); Wed, 5 Jul 2000 19:36:57 +0200
Received: from esealnt172.ericsson.se ([130.100.184.165]) by 153.88.251.32
(Norton AntiVirus for Internet Email Gateways 1.0) ; Wed, 05 Jul 2000
17:36:56 0000 (GMT)
Received: by esealnt172 with Internet Mail Service (5.5.2651.58) id ;
Wed, 5 Jul 2000 19:36:18 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain; charset="iso-8859-1"
X-OriginalArrivalTime: 05 Jul 2000 17:36:57.0030 (UTC)
FILETIME=[9DC19660:01BFE6A7]
Message-ID: <5F05C89FB2F8D211B6430008C791912703EA80CF@esealnt190>
Date: Wed, 5 Jul 2000 19:36:55 +0200
Reply-To: "Karim El-Malki (ERA)"
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "Karim El-Malki (ERA)"
Subject: [MOBILE-IP] Fast Handoffs (fast-handoffs and proactive-FA)
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Hello Pat and James
I have read your proactive-FA-01 draft. This new version
is quite different from v00 and now describes a similar
hierarchical mechanism to the Fast Handoffs presented
in Adelaide: draft-elmalki-soliman-hmipv4v6-00 (previously
presented in Oslo as draft-elmalki-mobileip-fast-handoffs-01).
This has undergone a few revisions and we think it is
now in quite a stable state. I haven't seen any comparison
or reference to it in your memo. Could you elaborate on the
differences? If my understanding is correct, your approach
requires a registration following L2 handoff (to a new FA)
before the MN can resume communication. We have tried to
avoid this added delay. Also, why did you choose to introduce
a new message between RFA and GFA when there is the
(Regional) Registration Request available? What is the
advantage? MIP transparency to the MN should be maintained
IMO. In our approach we have decided to maintain this and
no new messages are used.
Rgds,
Karim
P.S. The MIPv4 part of the draft presented in Adelaide has
just been resubmitted as: draft-elmalki-mobileip-fast-handoffs-02
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Wed Jul 5 14:36:37 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13710
for ; Wed, 5 Jul 2000 14:36:35 -0400 (EDT)
Received: from standards (47.234.32.16:1900) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B006@standards.nortelnetworks.com>; Wed, 5 Jul 2000 14:26:07 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 8014 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 5 Jul 2000 14:26:07 -0400
Received: from qhars002.nortel.com (47.101.112.102:36464) by
standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP
id <0.FFB7AFFD@standards.nortelnetworks.com>; Wed, 5 Jul 2000
14:16:06 -0400
Received: from smtprch1.nortel.com (actually erchg0j) by qhars002.nortel.com;
Wed, 5 Jul 2000 19:22:52 +0100
Received: from zrchb200.us.nortel.com (actually zrchb200) by
smtprch1.nortel.com; Wed, 5 Jul 2000 12:50:43 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2650.21) id
<3F6D4GNL>; Wed, 5 Jul 2000 12:52:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01BFE6A9.D5F42BD6"
Message-ID:
Date: Wed, 5 Jul 2000 12:52:50 -0500
Reply-To: Glenn Morrow
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Glenn Morrow
Subject: [MOBILE-IP] Security Questions for Mobility in IPv6 Drafts
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
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_01BFE6A9.D5F42BD6
Content-Type: text/plain
Excuse me but can the binding update option be encrypted for security
purposes?
If not, do people feel it should be?
If so, would IPv6 security have to be altered in some way or do people
believe there should be some encryption that is option specific?
------_=_NextPart_001_01BFE6A9.D5F42BD6
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
Security Questions for Mobility in IPv6 Drafts
Excuse me but can the binding update =
option be encrypted for security purposes?
If not, do people feel it should =
be?
If so, would IPv6 security have to be =
altered in some way or do people believe there should be some =
encryption that is option specific?
------_=_NextPart_001_01BFE6A9.D5F42BD6--
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Wed Jul 5 16:03:25 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15796
for ; Wed, 5 Jul 2000 16:03:25 -0400 (EDT)
Received: from standards (47.234.32.16:1900) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B123@standards.nortelnetworks.com>; Wed, 5 Jul 2000 15:53:08 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 8400 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 5 Jul 2000 15:53:08 -0400
Received: from lukla.Sun.COM by standards.nortelnetworks.com (LSMTP for Windows
NT v1.1b) with SMTP id <0.FFB7B122@standards.nortelnetworks.com>;
Wed, 5 Jul 2000 15:53:08 -0400
Received: from engmail1.Eng.Sun.COM ([129.146.1.13]) by lukla.Sun.COM
(8.9.3+Sun/8.9.3) with ESMTP id OAA24011 for
; Wed, 5 Jul 2000 14:02:59
-0600 (MDT)
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,v1.7) with ESMTP id
NAA19405; Wed, 5 Jul 2000 13:02:56 -0700 (PDT)
Received: from suntana (suntana [129.146.122.88]) by nasnfs.eng.sun.com
(8.9.3+Sun/8.9.1) with SMTP id NAA03553; Wed, 5 Jul 2000 13:02:55
-0700 (PDT)
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: xKcoa/msKgMyXFpY6dkr2Q==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.2 SunOS 5.7 sun4u sparc
Message-ID: <200007052002.NAA03553@nasnfs.eng.sun.com>
Date: Wed, 5 Jul 2000 13:06:53 -0700
Reply-To: James Kempf
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: James Kempf
Subject: Re: [MOBILE-IP] Fast Handoffs (fast-handoffs and proactive-FA)
X-To: Karim.El-Malki@ERA.ERICSSON.SE
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
>I have read your proactive-FA-01 draft. This new version
>is quite different from v00 and now describes a similar
>hierarchical mechanism to the Fast Handoffs presented
>in Adelaide: draft-elmalki-soliman-hmipv4v6-00 (previously
>presented in Oslo as draft-elmalki-mobileip-fast-handoffs-01).
>This has undergone a few revisions and we think it is
>now in quite a stable state. I haven't seen any comparison
>or reference to it in your memo. Could you elaborate on the
>differences? If my understanding is correct, your approach
I haven't had a chance to read it. I will take a look at it.
>requires a registration following L2 handoff (to a new FA)
See below for more on this.
>before the MN can resume communication. We have tried to
>avoid this added delay. Also, why did you choose to introduce
The MN starts getting packets as soon as the FA and GFA
have set up the registration. There is no need for the MN
to do any registration back to the HA because the GFA has
not changed.
>a new message between RFA and GFA when there is the
>(Regional) Registration Request available? What is the
>advantage? MIP transparency to the MN should be maintained
>IMO. In our approach we have decided to maintain this and
>no new messages are used.
>
I'll take a look and see if I can give you a more detailed answer.
>Rgds,
>Karim
>
>P.S. The MIPv4 part of the draft presented in Adelaide has
>just been resubmitted as: draft-elmalki-mobileip-fast-handoffs-02
Regarding your statement about L2 handoff, there is additionally a
need to do handoff when there is no L2 connection between the old
and new RANs. I'm thinking about the CDMA hard handoff case here,
in which there is no physical interconnection directly between
the old and new RAN, and so the handoff must go through the
L3 core (currently, this is done by involving the MSCs in handoff).
This will, of necessity, involve communicating radio specific
information across L3, channel parameters, current cell site, etc.
We believe FA assisted handoff as we have outlined it will handle
this case, with an extension to carry the radio specific information
needed in order to have the new RAN set up the handoff. Does your
proposal work for this as well?
jak
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Wed Jul 5 17:32:02 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17500
for ; Wed, 5 Jul 2000 17:32:02 -0400 (EDT)
Received: from standards (47.234.32.16:4074) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B1A7@standards.nortelnetworks.com>; Wed, 5 Jul 2000 17:21:49 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 8572 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 5 Jul 2000 17:21:49 -0400
Received: from melimelo.enst-bretagne.fr by standards.nortelnetworks.com (LSMTP
for Windows NT v1.1b) with SMTP id
<0.FFB7B1A6@standards.nortelnetworks.com>; Wed, 5 Jul 2000 17:21:48
-0400
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr
[192.44.77.1]) by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with
ESMTP id e65LVZ646332; Wed, 5 Jul 2000 23:31:35 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
[193.52.74.194]) by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with
ESMTP id XAA21925; Wed, 5 Jul 2000 23:31:29 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr
[127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with
ESMTP id XAA46607; Wed, 5 Jul 2000 23:33:01 +0200 (CEST)
(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-ID: <200007052133.XAA46607@givry.rennes.enst-bretagne.fr>
Date: Wed, 5 Jul 2000 23:33:01 +0200
Reply-To: Francis.Dupont@ENST-BRETAGNE.FR
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Francis Dupont
Subject: Re: [MOBILE-IP] Security Questions for Mobility in IPv6 Drafts
X-To: Glenn Morrow
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To: Your message of Wed, 05 Jul 2000 12:52:50 CDT.
In your previous mail you wrote:
Excuse me but can the binding update option be encrypted for security
purposes?
=> it may but there is an issue if the home address option (which
must be in the same packet) is encrypted because the security association
should use it.
If so, would IPv6 security have to be altered in some way or do people
believe there should be some encryption that is option specific?
=> the only thing which has to be altered is the recommended order
of IPv6 extension headers: ESP must be after the destination option
header which carries the home address. The constraints are:
- the home address option must be before any IPsec header
(then tunnel mode doesn't work)
- there must be an AH header with anti-replay
The binding update can be after or before the home address option
and any IPsec header, in the same or a different destination option
header than the home address.
Francis.Dupont@enst-bretagne.fr
PS: for instance in my code (which works with IPsec and negociates
SA with IKE) you get:
IPv6 header:
src = care-of address
dst = home agent address
Dest-option header:
Binding Update
Home Address (with the home address)
Auth-header (with SPI for mobile home address -> home agent address SA)
No-next-header (empty)
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 04:43:36 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09725
for ; Thu, 6 Jul 2000 04:43:35 -0400 (EDT)
Received: from standards (47.234.32.16:2245) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B3F9@standards.nortelnetworks.com>; Thu, 6 Jul 2000 4:32:59 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 9315 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 04:32:58 -0400
Received: from ish7.ericsson.com.au (203.61.155.111:42517) by
standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP
id <0.FFB7B3F8@standards.nortelnetworks.com>; Thu, 6 Jul 2000 4:32:57
-0400
Received: from brsi02.epa.ericsson.se (brsi02 [146.11.15.8]) by
ish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id SAA29373; Thu, 6
Jul 2000 18:41:32 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165]) by
brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id SAA27679; Thu, 6
Jul 2000 18:42:38 +1000 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service
(5.5.2650.21) id <3FW9RALN>; Thu, 6 Jul 2000 18:42:27 +1000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01BFE726.1D3A0B60"
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A5089EB0F3@eaubrnt018.epa.ericsson.se>
Date: Thu, 6 Jul 2000 18:42:27 +1000
Reply-To: "Hesham Soliman (EPA)"
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "Hesham Soliman (EPA)"
Subject: Re: [MOBILE-IP] Security Questions for Mobility in IPv6 Drafts
X-To: Francis Dupont
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
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_01BFE726.1D3A0B60
Content-Type: text/plain
The binding update can be after or before the home address option
and any IPsec header, in the same or a different destination option
header than the home address.
I think we should be careful with this case though, because if you place the
BU after the ESP header it probably won't work through the translators.
Which would impact the V6 <-> V4 communication.
PS: for instance in my code (which works with IPsec and negociates
SA with IKE) you get:
IPv6 header:
src = care-of address
dst = home agent address
Dest-option header:
Binding Update
Home Address (with the home address)
Auth-header (with SPI for mobile home address -> home agent address SA)
No-next-header (empty)
Yes this is great but placing BU after the IPsec header will be a problem
for the migration mechanisms available today.
------_=_NextPart_001_01BFE726.1D3A0B60
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
RE: [MOBILE-IP] Security Questions for Mobility in IPv6 =
Drafts
The binding update can be after or before the home =
address option
and any IPsec header, in the same or a different =
destination option
header than the home address.
I think we should be careful with this case though, =
because if you place the BU after the ESP header it probably won't work =
through the translators. Which would impact the V6 <-> V4 =
communication.
PS: for instance in my code (which works with IPsec =
and negociates
SA with IKE) you get:
IPv6 header:
src =3D care-of address
dst =3D home agent address
Dest-option header:
Binding Update
Home Address (with the home address)
Auth-header (with SPI for mobile home address -> =
home agent address SA)
No-next-header (empty)
Yes this is great but placing BU after the IPsec =
header will be a problem for the migration mechanisms available =
today.
------_=_NextPart_001_01BFE726.1D3A0B60--
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 05:24:41 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09995
for ; Thu, 6 Jul 2000 05:24:41 -0400 (EDT)
Received: from standards (47.234.32.16:2245) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B44E@standards.nortelnetworks.com>; Thu, 6 Jul 2000 5:14:22 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 9422 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 05:14:22 -0400
Received: from mcn.xidian.edu.cn by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7B44D@standards.nortelnetworks.com>; Thu, 6 Jul 2000 5:12:51
-0400
Received: from ns1 (jxli [192.168.1.37]) by mcn.xidian.edu.cn (8.9.3/8.8.7)
with SMTP id QAA18658; Thu, 6 Jul 2000 16:57:47 -0800
References: <5F05C89FB2F8D211B6430008C791912703EA80CF@esealnt190>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
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
Message-ID: <001001bfe72a$f7bc03c0$2501a8c0@xidian.edu.cn>
Date: Thu, 6 Jul 2000 17:17:10 +0800
Reply-To: jxli
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: jxli
Subject: Re: [MOBILE-IP] Fast Handoffs (fast-handoffs and proactive-FA)
X-To: "Karim El-Malki (ERA)"
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id FAA09995
unsubscribe
----- Original Message -----
From: Karim El-Malki (ERA)
To:
Sent: Thursday, July 06, 2000 1:36 AM
Subject: [MOBILE-IP] Fast Handoffs (fast-handoffs and proactive-FA)
> Hello Pat and James
>
> I have read your proactive-FA-01 draft. This new version
> is quite different from v00 and now describes a similar
> hierarchical mechanism to the Fast Handoffs presented
> in Adelaide: draft-elmalki-soliman-hmipv4v6-00 (previously
> presented in Oslo as draft-elmalki-mobileip-fast-handoffs-01).
> This has undergone a few revisions and we think it is
> now in quite a stable state. I haven't seen any comparison
> or reference to it in your memo. Could you elaborate on the
> differences? If my understanding is correct, your approach
> requires a registration following L2 handoff (to a new FA)
> before the MN can resume communication. We have tried to
> avoid this added delay. Also, why did you choose to introduce
> a new message between RFA and GFA when there is the
> (Regional) Registration Request available? What is the
> advantage? MIP transparency to the MN should be maintained
> IMO. In our approach we have decided to maintain this and
> no new messages are used.
>
> Rgds,
> Karim
>
> P.S. The MIPv4 part of the draft presented in Adelaide has
> just been resubmitted as: draft-elmalki-mobileip-fast-handoffs-02
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 05:31:33 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10106
for ; Thu, 6 Jul 2000 05:31:33 -0400 (EDT)
Received: from standards (47.234.32.16:2245) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B47E@standards.nortelnetworks.com>; Thu, 6 Jul 2000 5:21:16 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 9485 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 05:21:16 -0400
Received: from melimelo.enst-bretagne.fr by standards.nortelnetworks.com (LSMTP
for Windows NT v1.1b) with SMTP id
<0.FFB7B47D@standards.nortelnetworks.com>; Thu, 6 Jul 2000 5:21:15
-0400
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr
[192.44.77.1]) by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with
ESMTP id e669Uv614508; Thu, 6 Jul 2000 11:30:58 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
[193.52.74.194]) by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with
ESMTP id LAA27602; Thu, 6 Jul 2000 11:30:57 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr
[127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with
ESMTP id LAA48919; Thu, 6 Jul 2000 11:32:36 +0200 (CEST)
(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-ID: <200007060932.LAA48919@givry.rennes.enst-bretagne.fr>
Date: Thu, 6 Jul 2000 11:32:36 +0200
Reply-To: Francis.Dupont@ENST-BRETAGNE.FR
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Francis Dupont
Subject: Re: [MOBILE-IP] Security Questions for Mobility in IPv6 Drafts
X-To: "Hesham Soliman (EPA)"
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To: Your message of Thu, 06 Jul 2000 18:42:27 +1000.
<4B6BC00CD15FD2119E5F0008C7A419A5089EB0F3@eaubrnt018.epa.ericsson.se>
In your previous mail you wrote:
>The binding update can be after or before the home address option
>and any IPsec header, in the same or a different destination option
>header than the home address.
I think we should be careful with this case though, because if you place the
BU after the ESP header it probably won't work through the translators.
Which would impact the V6 <-> V4 communication.
=> I don't believe in a V6 <-> V4 translator with mobility support
(for instance IPv4 source-routing is not available in the today Internet
for many reasons).
Yes this is great but placing BU after the IPsec header will be a problem
for the migration mechanisms available today.
=> it is a problem for firewalls too. I am in favour of a SHOULD (for
BU in the same header than HA) but we can't sell a MUST here.
I believe the I-D 12 doesn't specify this because to do the right thing
is more simple...
Regards
Francis.Dupont@enst-bretagne.fr
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 05:42:25 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10182
for ; Thu, 6 Jul 2000 05:42:25 -0400 (EDT)
Received: from standards (47.234.32.16:2245) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B4BB@standards.nortelnetworks.com>; Thu, 6 Jul 2000 5:32:08 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 9559 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 05:32:08 -0400
Received: from mcn.xidian.edu.cn by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7B4BA@standards.nortelnetworks.com>; Thu, 6 Jul 2000 5:32:05
-0400
Received: from ns1 (jxli [192.168.1.37]) by mcn.xidian.edu.cn (8.9.3/8.8.7)
with SMTP id RAA18746 for ;
Thu, 6 Jul 2000 17:23:07 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0038_01BFE771.8F1E1FA0"
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
Message-ID: <003b01bfe72e$810ba880$2501a8c0@xidian.edu.cn>
Date: Thu, 6 Jul 2000 17:42:30 +0800
Reply-To: jxli
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: jxli
Subject: [MOBILE-IP]
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
This is a multi-part message in MIME format.
------=_NextPart_000_0038_01BFE771.8F1E1FA0
Content-Type: text/plain;
charset="gb2312"
Content-Transfer-Encoding: base64
dW5zdWJzY3JpYmUganhsaUBtY24ueGlkaWFuLmVkdS5jbg0K
------=_NextPart_000_0038_01BFE771.8F1E1FA0
Content-Type: text/html;
charset="gb2312"
Content-Transfer-Encoding: base64
PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj51bnN1YnNjcmliZSA8QSAN
CmhyZWY9Im1haWx0bzpqeGxpQG1jbi54aWRpYW4uZWR1LmNuIj5qeGxpQG1jbi54aWRpYW4uZWR1
LmNuPC9BPjwvRk9OVD48L0RJVj48L0JPRFk+PC9IVE1MPg0K
------=_NextPart_000_0038_01BFE771.8F1E1FA0--
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 05:45:51 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10206
for ; Thu, 6 Jul 2000 05:45:51 -0400 (EDT)
Received: from standards (47.234.32.16:2245) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B4E3@standards.nortelnetworks.com>; Thu, 6 Jul 2000 5:34:15 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 9606 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 05:34:15 -0400
Received: from mcn.xidian.edu.cn by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7B4E0@standards.nortelnetworks.com>; Thu, 6 Jul 2000 5:34:12
-0400
Received: from ns1 (jxli [192.168.1.37]) by mcn.xidian.edu.cn (8.9.3/8.8.7)
with SMTP id RAA18731 for ;
Thu, 6 Jul 2000 17:21:39 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0022_01BFE771.5AF6AEE0"
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
Message-ID: <002501bfe72e$4ced5f80$2501a8c0@xidian.edu.cn>
Date: Thu, 6 Jul 2000 17:41:03 +0800
Reply-To: jxli
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: jxli
Subject: [MOBILE-IP] unsubscribe
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
This is a multi-part message in MIME format.
------=_NextPart_000_0022_01BFE771.5AF6AEE0
Content-Type: text/plain;
charset="gb2312"
Content-Transfer-Encoding: base64
DQo=
------=_NextPart_000_0022_01BFE771.5AF6AEE0
Content-Type: text/html;
charset="gb2312"
Content-Transfer-Encoding: base64
PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPiZuYnNwOzwvRElWPjwvQk9EWT48L0hUTUw+DQo=
------=_NextPart_000_0022_01BFE771.5AF6AEE0--
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 05:54:46 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10208
for ; Thu, 6 Jul 2000 05:45:51 -0400 (EDT)
Received: from standards (47.234.32.16:2245) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B4E5@standards.nortelnetworks.com>; Thu, 6 Jul 2000 5:34:19 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 9609 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 05:34:19 -0400
Received: from mcn.xidian.edu.cn by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7B4B5@standards.nortelnetworks.com>; Thu, 6 Jul 2000 5:31:34
-0400
Received: from ns1 (jxli [192.168.1.37]) by mcn.xidian.edu.cn (8.9.3/8.8.7)
with SMTP id RAA18738 for ;
Thu, 6 Jul 2000 17:22:23 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_002F_01BFE771.75382E00"
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
Message-ID: <003201bfe72e$672edea0$2501a8c0@xidian.edu.cn>
Date: Thu, 6 Jul 2000 17:41:47 +0800
Reply-To: jxli
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: jxli
Subject: [MOBILE-IP]
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
This is a multi-part message in MIME format.
------=_NextPart_000_002F_01BFE771.75382E00
Content-Type: text/plain;
charset="gb2312"
Content-Transfer-Encoding: base64
dW5zdWJzY3JpYmUNCg==
------=_NextPart_000_002F_01BFE771.75382E00
Content-Type: text/html;
charset="gb2312"
Content-Transfer-Encoding: base64
PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj51bnN1YnNjcmliZTwvRk9O
VD48L0RJVj48L0JPRFk+PC9IVE1MPg0K
------=_NextPart_000_002F_01BFE771.75382E00--
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 06:09:23 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10343
for ; Thu, 6 Jul 2000 06:09:23 -0400 (EDT)
Received: from standards (47.234.32.16:2245) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B583@standards.nortelnetworks.com>; Thu, 6 Jul 2000 5:59:09 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 9805 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 05:59:09 -0400
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se)
by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with
SMTP id <0.FFB7B582@standards.nortelnetworks.com>; Thu, 6 Jul 2000
5:59:04 -0400
Received: from esealnt409.al.sw.ericsson.se (esealnt409.al.sw.ericsson.se
[153.88.251.32]) by penguin.wise.edt.ericsson.se
(8.10.1/8.10.1/WIREfire-1.9) with ESMTP id e66A8qs23450 for
; Thu, 6 Jul 2000 12:08:52
+0200 (MET DST)
Received: from SMTP ([153.88.251.32]) by esealnt409.al.sw.ericsson.se with
Microsoft SMTPSVC(5.0.2172.1); Thu, 6 Jul 2000 12:08:51 +0200
Received: from esealnt172.ericsson.se ([130.100.184.165]) by 153.88.251.32
(Norton AntiVirus for Internet Email Gateways 1.0) ; Thu, 06 Jul 2000
10:08:51 0000 (GMT)
Received: by esealnt172 with Internet Mail Service (5.5.2651.58) id ;
Thu, 6 Jul 2000 12:08:11 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain; charset="iso-8859-1"
X-OriginalArrivalTime: 06 Jul 2000 10:08:51.0499 (UTC)
FILETIME=[2F24DFB0:01BFE732]
Message-ID: <5F05C89FB2F8D211B6430008C791912703EA80D0@esealnt190>
Date: Thu, 6 Jul 2000 12:08:47 +0200
Reply-To: "Karim El-Malki (ERA)"
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "Karim El-Malki (ERA)"
Subject: Re: [MOBILE-IP] Fast Handoffs (fast-handoffs and proactive-FA)
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Hello James
> The MN starts getting packets as soon as the FA and GFA
> have set up the registration. There is no need for the MN
> to do any registration back to the HA because the GFA has
> not changed.
Of course this is true in Regional Registrations and therefore
also in our approach. However my question is: following
movement to a new RFA, the MN cannot resume communication
until it has performed a regional registration with the new RFA.
Are you saying that the previous RFA registers with the new RFA
and the new RFA registers with the GFA without involving the MN?
(using the BU and a "surrogate" registration which would be your
new handoff request message) If so, wouldn't this break RFC2002
which requires the MN to send the Registration Request for a
binding with a FA to be established?
>
> Regarding your statement about L2 handoff, there is additionally a
> need to do handoff when there is no L2 connection between the old
> and new RANs. I'm thinking about the CDMA hard handoff case here,
> in which there is no physical interconnection directly between
> the old and new RAN, and so the handoff must go through the
> L3 core (currently, this is done by involving the MSCs in handoff).
> This will, of necessity, involve communicating radio specific
> information across L3, channel parameters, current cell site, etc.
> We believe FA assisted handoff as we have outlined it will handle
> this case, with an extension to carry the radio specific information
> needed in order to have the new RAN set up the handoff. Does your
> proposal work for this as well?
>
Our proposal describes a way to do an L3 Fast Handoff possibly utilising
L2 functions/information. The lack of a soft-handoff does not mean
there will not be a L2 interface to the radio/cellular specific part
of the network (which exists today). From your mail above I conclude
that you take a different assumption: L3 interface to the radio network.
Am I correct? I think that radio-specific information should be left to
L2 since it is an overkill to bring complex radio-technology-specific
parameters up to L3. This is also due to the fact that every radio/cellular
standard has its set of parameters. Only a few L2 parameters need to be
made visible to L3 (e.g. handoff indication), possibly through some API
to obtain the improved handoffs which we are aiming for. This is the
assumption we should work with IMO, since it allows us to define a generic
L3 (MIP) fast handoff method.
Rgds,
Karim
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 07:46:01 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12756
for ; Thu, 6 Jul 2000 07:46:01 -0400 (EDT)
Received: from standards (47.234.32.16:3465) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B62B@standards.nortelnetworks.com>; Thu, 6 Jul 2000 7:35:37 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 10019 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 07:35:37 -0400
Received: from ish7.ericsson.com.au (203.61.155.111:44090) by
standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP
id <0.FFB7B62A@standards.nortelnetworks.com>; Thu, 6 Jul 2000 7:35:35
-0400
Received: from brsi02.epa.ericsson.se (brsi02 [146.11.15.8]) by
ish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id VAA03626; Thu, 6
Jul 2000 21:44:08 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165]) by
brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id VAA06235; Thu, 6
Jul 2000 21:45:14 +1000 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service
(5.5.2650.21) id <3FW9RCAH>; Thu, 6 Jul 2000 21:45:03 +1000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01BFE73F.9F5CD3C0"
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A5089EB0F5@eaubrnt018.epa.ericsson.se>
Date: Thu, 6 Jul 2000 21:45:03 +1000
Reply-To: "Hesham Soliman (EPA)"
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "Hesham Soliman (EPA)"
Subject: Re: [MOBILE-IP] Security Questions for Mobility in IPv6 Drafts
X-To: Francis Dupont
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
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_01BFE73F.9F5CD3C0
Content-Type: text/plain
I think we should be careful with this case though, because if you
place the
BU after the ESP header it probably won't work through the
translators.
Which would impact the V6 <-> V4 communication.
=> I don't believe in a V6 <-> V4 translator with mobility support
(for instance IPv4 source-routing is not available in the today Internet
for many reasons).
I don't really understand what that means. Are you against translators that
support mobility ? I'm not sure how source routing is related to this.
Yes this is great but placing BU after the IPsec header will be a
problem
for the migration mechanisms available today.
=> it is a problem for firewalls too. I am in favour of a SHOULD (for
BU in the same header than HA) but we can't sell a MUST here.
I believe the I-D 12 doesn't specify this because to do the right thing
is more simple...
Maybe it should be stated in the relevant translator drafts instead of the
MIPv6 draft ? We have a draft for NGTRANS and this is one of the topics
addressed. Hopefully coming out soon.
Cheers,
Hesham
------_=_NextPart_001_01BFE73F.9F5CD3C0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
RE: [MOBILE-IP] Security Questions for Mobility in IPv6 Drafts =
I think we should be careful with this =
case though, because if you
place the
BU after the ESP header it probably =
won't work through the
translators.
Which would impact the V6 <-> V4 =
communication.
=3D> I don't believe in a V6 <-> V4 =
translator with mobility support
(for instance IPv4 source-routing is not available =
in the today Internet
for many reasons).
I don't really understand what that means. Are you =
against translators that support mobility ? I'm not sure how source =
routing is related to this.
Yes this is great but placing BU after =
the IPsec header will be a
problem
for the migration mechanisms available =
today.
=3D> it is a problem for firewalls too. I am in =
favour of a SHOULD (for
BU in the same header than HA) but we can't sell a =
MUST here.
I believe the I-D 12 doesn't specify this because to =
do the right thing
is more simple...
Maybe it should be stated in the relevant translator =
drafts instead of the MIPv6 draft ? We have a draft for NGTRANS and =
this is one of the topics addressed. Hopefully coming out =
soon.
Cheers,
Hesham
------_=_NextPart_001_01BFE73F.9F5CD3C0--
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 09:47:47 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16331
for ; Thu, 6 Jul 2000 09:47:46 -0400 (EDT)
Received: from standards (47.234.32.16:2122) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B69B@standards.nortelnetworks.com>; Thu, 6 Jul 2000 9:37:23 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 10157 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 09:37:22 -0400
Received: from lukla.Sun.COM by standards.nortelnetworks.com (LSMTP for Windows
NT v1.1b) with SMTP id <0.FFB7B69A@standards.nortelnetworks.com>;
Thu, 6 Jul 2000 9:37:22 -0400
Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by lukla.Sun.COM
(8.9.3+Sun/8.9.3) with ESMTP id HAA16613 for
; Thu, 6 Jul 2000 07:47:15
-0600 (MDT)
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,v1.7) with ESMTP id
GAA28176; Thu, 6 Jul 2000 06:47:13 -0700 (PDT)
Received: from mordor (mordor [129.146.120.122]) by nasnfs.eng.sun.com
(8.9.3+Sun/8.9.1) with SMTP id GAA26387; Thu, 6 Jul 2000 06:47:12
-0700 (PDT)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Message-ID:
Date: Thu, 6 Jul 2000 06:46:30 -0700
Reply-To: "pcalhoun@eng.sun.com"
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "pcalhoun@eng.sun.com"
Subject: Re: [MOBILE-IP] Fast Handoffs (fast-handoffs and proactive-FA)
X-To: "Karim El-Malki (ERA)"
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To: "Your message with ID"
<5F05C89FB2F8D211B6430008C791912703EA80D0@esealnt190>
> Hello James
>
> > The MN starts getting packets as soon as the FA and GFA
> > have set up the registration. There is no need for the MN
> > to do any registration back to the HA because the GFA has
> > not changed.
>
> Of course this is true in Regional Registrations and therefore
> also in our approach. However my question is: following
> movement to a new RFA, the MN cannot resume communication
> until it has performed a regional registration with the new RFA.
> Are you saying that the previous RFA registers with the new RFA
> and the new RFA registers with the GFA without involving the MN?
> (using the BU and a "surrogate" registration which would be your
> new handoff request message) If so, wouldn't this break RFC2002
> which requires the MN to send the Registration Request for a
> binding with a FA to be established?
No it doesn't break RFC 2002 anymore than Regional Registration Does. The main
idea is to let the GFA be aware that the Mobile Node is entering a new cell,
before MN registration occurs. This allows the network to adjust itself to
provide service to the Mobile Node when it does enter the cell.
The inverse requires that the Mobile Node detects it has entered a new cell by
receiving (or soliciting) an advertisement, then proceed with the registration
process. If we can provide temporary service while the registration process is
occuring, then we have what I would call hard hand-off. There would be nearly
no service impact (read packet loss) to the Mobile Node, especially if both
the old and new cell overlap.
Of course, the "temporary" registration is just that, temporary. We still
require that the Mobile Node issues a regional registration within a specified
amount of time.
>
> >
> > Regarding your statement about L2 handoff, there is additionally a
> > need to do handoff when there is no L2 connection between the old
> > and new RANs. I'm thinking about the CDMA hard handoff case here,
> > in which there is no physical interconnection directly between
> > the old and new RAN, and so the handoff must go through the
> > L3 core (currently, this is done by involving the MSCs in handoff).
> > This will, of necessity, involve communicating radio specific
> > information across L3, channel parameters, current cell site, etc.
> > We believe FA assisted handoff as we have outlined it will handle
> > this case, with an extension to carry the radio specific information
> > needed in order to have the new RAN set up the handoff. Does your
> > proposal work for this as well?
> >
>
> Our proposal describes a way to do an L3 Fast Handoff possibly utilising
> L2 functions/information. The lack of a soft-handoff does not mean
> there will not be a L2 interface to the radio/cellular specific part
> of the network (which exists today). From your mail above I conclude
> that you take a different assumption: L3 interface to the radio network.
> Am I correct? I think that radio-specific information should be left to
> L2 since it is an overkill to bring complex radio-technology-specific
> parameters up to L3. This is also due to the fact that every radio/cellular
> standard has its set of parameters. Only a few L2 parameters need to be
> made visible to L3 (e.g. handoff indication), possibly through some API
> to obtain the improved handoffs which we are aiming for. This is the
> assumption we should work with IMO, since it allows us to define a generic
> L3 (MIP) fast handoff method.
Well, James eluded to another draft, which isn't even published yet, and has
no bearings on the pro-active FA draft. The proposal does not require that we
pass along layer 2 information, and it would work just fine without it.
Similarly to your proposal, we assume that the Foreign Agent will receive an
indication from the layer 2 when the Mobile is entering a new cell. This draft
does define a generic L3 fast handoff method.
PatC
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 10:23:23 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17019
for ; Thu, 6 Jul 2000 10:23:23 -0400 (EDT)
Received: from standards (47.234.32.16:2122) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B6F7@standards.nortelnetworks.com>; Thu, 6 Jul 2000 10:12:56 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 10270 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 10:12:55 -0400
Received: from scarlatti.cs.colostate.edu by standards.nortelnetworks.com
(LSMTP for Windows NT v1.1b) with SMTP id
<0.FFB7B6F4@standards.nortelnetworks.com>; Thu, 6 Jul 2000 10:02:54
-0400
Received: (from gupta@localhost) by scarlatti.cs.colostate.edu (8.9.3/8.9.3) id
IAA29750 for MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000
08:12:48 -0600 (MDT)
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <200007061412.IAA29750@scarlatti.cs.colostate.edu>
Date: Thu, 6 Jul 2000 08:12:48 -0600
Reply-To: Sandeep Gupta
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Sandeep Gupta
Subject: [MOBILE-IP] CFP PERVASIVE COMPUTING
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit
Call for Papers
IEEE Personal Communications Magzine
Special Issue on Pervasive Computing
Publication Date: April 2001
http://www.cs.colostate.edu/~gupta/pervasiveComp-cfp.html
SCOPE:
The importance of pervasive or ubiquitous computing is rapidly
increasing with the current trend towards universal presence of mobile
computing, computer networks, and wireless communication in everyday
life. The word pervasive means having power to spread
throughout. Pervasive Computing essentially means to enable network
devices to be aware of their surroundings and peers, and to be capable
of providing services to and using services from peers effectively.
The purpose of this special issue is to bring together the researchers
and practitioners working on diverse aspects of this important
emerging area in order to identify current status, fundamental issues,
future problems and applications. We invite papers describing both
theoretical and experimental research as well as experience reports
and vision papers. Specific areas of interest include (but are not
limited to):
- Computing and communication Paradigms
- Infrastructures Issues
- Data Management Issues
- Security and Authentication Issues
- E-commerce
- Service Issues: Interface and Semantics
- Discovery/Advertisement and Applications
- Resource Discovery and Utilization
- Power Conservation
- User Interfaces
- Agents, Brokers
- Information Sharing, Access, Storage and Management
- Dynamic Context (e.g., time, space, and events)
- Enabling Technologies
Papers should report well-defined innovative ideas and practical
results in real-life applications; they should include evaluations
through analysis, simulation and experiments. Papers must be written
in the IEEE Personal Communications style. Please submit your
manuscript to either of the guest editors by September 30, 2000 :
Wang-Chien Lee
GTE Laboratories Inc.
40 Sylvan Road
Waltham, MA 02451
Voice: (781) 466-3321
Fax: (781) 466-4387
wlee@gte.com
Sandeep K. S. Gupta
Dept. of Computer Science
Colorado State University
Ft. Collins, CO 80523
Voice: (970) 491-7323
Fax: (970) 491-2466
gupta@cs.colostate.edu
Apratim Purakayastha
IBM T.J. Watson Research Center
30 Saw Mill River Road
Hawthorne, NY 10532
Voice: (914) 784-7004
Fax: (914) 784-3812
apu@us.ibm.com
Pradip K. Srimani
Dept. of Computer Science
Colorado State University
Ft. Collins, CO 80523
Voice: (970) 491-7097
Fax: (970) 491-2466
srimani@CS.ColoState.Edu
Instructions for submitting papers: Papers should include a 200 word
abstract and five to ten index words. Authors must follow the IEEE
Personal Communications guidelines regarding the manuscript and its
format. For more details, please refer to "Information for Authors" in
each IEEE Personal Communications issue, or check
guidelines. Electronic submissions are strongly encouraged.
Schedule:
Submission Deadline September 30, 2000
Acceptance Decision January 10, 2001
Final manuscript February 15, 2001
Publication April, 2001
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 10:26:48 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17095
for ; Thu, 6 Jul 2000 10:26:48 -0400 (EDT)
Received: from standards (47.234.32.16:2122) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B722@standards.nortelnetworks.com>; Thu, 6 Jul 2000 10:16:11 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 10327 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 10:16:11 -0400
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se)
by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with
SMTP id <0.FFB7B721@standards.nortelnetworks.com>; Thu, 6 Jul 2000
10:16:11 -0400
Received: from esealnt409.al.sw.ericsson.se (esealnt409.al.sw.ericsson.se
[153.88.251.32]) by penguin.wise.edt.ericsson.se
(8.10.1/8.10.1/WIREfire-1.9) with ESMTP id e66EQ4s19216 for
; Thu, 6 Jul 2000 16:26:04
+0200 (MET DST)
Received: from SMTP ([153.88.251.32]) by esealnt409.al.sw.ericsson.se with
Microsoft SMTPSVC(5.0.2172.1); Thu, 6 Jul 2000 16:26:04 +0200
Received: from esealnt172.ericsson.se ([130.100.184.165]) by 153.88.251.32
(Norton AntiVirus for Internet Email Gateways 1.0) ; Thu, 06 Jul 2000
14:26:04 0000 (GMT)
Received: by esealnt172 with Internet Mail Service (5.5.2651.58) id ;
Thu, 6 Jul 2000 16:25:24 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain; charset="iso-8859-1"
X-OriginalArrivalTime: 06 Jul 2000 14:26:04.0698 (UTC)
FILETIME=[1E0C27A0:01BFE756]
Message-ID: <5F05C89FB2F8D211B6430008C791912703EA80D4@esealnt190>
Date: Thu, 6 Jul 2000 16:25:45 +0200
Reply-To: "Karim El-Malki (ERA)"
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "Karim El-Malki (ERA)"
Subject: Re: [MOBILE-IP] Fast Handoffs (fast-handoffs and proactive-FA)
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Hello Pat
> No it doesn't break RFC 2002 anymore than Regional
> Registration Does. The main
> idea is to let the GFA be aware that the Mobile Node is
> entering a new cell,
> before MN registration occurs. This allows the network to
> adjust itself to
> provide service to the Mobile Node when it does enter the cell.
Regional Registration messages are sent by the MN to the RFA.
Your draft however makes the MN unaware that the network is
setting up bindings for it. This is the reason why I think that
it does not do the same as Regional Registrations with respect
to RFC2002. Also, your new handoff request message is basically
a surrogate or proxy Registration Request message. IMO it is
possible to do without a new message (see below).
You also refer to entering the "cell" above. I think that we
should not involve specific cellular issues when considering
a generic L3 fast handoff mechanism.
>
> The inverse requires that the Mobile Node detects it has
> entered a new cell by
> receiving (or soliciting) an advertisement, then proceed
> with the registration
> process.
There is another option though, which is the one we have chosen
and presented in Adelaide. Have you had a look at this?
The MN may register with the new FA through the old wireless
access point.
Rgds,
Karim
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 12:03:26 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19573
for ; Thu, 6 Jul 2000 12:03:26 -0400 (EDT)
Received: from standards (47.234.32.16:1574) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B7D2@standards.nortelnetworks.com>; Thu, 6 Jul 2000 11:52:59 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 0139 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 11:52:59 -0400
Received: from lukla.Sun.COM by standards.nortelnetworks.com (LSMTP for Windows
NT v1.1b) with SMTP id <0.FFB7B7D1@standards.nortelnetworks.com>;
Thu, 6 Jul 2000 11:52:58 -0400
Received: from engmail1.Eng.Sun.COM ([129.146.1.13]) by lukla.Sun.COM
(8.9.3+Sun/8.9.3) with ESMTP id KAA18932 for
; Thu, 6 Jul 2000 10:02:52
-0600 (MDT)
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,v1.7) with ESMTP id
JAA10221; Thu, 6 Jul 2000 09:02:50 -0700 (PDT)
Received: from suntana (suntana [129.146.122.88]) by nasnfs.eng.sun.com
(8.9.3+Sun/8.9.1) with SMTP id JAA29802; Thu, 6 Jul 2000 09:02:44
-0700 (PDT)
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: DkXI0WIZQKbfPmu6YE6Flg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.2 SunOS 5.7 sun4u sparc
Message-ID: <200007061602.JAA29802@nasnfs.eng.sun.com>
Date: Thu, 6 Jul 2000 09:06:43 -0700
Reply-To: James Kempf
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: James Kempf
Subject: Re: [MOBILE-IP] Fast Handoffs (fast-handoffs and proactive-FA)
X-To: Karim.El-Malki@ERA.ERICSSON.SE
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
>> Regarding your statement about L2 handoff, there is additionally a
>> need to do handoff when there is no L2 connection between the old
>> and new RANs. I'm thinking about the CDMA hard handoff case here,
>> in which there is no physical interconnection directly between
>> the old and new RAN, and so the handoff must go through the
>> L3 core (currently, this is done by involving the MSCs in handoff).
>> This will, of necessity, involve communicating radio specific
>> information across L3, channel parameters, current cell site, etc.
>> We believe FA assisted handoff as we have outlined it will handle
>> this case, with an extension to carry the radio specific information
>> needed in order to have the new RAN set up the handoff. Does your
>> proposal work for this as well?
>>
>
>Our proposal describes a way to do an L3 Fast Handoff possibly utilising
>L2 functions/information. The lack of a soft-handoff does not mean
>there will not be a L2 interface to the radio/cellular specific part
>of the network (which exists today). From your mail above I conclude
>that you take a different assumption: L3 interface to the radio network.
>Am I correct? I think that radio-specific information should be left to
As Pat indicated in his reply, there is no requirement for an L3
interface to the radio network in our draft. Our draft is independent
of L2.
>L2 since it is an overkill to bring complex radio-technology-specific
>parameters up to L3. This is also due to the fact that every radio/cellular
>standard has its set of parameters. Only a few L2 parameters need to be
>made visible to L3 (e.g. handoff indication), possibly through some API
>to obtain the improved handoffs which we are aiming for. This is the
>assumption we should work with IMO, since it allows us to define a generic
>L3 (MIP) fast handoff method.
>
I think it should be possible to allow radio specific parameters to
be exchanged between FAs that can handle them in a way that is generic
enough to handle multiple kinds of radio link technologies. L3 would
be used just for exchange of radio-link specific information, nothing more. For
CDMA and TDMA technologies, I don't believe a single parameter or generic set of
parameters will be sufficient to handle hard handoff between noninterconnected
RANs, i.e. the hard handoff case. There is otherwise no way for the two
RANs to find out information on the channel and cell that the mobile is
using in order to perform the handoff.
Whether or not the mobile IP working group, or even IETF, is the right
place for defining this is another question. It may be something
more appropriate for the 3G arena.
jak
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 13:14:23 2000
Received: from standards.nortelnetworks.com ([47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21360
for ; Thu, 6 Jul 2000 13:14:23 -0400 (EDT)
Received: from standards (47.234.32.16:3790) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B841@standards.nortelnetworks.com>; Thu, 6 Jul 2000 13:03:52 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 0280 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 13:03:51 -0400
Received: from melimelo.enst-bretagne.fr by standards.nortelnetworks.com (LSMTP
for Windows NT v1.1b) with SMTP id
<0.FFB7B840@standards.nortelnetworks.com>; Thu, 6 Jul 2000 13:03:51
-0400
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr
[192.44.77.1]) by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with
ESMTP id e66HDa604116; Thu, 6 Jul 2000 19:13:36 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
[193.52.74.194]) by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with
ESMTP id TAA03713; Thu, 6 Jul 2000 19:13:35 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr
[127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with
ESMTP id TAA50311; Thu, 6 Jul 2000 19:15:16 +0200 (CEST)
(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-ID: <200007061715.TAA50311@givry.rennes.enst-bretagne.fr>
Date: Thu, 6 Jul 2000 19:15:16 +0200
Reply-To: Francis.Dupont@ENST-BRETAGNE.FR
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Francis Dupont
Subject: Re: [MOBILE-IP] Security Questions for Mobility in IPv6 Drafts
X-To: "Hesham Soliman (EPA)"
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To: Your message of Thu, 06 Jul 2000 21:45:03 +1000.
<4B6BC00CD15FD2119E5F0008C7A419A5089EB0F5@eaubrnt018.epa.ericsson.se>
In your previous mail you wrote:
=> I don't believe in a V6 <-> V4 translator with mobility support
(for instance IPv4 source-routing is not available in the today Internet
for many reasons).
I don't really understand what that means. Are you against translators that
support mobility ?
=> I am not against translators that support mobility, I just believe it
is not possible for a translator to support mobility (but we have to
define what is to support mobility too :-).
I'm not sure how source routing is related to this.
=> IPv6 mobility uses source routing and if a translator translates
an IPv6 source route header to an IPv4 source route option the next
router will likely drop the packet on the floor: this doesn't work!
Yes this is great but placing BU after the IPsec header will be a
problem for the migration mechanisms available today.
=> it is a problem for firewalls too. I am in favour of a SHOULD (for
BU in the same header than HA) but we can't sell a MUST here.
I believe the I-D 12 doesn't specify this because to do the right thing
is more simple...
Maybe it should be stated in the relevant translator drafts instead of the
MIPv6 draft ? We have a draft for NGTRANS and this is one of the topics
addressed. Hopefully coming out soon.
=> if you cannot justify a MUST then the place you put the SHOULD is not
really important... In fact if someone is using ESP (with a real cipher)
then both translators and firewalls will have some problems (you have
to explain how to deal with headers and data which are not in the clear part).
Regards
Francis.Dupont@enst-bretagne.fr
PS: in fact I've disliked translators since I proposed to use them for
TUBA. There are too many ugly little details and no good solution for
address translation. I prefer clean design like DSTM!
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 18:44:40 2000
Received: from standards.nortelnetworks.com ([47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26949
for ; Thu, 6 Jul 2000 18:44:38 -0400 (EDT)
Received: from standards (47.234.32.16:2787) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B97A@standards.nortelnetworks.com>; Thu, 6 Jul 2000 18:34:10 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 0671 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 18:34:10 -0400
Received: from cheetah.cs.ucla.edu by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7B977@standards.nortelnetworks.com>; Thu, 6 Jul 2000 18:24:09
-0400
Received: from localhost (sjlee@localhost) by cheetah.cs.ucla.edu
(8.9.1/UCLACS-5.0) with ESMTP id PAA26629; Thu, 6 Jul 2000 15:33:54
-0700 (PDT)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-ID:
Date: Thu, 6 Jul 2000 15:33:54 -0700
Reply-To: SJ Lee
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: SJ Lee
Subject: [MOBILE-IP] MobiHOC 2000: Call for Participation
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
[Please accept our apologies if you receive duplicate messages]
==================================================================
Announcement & Call for Participation
THE FIRST ANNUAL WORKSHOP ON
MOBILE AD HOC NETWORKING & COMPUTING
(MobiHOC 2000)
in conjunction with Mobicom 2000
August 11, 2000
Boston, Massachusetts, USA
Advance program, registration information, and hotel
information for the MobiHOC workshop are now available at
http://www.cs.tamu.edu/faculty/vaidya/mobihoc/
If you are unable to access the above web page, please
send an e-mail to vaidya@cs.tamu.edu
--------------------------------------------------------------------------
MobiHOC 2000 Advance Program
--------------------------------------------------------------------------
MobiHoc received 82 submissions, of which 13 were accepted as regular
papers, and 12 as posters. The accepted papers/posters came from 13
countries.
--------------------------------------------------------------------------
Keynote
Leonard Kleinrock will present a keynote address on Beyond the Netherworld
of Cyberspace.
--------------------------------------------------------------------------
Introductions and Welcome
8:00 - 8:30 a.m.
--------------------------------------------------------------------------
Session A: Routing
8:30 - 10:15 a.m.
Session Chair: David B. Johnson, CMU and Rice University
* On the Impact of Alternate Path Routing for Load Balancing in Mobile
Ad-Hoc Networks
Marc Pearlman, Zygmunt Haas (Cornell University), Peter Sholander
(Scientific Research Corporation), and Siamak S. Tabrizi (Air Force
Rome Laboratories)
* LANMAR: Landmark Routing for Large Scale Wireless Ad Hoc Networks with
Group Mobility
Guangyu Pei, Mario Gerla, and Xiaoyan Hong (University of California,
Los Angeles)
* DDR-Distributed Dynamic Routing Algorithm for Mobile Ad Hoc Networks
Navid Nikaein, Houda Labiod, and Christian Bonnet (Eurecom Institute)
* Predicting Node Proximity in Ad-Hoc Networks: A Least Overhead Adaptive
Model for Selecting Stable Routes
A. Bruce McDonald and Taieb Znati (University of Pittsburgh)
--------------------------------------------------------------------------
Session B: Multicasting
10:45 - 12:00 a.m.
Session Chair: Joseph Macker, Naval Research Laboratory
* Neighbor Supporting Ad Hoc Multicast Routing Protocol
Seungjoon Lee and Chongkwon Kim (Seoul National University)
* Role-Based Multicast in Highly Mobile but Sparsely Connected Ad Hoc
Networks
Linda Briesemeister (DaimlerChrysler Research and Technology) and
Gunter Hommel (Technical University of Berlin)
* Content Based Multicast (CBM) in Ad Hoc Networks
Hu Zhou and Suresh Singh (Oregon State University)
--------------------------------------------------------------------------
Keynote Address and Lunch
12:00 - 1:30 p.m.
Keynote Speaker: Leonard Kleinrock
Topic: Beyond the Netherworld of Cyberspace
--------------------------------------------------------------------------
Session C: Novel Issues
1:30 - 2:45 p.m.
Session Chair: Andrew Campbell, Columbia University
* An Architecture for Building Self-Configurable Systems
Lakshminarayanan Subramanian and Randy H. Katz (University of
California, Berkeley)
* MIPMANET - Mobile IP for Mobile Ad Hoc Networks
Ulf Jonsson, Fredrik Alriksson, Tony Larsson, Per Johansson (Ericsson
Radio Systems), and Gerald Q. Maguire Jr. (Royal Institute of
Technology)
* Enforcing Service Availability in Mobile Ad-Hoc WANs
Levente Buttyan and Jean-Pierre Hubaux (Swiss Federal Institute of
Technology, Lausanne)
--------------------------------------------------------------------------
Session D: Link Layer
3:15 - 4:30 p.m.
Session Chair: Fred L. Templin, SRI International
* Fair Medium Access in 802.11 based Wireless Ad-Hoc Networks
Brahim Bensaou, Yu Wang, and Chi Chung Ko (National University of
Singapore)
* Low Power Rendezvous in Embedded Wireless Networks
Terry Todd (McMaster University), Frazer Bennett (PA Consulting Group),
and Alan Jones (AT&T Laboratories Cambridge)
* Assignment Methods for Spatial Reuse TDMA
Jimmi Gronkvist (Swedish Defence Research Establishment)
--------------------------------------------------------------------------
Poster Session
4:30 - 6:00 p.m.
Session Chair: TBA
* A Speech-Optimised Multiple Access Scheme for a Mobile Ad Hoc Network
V. N. Muthiah and W. C. Wong (National University of Singapore)
* On the Reduction of Broadcast Redundancy in Mobile Ad Hoc Networks
Wei Peng and Xi-Cheng Lu (Changsha Institute of Technology)
* Central Controller Handover Procedure for ETSI-BRAN HiperLAN/2 Ad Hoc
Networks and Clustering with Quality of Service Guarantees
Jorg Habetha, Andreas Hettich, Jorg Peetz (Aachen Institute of
Technology), and Yonggang Du (Philips Research Laboratories)
* DEAPspace -- Transient Ad-hoc Networking of Pervasive Devices
Reto Hermann, Dirk Husemann, Michael Moser, Michael Nidd, Christian
Rohner, and Andreas Schade (IBM Zurich Research Lab)
* Securing Ad Hoc Services, a Jini View
Christian Gehrmann (Ericsson Research), and Pekka Nikander (Helsinki
Institute of Technology)
* Dynamic Quality-of-Service for Mobile Ad Hoc Networks
M. Mirhakkak, N. Schult, and D. Thomson (MITRE Corporation)
* A Simulation Analysis on Reactive Route Repair Techniques for QoS
Sensitive Applications in Mobile Ad Hoc Networks
George Aggelou and Rahim Tafazolli (University of Surrey)
* Proximity Awareness and Fast Connection Establishment in Bluetooth
Theodoros Salonidis (University of Maryland), Pravin Bhagwat (IBM T. J.
Watson Research Center), and Leandros Tassiulas (University of
Maryland)
* Utility-Based Decision-Making in Wireless Sensor Networks
John Byers and Gabriel Nasser (Boston University)
* A Distributed Mechanism for Topology Discovery in Ad hoc Wireless
Networks using Mobile Agents
Romit RoyChoudhury (Haldia Institute of Technology), Somprakash
Bandyopadhyay (PricewaterhouseCoopers Ltd.), and Krishna Paul
(CTS-Calcutta)
* Performance Aspects of Bluetooth Scatternet Formation
G. Miklos, A. Racz, Z. Turanyi, A. Valko (Ericsson Research), and P.
Johansson (Ericsson Radio Systems)
* Load Balancing via Relay in Next Generation Wireless Systems
Chunming Qiao, Hongyi Wu, and Ozan Tonguz (University at Buffalo)
--------------------------------------------------------------------------
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Thu Jul 6 18:47:57 2000
Received: from standards.nortelnetworks.com ([47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26985
for ; Thu, 6 Jul 2000 18:47:57 -0400 (EDT)
Received: from standards (47.234.32.16:2787) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7B9B8@standards.nortelnetworks.com>; Thu, 6 Jul 2000 18:37:37 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 0752 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 6 Jul 2000 18:37:37 -0400
Received: from turin.trillium.com (38.187.146.197:4455) by
standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP
id <0.FFB7B9B7@standards.nortelnetworks.com>; Thu, 6 Jul 2000
18:37:37 -0400
Received: from aiglos.trillium.com (smtp.trillium.com) by turin.trillium.com
(Content Technologies SMTPRS 4.1.5) with ESMTP id
for
; Thu, 6 Jul 2000 16:01:22
-0700
Received: from aega.trillium.com (aega.trillium.com [192.168.1.19]) by
aiglos.trillium.com (8.9.3/8.9.3) with ESMTP id PAA29865 for
; Thu, 6 Jul 2000 15:47:28
-0700 (PDT)
Received: by aega.trillium.com with Internet Mail Service (5.5.2650.21) id
; Thu, 6 Jul 2000 15:43:50 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <8BBD33A986C5D311804000902719FF5D952B42@aega.trillium.com>
Date: Thu, 6 Jul 2000 15:43:49 -0700
Reply-To: Prem Shankar Sharma
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Prem Shankar Sharma
Subject: [MOBILE-IP] some queries on
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Hi,
I have some questions on the draft .
Though it proposes some interesting schemes to imbibe MPLS techniques
in Mobile IP, to enhance data efficiency (packet header compression
techniques), expedite data forwarding and to use of CRLSPs for QoS
requirements, but I feel, it doesn't fully address some of the issues.
* This draft doesn't address the cases when the route optimization
techniques are employed. What if they are employed? Can the LSPs
could be established directly from CN to FA or from CN to MN? What
if CN is not MPLS capable? What if MN itself is MPLS capable?
[not fully sure whether these questions need to be handled within
this draft or some other work on MPLS].
* How the packets in transit are going to be handled during handoff?
Can a "short lived" LSP be provisioned between the old FA and the
new FA. The new FA could be the HA itself. If such data driven
LSPs are provisioned, what are going to be their implications on
the scalability of the soln.?
Besides this, in section 2.4, there seems to be a typo - It says
"HA strips off the label and sends the packet to IP layer". Instead of
HA, it should have been FA.
Looking for the responses!!!
Thanks.
Prem
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Fri Jul 7 05:00:34 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18966
for ; Fri, 7 Jul 2000 05:00:34 -0400 (EDT)
Received: from standards (47.234.32.16:4941) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7BCDF@standards.nortelnetworks.com>; Fri, 7 Jul 2000 4:49:53 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 1811 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 7 Jul 2000 04:49:52 -0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7BCDA@standards.nortelnetworks.com>; Fri, 7 Jul 2000 4:39:52
-0400
Received: from emu.prod.itd.earthlink.net (emu.prod.itd.earthlink.net
[207.217.121.31]) by hosaka.smallworks.com (8.9.1/8.9.1) with ESMTP
id DAA07062; Fri, 7 Jul 2000 03:49:47 -0500 (CDT)
Received: from 209.179.245.134 (pool0389.cvx19-bradley.dialup.earthlink.net
[209.179.245.134]) by emu.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3)
with SMTP id BAA22710; Fri, 7 Jul 2000 01:49:36 -0700 (PDT)
X-Priority: 3
X-MSMail-Priority: Normal
Message-ID: <000004f6670c$00004f21$00000b04@>
Date: Fri, 7 Jul 2000 01:25:24 -0700
Reply-To: cardacct2505@HOTMAIL.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: cardacct2505@HOTMAIL.COM
Subject: [MOBILE-IP] Merchant Account - No Setup Fee
2820
X-To: Undisclosed.Recipients@earthlink.net
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
HOW TO SUBSTANTIALLY INCREASE SALES:
Easily accept major credit cards right away!
Act now and all Setup & App. fees waived
********************************************************
For Free Setup DOUBLE CLICK ON:
mailto:cardacct4@mailcity.com?subject=merchant_interested
Include your name, phone number and best time to call.
Or you can call 1(888) 242-8260 now! Our courteous
customer care reps are anxious to help you get your
merchant account today.
********************************************************
Merchant Status will help you increase sales by an
incredible 50% to 400%. Stop losing valuable sales!
With one phone call you can be:
Accepting all major credit cards!
Accepting checks over the net or by Fax!
Accepting real time processing for member sites!
Gaining costumer loyalty and trust!
Close the sale now. No more wondering if "The check
is in the mail"
We specialize in helping those entrepreneurs who
are just starting out: no credit, poor credit, or
even if you have great credit.
Almost everyone is approved!
For the next 5 days we will waive all Setup & App.
fees! (other companies charge $200 to $500 to set up)
In Business since 1992
********************************************************
For Free Setup DOUBLE CLICK ON:
mailto:cardacct4@mailcity.com?subject=merchant_interested
Include your name, phone number and best time to call.
Or you can call 1(888) 242-8260 now! Our courteous
customer care reps are anxious to help you get your
merchant account today.
********************************************************
This email has been delivered to you by the OPT IN PLUS email
delivery service. If you feel that this has reached you in error please
DOUBLE CLICK ON mailto:remov1@yahoo.com?subject=unsubscribe
We will insure that your email address is removed from our database
immediately. Thank you for participating in OPT IN PLUS!
We value your membership.
HOW TO SUBSTANTIALLY INCREASE SALES:
Easily accept major credit cards right away!
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Fri Jul 7 05:28:44 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19154
for ; Fri, 7 Jul 2000 05:28:44 -0400 (EDT)
Received: from standards (47.234.32.16:3009) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7BD4F@standards.nortelnetworks.com>; Fri, 7 Jul 2000 5:18:09 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 1975 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 7 Jul 2000 05:18:09 -0400
Received: from ish7.ericsson.com.au (203.61.155.111:61121) by
standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP
id <0.FFB7BD4E@standards.nortelnetworks.com>; Fri, 7 Jul 2000 5:18:08
-0400
Received: from brsi02.epa.ericsson.se (brsi02 [146.11.15.8]) by
ish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id TAA26312; Fri, 7
Jul 2000 19:26:46 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165]) by
brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id TAA07725; Fri, 7
Jul 2000 19:27:53 +1000 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service
(5.5.2650.21) id <3FW9RV1Y>; Fri, 7 Jul 2000 19:27:43 +1000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01BFE7F5.99FEF550"
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A5089EB0FE@eaubrnt018.epa.ericsson.se>
Date: Fri, 7 Jul 2000 19:27:42 +1000
Reply-To: "Hesham Soliman (EPA)"
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "Hesham Soliman (EPA)"
Subject: Re: [MOBILE-IP] Security Questions for Mobility in IPv6 Drafts
X-To: Francis Dupont
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
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_01BFE7F5.99FEF550
Content-Type: text/plain
In your previous mail you wrote:
=> I don't believe in a V6 <-> V4 translator with mobility support
(for instance IPv4 source-routing is not available in the today
Internet
for many reasons).
I don't really understand what that means. Are you against
translators that
support mobility ?
=> I am not against translators that support mobility, I just believe it
is not possible for a translator to support mobility (but we have to
define what is to support mobility too :-).
That's right, we need to define minimum level of support.
As you say translation of options is going to be really difficult.
I meant minimum support that allows an IPv6 MN to talk to an
IPv4 MN. That's actually fairly straight forward.
PS: in fact I've disliked translators since I proposed to use them for
TUBA. There are too many ugly little details and no good solution for
address translation. I prefer clean design like DSTM!
Well DSTM doesn't solve the same problem. If you have a small
device that can't have a dual stack then you need a translator.
I suppose that's getting beyond this list.
But anyway our solution combines both, translators and DSTM.
I'll look forward to the discussion in the NGTRANS meeting.
------_=_NextPart_001_01BFE7F5.99FEF550
Content-Type: text/html
RE: [MOBILE-IP] Security Questions for Mobility in IPv6 Drafts
In your previous mail you wrote:
=> I don't believe in a V6 <-> V4 translator with mobility support
(for instance IPv4 source-routing is not available in the today
Internet
for many reasons).
I don't really understand what that means. Are you against
translators that
support mobility ?
=> I am not against translators that support mobility, I just believe it
is not possible for a translator to support mobility (but we have to
define what is to support mobility too :-).
That's right, we need to define minimum level of support.
As you say translation of options is going to be really difficult.
I meant minimum support that allows an IPv6 MN to talk to an
IPv4 MN. That's actually fairly straight forward.
PS: in fact I've disliked translators since I proposed to use them for
TUBA. There are too many ugly little details and no good solution for
address translation. I prefer clean design like DSTM!
Well DSTM doesn't solve the same problem. If you have a small
device that can't have a dual stack then you need a translator.
I suppose that's getting beyond this list.
But anyway our solution combines both, translators and DSTM.
I'll look forward to the discussion in the NGTRANS meeting.
------_=_NextPart_001_01BFE7F5.99FEF550--
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Fri Jul 7 07:02:40 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20137
for ; Fri, 7 Jul 2000 07:02:40 -0400 (EDT)
Received: from standards (47.234.32.16:3009) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7BDFB@standards.nortelnetworks.com>; Fri, 7 Jul 2000 6:52:12 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 2191 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 7 Jul 2000 06:52:12 -0400
Received: from ietf.org (odin.ietf.org) by standards.nortelnetworks.com (LSMTP
for Windows NT v1.1b) with SMTP id
<0.FFB7BDF1@standards.nortelnetworks.com>; Fri, 7 Jul 2000 6:42:12
-0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org
(8.9.1a/8.9.1a) with ESMTP id GAA19957; Fri, 7 Jul 2000 06:52:08
-0400 (EDT)
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Message-ID: <200007071052.GAA19957@ietf.org>
Date: Fri, 7 Jul 2000 06:52:08 -0400
Reply-To: Internet-Drafts@ietf.org
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
Comments: RFC822 error: Incorrect or incomplete address field found and
ignored.
From: Internet-Drafts@ietf.org
Subject: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-aaa-reqs-04.txt
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
--NextPart
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP Routing for Wireless/Mobile Hosts Working Group of the IETF.
Title : Mobile IP Authentication, Authorization, and
Accounting Requirements
Author(s) : S. Glass, T. Hiller, S. Jacobs, C. Perkins
Filename : draft-ietf-mobileip-aaa-reqs-04.txt
Pages : 25
Date : 06-Jul-00
The Mobile IP and AAA working groups are currently looking at
defining the requirements for Authentication, Authorization, and
Accounting. This document contains the requirements which would
have to be supported by a AAA service to aid in providing Mobile IP
services.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mobileip-aaa-reqs-04.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-mobileip-aaa-reqs-04.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-mobileip-aaa-reqs-04.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: <20000706151851.I-D@ietf.org>
ENCODING mime
FILE /internet-drafts/draft-ietf-mobileip-aaa-reqs-04.txt
--OtherAccess
Content-Type: Message/External-body;
name="draft-ietf-mobileip-aaa-reqs-04.txt";
site="ftp.ietf.org";
access-type="anon-ftp";
directory="internet-drafts"
Content-Type: text/plain
Content-ID: <20000706151851.I-D@ietf.org>
--OtherAccess--
--NextPart--
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Fri Jul 7 08:17:05 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22861
for ; Fri, 7 Jul 2000 08:17:05 -0400 (EDT)
Received: from standards (47.234.32.16:4966) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7BE8A@standards.nortelnetworks.com>; Fri, 7 Jul 2000 8:06:42 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 2384 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 7 Jul 2000 08:06:42 -0400
Received: from cedar.dcs.shef.ac.uk by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7BE89@standards.nortelnetworks.com>; Fri, 7 Jul 2000 8:06:42
-0400
Received: from borg (borg.dcs.shef.ac.uk [143.167.11.44]) by
cedar.dcs.shef.ac.uk (8.9.3+Sun/8.9.3) with SMTP id NAA23464; Fri, 7
Jul 2000 13:16:30 +0100 (BST)
References:
<395A0645.92D77115@informatik.tu-muenchen.de>
<01e001bfe5bb$d012c7c0$2c0ba78f@dcs.shef.ac.uk>
<3961F064.879E82E8@informatik.tu-muenchen.de>
<020d01bfe5c7$341f91c0$2c0ba78f@dcs.shef.ac.uk>
<3961FEE4.C16E36F0@informatik.tu-muenchen.de>
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.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <018801bfe80d$7c2b61e0$2c0ba78f@dcs.shef.ac.uk>
Date: Fri, 7 Jul 2000 13:18:39 +0100
Reply-To: Chern Nam Yap
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Chern Nam Yap
Subject: Re: [MOBILE-IP] Fast Handovers/offs
X-To: Wolfgang Liebl
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit
Hi
> >
> > Currently I am working in the area of IIP (attachment)
> > and very interested on get information about cell size
> > and one's own location within a cell to calculate the
> > expected cell visiting time before handover to another
> > cell and herewith possibly to handoff to another subnetwork,
> > that hence improves handoff in IIP.
>
> I guess that IIP is that imaging prot. and thus on top of IP or tcp, isn't
it?
My apology that I don't understand what you mean by imaging prot.
IIP is an mobility mangement protocol that sits on top of TCP/IP, without
changing TCP/IP.
I have look through the you slides.
How do you got the information for the converage area of any data network
(LAN and MAN)?
Thanks and Regards
----------------------------------------------------------------------------
---
Chern Nam Yap
Research Associate
Center for Mobile Communication Research
Department of Electronic and Electrical Engineering
University of Sheffield
Regent Court
211 Portobello Street
Sheffield S1 4DP
United Kingdom
Tel:+44 (0) 114-222-3308
Fax:+44 (0) 114-222-8299
Web: www.mobile1.net
E-mail: cny@dcs.shef.ac.uk
E-mail: cny@ieee.org
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Fri Jul 7 11:13:31 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29181
for ; Fri, 7 Jul 2000 11:13:31 -0400 (EDT)
Received: from standards (47.234.32.16:2702) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7BFA2@standards.nortelnetworks.com>; Fri, 7 Jul 2000 11:01:16 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 2734 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 7 Jul 2000 11:01:16 -0400
Received: from cedar.dcs.shef.ac.uk by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7BF9C@standards.nortelnetworks.com>; Fri, 7 Jul 2000 11:01:15
-0400
Received: from borg (borg.dcs.shef.ac.uk [143.167.11.44]) by
cedar.dcs.shef.ac.uk (8.9.3+Sun/8.9.3) with SMTP id QAA10347; Fri, 7
Jul 2000 16:06:42 +0100 (BST)
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.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <026401bfe825$a6891960$2c0ba78f@dcs.shef.ac.uk>
Date: Fri, 7 Jul 2000 16:08:11 +0100
Reply-To: Chern Nam Yap
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Chern Nam Yap
Subject: Re: [MOBILE-IP] why IIP?
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit
Hi
Even though IIP is not meant to solve every problem,
but IIP trying to resolve what Mobile IP can't resolve currently.
Such as
1) Trianglar routing
For MIPv4 is still stuck with Triangluar routing and Reverse Tunnelling.
2) Signalling Traffic,
Current mobility protocols generate too much traffic and low
reliability.
3) Topology Complexity for fast hand off for IPv4 and IPv6,
Hierarchical model is far too complex just to solve handoff problem.
4) Mobility transition between IPv4 and IPv6.
Any node meant for MIPv4 would not work in MIPv6 environment, via visa.
Cheers
----------------------------------------------------------------------------
---
Chern Nam Yap
Research Associate
Center for Mobile Communication Research
Department of Electronic and Electrical Engineering
University of Sheffield
Regent Court
211 Portobello Street
Sheffield S1 4DP
United Kingdom
Tel:+44 (0) 114-222-3308
Fax:+44 (0) 114-222-8299
Web: www.mobile1.net
E-mail: cny@dcs.shef.ac.uk
E-mail: cny@ieee.org
>
>
>
>
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Fri Jul 7 22:39:53 2000
Received: from standards.nortelnetworks.com ([47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18811
for ; Fri, 7 Jul 2000 22:39:52 -0400 (EDT)
Received: from standards (47.234.32.16:4792) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7C16C@standards.nortelnetworks.com>; Fri, 7 Jul 2000 22:29:15 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 3301 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 7 Jul 2000 22:29:15 -0400
Received: from hansolm (210.112.10.141:18665) by standards.nortelnetworks.com
(LSMTP for Windows NT v1.1b) with SMTP id
<0.FFB7C16B@standards.nortelnetworks.com>; Fri, 7 Jul 2000 22:19:14
-0400
Received: from ns ([210.112.7.7]) by hansolm with Microsoft
SMTPSVC(5.5.1877.197.19); Sat, 8 Jul 2000 11:27: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
Message-ID: <009c01bfe884$63e8ee00$d012060a@hansol.co.kr>
Date: Sat, 8 Jul 2000 11:29:47 +0900
Reply-To: "Lee, Jiwoong"
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "Lee, Jiwoong"
Subject: [MOBILE-IP] Terms: Home Link vs Home Network
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit
Dear Authors of ,
Whereas RFC2002bis defines "Home Network" and uses this term generally,
Mobility Support in IPv6 defines "Home
Link"
instead of "Home Network" while
uses "Home Link" together with "Home Network" through this docuemnt.
Do you try to express particular meaning when the term "Home Link" is used
instead of "Home Network"? How about the mixed use of these two terms?
I appreciate your comment.
J Lee
M.com
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Sat Jul 8 00:18:02 2000
Received: from standards.nortelnetworks.com ([47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19992
for ; Sat, 8 Jul 2000 00:18:02 -0400 (EDT)
Received: from standards (47.234.32.16:3278) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7C1CB@standards.nortelnetworks.com>; Sat, 8 Jul 2000 0:07:34 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 3406 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Sat, 8 Jul 2000 00:07:34 -0400
Received: from default (c07-207.006.popsite.net) by
standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP
id <0.FFB7C1BD@standards.nortelnetworks.com>; Fri, 7 Jul 2000
23:57:30 -0400
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:
Date: Sat, 8 Jul 2000 00:07:34 -0400
Reply-To: LifeTime Homes
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: LifeTime Homes
Subject: [MOBILE-IP] LifeTime Homes
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
"Lifetime Homes"
You are invited to sign up to be a
"Lifetime Homes" Distributors (Worldwide).
Become our distributor (free), and get your free web site.
We Close All The Sales For You, You Do Nothing
But Have People Look At Your FREE Web Site
That We Put Up For You In 24 Hours With Your
Company Name On It And Collect 15% To 20% .
Your Site Will Have Photos, Floor plans, And Pricing!
The housing business is booming and we have only
scratched 1% of the market.
Click Here To See The Web Site:
Your FREE Web Site Will Look Just Like Mine.
http://www.lifetime-homes.com/SteelHomes/ajr/start.html
Earn as much as $9,500 Per sale with us!! As a Life
time Homes Associate, you'll be selling quality steel
framed homes manufactured by Tri-Steel Structures,
Inc., one of the largest manufacturer in the world
and earn 15% to 20% commissions per home sold. These
home packages come pre-cut ready to assemble.
Our business opportunity is worldwide. We currently
ship home packages to over 50 countries which has
made us one of the largest distributors of this
phenomenal product. From small homes to commercial
office buildings, we are sure you will find our
business opportunity the best out there as you breeze
through our various pages and floor plans.
Take a look at the PAY PLAN below:
1st $60,000 home...earn US$9,000 (15% commission)
2nd $60,000 home...earn US$9,000 (15% commission)
3rd $60,000 home...earn US$9,000 (15% commission)
4th $60,000 home...earn US$12,000 (20% commission)
Your Total Income from selling 4 homes = US$39,000
>From your 4th home sold and up, you'll earn 20%
commission.
Imagine what your earning will be when you sell one
of our $100,000 metal homes? Please Preview our
website for only (INFORMATION PURPOSES) at
http://www.lifetime-homes.com/SteelHomes/ajr/start.html
To become our distributor (free), and get your free
website, Fill out the CONTRACT AGREEMENT form below.
Email Back To: lifetimehomes@yahoo.com
or print and fill in the agent agreement form
and fax back to 1-888-584-7194 ( TOLL FREE )
Make sure you complete every aspect of this form for
easier processing. THANK YOU
----------------- APPLICATION ---------------------
NEW ASSOCIATE DISTRIBUTOR AGREEMENT
( NO COST- FREE TO SIGN UP )
Tri-Steel Structures, Inc.
Sponsored by: Anthony J. Russo Sr.
Russo Communication Group
Lifetime Homes Independent Authorized Distributor
1-888-584-7194 Toll Free
Yes, I want to be an Independent Authorized Associate
Distributor to refer Steel Framed Lifetime Homes &
Metal Buildings and receive a free website. Sponsored
by: Anthony J. Russo Sr.
Membership Contract Agreement
for:
(new distributor name)
and between R & R Welding Lifetime Homes,
referred to as CONTRACTING PARTY,
Male:
Female:
Name:
(to make checks to)
Date of Birth:
(Must be over 18 yrs, no date, you will be rejected)
Address:
City:
State:
Zip:
(Address will not be shown on your website)
What Business Name for your new Website:
(a must, or, one will be assigned for you).
Phone Number:
Show on website? Yes or No
Fax Number if any:
Show on website? Yes or No
Business E-mail Address:
Home E-mail Address:
Referred to as INDEPENDENT AUTHORIZED ASSOCIATE
DISTRIBUTOR ( FINDER & REFERRAL AGENT ),
Agreement: ASSOCIATE DISTRIBUTOR shall perform the
following services for CONTRACTING PARTY:
To find referrals (customers) for R & R Welding
Lifetime Homes. At the following rate of remuneration:
For each home sold,(on the steel framed packages only)
through your referrals, 15% commission, first (3)
lifetime homes, 20% commission on forth & thereafter.
(please, insert correct dates below) (You may Renew
Yearly.)
This agreement shall begin on: , and shall terminate
on: (fill in date you signed up)
THIS IS AN AGREEMENT FOR INDEPENDENT REFERRAL
SERVICES. THE CONTRACTING PARTY PROVIDES NO
BENEFITS SUCH AS UNEMPLOYMENT INSURANCE OR WORKER'S
COMPENSATION INSURANCE TO INDEPENDENT, ASSOCIATE
DISTRIBUTORS. ALL ASSOCIATE DISTRIBUTORS ARE
RESPONSIBLE FOR THEIR OWN SUPPLIES & ADVERTISEMENTS.
CONTRACTING PARTY IS ONLY INTERESTED IN THE RESULTS
OBTAINED BY THE INDEPENDENT ASSOCIATE DISTRIBUTOR.
ALL INDEPENDENT, ASSOCIATE DISTRIBUTORS ARE
RESPONSIBLE FOR PAYMENT OF ALL FEDERAL STATE AND
LOCAL TAXES.
VIDEOS, BROCHURES & SALES MATERIALS ARE AVAILABLE
THROUGH OUR SALES DEPARTMENT, etc.
X: Rudolph Ortiz, Sr.
Date:
Contracting party: R & R Welding Lifetime Homes:
IMPORTANT, Type in your Associate Distributor
Signature and current date below
X:
Date:
Please email this agreement to the following address
to activate: lifetimehomes@yahoo.com
We will email your URL to your website within 24 hrs.
Thank You
Anthony J. Russo Sr.
Russo Communication Group Steel Framed Lifetime Homes
1905 Fairfield St. Ste. A
Eureka Ca. 95501
lifetimehomes@yahoo.com
To send by fax: 1-888-584-7194 ( TOLL FREE )
http://www.lifetime-homes.com/SteelHomes/ajr/start.html
************************************************************************************
This message is sent in compliance of the new e-mail bill: SECTION 301. Per Section
301, Paragraph (a)(2)(C) of S. 1618,
www.senate.gov/~murkowski/commercialemail/S771index.html
Further transmissions to you by the sender of this email may be stopped at no cost to
you by sending an Email To: delete_2000_2002@yahoo.com with the word "remove" in the
subject line.
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Sat Jul 8 08:45:07 2000
Received: from standards.nortelnetworks.com ([47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05440
for ; Sat, 8 Jul 2000 08:45:06 -0400 (EDT)
Received: from standards (47.234.32.16:4280) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7C2D3@standards.nortelnetworks.com>; Sat, 8 Jul 2000 8:34:16 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 3756 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Sat, 8 Jul 2000 08:34:16 -0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7C2D0@standards.nortelnetworks.com>; Sat, 8 Jul 2000 8:24:16
-0400
Received: from email.emailmkt ([208.225.197.49]) by hosaka.smallworks.com
(8.9.1/8.9.1) with SMTP id HAA14692; Sat, 8 Jul 2000 07:33:58 -0500
(CDT)
Message-ID: <200007081233.HAA14692@hosaka.smallworks.com>
Date: Sat, 8 Jul 2000 07:33:58 -0500
Reply-To: a_z55@YAHOO.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: a_z55@YAHOO.COM
Subject: [MOBILE-IP]
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
TIRED OF ENDLESSLY POSTING YOUR ONLINE CLASSIFIED AD AND GETTING NORESULTS?
The fact is there are over 7000 such sites scattered about the web
and frankly none of them generate enough traffic to be worth your
while. Even when someone does find or visits one of these sites, your
ad is hopelessly lost in a myriad of similar offerings.
Another frustration is search engines. If you are not in the Top 10
forget about high traffic visiting your web site. Not everyone can be
in the Top 10 and stay there, when there are estimates of 4 million
that have a web pages.
You ask, how do we know? That's exactly what we used to do.
The greatest way of marketing this century is undoubtedly direct
e-mail. It's similar to the postman delivering a letter to your
mailbox. There is NO stumbling on to it! The ability to promote your
product, service, website, or MLM/Network Marketing opportunity to
millions instantly is what advertisers have been dreaming of for over
100 years. We will e-mail your one page promotion to a list of our
general addresses. The greatest part is, it's completely affordable.
-----------------------------------------------------------------------
NOTICE: No pornography, chain letters, get quick rich, pyramid scheme,
or any threatening or questionable materials. Don't even Ask!!
-----------------------------------------------------------------------
STANDARD PRICING AND PROCEDURES
-----------------------------------------------------------------------
EXTRACTING:Our list of general Internet addreses are actually extracted from the
most popular web sites on the Internet. The addresses are verified and
run through our purification process. The process includes addresses
run against our custom filter of 2,492 keywords to remove as well as
through our 192MB remove /flamer list. The EDU, ORG, GOV, Mil, and US
domains are removed as well as well as other domains that asked not to
receive e-mail.
-----------------------------------------------------------------------
SET-UP FEE: $150.00
This will cover the costs of uploading files, Internet Access (ISP),
and software set-up.
-----------------------------------------------------------------------
EVALUATION: $350.00 (optional)
One of our Marketing Specialists will evaluate your sales letter, and
offer his/her expertise on how to make it the most successful.
-----------------------------------------------------------------------
STANDARD PRICING: (Emails Delivered)1 Million- $800.00 per2 Million- $700.00 per
3 Million & up- $600.00 per
-----------------------------------------------------------------------
SPECIAL OFFER!This introductory offer of $475.00 includes:1. Set-Up Fee
2. Evaluation of sales letter
3. 250,000 e-mails delivered to a general list of recipients.
-----------------------------------------------------------------------
PAYMENT POLICY
All services must be paid in full prior to delivery of advertisement.
Under NO CIRCUMSTANCES will any sales or marketing strategies be
discussed until payment is received.
-----------------------------------------------------------------------
If you are serious about Direct Email Marketing-Fax the following
form to (520) 438-2702
----------------------------------------------------------------------
THIS FORM MUST BE COMPLETELY FILLED OUT!
Contact Name: _____________________________________________
Business Name: ______________________________________
Business Type: ______________________________________
# Years in Business: _________________________
Address: _________________________________________________
City: ____________________ State: ______ Zip: ______________
Country: _______________
Email Address: _______________________________________________
Phone: __________________________Fax: ____________________________
-----------------------------------------------------------------------
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Sat Jul 8 09:12:04 2000
Received: from standards.nortelnetworks.com ([47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05638
for ; Sat, 8 Jul 2000 09:12:04 -0400 (EDT)
Received: from standards (47.234.32.16:4280) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7C33E@standards.nortelnetworks.com>; Sat, 8 Jul 2000 9:01:33 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 3899 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Sat, 8 Jul 2000 09:01:33 -0400
Received: from melimelo.enst-bretagne.fr by standards.nortelnetworks.com (LSMTP
for Windows NT v1.1b) with SMTP id
<0.FFB7C33D@standards.nortelnetworks.com>; Sat, 8 Jul 2000 9:01:33
-0400
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr
[192.44.77.1]) by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with
ESMTP id e68DBM625878; Sat, 8 Jul 2000 15:11:23 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
[193.52.74.194]) by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with
ESMTP id PAA24959; Sat, 8 Jul 2000 15:11:22 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr
[127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with
ESMTP id PAA60539; Sat, 8 Jul 2000 15:13:13 +0200 (CEST)
(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-ID: <200007081313.PAA60539@givry.rennes.enst-bretagne.fr>
Date: Sat, 8 Jul 2000 15:13:13 +0200
Reply-To: Francis.Dupont@ENST-BRETAGNE.FR
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Francis Dupont
Subject: Re: [MOBILE-IP] Terms: Home Link vs Home Network
X-To: "Lee, Jiwoong"
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To: Your message of Sat, 08 Jul 2000 11:29:47 +0900.
<009c01bfe884$63e8ee00$d012060a@hansol.co.kr>
In your previous mail you wrote:
Dear Authors of ,
Whereas RFC2002bis defines "Home Network" and uses this term generally,
Mobility Support in IPv6 defines "Home
Link"
=> ID 12 uses "home link" because IPv6 has an accurate notion of "link".
instead of "Home Network" while
uses "Home Link" together with "Home Network" through this docuemnt.
=> "home network" is used only twice in ID 12 for the home agent
interception of packets to the home address (which belongs to the home link).
I believe the idea is these packets can never be on the home link itself,
for instance if the router between the outside and the home link is the
home agent (in fact the home link can be fully virtual, ie. be used only
as an address space without a concrete physical incarnation).
Then the "home network" is the place where is the home stuff and
packets to a home destination go through it.
Do you try to express particular meaning when the term "Home Link" is used
instead of "Home Network"? How about the mixed use of these two terms?
=> I'd like to read ID 12 authors' answer but the two terms are not
used inconsistently (and home subnetwork which had been ambiguous
can't be found in ID 12).
Regards
Francis.Dupont@enst-bretagne.fr
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Sun Jul 9 07:17:48 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07513
for ; Sun, 9 Jul 2000 07:17:47 -0400 (EDT)
Received: from standards (47.234.32.16:1105) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7C588@standards.nortelnetworks.com>; 9 Jul 2000 7:06:59 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 4619 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Sun, 9 Jul 2000 07:06:59 -0400
Received: from neopolis.t.u-tokyo.ac.jp by standards.nortelnetworks.com (LSMTP
for Windows NT v1.1b) with SMTP id
<0.FFB7C584@standards.nortelnetworks.com>; 9 Jul 2000 6:56:58 -0400
Received: from mori (mori.t.u-tokyo.ac.jp [133.11.65.210]) by
neopolis.t.u-tokyo.ac.jp (8.9.3/3.7W-01/12/00) with ESMTP id
UAA04684; Sun, 9 Jul 2000 20:01:27 +0900 (JST)
X-Sender: mori@neopolis.t.u-tokyo.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <4.2.0.58.J.20000709200858.00b3bef0@neopolis.t.u-tokyo.ac.jp>
Date: Sun, 9 Jul 2000 20:09:20 +0900
Reply-To: Hiroyuki Morikawa
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Hiroyuki Morikawa
Subject: [MOBILE-IP] Call for Papers: MoMuC2000 and IEICE special issue
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
------------- MoMuC2000: Call for Papers ---------------
CALL FOR PAPERS
The 7th International Workshop on Mobile Multimedia Communications
MoMuC2000
http://www.giti.or.jp/activity/momucj
Date: October 23.-26. 2000
Place: Waseda, Tokyo, JAPAN
Submission due: August 11, 2000
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The 7th International Workshop on Mobile Multimedia Communications
(MoMuC2000) will provide an international forum for the discussion for
research in mobile multimedia communications and platforms regardless
of wireless and wired medium. The workshop, to be held in Tokyo,
Waseda, a city where the 1st MoMuC(MoMuC-1) was held back in 1993,
will bring together researchers, developers and practitioners working
in all facets of advanced mobile multimedia communications. The scope
of MoMuC2000 will include mobile multimedia systems and applications
together with associated mobile computing, broadband wireless
networking, video processing and enabling software technologies.
The workshop will be corss-diciplinary, well focused, consisting
keynote speakers, tutorials, panels and solicited contributions with
the emphasis on innovations. An amount of time should be devoted to
informal discussion. Authors are cordially invited to submit
previously unpublished papers including short papers. Papers with
regard to concept and proposal of immature idea are also welcome for
an inherent nature of workshop. Technical visit to Yokosuka Research
Park(YRP) is also planned.
Further information will be provided through MoMuC2000 web page with
the following URL.
http://www.giti.or.jp/activity/momucj
Suggested Areas
- Mobile multimedia applications and platforms
- Mobile computing and advanced mobile IP
- Source coding and channel coding for mobile multimedia including MPEG-4
- Distributed systems and mobile multimedia communications
- Mobile ad hoc networks
- Mobile multimedia networks
- High speed wireless packet systems and technologies
- Mobile multimedia applications and technologies in IMT-2000
- Intelligent Transportation System for mobile multimedia
- Internetworking of wired and wireless networks
- Next generation mobile Internet
- Mobile agent technology
- Enabling software technologies for mobile systems
- Quality of service in wireless and mobile networks
- Medium access/data link control
- Wireless networks management & service control for mobile multimedia
- Software radio for mobile multimedia
Workshop Committee
- Steering Committee:
D. Goodman (Polytechnic University, USA)
D. Raychaudhuri (NEC, Princeton, USA)
H. Tominaga (Waseda University, JAPAN)
- Organizing Committee
Chair: H. Tominaga(Waseda University)
- Technical Program Committee:
Chair: T. Hattori(Sophia University)
Co-Chairs: H. Yasuda(University of Tokyo)
S. Komaki(University of Osaka)
K. Aizawa(University of Tokyo)
- Local Organization Committee:
Chair: M. Matsumoto(Waseda University)
- Secretariat:
Ms. Noriko Hosokawa
Global Information and Telecommunication Institute, Waseda University, 29-7
Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo
169-0051 JAPAN
Tel. /Fax. +81-3-5286-9863
E-mail: momuc2000@giti.or.jp
http://www.giti.or.jp/activity/momucj
Important Dates
Paper(Extended Abstract) Submission Deadline: 11 August 2000
Acceptance of Notification: 4 September 2000
Camera Ready Copy Submission: 22 September 2000
Instructions
Manuscripts must be in English and not exceed 3000 words and may include
figures and tables.
Each copy of the manuscript should include a cover page containing:
1. Name of all authors
2. Name of contact author, affiliation, return address, e-mail,
telephone and fax numbers of contact author.
3. A double-spaced, 100-word abstract containing no equations and
printed in a 12 point or larger plain font suitable for
electronic scanning.
4. All other pages should be marked with the title of the paper,
name of the first author, and page numbers.
For electronic submissions, file format will be disirable in whether
MS-Word 6.0/higher or Adobe PDF format. On-line paper submission
is available at the following URL;
http://www.giti.or.jp/activity/momucj/submissions.html
Sponsors
Host:
MoMuC-J of IEICE,
Waseda University
Co-sponsors:
IEEE Commnucation Society Japan Chapter,
IEEE Communication Society,
IEICE (Institute of Electronics, Information and Communication Engineering),
IPSJ (Information Processing Society of Japan),
IIEEJ (The Institute of Image Electronics Engineers of Japan),
ITE (The Institute fo Image Information and Television Engineers)
------------- IEICE special issue: Call for Papers ---------------
CALL FOR PAPERS
IEICE Special Issue on Mobile Multimedia Communications
The IEICE (Institute of Electronics, Information and Communication
Engineering) Transactions on Communications announces a forthcoming
special issue on Mobile Multimedia Communications to be published in
April 2001.
Recently, intensive efforts are now underway to promote practical use
of mobile multimedia communications technologies; Progress has been
achieved in the international standardization activities such as
IMT-2000, IrDA, MPEG-4, etc. Many test bed experiments have been
carried out as mobile communications systems such as wireless ATM,
wireless Internet, etc. Also, various research and developments are
widely in progress in the field of application and terminal
technologies such as mobile contents, data broadcasting, PDA
terminals, information appliance, etc., and of networking technologies
such as mobile IP, quality of service, mobile agent, etc.
The purpose of this special issue is to present the recent advance of
mobile multimedia communications technologies including mobile
applications, terminals, network, broadcasting, etc., and to promote
future progress of research, development, and new applications of
mobile multimedia communications. We are calling for papers from
engineers in Japan and abroad. Submission of a paper presented at
MoMuC 2000, to be held in Tokyo during October 23rd to 26th, 2000, is
encouraged, but presentation of the paper at the workshop is not a
requirement for its inclusion in this special issue. Conversely,
presentation at the conference will not guarantee acceptance in the
special issue.
1. Scope
Suggested topics include but are not limited to the following:
- Mobile multimedia applications and terminals
Mobile computing, mobile contents, architecture for multimedia
mobile terminals, mobile IP, personal multimedia applications,
audiovisual compressions for mobile applications, security
- Mobile multimedia systems and implementations
System architecture for mobile multimedia (including fast LAN),
quality of service for mobile multimedia communications, agent
systems, multimedia satellite, implementation techniques of advanced
wireless systems for mobile multimedia, data integration for mobile
communications, multimedia location service
- Network for Mobile Multimedia
Broadband/fast wireless network (including wireless ATM), IP
adaptive wireless access method, distributed networking, mobile
multimedia advanced wireless techniques (including IrDA), multimedia
data integrated service network for mobile communications
2. Submission Instructions
Submitted papers will be reviewed by referees in accordance with the
regular rules of the Transactions Editorial Committee. The standard
number of pages is 8 for a paper and 2 for a letter. Refer to
``Information for Authors'' at the following web site for more
details; http://www.ieice.or.jp/eng/shiori/mokuji.html. Prospective
authors are requested to send four copies of their manuscripts to the
address below. ``Special Issue on Mobile Multimedia Communications''
should be placed on top of the first page.
Hirohisa Jozawa
NTT Department III (R&D Strategy Department)
Teishin Building 8F, 2-3-1, Otemachi, Chiyoda-ku, Tokyo, 100-8116 Japan
Tel: +81 3 5205 5379, Fax: +81 3 5205 5369
E-mail: h.jozawa@hco.ntt.co.jp
3. Paper Submission Deadline
Papers must be received by August 25, 2000.
^^^^^^^^^^^^^^^
4. Special Issue Editorial Committee
Editor-in-Chief
Takeshi Hattori (Sophia University)
Secretary
Hirohisa Jozawa (NTT), Takehiko Kobayashi (YRP), Hisashi Miyamori (CRL)
Guest Editors
Hirotaka Nakano (NTT DoCoMo), Shiro Sakata (NEC), Tadanori Mizuno
(Shizuoka Univ), Kiyoharu Aizawa (Univ of Tokyo), Ki-ichi Matsuda
(Fujitsu Lab), Minoru Etoh (Matsushita), Hiroshi Watanabe (NTT),
Shuuichi Matsumoto (KDD Lab), Yoshihiko Akaiwa (Kyushu Univ), Shozo
Komaki (Osaka Univ), Mitsuji Matsumoto (Waseda University), Mitsuo
Iwama (Sharp), Kouichi Honma (Matsushita), Hiroshi Nakamura (NTT
DoCoMo), Fumiyuki Adachi (Touhoku Univ), Hiroyuki Morikawa (Univ of
Tokyo), Takuro Satoh (Niigata Univ)
* Please note that if accepted for publication, all authors, including
authors of invited papers, should pay for the page charges covering
partial cost of publication. Authors will receive 100 copies of the
reprint.
----------------------------------------------------
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Sun Jul 9 16:49:24 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10796
for ; Sun, 9 Jul 2000 16:49:24 -0400 (EDT)
Received: from standards (47.234.32.16:3251) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7C68F@standards.nortelnetworks.com>; 9 Jul 2000 16:38:37 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 4930 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Sun, 9 Jul 2000 16:38:37 -0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7C68C@standards.nortelnetworks.com>; 9 Jul 2000 16:28:37 -0400
Received: from beta.vinet.com.mx ([200.34.41.11]) by hosaka.smallworks.com
(8.9.1/8.9.1) with ESMTP id PAA23077 for ;
Sun, 9 Jul 2000 15:38:39 -0500 (CDT)
Received: from eol (host-216-78-227-58.mco.bellsouth.net [216.78.227.58]) by
beta.vinet.com.mx (Build 98 8.9.3/NT-8.9.3) with SMTP id PAA04156;
Sun, 09 Jul 2000 15:34:11 -0500
Message-ID: <200007092034.PAA04156@beta.vinet.com.mx>
Date: Sun, 9 Jul 2000 15:34:11 -0500
Reply-To: michelle3@BUSINESSWEEKMAIL.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: michelle3@BUSINESSWEEKMAIL.COM
Subject: [MOBILE-IP] How to make $100 - $1,500 per hour or two
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
From: Michelle Smith - publisher of the "Work From Home Opportunities" Newsletter
Saturday, 9:30 p.m.
Hello,
If you're interested in earning $100 - $1,500 per hour or two,
Then I want to share something with you...
Now you can make an additional $100 - $1,500 Per Hour or Two!
Imagine you come home from a hard day's work (exhausted..),
You immediately go straight to bed. You get undressed,
lay down, turn off the lights, and snuggle up face-down on
the pillow. A few moments later, you feel uncomfortable and
stressed out so you lie on your back.
When you look up at the ceiling, it's as if the ceiling has been removed!
You see exactly what you would see if outside stargazing!
A stunning, accurate 3-dimensional re-creation of the starry
night sky, including constellations such as the Big Dipper,
Pegasus and the Milky Way galaxy,
...and even shooting stars!
You can't see it during the day. The ceiling looks normal.
But at night, when the lights are off, you see what looks
like the sky outside!
It's so relaxing and romantic. And educational!
And talk about stress-relief! The moment you look at it,
it'll melt your tension away faster than a great massage!
Now how many people do you think would LOVE seeing this when
they look up in their beds at night?
"It's like you're sleeping under the stars!"
Ok, I know you want to know How You Make Money.
Here's how.
You can put that awesome "convertible ceiling" in ANYONE'S bedroom with a
product cost to you of..
Guess how much..
Only ONE to TWO Dollars! And you offer this masterpiece for $100 - $1,500!
Talk about *nice* profits!
And it only takes you an hour or two!
Here's an important point:
These profits are similar to the profits of selling Information:
the material costs next to nothing, but the customer really VALUES
the END RESULT. So you can charge more (a LOT more).
"Who'd want this?"
Anyone with a bedroom ceiling (or any ceiling),
as well as homes, hotels, etc.
Who do you know that has a bedroom ceiling?
Whew! The official money-making opportunity of the Millenium!
(Well... I think it should be!) |;-)
Anyway, I know you want more information to make a decision, so ...
To receive more FREE information on How To Make $100 - $1,500 Per Hour or Two,
Simply Click On The Email Link Below and Send Back The Following:
Mailto:starbiz140@newmail.net
Name:
E-Mail:
Phone:
Street:
City:
State:
ZIP or Postal Code:
Country (available INTERNATIONALLY):
Mailto:starbiz140@newmail.net
And you'll be sent the full details on
how to make $100 - $1,500 Per Hour or Two, as
well as pictures of these murals so you can
see for yourself how breathtaking they are!
Best regards,
Michelle Smith
P.S. We'll also send you a free Opportunity E-zine with
more interesting Money-Making Opportunities like this one,
and important info. for the home-based entrepreneur!
P.P.S. Also, even though 99% of people don't know about this
opportunity, that won't be the case forever, so hurry up and
reply to make sure you get to lock down YOUR city!
To unsubscribe mailto:unsubscribe708@newmail.net
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Mon Jul 10 06:40:57 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02645
for ; Mon, 10 Jul 2000 06:40:57 -0400 (EDT)
Received: from standards (47.234.32.16:3131) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7C7A3@standards.nortelnetworks.com>; Mon, 10 Jul 2000 6:30:16 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 5296 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 10 Jul 2000 06:30:16
-0400
Received: from ietf.org (odin.ietf.org) by standards.nortelnetworks.com (LSMTP
for Windows NT v1.1b) with SMTP id
<0.FFB7C7A1@standards.nortelnetworks.com>; Mon, 10 Jul 2000 6:20:16
-0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org
(8.9.1a/8.9.1a) with ESMTP id GAA01715; Mon, 10 Jul 2000 06:30:21
-0400 (EDT)
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Message-ID: <200007101030.GAA01715@ietf.org>
Date: Mon, 10 Jul 2000 06:30:21 -0400
Reply-To: Internet-Drafts@ietf.org
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
Comments: RFC822 error: Incorrect or incomplete address field found and
ignored.
From: Internet-Drafts@ietf.org
Subject: [MOBILE-IP] I-D ACTION:draft-elmalki-mobileip-fast-handoffs-02.txt
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
--NextPart
A New Internet-Draft is available from the on-line Internet-Drafts directories.
Title : Fast Handoffs in Mobile IPv4
Author(s) : K. El Malki, H. Soliman
Filename : draft-elmalki-mobileip-fast-handoffs-02.txt
Pages : 15
Date : 07-Jul-00
This draft describes a method to achieve Fast Handoffs in Mobile
IPv4. Fast Handoffs are required in Mobile IPv4 in order to limit the
period of service disruption experienced by a wireless Mobile Node
when moving between Foreign Agents. This requirement becomes even
more important when supporting real-time services. Fast Handoffs
involve anticipating the movement of MNs by sending multiple copies
of the traffic to potential Mobile Node movement locations (i.e. FAs).
Both a flat and a Hierarchical Mobile IPv4 model are considered. The
Hierarchical MIPv4 model in Regional Tunnel Management [1] already
offers improvements to Mobile IP handoffs by providing local Home
Agent functionality. Some additions are made to the operation of this
existing Hierarchical model to achieve Fast Handoffs and limit or
avoid triangle routing within the hierarchical domain.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-elmalki-mobileip-fast-handoffs-02.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-elmalki-mobileip-fast-handoffs-02.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-elmalki-mobileip-fast-handoffs-02.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: <20000707143157.I-D@ietf.org>
ENCODING mime
FILE /internet-drafts/draft-elmalki-mobileip-fast-handoffs-02.txt
--OtherAccess
Content-Type: Message/External-body;
name="draft-elmalki-mobileip-fast-handoffs-02.txt";
site="ftp.ietf.org";
access-type="anon-ftp";
directory="internet-drafts"
Content-Type: text/plain
Content-ID: <20000707143157.I-D@ietf.org>
--OtherAccess--
--NextPart--
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Mon Jul 10 19:33:09 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01801
for ; Mon, 10 Jul 2000 19:33:09 -0400 (EDT)
Received: from standards (47.234.32.16:1773) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7CAD6@standards.nortelnetworks.com>; Mon, 10 Jul 2000 19:22:19 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 6399 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 10 Jul 2000 19:22:18
-0400
Received: from emaxr1.emax.com.pl (emax-gw.man.poznan.pl) by
standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP
id <0.FFB7CAD5@standards.nortelnetworks.com>; Mon, 10 Jul 2000
19:12:17 -0400
Received: from intra.emax.com.pl (intra.emax.com.pl [212.126.5.50]) by
emaxr1.emax.com.pl (8.8.5/8.8.5) with ESMTP id BAA19673; Tue, 11 Jul
2000 01:26:48 +0200
Received: from INTRA/SpoolDir by intra.emax.com.pl (Mercury 1.44); 11 Jul 00
01:27:50 +0100
Received: from SpoolDir by INTRA (Mercury 1.44); 11 Jul 00 01:11:12 +0100
Received: from djdswk (204.164.170.21) by intra.emax.com.pl (Mercury 1.44) with
ESMTP; 11 Jul 00 01:11:09 +0100
X-Mailer: Mozilla 4.70 [en] (Win95; I)
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:
Date: Mon, 10 Jul 2000 17:20:07 -0500
Reply-To: "Edward R."
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "Edward R."
Subject: [MOBILE-IP] Your Call #47C4
X-To: today39d@emaxr1.emax.com.pl
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA01801
WE MAKE IT EASY & AFFORDABLE TO ACCEPT CREDIT CARDS FOR YOUR BUSINESS
!
INTERNET (Auction Vendors & Online Mall Stores Too!)
STOREFRONT OR MAIL ORDER MERCHANTS
WE SPECIALIZE IN APPROVING YOU!
APPLY TODAY AND START FOR JUST $9.95!
FREE APPLICATION!!
FREE PROGRAMMING!!
DON'T LOSE ANOTHER SALE!
APPLY TO ACCEPT CREDIT CARDS
AND CALL (888) 264-9272
DON'T FORGET TO ASK ABOUT OUR WEB DESIGN AND HOSTING PACKAGE !!!
************************************************************
If you receive this message and have never joined one of our
email lists you can be removed by replying to:
mailto:maiqx@188mail.com?subject=remove
************************************************************
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Tue Jul 11 01:22:46 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10649
for ; Tue, 11 Jul 2000 01:22:46 -0400 (EDT)
Received: from standards (47.234.32.16:1557) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7CC0C@standards.nortelnetworks.com>; Tue, 11 Jul 2000 1:12:09 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 6794 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 11 Jul 2000 01:12:09
-0400
Received: from mailhost.iprg.nokia.com by standards.nortelnetworks.com (LSMTP
for Windows NT v1.1b) with SMTP id
<0.FFB7CC02@standards.nortelnetworks.com>; Tue, 11 Jul 2000 1:02:09
-0400
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 WAA04790;
Mon, 10 Jul 2000 22:12:18 -0700 (PDT)
Received: (from root@localhost) by darkstar.iprg.nokia.com
(8.9.3/8.9.3-VIRSCAN) id WAA11633; Mon, 10 Jul 2000 22:12:14 -0700
X-Virus-Scanned: Mon, 10 Jul 2000 22:12:14 -0700 Nokia Silicon Valley Email
Exploit Scanner
Received: from jmalinen.iprg.nokia.com (205.226.2.98,
claiming to be "iprg.nokia.com") by
darkstar.iprg.nokia.com(WTS.12.69) smtpd7MHcFJ; Mon, 10 Jul 2000
22:12:10 PDT
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
References: <396AB430.902573CA@comet.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <396AACAD.D48FEA1F@iprg.nokia.com>
Date: Mon, 10 Jul 2000 22:12:13 -0700
Reply-To: jmalinen@IPRG.NOKIA.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "Jari T. Malinen"
Subject: Re: [MOBILE-IP] Paging
X-To: campbell@comet.columbia.edu
X-cc: Henry.Haverinen@nokia.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit
Hello, Andrew,
Indeed, we did submit an Internet-Draft on how to use paging with
Regional Registrations.
The draft is available at the IETF Internet Drafts archive, at URL
http://www.ietf.org/internet-drafts/
draft-haverinen-mobileip-reg-paging-00.txt
It seems there are spaces in the URL thus it might be that it does not
show correctly in all
places (e.g. the I-D search does not seem to find it). However, it is
available behind the
above link with the spaces included.
The draft presents paging as a rather straightforward extension to
Regional Registrations,
and provides thus a different approach to that taken in Cellular IP. The
paging area is also
static providing opportunities for supporting timeslot-based paging ,and
with it, power-
constrained operation.
Best Regards,
--jari
Jari T. Malinen,
Nokia Research Center.
"Andrew T. Campbell" wrote:
> Hi Jari:
>
> One of my students mentioned that you authors an Intenet
> Draft on paging. Could you let me have a copy?
>
> Andrew
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Tue Jul 11 07:26:02 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25749
for ; Tue, 11 Jul 2000 07:26:02 -0400 (EDT)
Received: from standards (47.234.32.16:1053) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7CE10@standards.nortelnetworks.com>; Tue, 11 Jul 2000 7:15:25 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 7500 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 11 Jul 2000 07:15:25
-0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7CE07@standards.nortelnetworks.com>; Tue, 11 Jul 2000 7:05:25
-0400
Received: from staff-svcs.geckosss (ip123.phoenix8.az.pub-ip.psi.net
[38.29.61.123]) by hosaka.smallworks.com (8.9.1/8.9.1) with SMTP id
GAA03529; Tue, 11 Jul 2000 06:15:28 -0500 (CDT)
Message-ID: <200007111115.GAA03529@hosaka.smallworks.com>
Date: Tue, 11 Jul 2000 06:15:28 -0500
Reply-To: a_z48@YAHOO.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: a_z48@YAHOO.COM
Subject: [MOBILE-IP]
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
For Homeowners Only!!
Want to pay off your credit card debt? Need cash for some other reason?
We can get you the loan you need regardless of whether you
have good or bad credit. Qualify even if you have hard to prove
income (Self-Employed.) Pay off tax liens, judgments, or
collection accounts. Pay off your chapter 13 bankruptcy or avoid foreclosure.
Get CASH for ANY REASON!!
If you are serious about improving your lifestyle APPLY NOW!
We can help. We specialize in funding the loans that other lenders turn down.
Click on the link below for the fastest free loan quote!!!
http://www.whattodoifyouneedmoney.com
Can't take the time to apply now? Then print out the form
below and fax it to us today.
FAX: (509) 562-7964
Please fill out this form completely. Enter NA in those fields which do not apply. ************************************************************************
Are you a HomeOwner? Y / N
Applicant First and Last Name: ________________________________
Co-Applicant First and Last Name: _____________________________
Address: __________________________________________________
City, State: ________________________________________________
Zip code: _______________________
Home Phone: ___________________________
Work Phone: ____________________________
Property Type: Single Family Residence, Town-home, Condo, Other
Purchase Price: _________________________________________
Year Property was Acquired: ______________________________
Present Value of Property: ________________________________
Amount Owed on First Mortgage: __________________________
Current Interest Rate: ____________________________________
Fixed or Adjustable: _____________________________________
Monthly Payment: _______________________________________
Second Mortgage Balance: ________________________________
Current Employer: _______________________________________
Years with Current Employer: ______________________________
Yearly Income: __________________________________________
How would you describe Your Credit: Excellent/Good/Fair/Poor
Best Time to Contact You: _________________________________
Type of Loan Desired: ____________________________________
Loan Amount Desired: ____________________________________
Email Address: __________________________________________ ************************************************************************
We respect your online time and privacy and pledge not to abuse
this medium. If you prefer not to receive further e-mails from us
of this type, please reply to this e-mail and type 'Remove' in the subject line.
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Tue Jul 11 13:59:14 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12187
for ; Tue, 11 Jul 2000 13:59:13 -0400 (EDT)
Received: from standards (47.234.32.16:3336) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7D040@standards.nortelnetworks.com>; Tue, 11 Jul 2000 13:48:31 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 0316 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 11 Jul 2000 13:48:30
-0400
Received: from lukla.Sun.COM by standards.nortelnetworks.com (LSMTP for Windows
NT v1.1b) with SMTP id <0.FFB7D03F@standards.nortelnetworks.com>;
Tue, 11 Jul 2000 13:48:25 -0400
Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by lukla.Sun.COM
(8.9.3+Sun/8.9.3) with ESMTP id LAA01404 for
; Tue, 11 Jul 2000 11:57:23
-0600 (MDT)
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,v1.7) with ESMTP id
KAA24118 for ; Tue, 11 Jul
2000 10:44:51 -0700 (PDT)
Received: from mordor (mordor [129.146.120.122]) by nasnfs.eng.sun.com
(8.9.3+Sun/8.9.1) with SMTP id KAA11320 for
; Tue, 11 Jul 2000 10:44:50
-0700 (PDT)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Message-ID:
Date: Tue, 11 Jul 2000 10:44:01 -0700
Reply-To: "pcalhoun@eng.sun.com"
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "pcalhoun@eng.sun.com"
Subject: Re: [MOBILE-IP] WG Internet Drafts to last call...
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Raj,
As per the e-mail below on June 16th, you had agreed to move
draft-ietf-mobileip-gnaie-00.txt to last call. I haven't seen a last call
e-mail from you. Is a last call for this spec still in the cards?
PatC
----
Date: Fri, 16 Jun 2000 13:43:08 -0500
Reply-To: Basavaraj.Patil@NOKIA.COM
Sender: "IP Routing for Wireless/Mobile Hosts
(mobile-ip)"
From: Basavaraj Patil
Subject: Re: WG Internet Drafts to last call...
X-cc: Pat.Calhoun@Eng.Sun.COM
Content-Type: text/plain; charset="iso-8859-1"
Pat,
>All,
>
>I was wondering if the following Internet Drafts could
be moved to WG
>last call, and sent to the IESG for publication:
>1.draft-ietf-mobileip-mier-03.txt.
>This one has already received interoperability, and I
believe it is
>ready.
This one has already completed WG last call and has
been submitted to
the IESG.
>2.draft-ietf-mobileip-aaa-key-01.txt. This one was
also sucessfully
>tested at the last connectathon, and should be moved
ahead.
References to DIAMETER in this document need to be
removed and also
the use of MD5 as suggested in the draft needs to be
updated to be
more in-line with the FA challenge draft (ver.12).
Maybe you should
reissue a new draft and then we can do a WG last call.
>3.draft-ietf-mobileip-gnaie-00.txt. This fairly
non-controversial
>draft is a no-brainer and should be moved ahead as
well.
Sounds reasonable.
>
>Thanks,
>
>PatC
-Basavaraj
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Tue Jul 11 18:14:45 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21884
for ; Tue, 11 Jul 2000 18:14:45 -0400 (EDT)
Received: from standards (47.234.32.16:2934) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7D0DD@standards.nortelnetworks.com>; Tue, 11 Jul 2000 18:04:01 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 0519 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 11 Jul 2000 18:04:01
-0400
Received: from mailhost.iprg.nokia.com by standards.nortelnetworks.com (LSMTP
for Windows NT v1.1b) with SMTP id
<0.FFB7D0DC@standards.nortelnetworks.com>; Tue, 11 Jul 2000 18:04:00
-0400
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 PAA02343
for ; Tue, 11 Jul 2000
15:14:07 -0700 (PDT)
Received: (from root@localhost) by darkstar.iprg.nokia.com
(8.9.3/8.9.3-VIRSCAN) id PAA00462 for
; Tue, 11 Jul 2000 15:14:04
-0700
X-Virus-Scanned: Tue, 11 Jul 2000 15:14:04 -0700 Nokia Silicon Valley Email
Exploit Scanner
Received: from charliep.iprg.nokia.com (205.226.2.89,
claiming to be "iprg.nokia.com") by
darkstar.iprg.nokia.com(WTS.12.69) smtpdvIlrhO; Tue, 11 Jul 2000
15:13:56 PDT
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
References: <38A4588D.92FCE771@alcatel.be> <38A4951C.A369B13F@iprg.nokia.com>
<00021414482106.24820@tpce13> <38BB4A9F.34ACF492@iprg.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <396B9C27.FAB4C9D4@iprg.nokia.com>
Date: Tue, 11 Jul 2000 15:13:59 -0700
Reply-To: charliep@IPRG.NOKIA.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "Charles E. Perkins"
Organization: Nokia Research Center
Subject: Re: [MOBILE-IP] micromobility in IPv6 ?
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit
Hello folks,
I am preparing a new revision for RFC2002bis, incorporating all
of the comments over the past months.
Recently, RFC 2794 has been promoted to Proposed Standard.
This specification makes it legal for a Mobile IP registration
message to be accepted by the Home Agent without containing
a Mobile-Home authentication extension. Therefore, I propose
to change the relevant portions of RFC2002bis to allow for this
possibility.
I hope this is O.K. It is a lot of work! I expect that I will
make it more easily digestible by defining a new piece of
terminology called something like "Admissible Authentication Extension",
where admissible means admissible to the home agent. This might
otherwise be ambiguous, except that in RFC2002bis there is only
one context where it matters.
Comments? Sorry for the short notice, but like everybody else
I put this task off a little too long for extended debate.
Regards,
Charlie P.
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Tue Jul 11 18:49:31 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22486
for ; Tue, 11 Jul 2000 18:49:31 -0400 (EDT)
Received: from standards (47.234.32.16:1068) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7D12D@standards.nortelnetworks.com>; Tue, 11 Jul 2000 18:38:58 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 0611 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 11 Jul 2000 18:38:58
-0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7D122@standards.nortelnetworks.com>; Tue, 11 Jul 2000 18:28:58
-0400
Received: from eastmail2.East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM
(8.9.3+Sun/8.9.3) with ESMTP id PAA02571; Tue, 11 Jul 2000 15:39:06
-0700 (PDT)
Received: from atlantic.East.Sun.COM (atlantic.East.Sun.COM [129.148.174.27])
by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP
id SAA23069; Tue, 11 Jul 2000 18:39:05 -0400 (EDT)
Received: from onion.east.sun.com (onion [129.148.174.110]) by
atlantic.East.Sun.COM (8.9.1b+Sun/8.9.1) with SMTP id SAA28778; Tue,
11 Jul 2000 18:39:56 -0400 (EDT)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Message-ID:
Date: Tue, 11 Jul 2000 18:38:59 -0400
Reply-To: Steven Glass - Solaris Software
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Steven Glass - Solaris Software
Subject: Re: [MOBILE-IP] micromobility in IPv6 ?
X-To: charliep@IPRG.NOKIA.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To: "Your message with ID" <396B9C27.FAB4C9D4@iprg.nokia.com>
> Hello folks,
>
> I am preparing a new revision for RFC2002bis, incorporating all
> of the comments over the past months.
How about the comments on the "V" bit? Yes, late for anything resembling
extended debate...
> Recently, RFC 2794 has been promoted to Proposed Standard.
> This specification makes it legal for a Mobile IP registration
> message to be accepted by the Home Agent without containing
> a Mobile-Home authentication extension. Therefore, I propose
> to change the relevant portions of RFC2002bis to allow for this
> possibility.
>
> I hope this is O.K. It is a lot of work! I expect that I will
> make it more easily digestible by defining a new piece of
> terminology called something like "Admissible Authentication Extension",
> where admissible means admissible to the home agent.
^^^^^^^^^^
More like the "home authentication agent", which is similar to 'home
agent' only it may not be the home agent doing the authenticating?
Cheers,
Steve
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Tue Jul 11 19:11:31 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22842
for ; Tue, 11 Jul 2000 19:11:31 -0400 (EDT)
Received: from standards (47.234.32.16:4332) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7D1A3@standards.nortelnetworks.com>; Tue, 11 Jul 2000 19:00:59 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 0790 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 11 Jul 2000 19:00:59
-0400
Received: from mailhost.iprg.nokia.com by standards.nortelnetworks.com (LSMTP
for Windows NT v1.1b) with SMTP id
<0.FFB7D1A2@standards.nortelnetworks.com>; Tue, 11 Jul 2000 19:00:59
-0400
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 QAA08834;
Tue, 11 Jul 2000 16:11:09 -0700 (PDT)
Received: (from root@localhost) by darkstar.iprg.nokia.com
(8.9.3/8.9.3-VIRSCAN) id QAA16086; Tue, 11 Jul 2000 16:11:06 -0700
X-Virus-Scanned: Tue, 11 Jul 2000 16:11:06 -0700 Nokia Silicon Valley Email
Exploit Scanner
Received: from charliep.iprg.nokia.com (205.226.2.89,
claiming to be "iprg.nokia.com") by
darkstar.iprg.nokia.com(WTS.12.69) smtpdNFZNG9; Tue, 11 Jul 2000
16:11:02 PDT
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
References:
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <396BA989.AC651E2A@iprg.nokia.com>
Date: Tue, 11 Jul 2000 16:11:05 -0700
Reply-To: charliep@IPRG.NOKIA.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "Charles E. Perkins"
Organization: Nokia Research Center
Subject: Re: [MOBILE-IP] micromobility in IPv6 ?
X-To: Steven Glass - Solaris Software
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit
Hello Steve,
I'll take the `V' bit out unless somebody complains. I never
implemented it either.
> How about the comments on the "V" bit? Yes, late for anything resembling
> extended debate...
> > I hope this is O.K. It is a lot of work! I expect that I will
> > make it more easily digestible by defining a new piece of
> > terminology called something like "Admissible Authentication Extension",
> > where admissible means admissible to the home agent.
> ^^^^^^^^^^
> More like the "home authentication agent", which is similar to 'home
> agent' only it may not be the home agent doing the authenticating?
Well, all that is needed is that whatever authentication is performed
has to be _acceptable_ to the home agent. So, I sort-of like the
"admissible" terminology better for that reason, but I'm still open
to suggestion...
Regards,
Charlie P.
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Wed Jul 12 00:41:00 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29356
for ; Wed, 12 Jul 2000 00:40:59 -0400 (EDT)
Received: from standards (47.234.32.16:3994) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7D258@standards.nortelnetworks.com>; Wed, 12 Jul 2000 0:30:00 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 1034 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 12 Jul 2000 00:30:00
-0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7D251@standards.nortelnetworks.com>; Wed, 12 Jul 2000 0:20:00
-0400
Received: from correo.interlink.es (correo.interlink.es [194.224.34.22]) by
hosaka.smallworks.com (8.9.1/8.9.1) with SMTP id XAA08257 for
; Tue, 11 Jul 2000 23:30:10 -0500 (CDT)
Received: from stacy (unverified [216.78.230.161]) by correo.interlink.es
(EMWAC SMTPRS 0.83) with SMTP id ;
Wed, 12 Jul 2000 06:30:09 +0200
Message-ID:
Date: Wed, 12 Jul 2000 06:30:09 +0200
Reply-To: stacy2@SONICNETMAIL.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: stacy2@SONICNETMAIL.COM
Subject: [MOBILE-IP] ByOwner Income Opportunity
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
ByOwner Income Opportunity
Be your own boss! Help people sell BY OWNER!
Now you can make money working from home
or add to your existing income.
No Real Estate experience is necessary!
You can become a BYOWNER COACH
WE WILL TRAIN YOU TO HELP SOME OF THE
OVER 1 MILLION HOME SELLERS WHO SELL
their OWN HOME EACH YEAR.
These home sellers need advice, advertising and marketing
power, and you're just the one to give it to them.
We will train you on:
- How to find FSBO's
- How to close them on our services
- How to integrate this program into your existing business
- How to generate more dollars for you
And we'll also:
- Provide you with ad slicks
- Provide you with leads!
As you may already know, THIS MARKET IS HUGE!
We support you 24 hrs a day 7 days a week via:
- email
- chat
- 800#
For The Full, Exciting Details, Send Your Phone # and Zip Code
To: Mailto:fsbo-opp2@newmail.net
P.S. We'll also send you a free Opportunity E-zine with more
interesting Money-Making Opportunities like this one, and
important info. for the home-based entrepreneur!
To unsubscribe mailto:unsubscribe708@newmail.net
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Wed Jul 12 10:38:58 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24960
for ; Wed, 12 Jul 2000 10:38:56 -0400 (EDT)
Received: from standards (47.234.32.16:4739) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7D5A8@standards.nortelnetworks.com>; Wed, 12 Jul 2000 10:28:05 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 2173 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 12 Jul 2000 10:28:05
-0400
Received: from prue.eim.surrey.ac.uk by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7D5A5@standards.nortelnetworks.com>; Wed, 12 Jul 2000 10:18:05
-0400
Received: from regan.ee.surrey.ac.uk ([131.227.89.11]) by prue.eim.surrey.ac.uk
with esmtp (Exim 3.03 #1) id 13CNUn-0000ok-00 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 12 Jul 2000 15:28:17
+0100
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-ID:
Date: Wed, 12 Jul 2000 15:28:17 +0100
Reply-To: Eleftheria Menegou
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Eleftheria Menegou
Subject: [MOBILE-IP] PRMA Implementation
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Dear All:
I am working towards my MSc thesis and currently studying the PRMA
protocol. As I am new in this field, is any one that can provide me with
a prototype implementation of PRMA to have this as a reference point on
my study? I am working with MAISIE/PARSEC and C.
Thanks in advance.
Eleftheria
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Wed Jul 12 11:41:07 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28329
for ; Wed, 12 Jul 2000 11:41:06 -0400 (EDT)
Received: from standards (47.234.32.16:4739) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7D667@standards.nortelnetworks.com>; Wed, 12 Jul 2000 11:30:02 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 2437 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 12 Jul 2000 11:30:02
-0400
Received: from mailhost.iprg.nokia.com by standards.nortelnetworks.com (LSMTP
for Windows NT v1.1b) with SMTP id
<0.FFB7D666@standards.nortelnetworks.com>; Wed, 12 Jul 2000 11:30:02
-0400
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 IAA16997;
Wed, 12 Jul 2000 08:40:15 -0700 (PDT)
Received: (from root@localhost) by darkstar.iprg.nokia.com
(8.9.3/8.9.3-VIRSCAN) id IAA04257; Wed, 12 Jul 2000 08:40:11 -0700
X-Virus-Scanned: Wed, 12 Jul 2000 08:40:11 -0700 Nokia Silicon Valley Email
Exploit Scanner
Received: from charliep.iprg.nokia.com (205.226.2.89,
claiming to be "iprg.nokia.com") by
darkstar.iprg.nokia.com(WTS.12.69) smtpdY5eqyY; Wed, 12 Jul 2000
08:39:59 PDT
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
References:
<38FF86A8.563413B8@Motorola.Com>
<002901bfab60$a3b63260$d012060a@hansol.co.kr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <396C9151.DD5B6617@iprg.nokia.com>
Date: Wed, 12 Jul 2000 08:40:01 -0700
Reply-To: charliep@IPRG.NOKIA.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "Charles E. Perkins"
Organization: Nokia Research Center
Subject: Re: [MOBILE-IP] Missing Terminology in RFC2002bis
X-To: "Lee, Jiwoong"
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit
Hello Jiwoong Lee,
I am processing more of the comments that you have submitted
regarding RFC 2002bis. I appreciate that you have taken the time
to contribute these ideas.
As editor, and in consideration of the status of Mobile IP, I feel
that changes to the document need to be selected very judiciously.
Thus, I didn't add two of your suggested terminology definitions,
for reasons as follows.
> Authentication
> The recipient of a message should be able to determine ho the actual
> (real) originator of the message is.
Here's what I wrote:
The process of verifying (using cryptographic techniques, for
all applications in this specification) the identity of the
originator of a message.
> Authorisation
> Provide the ability to an organisation that owns and/or operates a
> network to decide who may attach to the network resources may be
> used by the attaching node.
This term is not used in RFC2002bis, so I didn't use this definition.
It is much more relevant to recent work done in the aaa-wg.
> Location Privacy
> Gives the ability to a sender of a message to control which, if any,
> receivers know the location of the sender's current physical attachment
> to the network. Location privacy is concerned with hiding the location
> of
> an MN from CN's.
Location Privacy does not play a significant role in RFC2002{,bis}. There
is a section describing privacy considerations, but it is self-contained.
Therefore, defining this new term seems unnecessary for understanding
the rest of the document, and unnecessary for understanding the privacy
section.
Thanks again for these comments. If you still think that the other two
terms need to be defined, please send your additional comments to the
mailing list.
Regards,
Charlie P.
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Wed Jul 12 12:23:13 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00651
for ; Wed, 12 Jul 2000 12:23:13 -0400 (EDT)
Received: from standards (47.234.32.16:3831) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7D6CB@standards.nortelnetworks.com>; Wed, 12 Jul 2000 12:12:21 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 2570 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 12 Jul 2000 12:12:21
-0400
Received: from mailhost.iprg.nokia.com by standards.nortelnetworks.com (LSMTP
for Windows NT v1.1b) with SMTP id
<0.FFB7D6CA@standards.nortelnetworks.com>; Wed, 12 Jul 2000 12:12:20
-0400
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 JAA21702
for ; Wed, 12 Jul 2000
09:22:33 -0700 (PDT)
Received: (from root@localhost) by darkstar.iprg.nokia.com
(8.9.3/8.9.3-VIRSCAN) id JAA10895 for
; Wed, 12 Jul 2000 09:22:31
-0700
X-Virus-Scanned: Wed, 12 Jul 2000 09:22:31 -0700 Nokia Silicon Valley Email
Exploit Scanner
Received: from charliep.iprg.nokia.com (205.226.2.89,
claiming to be "iprg.nokia.com") by
darkstar.iprg.nokia.com(WTS.12.69) smtpdSLo8PS; Wed, 12 Jul 2000
09:22:26 PDT
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <396C9B44.21520805@iprg.nokia.com>
Date: Wed, 12 Jul 2000 09:22:28 -0700
Reply-To: charliep@IPRG.NOKIA.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: "Charles E. Perkins"
Organization: Nokia Research Center
Subject: [MOBILE-IP] New version of RFC2002bis
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit
Hello,
I have almost completed editing the new revision of RFC2002bis.
Here is the text of the appendix listing the changes:
=========================================================================
This section lists the changes between this version (...-02.txt) and
the previous version of the document.
- Allowed registrations to be authenticated by use of a security
association between the mobile node and a suitable authentication
entity acceptable to the home agent. Defined "Admissible
Authentication extension" to be an authentication extension that
makes a registration message acceptable to the recipient.
- Allowed registration replies to be processed by the mobile node,
even in the absence of any Mobile-Home Authentication extension,
when containing rejection code by the foreign agent.
- Specified that the mobile node SHOULD take the first care-of
address in a list offered by a foreign agent, and MAY try
each subsequent advertised address in turn if the attempted
registrations are rejected by the foreign agent
- Eliminated Van-Jacobson Compression feature
- Updated assigned numbers lists
- Removed Open Issues
- Still more syntax corrections and editorial improvements
========================================================================
I have made the following resolutions for the Open Issues:
------------------------------------------------------------------------
J. Open Issues
- Whenever the foreign agent can change the Code in a Registration
Reply from the home agent to indicate rejection, the mobile node
can no longer check validity.
This is also true if the foreign agent can change the granted
lifetime in a Registration Reply.
On the other hand, the mobile node could re-calculate with its
record of what Lifetime it had requested, or assuming that the
registration Code was a successful code. Should the revised
draft specify these behaviors?
Answer:
This is addressed by allowing rejection codes to be processed by
the mobile node. If a foreign agent rejects registrations, and it
is bogus, then you don't want to use that foreign agent anyway.
If the foreign agent changes the lifetime, the authentication is
bad and the mobile node SHOULD NOT believe it. The foreign agent
can send back a modified Registration Reply with a rejection Code
if it doesn't like the home agent's modified Lifetime.
This is already covered by the draft.
------------------------------------------------------------------------
- Should we just get rid of the possibility of considering the
Router Addresses in Agent Advertisements?
Answer:
If anyone wants to suggest some further changes to the draft,
then the working group can discuss the changes. Until then,
I don't see any substantial reason to make further changes.
------------------------------------------------------------------------
- From the mailing list:
Q: new FA forwarding text; sometimes two MNs on the same
FA sometimes get traffic forwarded directly rather than
via HA. Also MNs can introduce denial of service if they
make a mistake in their registration messages - sometimes
re-registrations can be redirected at a MN!
Is anything needed here?
Answer:
This is done better by using Binding Updates from the Route Optimization
draft. Thus, it should not be considered an open issue for RFC 2002bis.
------------------------------------------------------------------------
- What does a home agent do with a reverse-tunneled broadcast
packet? Does it send the broadcast on the appropriate network
interface? Does it drop the packet? Does the behavior depend
on whether the mobile node set the 'B' bit in its Registration
Request?
Answer:
These behaviors should be specified by the revised Reverse Tunneling draft.
I suggest moving the open issue to that draft.
------------------------------------------------------------------------
If the changes, and the resolutions to the open issues are acceptable,
I think the draft is ready for Last Call to Draft Standard.
Regards,
Charlie P.
PS. I will send the URL for the revised RFC2002bis soon.
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Wed Jul 12 15:02:44 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09154
for ; Wed, 12 Jul 2000 15:02:42 -0400 (EDT)
Received: from standards (47.234.32.16:2309) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7D7B0@standards.nortelnetworks.com>; Wed, 12 Jul 2000 14:51:43 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 2826 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 12 Jul 2000 14:51:43
-0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7D790@standards.nortelnetworks.com>; Wed, 12 Jul 2000 14:41:42
-0400
Received: from eastmail2.East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM
(8.9.3+Sun/8.9.3) with ESMTP id LAA29139; Wed, 12 Jul 2000 11:51:47
-0700 (PDT)
Received: from atlantic.East.Sun.COM (atlantic.East.Sun.COM [129.148.174.27])
by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP
id OAA22971; Wed, 12 Jul 2000 14:45:25 -0400 (EDT)
Received: from onion.east.sun.com (onion [129.148.174.110]) by
atlantic.East.Sun.COM (8.9.1b+Sun/8.9.1) with SMTP id OAA00445; Wed,
12 Jul 2000 14:46:16 -0400 (EDT)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Message-ID:
Date: Wed, 12 Jul 2000 14:43:01 -0400
Reply-To: Steven Glass - Solaris Software
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
From: Steven Glass - Solaris Software
Subject: Re: [MOBILE-IP] micromobility in IPv6 ?
X-To: charliep@IPRG.NOKIA.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To: "Your message with ID" <396BA989.AC651E2A@iprg.nokia.com>
> Hello Steve,
>
> I'll take the `V' bit out unless somebody complains. I never
> implemented it either.
I don't think it's even implementable, but as I've never tried, how would
I know! Personally, my take is if the bit can be shown to have been
unimplimentable, we can label it reserved for now, and reuse it later, though
I don't know how the general internet community feels about this. Another
argument is as 2002-bis is going to obsolete 2002, only people with current
Mobile IP implementations [of the V-bit] can object (and SHOULD object!);
anyone implementing in the future should be implementing to 2002-bis as RFC,
so if there are no objections now... (nice theory, but does it work?)
> > > I hope this is O.K. It is a lot of work! I expect that I will
> > > make it more easily digestible by defining a new piece of
> > > terminology called something like "Admissible Authentication Extension",
> > > where admissible means admissible to the home agent.
> > ^^^^^^^^^^
> > More like the "home authentication agent", which is similar to 'home
> > agent' only it may not be the home agent doing the authenticating?
>
> Well, all that is needed is that whatever authentication is performed
> has to be _acceptable_ to the home agent. So, I sort-of like the
> "admissible" terminology better for that reason, but I'm still open
> to suggestion...
We're comming towards the same point from different sides, so lets just
get a little closer. "Admissible Mobile-Home Authentication Extension" where
admissible means authenticated in a way acceptable to the home agent. This
means we can also use the term "Admissible Mobile-Foreign Authentication
Extension" where admissible means authenticated in a way acceptable to the
foreign agent (FA passes M-F authentication extension to its AAA server, etc),
and "Admissible Foreign-Home Authentication Extension", etc...
Cheers,
Steve
From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM Wed Jul 12 16:00:24 2000
Received: from standards.nortelnetworks.com (h16s32a234n47.user.nortelnetworks.com [47.234.32.16])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11627
for ; Wed, 12 Jul 2000 16:00:23 -0400 (EDT)
Received: from standards (47.234.32.16:1846) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1b) with SMTP id <0.FFB7D820@standards.nortelnetworks.com>; Wed, 12 Jul 2000 15:49:39 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
(LISTSERV-TCP/IP release 1.8d) with spool id 2973 for
MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 12 Jul 2000 15:49:39
-0400
Received: from motgate2.mot.com by standards.nortelnetworks.com (LSMTP for
Windows NT v1.1b) with SMTP id
<0.FFB7D7FC@standards.nortelnetworks.com>; Wed, 12 Jul 2000 15:39:39
-0400
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by
motgate2.mot.com (motgate2 2.1) with ESMTP id MAA13199 for
; Wed, 12 Jul 2000 12:49:52
-0700 (MST)]
Received: [from il02exi01.comm.mot.com (il02exi01.comm.mot.com [145.1.204.40])
by mothost.mot.com (MOT-mothost 2.0) with ESMTP id MAA10259 for
; Wed, 12 Jul 2000 12:49:52
-0700 (MST)]
Received: by il02exi01.comm.mot.com with Internet Mail Service (5.5.2650.21) id
<3X56VHHD>; Wed, 12 Jul 2000 14:49:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain; charset="ISO-8859-1"
Message-ID: <1DA6058E1005D411BC0600805F31E078616C8D@il02exi01.comm.mot.com>
Date: Wed, 12 Jul 2000 14:49:49 -0500
Reply-To: Stanaway Chris-CCS018
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"