From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Wed Aug  4 12:15:57 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16017
	for <mobileip-archive@LISTS.IETF.ORG>; Wed, 4 Aug 1999 12:15:57 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.A2120300@standards.nortelnetworks.com>; Wed, 4 Aug 1999 12:12:33 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 31747 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 4 Aug 1999 12:11:36 -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.7F6A8D40@standards.nortelnetworks.com>; Wed, 4 Aug 1999
          12:11:35 -0400
Received: from zrchh190 by smtprch1.nortel.com; Wed, 4 Aug 1999 11:05:51 -0500
Received: from zrtpd004.us.nortel.com (actually nrtpd004) by zrchh190; Wed, 4
          Aug 1999 11:16:23 -0500
Received: by zrtpd004.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QG4LW0RS>; Wed, 4 Aug 1999 12:12:39 -0400
X-Mailer: Internet Mail Service (5.5.2448.0)
X-Orig: <ronyoung@americasm01.nt.com>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
X-Orig: <ronyoung@americasm01.nt.com>
Message-ID:  <A56F0B4D52CDD1118F500000F8073C9B01FE3698@crchy272.us.nortel.com>
Date:         Wed, 4 Aug 1999 12:12:11 -0400
Reply-To: Ron Young <ronyoung@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Ron Young <ronyoung@NORTELNETWORKS.COM>
Subject:      [MOBILE-IP] URL to the Mobile IP Archives
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi,

The current URL to the Mobile IP archives as advertised on the IETFs Mobile
IP page is experiencing some problems. Please use the following URL for the
archives:

http://standards.nortelnetworks.com/


------------------------------------------------------------------------
Ron Young   ronyoung@nortelnetworks.com   http://www.nortelnetworks.com/

  You can't spell Nortel without Ron; of course, you can't spell moron
                           without Ron either.


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug  5 15:41:13 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02397
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 5 Aug 1999 15:41:12 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.711CC6E0@standards.nortelnetworks.com>; Thu, 5 Aug 1999 15:37:36 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 32351 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 5 Aug 1999 15:36:10 -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.3DEAD9B0@standards.nortelnetworks.com>; Thu, 5 Aug 1999 15:36:10
          -0400
Received: from engmail1.Eng.Sun.COM ([129.146.1.13]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id MAA03091 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Thu, 5 Aug 1999 12:38:41
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.63.37]) by
          engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          MAA17673 for <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Thu, 5 Aug
          1999 12:38:40 -0700 (PDT)
Received: from hsmpka.Eng.Sun.COM by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id
          MAA08398; Thu, 5 Aug 1999 12:38:31 -0700
X-Mailer: Sun NetMail 2.2.5
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-ID:  <199908051938.MAA08398@hsmpka.eng.sun.com>
Date:         Thu, 5 Aug 1999 12:39:46 -0700
Reply-To: Pat.Calhoun@Eng.Sun.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Patrice Calhoun <Pat.Calhoun@Eng.Sun.COM>
Subject:      [MOBILE-IP] Bake-off issues
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

All,

One of the biggest problems that were found during the bake-off is the fact that
RFC2002 incorrectly states how the computation of the authentication extensions
are done. Charlie Perkins has put together a Mobile-IP v2 draft, and I strongly
urge the Working Group to move this document forward to last call. The issue we
currently have is if someone states that they are RFC2002 compliant, they will not
interoperate with the rest of the world. This is obviously not to the advantage of
the IETF, and the Internet Community.

I strongly propose that the WG chairs move the said document ahead to last call.

On a side note, I have started to put together the bake-off results, but I am still
waiting for the results from two participants (you know who you are:). As soon as I
receive this information I will make it available to the list.

PatC


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug  5 16:44:47 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03523
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 5 Aug 1999 16:44:47 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.6476C680@standards.nortelnetworks.com>; Thu, 5 Aug 1999 16:41:40 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 32403 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 5 Aug 1999 16:40:21 -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.357822C0@standards.nortelnetworks.com>; Thu, 5 Aug 1999 16:40:21
          -0400
Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id NAA26484 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Thu, 5 Aug 1999 13:42:51
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.103.37]) by
          engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          NAA11442; Thu, 5 Aug 1999 13:42:47 -0700 (PDT)
Received: from finesse by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id NAA27629;
          Thu, 5 Aug 1999 13:42:42 -0700
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: +9BCT4YK7PssLr/thTyU6Q==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc
Message-ID:  <199908052042.NAA27629@hsmpka.eng.sun.com>
Date:         Thu, 5 Aug 1999 13:43:00 -0700
Reply-To: Charles Perkins <Charles.Perkins@eng.sun.com>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Charles Perkins <Charles.Perkins@eng.sun.com>
Subject:      [MOBILE-IP] RFC 2002bis (was, Bake-off issues)
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hello all,

There has been a revised protocol specification around now for
several years, which was intended to repair protocol deficiencies
in RFC 2002.  This document, which was produced from working group
input after the previous interoperability test in Andover, MA,
is available at the following URL:
        ftp://ietf.org/internet-drafts/draft-ietf-mobileip-v2-00.txt

The changes in the document are pretty minimal.  It is unfortunate
that the existence of this document was not widely announced before
the bake-off.  That might have saved a lot of headaches.

I think it's likely that, by now, we should include one or two
other changes to RFC2002bis.  For instance, we might make it
mandatory to support reverse tunneling, given the increased
prevalence of ingress filtering.

Another possibility is that we could make these changes along
the way to moving Mobile IP to Draft Standard.

Regards,
Charlie P.

PS. As a matter of terminology, I agree with what others have said,
    that we should not call this Mobile IP version 2.

------------- Begin Forwarded Message -------------

MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Date: Thu, 5 Aug 1999 12:39:46 -0700
From: Patrice Calhoun <Pat.Calhoun@eng.sun.com>
Subject: [MOBILE-IP] Bake-off issues
To:


All,

One of the biggest problems that were found during the bake-off is the fact that
RFC2002 incorrectly states how the computation of the authentication extensions
are done. Charlie Perkins has put together a Mobile-IP v2 draft, and I strongly
urge the Working Group to move this document forward to last call. The issue we
currently have is if someone states that they are RFC2002 compliant, they will
not
interoperate with the rest of the world. This is obviously not to the advantage
of
the IETF, and the Internet Community.

I strongly propose that the WG chairs move the said document ahead to last call.

On a side note, I have started to put together the bake-off results, but I am
still
waiting for the results from two participants (you know who you are:). As soon
as I
receive this information I will make it available to the list.

PatC

------------- End Forwarded Message -------------


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug  5 16:56:44 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04511
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 5 Aug 1999 16:56:43 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.12CCCA80@standards.nortelnetworks.com>; Thu, 5 Aug 1999 16:53:42 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 32428 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 5 Aug 1999 16:51:54 -0400
Received: from gw3.sprintspectrum.com by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.D22A9E30@standards.nortelnetworks.com>; Thu, 5 Aug 1999 16:51:53
          -0400
Received: by gw3.sprintspectrum.com; id PAA13109; Thu, 5 Aug 1999 15:49:59
          -0500 (CDT)
Received: from uskmessoa001.sprintspectrum.com(208.10.75.11) by
          gw3.sprintspectrum.com via smap (V2.0) id xmaa12359; Thu, 5 Aug 99
          15:48:41 -0500
Received: by uskmessoa001.sprintspectrum.com with Internet Mail Service
          (5.5.2448.0) id <QKZ1428D>; Thu, 5 Aug 1999 15:48:40 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <ABA3B5AA1991D21195940060970EB0E3C2AC5B@uskmessoa021.sprintspectrum.com>
Date:         Thu, 5 Aug 1999 15:46:36 -0500
Reply-To: "Lipford, Mark" <MLipfo01@SPRINTSPECTRUM.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "Lipford, Mark" <MLipfo01@SPRINTSPECTRUM.COM>
Subject:      Re: [MOBILE-IP] Consensus vote: Private addresses and Mobile IP
X-To:         "patrik.flykt@NOKIA.COM" <patrik.flykt@NOKIA.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

This sounds like a reasonable solution

                -----Original Message-----
                From:   Patrik Flykt [mailto:patrik.flykt@NOKIA.COM]
                Sent:   Friday, July 30, 1999 7:17 AM
                To:     MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
                Subject:        Re: [MOBILE-IP] Consensus vote: Private
addresses and Mobile IP

                        Hello,

                > 1. Use co-located care of address as an option for mobile
nodes with
                >    private addresses when they are roaming outside their
                >    administrative domains.
                >
                > 2. Mandatory reverse tunneling for mobile nodes that
prefer to use
                >    the Foreign Agents Care Of Address but have a private
address.

                Correct me if I'm wrong, but shouldn't both co-located COAs
and FA COAs be
                equally supported ? Sometimes the MN will roam into a
network with Foreign
                Agent functionality, and sometimes it will acquire an
address by DHCP or
                some other means. I think both options should be supported,
therefore I
                believe that both 1) and 2) should be done.

                Regards,

                        Patrik Flykt


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug  5 17:17:07 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06191
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 5 Aug 1999 17:17:06 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.BBBEFEE0@standards.nortelnetworks.com>; Thu, 5 Aug 1999 17:12:44 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 32461 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 5 Aug 1999 17:11:21 -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.8A0A89F0@standards.nortelnetworks.com>; Thu, 5 Aug 1999
          17:11:21 -0400
Received: from zrchh190 by smtprch1.nortel.com; Thu, 5 Aug 1999 15:21:05 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Thu, 5
          Aug 1999 15:32:17 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QKP6VKXZ>; Thu, 5 Aug 1999 15:28:26 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-Orig: <bpatil@americasm01.nt.com>
X-Orig: <bpatil@americasm01.nt.com>
Message-ID:  <61DEB565F616D31187880000F805A8D5817E29@crchy270.us.nortel.com>
Date:         Thu, 5 Aug 1999 15:28:06 -0500
Reply-To: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Subject:      Re: [MOBILE-IP] Bake-off issues
X-To:         "Pat.Calhoun@Eng.Sun.COM" <Pat.Calhoun@Eng.Sun.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

>All,
>
>One of the biggest problems that were found during the bake-off is the
>fact that RFC2002 incorrectly states how the computation of the
>authentication extensions are done. Charlie Perkins has put together a
>Mobile-IP v2 draft, and I strongly urge the Working Group to move this
>document forward to last call. The issue we currently have is if
>someone states that they are RFC2002 compliant, they will not
>interoperate with the rest of the world. This is obviously not to the
>advantage of the IETF, and the Internet Community.
>
>I strongly propose that the WG chairs move the said document ahead to
>last call.
>
>On a side note, I have started to put together the bake-off results,
>but I am still waiting for the results from two participants (you know
>who you are:). As soon as I receive this information I will make it
>available to the list.
>
>PatC
>

Pat,

First of all the name draft-ietf-mobileip-v2-00.txt draft needs to be
changed to reflect a more appropriate title. Additionally this draft
does more than just clarify how the computaion of the authentication
extensions MUST be done. We need to discuss the addendums and
clarifications that this draft proposes before acting on it. Maybe
Charlie (as the editor) would like to summarize the differences of
this draft with 2002?

-Basavaraj



From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug  5 17:19:17 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06389
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 5 Aug 1999 17:19:17 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.04DAD0E0@standards.nortelnetworks.com>; Thu, 5 Aug 1999 17:14:47 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 32489 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 5 Aug 1999 17:13:44 -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.DF73ED00@standards.nortelnetworks.com>; Thu, 5 Aug 1999 17:13:44
          -0400
Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id OAA08978; Thu, 5 Aug 1999 14:16:16
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (hsmpka.Eng.Sun.COM [129.146.101.47]) by
          engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          OAA12924; Thu, 5 Aug 1999 14:16:13 -0700 (PDT)
Received: from westapp by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id OAA09211;
          Thu, 5 Aug 1999 14:16:02 -0700
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailer: Sun(TM) Web Access 1.0
Message-ID:  <492218854.933887762387.JavaMail.pcalhoun@hsmpka.Eng.Sun.COM>
Date:         Thu, 5 Aug 1999 14:16:02 -0700
Reply-To: Pat.Calhoun@ENG.SUN.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pat.Calhoun@ENG.SUN.COM
Subject:      [MOBILE-IP] Mobile-IP DIAMETER Extension - New rev
X-To:         diameter@ipass.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

First, I want to appologize for the cross-post, but it seemed like a good idea.

I have just finished cleaning up the Mobile-IP Extension draft, and it is now
available at www.diameter.org. I would like to appologize for the poor state that the web page is in, but I really have not had time to clean it up very much (hey, it's only been a day).

Most of the fixes in the draft were related to issues and clarifications needed as a result of the bake-off. However, there are a few that are a result of minor changes to the base protocol, which is also available on the web site.

I would like to get initial feedback before I send it out to the secretariat.

I am including a list of the changes made to the spec below.

PatC

1.2  Changes in version -03

   The following are the changes done to version 03 of the draft:

      - Cleaned up the AVP Header flags

      - The Command Code sections now show an optional Proxy-State AVP
      as part of the message format.

      - The previous version required that the MIP-Registration-Reply be
      present in the AMA, but the AVP could not be present if the AAAH
      could not service the request. The AVP is now only mandatory if
      the AMA is successful.

      - Cleaned up the description of the various key and SPI AVPs.

      - Added text in section 4.1 that describes how the AAAH can cache
      the keys directed for the AAAF so they can be included in the
      message when the response is received by the HA. This was the
      point that cause interoperability at the bake-off due to the fact
      that it was quite unclear.

      - Section 4.1 now correctly states that the Home-Address AVP MUST
      be present and MAY have a value of 0.0.0.0.

      - Section 4.1 now also states that the Mobile-IP FA-HA and the MN-
      HA authentication extensions must be used.

      - Added a reference to ESP

      - Added IANA Considerations


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug  5 17:25:50 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06811
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 5 Aug 1999 17:25:50 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.24E733F0@standards.nortelnetworks.com>; Thu, 5 Aug 1999 17:22:50 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 32457 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 5 Aug 1999 17:21:19 -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.8872D2F0@standards.nortelnetworks.com>; Thu, 5 Aug 1999
          17:11:18 -0400
Received: from zrchh190 by smtprch1.nortel.com; Thu, 5 Aug 1999 14:48:42 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Thu, 5
          Aug 1999 14:59:41 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QKP6VGRR>; Thu, 5 Aug 1999 14:55:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-Orig: <haseeb@americasm01.nt.com>
X-Orig: <haseeb@americasm01.nt.com>
Message-ID:  <3135632FC861D2118F2A0000F806EEEC01C3CC94@zrchb199.us.nortel.com>
Date:         Thu, 5 Aug 1999 14:55:41 -0500
Reply-To: Haseeb Akhtar <haseeb@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Haseeb Akhtar <haseeb@NORTELNETWORKS.COM>
Subject:      Re: [MOBILE-IP] Bake-off issues
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hello all,

I strongly agree with Pat that we need to move ahead with Charlie's updated
draft.

Specially the issue of including SPI field in the list of protective fields
(section 3.5.1) to compute the authenticator value.

The change needed is on page 28, section 3.5.1. The third bullet after the
first paragraph should say "the Type, Length and SPI of this Extension"
instead of "the Type and Length of this Extension".

Regards,

Haseeb

> -----Original Message-----
> From: Patrice Calhoun [SMTP:Pat.Calhoun@ENG.SUN.COM]
> Sent: Thursday, August 05, 1999 2:40 PM
> To:   mobile-ip@standards.nortelnetworks.com
> Subject:      [MOBILE-IP] Bake-off issues
>
> All,
>
> One of the biggest problems that were found during the bake-off is the
> fact that
> RFC2002 incorrectly states how the computation of the authentication
> extensions
> are done. Charlie Perkins has put together a Mobile-IP v2 draft, and I
> strongly
> urge the Working Group to move this document forward to last call. The
> issue we
> currently have is if someone states that they are RFC2002 compliant, they
> will not
> interoperate with the rest of the world. This is obviously not to the
> advantage of
> the IETF, and the Internet Community.
>
> I strongly propose that the WG chairs move the said document ahead to last
> call.
>
> On a side note, I have started to put together the bake-off results, but I
> am still
> waiting for the results from two participants (you know who you are:). As
> soon as I
> receive this information I will make it available to the list.
>
> PatC


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug  5 18:09:53 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10006
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 5 Aug 1999 18:09:53 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.4BD5BA80@standards.nortelnetworks.com>; Thu, 5 Aug 1999 18:06:52 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 32562 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 5 Aug 1999 18:05:42 -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.2169BE40@standards.nortelnetworks.com>; Thu, 5 Aug 1999
          18:05:41 -0400
Received: from zrchh190 by smtprch1.nortel.com; Thu, 5 Aug 1999 16:21:10 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Thu, 5
          Aug 1999 16:32:06 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QKP6VSC3>; Thu, 5 Aug 1999 16:28:15 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-Orig: <haseeb@americasm01.nt.com>
X-Orig: <haseeb@americasm01.nt.com>
Message-ID:  <3135632FC861D2118F2A0000F806EEEC01C3CC97@zrchb199.us.nortel.com>
Date:         Thu, 5 Aug 1999 16:28:13 -0500
Reply-To: Haseeb Akhtar <haseeb@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Haseeb Akhtar <haseeb@NORTELNETWORKS.COM>
Subject:      Re: [MOBILE-IP] Mobile-IP DIAMETER Extension - New rev
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Pat,

What about merging AMR/HAR and AMA/HAA together into just two messages? That
is leave AMR and AMA, delete HAR and HAA? AAA server does not need to create
a state to remember that AMR will have to be mapped into HAR and vice versa.
All the functionality of HAR/HAA can easily be deployed with AMR/AMA.

What do you think?

Regards,

Haseeb

> -----Original Message-----
> From: Pat.Calhoun@ENG.SUN.COM [SMTP:Pat.Calhoun@ENG.SUN.COM]
> Sent: Thursday, August 05, 1999 4:16 PM
> To:   mobile-ip@standards.nortelnetworks.com
> Subject:      [MOBILE-IP] Mobile-IP DIAMETER Extension - New rev
>
> First, I want to appologize for the cross-post, but it seemed like a good
> idea.
>
> I have just finished cleaning up the Mobile-IP Extension draft, and it is
> now
> available at www.diameter.org. I would like to appologize for the poor
> state that the web page is in, but I really have not had time to clean it
> up very much (hey, it's only been a day).
>
> Most of the fixes in the draft were related to issues and clarifications
> needed as a result of the bake-off. However, there are a few that are a
> result of minor changes to the base protocol, which is also available on
> the web site.
>
> I would like to get initial feedback before I send it out to the
> secretariat.
>
> I am including a list of the changes made to the spec below.
>
> PatC
>
> 1.2  Changes in version -03
>
>    The following are the changes done to version 03 of the draft:
>
>       - Cleaned up the AVP Header flags
>
>       - The Command Code sections now show an optional Proxy-State AVP
>       as part of the message format.
>
>       - The previous version required that the MIP-Registration-Reply be
>       present in the AMA, but the AVP could not be present if the AAAH
>       could not service the request. The AVP is now only mandatory if
>       the AMA is successful.
>
>       - Cleaned up the description of the various key and SPI AVPs.
>
>       - Added text in section 4.1 that describes how the AAAH can cache
>       the keys directed for the AAAF so they can be included in the
>       message when the response is received by the HA. This was the
>       point that cause interoperability at the bake-off due to the fact
>       that it was quite unclear.
>
>       - Section 4.1 now correctly states that the Home-Address AVP MUST
>       be present and MAY have a value of 0.0.0.0.
>
>       - Section 4.1 now also states that the Mobile-IP FA-HA and the MN-
>       HA authentication extensions must be used.
>
>       - Added a reference to ESP
>
>       - Added IANA Considerations


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug  5 19:30:03 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13586
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 5 Aug 1999 19:30:02 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.7FE869C0@standards.nortelnetworks.com>; Thu, 5 Aug 1999 19:27:04 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 32699 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 5 Aug 1999 19:25:42 -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.4E95C3E0@standards.nortelnetworks.com>; Thu, 5 Aug 1999 19:25:42
          -0400
Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id QAA26340; Thu, 5 Aug 1999 16:28:12
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (hsmpka.Eng.Sun.COM [129.146.55.47]) by
          engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          QAA10086; Thu, 5 Aug 1999 16:28:08 -0700 (PDT)
Received: from westapp by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id QAA22884;
          Thu, 5 Aug 1999 16:28:06 -0700
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailer: Sun(TM) Web Access 1.0
Message-ID:  <492639018.933895686719.JavaMail.pcalhoun@hsmpka.Eng.Sun.COM>
Date:         Thu, 5 Aug 1999 16:28:06 -0700
Reply-To: Pat.Calhoun@ENG.SUN.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pat.Calhoun@ENG.SUN.COM
Subject:      Re: [MOBILE-IP] Mobile-IP DIAMETER Extension - New rev
X-To:         Haseeb Akhtar <haseeb@NORTELNETWORKS.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

>Pat,
>
>What about merging AMR/HAR and AMA/HAA together into just two messages? That
>is leave AMR and AMA, delete HAR and HAA? AAA server does not need to create
>a state to remember that AMR will have to be mapped into HAR and vice versa.
>All the functionality of HAR/HAA can easily be deployed with AMR/AMA.
>
>What do you think?

Haseeb,

Yes I do remember talking about this and I tentatively agreed to make the change. This was obviously not part of the bake-off. I have no real issue with making this change, but I want to make sure that everyone else (that cares) is also in agreement.

Any comments, objections, flames from the rest of the WG?

PatC
>
>Regards,
>
>Haseeb
>
>> -----Original Message-----
>> From: Pat.Calhoun@ENG.SUN.COM [SMTP:Pat.Calhoun@ENG.SUN.COM]
>> Sent: Thursday, August 05, 1999 4:16 PM
>> To:   mobile-ip@standards.nortelnetworks.com
>> Subject:      [MOBILE-IP] Mobile-IP DIAMETER Extension - New rev
>>
>> First, I want to appologize for the cross-post, but it seemed like a good
>> idea.
>>
>> I have just finished cleaning up the Mobile-IP Extension draft, and it is
>> now
>> available at www.diameter.org. I would like to appologize for the poor
>> state that the web page is in, but I really have not had time to clean it
>> up very much (hey, it's only been a day).
>>
>> Most of the fixes in the draft were related to issues and clarifications
>> needed as a result of the bake-off. However, there are a few that are a
>> result of minor changes to the base protocol, which is also available on
>> the web site.
>>
>> I would like to get initial feedback before I send it out to the
>> secretariat.
>>
>> I am including a list of the changes made to the spec below.
>>
>> PatC
>>
>> 1.2  Changes in version -03
>>
>>    The following are the changes done to version 03 of the draft:
>>
>>       - Cleaned up the AVP Header flags
>>
>>       - The Command Code sections now show an optional Proxy-State AVP
>>       as part of the message format.
>>
>>       - The previous version required that the MIP-Registration-Reply be
>>       present in the AMA, but the AVP could not be present if the AAAH
>>       could not service the request. The AVP is now only mandatory if
>>       the AMA is successful.
>>
>>       - Cleaned up the description of the various key and SPI AVPs.
>>
>>       - Added text in section 4.1 that describes how the AAAH can cache
>>       the keys directed for the AAAF so they can be included in the
>>       message when the response is received by the HA. This was the
>>       point that cause interoperability at the bake-off due to the fact
>>       that it was quite unclear.
>>
>>       - Section 4.1 now correctly states that the Home-Address AVP MUST
>>       be present and MAY have a value of 0.0.0.0.
>>
>>       - Section 4.1 now also states that the Mobile-IP FA-HA and the MN-
>>       HA authentication extensions must be used.
>>
>>       - Added a reference to ESP
>>
>>       - Added IANA Considerations
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug  6 03:30:50 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03971
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 6 Aug 1999 03:30:50 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.94BB8BF0@standards.nortelnetworks.com>; Fri, 6 Aug 1999 3:27:16 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 32838 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 6 Aug 1999 03:25:16 -0400
Received: from netra-i (202.120.127.219) by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.E692D980@standards.nortelnetworks.com>; Fri, 6 Aug 1999 3:15:14
          -0400
Received: from 202.120.127.219 by netra-i (SMI-8.6/SMI-SVR4) id PAA00449; Fri,
          6 Aug 1999 15:30:50 +0900
Message-ID:  <>
Date:         Fri, 6 Aug 1999 00:06:58 EST
Reply-To: lkjljhjh@ZOOM.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: lkjljhjh@ZOOM.COM
Subject:      [MOBILE-IP] Accept Credit Cards Online!!!
X-To:         Friend@public.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

INCREASE SALES UP TO 100%
ACCEPT CREDIT CARDS OVER THE INTERNET *** NO SETUP FEES
ONLY $49.95 TO GET STARTED!!!

Good Credit / Bad Credit/ No Credit **** NO PROBLEM****!!!
It Just Doesn't Matter - Everyone Gets Approved
No Upfront Fees For Application-Processing
While Others Charge You From $195 TO $250 To Get Set Up
WE CHARGE ZERO FOR SETUP FEES!!
Limited Offer So Take Advantage Of It!!
We Specialize In Servicing The Following:
*Multilevel Marketing
*Mail Order/Phone Sales
*At Home Business*INTERNET BASED BUSINESS
*New Business*Small Business
Whatever!!! We Do It All!!! Everyone Is Welcome!

Call us toll free today 1-800-242-0363 ext. 2112

What Can We Do For Your Company????

>>>>>INTERNET SERVICE<<<<<

SECURE REAL-TIME ON-LINE TRANSACTIONS make it as easy as
possible for your customers to purchase your products or
services.  We use SSL SECURITY (best on the NET today).

Now tell me if this doesn't sound intriguing, lets say a
customer visits your web site and decides they want to buy
your product(s) or service(s). They would simply enter
their credit card information and receive an approval
WITHIN 5 SECONDS.  That's all there is to it!!!

From that point on, the sale is complete and the money will
be directly deposited into your business checking account
within 24 to 48 hours.  So you will have LIQUID ASSETS
AVAILABLE ALMOST IMMEDIATELY!!!!

Your customer will be e-mailed a receipt and you will be
e-mailed an invoice slip, all instantaneously.  Now, since
this program is automated for 24 hours a day 7 days a week,
you will be receiving orders and making money in your sleep!
IT'S JUST THAT EASY!!!!

WHAT MAKES US SO SPECIAL?????

* We process over $4 Billion in credit card transactions
  every year.
* We have over 100,000 merchants online and growing.
* We offer secured on-line real time transactions.
* We offer 24 hour customer service 7 days a week in 17
  different languages.
* We offer complete training and installation through our
  technical support group.
* We offer a life time warranty and unlimited upgrades.
* We help make money for your company and your customers.


>>>>>CONTACT INFORMATION<<<<<

Just place a toll free phone call to 1-800-242-0363 ext. 2112.
Leave a message with your Name, Phone Number, and a brief
description of your type of business.

Once you call, an account executive will contact you within
24 hours to discuss your options, answer your questions, and
start you on your way to financial success.

DON'T DELAY!!!! ACT TODAY!!!
____________________________________________________________
To Unsubscribe from this mailing list please send and email
to angie.p@mailcity.com


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug  6 07:29:48 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05245
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 6 Aug 1999 07:29:47 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.021416B0@standards.nortelnetworks.com>; Fri, 6 Aug 1999 7:26:32 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 33049 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 6 Aug 1999 07:24:47 -0400
Received: from jm2.epitest.fi (194.241.247.32) by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.C349DEB0@standards.nortelnetworks.com>; Fri, 6 Aug 1999 7:24:47
          -0400
Received: (qmail 4358 invoked by uid 500); 6 Aug 1999 11:27:17 -0000
Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Aug
          1999 11:27:17 -0000
X-Sender: jm@jm2.epitest.fi
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-ID:  <Pine.LNX.4.10.9908061423160.4349-100000@jm2.epitest.fi>
Date:         Fri, 6 Aug 1999 14:27:17 +0300
Reply-To: Jouni Malinen <jkmaline@CC.HUT.FI>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Jouni Malinen <jkmaline@CC.HUT.FI>
Subject:      [MOBILE-IP] RFC 2002bis (was: Bake-off issues)
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <199908051938.MAA08398@hsmpka.eng.sun.com>

Unfortunately we could not take part in the Bake-off, so I'm sending
our comments on the RFC 2002bis and compatibility issues to the Mobile
IP list. I'm, however, looking forward to the results of the Bake-off
session.

Is the goal with RFC 2002bis to maintain the compatibility with RFC
2002 and the older implementation? In that case we think that the
following details should be taken into account.

I include a brief list here due to the length of the message:
- authentication extension usage
- duplicate reply types with RFC 2344
- >255-byte extension data
- co-located COA clarification


On Thu, 5 Aug 1999, Patrice Calhoun wrote:

> One of the biggest problems that were found during the bake-off is the
> fact that RFC2002 incorrectly states how the computation of the
> authentication extensions are done. Charlie Perkins has put together a
> Mobile-IP v2 draft, and I strongly urge the Working Group to move this
> document forward to last call. The issue we currently have is if
> someone states that they are RFC2002 compliant, they will not
> interoperate with the rest of the world. This is obviously not to the
> advantage of the IETF, and the Internet Community.

This authentication extension computation clearly needs clarification. If
the protected area is simply changed (like in
draft-ietf-mobileip-v2-00.txt), it would break the compatibility with the
older RFC 2002 compliant implementations. I don't think this is wanted and
luckily, in most cases, not even needed. It is possible to make the new
implementations compatible with the older ones (that are using the RFC
2002 compliant method, i.e. SPI not included in the protected area) as far
as the authentication between MN and HA is concerned.

While trying to get our implementation (Dynamics - HUT Mobile IP) to work
with others we used a compatibility mode that has an automated fall-back
to use the data area without SPI if the other end (MN/HA) is using the
older method. This way the compatibility is maintained with RFC 2002. The
first try would be to include the SPI in the protected area.

As far as the registration request from RFC 2002 compliant MN is
concerned, the compatibility mode does not introduce any new message
exchanges. The HA can first check, whether a MAC calculated with SPI
matches - if it doesn't, then a MAC calculated without SPI is checked. If
the HA notices that the MN is using a RFC 2002 method, it records this
information in the binding data and uses the compatibility mode in the
replies. This adds only one additional MD5 operation.

If it is the HA that is RFC 2002 compliant, there will be one additional
registration/request round when the MN registers for the first time. The
HA should reply with code 131 (mobile node failed authentication; RFC
2002, Chap. 3.8.2.1). The MN can then try to send the same registration
request with RFC 2002 compliant method. If this registration succeeds, the
MN uses the older method in the following registrations.

The other authentication extensions (MN-FA, FA-HA) may bring a bit more
problems as the FA must silently discard messages that failed the
authentication. So, MN-FA auth. ext. with RFC 2002 compliant FA would not
get a reply. The MN could of course try (after some time) to use the RFC
2002 compliant method, but this is not as clear a solution as with the
MN-HA case. The FA-HA case is easier, as even the older HA should reply
with code 132 (Chap. 3.8.2.1) and FA should reply with code 68 (Chap.
3.7.3.1).

I would propose, that the compatibility issue would at least be mentioned
in the draft that would eventually obsolete RFC 2002. The above described
method of providing compatibility could be added as an optional (MAY or
even SHOULD) feature.


As far as the other points in draft-ietf-mobileip-v2-00.txt are concerned,
there is couple of things that would seem to need some fixing. As a quick
remainder I might mention the duplicate codes with RFC 2344 (codes 74 and
75; see my message of July 3 to this list and Gabriel Montenegro's reply
to it).

In addition, I think that there is a potential problem spot in the
extension usage when the length of the extensions is over 255 bytes. RFC
2002 clearly states that the extension header has 8-bit long length field
(Chap 1.9). There is, however, at least couple of drafts that define
extensions with 16-bit long length field (expired
draft-ietf-mobileip-regkey-00.txt and
draft-gupta-mobileip-inline-secparams-00.txt).

The use of 16-bit long length field would clearly make it impossible
for an agent that does not know the extension to parse the message. As
far as the extensions type is between 0 and 127, this may not be very
big a problem as the message would be discarded anyway. I don't think
that this is a proper way of handling the longer extensions. The RFC
2002bis should thus have some clarification on the issue of using
longer extensions. I would propose, that a compatible method would be
used. One way would be to devide the extension data to 255 byte
fragments and have multiple extensions with same type field and a
length of 255 (and the last fragment with the remaining bytes). This
way the compatibility would be maintained. In addition, the extra
space needed for the duplicate type fields would be minimal (two bytes
for each 255 bytes of data; in case the extension would be under 256
long this would even save one byte (compared to 16-bit length field)
and with <512 bytes of data the required length would be same).


As a last point of this already long enough message I would also like to
have some clarification on the use of co-located COA and FA registration.
RFC 2002 (2.4.1) states that the MN should register through the FA even if
it might be able to get own co-loc. COA. Does this mean that the MN must
use FA decapsulation in that case or is it allowed to register with its
acquired co-loc. COA through FA?

The co-loc. COA is apparently used mostly in direct connection with
the HA. We have, used it in our implementation as a normal method of
registering through FA. The difference is, though, that we are
concentrating on hierarchical FA structure and use private address
space for the co-loc. COA.


PS.

We just released the new version of our software, Dynamics - HUT Mobile IP
v0.5, and people interested in our solutions can get more information
from our website at http://www.cs.hut.fi/Research/Dynamics/.


--
Jouni Malinen


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug  6 11:57:24 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18570
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 6 Aug 1999 11:57:24 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.5B020CD0@standards.nortelnetworks.com>; Fri, 6 Aug 1999 11:53:53 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 33234 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 6 Aug 1999 11:52:43 -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.316F0B70@standards.nortelnetworks.com>; Fri, 6 Aug 1999
          11:52:43 -0400
Received: from zrchh190 by smtprch1.nortel.com; Fri, 6 Aug 1999 10:18:13 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Fri, 6
          Aug 1999 10:29:26 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QKP6XLTS>; Fri, 6 Aug 1999 10:25:31 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-Orig: <bpatil@americasm01.nt.com>
X-Orig: <bpatil@americasm01.nt.com>
Message-ID:  <61DEB565F616D31187880000F805A8D5817E30@crchy270.us.nortel.com>
Date:         Fri, 6 Aug 1999 10:24:03 -0500
Reply-To: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Subject:      [MOBILE-IP] Draft naming policy
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

The current policy for draft names/titles for this WG is to determine
whether
a draft is within the scope of the charter and, if so, to include
"draft-ietf-mobileip" in the title.
To this end when a new draft (-00) is submitted to
internet-drafts@ietf.org with "ietf-mobileip" in the title, the
secretariat will ask the working group chairs whether the draft is
within the scope of the working group's charter.  If the objective of
the draft is clear and falls within the scope of the mobile-ip
charter, the chairs will okay it.  If it's unclear to the chairs
whether it's within the scope of the charter, the chairs will ask the
working group whether to consider it.  This process will not delay a
draft that is close to a deadline, because its submission will have
been noted by the secretariat.   All other drafts that may be in the
domain of mobile-ip should be submitted as a personal draft
"draft-xyz-mobileip-."  It is important to include mobileip in the
title since it makes it easier for the working group to find drafts
related to mobileip.


Basavaraj Patil
Phil Roberts


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug  6 11:57:25 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18572
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 6 Aug 1999 11:57:24 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.5B2CED60@standards.nortelnetworks.com>; Fri, 6 Aug 1999 11:53:53 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 33238 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 6 Aug 1999 11:52:46 -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.32FF9680@standards.nortelnetworks.com>; Fri, 6 Aug 1999
          11:52:46 -0400
Received: from zrchh190 by smtprch1.nortel.com; Fri, 6 Aug 1999 10:18:51 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Fri, 6
          Aug 1999 10:29:58 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QKP6XLXK>; Fri, 6 Aug 1999 10:26:02 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-Orig: <bpatil@americasm01.nt.com>
X-Orig: <bpatil@americasm01.nt.com>
Message-ID:  <61DEB565F616D31187880000F805A8D5817E31@crchy270.us.nortel.com>
Date:         Fri, 6 Aug 1999 10:25:17 -0500
Reply-To: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Subject:      [MOBILE-IP] Drafts Cleanup
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hello,

One of the outstanding items of the Mobile IP WG meeting held at
IETF45 was to clean up the current drafts that have the title
draft-ietf-mobileip-xyz but are not necessarily agreed upon WG
documents. These drafts can be resubmitted as personal drafts
(eg: draft-myname-mobileip-xyz). The drafts that we believe are not WG
documents at this time are listed below. These drafts which also show
up on the IETFs Mobile IP page will be removed shortly.

Current Mobile IP WG documents:
-------------------------------

- Route Optimization in Mobile IP (draft-ietf-mobileip-optim-08.txt)

- Mobility Support in IPv6 (draft-ietf-mobileip-ipv6-08.txt)

- IP Mobility Support version 2 (draft-ietf-mobileip-v2-00.txt)
  Needs to be renamed.

- Registration Keys for Route Optimization
  (draft-ietf-mobileip-regkey-00.txt)

- Special Tunnels for Mobile IP (draft-ietf-mobileip-spectun-00.txt)

- Mobile IP Challenge/Response Extensions
  (draft-ietf-mobileip-challenge-02.txt)

- Mobile IP Network Address Identifier Extension
  (draft-ietf-mobileip-mn-nai-03.txt)

Drafts that may be considered as WG documents:
----------------------------------------------

We will consider these drafts as WG documents after ascertaining that
these fit in the scope of the charter and has WG consensus. These
drafts need to be resubmitted as personal drafts at this time and can be
renamed as WG documents when we have agreement.

- IP micro-mobility support using HAWAII
  (draft-ietf-mobileip-hawaii-00.txt)

- Paging support for IP mobility using HAWAII
  (draft-ietf-mobileip-paging-hawaii-00.txt)

- Requirements on Mobile IP from a Cellular Perspective
  (draft-ietf-mobileip-cellular-requirements-02.txt)

Drafts that will be removed from the Mobile IP page:
----------------------------------------------------

Some of these drafts have expired or may not be in the scope of the
charter at the present time. You may wish to resubmit them to the
drafts editor.

- Firewall Support for Mobile IP
  (draft-montenegro-firewall-sup-03.txt)

- Tunnel Establishment Protocol
  (draft-ietf-mobileip-calhoun-tep-01.txt)

- Rapid Authentication for Mobile IP (draft-ietf-mobileip-ra-00.txt)

- Use of IPSec in Mobile IP (draft-ietf-mobileip-ipsec-use-00.txt)

- Support for Mobile IP in Roaming
  (draft-ietf-roamops-mobileip-02.txt)

- Mobile IP Dynamic Home Address Allocation Extensions
  (draft-ietf-mobileip-home-addr-alloc-00.txt)

- Mobile IP Regionalized Tunnel Management
  (draft-ietf-mobileip-reg-tunnel-00.txt)

- NAI Resolution for Wireless Networks
  (draft-ietf-mobileip-nai-wn-00.txt)

- IP Mobility Architecture Framework
  (draft-ietf-mobileip-ipm-arch-00.txt)

- Simple Mobile IP (SMIP)(draft-ietf-mobileip-simple-01.txt)

- AAA Registration Keys for Mobile IP
  (draft-ietf-mobileip-aaa-key-00.txt) - explain

- Private Addresses in Mobile IP (draft-ietf-mobileip-privaddr-00.txt)
  Although this topic is in the charter, we are having a discussion on
  the mailing list at this time on the approach the WG wants to
  take. Hence this draft may be reconsidered at a later time.


Also please note the draft naming policy for this WG as discussed in
IETF45 (previous e-mail).

Basavaraj Patil
Phil Roberts


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug  6 13:03:13 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20322
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 6 Aug 1999 13:03:12 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.9831DFA0@standards.nortelnetworks.com>; Fri, 6 Aug 1999 13:00:01 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 33325 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 6 Aug 1999 12:58:26 -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.5F1D2440@standards.nortelnetworks.com>; Fri, 6 Aug 1999 12:58:25
          -0400
Received: from engmail3.Eng.Sun.COM ([129.144.170.5]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id KAA10581; Fri, 6 Aug 1999 10:00:58
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.93.37]) by
          engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          KAA16820; Fri, 6 Aug 1999 10:00:57 -0700 (PDT)
Received: from westapp by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id KAA15323;
          Fri, 6 Aug 1999 10:00:56 -0700
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailer: Sun(TM) Web Access 1.0
Message-ID:  <492645476.933958856076.JavaMail.pcalhoun@hsmpka.Eng.Sun.COM>
Date:         Fri, 6 Aug 1999 10:00:56 -0700
Reply-To: Pat.Calhoun@ENG.SUN.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pat.Calhoun@ENG.SUN.COM
Subject:      Re: [MOBILE-IP] Mobile-IP DIAMETER Extension - New rev
X-To:         Haseeb Akhtar <haseeb@NORTELNETWORKS.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

Haseeb,

I have been thinking a little about this one, and I do have a question. The AMR and the HAR both require different AVPs to be present, as does the HAA and the AMA. Therefore, if we combine both of these messages into one, it would increase the complexity of the implementation in trying to determine the intent of such a message.

Could you provide me with a reasonable argument for merging both command codes. I am sorry to bring this up so late in the game, but this just occurred to me.

BTW, It is not clear to me that this is the correct forum to discuss design of DIAMETER extensions given that the WG has not yet accepted any specific protocols, but I also cannot think of where else it could be discussed. Perhaps the DIAMETER mailing list?

Thanks

PatC

>Pat,
>
>What about merging AMR/HAR and AMA/HAA together into just two messages? That
>is leave AMR and AMA, delete HAR and HAA? AAA server does not need to create
>a state to remember that AMR will have to be mapped into HAR and vice versa.
>All the functionality of HAR/HAA can easily be deployed with AMR/AMA.
>
>What do you think?
>
>Regards,
>
>Haseeb
>
>> -----Original Message-----
>> From: Pat.Calhoun@ENG.SUN.COM [SMTP:Pat.Calhoun@ENG.SUN.COM]
>> Sent: Thursday, August 05, 1999 4:16 PM
>> To:   mobile-ip@standards.nortelnetworks.com
>> Subject:      [MOBILE-IP] Mobile-IP DIAMETER Extension - New rev
>>
>> First, I want to appologize for the cross-post, but it seemed like a good
>> idea.
>>
>> I have just finished cleaning up the Mobile-IP Extension draft, and it is
>> now
>> available at www.diameter.org. I would like to appologize for the poor
>> state that the web page is in, but I really have not had time to clean it
>> up very much (hey, it's only been a day).
>>
>> Most of the fixes in the draft were related to issues and clarifications
>> needed as a result of the bake-off. However, there are a few that are a
>> result of minor changes to the base protocol, which is also available on
>> the web site.
>>
>> I would like to get initial feedback before I send it out to the
>> secretariat.
>>
>> I am including a list of the changes made to the spec below.
>>
>> PatC
>>
>> 1.2  Changes in version -03
>>
>>    The following are the changes done to version 03 of the draft:
>>
>>       - Cleaned up the AVP Header flags
>>
>>       - The Command Code sections now show an optional Proxy-State AVP
>>       as part of the message format.
>>
>>       - The previous version required that the MIP-Registration-Reply be
>>       present in the AMA, but the AVP could not be present if the AAAH
>>       could not service the request. The AVP is now only mandatory if
>>       the AMA is successful.
>>
>>       - Cleaned up the description of the various key and SPI AVPs.
>>
>>       - Added text in section 4.1 that describes how the AAAH can cache
>>       the keys directed for the AAAF so they can be included in the
>>       message when the response is received by the HA. This was the
>>       point that cause interoperability at the bake-off due to the fact
>>       that it was quite unclear.
>>
>>       - Section 4.1 now correctly states that the Home-Address AVP MUST
>>       be present and MAY have a value of 0.0.0.0.
>>
>>       - Section 4.1 now also states that the Mobile-IP FA-HA and the MN-
>>       HA authentication extensions must be used.
>>
>>       - Added a reference to ESP
>>
>>       - Added IANA Considerations
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug  6 16:10:57 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23329
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 6 Aug 1999 16:10:56 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.C685ECB0@standards.nortelnetworks.com>; Fri, 6 Aug 1999 16:07:26 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 33495 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 6 Aug 1999 16:05:55 -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.901FD690@standards.nortelnetworks.com>; Fri, 6 Aug 1999 16:05:54
          -0400
Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id NAA27687; Fri, 6 Aug 1999 13:08:22
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (hsmpka.Eng.Sun.COM [129.146.55.47]) by
          engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          NAA09091; Fri, 6 Aug 1999 13:08:20 -0700 (PDT)
Received: from finesse by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id NAA18856;
          Fri, 6 Aug 1999 13:08:10 -0700
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 2B1MaqR6BV5t58V2Pm7/tQ==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc
Message-ID:  <199908062008.NAA18856@hsmpka.eng.sun.com>
Date:         Fri, 6 Aug 1999 13:08:27 -0700
Reply-To: Charles Perkins <Charles.Perkins@eng.sun.com>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Charles Perkins <Charles.Perkins@eng.sun.com>
Subject:      Re: [MOBILE-IP] Drafts Cleanup
X-To:         bpatil@NORTELNETWORKS.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hello Raj,

> Drafts that will be removed from the Mobile IP page:
> ----------------------------------------------------

> - Mobile IP Regionalized Tunnel Management
>   (draft-ietf-mobileip-reg-tunnel-00.txt)

I don't mind resubmitting this as a personal draft, but
I would like to ask that it remain on the working group
page.  There are quite a few people within the working
group interested in such an approach, as was indicated
at the last meeting in Oslo.

> - AAA Registration Keys for Mobile IP
>   (draft-ietf-mobileip-aaa-key-00.txt) - explain

This is a way for the AAA to encode registration keys for
the mobile node and mobility agents.  Doing this is crucial
for operation of route optimization with AAA, and for smooth
handoff, and for allowing intermediate Mobile IP registration
messages to be validated at the foreign agent without having
to invoke the AAA infrastructure at each registration.

> - Private Addresses in Mobile IP (draft-ietf-mobileip-privaddr-00.txt)
>   Although this topic is in the charter, we are having a discussion on
>   the mailing list at this time on the approach the WG wants to
>   take. Hence this draft may be reconsidered at a later time.

It still deserves to be made available, however.  And, I think
that the page won't be so crowded once the expired, dead, and
inactive drafts disappear.

Would you prefer that this draft become an individual submission?

Regards,
Charlie P.


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug  6 16:44:41 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23710
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 6 Aug 1999 16:44:41 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.8B350AB0@standards.nortelnetworks.com>; Fri, 6 Aug 1999 16:41:34 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 33526 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 6 Aug 1999 16:40:24 -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.61C12A10@standards.nortelnetworks.com>; Fri, 6 Aug 1999
          16:40:24 -0400
Received: from zrchh190 by smtprch1.nortel.com; Fri, 6 Aug 1999 15:31:44 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Fri, 6
          Aug 1999 15:43:04 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QKP6YVFB>; Fri, 6 Aug 1999 15:39:07 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-Orig: <bpatil@americasm01.nt.com>
X-Orig: <bpatil@americasm01.nt.com>
Message-ID:  <61DEB565F616D31187880000F805A8D5817E42@crchy270.us.nortel.com>
Date:         Fri, 6 Aug 1999 15:38:59 -0500
Reply-To: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Subject:      Re: [MOBILE-IP] Drafts Cleanup
X-To:         Charles Perkins <Charles.Perkins@eng.sun.com>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi Charles,

My comments below:

>
>Hello Raj,
>
>> Drafts that will be removed from the Mobile IP page:
>> ----------------------------------------------------
>
>> - Mobile IP Regionalized Tunnel Management
>>   (draft-ietf-mobileip-reg-tunnel-00.txt)
>
>I don't mind resubmitting this as a personal draft, but
>I would like to ask that it remain on the working group
>page.  There are quite a few people within the working
>group interested in such an approach, as was indicated
>at the last meeting in Oslo.

It would help if you could resubmit it as a personal draft. Since a
lot of other drafts are using this as a reference and has spawned many
new ideas we can keep it on the page.

>
>> - AAA Registration Keys for Mobile IP
>>   (draft-ietf-mobileip-aaa-key-00.txt) - explain
>
>This is a way for the AAA to encode registration keys for
>the mobile node and mobility agents.  Doing this is crucial
>for operation of route optimization with AAA, and for smooth
>handoff, and for allowing intermediate Mobile IP registration
>messages to be validated at the foreign agent without having
>to invoke the AAA infrastructure at each registration.

Since we have agreed to just define the requirements that Mobile IP
needs from AAA at the last IETF, this draft does not at this point in
time fit in the scope of the charter and WG emphasis which is
deployment. We can always pick it up if there is sufficient interest
and reason to do so and make it a WG document. I just do not feel that
it is within the scope at the present.

>
>> - Private Addresses in Mobile IP (draft-ietf-mobileip-privaddr-00.txt)
>>   Although this topic is in the charter, we are having a discussion on
>>   the mailing list at this time on the approach the WG wants to
>>   take. Hence this draft may be reconsidered at a later time.
>
>It still deserves to be made available, however.  And, I think
>that the page won't be so crowded once the expired, dead, and
>inactive drafts disappear.
>
>Would you prefer that this draft become an individual submission?

There is at least one other draft (draft-teoyli-mobileip-mvpn-02.txt)
that addresses the same problem and there probably will be more in the
future. We need to decide what is the best/optimum solution that the
WG wants to pursue and choose to work on that draft. We could then
decide to make that ID a WG document. But until that happens it would be
preferable to keep the I-Ds as personal submissions aimed at the
Mobile IP WG.

>
>Regards,
>Charlie P.
>

Cheers,
-Raj


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug  9 05:07:37 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00251
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 9 Aug 1999 05:07:36 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.93708F00@standards.nortelnetworks.com>; Mon, 9 Aug 1999 5:03:53 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 34233 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 9 Aug 1999 05:02:38 -0400
Received: from p-biset.issy.cnet.fr (139.100.0.33) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.66775830@standards.nortelnetworks.com>; Mon, 9 Aug 1999 5:02:37
          -0400
Received: by p-biset.issy.cnet.fr with Internet Mail Service (5.5.2232.9) id
          <QH4MKRMH>; Mon, 9 Aug 1999 11:05:15 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain
Message-ID:  <F09BA6AD2FB2D211BFAC00805F312C894851FB@p-heron.issy.cnet.fr>
Date:         Mon, 9 Aug 1999 11:05:15 +0200
Reply-To: COELHO-ALVES Emmanuel CNET/DMR/ISS
              <emmanuel.coelhoalves@CNET.FRANCETELECOM.FR>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: COELHO-ALVES Emmanuel CNET/DMR/ISS
              <emmanuel.coelhoalves@CNET.FRANCETELECOM.FR>
Subject:      [MOBILE-IP] handover drafts
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi,

In June 99, there had many drafts concerning handovers which have been
introduced in the WG MIP.
I would like to understand the correct meaning of "BS" which has been
mentioned in those drafts. Does BS correspond to the definition we have in
GSM (BS = BTS) or UMTS (BS = Node B) ? Is it different ? In the last case
what are the differences ?

Thanks in advance
Emmanuel Coelho Alves


Emmanuel COELHO ALVES
Research Engineer
Third Generation Mobile Systems and Services
FRANCE TELECOM LABORATORY

Tel : +33 1 45 29 44 97
Fax : +33 1 45 29 43 99
Email : emmanuel.coelhoalves@cnet.francetelecom.fr


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug  9 10:51:06 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08824
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 9 Aug 1999 10:51:06 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.90460230@standards.nortelnetworks.com>; Mon, 9 Aug 1999 10:47:23 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 34519 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 9 Aug 1999 10:45:59 -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.5DD08730@standards.nortelnetworks.com>; Mon, 9 Aug 1999
          10:45:59 -0400
Received: from zrchh190 by smtprch1.nortel.com; Mon, 9 Aug 1999 09:39:50 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Mon, 9
          Aug 1999 09:51:08 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QN19B2LN>; Mon, 9 Aug 1999 09:46:54 -0500
X-Mailer: Internet Mail Service (5.5.2448.0)
X-Orig: <rccoffin@americasm01.nt.com>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
X-Orig: <rccoffin@americasm01.nt.com>
Message-ID:  <417CF9E6B325D3119DA90000F81FAE16610F8F@zrchb201.us.nortel.com>
Date:         Mon, 9 Aug 1999 09:46:44 -0500
Reply-To: Russ Coffin <rccoffin@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Russ Coffin <rccoffin@NORTELNETWORKS.COM>
Subject:      Re: [MOBILE-IP] Mobile-IP DIAMETER Extension - New rev
X-To:         Pat.Calhoun@ENG.SUN.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Pat - I am impressed by the amount of testing, fixing, and re-protocoling
was done at the bakeoff - I think all participants should be thanked and
congratulated. I believe that the bakeoff results will be key in the
deployment ramp of IP Mobility.



Cheers - Russ


-----Original Message-----
From: Pat.Calhoun@ENG.SUN.COM [mailto:Pat.Calhoun@ENG.SUN.COM]
Sent: Thursday, August 05, 1999 04:16 PM
To: mobile-ip@standards.nortelnetworks.com
Subject: [MOBILE-IP] Mobile-IP DIAMETER Extension - New rev


First, I want to appologize for the cross-post, but it seemed like a good
idea.

I have just finished cleaning up the Mobile-IP Extension draft, and it is
now
available at www.diameter.org. I would like to appologize for the poor state
that the web page is in, but I really have not had time to clean it up very
much (hey, it's only been a day).

Most of the fixes in the draft were related to issues and clarifications
needed as a result of the bake-off. However, there are a few that are a
result of minor changes to the base protocol, which is also available on the
web site.

I would like to get initial feedback before I send it out to the
secretariat.

I am including a list of the changes made to the spec below.

PatC

1.2  Changes in version -03

   The following are the changes done to version 03 of the draft:

      - Cleaned up the AVP Header flags

      - The Command Code sections now show an optional Proxy-State AVP
      as part of the message format.

      - The previous version required that the MIP-Registration-Reply be
      present in the AMA, but the AVP could not be present if the AAAH
      could not service the request. The AVP is now only mandatory if
      the AMA is successful.

      - Cleaned up the description of the various key and SPI AVPs.

      - Added text in section 4.1 that describes how the AAAH can cache
      the keys directed for the AAAF so they can be included in the
      message when the response is received by the HA. This was the
      point that cause interoperability at the bake-off due to the fact
      that it was quite unclear.

      - Section 4.1 now correctly states that the Home-Address AVP MUST
      be present and MAY have a value of 0.0.0.0.

      - Section 4.1 now also states that the Mobile-IP FA-HA and the MN-
      HA authentication extensions must be used.

      - Added a reference to ESP

      - Added IANA Considerations


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug  9 11:59:25 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10050
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 9 Aug 1999 11:59:25 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.15903C90@standards.nortelnetworks.com>; Mon, 9 Aug 1999 11:55:32 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 34610 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 9 Aug 1999 11:55:07 -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.06396320@standards.nortelnetworks.com>; Mon, 9 Aug 1999
          11:55:07 -0400
Received: from zrchh190 by smtprch1.nortel.com; Mon, 9 Aug 1999 10:45:30 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Mon, 9
          Aug 1999 10:57:01 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QN19BTKN>; Mon, 9 Aug 1999 10:52:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-Orig: <bpatil@americasm01.nt.com>
X-Orig: <bpatil@americasm01.nt.com>
Message-ID:  <61DEB565F616D31187880000F805A8D5817E4E@crchy270.us.nortel.com>
Date:         Mon, 9 Aug 1999 10:52:42 -0500
Reply-To: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Subject:      Re: [MOBILE-IP] handover drafts
X-To:         COELHO-ALVES Emmanuel CNET/DMR/ISS
              <emmanuel.coelhoalves@CNET.FRANCETELECOM.FR>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

>
>Hi,
>
>In June 99, there had many drafts concerning handovers which have been
>introduced in the WG MIP.
>I would like to understand the correct meaning of "BS" which has been
>mentioned in those drafts. Does BS correspond to the definition we have in
>GSM (BS = BTS) or UMTS (BS = Node B) ? Is it different ? In the last case
>what are the differences ?

My interpretation of the "BS", in the drafts that were discussed at
IETF45, refers to the "BTS" (BS = BTS).

-Basavaraj

>
>Thanks in advance
>Emmanuel Coelho Alves
>
>
>Emmanuel COELHO ALVES
>Research Engineer
>Third Generation Mobile Systems and Services
>FRANCE TELECOM LABORATORY
>
>Tel : +33 1 45 29 44 97
>Fax : +33 1 45 29 43 99
>Email : emmanuel.coelhoalves@cnet.francetelecom.fr


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug  9 12:02:56 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10197
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 9 Aug 1999 12:02:55 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.5E40C9A0@standards.nortelnetworks.com>; Mon, 9 Aug 1999 11:57:34 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 34588 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 9 Aug 1999 11:57:31 -0400
Received: from mailhub2.shef.ac.uk by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.F6558160@standards.nortelnetworks.com>; Mon, 9 Aug 1999 11:47:31
          -0400
Received: from stoat.shef.ac.uk ([143.167.2.1]) by mailhub2 with smtp (Exim
          3.02 #2) id 11Comy-0006Rf-00; Fri, 06 Aug 1999 19:32:20 +0100
Received: from acq95ke by stoat.shef.ac.uk with smtp (Exim 1.82 #2) id
          11Comx-0001Sm-00; Fri, 6 Aug 1999 19:32:19 +0100
X-Sender: acq95ke@stoat
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-ID:  <Pine.GSO.3.93.990806191810.2237F-100000@stoat>
Date:         Fri, 6 Aug 1999 19:32:19 +0100
Reply-To: K Malki <K.ElMalki@SHEFFIELD.AC.UK>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: K Malki <K.ElMalki@SHEFFIELD.AC.UK>
Subject:      Re: [MOBILE-IP] CDMA misinterpreted and
X-To:         "Casati, Alessio (Alessio)" <acasati@LUCENT.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <976F7C55E3B2D111A0720008C728549C020A46C4@en0060exch001u.uk.lucent.com>

Hi Alessio

I actually have not "misinterpreted" CDMA, but rather you clearly have
your interpretation :)

> By the way, if the target application of this is to do something applicable
> to
> CDMA access networks, CDMA access networks for cellular systems are
> already mostly defined and do a good job at handling micromobility.

They don't do a good job if the operator decides to split the network
into subnets within the same administrative domain. That's the point
behind the draft.

If the operator decides to have flat adressing and micromobility (layer2)
then MIP's importance is largely reduced. However, personally I feel
this is a limitation which operators may not want, therefore fast
handoffs would be useful in supporting inelastic IP-telephony-like apps
in CDMA networks.

Cheers
Karim


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug  9 12:52:04 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10789
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 9 Aug 1999 12:52:04 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.82C64A00@standards.nortelnetworks.com>; Mon, 9 Aug 1999 12:48:42 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 34728 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 9 Aug 1999 12:47:50 -0400
Received: from crufty.research.bell-labs.com by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.63639F00@standards.nortelnetworks.com>; Mon, 9 Aug 1999 12:47:50
          -0400
Received: from scummy.research.bell-labs.com ([135.104.2.10]) by crufty; Mon
          Aug  9 12:48:08 EDT 1999
Received: from king.research.bell-labs.com ([135.1.152.1]) by scummy; Mon Aug 
          9 12:48:39 EDT 1999
Received: from notmafia.research.bell-labs.com.research.bell-labs.com (notmafia
          [135.1.152.230]) by king.research.bell-labs.com (Postfix) with SMTP
          id B74A957013; Mon,  9 Aug 1999 11:48:39 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <976F7C55E3B2D111A0720008C728549C020A46C4@en0060exch001u.uk.lucent.com>
            <Pine.GSO.3.93.990806191810.2237F-100000@stoat>
X-Mailer: VM 6.33 under Emacs 19.34.2
Message-ID:  <19990809164839.B74A957013@king.research.bell-labs.com>
Date:         Mon, 9 Aug 1999 11:48:39 -0500
Reply-To: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Subject:      Re: [MOBILE-IP] CDMA misinterpreted and
X-To:         K Malki <K.ElMalki@SHEFFIELD.AC.UK>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <Pine.GSO.3.93.990806191810.2237F-100000@stoat>
Content-Transfer-Encoding: 7bit

Karim,

I think you may still have some misunderstanding about the way CDMA
networks are architected.  This is related to my question about "frame
selectors" right after your talk: this is a more-or-less centralized
location in a CDMA network where signals from multiple base stations
are received and the best one is "selected", as the name implies.

The point Alessio was trying to make is that even though CDMA
technology is apparently multipoint, because multiple base stations
receive the transmission simultaneously, these transmissions are
actually grouped into a single stream back at the frame selector.
This is also the first point at which IP packets can be formed up from
the data stream and is the logical place to put a Mobile IP foreign
agent (or in any case, it can't be done any closer to the base
stations than this).  So, if you want to have true multi-point
connectivity, that is, you want to have two points of IP connectivity,
you need to actually replicate a lot of hardware so that you can talk
on two different CDMA spreading codes at once.  This is typically not
done in the CDMA transmitters of today, and, although it may be a
possibility in the future, my understanding is that this is not really
being planned for (someone please correct me if I'm mistaken).

There may actually be solutions that allow you to talk to two
different frame selectors without replicating the transmission
hardware, but these still need a lot of work before they can become
reality.  In the meantime, we have a pretty good "micromobility"
solution in the CDMA access network itself, especially if it supports
"soft handoff" features.  Granted, there will be cases of handoff
between foreign agents, and these should be handled as quickly as
possible, but I think this will happen somewhat less often than you
indicate and certainly less often than at every base station.

When trying to build a data-over-cellular network, it's important to
keep in mind that traditional voice is still the most important
service and will likely be that way for some time to come.  Therefore,
you should try to piggyback the service as much as possible on the
existing voice infrastructure, which has already solved many of these
problems in a cost-effective way.  The more changes or additions to
the infrastructure you require, and the closer these changes/additions
are to the "fringes" of the network (base stations), the more
expensive and harder to deploy it will be.  This is a lesson that
should have been learned from CDPD.

-Pete


K Malki <K.ElMalki@SHEFFIELD.AC.UK> (KM) writes:

KM> Hi Alessio
KM> I actually have not "misinterpreted" CDMA, but rather you clearly have
KM> your interpretation :)

>> By the way, if the target application of this is to do something applicable
>> to
>> CDMA access networks, CDMA access networks for cellular systems are
>> already mostly defined and do a good job at handling micromobility.

KM> They don't do a good job if the operator decides to split the network
KM> into subnets within the same administrative domain. That's the point
KM> behind the draft.

KM> If the operator decides to have flat adressing and micromobility (layer2)
KM> then MIP's importance is largely reduced. However, personally I feel
KM> this is a limitation which operators may not want, therefore fast
KM> handoffs would be useful in supporting inelastic IP-telephony-like apps
KM> in CDMA networks.

KM> Cheers
KM> Karim


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug  9 13:39:35 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11291
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 9 Aug 1999 13:39:35 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.15604A90@standards.nortelnetworks.com>; Mon, 9 Aug 1999 13:35:45 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 34762 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 9 Aug 1999 13:33:53 -0400
Received: from dumburken.it.kth.se by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.D23A5990@standards.nortelnetworks.com>; Mon, 9 Aug 1999 13:33:52
          -0400
Received: (from maguire@localhost) by dumburken.it.kth.se (8.9.3/8.9.3) id
          TAA18454; Mon, 9 Aug 1999 19:36:32 +0200 (MET DST)
References: <976F7C55E3B2D111A0720008C728549C020A46C4@en0060exch001u.uk.lucent.com>
            <Pine.GSO.3.93.990806191810.2237F-100000@stoat>
            <19990809164839.B74A957013@king.research.bell-labs.com>
Message-ID:  <199908091736.TAA18454@dumburken.it.kth.se>
Date:         Mon, 9 Aug 1999 19:36:32 +0200
Reply-To: Gerald Maguire <maguire@IT.KTH.SE>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gerald Maguire <maguire@IT.KTH.SE>
Subject:      Re: [MOBILE-IP] CDMA misinterpreted and
X-To:         mccap@RESEARCH.BELL-LABS.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <19990809164839.B74A957013@king.research.bell-labs.com> (message
              from Pete McCann on Mon, 9 Aug 1999 11:48:39 -0500)

Pete McCann <mccap@RESEARCH.BELL-LABS.COM> stated:

    ... So, if you want to have true multi-point
    connectivity, that is, you want to have two points of IP connectivity,
    you need to actually replicate a lot of hardware so that you can talk
    on two different CDMA spreading codes at once.  This is typically not
    done in the CDMA transmitters of today, and, although it may be a
    possibility in the future, my understanding is that this is not really
    being planned for (someone please correct me if I'm mistaken).

Assuming that the CDMA system is using a single frequency for these
two channels (i.e., that it is only a code difference betwen the two)
then the is very little that needs to be replicated to _receive_ two
different channels of CDMA - since the RF section can be shared, all
you need to have is an extra correlator (or three - depending on if
the user is moving or not) for the additional spreading code. Thus the
cost of receiving on multiple codes is low and you can easily go from
chips to bits in the basestations. If these are IP packets in some
sort of link frame, then you could immediately put these frames into a
routed IP infrastructure right from the base station.

The transmission problem is more complex if you are going to do
accurate power control - since the different chip streams may have to
have different power levels when transmitted. However, in the case
where the power can be identical (for example indoors over short
distances) - then there is no problem simply combining (or-ing) the
chip streams and then feeding them into the same RF section {since
after all it is the codes which separate the streams not their
freq. etc.}. [Note that in this case I have assummed that you are
generating the chips for the different streams synchronously - which
just makes things simpler.] Once again there is no reason not to do
this as close to the basestation as possible - since it conserves
bandwidth on the typically wired link to put off the bit to chip
conversion until as late as possible.

Unlike the voice case there is no problem (other than the transport of
duplicate packets) with each of the basestations which can receive a
mobile sending on the IP traffic that it receives. These extra copies
can be eliminated by administratively deciding which basestations(s)
will be forwarding traffic coming from a given mobile. There are
clearly cases (such as when the mobile is on the fringe of two cells)
when it may be quite reasonable for several basestations to be
forwarding traffic to or from a given mobile.

Pete further states:
    When trying to build a data-over-cellular network, it's important to
    keep in mind that traditional voice is still the most important
    service and will likely be that way for some time to come.  Therefore,
    you should try to piggyback the service as much as possible on the
    existing voice infrastructure, which has already solved many of these
    problems in a cost-effective way.  The more changes or additions to
    the infrastructure you require, and the closer these changes/additions
    are to the "fringes" of the network (base stations), the more
    expensive and harder to deploy it will be.  This is a lesson that
    should have been learned from CDPD.

There is an important distinction of if this data-over-cellular
network is being built by an incumbant who is already operating an
voice oriented cellular system or not. In the case where there is no
existing voice oriented cellular system - there is no need to use the
typical voice oriented infrastructure and you can build an IP oriented
infrastructure from the start. Clearly if you have an existing voice
oriented cellular infrastructure you want to preserve its value for as
long as possible - therefore you are more likely to take an incremental
approach rather than forklift replace it. However, I don't see that a
voice oriented infrastructure is inherently more cost-effective in the
wireless setting (just as it is not in the wired setting).

For example, consider an operator who does not have an existing GSM
infrastructure but decides to go into the GPRS business. Is there any
reason why they should build a circuit switched infrastructure? By
utilizing VOIP from the handset to the remote end - you can
potentially remove 60% of the processing required since you don't have
to transcode voice packets to a mu-law or A-law stream into/out of a B
channel. Of course if you do have to go through a voice gateway at the
national gateway or where you interconnection to other operators you
will have to do the transcoding, but thanks to the digital modems used
to create dialin modem pools (such as in the Ascend Max) you can do
this with very high density devices (i.e., 2-4 E1 connections per 10cm
of rack space).

From a practical point of view there is evidence that putting all of
the processing in the center (i.e., not distributing it) is not always
the preferred solution - otherwise _everyone_ would use Ericsson's
AXEs to make their infrastructures (which they don't).  Even though
this was the case at the start of many cellular voice networks it is
not the case today.

Regards,
G. Q. "Chip" Maguire Jr.


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug  9 13:39:36 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11293
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 9 Aug 1999 13:39:36 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.15867030@standards.nortelnetworks.com>; Mon, 9 Aug 1999 13:35:45 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 34761 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 9 Aug 1999 13:34:22 -0400
Received: from pdp (140.113.215.140) by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.7D53B080@standards.nortelnetworks.com>; Mon, 9 Aug 1999 13:24:21
          -0400
Received: from pdp3.csie.nctu.edu.tw (pdp3.csie.nctu.edu.tw [140.113.215.133])
          by pdp (8.8.7/8.8.5) with SMTP id BAA23628; Tue, 10 Aug 1999 01:28:12
          +0800 (CST)
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-ID:  <199908091728.BAA23628@pdp>
Date:         Tue, 10 Aug 1999 00:57:46 +0800
Reply-To: Kuang-Hwei Chi <khchi@PDP.NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Kuang-Hwei Chi <khchi@PDP.NORTELNETWORKS.COM>
Subject:      Re: [MOBILE-IP] mip and multicast
X-To:         floroiu@FOKUS.GMD.DE
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <378B5540.AB35B6EB@fokus.gmd.de> from John Williams Floroiu at
              "Jul 13, 99 05:03:28 pm"
Content-Transfer-Encoding: 7bit

Hello John

The following are my personal points of view in response to
your post. I'll be very glad to receive any comments on
this subject from you as well as the mailing list.

Best Regards

Chi

John Williams Floroiu wrote:
>
>Hi All,
>
>1. Concerning the scenario in which the MN acts as a multicast client in
>the HNet (option (2) in paragraph 4.4 of RFC2002), it is written in
>several places in RFC2002 that HA should be a multicast router. My
>question is why would be that necessary, since the HA can just tunnel
>mcast datagrams to the roaming MNs, and inject in the HNet those mcast
>datagrams arriving from the roaming MNs via the reverse tunnels.
>
        As you have noticed, HA can tunnel multicast datagrams to
        the MNs that are away from home.
        This means that HA must be multicast capable, with the
        ability of recognizing packets meant for a group.
        On the other hand, the HA can deliver multicast datagrams
        toward the intended group members for these MNs.
        In practice, the delivery of multicast datagrams relies on
        a pre-setup of multicast forwarding paths.
        The establishment of such paths is an essential task of
        multicast routers, requiring coordinations among these
        routers.
        In other words, there need be a multicast delivery path
        originated from the HNet to the group members.
        The home agent, as a multicast router, will suffice to
        meet this need.

>2. Since a node which will shortly leave HNet may not send an IGMP Join
>message (if it is not the first node in HNet interested in joining a
>given group), the HA will need to tunnel all mcast datagrams to all
>roaming MNs interested in receiving mcast. (Since these datagrams arrive
>at the MNs via a tunnel, they will be no any longer filtered by the MNs'
>network cards, so the filtering will need to take place at IP layer).
>This adds an important overhead to the HA, so that maybe some extensions
>to the RegReq messages will be usefull in order to tell HA which
>specific groups is a certain MN interested in. In this way the HA will
>be able to reduce this overhead by playing a role in the mcast
>delivering mechanisms (i.e. HA will manage logical mcast branches to the
>roaming MNs).
>
        My understanding is a bit different.
        If an MN that is away from home would like to receive
        multicasts via its home agent, the MN should first send
        its IGMP join message to the home agent (paragraph 3 in
        Section 4.4 of RFC 2002.)
        Thus the home agent can be informed of which group is
        interested by the MN and only tunnels the interested
        multicasts to the MN.

>
>I am looking forward to hearing your comments,
>John.

There are some references related to this issue.
Hope they are useful to you.

- Chikarmane, V. et al. (1995)
        Mobile IP-based multicast as a service for mobile hosts,
        Proc. 2nd IEEE Int'l Wksp. Services in
        Distributed and Network Environments, 11-18.
- Chikarmane, V. et al. (1999)
        Multicast support for mobile hosts using mobile IP:
        design issues and proposed architecture,
        ACM/Baltzer Mobile Networking and
        Applications, Vol.3, 365-379.
- Harrison, T.G. et al. (1997)
        Mobile multicast (MoM) protocol: multicast support
        for mobile hosts,
        Proc. 3rd Annual ACM/IEEE Conf. Mobile Comp.
        and Networks, 151-160.

--
Kuang-Hwei Chi, Institute of Computer Science & Information Engineering
National Chiaotung University, Hsinchu, Taiwan    Phone: +886-3-5731892
Email: chikh@csie.nctu.edu.tw   WWW: http://www.csie.nctu.edu.tw/~chikh


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug  9 13:55:08 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11410
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 9 Aug 1999 13:55:08 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.544CECC0@standards.nortelnetworks.com>; Mon, 9 Aug 1999 13:51:50 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 34812 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 9 Aug 1999 13:50:24 -0400
Received: from ccsun5.csie.nctu.edu.tw by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.BA8E35E0@standards.nortelnetworks.com>; Mon, 9 Aug 1999 13:40:22
          -0400
Received: (from chikh@localhost) by ccsun5.csie.nctu.edu.tw (8.9.3/8.9.0) id
          BAA02270; Tue, 10 Aug 1999 01:42:52 +0800 (CST)
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-ID:  <199908091742.BAA02270@ccsun5.csie.nctu.edu.tw>
Date:         Tue, 10 Aug 1999 01:42:51 +0800
Reply-To: khchi@pdp.csie.nctu.edu.tw
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Kuang-Hwei Chi <chikh@CSIE.NCTU.EDU.TW>
Subject:      Re: [MOBILE-IP] mip and multicast
X-To:         floroiu@FOKUS.GMD.DE
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <378B5540.AB35B6EB@fokus.gmd.de> from John Williams Floroiu at
              "Jul 13, 99 05:03:28 pm"
Content-Transfer-Encoding: 7bit

Hello John

The following are my personal points of view in response to
your post. I'll be very grateful to receive any comments on
this subject from the mailing list.

Best Regards

Chi

John Williams Floroiu wrote:
>
>Hi All,
>
>1. Concerning the scenario in which the MN acts as a multicast client in
>the HNet (option (2) in paragraph 4.4 of RFC2002), it is written in
>several places in RFC2002 that HA should be a multicast router. My
>question is why would be that necessary, since the HA can just tunnel
>mcast datagrams to the roaming MNs, and inject in the HNet those mcast
>datagrams arriving from the roaming MNs via the reverse tunnels.
>
        As you have noticed, HA can tunnel multicast datagrams to
        the MNs that are away from home.
        This means that HA must be multicast capable, with the
        ability of recognizing packets meant for a group.
        On the other hand, the HA can deliver multicast datagrams
        toward the intended group members for these MNs.
        In practice, the delivery of multicast datagrams relies on
        a pre-setup of multicast forwarding paths.
        The establishment of such paths is an essential task of
        multicast routers, requiring coordinations among these
        routers.
        In other words, there need be a multicast delivery path
        originated from the HNet to the group members.
        The home agent, as a multicast router, will suffice to
        meet this need.

>2. Since a node which will shortly leave HNet may not send an IGMP Join
>message (if it is not the first node in HNet interested in joining a
>given group), the HA will need to tunnel all mcast datagrams to all
>roaming MNs interested in receiving mcast. (Since these datagrams arrive
>at the MNs via a tunnel, they will be no any longer filtered by the MNs'
>network cards, so the filtering will need to take place at IP layer).
>This adds an important overhead to the HA, so that maybe some extensions
>to the RegReq messages will be usefull in order to tell HA which
>specific groups is a certain MN interested in. In this way the HA will
>be able to reduce this overhead by playing a role in the mcast
>delivering mechanisms (i.e. HA will manage logical mcast branches to the
>roaming MNs).
>
        My understanding is a bit different.
        If an MN that is away from home would like to receive
        multicasts via its home agent, the MN should first send
        its IGMP join message to the home agent (paragraph 3 in
        Section 4.4 of RFC 2002.)
        Thus the home agent can be informed of which group is
        interested by the MN and only tunnels the interested
        multicasts to the MN.

>
>I am looking forward to hearing your comments,
>John.

There are some references related to this issue.
Hope they are useful to you.

- Chikarmane, V. et al. (1995)
        Mobile IP-based multicast as a service for mobile hosts,
        Proc. 2nd IEEE Int'l Wksp. Services in
        Distributed and Network Environments, 11-18.
- Chikarmane, V. et al. (1999)
        Multicast support for mobile hosts using mobile IP:
        design issues and proposed architecture,
        ACM/Baltzer Mobile Networking and
        Applications, Vol.3, 365-379.
- Harrison, T.G. et al. (1997)
        Mobile multicast (MoM) protocol: multicast support
        for mobile hosts,
        Proc. 3rd Annual ACM/IEEE Conf. Mobile Comp.
        and Networks, 151-160.

--
Kuang-Hwei Chi, Institute of Computer Science & Information Engineering
National Chiaotung University, Hsinchu, Taiwan    Phone: +886-3-5731892
Email: chikh@csie.nctu.edu.tw   WWW: http://www.csie.nctu.edu.tw/~chikh


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 10 03:04:52 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03877
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 10 Aug 1999 03:04:52 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.905318C0@standards.nortelnetworks.com>; Tue, 10 Aug 1999 3:00:55 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 35558 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 10 Aug 1999 02:59:05
          -0400
Received: from motgate2.mot.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.E8CE3A90@standards.nortelnetworks.com>; Tue, 10 Aug 1999 2:49:04
          -0400
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by
          motgate2.mot.com (MOT-motgate2 1.0) with ESMTP id BAA28958 for
          <mobile-ip@standards.nortelnetworks.com>; Tue, 10 Aug 1999 01:52:36
          -0500 (CDT)]
Received: [from hpux4.miel.mot.com (hpux4.miel.mot.com [217.1.84.89]) by
          mothost.mot.com (MOT-mothost 2.0) with SMTP id BAA04893 for
          <mobile-ip@standards.nortelnetworks.com>; Tue, 10 Aug 1999 01:51:46
          -0500 (CDT)]
Received: from miel.mot.com (pc84156.miel.mot.com) by hpux4.miel.mot.com with
          SMTP id AA20427 (5.67b/IDA-1.6 for
          mobile-ip@standards.nortelnetworks.com); Tue, 10 Aug 1999 12:13:43
          +0500
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID:  <37B0441A.7043066B@miel.mot.com>
Date:         Tue, 10 Aug 1999 12:24:10 -0300
Reply-To: GeeVarghese John <gvjohn@MIEL.MOT.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: GeeVarghese John <gvjohn@MIEL.MOT.COM>
Organization: Motorola India Electronics Ltd.
Subject:      [MOBILE-IP] subscribe
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

-subscribe mobile-ip Geevarghese John


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 10 11:31:04 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18864
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 10 Aug 1999 11:31:03 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.D31B2F80@standards.nortelnetworks.com>; Tue, 10 Aug 1999 11:23:52 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 36150 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 10 Aug 1999 11:22:09
          -0400
Received: from gw3.sprintspectrum.com by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.95C4F9E0@standards.nortelnetworks.com>; Tue, 10 Aug 1999 11:22:09
          -0400
Received: by gw3.sprintspectrum.com; id KAA20691; Tue, 10 Aug 1999 10:24:55
          -0500 (CDT)
Received: from unknown(208.10.75.11) by gw3.sprintspectrum.com via smap (V2.0)
          id xma019909; Tue, 10 Aug 99 10:23:50 -0500
Received: by uskmessoa001.sprintspectrum.com with Internet Mail Service
          (5.5.2448.0) id <QS4Y2JT0>; Tue, 10 Aug 1999 10:23:39 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <ABA3B5AA1991D21195940060970EB0E3C2AC79@uskmessoa021.sprintspectrum.com>
Date:         Tue, 10 Aug 1999 10:23:28 -0500
Reply-To: "Lipford, Mark" <MLipfo01@SPRINTSPECTRUM.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "Lipford, Mark" <MLipfo01@SPRINTSPECTRUM.COM>
Subject:      Re: [MOBILE-IP] CDMA misinterpreted and
X-To:         Gerald Maguire <maguire@IT.KTH.SE>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

I haven't been following this closely, but if I understand the concept
correctly you are discussing have multiple IP connections over the RF link.
Why would you want to do that when the problem with wireless data is limited
RF resources?  Now you are suggesting using two times (or more) the RF
resources required.  As a CDMA carrier we are fighting to reduce the traffic
over the RF to allow for more subscribers, not the opposite.

Tell me if I'm missing something here.

                -----Original Message-----
                From:   Gerald Maguire [mailto:maguire@IT.KTH.SE]
                Sent:   Monday, August 09, 1999 12:37 PM
                To:     MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
                Subject:        Re: [MOBILE-IP] CDMA misinterpreted and

                Pete McCann <mccap@RESEARCH.BELL-LABS.COM> stated:

                    ... So, if you want to have true multi-point
                    connectivity, that is, you want to have two points of IP
connectivity,
                    you need to actually replicate a lot of hardware so that
you can talk
                    on two different CDMA spreading codes at once.  This is
typically not
                    done in the CDMA transmitters of today, and, although it
may be a
                    possibility in the future, my understanding is that this
is not really
                    being planned for (someone please correct me if I'm
mistaken).

                Assuming that the CDMA system is using a single frequency
for these
                two channels (i.e., that it is only a code difference betwen
the two)
                then the is very little that needs to be replicated to
_receive_ two
                different channels of CDMA - since the RF section can be
shared, all
                you need to have is an extra correlator (or three -
depending on if
                the user is moving or not) for the additional spreading
code. Thus the
                cost of receiving on multiple codes is low and you can
easily go from
                chips to bits in the basestations. If these are IP packets
in some
                sort of link frame, then you could immediately put these
frames into a
                routed IP infrastructure right from the base station.

                The transmission problem is more complex if you are going to
do
                accurate power control - since the different chip streams
may have to
                have different power levels when transmitted. However, in
the case
                where the power can be identical (for example indoors over
short
                distances) - then there is no problem simply combining
(or-ing) the
                chip streams and then feeding them into the same RF section
{since
                after all it is the codes which separate the streams not
their
                freq. etc.}. [Note that in this case I have assummed that
you are
                generating the chips for the different streams synchronously
- which
                just makes things simpler.] Once again there is no reason
not to do
                this as close to the basestation as possible - since it
conserves
                bandwidth on the typically wired link to put off the bit to
chip
                conversion until as late as possible.

                Unlike the voice case there is no problem (other than the
transport of
                duplicate packets) with each of the basestations which can
receive a
                mobile sending on the IP traffic that it receives. These
extra copies
                can be eliminated by administratively deciding which
basestations(s)
                will be forwarding traffic coming from a given mobile. There
are
                clearly cases (such as when the mobile is on the fringe of
two cells)
                when it may be quite reasonable for several basestations to
be
                forwarding traffic to or from a given mobile.

                Pete further states:
                    When trying to build a data-over-cellular network, it's
important to
                    keep in mind that traditional voice is still the most
important
                    service and will likely be that way for some time to
come.  Therefore,
                    you should try to piggyback the service as much as
possible on the
                    existing voice infrastructure, which has already solved
many of these
                    problems in a cost-effective way.  The more changes or
additions to
                    the infrastructure you require, and the closer these
changes/additions
                    are to the "fringes" of the network (base stations), the
more
                    expensive and harder to deploy it will be.  This is a
lesson that
                    should have been learned from CDPD.

                There is an important distinction of if this
data-over-cellular
                network is being built by an incumbant who is already
operating an
                voice oriented cellular system or not. In the case where
there is no
                existing voice oriented cellular system - there is no need
to use the
                typical voice oriented infrastructure and you can build an
IP oriented
                infrastructure from the start. Clearly if you have an
existing voice
                oriented cellular infrastructure you want to preserve its
value for as
                long as possible - therefore you are more likely to take an
incremental
                approach rather than forklift replace it. However, I don't
see that a
                voice oriented infrastructure is inherently more
cost-effective in the
                wireless setting (just as it is not in the wired setting).

                For example, consider an operator who does not have an
existing GSM
                infrastructure but decides to go into the GPRS business. Is
there any
                reason why they should build a circuit switched
infrastructure? By
                utilizing VOIP from the handset to the remote end - you can
                potentially remove 60% of the processing required since you
don't have
                to transcode voice packets to a mu-law or A-law stream
into/out of a B
                channel. Of course if you do have to go through a voice
gateway at the
                national gateway or where you interconnection to other
operators you
                will have to do the transcoding, but thanks to the digital
modems used
                to create dialin modem pools (such as in the Ascend Max) you
can do
                this with very high density devices (i.e., 2-4 E1
connections per 10cm
                of rack space).

                From a practical point of view there is evidence that
putting all of
                the processing in the center (i.e., not distributing it) is
not always
                the preferred solution - otherwise _everyone_ would use
Ericsson's
                AXEs to make their infrastructures (which they don't).  Even
though
                this was the case at the start of many cellular voice
networks it is
                not the case today.

                Regards,
                G. Q. "Chip" Maguire Jr.


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 10 12:00:03 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19538
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 10 Aug 1999 12:00:03 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.09F7FF70@standards.nortelnetworks.com>; Tue, 10 Aug 1999 11:54:02 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 36269 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 10 Aug 1999 11:53:36
          -0400
Received: from wodc7-1.relay.mail.uu.net by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.FA73FB80@standards.nortelnetworks.com>; Tue, 10 Aug 1999 11:53:36
          -0400
Received: from hub.ecutel.com by wodc7mr0.ffx.ops.us.uu.net with SMTP (peer
          crosschecked as: [207.77.54.132]) id QQhbrj08504 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Tue, 10 Aug 1999 15:56:22
          GMT
Received: from hub(192.168.50.149) by smtp.ecutel.com via Gauntlet (3.0) Tue,
          10 Aug 1999 12:01:00 -0500
Received: from qiangmmx [192.168.50.155] by hub.ecutel.com (SMTPD32-5.01) id
          AD6C51009C; Tue, 10 Aug 1999 12:03:56 EDT
X-Sender: qzhang@hub.ecutel.com
X-Mailer: Windows Eudora Light Version 1.5.4 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-ID:  <1.5.4.32.19990810153957.013e1a60@hub.ecutel.com>
Date:         Tue, 10 Aug 1999 11:39:57 -0400
Reply-To: Qiang Zhang <qzhang@ECUTEL.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Qiang Zhang <qzhang@ECUTEL.COM>
Subject:      Re: [MOBILE-IP] CDMA misinterpreted and
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

>
>At 10:23 AM 8/10/99 -0500, you wrote:
>>I haven't been following this closely, but if I understand the concept
>>correctly you are discussing have multiple IP connections over the RF link.
>>Why would you want to do that when the problem with wireless data is limited
>>RF resources?  Now you are suggesting using two times (or more) the RF
>>resources required.  As a CDMA carrier we are fighting to reduce the traffic
>>over the RF to allow for more subscribers, not the opposite.
>>
>>Tell me if I'm missing something here.
>
I believe people are talking about the arriving 3G or even 4G cellular
networks which can support up to 2M data rate in an indoor office WLL
environment. Beside the legacy forward/reverse channels you have for voice,
another seperated much wider bandwidth can be allocated for data purpose or
an overlapped frequency structure can be deployed... So ppl will have more
resource problem to worry :)

Qiang
>
>>
>>                -----Original Message-----
>>                From:   Gerald Maguire [mailto:maguire@IT.KTH.SE]
>>                Sent:   Monday, August 09, 1999 12:37 PM
>>                To:     MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
>>                Subject:        Re: [MOBILE-IP] CDMA misinterpreted and
>>
>>                Pete McCann <mccap@RESEARCH.BELL-LABS.COM> stated:
>>
>>                    ... So, if you want to have true multi-point
>>                    connectivity, that is, you want to have two points of IP
>>connectivity,
>>                    you need to actually replicate a lot of hardware so that
>>you can talk
>>                    on two different CDMA spreading codes at once.  This is
>>typically not
>>                    done in the CDMA transmitters of today, and, although it
>>may be a
>>                    possibility in the future, my understanding is that this
>>is not really
>>                    being planned for (someone please correct me if I'm
>>mistaken).
>>
>>                Assuming that the CDMA system is using a single frequency
>>for these
>>                two channels (i.e., that it is only a code difference betwen
>>the two)
>>                then the is very little that needs to be replicated to
>>_receive_ two
>>                different channels of CDMA - since the RF section can be
>>shared, all
>>                you need to have is an extra correlator (or three -
>>depending on if
>>                the user is moving or not) for the additional spreading
>>code. Thus the
>>                cost of receiving on multiple codes is low and you can
>>easily go from
>>                chips to bits in the basestations. If these are IP packets
>>in some
>>                sort of link frame, then you could immediately put these
>>frames into a
>>                routed IP infrastructure right from the base station.
>>
>>                The transmission problem is more complex if you are going to
>>do
>>                accurate power control - since the different chip streams
>>may have to
>>                have different power levels when transmitted. However, in
>>the case
>>                where the power can be identical (for example indoors over
>>short
>>                distances) - then there is no problem simply combining
>>(or-ing) the
>>                chip streams and then feeding them into the same RF section
>>{since
>>                after all it is the codes which separate the streams not
>>their
>>                freq. etc.}. [Note that in this case I have assummed that
>>you are
>>                generating the chips for the different streams synchronously
>>- which
>>                just makes things simpler.] Once again there is no reason
>>not to do
>>                this as close to the basestation as possible - since it
>>conserves
>>                bandwidth on the typically wired link to put off the bit to
>>chip
>>                conversion until as late as possible.
>>
>>                Unlike the voice case there is no problem (other than the
>>transport of
>>                duplicate packets) with each of the basestations which can
>>receive a
>>                mobile sending on the IP traffic that it receives. These
>>extra copies
>>                can be eliminated by administratively deciding which
>>basestations(s)
>>                will be forwarding traffic coming from a given mobile. There
>>are
>>                clearly cases (such as when the mobile is on the fringe of
>>two cells)
>>                when it may be quite reasonable for several basestations to
>>be
>>                forwarding traffic to or from a given mobile.
>>
>>                Pete further states:
>>                    When trying to build a data-over-cellular network, it's
>>important to
>>                    keep in mind that traditional voice is still the most
>>important
>>                    service and will likely be that way for some time to
>>come.  Therefore,
>>                    you should try to piggyback the service as much as
>>possible on the
>>                    existing voice infrastructure, which has already solved
>>many of these
>>                    problems in a cost-effective way.  The more changes or
>>additions to
>>                    the infrastructure you require, and the closer these
>>changes/additions
>>                    are to the "fringes" of the network (base stations), the
>>more
>>                    expensive and harder to deploy it will be.  This is a
>>lesson that
>>                    should have been learned from CDPD.
>>
>>                There is an important distinction of if this
>>data-over-cellular
>>                network is being built by an incumbant who is already
>>operating an
>>                voice oriented cellular system or not. In the case where
>>there is no
>>                existing voice oriented cellular system - there is no need
>>to use the
>>                typical voice oriented infrastructure and you can build an
>>IP oriented
>>                infrastructure from the start. Clearly if you have an
>>existing voice
>>                oriented cellular infrastructure you want to preserve its
>>value for as
>>                long as possible - therefore you are more likely to take an
>>incremental
>>                approach rather than forklift replace it. However, I don't
>>see that a
>>                voice oriented infrastructure is inherently more
>>cost-effective in the
>>                wireless setting (just as it is not in the wired setting).
>>
>>                For example, consider an operator who does not have an
>>existing GSM
>>                infrastructure but decides to go into the GPRS business. Is
>>there any
>>                reason why they should build a circuit switched
>>infrastructure? By
>>                utilizing VOIP from the handset to the remote end - you can
>>                potentially remove 60% of the processing required since you
>>don't have
>>                to transcode voice packets to a mu-law or A-law stream
>>into/out of a B
>>                channel. Of course if you do have to go through a voice
>>gateway at the
>>                national gateway or where you interconnection to other
>>operators you
>>                will have to do the transcoding, but thanks to the digital
>>modems used
>>                to create dialin modem pools (such as in the Ascend Max) you
>>can do
>>                this with very high density devices (i.e., 2-4 E1
>>connections per 10cm
>>                of rack space).
>>
>>                From a practical point of view there is evidence that
>>putting all of
>>                the processing in the center (i.e., not distributing it) is
>>not always
>>                the preferred solution - otherwise _everyone_ would use
>>Ericsson's
>>                AXEs to make their infrastructures (which they don't).  Even
>>though
>>                this was the case at the start of many cellular voice
>>networks it is
>>                not the case today.
>>
>>                Regards,
>>                G. Q. "Chip" Maguire Jr.
>>
>>
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 10 13:17:13 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20989
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 10 Aug 1999 13:17:13 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.210A5DB0@standards.nortelnetworks.com>; Tue, 10 Aug 1999 13:13:25 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 36513 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 10 Aug 1999 13:12:15
          -0400
Received: from strange.qualcomm.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.91C14390@standards.nortelnetworks.com>; Tue, 10 Aug 1999 13:02:15
          -0400
Received: from jwillkie1 (jwillkie1.qualcomm.com [129.46.219.171]) by
          strange.qualcomm.com (8.8.5/1.4/8.7.2/1.14) with SMTP id KAA17563;
          Tue, 10 Aug 1999 10:02:55 -0700 (PDT)
X-Sender: jwillkie@apprentice.qualcomm.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-ID:  <4.1.19990810095226.00cc2e80@apprentice.qualcomm.com>
Date:         Tue, 10 Aug 1999 10:04:06 -0700
Reply-To: Jim Willkie <jwillkie@QUALCOMM.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Jim Willkie <jwillkie@QUALCOMM.COM>
Subject:      Re: [MOBILE-IP] CDMA misinterpreted and
X-To:         "Lipford, Mark" <MLipfo01@SPRINTSPECTRUM.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <ABA3B5AA1991D21195940060970EB0E3C2AC79@uskmessoa021.sprint
              spectrum.com>

At 10:23 AM 8/10/99 -0500, Lipford, Mark wrote:
>I haven't been following this closely, but if I understand the concept
>correctly you are discussing have multiple IP connections over the RF link.
>Why would you want to do that when the problem with wireless data is limited
>RF resources?  Now you are suggesting using two times (or more) the RF
>resources required.  As a CDMA carrier we are fighting to reduce the traffic
>over the RF to allow for more subscribers, not the opposite.
>
>Tell me if I'm missing something here.

Mark:
You are missing nothing. The scheme being proposed seems built around the
premise that multiple CDMA traffic channels can be received to a single
user (which is how the IS-95B Medium Data Rate service provides higher
rates) but it seems suspect to split the channels into 2 distinct services,
especially if the split is at the IP layer. Seems like a good idea
(multiple traffic channels delivered to a single user) taken in a bad
direction (multiple IP end-points).

This is my opinion, for what it's worth.

Jim Willkie

>                -----Original Message-----
>                From:   Gerald Maguire [mailto:maguire@IT.KTH.SE]
>                Sent:   Monday, August 09, 1999 12:37 PM
>                To:     MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
>                Subject:        Re: [MOBILE-IP] CDMA misinterpreted and
>
>                Pete McCann <mccap@RESEARCH.BELL-LABS.COM> stated:
>
>                    ... So, if you want to have true multi-point
>                    connectivity, that is, you want to have two points of IP
>connectivity,
>                    you need to actually replicate a lot of hardware so that
>you can talk
>                    on two different CDMA spreading codes at once.  This is
>typically not
>                    done in the CDMA transmitters of today, and, although it
>may be a
>                    possibility in the future, my understanding is that this
>is not really
>                    being planned for (someone please correct me if I'm
>mistaken).
>
>                Assuming that the CDMA system is using a single frequency
>for these
>                two channels (i.e., that it is only a code difference betwen
>the two)
>                then the is very little that needs to be replicated to
>_receive_ two
>                different channels of CDMA - since the RF section can be
>shared, all
>                you need to have is an extra correlator (or three -
>depending on if
>                the user is moving or not) for the additional spreading
>code. Thus the
>                cost of receiving on multiple codes is low and you can
>easily go from
>                chips to bits in the basestations. If these are IP packets
>in some
>                sort of link frame, then you could immediately put these
>frames into a
>                routed IP infrastructure right from the base station.
>
>                The transmission problem is more complex if you are going to
>do
>                accurate power control - since the different chip streams
>may have to
>                have different power levels when transmitted. However, in
>the case
>                where the power can be identical (for example indoors over
>short
>                distances) - then there is no problem simply combining
>(or-ing) the
>                chip streams and then feeding them into the same RF section
>{since
>                after all it is the codes which separate the streams not
>their
>                freq. etc.}. [Note that in this case I have assummed that
>you are
>                generating the chips for the different streams synchronously
>- which
>                just makes things simpler.] Once again there is no reason
>not to do
>                this as close to the basestation as possible - since it
>conserves
>                bandwidth on the typically wired link to put off the bit to
>chip
>                conversion until as late as possible.
>
>                Unlike the voice case there is no problem (other than the
>transport of
>                duplicate packets) with each of the basestations which can
>receive a
>                mobile sending on the IP traffic that it receives. These
>extra copies
>                can be eliminated by administratively deciding which
>basestations(s)
>                will be forwarding traffic coming from a given mobile. There
>are
>                clearly cases (such as when the mobile is on the fringe of
>two cells)
>                when it may be quite reasonable for several basestations to
>be
>                forwarding traffic to or from a given mobile.
>
>                Pete further states:
>                    When trying to build a data-over-cellular network, it's
>important to
>                    keep in mind that traditional voice is still the most
>important
>                    service and will likely be that way for some time to
>come.  Therefore,
>                    you should try to piggyback the service as much as
>possible on the
>                    existing voice infrastructure, which has already solved
>many of these
>                    problems in a cost-effective way.  The more changes or
>additions to
>                    the infrastructure you require, and the closer these
>changes/additions
>                    are to the "fringes" of the network (base stations), the
>more
>                    expensive and harder to deploy it will be.  This is a
>lesson that
>                    should have been learned from CDPD.
>
>                There is an important distinction of if this
>data-over-cellular
>                network is being built by an incumbant who is already
>operating an
>                voice oriented cellular system or not. In the case where
>there is no
>                existing voice oriented cellular system - there is no need
>to use the
>                typical voice oriented infrastructure and you can build an
>IP oriented
>                infrastructure from the start. Clearly if you have an
>existing voice
>                oriented cellular infrastructure you want to preserve its
>value for as
>                long as possible - therefore you are more likely to take an
>incremental
>                approach rather than forklift replace it. However, I don't
>see that a
>                voice oriented infrastructure is inherently more
>cost-effective in the
>                wireless setting (just as it is not in the wired setting).
>
>                For example, consider an operator who does not have an
>existing GSM
>                infrastructure but decides to go into the GPRS business. Is
>there any
>                reason why they should build a circuit switched
>infrastructure? By
>                utilizing VOIP from the handset to the remote end - you can
>                potentially remove 60% of the processing required since you
>don't have
>                to transcode voice packets to a mu-law or A-law stream
>into/out of a B
>                channel. Of course if you do have to go through a voice
>gateway at the
>                national gateway or where you interconnection to other
>operators you
>                will have to do the transcoding, but thanks to the digital
>modems used
>                to create dialin modem pools (such as in the Ascend Max) you
>can do
>                this with very high density devices (i.e., 2-4 E1
>connections per 10cm
>                of rack space).
>
>                From a practical point of view there is evidence that
>putting all of
>                the processing in the center (i.e., not distributing it) is
>not always
>                the preferred solution - otherwise _everyone_ would use
>Ericsson's
>                AXEs to make their infrastructures (which they don't).  Even
>though
>                this was the case at the start of many cellular voice
>networks it is
>                not the case today.
>
>                Regards,
>                G. Q. "Chip" Maguire Jr.


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 10 13:42:21 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21322
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 10 Aug 1999 13:42:21 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.A24930B0@standards.nortelnetworks.com>; Tue, 10 Aug 1999 13:38:30 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 36612 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 10 Aug 1999 13:36:48
          -0400
Received: from dumburken.it.kth.se by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.64DFE840@standards.nortelnetworks.com>; Tue, 10 Aug 1999 13:36:47
          -0400
Received: (from maguire@localhost) by dumburken.it.kth.se (8.9.3/8.9.3) id
          TAA20510; Tue, 10 Aug 1999 19:39:22 +0200 (MET DST)
References:  <4.1.19990810095226.00cc2e80@apprentice.qualcomm.com>
Message-ID:  <199908101739.TAA20510@dumburken.it.kth.se>
Date:         Tue, 10 Aug 1999 19:39:22 +0200
Reply-To: Gerald Maguire <maguire@IT.KTH.SE>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gerald Maguire <maguire@IT.KTH.SE>
Subject:      Re: [MOBILE-IP] CDMA misinterpreted and
X-To:         jwillkie@QUALCOMM.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <4.1.19990810095226.00cc2e80@apprentice.qualcomm.com> (message
              from Jim Willkie on Tue, 10 Aug 1999 10:04:06 -0700)

Jim Willkie states:
    Mark:
    You are missing nothing. The scheme being proposed seems built around the
    premise that multiple CDMA traffic channels can be received to a single
    user (which is how the IS-95B Medium Data Rate service provides higher
    rates) but it seems suspect to split the channels into 2 distinct services,
    especially if the split is at the IP layer. Seems like a good idea
    (multiple traffic channels delivered to a single user) taken in a bad
    direction (multiple IP end-points).

Consider a mobile user who has a mobile IP client, if said user is
currently using operator A's network and is about to go into operator
B's network they might register a care-of address (with their home
agent) which will deliver traffic to operator B's cell which they are
about to enter. Thus the mobile user now has two care-of address and
will get copies of their IP traffic set to both of these addresses. As
the user moves from one infrastructure to the other there will now be
no period during which they have left one but not yet entered the
next, there need not be a delay in getting the home agent to start
sending traffic to their new point of attachment, etc. -- the result
is a soft handover -- even though it was across multiple operators.

In order for this to work well the mobile needs to be able to know
that operator B's infrastructure exists, know how to request a care-of
address for B's cell that they are about to enter, and needs to be
able to receive traffic from both operators during the handover
process.

Jiang Wu (jiang@it.kth.se) has shown that by registering with an agent
in the network which you are going to enter you can even have your
multicast joins done (if necessary) before you arrive - thus you can
combine his results with the soft handoff described above and thus do
soft handoffs even while participating in a multicast.

Thus I don't think that multiple IP end-points is necessarily a bad idea.

Similarily doing simulcasts (sending the same IP packet to/from more
than one BS) can be used even within a single operator's
infrastructure in order to hide the effects of handoffs between parts
of their network (i.e., when the common point in the network is
distant although the cells are adjacent) -- assuming that the operator
has a packet network infrastructure and not a circuit switched network.

Chip


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 10 13:42:22 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21324
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 10 Aug 1999 13:42:21 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.A2743850@standards.nortelnetworks.com>; Tue, 10 Aug 1999 13:38:31 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 36584 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 10 Aug 1999 13:38:17
          -0400
Received: from nbrmr1002.ac.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.34AD4DD0@standards.nortelnetworks.com>; Tue, 10 Aug 1999 13:28:17
          -0400
Received: from amrhm1101.ac.com ([170.252.192.7]) by nbrmr1002.ac.com
          (8.8.8/8.8.8) with SMTP id MAA17989 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Tue, 10 Aug 1999 12:17:08
          -0500 (CDT)
Received: by amrhm1101.ac.com(Lotus SMTP MTA v4.6.4  (830.2 3-23-1999))  id
          862567C9.005FE5F8 ; Tue, 10 Aug 1999 12:27:27 -0500
X-Lotus-FromDomain: ANDERSEN CONSULTING
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Message-ID:  <862567C9.005FE029.00@amrhm1101.ac.com>
Date:         Tue, 10 Aug 1999 12:29:23 -0500
Reply-To: shahid.ahmed@AC.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: shahid.ahmed@AC.COM
Subject:      Re: [MOBILE-IP] CDMA misinterpreted and
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

When 3G arrives, bandwidth is no longer going to be an issue. Multi-point
connectivity will provide the necessary capabilities for enabling innovative new
data application - helping carriers bring their ARPU back to normal while
keeping churn rate down to a minimum.


"Lipford, Mark" <MLipfo01@SPRINTSPECTRUM.COM> (Mailed by: "Lipford, Mark"
<MLipfo01@SPRINTSPECTRUM.COM>)
08/10/99 03:23 PM GMT
Please respond to "Lipford, Mark" <MLipfo01@SPRINTSPECTRUM.COM>

To:   MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
cc:    (bcc: Shahid Ahmed)
Subject:  Re: [MOBILE-IP] CDMA misinterpreted and




I haven't been following this closely, but if I understand the concept
correctly you are discussing have multiple IP connections over the RF link.
Why would you want to do that when the problem with wireless data is limited
RF resources?  Now you are suggesting using two times (or more) the RF
resources required.  As a CDMA carrier we are fighting to reduce the traffic
over the RF to allow for more subscribers, not the opposite.

Tell me if I'm missing something here.

                -----Original Message-----
                From:   Gerald Maguire [mailto:maguire@IT.KTH.SE]
                Sent:   Monday, August 09, 1999 12:37 PM
                To:     MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
                Subject:        Re: [MOBILE-IP] CDMA misinterpreted and

                Pete McCann <mccap@RESEARCH.BELL-LABS.COM> stated:

                    ... So, if you want to have true multi-point
                    connectivity, that is, you want to have two points of IP
connectivity,
                    you need to actually replicate a lot of hardware so that
you can talk
                    on two different CDMA spreading codes at once.  This is
typically not
                    done in the CDMA transmitters of today, and, although it
may be a
                    possibility in the future, my understanding is that this
is not really
                    being planned for (someone please correct me if I'm
mistaken).

                Assuming that the CDMA system is using a single frequency
for these
                two channels (i.e., that it is only a code difference betwen
the two)
                then the is very little that needs to be replicated to
_receive_ two
                different channels of CDMA - since the RF section can be
shared, all
                you need to have is an extra correlator (or three -
depending on if
                the user is moving or not) for the additional spreading
code. Thus the
                cost of receiving on multiple codes is low and you can
easily go from
                chips to bits in the basestations. If these are IP packets
in some
                sort of link frame, then you could immediately put these
frames into a
                routed IP infrastructure right from the base station.

                The transmission problem is more complex if you are going to
do
                accurate power control - since the different chip streams
may have to
                have different power levels when transmitted. However, in
the case
                where the power can be identical (for example indoors over
short
                distances) - then there is no problem simply combining
(or-ing) the
                chip streams and then feeding them into the same RF section
{since
                after all it is the codes which separate the streams not
their
                freq. etc.}. [Note that in this case I have assummed that
you are
                generating the chips for the different streams synchronously
- which
                just makes things simpler.] Once again there is no reason
not to do
                this as close to the basestation as possible - since it
conserves
                bandwidth on the typically wired link to put off the bit to
chip
                conversion until as late as possible.

                Unlike the voice case there is no problem (other than the
transport of
                duplicate packets) with each of the basestations which can
receive a
                mobile sending on the IP traffic that it receives. These
extra copies
                can be eliminated by administratively deciding which
basestations(s)
                will be forwarding traffic coming from a given mobile. There
are
                clearly cases (such as when the mobile is on the fringe of
two cells)
                when it may be quite reasonable for several basestations to
be
                forwarding traffic to or from a given mobile.

                Pete further states:
                    When trying to build a data-over-cellular network, it's
important to
                    keep in mind that traditional voice is still the most
important
                    service and will likely be that way for some time to
come.  Therefore,
                    you should try to piggyback the service as much as
possible on the
                    existing voice infrastructure, which has already solved
many of these
                    problems in a cost-effective way.  The more changes or
additions to
                    the infrastructure you require, and the closer these
changes/additions
                    are to the "fringes" of the network (base stations), the
more
                    expensive and harder to deploy it will be.  This is a
lesson that
                    should have been learned from CDPD.

                There is an important distinction of if this
data-over-cellular
                network is being built by an incumbant who is already
operating an
                voice oriented cellular system or not. In the case where
there is no
                existing voice oriented cellular system - there is no need
to use the
                typical voice oriented infrastructure and you can build an
IP oriented
                infrastructure from the start. Clearly if you have an
existing voice
                oriented cellular infrastructure you want to preserve its
value for as
                long as possible - therefore you are more likely to take an
incremental
                approach rather than forklift replace it. However, I don't
see that a
                voice oriented infrastructure is inherently more
cost-effective in the
                wireless setting (just as it is not in the wired setting).

                For example, consider an operator who does not have an
existing GSM
                infrastructure but decides to go into the GPRS business. Is
there any
                reason why they should build a circuit switched
infrastructure? By
                utilizing VOIP from the handset to the remote end - you can
                potentially remove 60% of the processing required since you
don't have
                to transcode voice packets to a mu-law or A-law stream
into/out of a B
                channel. Of course if you do have to go through a voice
gateway at the
                national gateway or where you interconnection to other
operators you
                will have to do the transcoding, but thanks to the digital
modems used
                to create dialin modem pools (such as in the Ascend Max) you
can do
                this with very high density devices (i.e., 2-4 E1
connections per 10cm
                of rack space).

                From a practical point of view there is evidence that
putting all of
                the processing in the center (i.e., not distributing it) is
not always
                the preferred solution - otherwise _everyone_ would use
Ericsson's
                AXEs to make their infrastructures (which they don't).  Even
though
                this was the case at the start of many cellular voice
networks it is
                not the case today.

                Regards,
                G. Q. "Chip" Maguire Jr.


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 10 17:27:34 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24224
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 10 Aug 1999 17:27:34 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.1E259F60@standards.nortelnetworks.com>; Tue, 10 Aug 1999 17:23:53 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 36886 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 10 Aug 1999 17:23:43
          -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.18539A10@standards.nortelnetworks.com>; Tue, 10 Aug 1999 17:23:43
          -0400
Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id OAA10550 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Tue, 10 Aug 1999 14:26:30
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.51.37]) by
          engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          OAA27189 for <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Tue, 10 Aug
          1999 14:26:30 -0700 (PDT)
Received: from mordor by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id OAA07110;
          Tue, 10 Aug 1999 14:26:29 -0700
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Message-ID:  <Roam.SIMC.2.0.6.934320389.16560.pcalhoun@hsmpka>
Date:         Tue, 10 Aug 1999 14:26:29 -0700
Reply-To: "pcalhoun@eng.sun.com" <Pat.Calhoun@Eng.Sun.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "pcalhoun@eng.sun.com" <Pat.Calhoun@Eng.Sun.COM>
Subject:      [MOBILE-IP] Initial bake-off results
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  "Your message with ID"
              <4.1.19990810095226.00cc2e80@apprentice.qualcomm.com>

All,

I am making the initial bake-off results available at www.diameter.org. Please
take note that the report is not final, and I still need to include the
information in a table format, but the challenge of creating a 3D ASCII table
is quite formidable.

I have looked at the last test-a-thon report, and will probably provide the
information in a similar format. I will post a mail when I am done updating the
document.

The URL is http://www.diameter.org/mip_results.txt

Enjoy,

PatC


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 10 22:09:05 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28622
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 10 Aug 1999 22:09:04 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.723F3F30@standards.nortelnetworks.com>; Tue, 10 Aug 1999 22:05:24 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 37236 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 10 Aug 1999 22:03:24
          -0400
Received: from exs24.ex.nus.edu.sg by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.C4ED16A0@standards.nortelnetworks.com>; Tue, 10 Aug 1999 21:53:24
          -0400
Received: by EXS24 with Internet Mail Service (5.5.2448.0) id <QN4NF65J>; Wed,
          11 Aug 1999 09:57:05 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <DABFA252A5A2D1118ADB00805FBED9C502D2AB1D@exs23.ex.nus.edu.sg>
Date:         Wed, 11 Aug 1999 09:56:57 +0800
Reply-To: Gao Qing <engp8682@NUS.EDU.SG>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gao Qing <engp8682@NUS.EDU.SG>
Subject:      [MOBILE-IP] routing optimization authentication
X-To:         "emadq@NORTELNETWORKS.COM" <emadq@NORTELNETWORKS.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi Emad,

In your previous email, you said:
>         In addition, once the registration reply is received by the MN,
then
> the new FA is authenticated. The HA does not send a successful reply if
the
> FA is trusted by the HA resulting in the MN trusting the FA.


Could you please tell me in your scheme which on earth entity pairs need
to perform authentication, both HA-newFA and MN-newFA, or either of them?

Is there any basis (standard or draft) for your second statement of trust
relationship derivation?

Why do you say that the HA does not send a successful reply when the
following assumption holds?

Thanks & regards,

Qing


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Wed Aug 11 07:17:57 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17943
	for <mobileip-archive@LISTS.IETF.ORG>; Wed, 11 Aug 1999 07:17:56 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.17F4E690@standards.nortelnetworks.com>; Wed, 11 Aug 1999 7:14:04 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 37719 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 11 Aug 1999 07:12:43
          -0400
Received: from p-voyageur.issy.cnet.fr by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.E7909850@standards.nortelnetworks.com>; Wed, 11 Aug 1999 7:12:43
          -0400
Received: by p-voyageur.issy.cnet.fr with Internet Mail Service (5.5.2232.9) id
          <QHVS9NV0>; Wed, 11 Aug 1999 13:16:07 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain
Message-ID:  <F09BA6AD2FB2D211BFAC00805F312C89485213@p-heron.issy.cnet.fr>
Date:         Wed, 11 Aug 1999 13:16:05 +0200
Reply-To: COELHO-ALVES Emmanuel CNET/DMR/ISS
              <emmanuel.coelhoalves@CNET.FRANCETELECOM.FR>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: COELHO-ALVES Emmanuel CNET/DMR/ISS
              <emmanuel.coelhoalves@CNET.FRANCETELECOM.FR>
Subject:      [MOBILE-IP] hawaii drafts (june 99)
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi,

I have some questions concerning hawaii drafts which have been submitted in
june 99.

Imagine we have split the access network into severals Domains. Each domain
has a Domain Root Router and each mobile host has a Home Domain.

The solution to manage mobility inside a Domain is clear.

I have some questions for clarification for the case where the mobile host
leaves its Home Domain and goes to a Foreign Domain 1.
During all the time the mobile host is in the Foreign Domain 1 we must have
a permanent forwarding from the Home Domain Root Router to the Foreign
Domain 1 Root Router.

Moreover imagine that the mobile host, after visiting the Foreign Domain 1,
goes to Foreign Domain 2.
What is the relation between Home Domain Root Router, Foreign Domain 1 Root
Router and Foreign Domain 2 Root Router when the mobile host does its
handover ? How to manage handover in this configuration ?
What is the solution to route incoming packets (I assume that routing
follows the classical IP model for outgoing packets) :
*       Home Domain Root Router -> Foreign Domain 1 Root Router -> Foreign
Domain 2 Root Router ?
or
*       Home Domain Root Router -> Foreign Domain 2 Root Router ? But if
this is the correct case, I don't see how to overpass the Foreign Domain 1
Root Router ?

In Hawaii solution, the Home Domain Root Router is a necessary point of
transit where all incoming packets must go before to join one of the Foreign
Domain Root Routers ?


Thanks in advance.
Emmanuel Coelho Alves


Emmanuel COELHO ALVES
Research Engineer
Third Generation Mobile Systems and Services
FRANCE TELECOM LABORATORY

Tel : +33 1 45 29 44 97
Fax : +33 1 45 29 43 99
Email : emmanuel.coelhoalves@cnet.francetelecom.fr


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Wed Aug 11 09:06:02 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22810
	for <mobileip-archive@LISTS.IETF.ORG>; Wed, 11 Aug 1999 09:06:02 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.3EA05A90@standards.nortelnetworks.com>; Wed, 11 Aug 1999 9:02:31 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 37988 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 11 Aug 1999 09:01:22
          -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.157FCA10@standards.nortelnetworks.com>; Wed, 11 Aug 1999
          9:01:22 -0400
Received: from zrchh190 by smtprch1.nortel.com; Wed, 11 Aug 1999 07:56:32 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Wed, 11
          Aug 1999 08:08:04 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QV1J265P>; Wed, 11 Aug 1999 08:03:37 -0500
X-Mailer: Internet Mail Service (5.5.2448.0)
X-Orig: <emadq@americasm01.nt.com>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
X-Orig: <emadq@americasm01.nt.com>
Message-ID:  <61DEB565F616D31187880000F805A8D5499A53@crchy270.us.nortel.com>
Date:         Wed, 11 Aug 1999 08:03:36 -0500
Reply-To: Emad Qaddoura <emadq@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Emad Qaddoura <emadq@NORTELNETWORKS.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Gao Qing <engp8682@NUS.EDU.SG>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Dear Gao,

        To start, there was a typo error in my earlier statement "The HA
does not send a successful reply if the FA is trusted by the HA resulting in
the MN trusting the FA" it should read:

"The HA does send a successful reply if the FA is trusted by the HA
resulting in the MN trusting the FA"

        Additional comments are below.

Regards,
Emad Qaddoura, 972-684-2705, esn (444)

> -----Original Message-----
> From: Gao Qing [mailto:engp8682@NUS.EDU.SG]
> Sent: Tuesday, August 10, 1999 8:57 PM
> To: mobile-ip@standards.nortelnetworks.com
> Subject: [MOBILE-IP] routing optimization authentication
>
>
> Hi Emad,
>
> In your previous email, you said:
> >         In addition, once the registration reply is
> received by the MN,
> then
> > the new FA is authenticated. The HA does not send a
> successful reply if
> the
> > FA is trusted by the HA resulting in the MN trusting the FA.
>
>
> Could you please tell me in your scheme which on earth entity
> pairs need
> to perform authentication, both HA-newFA and MN-newFA, or
> either of them?

In MIP, the required SA is between the MN and HA. Others between (MN and
FA), (HA and FA) are optional extensions.

Now, there is some concern about the MN establishing a new security
association during a handoff due to the delay introduced. However, what I
was suggesting is, one way for the MN to trust the new FA is:

        o The MN and HA have a SA,
        o The newFA and HA have a SA,
        o Then, the MN can trust the newFA without a direct SA between the
MN and FA.

I was not making new SAs. The mandatory and optional extensions are in 2002.


What would be your suggested SAs?

>
> Is there any basis (standard or draft) for your second
> statement of trust
> relationship derivation?

What do you see wrong in it?

>
> Why do you say that the HA does not send a successful reply when the
> following assumption holds?
>
Please see corrected statement above.

> Thanks & regards,
>
> Qing
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Wed Aug 11 10:37:19 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28661
	for <mobileip-archive@LISTS.IETF.ORG>; Wed, 11 Aug 1999 10:37:16 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.F82426C0@standards.nortelnetworks.com>; Wed, 11 Aug 1999 10:33:36 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 38046 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 11 Aug 1999 10:31:42
          -0400
Received: from crufty.research.bell-labs.com (204.178.16.49) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.B4018640@standards.nortelnetworks.com>; Wed, 11 Aug 1999
          10:31:42 -0400
Received: from bronx.dnrc.bell-labs.com ([135.180.160.8]) by crufty; Wed Aug 11
          10:33:39 EDT 1999
Received: from dnrc.bell-labs.com (IDENT:21257@ramjeepc [135.180.240.106]) by
          bronx.dnrc.bell-labs.com (8.9.3/8.9.3) with ESMTP id KAA24479; Wed,
          11 Aug 1999 10:33:35 -0400 (EDT)
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
References: <F09BA6AD2FB2D211BFAC00805F312C89485213@p-heron.issy.cnet.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID:  <37B18B62.E8E5A58D@dnrc.bell-labs.com>
Date:         Wed, 11 Aug 1999 14:40:34 +0000
Reply-To: ramjee@DNRC.BELL-LABS.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Ramachandran Ramjee <ramjee@DNRC.BELL-LABS.COM>
Subject:      Re: [MOBILE-IP] hawaii drafts (june 99)
X-To:         COELHO-ALVES Emmanuel CNET/DMR/ISS
              <emmanuel.coelhoalves@CNET.FRANCETELECOM.FR>
X-cc:         tlp@dnrc.bell-labs.com, thuel@dnrc.bell-labs.com,
              kannanv@dnrc.bell-labs.com, salga@dnrc.bell-labs.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

Hello Emmanuel,

When a mobile host is handed off from foreign domain 1 to foreign domain
2, packets will flow directly from the home domain to foreign domain
2 (the reason is that the Mobile IP home agent at the home domain
will now directly tunnel packets to a (co-located) IP address assigned
from foreign domain 2 - thus, foreign domain 1 is bypassed
automatically).
So, your second scenario is correct.

In general , whenever a mobile host moves away from its home domain,
packets have to go through the Mobile IP home agent which is located
at the home domain root router in HAWAII. There are some optimizations
that can circumvent this - for example, 1) if the foreign domain is
in the same administrative control as the home domain and the
mobile host powers up in the foreign domain, then the
mobile host can be assigned a dynamic home address and home agent
in the foreign domain itself 2) for browsing-type client-based
applications
where maintaining an IP address continously is not critical, we
could allow the mobile host to give up its old home address and
obtain a new home address on domain crossings.

Hope this clarifies.

Cheers,
Ram



COELHO-ALVES Emmanuel CNET/DMR/ISS wrote:
>
> Hi,
>
> I have some questions concerning hawaii drafts which have been submitted in
> june 99.
>
> Imagine we have split the access network into severals Domains. Each domain
> has a Domain Root Router and each mobile host has a Home Domain.
>
> The solution to manage mobility inside a Domain is clear.
>
> I have some questions for clarification for the case where the mobile host
> leaves its Home Domain and goes to a Foreign Domain 1.
> During all the time the mobile host is in the Foreign Domain 1 we must have
> a permanent forwarding from the Home Domain Root Router to the Foreign
> Domain 1 Root Router.
>
> Moreover imagine that the mobile host, after visiting the Foreign Domain 1,
> goes to Foreign Domain 2.
> What is the relation between Home Domain Root Router, Foreign Domain 1 Root
> Router and Foreign Domain 2 Root Router when the mobile host does its
> handover ? How to manage handover in this configuration ?
> What is the solution to route incoming packets (I assume that routing
> follows the classical IP model for outgoing packets) :
> *       Home Domain Root Router -> Foreign Domain 1 Root Router -> Foreign
> Domain 2 Root Router ?
> or
> *       Home Domain Root Router -> Foreign Domain 2 Root Router ? But if
> this is the correct case, I don't see how to overpass the Foreign Domain 1
> Root Router ?
>
> In Hawaii solution, the Home Domain Root Router is a necessary point of
> transit where all incoming packets must go before to join one of the Foreign
> Domain Root Routers ?
>
> Thanks in advance.
> Emmanuel Coelho Alves
>
> Emmanuel COELHO ALVES
> Research Engineer
> Third Generation Mobile Systems and Services
> FRANCE TELECOM LABORATORY
>
> Tel : +33 1 45 29 44 97
> Fax : +33 1 45 29 43 99
> Email : emmanuel.coelhoalves@cnet.francetelecom.fr


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 12 05:25:33 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27832
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 12 Aug 1999 05:25:33 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.926C3900@standards.nortelnetworks.com>; Thu, 12 Aug 1999 5:21:46 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 39250 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 12 Aug 1999 05:20:42
          -0400
Received: from exs24.ex.nus.edu.sg by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.6BF0D7E0@standards.nortelnetworks.com>; Thu, 12 Aug 1999 5:20:42
          -0400
Received: by EXS24 with Internet Mail Service (5.5.2448.0) id <QN4NGML0>; Thu,
          12 Aug 1999 17:25:08 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <DABFA252A5A2D1118ADB00805FBED9C502D2AB22@exs23.ex.nus.edu.sg>
Date:         Thu, 12 Aug 1999 17:25:06 +0800
Reply-To: Gao Qing <engp8682@NUS.EDU.SG>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gao Qing <engp8682@NUS.EDU.SG>
Subject:      [MOBILE-IP] smooth handoff
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Dear all,

In route optimizaion draft, the problem of  'smooth handoff' is presented.
However, I wonder it conforms to the strict definition of 'handoff'.
Isn't 'handoff' a concept specific to the link layer?

What exactly 'handoff' is defined as?

regards,
Qing


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 12 05:55:10 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28004
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 12 Aug 1999 05:55:10 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.C43F35A0@standards.nortelnetworks.com>; Thu, 12 Aug 1999 5:51:48 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 39271 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 12 Aug 1999 05:50:21
          -0400
Received: from ebene.inrialpes.fr by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.2AA45A70@standards.nortelnetworks.com>; Thu, 12 Aug 1999 5:40:21
          -0400
Received: from iseran.inrialpes.fr (iseran.inrialpes.fr [194.199.24.100]) by
          ebene.inrialpes.fr (8.8.5/8.8.5) with ESMTP id LAA25577; Thu, 12 Aug
          1999 11:43:10 +0200 (MET DST)
Received: from inrialpes.fr (localhost [127.0.0.1]) by iseran.inrialpes.fr
          (8.8.7/8.8.5) with ESMTP id LAA13682; Thu, 12 Aug 1999 11:43:11 +0200
          (MET DST)
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
References: <DABFA252A5A2D1118ADB00805FBED9C502D2AB22@exs23.ex.nus.edu.sg>
Content-Type: multipart/alternative;
              boundary="------------F3977D571BB885184856ED63"
Message-ID:  <37B2972F.92F302F1@inrialpes.fr>
Date:         Thu, 12 Aug 1999 11:43:11 +0200
Reply-To: Imad.Aad@INRIALPES.FR
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Imad AAD <imad.aad@INRIALPES.FR>
Organization: INRIA
Subject:      Re: [MOBILE-IP] smooth handoff
X-To:         Gao Qing <engp8682@NUS.EDU.SG>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

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

Gao Qing wrote:

> Dear all,
>
> In route optimizaion draft, the problem of  'smooth handoff' is presented.
> However, I wonder it conforms to the strict definition of 'handoff'.
> Isn't 'handoff' a concept specific to the link layer?
>
> What exactly 'handoff' is defined as?
>
> regards,
> Qing

Within a single domain, the handoff could be performed on the link layer, and
it depends on your WLAN access type (GSM, WaveLAN using WavePoints etc...)

Within 2 different domains, of possibly different local architectures, a
Handoff on the IP level is necessary, independently of the lower layers.

Imad

--
Imad AAD
http://www.inrialpes.fr/planete/people/aad



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<body text="#000000" bgcolor="#FFFFFF" link="#0000EE" vlink="#551A8B" alink="#FF0000">
Gao Qing wrote:
<blockquote TYPE=CITE>Dear all,
<p>In route optimizaion draft, the problem of&nbsp; 'smooth handoff' is
presented.
<br>However, I wonder it conforms to the strict definition of 'handoff'.
<br>Isn't 'handoff' a concept specific to the link layer?
<p>What exactly 'handoff' is defined as?
<p>regards,
<br>Qing</blockquote>
Within a single domain, the handoff could be performed on the link layer,
and it depends on your WLAN access type (GSM, WaveLAN using WavePoints
etc...)
<p>Within 2 different domains, of possibly different local architectures,
a Handoff on the IP level is necessary, independently of the lower layers.
<p>Imad
<pre>--&nbsp;
Imad AAD
<A HREF="http://www.inrialpes.fr/planete/people/aad">http://www.inrialpes.fr/planete/people/aad</A></pre>
&nbsp;
</body>
</html>

--------------F3977D571BB885184856ED63--


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 12 10:04:28 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10575
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 12 Aug 1999 10:04:27 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.7D2E60F0@standards.nortelnetworks.com>; Thu, 12 Aug 1999 10:00:21 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 39583 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 12 Aug 1999 09:59:18
          -0400
Received: from exs24.ex.nus.edu.sg by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.57B6B430@standards.nortelnetworks.com>; Thu, 12 Aug 1999 9:59:18
          -0400
Received: by EXS24 with Internet Mail Service (5.5.2448.0) id <QN4NG369>; Thu,
          12 Aug 1999 22:02:57 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <DABFA252A5A2D1118ADB00805FBED9C502D2AB24@exs23.ex.nus.edu.sg>
Date:         Thu, 12 Aug 1999 22:02:54 +0800
Reply-To: Gao Qing <engp8682@NUS.EDU.SG>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gao Qing <engp8682@NUS.EDU.SG>
Subject:      [MOBILE-IP] routing optimization authentication
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Dear Emad,

You've made your idea clear to us this time.
Actually I also came up with a similar idea.

I suggest the pre-established SAs are: MN-HA, FA-CA1, HA-CA2. (CA1 and CA2
are
respectively certification authorities of FA and HA. there is also an SA
between CA1
and CA2 as they both belong to the same CA structure.).



EXPLANARATON:

In MIP, it is compulsory that MN-HA authenticate each other because of
remote
redirection. MN-FA and FA-HA authentication are optional.

However, if we only perform MN-HA authentication, we are very likely to take
a risk
of being exposed to a hostile FA. A hostile FA can perform denial-of-service
attack to a MN or
forward the MN's registration request to a host other than the MN's HA.
Therefore, it
is also necessary to authenticate the FA.

It is impractical that all of the three security associations (MN-HA, FA-HA,
MN-FA) be
established in advance. The reason is that the MN could roam over a large
area and the number
of FAs it may get service from could be very large, thus with the MIP
standard solution based on
secret-key crypto-mechanism, such a senario would involve too many keys be
distributed between
the entity pairs. The difficulty of key management would severely impair the
scalability of MIP.

There are two methods dealing the MIP distributed authentication.
The first is based on secret-key authentication with the help of AAA
(Authentication, Authorization and Accounting)
servers which are borrowed from RADIUS (Remote Authentication Dial-in User
Service). The AAAH (Home AAA server) responds for generating three keys for
the three entity pairs of the tripartite authentication and distributing
these keys
with the help of the AAAF (Foreign AAA server). This scheme solved the
scalability
problem. However, it requires on-the-fly key generation and delivery.
The more communicants involved, the more significant overhead and delay will
be introduced.

The second method is based on public-key
authentication(draft-jacobs-mobileip-pki-auth-02.txt).
 It is based on X.509 digital certificates, digital signatures and
public-key mechanism.
This scheme solves the scalability problem of MIP without on-the-fly
key generation. However, it is more computationally intensive than the
secret-key
based method. Moreover, all the three entities need to verify each other's
public key contained in
the certificate. This may introduce significant delay especially for the
MN-FA pair since
they are very likely to belong to different Certification Authorities due to
the possibly large geographic
distance originally between their domain.

Taking into consideration that usually, the bandwidth of wireless networks
are much
more limited and the transmission error rate is much higher than those in
the wired networks,
it is desirable to optimize and reduce the number of messages sent
over the wireless link. From the viewpoint of an MN, it is also better to
have as little computation load as possible.
We proposed an authentication protocol based on both the secret-key
and public-key cryptographic mechanisms.
We keep applying the secret-key authentication between the MN and the HA.
This
is reasonable since the number of MNs an HA handles is usually limited and
they can be viewed as belonging to the same administrative domain.
Public-key based authentication is applied to the FA and the HA to
improve the scalability of the standard authentication protocol.
There is no direct authentication between the FA and the MN, but an implicit
one.
This is because the HA can in fact verify the identity of the MN to the FA
and vice
versa, provided that the two-way authentication between the two pairs, MN-HA
and FA-HA, is successfully performed. In other words, if the HA does not
trust either the MN or the FA, the authentication will fail and so will the
registration. In this way, the MN and FA can be viewed as implicitly
realizing the two-way authentication between each other.
Therefore, without on-the-fly key generation and
with one pair direct auththentication skipped, this scheme is scalable and
efficient.

PS. Though in mathematical sense, it is said that trust is not transitive:
A*B and B*C <> A*C,
I think in real world, different situation have different requirement, and
in MIP, trust relationship
to this degree is able to meet the security requirement.

regards,

Qing



-----Original Message-----
From: Emad Qaddoura [mailto:emadq@NORTELNETWORKS.COM]
Sent: Wednesday, August 11, 1999 6:04 AM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Subject: Re: [MOBILE-IP] routing optimization authentication


Dear Gao,

        To start, there was a typo error in my earlier statement "The HA
does not send a successful reply if the FA is trusted by the HA resulting in
the MN trusting the FA" it should read:

"The HA does send a successful reply if the FA is trusted by the HA
resulting in the MN trusting the FA"

        Additional comments are below.

Regards,
Emad Qaddoura, 972-684-2705, esn (444)

> -----Original Message-----
> From: Gao Qing [mailto:engp8682@NUS.EDU.SG]
> Sent: Tuesday, August 10, 1999 8:57 PM
> To: mobile-ip@standards.nortelnetworks.com
> Subject: [MOBILE-IP] routing optimization authentication
>
>
> Hi Emad,
>
> In your previous email, you said:
> >         In addition, once the registration reply is
> received by the MN,
> then
> > the new FA is authenticated. The HA does not send a
> successful reply if
> the
> > FA is trusted by the HA resulting in the MN trusting the FA.
>
>
> Could you please tell me in your scheme which on earth entity
> pairs need
> to perform authentication, both HA-newFA and MN-newFA, or
> either of them?

In MIP, the required SA is between the MN and HA. Others between (MN and
FA), (HA and FA) are optional extensions.

Now, there is some concern about the MN establishing a new security
association during a handoff due to the delay introduced. However, what I
was suggesting is, one way for the MN to trust the new FA is:

        o The MN and HA have a SA,
        o The newFA and HA have a SA,
        o Then, the MN can trust the newFA without a direct SA between the
MN and FA.

I was not making new SAs. The mandatory and optional extensions are in 2002.


What would be your suggested SAs?

>
> Is there any basis (standard or draft) for your second
> statement of trust
> relationship derivation?

What do you see wrong in it?

>
> Why do you say that the HA does not send a successful reply when the
> following assumption holds?
>
Please see corrected statement above.

> Thanks & regards,
>
> Qing
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 12 16:52:08 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22267
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 12 Aug 1999 16:52:07 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.7BFF66F0@standards.nortelnetworks.com>; Thu, 12 Aug 1999 16:48:20 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 40090 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 12 Aug 1999 16:47:06
          -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.4F500A60@standards.nortelnetworks.com>; Thu, 12 Aug 1999
          16:47:05 -0400
Received: from zrchh190 by smtprch1.nortel.com; Thu, 12 Aug 1999 15:40:49 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Thu, 12
          Aug 1999 15:52:34 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QZKLC94L>; Thu, 12 Aug 1999 15:47:52 -0500
X-Mailer: Internet Mail Service (5.5.2448.0)
X-Orig: <emadq@americasm01.nt.com>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
X-Orig: <emadq@americasm01.nt.com>
Message-ID:  <61DEB565F616D31187880000F805A8D5B7DA7A@crchy270.us.nortel.com>
Date:         Thu, 12 Aug 1999 15:25:22 -0500
Reply-To: Emad Qaddoura <emadq@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Emad Qaddoura <emadq@NORTELNETWORKS.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Gao Qing <engp8682@NUS.EDU.SG>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hello Gao,

> -----Original Message-----
> From: Gao Qing [mailto:engp8682@NUS.EDU.SG]
> Sent: Thursday, August 12, 1999 9:03 AM
> To: mobile-ip@standards.nortelnetworks.com
> Subject: [MOBILE-IP] routing optimization authentication
>
>
> Dear Emad,
>
> You've made your idea clear to us this time.
> Actually I also came up with a similar idea.
>
> I suggest the pre-established SAs are: MN-HA, FA-CA1, HA-CA2.
> (CA1 and CA2
> are
> respectively certification authorities of FA and HA. there is
> also an SA
> between CA1
> and CA2 as they both belong to the same CA structure.).
>
>
>
> EXPLANARATON:
>
> In MIP, it is compulsory that MN-HA authenticate each other because of
> remote
> redirection. MN-FA and FA-HA authentication are optional.
>
> However, if we only perform MN-HA authentication, we are very
> likely to take
> a risk
> of being exposed to a hostile FA. A hostile FA can perform
> denial-of-service
> attack to a MN or
> forward the MN's registration request to a host other than
> the MN's HA.
> Therefore, it
> is also necessary to authenticate the FA.

I totally agree. We made the same point in the draft by Mohamed Khalil and
Liem Le, "draft-mkhalil-mobileip-optim-sec-00.txt"

>
> It is impractical that all of the three security associations
> (MN-HA, FA-HA,
> MN-FA) be
> established in advance. The reason is that the MN could roam
> over a large
> area and the number
> of FAs it may get service from could be very large, thus with the MIP
> standard solution based on
> secret-key crypto-mechanism, such a senario would involve too
> many keys be
> distributed between
> the entity pairs. The difficulty of key management would
> severely impair the
> scalability of MIP.

My personal view is, it may not be practical to setup these static
relationship. The MN may visit many domains and for it to have static
relationship with all of the FAs, to allow explicit trust, would be painful
to manage.

However, if we assume that the implicit trust between the FA by the MN
resulting due to the FA trusting the HA and the MN trusting the HA, the
complexity of the static SAs may be simplified. But, any solution should
allow for dynamic trust relationship as it would be impossible to have all
SAs static.

>
> There are two methods dealing the MIP distributed authentication.
> The first is based on secret-key authentication with the help of AAA
> (Authentication, Authorization and Accounting)
> servers which are borrowed from RADIUS (Remote Authentication
> Dial-in User
> Service). The AAAH (Home AAA server) responds for generating
> three keys for
> the three entity pairs of the tripartite authentication and
> distributing
> these keys
> with the help of the AAAF (Foreign AAA server). This scheme solved the
> scalability
> problem. However, it requires on-the-fly key generation and delivery.
> The more communicants involved, the more significant overhead
> and delay will
> be introduced.
>
> The second method is based on public-key
> authentication(draft-jacobs-mobileip-pki-auth-02.txt).
>  It is based on X.509 digital certificates, digital signatures and
> public-key mechanism.
> This scheme solves the scalability problem of MIP without on-the-fly
> key generation. However, it is more computationally intensive than the
> secret-key
> based method. Moreover, all the three entities need to verify
> each other's
> public key contained in
> the certificate. This may introduce significant delay
> especially for the
> MN-FA pair since
> they are very likely to belong to different Certification
> Authorities due to
> the possibly large geographic
> distance originally between their domain.
>
> Taking into consideration that usually, the bandwidth of
> wireless networks
> are much
> more limited and the transmission error rate is much higher
> than those in
> the wired networks,
> it is desirable to optimize and reduce the number of messages sent
> over the wireless link. From the viewpoint of an MN, it is
> also better to
> have as little computation load as possible.
> We proposed an authentication protocol based on both the secret-key
> and public-key cryptographic mechanisms.
> We keep applying the secret-key authentication between the MN
> and the HA.
> This
> is reasonable since the number of MNs an HA handles is
> usually limited and
> they can be viewed as belonging to the same administrative domain.
> Public-key based authentication is applied to the FA and the HA to
> improve the scalability of the standard authentication protocol.
> There is no direct authentication between the FA and the MN,
> but an implicit
> one.
> This is because the HA can in fact verify the identity of the
> MN to the FA
> and vice
> versa, provided that the two-way authentication between the
> two pairs, MN-HA
> and FA-HA, is successfully performed. In other words, if the
> HA does not
> trust either the MN or the FA, the authentication will fail
> and so will the
> registration. In this way, the MN and FA can be viewed as implicitly
> realizing the two-way authentication between each other.
> Therefore, without on-the-fly key generation and
> with one pair direct auththentication skipped, this scheme is
> scalable and
> efficient.
>
> PS. Though in mathematical sense, it is said that trust is
> not transitive:
> A*B and B*C <> A*C,
> I think in real world, different situation have different
> requirement, and
> in MIP, trust relationship
> to this degree is able to meet the security requirement.
>
> regards,
>
> Qing
>
>
>
> -----Original Message-----
> From: Emad Qaddoura [mailto:emadq@NORTELNETWORKS.COM]
> Sent: Wednesday, August 11, 1999 6:04 AM
> To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
> Subject: Re: [MOBILE-IP] routing optimization authentication
>
>
> Dear Gao,
>
>         To start, there was a typo error in my earlier
> statement "The HA
> does not send a successful reply if the FA is trusted by the
> HA resulting in
> the MN trusting the FA" it should read:
>
> "The HA does send a successful reply if the FA is trusted by the HA
> resulting in the MN trusting the FA"
>
>         Additional comments are below.
>
> Regards,
> Emad Qaddoura, 972-684-2705, esn (444)
>
> > -----Original Message-----
> > From: Gao Qing [mailto:engp8682@NUS.EDU.SG]
> > Sent: Tuesday, August 10, 1999 8:57 PM
> > To: mobile-ip@standards.nortelnetworks.com
> > Subject: [MOBILE-IP] routing optimization authentication
> >
> >
> > Hi Emad,
> >
> > In your previous email, you said:
> > >         In addition, once the registration reply is
> > received by the MN,
> > then
> > > the new FA is authenticated. The HA does not send a
> > successful reply if
> > the
> > > FA is trusted by the HA resulting in the MN trusting the FA.
> >
> >
> > Could you please tell me in your scheme which on earth entity
> > pairs need
> > to perform authentication, both HA-newFA and MN-newFA, or
> > either of them?
>
> In MIP, the required SA is between the MN and HA. Others
> between (MN and
> FA), (HA and FA) are optional extensions.
>
> Now, there is some concern about the MN establishing a new security
> association during a handoff due to the delay introduced.
> However, what I
> was suggesting is, one way for the MN to trust the new FA is:
>
>         o The MN and HA have a SA,
>         o The newFA and HA have a SA,
>         o Then, the MN can trust the newFA without a direct
> SA between the
> MN and FA.
>
> I was not making new SAs. The mandatory and optional
> extensions are in 2002.
>
>
> What would be your suggested SAs?
>
> >
> > Is there any basis (standard or draft) for your second
> > statement of trust
> > relationship derivation?
>
> What do you see wrong in it?
>
> >
> > Why do you say that the HA does not send a successful reply when the
> > following assumption holds?
> >
> Please see corrected statement above.
>
> > Thanks & regards,
> >
> > Qing
> >
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 12 17:13:44 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22585
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 12 Aug 1999 17:13:44 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.8FAE96A0@standards.nortelnetworks.com>; Thu, 12 Aug 1999 17:10:22 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 40113 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 12 Aug 1999 17:08:34
          -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.4F8AC210@standards.nortelnetworks.com>; Thu, 12 Aug 1999 17:08:34
          -0400
Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id OAA21137 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Thu, 12 Aug 1999 14:11:27
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.53.37]) by
          engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          OAA05236 for <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Thu, 12 Aug
          1999 14:11:27 -0700 (PDT)
Received: from hsmpka.Eng.Sun.COM by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id
          OAA27502; Thu, 12 Aug 1999 14:11:22 -0700
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-ID:  <199908122111.OAA27502@hsmpka.eng.sun.com>
Date:         Thu, 12 Aug 1999 14:08:17 -0700
Reply-To: Pat.Calhoun@Eng.Sun.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Patrice Calhoun <Pat.Calhoun@Eng.Sun.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

>
>>
>> There are two methods dealing the MIP distributed authentication.
>> The first is based on secret-key authentication with the help of AAA
>> (Authentication, Authorization and Accounting)
>> servers which are borrowed from RADIUS (Remote Authentication
>> Dial-in User
>> Service). The AAAH (Home AAA server) responds for generating
>> three keys for
>> the three entity pairs of the tripartite authentication and
>> distributing
>> these keys
>> with the help of the AAAF (Foreign AAA server). This scheme solved the
>> scalability
>> problem. However, it requires on-the-fly key generation and delivery.
>> The more communicants involved, the more significant overhead
>> and delay will
>> be introduced.
>>
>> The second method is based on public-key
>> authentication(draft-jacobs-mobileip-pki-auth-02.txt).
>>  It is based on X.509 digital certificates, digital signatures and
>> public-key mechanism.
>> This scheme solves the scalability problem of MIP without on-the-fly
>> key generation. However, it is more computationally intensive than the
>> secret-key
>> based method. Moreover, all the three entities need to verify
>> each other's
>> public key contained in
>> the certificate. This may introduce significant delay
>> especially for the
>> MN-FA pair since
>> they are very likely to belong to different Certification
>> Authorities due to
>> the possibly large geographic
>> distance originally between their domain.
>>

I certainly cannot dispute the fact that a full blown PKI has scaling advantages,
but it also has deployment problems. The reality of the fact is that the global PKI
is not here yet, and may be here 5+ years from now.

That said, simply using a PKI is not quite sufficient. A service provider is probably
willing to authenticate a user given a certificate, but it certainly wants *some*
proof from the home domain that the services provided will be paid for. So AAA is more
than just for authentication, it also provides authorization and accounting. There is
some work going on in regards to authorization certificates, but these are assumed to
be longer lived than what we need here, because the overhead of creating such a certificate
is very high. I would think that such a certificate could be employed to allow a user to
print to a certain class of printers within a network, but not in this environment.

So we end up with AAA anyways. The home domain will *have* to authenticate the user, and
will perform the authorization. Generating the keying information is not that much of a
drain on resources, but encrypting the keys *could* be. Today, people scale their AAA
(read RADIUS) infrastructure by deploying more and higher end systems. The network provider
that runs their AAA infrastructure on a single 66MHz pc is in for a world of trouble.

> This
> is reasonable since the number of MNs an HA handles is
> usually limited and
> they can be viewed as belonging to the same administrative domain.
> Public-key based authentication is applied to the FA and the HA to
> improve the scalability of the standard authentication protocol.
> There is no direct authentication between the FA and the MN,
> but an implicit
> one.
> This is because the HA can in fact verify the identity of the
> MN to the FA
> and vice
> versa, provided that the two-way authentication between the
> two pairs, MN-HA
> and FA-HA, is successfully performed. In other words, if the
> HA does not
> trust either the MN or the FA, the authentication will fail
> and so will the
> registration. In this way, the MN and FA can be viewed as implicitly
> realizing the two-way authentication between each other.
> Therefore, without on-the-fly key generation and
> with one pair direct auththentication skipped, this scheme is
> scalable and
> efficient.

Lastly, your comment about MN-FA authentication not being necessary raises an issue. My
feeling was that local hand-off could be performed by allowing the Foreign Agents to
authenticate the Mobile Node, without having to inform the home agent. Of course I am
implying a hierarchical network here, and the movement is within a local network.
If the MN-FA does not exist, then how could a Foreign-Agent securely handle hand-offs?

PatC


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 12 17:56:45 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22962
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 12 Aug 1999 17:56:44 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.940FBF20@standards.nortelnetworks.com>; Thu, 12 Aug 1999 17:53:26 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 40172 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 12 Aug 1999 17:51:32
          -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.EA074350@standards.nortelnetworks.com>; Thu, 12 Aug 1999 17:41:31
          -0400
Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id OAA03568 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Thu, 12 Aug 1999 14:44:25
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (hsmpka.Eng.Sun.COM [129.146.91.47]) by
          engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          OAA12079; Thu, 12 Aug 1999 14:44:24 -0700 (PDT)
Received: from nobel by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id OAA09669; Thu,
          12 Aug 1999 14:44:21 -0700
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 3GizxM1Jh8CTqRsPu/kOJw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_28 SunOS 5.8 sun4u sparc
Message-ID:  <199908122144.OAA09669@hsmpka.eng.sun.com>
Date:         Thu, 12 Aug 1999 14:35:02 -0700
Reply-To: Vipul Gupta <Vipul.Gupta@eng.sun.com>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Vipul Gupta <Vipul.Gupta@eng.sun.com>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Pat.Calhoun@eng.sun.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

> From: Patrice Calhoun <Pat.Calhoun@eng.sun.com>

> I certainly cannot dispute the fact that a full blown PKI has scaling
advantages,
> but it also has deployment problems. The reality of the fact is that the
global PKI
> is not here yet, and may be here 5+ years from now.


  I don't see why the use of public-key style authentication in the
  context of Mobile IP has to require a "global PKI". As Steve Kent
  has also mentioned several times on the IPSec mailing list, deploying
  PKI in a closed system isn't hard (it is more a mental block than
  anything else).

  Also consider the fact that there are several thousand (if not more)
  HTTPS servers operating today using public-key technology.

  vipul


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 12 20:02:14 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24047
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 12 Aug 1999 20:02:14 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.15286420@standards.nortelnetworks.com>; Thu, 12 Aug 1999 19:58:44 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 40327 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 12 Aug 1999 19:57:20
          -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.E30B1B40@standards.nortelnetworks.com>; Thu, 12 Aug 1999 19:57:20
          -0400
Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id RAA19014 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Thu, 12 Aug 1999 17:00:14
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.91.37]) by
          engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          RAA07519; Thu, 12 Aug 1999 17:00:13 -0700 (PDT)
Received: from hsmpka.Eng.Sun.COM by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id
          RAA23218; Thu, 12 Aug 1999 17:00:03 -0700
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-ID:  <199908130000.RAA23218@hsmpka.eng.sun.com>
Date:         Thu, 12 Aug 1999 16:57:02 -0700
Reply-To: Pat.Calhoun@eng.sun.com
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Patrice Calhoun <Pat.Calhoun@eng.sun.com>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Vipul Gupta <Vipul.Gupta@eng.sun.com>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

>> From: Patrice Calhoun <Pat.Calhoun@eng.sun.com>
>
>> I certainly cannot dispute the fact that a full blown PKI has scaling
>advantages,
>> but it also has deployment problems. The reality of the fact is that the
>global PKI
>> is not here yet, and may be here 5+ years from now.
>
>
>  I don't see why the use of public-key style authentication in the
>  context of Mobile IP has to require a "global PKI". As Steve Kent
>  has also mentioned several times on the IPSec mailing list, deploying
>  PKI in a closed system isn't hard (it is more a mental block than
>  anything else).
>
>  Also consider the fact that there are several thousand (if not more)
>  HTTPS servers operating today using public-key technology.
>
>  vipul

Because with the current plans of CDMA deployment, it really isn't a "closed"
network.

PatC


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 12 20:09:09 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24097
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 12 Aug 1999 20:09:08 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.10DB5BB0@standards.nortelnetworks.com>; Thu, 12 Aug 1999 20:05:46 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 40354 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 12 Aug 1999 20:04:25
          -0400
Received: from omega.cisco.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.E01C9160@standards.nortelnetworks.com>; Thu, 12 Aug 1999 20:04:25
          -0400
Received: (from gdommety@localhost) by omega.cisco.com (8.8.8-Cisco List
          Logging/8.8.8) id RAA12443; Thu, 12 Aug 1999 17:07:17 -0700 (PDT)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-ID:  <199908130007.RAA12443@omega.cisco.com>
Date:         Thu, 12 Aug 1999 17:07:17 -0700
Reply-To: Gopal Dommety <gdommety@CISCO.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gopal Dommety <gdommety@CISCO.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Pat.Calhoun@eng.sun.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <199908130000.RAA23218@hsmpka.eng.sun.com> from "Patrice Calhoun"
              at Aug 12, 99 04:57:02 pm
Content-Transfer-Encoding: 7bit

>
> >> From: Patrice Calhoun <Pat.Calhoun@eng.sun.com>
> >
> >> I certainly cannot dispute the fact that a full blown PKI has scaling
> >advantages,
> >> but it also has deployment problems. The reality of the fact is that the
> >global PKI
> >> is not here yet, and may be here 5+ years from now.
> >
> >
> >  I don't see why the use of public-key style authentication in the
> >  context of Mobile IP has to require a "global PKI". As Steve Kent
> >  has also mentioned several times on the IPSec mailing list, deploying
> >  PKI in a closed system isn't hard (it is more a mental block than
> >  anything else).
> >
> >  Also consider the fact that there are several thousand (if not more)
> >  HTTPS servers operating today using public-key technology.
> >
> >  vipul
>
> Because with the current plans of CDMA deployment, it really isn't a "closed"
> network.

What is the definiton of a closed network?

-Gopal


>
> PatC
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 12 20:21:08 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24183
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 12 Aug 1999 20:21:08 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.BF1E4CE0@standards.nortelnetworks.com>; Thu, 12 Aug 1999 20:17:48 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 40370 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 12 Aug 1999 20:17:04
          -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.3EBE2F30@standards.nortelnetworks.com>; Thu, 12 Aug 1999 20:07:03
          -0400
Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id RAA21777 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Thu, 12 Aug 1999 17:09:57
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.55.37]) by
          engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          RAA24778; Thu, 12 Aug 1999 17:09:56 -0700 (PDT)
Received: from nobel by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id RAA26135; Thu,
          12 Aug 1999 17:09:55 -0700
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: CcHNN1NN/oOcK2gXigaglQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_28 SunOS 5.8 sun4u sparc
Message-ID:  <199908130009.RAA26135@hsmpka.eng.sun.com>
Date:         Thu, 12 Aug 1999 17:00:36 -0700
Reply-To: Vipul Gupta <Vipul.Gupta@eng.sun.com>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Vipul Gupta <Vipul.Gupta@eng.sun.com>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Pat.Calhoun@eng.sun.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

> From: Pat.Calhoun@eng.sun.com (Patrice Calhoun)

> >  I don't see why the use of public-key style authentication in the
> >  context of Mobile IP has to require a "global PKI". As Steve Kent
> >  has also mentioned several times on the IPSec mailing list, deploying
> >  PKI in a closed system isn't hard (it is more a mental block than
> >  anything else).
> >
> >  Also consider the fact that there are several thousand (if not more)
> >  HTTPS servers operating today using public-key technology.
> >
> >  vipul
>
> Because with the current plans of CDMA deployment, it really isn't a "closed"
> network.
>
> PatC

  Can you elaborate? I don't see the effort involved in setting up a
  shared key between AAA servers belonging to different carriers
  as being much different from having them cross certify each others
  root key (irrespective of whether this roaming agreement happens
  directly or indirectly through a broker).

  vipul


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 12 23:12:05 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27131
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 12 Aug 1999 23:12:04 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.665D1F60@standards.nortelnetworks.com>; Thu, 12 Aug 1999 23:07:07 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 40618 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 12 Aug 1999 23:06:16
          -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.477B1610@standards.nortelnetworks.com>; Thu, 12 Aug 1999 23:06:15
          -0400
Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id UAA27055 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Thu, 12 Aug 1999 20:09:05
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (hsmpka.Eng.Sun.COM [129.146.53.47]) by
          engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          UAA12598; Thu, 12 Aug 1999 20:09:04 -0700 (PDT)
Received: from hsmpka.Eng.Sun.COM by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id
          UAA01554; Thu, 12 Aug 1999 20:08:44 -0700
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-ID:  <199908130308.UAA01554@hsmpka.eng.sun.com>
Date:         Thu, 12 Aug 1999 20:05:51 -0700
Reply-To: Pat.Calhoun@eng.sun.com
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Patrice Calhoun <Pat.Calhoun@eng.sun.com>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Vipul.Gupta@eng.sun.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

>
>> From: Pat.Calhoun@eng.sun.com (Patrice Calhoun)
>
>> >  I don't see why the use of public-key style authentication in the
>> >  context of Mobile IP has to require a "global PKI". As Steve Kent
>> >  has also mentioned several times on the IPSec mailing list, deploying
>> >  PKI in a closed system isn't hard (it is more a mental block than
>> >  anything else).
>> >
>> >  Also consider the fact that there are several thousand (if not more)
>> >  HTTPS servers operating today using public-key technology.
>> >
>> >  vipul
>>
>> Because with the current plans of CDMA deployment, it really isn't a "closed"
>> network.
>>
>> PatC
>
>  Can you elaborate? I don't see the effort involved in setting up a
>  shared key between AAA servers belonging to different carriers
>  as being much different from having them cross certify each others
>  root key (irrespective of whether this roaming agreement happens
>  directly or indirectly through a broker).

Vipul,

The number of relationships in the AAA case is one per peer, in the case of the
PKI we are talking about a cert for each mobile node and mobility agent. One
also has to consider the CRL infrastructure that need to be in place to support
that kind of network.

I could be wrong but setting up a relationship with a broker, and getting a single
cert for the AAA server seems much less complex. Furthermore, no CRL is required since
the broker participates in the AA/A, and therefore would deny any requests for/from
an ISP/corporate customer that is no longer part of the consortium.

PatC
>
>  vipul
>
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 02:32:56 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13429
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 02:32:56 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.A7659DE0@standards.nortelnetworks.com>; Fri, 13 Aug 1999 2:29:22 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 40779 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 02:28:15
          -0400
Received: from omega.cisco.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.7EE4A8C0@standards.nortelnetworks.com>; Fri, 13 Aug 1999 2:28:14
          -0400
Received: (from gdommety@localhost) by omega.cisco.com (8.8.8-Cisco List
          Logging/8.8.8) id XAA05935; Thu, 12 Aug 1999 23:31:05 -0700 (PDT)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-ID:  <199908130631.XAA05935@omega.cisco.com>
Date:         Thu, 12 Aug 1999 23:31:05 -0700
Reply-To: Gopal Dommety <gdommety@CISCO.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gopal Dommety <gdommety@CISCO.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Pat.Calhoun@eng.sun.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <199908130308.UAA01554@hsmpka.eng.sun.com> from "Patrice Calhoun"
              at Aug 12, 99 08:05:51 pm
Content-Transfer-Encoding: 7bit

> >> network.
> >>
> >> PatC
> >
> >  Can you elaborate? I don't see the effort involved in setting up a
> >  shared key between AAA servers belonging to different carriers
> >  as being much different from having them cross certify each others
> >  root key (irrespective of whether this roaming agreement happens
> >  directly or indirectly through a broker).
>
> Vipul,
>
> The number of relationships in the AAA case is one per peer, in the case of the
> PKI we are talking about a cert for each mobile node and mobility agent. One

Pat,

If we assume a shared key between the mobile and the HA and use certs
for HA and FA then the scalability may not be problem. We may not need
FA-MN auth in most cases (if MN-HA and FA-HA exist).


> also has to consider the CRL infrastructure that need to be in place to support
> that kind of network.
>
> I could be wrong but setting up a relationship with a broker, and getting a single
> cert for the AAA server seems much less complex. Furthermore, no CRL is required since
> the broker participates in the AA/A, and therefore would deny any
> requests for/from

Are you assuming that the AAA borker is also the CA (Certificate Authority)?

-Gopal


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 07:47:33 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18506
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 07:47:33 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.8DB8E0B0@standards.nortelnetworks.com>; Fri, 13 Aug 1999 7:43:37 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 40946 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 07:42:20
          -0400
Received: from mgw-x2.nokia.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.F9CEC730@standards.nortelnetworks.com>; Fri, 13 Aug 1999 7:32:19
          -0400
Received: from mgw-i2.ntc.nokia.com (mgw-i2.ntc.nokia.com [131.228.118.61]) by
          mgw-x2.nokia.com (8.9.3/8.9.3) with ESMTP id OAA11240 for
          <mobile-ip@standards.nortelnetworks.com>; Fri, 13 Aug 1999 14:35:13
          +0300 (EETDST)
Received: from loki.research.nokia.com (loki.research.nokia.com [172.21.33.76])
          by mgw-i2.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id OAA05785 for
          <mobile-ip@standards.nortelnetworks.com>; Fri, 13 Aug 1999 14:35:12
          +0300 (EETDST)
Received: from pupu.research.nokia.com (pupu.research.nokia.com [172.21.33.84])
          by loki.research.nokia.com (8.9.3/8.9.3) with ESMTP id OAA22754 for
          <mobile-ip@standards.nortelnetworks.com>; Fri, 13 Aug 1999 14:33:14
          +0300 (EETDST)
Received: from possu.research.nokia.com (possu.research.nokia.com
          [172.21.33.80]) by pupu.research.nokia.com (8.9.1a/8.9.1) with ESMTP
          id OAA28298 for <mobile-ip@standards.nortelnetworks.com>; Fri, 13 Aug
          1999 14:31:11 +0300 (EET DST)
Received: (from asokan@localhost) by possu.research.nokia.com (8.9.1/8.9.1) id
          OAA00707; Fri, 13 Aug 1999 14:32:50 +0300 (EET DST)
References: <7ouk8q$9m@ammu.research.nokia.com>
Lines: 65
X-Mailer: Gnus v5.6.45/Emacs 19.34
Message-ID:  <1tdbtcbapb1.fsf@possu.research.nokia.com>
Date:         Fri, 13 Aug 1999 14:32:49 +0300
Reply-To: "n. asokan" <n.asokan@NOKIA.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "n. asokan" <n.asokan@NOKIA.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  engp8682@NUS.EDU.SG's message of "Thu, 12 Aug 1999 22:02:54 +0800"

Hi,

engp8682@NUS.EDU.SG (EXT Gao Qing) writes:
[...]
> However, if we only perform MN-HA authentication, we are very likely to take
> a risk
> of being exposed to a hostile FA. A hostile FA can perform denial-of-service
> attack to a MN or
> forward the MN's registration request to a host other than the MN's HA.
> Therefore, it
> is also necessary to authenticate the FA.

What exactly is the threat and how will FA->HA authentication help
with that?

If the threat is denial of service, FA->HA authentication
won't help (FA can simply not forward any packets, including the
registration request).

If the threat is FA having access to MN's data, it is probably best
dealt with using upper layer confidentiality protection.

In any case, to avoid 'hostile FAs', FA->HA authentication alone isn't
enough.  HA has to have some way of deciding whether an FA is
'hostile' (black lists, white lists, whatever).  This probably implies
more infrastructure.

[...]

>
> There are two methods dealing the MIP distributed authentication.
> The first is based on secret-key authentication with the help of AAA
> (Authentication, Authorization and Accounting)
> servers which are borrowed from RADIUS (Remote Authentication Dial-in User
> Service). The AAAH (Home AAA server) responds for generating three keys for
> the three entity pairs of the tripartite authentication and distributing
> these keys
> with the help of the AAAF (Foreign AAA server). This scheme solved the
> scalability
> problem. However, it requires on-the-fly key generation and delivery.
> The more communicants involved, the more significant overhead and delay will
> be introduced.

Actually, use of shared-key systems does not have to necessarily imply
having an entity like AAAH generate keys on the fly and distribute it
to MN: short term/temporary keys can be derived from a long term key.
E.g., in your example above, if the MN shares a long term key K with
the AAAH, then the key between MN and a given FA can be derived as a
function of K, the identity of the FA, and possibly some transient
information (like the current time).  That way, the AAAH does not have
to generate a key and convey it to MN and FA but compute it and convey
it only to the FA (via AAAF). I.e., MN can already compute this key
and use it to compute and attach an authenticator in its registration
request.  FA will be able to verify the authenticator when it receives
the key from AAAH.  No additional flows between FA and MN are
necessary.

[...]

Regards,
- Asokan

--
N. Asokan, Communication Systems Lab, Nokia Research Center, Helsinki


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 09:19:16 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25935
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 09:19:15 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.6B3B9C50@standards.nortelnetworks.com>; Fri, 13 Aug 1999 9:15:43 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 41015 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 09:13:51
          -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.283E1AE0@standards.nortelnetworks.com>; Fri, 13 Aug 1999 9:13:50
          -0400
Received: from engmail3.Eng.Sun.COM ([129.144.170.5]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id GAA13356; Fri, 13 Aug 1999 06:16:45
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpkb.Eng.Sun.COM [129.146.103.38]) by
          engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          GAA27516; Fri, 13 Aug 1999 06:16:45 -0700 (PDT)
Received: from hsmpka.Eng.Sun.COM by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id
          GAA26642; Fri, 13 Aug 1999 06:16:34 -0700
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-ID:  <199908131316.GAA26642@hsmpka.eng.sun.com>
Date:         Fri, 13 Aug 1999 06:13:27 -0700
Reply-To: Pat.Calhoun@eng.sun.com
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Patrice Calhoun <Pat.Calhoun@eng.sun.com>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Gopal Dommety <gdommety@cisco.com>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

>> >> network.
>> >>
>> >> PatC
>> >
>> >  Can you elaborate? I don't see the effort involved in setting up a
>> >  shared key between AAA servers belonging to different carriers
>> >  as being much different from having them cross certify each others
>> >  root key (irrespective of whether this roaming agreement happens
>> >  directly or indirectly through a broker).
>>
>> Vipul,
>>
>> The number of relationships in the AAA case is one per peer, in the case of
>the
>> PKI we are talking about a cert for each mobile node and mobility agent. One
>
>Pat,
>
>If we assume a shared key between the mobile and the HA and use certs
>for HA and FA then the scalability may not be problem. We may not need
>FA-MN auth in most cases (if MN-HA and FA-HA exist).

See my previous response to this in regards to local mobility in a hierarchical
network.

>
>
>> also has to consider the CRL infrastructure that need to be in place to
>support
>> that kind of network.
>>
>> I could be wrong but setting up a relationship with a broker, and getting a
>single
>> cert for the AAA server seems much less complex. Furthermore, no CRL is
>required since
>> the broker participates in the AA/A, and therefore would deny any
>> requests for/from
>
>Are you assuming that the AAA borker is also the CA (Certificate Authority)?

I think most of my AAA documents are pretty clear about this. A broker can easily
act as a CA, issuing certs to the AAA servers that are part of the roaming
consortium.

PatC


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 11:42:11 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03821
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 11:42:10 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.51CA7570@standards.nortelnetworks.com>; Fri, 13 Aug 1999 11:38:10 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 41215 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 11:36:47
          -0400
Received: from mainframe.dgrc.crc.ca by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.BA302530@standards.nortelnetworks.com>; Fri, 13 Aug 1999 11:26:46
          -0400
Received: from crc.ca (curly.dgrc.crc.ca [142.92.38.251]) by
          mainframe.dgrc.crc.ca (8.9.3/8.9.3) with ESMTP id LAA16051 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Fri, 13 Aug 1999 11:27:56
          -0400 (EDT)
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID:  <37B438B7.C0CD57C0@crc.ca>
Date:         Fri, 13 Aug 1999 11:24:39 -0400
Reply-To: Guilhem Tardy <Guilhem.Tardy@CRC.CA>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Guilhem Tardy <Guilhem.Tardy@CRC.CA>
Subject:      [MOBILE-IP] QoS [diff-serv or int-serv/RSVP]
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

Hi!

I am looking into the QoS stuff... do you have some links about what's
underway about it within MOBIP?

Best regards,
Guilhem.

--
Guilhem Tardy                       phone: (613) 993-8232
Communications Research Center      email: Guilhem.Tardy@crc.ca
Network Systems and Technologies    web:   http://www.crc.ca/


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 12:10:54 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04542
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 12:10:54 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.6499FE10@standards.nortelnetworks.com>; Fri, 13 Aug 1999 12:07:19 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 41363 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 12:06:38
          -0400
Received: from sirius.ctr.columbia.edu by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.4BFA4810@standards.nortelnetworks.com>; Fri, 13 Aug 1999 12:06:38
          -0400
Received: from comet.columbia.edu (sweetpea.comet.columbia.edu [128.59.68.61])
          by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) with ESMTP id MAA13215
          for <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Fri, 13 Aug 1999
          12:09:29 -0400 (EDT)
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID:  <37B47032.DF9D1B7D@comet.columbia.edu>
Date:         Fri, 13 Aug 1999 12:21:22 -0700
Reply-To: campbell@comet.columbia.edu
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "Andrew T. Campbell" <campbell@comet.columbia.edu>
Organization: Center for Telecommunications Research
Subject:      [MOBILE-IP] IEEE MOMUC99: Call For Demos and Position/Short Papers
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

Call For Demos and Position/Short Papers

IEEE MOMUC99

Sponsored by the IEEE Communications Society

The deadline for submission of short/position papers
and demos for the Sixth IEEE International
Workshop on Mobile Multimedia Communications (MOMUC'99)
is fast approaching: September 1, 1999.

(Note that submission for long papers is closed).

Position/short papers can outline new research projects,
new research ideas or positions on possible
solutions to exiting or future challenges in
mobile multimedia communications.

Researchers are also invited to submit DEMO outlines
for systems to be demonstrated at the workshop. To qualify
for consideration, a prototype should be capable of
demonstrating multimedia services (including voice, video
and data) over a wireless interface. Full details of
the radio layer characteristics (particularly the operating
frequency) should be included in the outline.

Accepted position/short papers and DEMO outlines
will be published by IEEE as part of the workshop
proceedings. Position/short papers and
DEMO outlines are limited to 3 pages.

For full submission details see:

  http://cwc.ucsd.edu/momuc99/momuc_submission.html

Position papers and DEMO outlines due: September 1, 1999.
Notification of acceptance: September 15, 1999.
Camera Ready Due: September 25, 1999


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 12:17:02 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04632
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 12:17:01 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.3C52E830@standards.nortelnetworks.com>; Fri, 13 Aug 1999 12:13:21 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 41391 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 12:11:30
          -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.F9DFCC70@standards.nortelnetworks.com>; Fri, 13 Aug 1999
          12:11:30 -0400
Received: from zrchh190 by smtprch1.nortel.com; Fri, 13 Aug 1999 11:06:22 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Fri, 13
          Aug 1999 11:18:16 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QZ38Q6K6>; Fri, 13 Aug 1999 11:13:37 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-Orig: <bpatil@americasm01.nt.com>
X-Orig: <bpatil@americasm01.nt.com>
Message-ID:  <61DEB565F616D31187880000F805A8D5817E91@crchy270.us.nortel.com>
Date:         Fri, 13 Aug 1999 11:13:28 -0500
Reply-To: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         "Pat.Calhoun@eng.sun.com" <Pat.Calhoun@eng.sun.com>
X-cc:         Vipul Gupta <Vipul.Gupta@ENG.SUN.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

>>> From: Patrice Calhoun <Pat.Calhoun@eng.sun.com>
>>
>>> I certainly cannot dispute the fact that a full blown PKI has scaling
>>advantages,
>>> but it also has deployment problems. The reality of the fact is that the
>>global PKI
>>> is not here yet, and may be here 5+ years from now.
>>
>>
>>  I don't see why the use of public-key style authentication in the
>>  context of Mobile IP has to require a "global PKI". As Steve Kent
>>  has also mentioned several times on the IPSec mailing list, deploying
>>  PKI in a closed system isn't hard (it is more a mental block than
>>  anything else).
>>
>>  Also consider the fact that there are several thousand (if not more)
>>  HTTPS servers operating today using public-key technology.
>>
>>  vipul
>
>Because with the current plans of CDMA deployment, it really isn't a
"closed"
>network.
>
>PatC

The current CDMA deployment is among a few major service providers
and can be *considered* a "Closed" network for the purpose of
discussion here. The organizations that intend on deploying Mobile IP
need to take a serious look at the option of having a closed PKI
system and the fact that it is very much a feasible solution. I agree
with Vipul's thought here,  that deployment of Mobile IP by a group of
service providers who can agree and thereby have a closed PKI
system. Global roaming in the future will require supporting global
PKI. But by the time we get to that point I believe we will have such
an infrastructure in place.

-Basavaraj


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 12:24:03 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04746
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 12:24:03 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.37D18950@standards.nortelnetworks.com>; Fri, 13 Aug 1999 12:20:23 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 41417 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 12:19:23
          -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.136754F0@standards.nortelnetworks.com>; Fri, 13 Aug 1999 12:19:22
          -0400
Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id JAA15435; Fri, 13 Aug 1999 09:21:25
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.91.37]) by
          engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          JAA13485; Fri, 13 Aug 1999 09:21:24 -0700 (PDT)
Received: from hsmpka.Eng.Sun.COM by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id
          JAA28045; Fri, 13 Aug 1999 09:20:43 -0700
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-ID:  <199908131620.JAA28045@hsmpka.eng.sun.com>
Date:         Fri, 13 Aug 1999 09:17:53 -0700
Reply-To: Pat.Calhoun@Eng.Sun.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Patrice Calhoun <Pat.Calhoun@Eng.Sun.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Basavaraj Patil <bpatil@nortelnetworks.com>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

>
>
>>>> From: Patrice Calhoun <Pat.Calhoun@eng.sun.com>
>>>
>>>> I certainly cannot dispute the fact that a full blown PKI has scaling
>>>advantages,
>>>> but it also has deployment problems. The reality of the fact is that the
>>>global PKI
>>>> is not here yet, and may be here 5+ years from now.
>>>
>>>
>>>  I don't see why the use of public-key style authentication in the
>>>  context of Mobile IP has to require a "global PKI". As Steve Kent
>>>  has also mentioned several times on the IPSec mailing list, deploying
>>>  PKI in a closed system isn't hard (it is more a mental block than
>>>  anything else).
>>>
>>>  Also consider the fact that there are several thousand (if not more)
>>>  HTTPS servers operating today using public-key technology.
>>>
>>>  vipul
>>
>>Because with the current plans of CDMA deployment, it really isn't a
>"closed"
>>network.
>>
>>PatC
>
>The current CDMA deployment is among a few major service providers
>and can be *considered* a "Closed" network for the purpose of
>discussion here. The organizations that intend on deploying Mobile IP
>need to take a serious look at the option of having a closed PKI
>system and the fact that it is very much a feasible solution. I agree
>with Vipul's thought here,  that deployment of Mobile IP by a group of
>service providers who can agree and thereby have a closed PKI
>system. Global roaming in the future will require supporting global
>PKI. But by the time we get to that point I believe we will have such
>an infrastructure in place.
>
The current AAA proposals that I've made allow for the broker to issue certificates
to all roaming partners, but not in the scale that you are talking about. In fact,
no cross-certs are necessary, unless inter-broker mobility is allowed.

As I stated earlier, even if that is the case the AAAF/AAAH are still needed
to make on-the-fly authorization decisions. A certificate alone will not be
sufficient for a foreign service provider to provide service to a mobile node.

PatC


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 12:47:13 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05268
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 12:47:12 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.78694E00@standards.nortelnetworks.com>; Fri, 13 Aug 1999 12:43:40 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 41576 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 12:42:27
          -0400
Received: from babelfish.axion.bt.co.uk by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.4CE8D480@standards.nortelnetworks.com>; Fri, 13 Aug 1999 12:42:27
          -0400
Received: from cbtlipnt02.btlabs.bt.co.uk by babelfish.axion.bt.co.uk (local)
          with ESMTP; Fri, 13 Aug 1999 17:45:09 +0100
Received: by cbtlipnt02.btlabs.bt.co.uk with Internet Mail Service (5.5.2448.0)
          id <QWTKPYNQ>; Fri, 13 Aug 1999 17:45:05 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Message-ID:  <5104D4DBC598D211B5FE0000F8FE7EB202432748@mbtlipnt02.btlabs.bt.co.uk>
Date:         Fri, 13 Aug 1999 17:45:08 +0100
Reply-To: guilhem.ensuque@BT.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "G. Ensuque" <guilhem.ensuque@BT.COM>
Subject:      [MOBILE-IP] Dial-up scenario with Mobile IP - help needed
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi all

I am trying to get my head 'round what happens when a Mobile Node dials up a
NAS using PPP and the ISP uses RADIUS to authenticate him.

Has anyone already looked at that? I would be very grateful if someone could
point me towards web resources, slide packs, articles... describing the
whole session setup process

I have problems figuring out the interactions and message exchanges between
PPP, IPCP, RADIUS and Mobile IP NAI and Challenge/response extensions.

Are Challenge/Response and RADIUS authentication mutually exclusive ?

Is a double authentication needed:
1) with PPP/RADIUS to access the link layer
2) with the FA to be able to register the FCoA with the HA

Thanks for any bit of help

Guilhem Ensuque

Mobility Futures Unit                           guilhem.ensuque@bt.com
B55-131B
BT Advanced Communications Technology Centre
Adastral Park, Martlesham Heath
IPSWICH IP5 3RE                              Tel: +44 1473 645 232
UK                                                   Fax: +44 1473 646 885


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 13:00:58 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05506
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 13:00:58 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.4F285250@standards.nortelnetworks.com>; Fri, 13 Aug 1999 12:56:50 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 41635 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 12:55:21
          -0400
Received: from omega.cisco.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.1A043210@standards.nortelnetworks.com>; Fri, 13 Aug 1999 12:55:21
          -0400
Received: (from gdommety@localhost) by omega.cisco.com (8.8.8-Cisco List
          Logging/8.8.8) id JAA06618; Fri, 13 Aug 1999 09:58:16 -0700 (PDT)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-ID:  <199908131658.JAA06618@omega.cisco.com>
Date:         Fri, 13 Aug 1999 09:58:16 -0700
Reply-To: Gopal Dommety <gdommety@CISCO.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gopal Dommety <gdommety@CISCO.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Pat.Calhoun@Eng.Sun.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <199908131620.JAA28045@hsmpka.eng.sun.com> from "Patrice Calhoun"
              at Aug 13, 99 09:17:53 am
Content-Transfer-Encoding: 7bit

>
> As I stated earlier, even if that is the case the AAAF/AAAH are still needed
> to make on-the-fly authorization decisions. A certificate alone will not be
> sufficient for a foreign service provider to provide service to a mobile node.

We will need for accounting reasons.  As for authorization, why cann't
the FA interact  with FAAA locally,  and HA with  the HAAA locally (to
avoid  the configuration  of authorization information   at the HA and
FA)?

Thanks
Gopal




>
> PatC
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 13:00:58 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05508
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 13:00:58 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.4FB04700@standards.nortelnetworks.com>; Fri, 13 Aug 1999 12:56:51 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 41645 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 12:56:12
          -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.387FB160@standards.nortelnetworks.com>; Fri, 13 Aug 1999
          12:56:12 -0400
Received: from zrchh190 by smtprch1.nortel.com; Fri, 13 Aug 1999 11:50:41 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Fri, 13
          Aug 1999 12:02:36 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QZ38Q897>; Fri, 13 Aug 1999 11:57:56 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-Orig: <bpatil@americasm01.nt.com>
X-Orig: <bpatil@americasm01.nt.com>
Message-ID:  <61DEB565F616D31187880000F805A8D5817E92@crchy270.us.nortel.com>
Date:         Fri, 13 Aug 1999 11:57:54 -0500
Reply-To: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         "Pat.Calhoun" <Pat.Calhoun@Eng.Sun.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

>>>>> From: Patrice Calhoun <Pat.Calhoun@eng.sun.com>
>>>>
>>>>> I certainly cannot dispute the fact that a full blown PKI has scaling
>>>>advantages,
>>>>> but it also has deployment problems. The reality of the fact is that
the
>>>>global PKI
>>>>> is not here yet, and may be here 5+ years from now.
>>>>
>>>>
>>>>  I don't see why the use of public-key style authentication in the
>>>>  context of Mobile IP has to require a "global PKI". As Steve Kent
>>>>  has also mentioned several times on the IPSec mailing list, deploying
>>>>  PKI in a closed system isn't hard (it is more a mental block than
>>>>  anything else).
>>>>
>>>>  Also consider the fact that there are several thousand (if not more)
>>>>  HTTPS servers operating today using public-key technology.
>>>>
>>>>  vipul
>>>
>>>Because with the current plans of CDMA deployment, it really isn't a
>>"closed"
>>>network.
>>>
>>>PatC
>>
>>The current CDMA deployment is among a few major service providers
>>and can be *considered* a "Closed" network for the purpose of
>>discussion here. The organizations that intend on deploying Mobile IP
>>need to take a serious look at the option of having a closed PKI
>>system and the fact that it is very much a feasible solution. I agree
>>with Vipul's thought here,  that deployment of Mobile IP by a group of
>>service providers who can agree and thereby have a closed PKI
>>system. Global roaming in the future will require supporting global
>>PKI. But by the time we get to that point I believe we will have such
>>an infrastructure in place.
>>
>The current AAA proposals that I've made allow for the broker to
>issue certificates to all roaming partners, but not in the scale that
>you are talking about. In fact, no cross-certs are necessary, unless
>inter-broker mobility is allowed.
>
>As I stated earlier, even if that is the case the AAAF/AAAH are still
needed
>to make on-the-fly authorization decisions. A certificate alone will not be
>sufficient for a foreign service provider to provide service to a mobile
node.
>
>PatC
>


Pat,

So the broker is a CA and issues certs to the roaming partners? What I
am refering to is the case where you have a few service providers who
agree to cross certify their CAs as a result of roaming agreements
between them. The PKI managed by a service provider could issue certs
to the mobility agents. I am not refering to brokers at all. Well I
guess you could still have a broker concept to minimize the number of
associations between roaming partners, but in a small subset it does
not really matter.

In order to provide service to a foreign MN the visiting network needs
to be assured of receiving payment. Since the FA and HA *may* authenticate
each other via certs, receiving a successful registration reply should
be sufficient (in my opinion). What other authorization info (in the
present context) needs to be provided to the visiting network in order
to provide service. Of course you will need the capability of
generating accounting records and that's where the *A* of AAA may fit
in. Maybe I am missing your point Pat....If I am please clarify.

-Raj


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 13:03:53 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05613
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 13:03:52 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.BF28A780@standards.nortelnetworks.com>; Fri, 13 Aug 1999 12:59:58 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 41734 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 12:59:27
          -0400
Received: from dirty.research.bell-labs.com (204.178.16.6) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.ACB7E3E0@standards.nortelnetworks.com>; Fri, 13 Aug 1999
          12:59:27 -0400
Received: from grubby.research.bell-labs.com ([135.104.2.9]) by dirty; Fri Aug
          13 13:00:52 EDT 1999
Received: from king.research.bell-labs.com ([135.1.152.1]) by grubby; Fri Aug
          13 13:01:15 EDT 1999
Received: from notmafia.research.bell-labs.com.research.bell-labs.com (notmafia
          [135.1.152.230]) by king.research.bell-labs.com (Postfix) with SMTP
          id D0E8D57013; Fri, 13 Aug 1999 12:01:15 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <5104D4DBC598D211B5FE0000F8FE7EB202432748@mbtlipnt02.btlabs.bt.co.uk>
X-Mailer: VM 6.33 under Emacs 19.34.2
Message-ID:  <19990813170115.D0E8D57013@king.research.bell-labs.com>
Date:         Fri, 13 Aug 1999 12:01:15 -0500
Reply-To: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Subject:      [MOBILE-IP] Dial-up scenario with Mobile IP - help needed
X-To:         guilhem.ensuque@BT.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <5104D4DBC598D211B5FE0000F8FE7EB202432748@mbtlipnt02.btlabs.bt.co.uk>
Content-Transfer-Encoding: 7bit

Hi, Guilhem,

You ask good questions.

My understanding is that the basic authentication algorithm given in
Charlie's Mobile IP Challenge-Response document is incompatible with
current RADIUS implementations.  However, nothing prevents you from
using a different algorithm; your infrastructure should use the SPI to
determine which one is used.  Ken Pierce made a presentation in Oslo
describing how to use the Challenge-Response extension with RADIUS.
So, Mobile IP has the potential to replace CHAP as an authentication
mechanism.  It has the advantage of being link-layer independent.  So
double authentication is not necessary, although certain deployment
scenarios (where support of non-Mobile IP devices is needed) might do
this.

Some aspects of IPCP are also redundant if Mobile IP is used to assign
a home address (which is possible when using the NAI extension) and
when using an FA-located COA.  For instance, address assignment should
not be done with IPCP in this case - the PPP implementation should
leave out the "IP Address" option in the Configure-Request, and use
the source address 0.0.0.0 until it is assigned an address.

-Pete


"G. Ensuque" <guilhem.ensuque@BT.COM> (GE) writes:

GE> Hi all
GE> I am trying to get my head 'round what happens when a Mobile Node dials up a
GE> NAS using PPP and the ISP uses RADIUS to authenticate him.

GE> Has anyone already looked at that? I would be very grateful if someone could
GE> point me towards web resources, slide packs, articles... describing the
GE> whole session setup process

GE> I have problems figuring out the interactions and message exchanges between
GE> PPP, IPCP, RADIUS and Mobile IP NAI and Challenge/response extensions.

GE> Are Challenge/Response and RADIUS authentication mutually exclusive ?

GE> Is a double authentication needed:
GE> 1) with PPP/RADIUS to access the link layer
GE> 2) with the FA to be able to register the FCoA with the HA

GE> Thanks for any bit of help

GE> Guilhem Ensuque

GE> Mobility Futures Unit                           guilhem.ensuque@bt.com
GE> B55-131B
GE> BT Advanced Communications Technology Centre
GE> Adastral Park, Martlesham Heath
GE> IPSWICH IP5 3RE                              Tel: +44 1473 645 232
GE> UK                                                   Fax: +44 1473 646 885


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 13:09:32 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05713
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 13:09:32 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.9745AAA0@standards.nortelnetworks.com>; Fri, 13 Aug 1999 13:06:00 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 41769 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 13:05:04
          -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.7587AA80@standards.nortelnetworks.com>; Fri, 13 Aug 1999 13:05:04
          -0400
Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id KAA05499; Fri, 13 Aug 1999 10:07:45
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (hsmpka.Eng.Sun.COM [129.146.61.47]) by
          engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          KAA22378; Fri, 13 Aug 1999 10:07:44 -0700 (PDT)
Received: from hsmpka.Eng.Sun.COM by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id
          KAA13400; Fri, 13 Aug 1999 10:07:36 -0700
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-ID:  <199908131707.KAA13400@hsmpka.eng.sun.com>
Date:         Fri, 13 Aug 1999 10:04:23 -0700
Reply-To: Pat.Calhoun@eng.sun.com
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Patrice Calhoun <Pat.Calhoun@eng.sun.com>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Basavaraj Patil <bpatil@nortelnetworks.com>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

>
>>>>>> From: Patrice Calhoun <Pat.Calhoun@eng.sun.com>
>>>>>
>>>>>> I certainly cannot dispute the fact that a full blown PKI has scaling
>>>>>advantages,
>>>>>> but it also has deployment problems. The reality of the fact is that
>the
>>>>>global PKI
>>>>>> is not here yet, and may be here 5+ years from now.
>>>>>
>>>>>
>>>>>  I don't see why the use of public-key style authentication in the
>>>>>  context of Mobile IP has to require a "global PKI". As Steve Kent
>>>>>  has also mentioned several times on the IPSec mailing list, deploying
>>>>>  PKI in a closed system isn't hard (it is more a mental block than
>>>>>  anything else).
>>>>>
>>>>>  Also consider the fact that there are several thousand (if not more)
>>>>>  HTTPS servers operating today using public-key technology.
>>>>>
>>>>>  vipul
>>>>
>>>>Because with the current plans of CDMA deployment, it really isn't a
>>>"closed"
>>>>network.
>>>>
>>>>PatC
>>>
>>>The current CDMA deployment is among a few major service providers
>>>and can be *considered* a "Closed" network for the purpose of
>>>discussion here. The organizations that intend on deploying Mobile IP
>>>need to take a serious look at the option of having a closed PKI
>>>system and the fact that it is very much a feasible solution. I agree
>>>with Vipul's thought here,  that deployment of Mobile IP by a group of
>>>service providers who can agree and thereby have a closed PKI
>>>system. Global roaming in the future will require supporting global
>>>PKI. But by the time we get to that point I believe we will have such
>>>an infrastructure in place.
>>>
>>The current AAA proposals that I've made allow for the broker to
>>issue certificates to all roaming partners, but not in the scale that
>>you are talking about. In fact, no cross-certs are necessary, unless
>>inter-broker mobility is allowed.
>>
>>As I stated earlier, even if that is the case the AAAF/AAAH are still
>needed
>>to make on-the-fly authorization decisions. A certificate alone will not be
>>sufficient for a foreign service provider to provide service to a mobile
>node.
>>
>>PatC
>>
>
>
>Pat,
>
>So the broker is a CA and issues certs to the roaming partners? What I
>am refering to is the case where you have a few service providers who
>agree to cross certify their CAs as a result of roaming agreements
>between them. The PKI managed by a service provider could issue certs
>to the mobility agents. I am not refering to brokers at all. Well I
>guess you could still have a broker concept to minimize the number of
>associations between roaming partners, but in a small subset it does
>not really matter.
>
>In order to provide service to a foreign MN the visiting network needs
>to be assured of receiving payment. Since the FA and HA *may* authenticate
>each other via certs, receiving a successful registration reply should
>be sufficient (in my opinion). What other authorization info (in the
>present context) needs to be provided to the visiting network in order
>to provide service. Of course you will need the capability of
>generating accounting records and that's where the *A* of AAA may fit
>in. Maybe I am missing your point Pat....If I am please clarify.
>

In the current ROAMOPS model, local authentication and authorization is
simply not sufficient. The foreign domains normally wants to get some
assurances that payment will occur as a result of the services offered.

If a foreign network authenticates a user, should it simply assume that
by sending accounting records it will get paid? Not at all. It needs to
get authorization from the home network that it is willing to pay for
the service. Furthermore, the home domain can have additional restrictions
on the service that is to be offered to the mobile node that cannot really
be expressed in the certificate.

All of the work done in ROAMOPS, and the work on the Authorization requirements
have pretty much made this clear in all of their documents. If you are
proposing that roaming using Mobile-IP is vastly different from the
normaly business model in use today, then the WG should make that clear.

PatC


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 14:00:40 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06907
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 14:00:39 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.BDAF2D40@standards.nortelnetworks.com>; Fri, 13 Aug 1999 13:57:11 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 41908 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 13:57:08
          -0400
Received: from auemlsrv.firewall.lucent.com (192.11.223.161) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.BB64A100@standards.nortelnetworks.com>; Fri, 13 Aug 1999
          13:57:07 -0400
Received: from uk0006exch001p.wins.lucent.com (h135-86-160-146.lucent.com
          [135.86.160.146]) by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3)
          with ESMTP id OAA29976 for <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>;
          Fri, 13 Aug 1999 14:00:00 -0400 (EDT)
Received: by uk0006exch001p.uk.lucent.com with Internet Mail Service
          (5.5.2448.0) id <PZYZ0YTJ>; Fri, 13 Aug 1999 18:59:51 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Message-ID:  <976F7C55E3B2D111A0720008C728549C020A4756@en0060exch001u.uk.lucent.com>
Date:         Fri, 13 Aug 1999 18:59:55 +0100
Reply-To: "Casati, Alessio (Alessio)" <acasati@LUCENT.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "Casati, Alessio (Alessio)" <acasati@LUCENT.COM>
Subject:      Re: [MOBILE-IP] Dial-up scenario with Mobile IP - help needed
X-To:         "guilhem.ensuque@BT.COM" <guilhem.ensuque@BT.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

> Is a double authentication needed:
> 1) with PPP/RADIUS to access the link layer
> 2) with the FA to be able to register the FCoA with the HA
>
Although I'm not in the dial-up business, I expect this to
be a healthy procedure. This would allow only authenticated
users to send packets over the PPP link, which operationally
is a valuable thing.

However one may think a close interaction between the FA
logic and the NAS may let to skip the PPP authentication phase.
This may depend on the deployment scenario (for instance, when
only MIP users can possibly dial-up, probably skipping
the PPP authentication phase may be possible).

In the general case, I would say CHAP (EAP) is used for user
authentication after the Link establishment phase.
The AAA protocol used for dial-up may be RADIUS,DIAMETER or whatever.
Then IPCP with MIPv4 option must be used so that MIP capability is detected
and no address is assigned in the IPCP phase in case FA COA is
used.
Here the issue raised by Jonas Malmquist comes into play
(that is the zero Home address is not allowed by RFC2290 and
a zero Home address is what the MN has when it requests a dynamic
Home address assignment). I haven't followed how this ended
and whether a solution now exists.

After the IPCP phase, MIP registration&authentication would happen.

alessio


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 14:05:44 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07155
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 14:05:43 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.0599D240@standards.nortelnetworks.com>; Fri, 13 Aug 1999 13:59:12 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 41888 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 13:58:03
          -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.768EAB80@standards.nortelnetworks.com>; Fri, 13 Aug 1999 13:48:03
          -0400
Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id KAA26119 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Fri, 13 Aug 1999 10:50:57
          -0700 (PDT)
Received: from nobel.eng.sun.com (nobel.Eng.Sun.COM [129.146.122.141]) by
          engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id
          KAA01626; Fri, 13 Aug 1999 10:50:52 -0700 (PDT)
Received: from nobel (nobel [129.146.122.141]) by nobel.eng.sun.com
          (8.9.3+Sun/8.9.3) with SMTP id KAA03325; Fri, 13 Aug 1999 10:41:33
          -0700 (PDT)
X-Sender: vgupta@nobel
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-ID:  <Pine.SOL.3.91.990813102232.3300A-100000@nobel>
Date:         Fri, 13 Aug 1999 10:41:33 -0700
Reply-To: Vipul Gupta <vgupta@ENG.SUN.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Vipul Gupta <vgupta@ENG.SUN.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Patrice Calhoun <Pat.Calhoun@eng.sun.com>
X-cc:         Pat.Calhoun@eng.sun.com, Vipul.Gupta@eng.sun.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <199908130308.UAA01554@hsmpka.eng.sun.com>

On Thu, 12 Aug 1999, Patrice Calhoun wrote:

> The number of relationships in the AAA case is one per peer, in the case of the
> PKI we are talking about a cert for each mobile node and mobility agent. One
> also has to consider the CRL infrastructure that need to be in place to support
> that kind of network.

  In terms of the effort involved, issuing a cert for each mobile node or
  agent doesn't seem all that different from setting up a secret key between
  that entity and its AAA. All certs need not be issued by the same CA, so
  for example, each carrier could choose to have its own CA that issues
  certs for its mobile users and mobility agents. Direct or indirect
  (through a broker) roaming agreements can be used to maintain the
  necessary certification paths. The PKIX working group has developed an
  Online Certificate Status Protocol - OCSP (RFC 2560) which eliminates
  the need for CRLs and can be used in the manner you describe below.

  vipul

> I could be wrong but setting up a relationship with a broker, and getting a single
> cert for the AAA server seems much less complex. Furthermore, no CRL is required since
> the broker participates in the AA/A, and therefore would deny any requests for/from
> an ISP/corporate customer that is no longer part of the consortium.
>
> PatC
> >
> >  vipul
> >
> >
>
>
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 15:02:14 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08656
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 15:02:14 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.542C7090@standards.nortelnetworks.com>; Fri, 13 Aug 1999 14:58:40 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 42271 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 14:58:02
          -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.3D7095C0@standards.nortelnetworks.com>; Fri, 13 Aug 1999
          14:58:02 -0400
Received: from zrchh190 by smtprch1.nortel.com; Fri, 13 Aug 1999 13:52:50 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Fri, 13
          Aug 1999 14:04:35 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <QZ38RFJA>; Fri, 13 Aug 1999 13:59:55 -0500
X-Mailer: Internet Mail Service (5.5.2448.0)
X-Orig: <bpatil@americasm01.nt.com>
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
X-Orig: <bpatil@americasm01.nt.com>
Message-ID:  <61DEB565F616D31187880000F805A8D5817E97@crchy270.us.nortel.com>
Date:         Fri, 13 Aug 1999 13:59:53 -0500
Reply-To: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         "Pat.Calhoun" <Pat.Calhoun@eng.sun.com>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

----snip snip----------

>>>>The current CDMA deployment is among a few major service providers
>>>>and can be *considered* a "Closed" network for the purpose of
>>>>discussion here. The organizations that intend on deploying Mobile IP
>>>>need to take a serious look at the option of having a closed PKI
>>>>system and the fact that it is very much a feasible solution. I agree
>>>>with Vipul's thought here,  that deployment of Mobile IP by a group of
>>>>service providers who can agree and thereby have a closed PKI
>>>>system. Global roaming in the future will require supporting global
>>>>PKI. But by the time we get to that point I believe we will have such
>>>>an infrastructure in place.
>>>>
>>>The current AAA proposals that I've made allow for the broker to
>>>issue certificates to all roaming partners, but not in the scale that
>>>you are talking about. In fact, no cross-certs are necessary, unless
>>>inter-broker mobility is allowed.
>>>
>>>As I stated earlier, even if that is the case the AAAF/AAAH are still
>>needed
>>>to make on-the-fly authorization decisions. A certificate alone will not
be
>>>sufficient for a foreign service provider to provide service to a mobile
>>node.
>>>
>>>PatC
>>>
>>
>>
>>Pat,
>>
>>So the broker is a CA and issues certs to the roaming partners? What I
>>am refering to is the case where you have a few service providers who
>>agree to cross certify their CAs as a result of roaming agreements
>>between them. The PKI managed by a service provider could issue certs
>>to the mobility agents. I am not refering to brokers at all. Well I
>>guess you could still have a broker concept to minimize the number of
>>associations between roaming partners, but in a small subset it does
>>not really matter.
>>
>>In order to provide service to a foreign MN the visiting network needs
>>to be assured of receiving payment. Since the FA and HA *may* authenticate
>>each other via certs, receiving a successful registration reply should
>>be sufficient (in my opinion). What other authorization info (in the
>>present context) needs to be provided to the visiting network in order
>>to provide service. Of course you will need the capability of
>>generating accounting records and that's where the *A* of AAA may fit
>>in. Maybe I am missing your point Pat....If I am please clarify.
>>

>In the current ROAMOPS model, local authentication and authorization is
>simply not sufficient. The foreign domains normally wants to get some
>assurances that payment will occur as a result of the services offered.

I did not intend to say that authentication and authorization be done
locally.
Authentication is still being done by the home network and the
assurance that the foreign domain needs for services offered is
received in the form of a succesful registration resonse message. The
reason that the foreign domain trusts this response message is because
of it's ability to authenticate this message (roaming agreement
between the foreign and home network and the existence of a PKI in
these networks.......previous discussion).

>If a foreign network authenticates a user, should it simply assume that
>by sending accounting records it will get paid? Not at all. It needs to
>get authorization from the home network that it is willing to pay for
>the service. Furthermore, the home domain can have additional restrictions
>on the service that is to be offered to the mobile node that cannot really
>be expressed in the certificate.

Refer to the comments above (the foreign network is not the one
authenticating the user). Services and authorization for what services
a Mobile user can avail of in a foreign/visited domain is definitely
not going to be expressed in a certificate. If you look at the
cellular model the foreign domain (VLR) receives a version of the Mobile
users profile from the HLR which allows the visited network to
determine what services the user is authorized for. My point is that I
am not expecting authorization for services to be "expressed in a
certificate".

>All of the work done in ROAMOPS, and the work on the Authorization
>requirements have pretty much made this clear in all of their
>documents. If you are proposing that roaming using Mobile-IP is vastly
>different from the normaly business model in use today, then the WG
>should make that clear.
>
>PatC
>

The roaming model for Mobile IP is not (need not be) any different
than what is currently in existence today or has been proposed by
ROAMOPS. I think we were discussing the same problem with  different
contexts here.

-Raj


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 13 22:35:39 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14691
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 13 Aug 1999 22:35:38 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.A7BE2ED0@standards.nortelnetworks.com>; Fri, 13 Aug 1999 22:31:58 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 43335 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 13 Aug 1999 22:30:06
          -0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.FDDE2290@standards.nortelnetworks.com>; Fri, 13 Aug 1999 22:20:04
          -0400
Received: from ebiz1234cash (HSE-TOR-ppp48570.sympatico.ca [204.101.17.207]) by
          hosaka.smallworks.com (8.9.1/8.9.1) with SMTP id VAA03231; Fri, 13
          Aug 1999 21:22:51 -0500 (CDT)
Message-ID:  <337.400512.225817@ebiz1234cash>
Date:         Fri, 13 Aug 1999 22:30:06 -0400
Reply-To: ebiz@ONRAMP.CA
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: ebiz@ONRAMP.CA
Subject:      [MOBILE-IP] EBIZ = 1,2,3...4 CASH
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

This is a one time mailing.  My apologies if it reached you by
error.


To be removed from future mailings (see last paragraph for
details), reply to ebiz@onramp.ca.  In the subject write REMOVE.
This is it folks.
This is the letter you've been reading about in the news lately.
 Due to the popularity of this letter on the Internet, a major
nightly news program recently devoted an entire show to the
investigation of the program described below , to see if it
really can make people money. If you saw it, you know that their
conclusion was ,that while most people did not make the $55,000,
as discussed in the plan, EVERYONE who followed the instructions
was able to make 100 to 160 times their money at the VERY LEAST.
The show also investigated whether or not the program was legal.
 Their findings proved once and for all that there are absolutely
no laws prohibiting the participation in the program.  "This is
one of the most exciting opportunities with the MOST income
potential on the internet today!" --48 Hours..

Is it legal? - Yes, (Refer to title 18, Section 1302 & 1342 of
the U.S. Postal and Lottery Laws)
This opportunity isn't much of a risk and could turn out to
actually be a bit of fun.
Bottom Line;
The risk is only $20 and time on the Internet.


The following is a copy of the letter that the media was
referring to:

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

This is a LEGAL, MONEY-MAKING PHENOMENON.
PRINT this letter, READ the directions, THEN READ IT AGAIN !!!



You are about to embark on the most profitable and unique program
you may ever see. Many times over, it has demonstrated and proven
its ability to generate large amounts of cash. This program is
showing fantastic appeal with a huge and ever-growing on-line
population desirous of additional income.

This is a legitimate, LEGAL, money-making opportunity. It does
not require you to come in personal contact with people, do any
hard work, and best of all, you never have to leave the house,
except to get the mail and go to the bank!
This truly is that lucky break you've been waiting for! Simply
follow the easy instructions in this letter, and your financial
dreams can come true! When followed correctly, this electronic,
multi-level marketing program WORKS!
Thousands of people have used this program to:
· Raise capital to start their own business
· Pay off debts
· Buy homes, cars, etc.,
· Even retire!
This is your chance, Don't pass it up!


OVERVIEW OF THIS EXTRAORDINARY
ELECTRONIC MULTI-LEVEL MARKETING PROGRAM


Basically, this is what we do:
We send thousands of people a product that they paid us $5.00 US
for, that costs next to nothing to produce and e-mail back to
them. As with all multi-level businesses, we build our business
by recruiting new partners and selling our products. Every state
in the U.S. allows you to recruit new multi- level business
online (via your computer).
The products in this program are a series of four business and
financial reports costing $5.00 each. Each order you receive is
to include:
· $5.00 cash United States Currency
· The name and number of the report they are ordering
· The e-mail address where you will e-mail them the report they
ordered.

To fill each order, you simply e-mail the product to the buyer.
THAT'S IT! The $5.00 is yours! This is the EASIEST electronic
multi-level marketing business anywhere!

FOLLOW THE INSTRUCTIONS TO THE LETTER AND BE PREPARED TO REAP THE
STAGGERING BENEFITS!
+++++++++ I N S T R U C T I O N S +++++++++

This is what you MUST do:
1. Order all 4 reports shown on the list below (you can't sell
them if you don't order them).
· For each report, send $5.00 CASH, the NAME & NUMBER OF
THE REPORT YOU ARE ORDERING, YOUR E-MAIL ADDRESS,
and YOUR RETURN POSTAL ADDRESS (in case of a problem) to the
person whose name appears on the list next to the report.
· When you place your order, make sure you order each of the four
reports. You will need all four reports so that you can save them
on your computer and resell them.
· Within a few days you are to receive, via e-mail, each of the
four reports.
Save them on your computer so they will be accessible for you to
send to the 1,000's of people who will order them from you.
2.      IMPORTANT-DO NOT alter the names of the people who are
listed next to each report, or their sequence on the list, in any
way other than is instructed below in steps "a" through "d" or
you will lose out on the majority of your profits. Once you
understand the way this works, you'll also see how it doesn't
work if you change it. Remember, this method has been tested, and
if you alter it, it will not work.

a. Look below for the listing of available reports.
b. After you've ordered the four reports, replace the name and
address under REPORT #1 with your name and address, moving the
one that was there down to REPORT #2.
c. Move the name and address that was under REPORT #2 down to
REPORT #3
d. Move the name and address that was under REPORT #3 down to
REPORT#4
e. The name and address that was under REPORT #4 is removed from
the list and has NO DOUBT collected large sums of cash!

Please make sure you copy everyone's name and address
ACCURATELY!!!
3.      Take this entire letter, including the modified list of
names, and save it to your computer. Make NO changes to the
instruction portion of this letter.
4.      Now you're ready to start an advertising campaign on the
WORLDWIDE WEB! Advertising on the WEB can be very, very
inexpensive, and there are HUNDREDS of FREE places to advertise.
Another avenue which you could use for advertising is e-mail
lists. You can buy these lists for under $20/2,000 addresses or
you can pay someone to take care of it for you.
BE SURE TO START YOUR AD CAMPAIGN IMMEDIATELY!
5.      For every $5.00 you receive, all you must do is e-mail
them the report they ordered. THAT'S IT! ALWAYS PROVIDE SAME-DAY
SERVICE ON ALL
ORDERS! This will help guarantee that the e-mail THEY send out,
with YOUR name and address on it, will be prompt because they
can't advertise until they receive the report! To grow fast be
prompt and courteous.
AVAILABLE REPORTS

**Order Each REPORT by NUMBER and NAME**
Notes:
· ALWAYS SEND $5 CASH FOR EACH REPORT
· ALWAYS SEND YOUR ORDER VIA THE QUICKEST
DELIVERY
· Make sure the cash is concealed by wrapping it in at least two
sheets of paper
· On one of those sheets of paper, include: (a) the number & name
of the report you are ordering, (b) your e-mail address, and (c)
your postal address.

REPORT #1 "The Insider's Guide to Advertising for Free on the
Internet"
ORDER REPORT #1 FROM:
EBIZ
PH2 - 45 Grenoble Dr.
Toronto, ON   M3C 1C5
Canada

REPORT #2 "The Insider's Guide to Sending Bulk E-mail on the
Internet"
ORDER REPORT #2 FROM:
C. Alexander
2315 Lava Dr.
San Jose, CA 95133


REPORT #3 "The Secrets to Multilevel Marketing on the Internet"
ORDER REPORT #3 FROM:
P.G. Webb
16 Huntley Crescent
St. Catharines, Ontario
Canada, L2M 6E7

REPORT #4 "How to become a Millionaire utilizing the Power of
Multilevel Marketing and the Internet"
ORDER REPORT #4 FROM:
F.D. Hardy
22306 128th. ST. E.
Sumner, Wa. 98390-7634



HERE'S HOW THIS AMAZING PLAN WILL MAKE YOU $MONEY$


Let's say you decide to start small just to see how well it
works. Assume your goal is to get 10 people to participate on
your first level. (Placing a lot of FREE ads on the internet will
EASILY get a larger response.) Also assume that everyone else in
YOUR ORGANIZATION gets ONLY 10 downline members.  Follow this
example to achieve the STAGGERING results below.
1st level-your 10 members with
$5...........................................$50
2nd level--10 members from those 10 ($5 x
100)..................$500
3rd level--10 members from those 100 ($5 x 1,000)..........$5,000
4th level--10 members from those 1,000 ($5 x 10,000)...$50,000
THIS TOTALS ----------->$55,550
Remember friends, this assumes that the people who participate
only recruit 10 people each. Think for a moment what would happen
if they got 20 people to participate! Lots of people get 100s of
participants! THINK ABOUT IT!
Your cost to participate in this is practically nothing (surely
you can afford $20). You obviously already have an internet
connection and e-mail is FREE!!! REPORT#3 shows you the most
productive methods for bulk e-mailing and purchasing e-mail
lists. Some list & bulk e-mail vendors even work on trade!
About 67,000 new people get online every month


****TIPS FOR SUCCESS****
· TREAT THIS AS YOUR BUSINESS! Be prompt, professional, and
follow the directions accurately.
· Send for the four reports IMMEDIATELY so you will have them
when the orders start coming in because:
When you receive a $5 order, you MUST send out the requested
product/report to comply with the U.S. Postal & Lottery Laws,
Title 18,Sections 1302 and 1341 or Title 18, Section 3005 in the
U.S. Code also Code of Federal Regs. vol. 16, Sections 255 and
436, which state that "a product or service must be exchanged for
money received."
· ALWAYS PROVIDE SAME-DAY SERVICE ON THE ORDERS YOU RECEIVE.
· Be patient and persistent with this program. If you follow the
instructions exactly, the results WILL undoubtedly be SUCCESSFUL!
· ABOVE ALL, HAVE FAITH IN YOURSELF AND KNOW YOU WILL SUCCEED!


********************YOUR SUCCESS GUIDELINE********************


Follow these guidelines to help assure your success:
If you don't receive 10 to 20 orders for REPORT #1 within two
weeks, continue advertising until you do. Then, a couple of weeks
later you should receive at least 50 orders for REPORT #2. If you
don't, continue advertising until you do. Once you have received
50 or more orders for REPORT #2, YOU CAN RELAX, because the
system is already working for you, and the cash can continue to
roll in!
THIS IS IMPORTANT TO REMEMBER:
Every time your name is moved down on the list, you are placed in
front of a DIFFERENT report. You can KEEP TRACK of your PROGRESS
by watching which report people are ordering from you. If you
want to generate more income, send another batch of e-mails and
start the whole process again! There is no limit to the income
you will generate from this business!
NOTE: If you need help with starting a business, registering a
business name, how income tax is handled, etc., contact your
local office of the Small Business Administration (a Federal
agency) for free help and answers to questions. Also, the
Internal Revenue Service offers free help via telephone and free
seminars about business taxes. If you have any question of the
legality of this letter contact the Office of Associate Director
for Marketing Pratices Federal Trade Commission Bureau of
Consumer Protection in Washington DC.


**T E S T I M O N I A L S**


This program does work, but you must follow it EXACTLY!
Especially the rule of not trying to place your name in a
different position, it won't work and you'll lose a lot of
potential income. I'm living proof that it works. It really is a
great opportunity to make relatively easy money, with little cost
to you. If you do choose to participate, follow the program
exactly, and you'll be on your way to financial security.
Sean McLaughlin, Jackson, MS
The main reason for this letter is to convince you that this
system is honest, lawful, extremely profitable, and is a way to
get a large amount of money in a short time. I was approached
several times before I checked this out. I joined just to see
what one could expect in return for the minimal effort and money
required. To my astonishment, I received $36,470.00 in the first
19 weeks, with money still coming in.
Sincerely yours, Phillip A. Brown, Esq.
I had received this program before. I deleted it, but later I
wondered if I shouldn't have given it a try. Of course, I had no
idea who to contact to get another copy, so I had to wait until I
was e-mailed another program...11 months passed then it came...I
didn'tdelete this one!...I made more than $41,000 on the first
try!!
D. Wilburn, Muncie, IN
This is my third time to participate in this plan. We have quit
our jobs, and will soon buy a home on the beach and live off the
interest on our money. The only way on earth that this plan will
work for you is if you do it. For your sake, and for your
family's sake don't pass up this golden opportunity. Good luck
and happy spending!
Charles Fairchild, Spokane, WA
I am nearing the $90,000 mark from this program.I have used
several forms of advertisement.I used regular mail and bulk
e-mail. The regular mail that I used was very expensive for two
reasons. I purchased a very select list of names and the postage.
The third time I sent e-mails out,I did so in the quantity of 1
million. So, after 3 times participating in this program I am
almost at the $90,000 mark. That isn't too bad. I hope the same
success for you. .
Good Luck.
Raymond McCormick, New Cannan, Ct.
You have great potential for extra earnings that is available at
your finger-tips! You have unlimited access to wealth, but you
must be willing to take that first step! The Media ALREADY PROVED
That !!!!
You could be making an obscene amount of money!

I have given you the information, materials, and opportunity to
become financially better off. IT IS UP TO YOU NOW!- THINK ABOUT
IT -

Your risk is only $20.? HOW MUCH DO YOU SPEND ON LOTTO TICKETS-
for NO RETURN?

ORDER YOUR REPORTS TODAY AND GET STARTED ON YOUR ROAD TO
FINANCIAL FREEDOM!!!

Under Bill S.1618 TITLE III passed by the U.S. Congress this
letter can not be considered spam as long as we include the way
to be removed. To be removed from future mailings for free just
click on the hyperlink at the top of this page and put the title
"REMOVE" in the subject line. This will permanently remove you
from all future mailing. All future mailings from other e-mail
addresses must be dealt with separately.


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Sat Aug 14 21:25:57 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05625
	for <mobileip-archive@LISTS.IETF.ORG>; Sat, 14 Aug 1999 21:25:56 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.111CC4D0@standards.nortelnetworks.com>; Sat, 14 Aug 1999 21:22:09 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 44277 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Sat, 14 Aug 1999 21:20:32
          -0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.71B49F40@standards.nortelnetworks.com>; Sat, 14 Aug 1999 21:10:32
          -0400
Received: from imo18.mx.aol.com (imo18.mx.aol.com [198.81.17.8]) by
          hosaka.smallworks.com (8.9.1/8.9.1) with ESMTP id UAA11165 for
          <mobile-ip@smallworks.com>; Sat, 14 Aug 1999 20:13:26 -0500 (CDT)
Received: from Airman012@aol.com by imo18.mx.aol.com (mail_out_v22.4.) id
          dJKKa02415 (4205); Sat, 14 Aug 1999 20:33:53 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 3.0 for Windows 95 sub 62
Message-ID:  <ab53e135.24e764f0@aol.com>
Date:         Sat, 14 Aug 1999 20:33:52 EDT
Reply-To: Airman012@AOL.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
Comments:     RFC822 error: <W> Incorrect or incomplete address field found and
              ignored.
From: Airman012@AOL.COM
Subject:      [MOBILE-IP] >>> WARNING Members, Don't Get Ripped Off !!! <<<
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

>>> WARNING Members, Don't Get Ripped Off !!! <<<

/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/
 Volume 4 - Issue 8  Subscriber Count: 28,787

 PLEASE NOTE:  This E-Zine is sent to subscribers only.
 To UNSUBSCRIBE, please call 1-800-242-0363 Ext 1940
/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/

There are some dishonest people who have copied this advertisement in
an attempt to sell their own "cheap imitation" of the Internet Spy & You
program.

Don't be misled by other $15 and $22 programs being advertised on
the net... you get what you pay for, and there's only ONE "Internet Spy
& You" program!!!
****************************************************************************
Dear E-Zine Subscriber,

This special software offer will expire August 21st !!!

Don't miss this very limited time opportunity to get the software that
will allow you to become the ultimate "Super Snoop" on anyone !!!

Get The SOFTWARE They Want BANNED In All COUNTRIES!!!

"THE INTERNET SPY AND YOU"  SHOWS YOU
      HOW TO GET THE FACTS ON ANYONE!!!

You now have just 10 days left to get the software they want
banned in every country !!!  Why?  Because these secrets were never
intended to reach your eyes... Plus, this is a VERY LIMITED TIME OFFER!!!

Get the facts on anyone using the Internet!

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 daughters boyfriend!
(or her husband)

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, 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 the Internet Spy
and You and the Internet!  You'll be riveted to your computer screen!
Get the software they're trying to ban!

ACT NOW, Before it's too late!

LIMITED TIME OFFER -- THIS SPECIAL SOFTWARE OFFER EXPIRES
AUGUST 21st !!!  ORDER TODAY!!!

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 !!!

(ORDERS OUTSIDE THE USA, ADD $10.00)

(ALL SOFTWARE PACKAGES SHIPPED WITHIN 48 HOURS)

>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<
We have 100 licenses/copies of this program.  This offer may
be discontinued without notice.  Orders received or postmarked
AFTER 08/21/99, will be returned.  Sorry, there will be NO
exceptions!!!
>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<

DON'T WAIT TO GET STARTED... here's what to do:

**                         >>> Mail or Fax Order Form <<<
**
**             The Internet Spy & You Software  [Reg. Ver. 7.06]
**
**    E-Zine Subscribers order today to save more than 40% off the original
price!!!
**                             Only $45.95  (Regular price $79.95)
**
**    Enclosed is ____  $ 45.95 or
**                         ____  $ 48.87 (UT customers add 6.35% sales tax)
**
**   Yes, I am paying with Cash or Money Order, please take an additional
**   13% off this special offer price.
**    Enclosed is ____ $ 39.95 in the form of Cash or Money Order.
**                         ____ $ 42.49 (UT customers add 6.35% sales tax)
**
**       (Please add $7.00 to receive a MAC VERSION of this software.)
**
**    Sorry, we do not accept personal or business checks.
**
**    Your Ordering Options: (Choose one only.)
**
**    1) Print this complete order form then fax your credit card order:
(209) 796-9629
**
**    2) Send your payment and order form to:
**                                      Langton & Associates
**                                  1052 South Navajo Street
**                                        SLC,  Utah  84104
**
**    Authorization Code:  A1E
**
**    Your Name:      _________________________________________
**
**    Your Address:  _________________________________________
**
**    City:  _________________  State: __________  Zip ___________
**
**    Your E-mail Address: __________________________________
**    [   ] PC Version    [   ] Mac Version (please add $7.00 for Mac)
**
**    Method of payment:  [   ] Visa [   ] MasterCard [   ] American Express
**    Credit Card#:
**    Exp Date:
**    YOUR SIGNATURE HERE:_______________________________
**    We cannot process your credit card payment without your signature!

"Products & Services For Doing Business On The Net"

NOTE: THIS PROGRAM WILL NOT WORK ON WINDOWS 3.11 AND OLDER

REFUNDS:  Since this is "information" on disk, we cannot issue a refund
after your order is shipped, only a replacement if necessary.

DISCLAIMER:  The seller of this powerful software resource will not be
held responsible for how the purchaser chooses to use its resources.

******************************************************************************
**********

This mailing is done by an independent marketing company.  We apologize
if this message has reached you in error.  Save the Planet, Save the
Trees!
Advertise via E-mail.  No wasted paper!

This E-Zine is sent to subscribers only.  To UNSUBSCRIBE, please call
1-800-242-0363 Ext 1940 and we'll promptly honor your remove request.
















o-ge4afe-c1-8_49


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 16 03:46:25 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16675
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 16 Aug 1999 03:46:25 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.58A14890@standards.nortelnetworks.com>; Mon, 16 Aug 1999 3:42:21 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 45127 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 16 Aug 1999 03:41:00
          -0400
Received: from mailgate.rz.uni-karlsruhe.de (129.13.197.4) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.C2763FC0@standards.nortelnetworks.com>; Mon, 16 Aug 1999
          3:31:00 -0400
Received: from tp70.rz.uni-karlsruhe.de (exim@tp70.rz.uni-karlsruhe.de
          [129.13.98.225]) by mailgate.rz.uni-karlsruhe.de with esmtp (Exim
          3.02 #2) id 11GHH3-0004FK-00; Mon, 16 Aug 1999 09:33:41 +0200
Received: from ry85 (helo=localhost) by tp70.rz.uni-karlsruhe.de with
          local-smtp (Exim 2.12 #1) id 11GHH2-0005Zp-00; Mon, 16 Aug 1999
          09:33:40 +0200
X-Sender: ry85@tp70.rz.uni-karlsruhe.de
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-ID:  <Pine.HPP.3.96.990816093141.21437A-100000@tp70.rz.uni-karlsruhe.de>
Date:         Mon, 16 Aug 1999 09:33:40 +0200
Reply-To: Stefan Mink <stefan@RZ.UNI-KARLSRUHE.DE>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Stefan Mink <stefan@RZ.UNI-KARLSRUHE.DE>
Subject:      Re: [MOBILE-IP] QoS [diff-serv or int-serv/RSVP]
X-To:         Guilhem Tardy <Guilhem.Tardy@CRC.CA>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <37B438B7.C0CD57C0@crc.ca>

On Fri, 13 Aug 1999, Guilhem Tardy wrote:

> Hi!
>
> I am looking into the QoS stuff... do you have some links about what's
> underway about it within MOBIP?

the same with me; if there are some papers about this, I'd be glad to
know where I can get them.

   tschuess
             Stefan Mink

PS: Of course I'd be glad to hear about your work too, Guilhem :)

eMail: stefan@rz.uni-karlsruhe.de


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 16 04:28:10 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16910
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 16 Aug 1999 04:28:10 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.3882DFF0@standards.nortelnetworks.com>; Mon, 16 Aug 1999 4:24:24 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 45166 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 16 Aug 1999 04:23:19
          -0400
Received: from babelfish.axion.bt.co.uk by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.114D7DA0@standards.nortelnetworks.com>; Mon, 16 Aug 1999 4:23:18
          -0400
Received: from cbtlipnt01.btlabs.bt.co.uk by babelfish.axion.bt.co.uk (local)
          with ESMTP; Mon, 16 Aug 1999 09:25:20 +0100
Received: by cbtlipnt01.btlabs.bt.co.uk with Internet Mail Service (5.5.2448.0)
          id <QL8DYGL1>; Mon, 16 Aug 1999 09:25:18 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Message-ID:  <5104D4DBC598D211B5FE0000F8FE7EB202432749@mbtlipnt02.btlabs.bt.co.uk>
Date:         Mon, 16 Aug 1999 09:25:05 +0100
Reply-To: guilhem.ensuque@BT.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "G. Ensuque" <guilhem.ensuque@BT.COM>
Subject:      [MOBILE-IP] QoS and MIP
X-To:         stefan@RZ.UNI-KARLSRUHE.DE
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi all

I guess the following would be a good start:

draft-kim0mobile-diff-00
'Mobility support in the Differentiated Services'

draft-fhns-rsvp-support-in-mipv6-00
'RSVP support for Mobile IP version 6 in Wireless Enbironments'

I haven't read them though and they are maybe expired...

regards

Guilhem Ensuque
(the OTHER Guilhem)

Mobility Futures Unit                           guilhem.ensuque@bt.com
B55-131B
BT Advanced Communications Technology Centre
Adastral Park, Martlesham Heath
IPSWICH IP5 3RE                              Tel: +44 1473 645 232
UK                                                   Fax: +44 1473 646 885


> -----Original Message-----
> From: Stefan Mink [SMTP:stefan@RZ.UNI-KARLSRUHE.DE]
> Sent: 16 August 1999 08:34
> To:   MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
> Subject:      Re: [MOBILE-IP] QoS [diff-serv or int-serv/RSVP]
>
> On Fri, 13 Aug 1999, Guilhem Tardy wrote:
>
> > Hi!
> >
> > I am looking into the QoS stuff... do you have some links about what's
> > underway about it within MOBIP?
>
> the same with me; if there are some papers about this, I'd be glad to
> know where I can get them.
>
>    tschuess
>              Stefan Mink
>
> PS: Of course I'd be glad to hear about your work too, Guilhem :)
>
> eMail: stefan@rz.uni-karlsruhe.de


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 16 04:44:05 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17057
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 16 Aug 1999 04:44:05 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.762B4250@standards.nortelnetworks.com>; Mon, 16 Aug 1999 4:40:27 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 45198 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 16 Aug 1999 04:39:09
          -0400
Received: from arthur.axion.bt.co.uk by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.47AD6750@standards.nortelnetworks.com>; Mon, 16 Aug 1999 4:39:09
          -0400
Received: from cbtlipnt01.btlabs.bt.co.uk by arthur (local) with ESMTP; Mon, 16
          Aug 1999 09:40:13 +0100
Received: by cbtlipnt01.btlabs.bt.co.uk with Internet Mail Service (5.5.2448.0)
          id <QL8DYGSW>; Mon, 16 Aug 1999 09:39:25 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Message-ID:  <5104D4DBC598D211B5FE0000F8FE7EB20243274A@mbtlipnt02.btlabs.bt.co.uk>
Date:         Mon, 16 Aug 1999 09:39:13 +0100
Reply-To: guilhem.ensuque@BT.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "G. Ensuque" <guilhem.ensuque@BT.COM>
Subject:      [MOBILE-IP] Status of 'original' mobility drafts
X-To:         stefan@RZ.UNI-KARLSRUHE.DE
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi all

I have done a keyword I-D search for 'mobile', and quite a few drafts
appeared that I have never heard of (maybe it's my fault because I haven't
attended any IETF meeting).

Can someone (maybe the authors themselves ?) tell me what the status is
regarding the following drafts:

draft-chuafoo-mobileip-rafa-00
'regional Aware Foreign Agent (RAFA) for Fast Local Handoffs'

draft-bush-ncp-config-01
network control protocol for the configuration of mobile wireless ...

draft-jawanda-sdow-00
mobile service discovery over wireless links (sdow)

draft-chambless-mobileip-harp-00
'HARP - Home agent redundancy protocol

draft-shen-mobileip-ipv6-ha-discov-00
enhancements to dynamic home agent discovery


Thanks in advance

Guilhem Ensuque

Mobility Futures Unit                           guilhem.ensuque@bt.com
B55-131B
BT Advanced Communications Technology Centre
Adastral Park, Martlesham Heath
IPSWICH IP5 3RE                              Tel: +44 1473 645 232
UK                                                   Fax: +44 1473 646 885




> -----Original Message-----
> From: Stefan Mink [SMTP:stefan@RZ.UNI-KARLSRUHE.DE]
> Sent: 16 August 1999 08:34
> To:   MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
> Subject:      Re: [MOBILE-IP] QoS [diff-serv or int-serv/RSVP]
>
> On Fri, 13 Aug 1999, Guilhem Tardy wrote:
>
> > Hi!
> >
> > I am looking into the QoS stuff... do you have some links about what's
> > underway about it within MOBIP?
>
> the same with me; if there are some papers about this, I'd be glad to
> know where I can get them.
>
>    tschuess
>              Stefan Mink
>
> PS: Of course I'd be glad to hear about your work too, Guilhem :)
>
> eMail: stefan@rz.uni-karlsruhe.de


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 16 04:50:03 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17102
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 16 Aug 1999 04:50:03 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.4E294BC0@standards.nortelnetworks.com>; Mon, 16 Aug 1999 4:46:29 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 45231 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 16 Aug 1999 04:44:33
          -0400
Received: from arthur.axion.bt.co.uk by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.08DA1220@standards.nortelnetworks.com>; Mon, 16 Aug 1999 4:44:33
          -0400
Received: from cbtlipnt02.btlabs.bt.co.uk by arthur (local) with ESMTP; Mon, 16
          Aug 1999 09:46:08 +0100
Received: by cbtlipnt02.btlabs.bt.co.uk with Internet Mail Service (5.5.2448.0)
          id <QWTKQCQD>; Mon, 16 Aug 1999 09:46:00 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Message-ID:  <5104D4DBC598D211B5FE0000F8FE7EB20243274B@mbtlipnt02.btlabs.bt.co.uk>
Date:         Mon, 16 Aug 1999 09:46:02 +0100
Reply-To: guilhem.ensuque@BT.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "G. Ensuque" <guilhem.ensuque@BT.COM>
Subject:      [MOBILE-IP] Wanted: old hierarchical FA draft
X-To:         stefan@RZ.UNI-KARLSRUHE.DE
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi all again

I would be extremely grateful if someone could send me the now expired draft
by Charlie Perkins on Hierarchical Foreign Agents
(draft-ietf-mobileip-hierfa-00) as I cannot

Thanks in advance

Guilhem Ensuque

Mobility Futures Unit                           guilhem.ensuque@bt.com
B55-131B
BT Advanced Communications Technology Centre
Adastral Park, Martlesham Heath
IPSWICH IP5 3RE                              Tel: +44 1473 645 232
UK                                                   Fax: +44 1473 646 885


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 16 05:07:10 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17208
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 16 Aug 1999 05:07:10 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.B0690D00@standards.nortelnetworks.com>; Mon, 16 Aug 1999 5:03:33 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 45280 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 16 Aug 1999 05:02:35
          -0400
Received: from dent.axion.bt.co.uk by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.8D968FA0@standards.nortelnetworks.com>; Mon, 16 Aug 1999 5:02:34
          -0400
Received: from cbtlipnt02.btlabs.bt.co.uk by dent (local) with ESMTP; Mon, 16
          Aug 1999 09:55:12 +0100
Received: by cbtlipnt02.btlabs.bt.co.uk with Internet Mail Service (5.5.2448.0)
          id <QWTKQCV2>; Mon, 16 Aug 1999 09:54:45 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Message-ID:  <5104D4DBC598D211B5FE0000F8FE7EB20243274C@mbtlipnt02.btlabs.bt.co.uk>
Date:         Mon, 16 Aug 1999 09:54:47 +0100
Reply-To: guilhem.ensuque@BT.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "G. Ensuque" <guilhem.ensuque@BT.COM>
Subject:      [MOBILE-IP] Darwinian evolution of proxy tunnelling...
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi all

This is just to test my understanding: could the insiders correct me if I am
wrong...

Am I right to assume the following Darwinian evolution path for the idea of
having 'daisy-chained' tunnels through proxies?

Hierarchical FA --> TEP --> regionalized tunnel mgt --> THEMA

Thanks

Guilhem
(the other one)

BT Labs


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 16 05:47:26 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17457
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 16 Aug 1999 05:47:26 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.49D624A0@standards.nortelnetworks.com>; Mon, 16 Aug 1999 5:43:38 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 45335 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 16 Aug 1999 05:41:40
          -0400
Received: from exs24.ex.nus.edu.sg by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.FFE612B0@standards.nortelnetworks.com>; Mon, 16 Aug 1999 5:41:34
          -0400
Received: by EXS24 with Internet Mail Service (5.5.2448.0) id <QN4NH3AV>; Mon,
          16 Aug 1999 17:45:25 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <DABFA252A5A2D1118ADB00805FBED9C502D2AB2B@exs23.ex.nus.edu.sg>
Date:         Mon, 16 Aug 1999 17:45:23 +0800
Reply-To: Gao Qing <engp8682@NUS.EDU.SG>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gao Qing <engp8682@NUS.EDU.SG>
Subject:      Re: [MOBILE-IP] routing optimization authentication
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

-----Original Message-----
From: Patrice Calhoun [mailto:Pat.Calhoun@ENG.SUN.COM]
Sent: Thursday, August 12, 1999 2:08 PM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Subject: Re: [MOBILE-IP] routing optimization authentication

>Lastly, your comment about MN-FA authentication not being necessary raises
an issue. My
>feeling was that local hand-off could be performed by allowing the Foreign
Agents to
>authenticate the Mobile Node, without having to inform the home agent. Of
course I am
>implying a hierarchical network here, and the movement is within a local
network.
>If the MN-FA does not exist, then how could a Foreign-Agent securely handle
hand-offs?

>PatC

When assuming a hierarchical network, I agree with you. This architecture
implys
that FA is a trusted part of the local access network and FA has an SA with
HA.

However, when there is no such hierarchical network, for example, in the
internet,
the FA is NOT previously trusted by either the access network or the HA (no
roaming
agreement established in advance). In this senario, the FA acts passively.
Once it has seen the successful registration reply from the HA (implying
the HA successfully authenticated the MN and the FA) and has authenticated
the
HA successfully, the FA can derive that FA implicitly authenticated(thus can
trust)
MN counting on the HA. And once the MN has seen the successful
registration reply from the FA, it can derive that MN implicitly
authenticated(thus can
trust) FA counting on the HA.

By performing asymmetric HA-FA authentication, at least we can be sure that
an
hostile FA can not deny in the future what he had done.

Qing


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 16 06:09:29 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17785
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 16 Aug 1999 06:09:29 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.5E7FE0F0@standards.nortelnetworks.com>; Mon, 16 Aug 1999 6:05:41 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 45374 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 16 Aug 1999 06:04:52
          -0400
Received: from exs24.ex.nus.edu.sg by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.41038220@standards.nortelnetworks.com>; Mon, 16 Aug 1999 6:04:51
          -0400
Received: by EXS24 with Internet Mail Service (5.5.2448.0) id <QN4NH3GW>; Mon,
          16 Aug 1999 18:08:46 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <DABFA252A5A2D1118ADB00805FBED9C502D2AB2C@exs23.ex.nus.edu.sg>
Date:         Mon, 16 Aug 1999 18:08:44 +0800
Reply-To: Gao Qing <engp8682@NUS.EDU.SG>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gao Qing <engp8682@NUS.EDU.SG>
Subject:      Re: [MOBILE-IP] routing optimization authentication
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi,

-----Original Message-----
From: n. asokan [mailto:n.asokan@NOKIA.COM]
Sent: Friday, August 13, 1999 4:33 AM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Subject: Re: [MOBILE-IP] routing optimization authentication

>What exactly is the threat and how will FA->HA authentication help
>with that?
>If the threat is denial of service, FA->HA authentication
>won't help (FA can simply not forward any packets, including the
>registration request).
At least we can provide non-repudiation with asymmetric FA-HA
authentication.

>If the threat is FA having access to MN's data, it is probably best
>dealt with using upper layer confidentiality protection.
I agree. We only deal with entity authentication here.

>In any case, to avoid 'hostile FAs', FA->HA authentication alone isn't
>enough.  HA has to have some way of deciding whether an FA is
>'hostile' (black lists, white lists, whatever).  This probably implies
>more infrastructure.
Well, just like the CRL, it *may* be managed by the CAs. The HA should
only verify the certificate of the FA, thus the public key of the FA. With
that public key, the HA can verify the FA's signature appended to the
registration request. The result also provides the HA with 'non-repudiation
of
origin'.

>Actually, use of shared-key systems does not have to necessarily imply
>having an entity like AAAH generate keys on the fly and distribute it
>to MN: short term/temporary keys can be derived from a long term key.
>E.g., in your example above, if the MN shares a long term key K with
>the AAAH, then the key between MN and a given FA can be derived as a
>function of K, the identity of the FA, and possibly some transient
>information (like the current time).  That way, the AAAH does not have
>to generate a key and convey it to MN and FA but compute it and convey
>it only to the FA (via AAAF). I.e., MN can already compute this key
>and use it to compute and attach an authenticator in its registration
>request.  FA will be able to verify the authenticator when it receives
>the key from AAAH.  No additional flows between FA and MN are
>necessary.

But the HA still has to wait for the registration request and generate and
distribute a key for the FA, right? It can not avoid introducing significant

overhead and delay.

Moreover, the current time at the MN won't be conform to that at the HA.
They generate the key at different time.

Qing


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 16 09:38:19 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23466
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 16 Aug 1999 09:38:18 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.768E4D40@standards.nortelnetworks.com>; Mon, 16 Aug 1999 9:33:57 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 45574 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 16 Aug 1999 09:33:28
          -0400
Received: from relay1.mail.uk.psi.net by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.652D7300@standards.nortelnetworks.com>; Mon, 16 Aug 1999 9:33:27
          -0400
Received: from mail.isd-nec.co.uk ([193.122.212.249] helo=tokyo.isd-nec.co.uk)
          by relay1.mail.uk.psi.net with esmtp (Exim 2.12 #2) id
          11GMvU-0000G8-00 for MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 16
          Aug 1999 14:35:48 +0100
Received: by TOKYO with Internet Mail Service (5.5.1960.3) id <PJDFP15T>; Mon,
          16 Aug 1999 14:35:22 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain
Message-ID:  <3B9AA5E712DCD011AAD500609770A0E920374C@TOKYO>
Date:         Mon, 16 Aug 1999 14:35:21 +0100
Reply-To: "BINAR, Simon" <binar@ISD-NEC.CO.UK>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "BINAR, Simon" <binar@ISD-NEC.CO.UK>
Subject:      Re: [MOBILE-IP] Consensus vote: Private addresses and Mobile IP
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

There have been a lot of discussions highlighting both pros and cons for
the adoption of Options 1 and 2. How about the following extremely
simple possibility:

- Not to specify anything new.
- To write somewhere in an informational RFC that any MN roaming outside
the private corporate network should be configured with a globally
routable (home) IP address, or should use a (dynamically assigned) CCOA.

I am thinking about this due to the following thoughts/observations:

- Machines configured with fixed IP addresses can be 1) either
difficult-to-move desktop machines or 2) easy-to-move
laptops/PDAs/etc... The first category of machine wouldn't require MIP
support, since it can be assumed that the machine will most of the time
stay at the same place. The second category of machine probably will not
be happy to be configured with a private address, since by definition it
is mobile. It may be frequently moving outside of its subnet, and may
even frequently move from one site of a corporation to another (where a
conflict of private addresses could also occur simply because different
IT departments did not coordinate the allocation of private addresses to
hosts). Thus, it would make more sense to either dynamically assign an
IP address to this second category of machine or configure it with a
fixed address for use with MIP.

- More and more hosts use dynamic IP address allocation, simply because
it makes more sense from an economic point of view - both for
ISPs/network operators and private corporations...

So I am just questioning, looking at real-world situations, whether MIP
really needs to be extended to support private addresses...

Just being provocative, comments most welcome...

Simon

DISCLAIMER:  Any views or opinions expressed in
this E-Mail message should be considered as the
personal views/opinions of the author.  They do
not  necessarily  represent  the  views  of the
author's employer.


> -----Original Message-----
> From: Basavaraj Patil [mailto:bpatil@NORTELNETWORKS.COM]
> Sent: 27 July 1999 19:50
> To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
> Subject: [MOBILE-IP] Consensus vote: Private addresses and Mobile IP
>
>
> Hello,
>
> At IETF45 in Oslo we decided to take the question of how to deal with
> Mobile nodes that have a private IP address and obtain consensus on
> the mailing list. The options at hand for which consensus from the WG
> is sought in order to move forward, w.r.t handling private addresses
> in Mobile IP are :
>
> 1. Use co-located care of address as an option for mobile nodes with
>    private addresses when they are roaming outside their
>    administrative domains.
>
> 2. Mandatory reverse tunneling for mobile nodes that prefer to use
>    the Foreign Agents Care Of Address but have a private address.
>
> 3. The WG will develop a new solution to deal with the problem of
>    private address spaces for Mobile IP.
>
> Please mail your opinion to the mailing list or, to me or Phil
> Roberts.
>
> Basavaraj Patil
> Phil Roberts
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 16 11:37:19 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26352
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 16 Aug 1999 11:37:19 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.226374F0@standards.nortelnetworks.com>; Mon, 16 Aug 1999 11:33:17 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 45855 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 16 Aug 1999 11:31:39
          -0400
Received: from hermes.ccrl.nj.nec.com by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.E7E45420@standards.nortelnetworks.com>; Mon, 16 Aug 1999 11:31:39
          -0400
Received: from sun066 (sun066.ccrl.nj.nec.com [138.15.103.66]) by
          hermes.ccrl.nj.nec.com (1.00/LJF980616) with SMTP id LAA29767; Mon,
          16 Aug 1999 11:34:42 -0400 (EDT)
Received: by sun066 (4.1/CNC-Client) id AA02822; Mon, 16 Aug 99 11:36:55 EDT
Message-ID:  <9908161536.AA02822@sun066>
Date:         Mon, 16 Aug 1999 11:36:55 EDT
Reply-To: Arup Acharya <arup@CCRL.NJ.NEC.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Arup Acharya <arup@CCRL.NJ.NEC.COM>
Subject:      Re: [MOBILE-IP] QoS [diff-serv or int-serv/RSVP]
X-To:         stefan@RZ.UNI-KARLSRUHE.DE
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Stefan / Guilhem,

You may find this interesting:
"MRSVP : A Resource Reservation Protocol for an Integrated Services
Network with Mobile Hosts", Rutgers Tech-report, July 97, Submitted
for publication, available from paul.rutgers.edu/~talukdar/

Arup
_____________________________________________________________

Systems Architecture Group               arup@ccrl.nj.nec.com
C&C Research Labs, NEC USA               +1 609 951 2992
4 Independence Way, Princeton
NJ 08540



- On Fri, 13 Aug 1999, Guilhem Tardy wrote:
-
- > Hi!
- >
- > I am looking into the QoS stuff... do you have some links about what's
- > underway about it within MOBIP?
-
- the same with me; if there are some papers about this, I'd be glad to
- know where I can get them.
-
-    tschuess
-              Stefan Mink
-
- PS: Of course I'd be glad to hear about your work too, Guilhem :)
-
- eMail: stefan@rz.uni-karlsruhe.de
-


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 17 02:33:55 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06480
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 17 Aug 1999 02:33:55 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.5FEC2470@standards.nortelnetworks.com>; Tue, 17 Aug 1999 2:29:47 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 46696 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 17 Aug 1999 02:27:51
          -0400
Received: from mgw-x1.nokia.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.B4935AE0@standards.nortelnetworks.com>; Tue, 17 Aug 1999 2:17:50
          -0400
Received: from mgw-i2.ntc.nokia.com (mgw-i2.ntc.nokia.com [131.228.118.61]) by
          mgw-x1.nokia.com (8.9.3/8.9.3) with ESMTP id JAA26439; Tue, 17 Aug
          1999 09:17:19 +0300 (EETDST)
Received: from loki.research.nokia.com (loki.research.nokia.com [172.21.33.76])
          by mgw-i2.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id JAA02765; Tue, 17
          Aug 1999 09:01:36 +0300 (EETDST)
Received: from pupu.research.nokia.com (pupu.research.nokia.com [172.21.33.84])
          by loki.research.nokia.com (8.9.3/8.9.3) with ESMTP id JAA21783; Tue,
          17 Aug 1999 09:01:35 +0300 (EETDST)
Received: from possu.research.nokia.com (possu.research.nokia.com
          [172.21.33.80]) by pupu.research.nokia.com (8.9.1a/8.9.1) with ESMTP
          id IAA09615; Tue, 17 Aug 1999 08:59:34 +0300 (EET DST)
Received: (from asokan@localhost) by possu.research.nokia.com (8.9.1/8.9.1) id
          JAA08510; Tue, 17 Aug 1999 09:01:06 +0300 (EET DST)
References: <7p8o1u$9ie@ammu.research.nokia.com>
Lines: 97
X-Mailer: Gnus v5.6.45/Emacs 19.34
Message-ID:  <1tdd7wnymhp.fsf@possu.research.nokia.com>
Date:         Tue, 17 Aug 1999 09:01:06 +0300
Reply-To: "n. asokan" <n.asokan@NOKIA.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "n. asokan" <n.asokan@NOKIA.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         engp8682@NUS.EDU.SG
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  engp8682@NUS.EDU.SG's message of "Mon, 16 Aug 1999 18:08:44 +0800"

Hi Qing,

engp8682@NUS.EDU.SG (EXT Gao Qing) writes:
[...]
> At least we can provide non-repudiation with asymmetric FA-HA
> authentication.

I agree that asymmetric key cryptosystems in general enable nice
features. But I still don't see the rationale for FA->HA
authentication/non-repudiation.  What threat are you addressing when
you think of the non-repudiation service for FA->HA? (E.g., is there
some scenario when FA will later try to deny that it forwarded a
registration request from the MN?).


[...]
> Well, just like the CRL, it *may* be managed by the CAs. The HA should
> only verify the certificate of the FA, thus the public key of the FA. With
> that public key, the HA can verify the FA's signature appended to the
> registration request. The result also provides the HA with 'non-repudiation
> of
> origin'.

Well, it may not be as simple as that.  Consider the case when MN
sends a registration request for CoA X.  The only threat that seems to
justify FA->HA authentication is the following: MN is actually in the
X network; but it has been deemed a 'hostile network' by home domain
policy.  Here, HA needs a list of bad guys (or good guys). It is
unlikely that CAs can manage this list, since it is likely to be based
on domain-specific policy: note that FA will have a perfectly valid
certificate (or other means of authentication) corresponding to X;
just that MN's home domain policy does not allow MN to roam into the X
network.

   -> For black lists, FA->HA authentication is an overkill.  HA can
      simply reject the registration request based on CoA.
   -> For white lists, FA->HA authentication makes sense if we don't
      trust the security of the routing infrastructure (but we have
      bigger problems if routing infrastructure is compromised!).

Seems to me that FA->HA authentication based on IP address of FA is of
little use.

FAAA->HAAA authentication, based on a label from some other name
space than IP addresses may be useful. But perhaps this is beyond
scope for mobile-IP?

Supporting FA->HA authentication is probably no big deal.  For my own
edification, I would really like to know what rationales people
had in mind for the FA->HA authentication.

[...]
> But the HA still has to wait for the registration request and generate and
> distribute a key for the FA, right? It can not avoid introducing significant
>
> overhead and delay.

Yes, except that the key does not have to be sent (e.g., over the
wireless channel) to the MN.

When the MN does not have a key pair (as I thought you were
suggesting), HA has to wait anyway for the registration request, and
respond confirmation to FA and MN, right?  The overhead of
'generating' a key as I mentioned earlier (e.g., a single keyed hash)
or transporting it to FA (there is already an HA->FA flow) is not
significant.  The advantage is that in the end, there is an MN-FA
security association which is useful.

Even when MN does have a key pair, I think typically you cannot avoid
at least one on-line check with the home domain when an MN wanders in
for the first time into a foreign domain.  This is needed to ensure
the solvency of the user (i.e., that the foreign domain will get paid
for its services).  In general, asymmetric key based systems can
reduce the number of flows only when no on-line authorization check is
required.

>
> Moreover, the current time at the MN won't be conform to that at the HA.
> They generate the key at different time.
[...]

HA doesn't use its own time, but the time value used by the MN (which
MN can securely convey to the HA using the long term MN-HA shared
key).  It also does not have to be 'time' but any time-varying factor;
or it can be left out altogether (with the consequence that MN-FA key
will always be the same until the MN-HA key is changed).  By the way,
these are rather common techniques from the early '90s (if not before)
KryptoKnight suite of protocols.  For example, see "Authentication of
mobile users" by Samfat et al in IEEE Network, 8(2):26-35, March/April
1994.

Regards,
- Asokan

--
N. Asokan, Communication Systems Lab, Nokia Research Center, Helsinki


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 17 12:28:05 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27107
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 17 Aug 1999 12:28:05 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.4EAFD370@standards.nortelnetworks.com>; Tue, 17 Aug 1999 12:23:27 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 47129 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 17 Aug 1999 12:21:28
          -0400
Received: from pdp.csie.nctu.edu.tw by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.9BFBA570@standards.nortelnetworks.com>; Tue, 17 Aug 1999 12:11:17
          -0400
Received: (from khchi@localhost) by pdp.csie.nctu.edu.tw (8.8.7/8.8.5) id
          AAA16188; Wed, 18 Aug 1999 00:15:49 +0800 (CST)
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-ID:  <199908171615.AAA16188@pdp.csie.nctu.edu.tw>
Date:         Wed, 18 Aug 1999 00:15:49 +0800
Reply-To: Kuang-Hwei Chi <khchi@PDP.CSIE.NCTU.EDU.TW>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Kuang-Hwei Chi <khchi@PDP.CSIE.NCTU.EDU.TW>
Subject:      Re: [MOBILE-IP] Wanted: old hierarchical FA draft
X-To:         guilhem.ensuque@BT.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <5104D4DBC598D211B5FE0000F8FE7EB20243274B@mbtlipnt02.btlabs.bt.co.uk> from "G. Ensuque" at "Aug 16,
              99 09:46:02 am"
Content-Transfer-Encoding: 7bit

G. Ensuque wrote:
>Hi all again
>
>I would be extremely grateful if someone could send me the now expired draft
>by Charlie Perkins on Hierarchical Foreign Agents
>(draft-ietf-mobileip-hierfa-00) as I cannot
>
>Thanks in advance
>
>Guilhem Ensuque
>
>Mobility Futures Unit                           guilhem.ensuque@bt.com
>B55-131B
>BT Advanced Communications Technology Centre
>Adastral Park, Martlesham Heath
>IPSWICH IP5 3RE                              Tel: +44 1473 645 232
>UK                                                   Fax: +44 1473 646 885
>

Hello Guilhem,

Please visit web site
        http://www.svrloc.org/~charliep/txt/hierfa/hierfa.txt

Best

Chi

--
Kuang-Hwei Chi, Institute of Computer Science & Information Engineering
National Chiaotung University, Hsinchu, Taiwan    Phone: +886-3-5731892
Email: chikh@csie.nctu.edu.tw   WWW: http://www.csie.nctu.edu.tw/~chikh


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 17 13:06:19 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28789
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 17 Aug 1999 13:06:18 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.C51AD230@standards.nortelnetworks.com>; Tue, 17 Aug 1999 13:02:33 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 47187 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 17 Aug 1999 13:02:03
          -0400
Received: from engrss2.unl.edu by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.4D024DB0@standards.nortelnetworks.com>; Tue, 17 Aug 1999 12:52:02
          -0400
Received: from localhost (sci@localhost) by engrss2.unl.edu (8.9.3/8.9.3) with
          SMTP id LAA31710; Tue, 17 Aug 1999 11:53:05 -0500
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-ID:  <Pine.A32.3.95.990817115107.58261A-100000@engrss2.unl.edu>
Date:         Tue, 17 Aug 1999 11:53:04 -0500
Reply-To: Song Ci <sci@engrss2.unl.edu>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Song Ci <sci@engrss2.unl.edu>
Subject:      Re: [MOBILE-IP] QoS [diff-serv or int-serv/RSVP]
X-To:         Arup Acharya <arup@CCRL.NJ.NEC.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <9908161536.AA02822@sun066>

Hi,Arup,
Could you tell me whether you have the performance result about MRSVP?
And I want to know,do you think that it is feasible to use RSVP in mobile
IP network?
Best,
Song

On Mon, 16 Aug 1999, Arup Acharya wrote:

> Stefan / Guilhem,
>
> You may find this interesting:
> "MRSVP : A Resource Reservation Protocol for an Integrated Services
> Network with Mobile Hosts", Rutgers Tech-report, July 97, Submitted
> for publication, available from paul.rutgers.edu/~talukdar/
>
> Arup
> _____________________________________________________________
>
> Systems Architecture Group               arup@ccrl.nj.nec.com
> C&C Research Labs, NEC USA               +1 609 951 2992
> 4 Independence Way, Princeton
> NJ 08540
>
>
>
> - On Fri, 13 Aug 1999, Guilhem Tardy wrote:
> -
> - > Hi!
> - >
> - > I am looking into the QoS stuff... do you have some links about what's
> - > underway about it within MOBIP?
> -
> - the same with me; if there are some papers about this, I'd be glad to
> - know where I can get them.
> -
> -    tschuess
> -              Stefan Mink
> -
> - PS: Of course I'd be glad to hear about your work too, Guilhem :)
> -
> - eMail: stefan@rz.uni-karlsruhe.de
> -
>

-----------------------------------
Song Ci
Center of Communication and Information Sciences
Department of Electrical Engineering
University of Nebraska-Lincoln
Lincoln,NE68510
USA
Tel:(402)472-4056(D)
Email:sci@engrs.unl.edu
------------------------------------


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 17 13:25:34 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29544
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 17 Aug 1999 13:25:33 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.6F85C3E0@standards.nortelnetworks.com>; Tue, 17 Aug 1999 13:21:38 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 47274 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 17 Aug 1999 13:20:28
          -0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.DFE90B80@standards.nortelnetworks.com>; Tue, 17 Aug 1999 13:10:27
          -0400
Received: from brazil_imail. ([207.226.241.102]) by hosaka.smallworks.com
          (8.9.1/8.9.1) with ESMTP id MAA05115 for <mobile-ip@smallworks.com>;
          Tue, 17 Aug 1999 12:13:34 -0500 (CDT)
Received: from 207.226.241.102 [171.216.30.106] by brazil_imail. (SMTPD32-5.01)
          id A8B8164B011A; Tue, 17 Aug 1999 05:17:44 EDT
Message-ID:  <>
Date:         Mon, 17 Aug 1998 04:40:09 EST
Reply-To: Buddah159@AOL.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Buddah159@AOL.COM
Subject:      [MOBILE-IP] WIN THE AUGUST PENTIUM 350MHz LAPTOP GIVEAWAY !!
X-To:         Friend@public.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

<html>
<BODY BGCOLOR="#FFFFFF">
<CENTER>
<font COLOR="#000000" size="4"><b>This is to notify you that:<br>
You Have Been Specially Invited To Register For a...<p>
<b><font face="ARIAL" SIZE="4">Florida - Orlando</font>
<br>
<font face="ARIAL" color="#008040" SIZE="4">Cancun</font>
<br>
<font face="ARIAL" color="#8000ff" SIZE="4">Grand Cayman</font></b>
<br>
</font><b><font face="ARIAL" size="5"><em>Getaway!</em></font></b>
<br><font size="4">*******</font>
<font face="ARIAL" SIZE="4"><br>
<b>You will also be entered to win this months...</b><br>
<font COLOR="#0000FF" face="ARIAL" SIZE="5"><B>350 Mhz Pentium&#174 II<br>Notebook Computer <i>GIVEAWAY!</font>
<p>
<font face="ARIAL" SIZE="3">
No obligation - For complete details...
<br>
<font face="ARIAL" SIZE="4">
<CENTER><b><a href="http://www.travelwithus.com@3490464468/%74%72%61%76%65%6C%35/%69%6E%64%65%78%2E%68%74%6D%6C">Click Here NOW!</a><br>
</body></i></font></font></center></b></html>

















s--c1-8_79


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Wed Aug 18 06:12:27 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27922
	for <mobileip-archive@LISTS.IETF.ORG>; Wed, 18 Aug 1999 06:12:27 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.050A1C40@standards.nortelnetworks.com>; Wed, 18 Aug 1999 6:07:58 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 48312 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 18 Aug 1999 06:06:05
          -0400
Received: from mailer.berkom.de by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.5AF0D790@standards.nortelnetworks.com>; Wed, 18 Aug 1999 5:56:03
          -0400
Received: from tessier (tessier.berkom.de [141.39.14.22]) by mailer.berkom.de
          (8.8.8/8.8.8) with SMTP id LAA15926; Wed, 18 Aug 1999 11:58:54 +0200
          (MET DST)
Received: by localhost with Microsoft MAPI; Wed, 18 Aug 1999 12:02:14 +0200
X-Mailer: Microsoft Internet E-Mail/MAPI - 8.0.0.4211
Encoding: 21 TEXT
Message-ID:  <01BEE971.826165F0.S.Tessier@berkom.de>
Date:         Wed, 18 Aug 1999 12:02:13 +0200
Reply-To: "S.Tessier@berkom.de" <S.Tessier@berkom.de>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Serge Tessier <S.Tessier@berkom.de>
Organization: Berkom
Subject:      [MOBILE-IP] products overview
X-cc:         "sanmateu@berkom.de" <sanmateu@berkom.de>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

 Hi all,

I am trying to get some commercial informations about Mobile IP products and the status of them.

By status I mean:
Is it fully available, Can we test it for free?, which conditions?.....

I would be very grateful if someone could point me towards web resources, contacts, articles...

Best regards


Serge Tessier
Active Networks and Mobility
T-NOVA Deutsche Telekom mbH
Leistungszentrum Berkom
Goslarer Ufer 35
10589 Berlin
Germany
Tel: 00 49 30 3497 3146
Fax: 00 49 30 3497 3147


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Wed Aug 18 07:21:23 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28649
	for <mobileip-archive@LISTS.IETF.ORG>; Wed, 18 Aug 1999 07:21:23 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.8A676970@standards.nortelnetworks.com>; Wed, 18 Aug 1999 7:16:07 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 48424 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 18 Aug 1999 07:14:10
          -0400
Received: from ietf.org (132.151.1.176) by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.DED31D80@standards.nortelnetworks.com>; Wed, 18 Aug 1999 7:04:10
          -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org
          (8.9.1a/8.9.1a) with ESMTP id HAA28435; Wed, 18 Aug 1999 07:07:19
          -0400 (EDT)
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Message-ID:  <199908181107.HAA28435@ietf.org>
Date:         Wed, 18 Aug 1999 07:07:19 -0400
Reply-To: Internet-Drafts@ietf.org
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
Comments:     RFC822 error: <W> Incorrect or incomplete address field found and
              ignored.
From: Internet-Drafts@ietf.org
Subject:      [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.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 Regional Tunnel Management
        Author(s)       : E. Gustafsson,  A. Jonsson, C. Perkins
        Filename        : draft-ietf-mobileip-reg-tunnel-01.txt
        Pages           : 27
        Date            : 17-Aug-99

In Mobile IP a mobile node registers with its home agent each time it
changes care-of address.  If the distance between the visited network
and the home network of the mobile node is large, the signaling delay
for these registrations may be long.  We propose a solution for
performing registrations locally in the visited domain:  regional
registrations.  Regional registrations reduce the number of signaling
messages to the home network, and reduce the signaling delay when a
mobile node moves from one foreign agent to another, within the same
visited domain.  This may, for instance, improve the performance of
handover.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mobileip-reg-tunnel-01.txt

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

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


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

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-ietf-mobileip-reg-tunnel-01.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mobileip-reg-tunnel-01.txt

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

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

--OtherAccess--

--NextPart--


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Wed Aug 18 12:52:36 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17851
	for <mobileip-archive@LISTS.IETF.ORG>; Wed, 18 Aug 1999 12:52:35 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.F1273090@standards.nortelnetworks.com>; Wed, 18 Aug 1999 12:48:16 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 49361 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 18 Aug 1999 12:46:18
          -0400
Received: from bodeca.talarion (209.224.141.78) by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.443E0300@standards.nortelnetworks.com>; Wed, 18 Aug 1999 12:36:17
          -0400
Received: from hpy7y (03-119.012.popsite.net [198.31.24.119]) by
          bodeca.talarion with SMTP (Microsoft Exchange Internet Mail Service
          Version 5.5.2448.0) id RC105TFT; Wed, 18 Aug 1999 11:36:09 -0400
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 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID:  <001401bee997$b96b40e0$77181fc6@hpy7y>
Date:         Wed, 18 Aug 1999 12:35:45 -0400
Reply-To: vin siniscalchi <vsiniscalchi@THEFUTUREONLINE.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: vin siniscalchi <vsiniscalchi@THEFUTUREONLINE.COM>
Subject:      Re: [MOBILE-IP] products overview
X-To:         S.Tessier@berkom.de
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

I hold the same interest, but from the point of view of a college student
looking to do an honors project involving mobile-ip.
Thanks,
-vin siniscalchi-
TheFuture is here today.
www.thefutureonline.com

-----Original Message-----
From: Serge Tessier <S.Tessier@BERKOM.DE>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
<MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
Date: Wednesday, August 18, 1999 5:08 AM
Subject: [MOBILE-IP] products overview


> Hi all,
>
>I am trying to get some commercial informations about Mobile IP products
and the status of them.
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 19 00:29:18 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07344
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 19 Aug 1999 00:29:17 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.4B0757A0@standards.nortelnetworks.com>; Thu, 19 Aug 1999 0:25:08 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 50831 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 19 Aug 1999 00:23:23
          -0400
Received: from sunny.pacific.net.sg by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.A6501860@standards.nortelnetworks.com>; Thu, 19 Aug 1999 0:13:23
          -0400
Received: from pop2.pacific.net.sg (pop2.pacific.net.sg [203.120.90.86]) by
          sunny.pacific.net.sg with ESMTP id MAA28440; Thu, 19 Aug 1999
          12:16:33 +0800 (SGT)
Received: from yktan73 (ppp46.dyn108.pacific.net.sg [210.24.108.46]) by
          pop2.pacific.net.sg with SMTP id MAA04263; Thu, 19 Aug 1999 12:16:28
          +0800 (SGT)
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID:  <NDBBIAKLACOKFILHHDEKIEEFCAAA.y.k.tan@ieee.org>
Date:         Thu, 19 Aug 1999 12:13:53 +0800
Reply-To: y.k.tan@ieee.org
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Y K Tan <y.k.tan@ieee.org>
Subject:      Re: [MOBILE-IP] products overview
X-To:         vin siniscalchi <vsiniscalchi@THEFUTUREONLINE.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <001401bee997$b96b40e0$77181fc6@hpy7y>
Content-Transfer-Encoding: 7bit

Hi,

  May I know how do I unsubscribe this mailing list?

best ergards,
Y K Tan

> -----Original Message-----
> From: IP Routing for Wireless/Mobile Hosts (mobile-ip)
> [mailto:MOBILE-IP@STANDARDS.NORTELNETWORKS.COM]On Behalf Of vin
> siniscalchi
> Sent: Thursday, August 19, 1999 12:36 AM
> To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
> Subject: Re: [MOBILE-IP] products overview
>
>
> I hold the same interest, but from the point of view of a college student
> looking to do an honors project involving mobile-ip.
> Thanks,
> -vin siniscalchi-
> TheFuture is here today.
> www.thefutureonline.com
>
> -----Original Message-----
> From: Serge Tessier <S.Tessier@BERKOM.DE>
> To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
> <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
> Date: Wednesday, August 18, 1999 5:08 AM
> Subject: [MOBILE-IP] products overview
>
>
> > Hi all,
> >
> >I am trying to get some commercial informations about Mobile IP products
> and the status of them.
> >


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 19 00:36:00 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07515
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 19 Aug 1999 00:36:00 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.473B17F0@standards.nortelnetworks.com>; Thu, 19 Aug 1999 0:32:12 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 50871 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 19 Aug 1999 00:31:08
          -0400
Received: from exs24.ex.nus.edu.sg by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.20DC3F80@standards.nortelnetworks.com>; Thu, 19 Aug 1999 0:31:07
          -0400
Received: by EXS24 with Internet Mail Service (5.5.2448.0) id <QN4N2HNV>; Thu,
          19 Aug 1999 12:35:34 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <DABFA252A5A2D1118ADB00805FBED9C502D2AB38@exs23.ex.nus.edu.sg>
Date:         Thu, 19 Aug 1999 12:35:32 +0800
Reply-To: Gao Qing <engp8682@NUS.EDU.SG>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gao Qing <engp8682@NUS.EDU.SG>
Subject:      Re: [MOBILE-IP] routing optimization authentication
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi, Asokan

>I agree that asymmetric key cryptosystems in general enable nice
>features. But I still don't see the rationale for FA->HA
>authentication/non-repudiation.  What threat are you addressing when
>you think of the non-repudiation service for FA->HA? (E.g., is there
>some scenario when FA will later try to deny that it forwarded a
>registration request from the MN?).

OK. In the current internet, FA may just be a node providing MIP function.
It may not be intergrated with the access network closely. Thus, any node
that can provide FA function could broadcast Agent Advertisement and
detunnel packages. The situation is: A hostile FA can take over an newly
arrived MN from an existing legal FA. If the hostile FA is not
authenticated,
it can pass the MIP registration easily and make the MN have its IP address
as the care-of-address. When the HA tunnels the hostile FA the packets
destined to the MN, it can simply drop them or foward them to another host.
Thus, it is important to authenticate the FA's identity.

It is optimal that MN-FA directly authenticate each other. However, it is
very likely
that they don't share a security association in advance. As we mentioned
before,
one way is to let the home domain server (e.g. AAAH) generate a session key
and deliver it through a secure way to MN and FA. This method would
introduce
significant overhead due to key generation, encryption and decryption (AAAH
first encrypt it
with the security association it shares with AAAF. Then AAAF decrypt it and
encrypt
it with the security association it shares with FA). The other method is
to use asymmetric authentication between MN and FA. However, it could
also introduce significant overhead especially to the MN due to the
intensive computation
load of asymmetric crypto-algorithm and the delay resulting from certificate
verification.
In a wireless network, the MN has the need for power-saving. The less and
shorter the
signaling message it has to transfer and computation load it has to suffer,
the better.

Therefore, we try to circumvent this direct authentication by skpping the
direct authentication
between MN and FA. But implicitly deduce it from the success of MN-HA and
HA-FA two-way
authentication. Please refer to my previous email for detail.

>FAAA->HAAA authentication, based on a label from some other name
>space than IP addresses may be useful. But perhaps this is beyond
>scope for mobile-IP?
Yes, I think the identifier should based on person, but not device.
NAI is the trend, I think.

>Yes, except that the key does not have to be sent (e.g., over the
>wireless channel) to the MN.
It's not an exception. With your method, the key still has to be deliver
securely to the FA.

>When the MN does not have a key pair (as I thought you were
>suggesting), HA has to wait anyway for the registration request, and
>respond confirmation to FA and MN, right?  The overhead of
>'generating' a key as I mentioned earlier (e.g., a single keyed hash)
>or transporting it to FA (there is already an HA->FA flow) is not
>significant.
This is not that simple. Although there is an HA->FA flow, there may
not be a HA-FA security association. The overhead comes from encrypting
and decrypting the session key.

>In general, asymmetric key based systems can
>reduce the number of flows only when no on-line authorization check is
>required.
Could you please give an example?
Anyway, the on-line authorization should be done by the specific access
network.
MIP is a module above it.

In addition,I agree that in a hierarchical structure, when the FA/HA is a
part
of the access network, the FA can do surrogate registration on behalf of the

MN as long as the MN has successfully registered to the access network.

>HA doesn't use its own time, but the time value used by the MN (which
>MN can securely convey to the HA using the long term MN-HA shared
>key).
I think you are talking about using random number with challenge/response
for replay protection, right?

Regards,
Gao Qing


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 19 06:05:47 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20882
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 19 Aug 1999 06:05:46 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.458D03E0@standards.nortelnetworks.com>; Thu, 19 Aug 1999 6:01:26 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 51032 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 19 Aug 1999 05:59:53
          -0400
Received: from arthur.axion.bt.co.uk by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.0E76B090@standards.nortelnetworks.com>; Thu, 19 Aug 1999 5:59:53
          -0400
Received: from cbtlipnt02.btlabs.bt.co.uk by arthur (local) with ESMTP; Thu, 19
          Aug 1999 11:02:51 +0100
Received: by cbtlipnt02.btlabs.bt.co.uk with Internet Mail Service (5.5.2448.0)
          id <QWTKRMTG>; Thu, 19 Aug 1999 11:02:48 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Message-ID:  <5104D4DBC598D211B5FE0000F8FE7EB202432757@mbtlipnt02.btlabs.bt.co.uk>
Date:         Thu, 19 Aug 1999 11:02:32 +0100
Reply-To: guilhem.ensuque@BT.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "G. Ensuque" <guilhem.ensuque@BT.COM>
Subject:      [MOBILE-IP] THEMA and GRE
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi all

This is a question to the THEMA gurus.

I don't really understand why we need Tunnel IDs in THEMA. Is this to make
it look more like GPRS's GTP?

Also, in what field exactly are Tunnel IDs inserted in the GRE header?

Thanks in advance for all answers

Guilhem Ensuque

Mobility Futures Unit                           guilhem.ensuque@bt.com
B55-131B
BT Advanced Communications Technology Centre
Adastral Park, Martlesham Heath
IPSWICH IP5 3RE                              Tel: +44 1473 645 232
UK                                                   Fax: +44 1473 646 885


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 19 06:12:17 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20935
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 19 Aug 1999 06:12:17 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.4452E0C0@standards.nortelnetworks.com>; Thu, 19 Aug 1999 6:08:33 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 51099 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 19 Aug 1999 06:07:39
          -0400
Received: from exs24.ex.nus.edu.sg by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.23D46580@standards.nortelnetworks.com>; Thu, 19 Aug 1999 6:07:38
          -0400
Received: by EXS24 with Internet Mail Service (5.5.2448.0) id <QN4N2LDQ>; Thu,
          19 Aug 1999 18:12:18 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <DABFA252A5A2D1118ADB00805FBED9C502D2AB40@exs23.ex.nus.edu.sg>
Date:         Thu, 19 Aug 1999 18:12:16 +0800
Reply-To: Gao Qing <engp8682@NUS.EDU.SG>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gao Qing <engp8682@NUS.EDU.SG>
Subject:      Re: [MOBILE-IP] routing optimization authentication
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

>The advantage is that in the end, there is an MN-FA
>security association which is useful.

Is this security association really indispensible? In MIP, the
MN performs registration to home domain periodically. It is not
likely that the registration lifetime be very long. In this
case, does the MN need to prove its identity to the FA frequently
during a registration lifetime?


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 19 08:46:40 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26034
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 19 Aug 1999 08:46:39 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.CBB926E0@standards.nortelnetworks.com>; Thu, 19 Aug 1999 8:42:40 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 51175 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 19 Aug 1999 08:41:25
          -0400
Received: from vipunen.hut.fi (130.233.249.7) by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.39A701B0@standards.nortelnetworks.com>; Thu, 19 Aug 1999 8:31:25
          -0400
Received: from beta.hut.fi (jtm@beta.hut.fi [130.233.224.51]) by vipunen.hut.fi
          (8.9.3/8.9.3) with ESMTP id PAA183346; Thu, 19 Aug 1999 15:34:37 +0300
Received: (from jtm@localhost) by beta.hut.fi (8.9.1a/8.9.1) id PAA26558; Thu,
          19 Aug 1999 15:34:35 +0300 (EET DST)
X-Mailer: ELM [version 2.4 PL21]
Content-Type: text
Message-ID:  <199908191234.PAA26558@beta.hut.fi>
Date:         Thu, 19 Aug 1999 15:34:26 +0200
Reply-To: Jari T Malinen <jtm@CC.HUT.FI>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Jari T Malinen <jtm@CC.HUT.FI>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         engp8682@NUS.EDU.SG
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <DABFA252A5A2D1118ADB00805FBED9C502D2AB40@exs23.ex.nus.edu.sg>
              from "Gao Qing" at Aug 19, 99 06:12:16 pm

> >The advantage is that in the end, there is an MN-FA
> >security association which is useful.
>
> Is this security association really indispensible? In MIP, the
> MN performs registration to home domain periodically. It is not
> likely that the registration lifetime be very long. In this
> case, does the MN need to prove its identity to the FA frequently
> during a registration lifetime?

The registration lifetime [RFC 2002] can also be very long, even
infinite. It might be commonplace that the lifetime is small, but if
we use, say, signal-based handoff where we do not base our handoff
decisions on timeouts, we can reduce protocol overhead by having a long
lifetime.

Regards,

--jari

Jari Malinen (http://www.cs.hut.fi/~jtm)
Researcher, HUT/CS Lab. Tel. +358 9 451 4774, fax +358 9 451 5351.


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 19 20:04:23 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21313
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 19 Aug 1999 20:04:23 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.79A9B810@standards.nortelnetworks.com>; Thu, 19 Aug 1999 20:00:24 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 52575 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 19 Aug 1999 19:58:29
          -0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.CF1E0280@standards.nortelnetworks.com>; Thu, 19 Aug 1999 19:48:28
          -0400
Received: from search.japan.co.jp (sdn-ar-004carcorP271.dialsprint.net
          [168.191.207.201]) by hosaka.smallworks.com (8.9.1/8.9.1) with SMTP
          id SAA26040 for <mobile-ip@smallworks.com>; Thu, 19 Aug 1999 18:51:32
          -0500 (CDT)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID:  <700.634234.631446@search.japan.co.jp>
Date:         Thu, 19 Aug 1999 19:58:29 -0400
Reply-To: channel54@SUISSEMAIL.CH
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: channel54@SUISSEMAIL.CH
Subject:      [MOBILE-IP] Free Web Site Analysis
X-To:         mobile-ip@smallworks.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

Email Removal Answering Service call Monday - Friday 8am-5pm
Pacific time 877-855-2003. Sender/Site Owner is Traffic
Accelerator. Removal no cost.
==================================================

** IMMEDIATELY INCREASE YOUR SITES EXPOSURE **


          FREE Web Site Analysis

         FREE Meta Tag Generator

        FREE Search Engine Checker

      FREE Search Engine Submissions


     100% Free - No Strings Attached
    No Obligation To Purchase Anything
        Use As Often As You Like


Why do we provide these Free services? It's
our way of introducing ourselves to you and
to let you see our other web site promotion
products as well.

We are one of the largest web site submission
firms on the net today.  With over 3 1/2 years
of service we look forward to helping you
make your site more profitable and productive.


       Mon - Fri 8am-5pm Pacific Time

                USA / Canada
           Toll Free (877) 855-2003
              All Other Countries
             Direct (916) 771-4756


 ** IMMEDIATELY INCREASE YOUR SITES EXPOSURE **


To use these services there is no software
to download.  We provide the tools online
from our web site. You operate them over the
internet from your home or office.  Just type
in a little information and you'll see the
results immediately.


FREE COMPREHENSIVE WEB SITE ANALYSIS:

Obtain your comprehensive yet easy-to-read
web site analysis designed to provide you with
valuable information.  Tired of not being found
in the search engines?  This online analysis
can help.  It takes less then 30 seconds.

FREE SEARCH ENGINE SUBMISSIONS:

We will submit your web site to 5 of the hottest
search engines with absolutely no obligation.

FREE SEARCH ENGINE CHECKER:

This FREE service checks to see if your web site
is in the top 12 search engines. It's fast,
accurate, and FREE.

FREE META TAG GENERATOR:

This FREE service provides you with an easy-to-use
program that will ask you a few simple questions
and provide you with all you need to know to
get Meta Tags in your web site.

Remember - These services are FREE with No Strings
Attached.  You are under No Obligation to purchase
any of our other services.

If you want to obtain more exposure for your web site
then don't miss out on this valuable opportunity.
Call NOW.


        Mon - Fri 8am-5pm Pacific Time
                USA / Canada
           Toll Free (877) 855-2003
              All Other Countries
             Direct (916) 771-4756


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 20 10:28:37 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22976
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 20 Aug 1999 10:28:37 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.95879390@standards.nortelnetworks.com>; Fri, 20 Aug 1999 10:20:10 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 53046 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 20 Aug 1999 10:19:45
          -0400
Received: from zaphod.axion.bt.co.uk (132.146.5.1) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.20B623C0@standards.nortelnetworks.com>; Fri, 20 Aug 1999
          10:09:45 -0400
Received: from proton.b29net.bt.co.uk by zaphod.axion.bt.co.uk with SMTP (PP);
          Fri, 20 Aug 1999 15:12:42 +0100
Received: from galaxy.b29net.bt.co.uk by proton.b29net.bt.co.uk; Fri, 20 Aug
          1999 15:50:00 +0100
Received: from b29net.bt.co.uk by galaxy.b29net.bt.co.uk (SMI-8.6/SMI-SVR4) id
          PAA03241; Fri, 20 Aug 1999 15:12:40 +0100
X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.6 sun4u)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID:  <37BD6258.5169E8BA@b29net.bt.co.uk>
Date:         Fri, 20 Aug 1999 15:12:40 +0100
Reply-To: caroline@B29NET.BT.CO.UK
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Caroline Lebre <caroline@B29NET.BT.CO.UK>
Organization: BT, Mobile Systems Research
Subject:      [MOBILE-IP] Proposed extension for Mobile-IP
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

Dear all,

I'm part of a group looking at using MobileIP for handover between
different wireless networks in a tiered network infrastructure. We are
currently using networks such as Wireless LANs, IrDA and GSM.

We have developed an extension to Mobile IP that provides the Home Agent
with extra information about the network the mobile host is currently
using: the type of network and its bandwidth.

This extra information is very useful in a mobile environment because of
the changes in the bandwidth available to the mobile when handing over
between different wireless networks. We use it for dynamic downgrading,
transcoding or caching of data streams during handover for streams that
wouldn't be supported over the new wireless network used (for example
video over GSM). We also use it to put CBQ filters on tunnels with the
bandwidth of the access network.

We believe that these ideas are very important for the future of mobile
data and that Mobile IP has got an important role to play in that field.

We'd be interested to hear whether some of you are working on similar
ideas and what people think about this extension and the capabilities it
provides. Would you be interested in seeing more details of the
implementation on the mailing list?

This work is the network part of a European project called M3A (Mobile
Multi-Media Access) which aims to provide constant network coverage to a
mobile terminal by using a combination of the following networks:
HIPERLAN for up to 20 Mb/s indoor, DAB (Digital Audio Broadcasting) for
1.7 Mb/s downlink outdoor and GSM for wide range coverage at 14.4 kb/s.
Mobility across the different networks is provided using a Mobile IP
implementation that we've developed in C and JAVA on the Linux kernel
2.2.x.

If you would like more information about the project, please don't
hesitate to contact me or have a look at the web page at
http://m3a.hiperlan.org

Regards,

Caroline.
--
Caroline Lebre                           Email: caroline@b29net.bt.co.uk
B55 Rm122, BT Laboratories
Martlesham Heath                         Tel:   +44 (0)1473 644545
Ipswich, Suffolk, IP5 3RE, UK            Fax:   +44 (0)1473 646885


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Sat Aug 21 10:04:31 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07060
	for <mobileip-archive@LISTS.IETF.ORG>; Sat, 21 Aug 1999 10:04:31 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.F5ECEF70@standards.nortelnetworks.com>; Sat, 21 Aug 1999 10:00:13 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 54261 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Sat, 21 Aug 1999 09:58:19
          -0400
Received: from leonis.nus.edu.sg by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.4BD5F4B0@standards.nortelnetworks.com>; Sat, 21 Aug 1999 9:48:18
          -0400
Received: from localhost (engp7643@localhost) by leonis.nus.edu.sg
          (8.9.3/8.6.9/CNS-3.5) with SMTP id VAA23303; Sat, 21 Aug 1999
          21:51:24 +0800 (SST)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-ID:  <Pine.SGI.4.02.9908212120180.16893-100000@leonis.nus.edu.sg>
Date:         Sat, 21 Aug 1999 21:51:24 +0800
Reply-To: Foo Chun Choong <engp7643@LEONIS.NUS.EDU.SG>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Foo Chun Choong <engp7643@LEONIS.NUS.EDU.SG>
Subject:      [MOBILE-IP] QoS [diff-serv or int-serv/RSVP],
              and Windows MIP implementation
X-To:         Guilhem.Tardy@CRC.CA
X-cc:         mattyc@leonis.nus.edu.sg, chuakc@cwc.nus.edu.sg
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi Guilhem,

We at NUS have done some work regarding MIPv4 and RSVP/int-serv
integration. Some documents regarding this can be obtained from
http://mip.ee.nus.edu.sg/slcchua.ps.gz , slcfoo.ps.gz , and slcloh.ps.gz
The source code for the prototype implementation that we've developed here
at NUS to support MIP/RSVP/int-serv integration can be obtained from
http://mip.ee.nus.edu.sg/v3.0beta

BTW, we would also like to gauge the interest of the MIP community regarding an
implementation of MIP on Windows. We have developed a prototype implementation
of MN on Win95, and the agents on NT, and are contemplating an open-source
release of the source code for these if there's a big enough demand for it.

Regards,
Foo Chun Choong,
NUS Mobile IP project, http://mip.ee.nus.edu.sg
National University of Singapore


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 23 03:49:01 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06193
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 23 Aug 1999 03:49:01 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.BA78D940@standards.nortelnetworks.com>; Mon, 23 Aug 1999 3:43:57 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 54814 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 23 Aug 1999 03:42:05
          -0400
Received: from lorraine.loria.fr by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.12164540@standards.nortelnetworks.com>; Mon, 23 Aug 1999 3:32:05
          -0400
Received: from loria.fr (antibes.loria.fr [152.81.12.73]) by lorraine.loria.fr
          (8.9.3/8.9.3/8.9.3/JCG-DG) with ESMTP id JAA20367; Mon, 23 Aug 1999
          09:35:28 +0200 (MET DST)
X-Mailer: Mozilla 4.03 [fr] (WinNT; I)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID:  <37C0F9C0.457E20DA@loria.fr>
Date:         Mon, 23 Aug 1999 09:35:28 +0200
Reply-To: Isabelle Chrisment <Isabelle.Chrisment@LORIA.FR>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Isabelle Chrisment <Isabelle.Chrisment@LORIA.FR>
Subject:      [MOBILE-IP] Call For Participation in Mobile-IPv6 Connectathon
X-To:         ipng@sunroof.eng.sun.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 8bit

CALL FOR PARTICIPATION

                    MOBILE IPv6 CONNECTATHON

                    September 15-  17, 1999,
                    LORIA, Nancy, France


The G6 group is organizing a mobile-IPv6 connectathon in France, in
Nancy,
on September 15, 16 & 17 1999. Nancy is located in the east of France.
If you have mobile-IPv6 code and would like to participate to this
event complete the enclosed  registration form before END OF AUGUST.

Further information is available at http://www.loria.fr/~ichris/mobipv6


REGISTRATION FORM FOR  MOBILE-IPv6 CONNECTATHON'99


Workshop Date : Septembre 15  - September 17 1999
The reception of participants will begin September 15, from 10.00 am to
10.30 am.
The workshop will be ended  September 17, at  midday.

Conference Location  INRIA-LORIA/ Nancy
                     615 rue du Jardin Botanique
                     BP 101
                     54602 Villers-Lès-Nancy
                     url : http://www.loria.fr

Registration form to be completed and forwarded to re@loria.fr

_______________________________________________________________________________
Name (first, middle, last)

_______________________________________________________________________________
Affiliation (for badge)

_______________________________________________________________________________
Title/Job Function

_______________________________________________________________________________
Address

_______________________________________________________________________________
City                               Prov/State
Zip Code

_______________________________________________________________________________
Country

_______________________________________________________________________________
Telephone

_______________________________________________________________________________
Fax

_______________________________________________________________________________
E-mail



Participation in the Dinner   :
(9/16/1999)                     Yes  __
                                No   __



Date/Time of arrival   :

Date/Time of departure :


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 23 05:17:23 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07095
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 23 Aug 1999 05:17:22 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.2CAF51E0@standards.nortelnetworks.com>; Mon, 23 Aug 1999 5:13:02 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 54884 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 23 Aug 1999 05:11:05
          -0400
Received: from nms.nc3a.nato.int by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.E61018A0@standards.nortelnetworks.com>; Mon, 23 Aug 1999 5:11:04
          -0400
Received: from comsun21.nc3a.nato.int (comsun21.nc3a.nato.int [192.150.94.60])
          by nms.nc3a.nato.int (8.9.0/8.9.0) with ESMTP id LAA28747; Mon, 23
          Aug 1999 11:11:54 +0200 (MET DST)
Received: from comsun21 (comsun21 [192.150.94.60]) by comsun21.nc3a.nato.int
          (8.9.1b+Sun/8.9.1) with SMTP id MAA27558; Mon, 23 Aug 1999 12:12:31
          +0200 (MET DST)
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: r78fkUREqYB68HBAwWzrJA==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4m sparc
Message-ID:  <199908231012.MAA27558@comsun21.nc3a.nato.int>
Date:         Mon, 23 Aug 1999 12:12:31 +0200
Reply-To: Rob Goode <goode@nc3a.nato.int>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Rob Goode <goode@nc3a.nato.int>
Subject:      Re: [MOBILE-IP] QoS [diff-serv or int-serv/RSVP],
              and Windows MIP implementation
X-To:         engp7643@LEONIS.NUS.EDU.SG
X-cc:         eit@nc3a.nato.int, Guilhem.Tardy@CRC.CA
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Dear Foo Chun Choong,

We at NC3A have a testbed looking at emerging internet technologies,
specifically mobile IP, QoS and IPv6 and I would be interested
in some open source for these technologies on the Windows platform
as that is the most widely deployed platform in our organisation.

I would have a high interest in MIP on windows, especially in
source form, as my interest is in mobile routers (or mobile
hosts with two interfaces and IP forwarding enabled) which I
find tends not to be a standard function of most implementations,
and hence tends to require (small) source code modifications. Our
current interest is in MIP for IPv4, until MIPv6 becomes more
widely implemented.

Cheers,

Rob Goode
Principal Scientist
Communications Techniques Branch,
Communications Systems Division,
NC3A
PO Box 2501 CD
The Hague
The Netherlands


> MIME-Version: 1.0
> Date: Sat, 21 Aug 1999 21:51:24 +0800
> From: Foo Chun Choong <engp7643@LEONIS.NUS.EDU.SG>
> Subject: [MOBILE-IP] QoS [diff-serv or int-serv/RSVP], and Windows MIP
implementation
> X-To: Guilhem.Tardy@CRC.CA
> X-cc: mattyc@leonis.nus.edu.sg, chuakc@cwc.nus.edu.sg
> To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
>
> Hi Guilhem,
>
> We at NUS have done some work regarding MIPv4 and RSVP/int-serv
> integration. Some documents regarding this can be obtained from
> http://mip.ee.nus.edu.sg/slcchua.ps.gz , slcfoo.ps.gz , and slcloh.ps.gz
> The source code for the prototype implementation that we've developed here
> at NUS to support MIP/RSVP/int-serv integration can be obtained from
> http://mip.ee.nus.edu.sg/v3.0beta
>
> BTW, we would also like to gauge the interest of the MIP community regarding
an
> implementation of MIP on Windows. We have developed a prototype implementation
> of MN on Win95, and the agents on NT, and are contemplating an open-source
> release of the source code for these if there's a big enough demand for it.
>
> Regards,
> Foo Chun Choong,
> NUS Mobile IP project, http://mip.ee.nus.edu.sg
> National University of Singapore


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 23 05:27:38 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07186
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 23 Aug 1999 05:27:37 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.94C0BFC0@standards.nortelnetworks.com>; Mon, 23 Aug 1999 5:23:06 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 54888 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 23 Aug 1999 05:21:34
          -0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.F794CE90@standards.nortelnetworks.com>; Mon, 23 Aug 1999 5:11:33
          -0400
Received: from mx.seanet.com (ats1-61.worldramp.net [207.30.147.63]) by
          hosaka.smallworks.com (8.9.1/8.9.1) with SMTP id EAA28541; Mon, 23
          Aug 1999 04:14:48 -0500 (CDT)
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Message-ID:  <584.838160.236129@mx.seanet.com>
Date:         Mon, 23 Aug 1999 05:21:34 -0400
Reply-To: Pent350MHz@CITYCOM.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pent350MHz@CITYCOM.COM
Subject:      [MOBILE-IP] Free Trial Research Report Enclosed....!!!(adv)
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

<base HREF="http://www.ismh.com/">
<html>

<head>

<meta name="DESCRIPTION"
content="International Sports Management Holding Corporation is a publicly held Corporation established in 1993 and currently listed under the symbol (ISMH)">
<meta name="KEYWORDS"
content="international, ISM, Team, IRL, ISMH, Holding, Marketing, Management, sports, Athlete, football, basketball, golf, racing, Indy Racing League, auto, sports, Indy-car, Indy, Indiana, Indianapolis, track, sports, motorsports,  Jeff Ward, 500, 200, oval, Sponsors, Fan Club">
<meta name="RATING" content="General">
<meta name="ROBOTS" content="All">
<meta name="AUTHOR" content="Webize, Inc. - http://www.webize.com">
<script language="JavaScript">

<!--
if (top==self) self.location.href = "index.htm";
//-->

</script>

<title>ISM HOLDING CORP.</title>
<base Target="body">
</head>

<body topmargin="0" leftmargin="0" bgcolor="#FFFFFF"
style="font-family: Arial, verdana, sans-serif">
<div align="left">

<table border="0" cellpadding="0" cellspacing="0" width="909">
</table>
</div><div align="center"><center>

<table border="0" cellspacing="0" width="90%">
  <tr>
    <td width="100%"><div align="center"><center><table border="1" cellspacing="0"
    bordercolor="#FFFFFF" bordercolorlight="#FFFFFF" bordercolordark="#0000FF" cellpadding="4">
      <tr>
        <td><blink>EMERGING GROWTH RESEARCH REPORTS PRESENTS</blink></td>
      </tr>
    </table>
    </center></div><p><small><font face="Arial">International Sports Management Holding
    Corporation (ISM) is a publicly held Corporation established in 1993 and currently listed
    under the symbol (ISMH). The company&#146;s offices and race shops are located in a 42,000
    square foot state of the art building at 4500 W. 96<sup>th</sup> St. in Indianapolis,
    Indiana in the Mayflower Business Park. ISM specializes in sports marketing and
    sponsorship solicitation for sports properties, as well as owning, marketing and managing
    its own professional auto racing teams. ISM currently owns a team in the Indy Racing
    League (IRL), which races in the prestigious Indianapolis 500 as well as ten additional
    races in eight major cities in the United States. </font></small></p>
    <font face="Arial"><p><small>It is ISM&#146;s objective to maximize shareholder value
    through the utilization of its corporate officers&#146; vast knowledge and experience in
    the field of sports marketing and management as well as incremental revenue programs.
    ISM&#146;s business philosophy and practices are geared toward maximizing success and
    minimizing uncertainty and instability. Together with a staff of highly experienced and
    competent personnel, ISM has enjoyed great success in efficient utilization its capital
    resources.</small></font></p>
    <p align="center"><a name="DESCRIPTION OF BUSINESS"><font face="Arial" size="3"><strong>DESCRIPTION
    OF BUSINESS</strong></font></a></p>
    <p align="left"><font FACE="Arial" size="2">ISM is a nationally recognized sports
    management company specializing in three major areas of professional sports management;
    Sports Marketing, Athlete Management, and Professional Race Team Management. Since its
    inception, a number of major corporations and professional athletes have engaged the
    services of ISM to assist them in their sports marketing needs. The company has cultivated
    marketing opportunities for athletes in professional and collegiate sports such as;
    professional golf, football and basketball as well as owning and managing several
    professional auto-racing teams.</font></p>
    <p align="center"><font face="Arial" size="3"><strong>ISM HOLDING <a name="MANAGEMENT">MANAGEMENT</a></strong></font></p>
    <p align="left"><font face="Arial"><small>L.G. Hancher and Gary D. Sallee were co-founders
    of the company and are currently its principal shareholders.</small></font></p>
    <p><small><font face="Arial"><strong>L. G. Hancher</strong>, Chairman of ISM Holding, has
    a diversified professional motor sports marketing background. In 1985 while serving as
    Sales and Marketing Manager for the Raynor Garage Door Company, Mr. Hancher initiated
    Raynor&#146;s involvement in motorsports with a product sponsorship at the Indianapolis
    500 garages. The program was so successful in increasing sales of Raynor products that the
    following year Raynor purchased their own racing team and appointed Mr. Hancher as
    President and General Manager of the team.</font></small></p>
    <p><small><font face="Arial">He then went on to lead the Raynor team to a top ten standing
    in 1987 and 1988.</font></small></p>
    <p><small><font face="Arial">Following Mr. Hancher&#146;s success at Raynor, he began an
    entrepreneurial endeavor as an importer for Pi Research computer systems where he worked
    with leading race teams in NASCAR, INDY Car, Formula One and IMSA. He then furthered his
    racing experience as General Manager for the McKenzie Group Financial racing team and
    achieved top ten finishes in every oval race for the 1990 season. Mr. Hancher was managing
    partner of ISM Holding&#146;s FIRST PLUS/Team Cheever sponsored IRL Team, winning
    it&#146;s third race as a new team and the first race in 1997 at the Walt Disney 200 and
    continuing on to a third place finish at the prestigious Indianapolis 500 that year</font></small></p>
    <p><font face="Arial"><small><strong>Gary Sallee</strong>, President of ISM Holding, has
    been practicing general business law in Indianapolis, Indiana since 1981. His law practice
    has focused on sports and entertainment management as well as commercial real estate
    development. In 1993, Mr. Sallee together with Mr. Hancher formed International Sports
    Management. Mr. Sallee is an NFLPA contract advisor and has represented players in the
    NFL; USFL, CFL, NHL and other team based sports. During the early 80&#146;s He was also a
    member of the Board of Advisors of the Indianapolis Checkers IHL Hockey Team. Mr. Sallee
    has represented many personalities from the entertainment world including record
    companies, a recording studio, promoters and sponsors. He has also been involved in the
    organizing of special events such as the closing ceremonies for the Pan American games and
    the National Sports Festival, hosted by the city of Indianapolis. Mr. Sallee has also been
    involved with various charitable organizations such as the Hemophilia Foundation of
    Indiana where he served on the Board of Directors for more than ten years and as President
    has for five years. He recently served as a member of the Board of Directors of the
    National Hemophilia Foundation.</small></font></p>
    <p align="center"><a name="MOTORSPORTS"><strong><font face="Arial">MOTORSPORTS</font></strong></a></p>
    <p align="left"><font face="Arial"><small>In the motorsports field, ISM has actively been
    involved in race team ownership since 1997 and management since it&#146;s inception.
    Currently the company owns and manages a team that competes in the Indy Racing League
    (IRL) series. ISM Holding has been very successful in fielding winning cars and numerous
    front-line drivers since the team&#146;s inception in 1993.</small></font></p>
    <p><small><font face="Arial">For the 1997-1998 IRL season ISM Racing Corp. a subsidiary of
    ISM, fielded one car driven by Jeff Ward in all 11 IRL events. At the Disney 200, and the
    Phoenix 200 ISM fielded a two-car team. ISM was the only team in 1998 to have entered and
    successfully qualified three cars in the 1998 Indianapolis 500. Steve Knapp who finished
    third and won the coveted ROOKIE OF THE YEAR AWARD in 1998 drove one of the cars.</font></small></p>
    <p><font face="Arial"><small>During the 1997-1998 IRL season Jeff Ward finished third and
    won THE ROOKIE OF THE YEAR AWARD in the 1997 Indianapolis 500. In addition Jeff completed
    his first full IRL season with ISM Racing Corp. Jeff finished sixth in the 1997-1998
    points standings, was second in laps led with 326, had five top ten finishes, eight top
    ten starts, with one pole position, and started from the front row four times in eleven
    races.</small></font></p>
    <div align="center"><center><table border="0" cellpadding="0" cellspacing="0" width="100%">
      <tr>
        <td width="50%"><small><font face="Arial">With multi year co-title sponsorships from
        Thermo Tech Technologies (TTRIF) and Cease-Fire (BIOF), ISM Racing Corp. is again poised
        to be a top contending team for the 1998-1999 IRL season. </font></small></td>
        <td width="50%"><img src="../images/car35a.gif" WIDTH="368" HEIGHT="78"></td>
      </tr>
    </table>
    </center></div><p><small><font face="Arial">Associate sponsors Prolong Super Lubricants,
    National Car Rental, Volvo, Nextel, and other sponsors at various levels will benefit from
    the exposure on race day and the proven experience that the ISM team has in nurturing
    Business to Business relationships.</font></small></p>
    <p><small><font face="Arial">It is ISM&#146;s intent to own a majority interest in all
    open wheel-racing venues. All race teams will be based out of ISM&#146;s offices and shop
    facility, located in Indianapolis, Indiana. ISM will control all operational, financial,
    and management functions of the teams.</font></small></p>
    <p><font face="Arial"><small>In 1997, ISM became involved in the highly successful NASCAR
    Winston Cup series as an owner of a newly formed team. At the end of the season the
    company elected to sell its interest in the team. Nevertheless, ISM will continue to be
    involved in securing sponsors for the teams new owners.</small></font></p>
    <p align="center"><a name="SPORTS MANAGEMENT"><strong><font face="Arial">SPORTS </font><font
    face="Arial" size="3">MANAGEMENT</font></strong></a></p>
    <p align="left"><font face="Arial"><small>ISM management and staff have successfully
    developed programs for major corporations desiring to promote their products through
    professional athletes and sports leagues including The PGA, LPGA, SPGA Tour, NFL, NHL,
    NHRA, IMSA, USAC, NASCAR, and the IRL. With the diversified expertise and vast knowledge
    ISM intends to continue to expand the Sports Management segment of the business as sports
    marketing continues to grow as a viable way for corporations to market their products.</small></font></p>
    <p align="center"><a name="MARKETING"><font face="Arial"><strong>MARKETING</strong></font></a></p>
    <p align="left"><small><font face="Arial">ISM has a full time staff of professionals that
    focus on &quot;sports sponsorship solicitation&quot; for both motor sports as well as
    athletes. ISM marketing personnel focus on soliciting sponsorship monies from corporations
    looking to use sports marketing as a way to promote their products and services. As a
    result of the national media exposure and its fast pace level of excitement, auto racing
    has and is continuing to become one of the most popular areas of involvement for corporate
    America. Brand loyalty among race fans is the highest of any fan base in the world of
    professional sports.</font></small></p>
    <p><font face="Arial"><small>ISM through its management and marketing personnel have
    successfully developed and implemented many successful and profitable incremental revenue
    programs. ISM will continue to develop programs that can be designed to utilize the
    business to business relationships that the company has established in the past.</small></font></p>
    <p align="center"><a name="BUSINESS STRATEGY"><strong><font face="Arial">BUSINESS STRATEGY</font></strong></a></p>
    <p align="left"><font face="Arial"><small>The company is committed to solid systematic
    profitable growth through the expansion of its existing motorsports division. The company
    plans to expand from a one-car team to a two-car team in the IRL series. The company will
    continue to aggressively pursue its Athlete Management endeavors by finding new players to
    join the ever-growing stable of professional athletes that it currently represents. The
    company will continue ride the current wave of corporate sponsorship involvement to
    maximize their sports marketing programs.</small></font></td>
  </tr>
</table>
</center></div>

<p align="center"><br>
<small><font face="Arial">DISCLAIMER </font></small></p>

<p align="center">=========================================================== </p>

<p><font face="Arial"><small>The sender of this report cannot and does not warrant the
completeness, accuracy, merchant ability, or fitness of the news, information, or
entertainment content found herein for any particular purpose. Further, you agree that the
sender shall not be held liable to anyone for any loss or injury resulting from the direct
or indirect use of this report. This includes, but is not limited to, loss or injury
caused in whole or in part by its negligence or by contingencies beyond its control in
procuring, compiling, interpreting, reporting or delivering any portion of this report.
You agree that you bear responsibility for your own investment research and investment
decisions, and that the sender of this report shall not be liable for any decision made or
action taken by you or others based upon reliance on news, information, or any material
published herein. All information provided herein is to be used on an &quot;as is, with
all faults&quot; basis. The sender of this report relies on various sources of information
that we believe to be accurate and reliable. However, the sender makes no claims or
representations with regard to the accuracy, completeness, or truth of any material
contained herein. The sender of this email was paid $2,000 in return for this service. </small></font></p>

<p align="center"><small><font face="Arial">TO UNSUBSCRIBE </font></small></p>

<p align="center">=========================================================== </p>

<p><small>To be removed from the Stock Alert mailing list, reply to this message with the
word REMOVE or UNSUBSCRIBE in the subject and include your e-mail address in the text of
your reply. Please note: if you have more than one e-mail address, include ALL of your
addresses in the text of your reply to ensure removal from the mailing list. </small></p>
</body>
</html>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 23 11:58:36 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21917
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 23 Aug 1999 11:58:35 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.32FA5D50@standards.nortelnetworks.com>; Mon, 23 Aug 1999 11:54:05 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 55352 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 23 Aug 1999 11:52:12
          -0400
Received: from sirius.ctr.columbia.edu by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.EFD46C50@standards.nortelnetworks.com>; Mon, 23 Aug 1999 11:52:12
          -0400
Received: from comet.columbia.edu (sweetpea.comet.columbia.edu [128.59.68.61])
          by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) with ESMTP id LAA03248;
          Mon, 23 Aug 1999 11:55:28 -0400 (EDT)
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
References: <37BD6258.5169E8BA@b29net.bt.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID:  <37C19BD5.81B41088@comet.columbia.edu>
Date:         Mon, 23 Aug 1999 12:07:01 -0700
Reply-To: campbell@comet.columbia.edu
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "Andrew T. Campbell" <campbell@comet.columbia.edu>
Organization: Center for Telecommunications Research
Subject:      Re: [MOBILE-IP] Proposed extension for Mobile-IP
X-To:         caroline@B29NET.BT.CO.UK
X-cc:         mobiware@comet.columbia.edu
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

Caroline:

> We'd be interested to hear whether some of you are working on similar
> ideas and what people think about this extension and the capabilities it
> provides.

Mobiware is a programmable mobile networking toolkit (based
on CORBA and Java software technologies) that allows
third parties to program wireless/mobile services into cellular
infrastructures - it interworks with mobile IP at gateways.
Inside the cellular access networks you can implement different
styles of services (e.g., handoff, filtering service, etc.)
using a set of well defined networking APIs.

Regarding your specific note, mobiware has the capability to
inject new audio and video filters
into the access points on-the-fly. If fact mobiware can
install and bind new filters during handoff without
disruption to service - and in response to changing
QOS conditions.

The Mobiware source code has been available for
over a year now (with some 400 downloads) with people
building mirror testbeds (e.g., at Nortel Networks)
and extending the code base to other services of
interest; for free source code and manual see:

 http://comet.columbia.edu/mobiware/

There is a recent journal paper:

A. T. Campbell, M. E. Kounavis, and R. R.-F. Liao,
"Programmable Mobile Networks", Computer Networks and ISDN Systems,
Vol. 31, No. 7, pg. 741-765, April 1999.

that you will find on my pubs page. The mobiware page
has other related papers but not this one as yet.

--
Andrew
http://comet.columbia.edu/~campbell


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 23 12:36:45 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23233
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 23 Aug 1999 12:36:44 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.86C9CD30@standards.nortelnetworks.com>; Mon, 23 Aug 1999 12:32:13 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 55454 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 23 Aug 1999 12:30:28
          -0400
Received: from gw3.sprintspectrum.com by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.47FF9530@standards.nortelnetworks.com>; Mon, 23 Aug 1999 12:30:27
          -0400
Received: by gw3.sprintspectrum.com; id LAA28826; Mon, 23 Aug 1999 11:33:51
          -0500 (CDT)
Received: from uskmessoa001.sprintspectrum.com(208.10.75.11) by
          gw3.sprintspectrum.com via smap (V2.0) id xma028691; Mon, 23 Aug 99
          11:33:02 -0500
Received: by uskmessoa001.sprintspectrum.com with Internet Mail Service
          (5.5.2448.0) id <RFFVZ98S>; Mon, 23 Aug 1999 11:33:00 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <ABA3B5AA1991D21195940060970EB0E3C2ACC7@uskmessoa021.sprintspectrum.com>
Date:         Mon, 23 Aug 1999 11:32:43 -0500
Reply-To: "Lipford, Mark" <MLipfo01@SPRINTSPECTRUM.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "Lipford, Mark" <MLipfo01@SPRINTSPECTRUM.COM>
Subject:      Re: [MOBILE-IP] Consensus vote: Private addresses and Mobile IP
X-To:         "BINAR, Simon" <binar@ISD-NEC.CO.UK>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

As a planned MIP service provider we are hearing from potential customers
that support of dynamic and private IP addressing for MIP service is high on
the priority list.  I would stand strong on my previous statements that we
need to have private dynamic IP addressing supported.

Regards

                -----Original Message-----
                From:   BINAR, Simon [mailto:binar@ISD-NEC.CO.UK]
                Sent:   Monday, August 16, 1999 8:35 AM
                To:     MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
                Subject:        Re: [MOBILE-IP] Consensus vote: Private
addresses and Mobile IP

                There have been a lot of discussions highlighting both pros
and cons for
                the adoption of Options 1 and 2. How about the following
extremely
                simple possibility:

                - Not to specify anything new.
                - To write somewhere in an informational RFC that any MN
roaming outside
                the private corporate network should be configured with a
globally
                routable (home) IP address, or should use a (dynamically
assigned) CCOA.

                I am thinking about this due to the following
thoughts/observations:

                - Machines configured with fixed IP addresses can be 1)
either
                difficult-to-move desktop machines or 2) easy-to-move
                laptops/PDAs/etc... The first category of machine wouldn't
require MIP
                support, since it can be assumed that the machine will most
of the time
                stay at the same place. The second category of machine
probably will not
                be happy to be configured with a private address, since by
definition it
                is mobile. It may be frequently moving outside of its
subnet, and may
                even frequently move from one site of a corporation to
another (where a
                conflict of private addresses could also occur simply
because different
                IT departments did not coordinate the allocation of private
addresses to
                hosts). Thus, it would make more sense to either dynamically
assign an
                IP address to this second category of machine or configure
it with a
                fixed address for use with MIP.

                - More and more hosts use dynamic IP address allocation,
simply because
                it makes more sense from an economic point of view - both
for
                ISPs/network operators and private corporations...

                So I am just questioning, looking at real-world situations,
whether MIP
                really needs to be extended to support private addresses...

                Just being provocative, comments most welcome...

                Simon

                DISCLAIMER:  Any views or opinions expressed in
                this E-Mail message should be considered as the
                personal views/opinions of the author.  They do
                not  necessarily  represent  the  views  of the
                author's employer.


                > -----Original Message-----
                > From: Basavaraj Patil [mailto:bpatil@NORTELNETWORKS.COM]
                > Sent: 27 July 1999 19:50
                > To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
                > Subject: [MOBILE-IP] Consensus vote: Private addresses and
Mobile IP
                >
                >
                > Hello,
                >
                > At IETF45 in Oslo we decided to take the question of how
to deal with
                > Mobile nodes that have a private IP address and obtain
consensus on
                > the mailing list. The options at hand for which consensus
from the WG
                > is sought in order to move forward, w.r.t handling private
addresses
                > in Mobile IP are :
                >
                > 1. Use co-located care of address as an option for mobile
nodes with
                >    private addresses when they are roaming outside their
                >    administrative domains.
                >
                > 2. Mandatory reverse tunneling for mobile nodes that
prefer to use
                >    the Foreign Agents Care Of Address but have a private
address.
                >
                > 3. The WG will develop a new solution to deal with the
problem of
                >    private address spaces for Mobile IP.
                >
                > Please mail your opinion to the mailing list or, to me or
Phil
                > Roberts.
                >
                > Basavaraj Patil
                > Phil Roberts
                >


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 23 12:42:36 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23392
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 23 Aug 1999 12:42:35 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.5F37D680@standards.nortelnetworks.com>; Mon, 23 Aug 1999 12:38:16 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 55487 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 23 Aug 1999 12:36:28
          -0400
Received: from gw3.sprintspectrum.com by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.1E850860@standards.nortelnetworks.com>; Mon, 23 Aug 1999 12:36:27
          -0400
Received: by gw3.sprintspectrum.com; id LAA01354; Mon, 23 Aug 1999 11:39:53
          -0500 (CDT)
Received: from uskmessoa001.sprintspectrum.com(208.10.75.11) by
          gw3.sprintspectrum.com via smap (V2.0) id xma001250; Mon, 23 Aug 99
          11:39:36 -0500
Received: by uskmessoa001.sprintspectrum.com with Internet Mail Service
          (5.5.2448.0) id <RFFVZ0MX>; Mon, 23 Aug 1999 11:39:35 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <ABA3B5AA1991D21195940060970EB0E3C2ACC8@uskmessoa021.sprintspectrum.com>
Date:         Mon, 23 Aug 1999 11:39:32 -0500
Reply-To: "Lipford, Mark" <MLipfo01@SPRINTSPECTRUM.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "Lipford, Mark" <MLipfo01@SPRINTSPECTRUM.COM>
Subject:      Re: [MOBILE-IP] routing optimization authentication
X-To:         Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

                -----Original Message-----
                From:   Basavaraj Patil [mailto:bpatil@NORTELNETWORKS.COM]
                Sent:   Friday, August 13, 1999 11:58 AM
                To:     MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
                Subject:        Re: [MOBILE-IP] routing optimization
authentication

                >>>>> From: Patrice Calhoun <Pat.Calhoun@eng.sun.com>
                >>>>
                >>>>> I certainly cannot dispute the fact that a full blown
PKI has scaling
                >>>>advantages,
                >>>>> but it also has deployment problems. The reality of
the fact is that
                the
                >>>>global PKI
                >>>>> is not here yet, and may be here 5+ years from now.
                >>>>
                >>>>
                >>>>  I don't see why the use of public-key style
authentication in the
                >>>>  context of Mobile IP has to require a "global PKI". As
Steve Kent
                >>>>  has also mentioned several times on the IPSec mailing
list, deploying
                >>>>  PKI in a closed system isn't hard (it is more a mental
block than
                >>>>  anything else).
                >>>>
                >>>>  Also consider the fact that there are several thousand
(if not more)
                >>>>  HTTPS servers operating today using public-key
technology.
                >>>>
                >>>>  vipul
                >>>
                >>>Because with the current plans of CDMA deployment, it
really isn't a
                >>"closed"
                >>>network.
                >>>
                >>>PatC
                >>
                >>The current CDMA deployment is among a few major service
providers
                >>and can be *considered* a "Closed" network for the purpose
of
                >>discussion here. The organizations that intend on
deploying Mobile IP
                >>need to take a serious look at the option of having a
closed PKI
                >>system and the fact that it is very much a feasible
solution. I agree
                >>with Vipul's thought here,  that deployment of Mobile IP
by a group of
                >>service providers who can agree and thereby have a closed
PKI
                >>system. Global roaming in the future will require
supporting global
                >>PKI. But by the time we get to that point I believe we
will have such
                >>an infrastructure in place.
                >>
                >The current AAA proposals that I've made allow for the
broker to
                >issue certificates to all roaming partners, but not in the
scale that
                >you are talking about. In fact, no cross-certs are
necessary, unless
                >inter-broker mobility is allowed.
                >
                >As I stated earlier, even if that is the case the AAAF/AAAH
are still
                needed
                >to make on-the-fly authorization decisions. A certificate
alone will not be
                >sufficient for a foreign service provider to provide
service to a mobile
                node.
                >
                >PatC
                >


                Pat,

                So the broker is a CA and issues certs to the roaming
partners? What I
                am refering to is the case where you have a few service
providers who
                agree to cross certify their CAs as a result of roaming
agreements
                between them. The PKI managed by a service provider could
issue certs
                to the mobility agents. I am not refering to brokers at all.
Well I
                guess you could still have a broker concept to minimize the
number of
                associations between roaming partners, but in a small subset
it does
                not really matter.

                In order to provide service to a foreign MN the visiting
network needs
                to be assured of receiving payment. Since the FA and HA
*may* authenticate
                each other via certs, receiving a successful registration
reply should
                be sufficient (in my opinion). What other authorization info
(in the
                present context) needs to be provided to the visiting
network in order
                to provide service. Of course you will need the capability
of
                generating accounting records and that's where the *A* of
AAA may fit
                in. Maybe I am missing your point Pat....If I am please
clarify.

                -Raj

                There seems to be a continued assumption that we are only
talking about Roaming between wireless Carriers.  That is not a problem as
far a revenue assurance.  Any roaming between Carriers will be validated and
revenue assured vai the RF technology (CDMA HLR validation).  The Roaming
that I (as a carrier) is wanting to handle is from a non-RF MIP provider.
To me this is everybody EXCEPT the wireless carrier.  Let's look at this
discussion from that view point.

                Regards


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 24 06:30:16 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19287
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 24 Aug 1999 06:30:15 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.7CD86A70@standards.nortelnetworks.com>; Tue, 24 Aug 1999 6:25:41 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 56491 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 24 Aug 1999 06:23:47
          -0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.D3102BF0@standards.nortelnetworks.com>; Tue, 24 Aug 1999 6:13:46
          -0400
Received: from ani.univie.ac.at (heraklit.ani.univie.ac.at [131.130.32.104]) by
          hosaka.smallworks.com (8.9.1/8.9.1) with SMTP id FAA09469 for
          <mobile-ip@SMALLWORKS.COM>; Tue, 24 Aug 1999 05:16:55 -0500 (CDT)
Received: from goedel.ani.univie.ac.at by ani.univie.ac.at with SMTP id AA05624
          (5.65c8/IDA-1.4.4 for <mobile-ip@SMALLWORKS.COM>); Tue, 24 Aug 1999
          12:09:59 +0200
Received: by goedel.ani.univie.ac.at (5.x/SMI-4.1) id AA05312; Tue, 24 Aug 1999
          12:16:40 +0200
X-Charset: ASCII
X-Char-Esc: 29
Message-ID:  <9908241016.AA05312@goedel.ani.univie.ac.at>
Date:         Tue, 24 Aug 1999 12:16:40 +0200
Reply-To: gabi@ANI.UNIVIE.AC.AT
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: gabi@ANI.UNIVIE.AC.AT
Subject:      [MOBILE-IP] Announcement MASCOTS99
X-To:         mobile-ip@SMALLWORKS.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

******************************************************************************
Call for Participation: M A S C O T S ' 99
the Seventh International Symposium on Modeling, Analysis and Simulation
http://scylla.ani.univie.ac.at/~mascots/
                                  (co-located with IEEE DiS-RT'99, Oct 22-24,
                                   http://www.cs.unt.edu/~boukerch/wdis99)
******************************************************************************

Date and Venue:
    October 24-28, 1999
    The Inn and Conference Center University of Maryland,
    College Park MD, USA

******************************************************************************

Conference Program at a Glance

 Tutorials on Sunday, October 24, 1999
- Mobility Management in Mobile IP (Half-day)
- An Introduction to Network Security (Half-day)
- GloMoSim - A Library for Simulation of Large Wireless Networks (Full-day)

 Invited Seminars on Monday, October 25, 1999
- R. Fujimoto, Georgia Institute of Technology
- D. Nicol, Dartmouth College
- W. Sanders, University of Illinois at Urbana-Champaign
- M. Satyanarayanan, Carnegie Mellon University
- D. Towsley, University of Massachusetts
- K. Trivedi, Duke University

 Sessions on Tuesday, October 26, 1999
- ATM Networks
- Mobile, Wireless and Optical Networks
- Simulation Techniques and Environments
- Network Simulation

 Sessions on Wednesday, October 27, 1999
- Performance Techniques
- Performance Modeling and Analysis
- Workload
- QoS and Multimedia

 Sessions on Thursday, October 28, 1999
- Memory, Cache, and I/O Performance
- Software Analysis
- Analysis of Security Systems

******************************************************************************

For the detailed program and registration information please visit

    http://scylla.ani.univie.ac.at/~mascots/

or contact

    Cecilia Kullman
    UMIACS - MASCOTS Registration
    A. V. Williams Building
    University of Maryland
    College Park, MD 20742, USA
    Telephone: (301) 405-0304
    Fax: (301) 314-9658
    Email: cecilia@umiacs.umd.edu

******************************************************************************

PROGRAM CHAIR

Alois Ferscha
Department of Applied Computer Science
University of Vienna
Lenaugasse 2/8, A-1080 Vienna, Austria
Email: ferscha@ani.univie.ac.at
http://www.ani.univie.ac.at/~ferscha/
Phone: +43 1 408 63 66 18
Fax : +43 1 408 04 50

GENERAL CHAIRS

Patrick Dowd                            Darrell D. E. Long
Dept Electrical Engineering             Computer Science Department
University of Maryland &                University of California
U.S. Department of Defense                (Santa Cruz, CA)
Email: p.dowd@ieee.org                  Email: d.long@computer.org
Phone: +1 301 688 1420                  Phone: +1 831 459 2616
Fax : +1 301 931 2591                   Fax : +1 831 459 4829

PUBLICITY CO-CHAIRS

   Gabriele Kotsis, University of Vienna,
   Department of Applied Computer Science, Vienna, AUSTRIA
   Email: gabi@ani.univie.ac.at

   S. V. Raghavan, Indian Institute of Technology, Madras
   Department of Computer Science & Engineering, Madras, INDIA
   Email: svr@iitm.ernet.in

   Jerome Rolia, Carleton University
   Department of Systems and Computer Engineering, Ottawa, CANADA
   Email: jar@sce.carleton.ca

   Albert Y. Zomaya, The University of Western Australia
   Department of Electrical & Electronic Engineering, Perth, WESTERN AUSTRALIA
   Email: zomaya@ee.uwa.edu.au

******************************************************************************


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 24 12:02:54 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11896
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 24 Aug 1999 12:02:53 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.EEE45830@standards.nortelnetworks.com>; Tue, 24 Aug 1999 11:58:09 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 56980 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 24 Aug 1999 11:56:31
          -0400
Received: from dirty.research.bell-labs.com by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.B4332AE0@standards.nortelnetworks.com>; Tue, 24 Aug 1999 11:56:30
          -0400
Received: from grubby.research.bell-labs.com ([135.104.2.9]) by dirty; Tue Aug
          24 11:59:33 EDT 1999
Received: from king.research.bell-labs.com ([135.1.152.1]) by grubby; Tue Aug
          24 11:59:33 EDT 1999
Received: from notmafia.research.bell-labs.com.research.bell-labs.com (notmafia
          [135.1.152.230]) by king.research.bell-labs.com (Postfix) with SMTP
          id BCE6E57036 for <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Tue, 24
          Aug 1999 10:59:33 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <199908181107.HAA28435@ietf.org>
X-Mailer: VM 6.33 under Emacs 19.34.2
Message-ID:  <19990824155934.BCE6E57036@king.research.bell-labs.com>
Date:         Tue, 24 Aug 1999 10:59:34 -0500
Reply-To: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Subject:      [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <199908181107.HAA28435@ietf.org>
Content-Transfer-Encoding: 7bit

Internet-Drafts@IETF.ORG (I) writes:

I> http://www.ietf.org/internet-drafts/draft-ietf-mobileip-reg-tunnel-01.txt

I read through this draft and I have a couple of problems with it.

1) I do not believe it can correctly handle MNs with private IP addresses.

To quote:

   If the GFA receives a tunneled packet from a foreign agent in its
   domain, then after decapsulation the GFA looks to see whether it
   has an entry in its visitor list for the source IP address of the
   inner IP header after decapsulation.  If so, then it checks the
   visitor list to see whether reverse tunneling has been requested;
   if requested, then the GFA re-encapsulates the packet with its own
   address as the source IP address, and the address of the home agent
   as the destination IP address.

Thus demultiplexing is based explicitly on the IP address of the MN.  What
about the case where these addresses come from overlapping private address
spaces?  The GFA will get confused about to which HA these packets should
be tunneled.  It seems that to properly handle this case GRE tunnels must
be used on the leg from FA to GFA.

2) Complexity

Do we really need to expose all of this machinery to MNs?  It seems to
me that a greater degree of transparency (like that provided by THEMA)
would provide a cleaner architecture.

In this draft, the MN must explicitly realize that it is on a
regionalized network by looking at the 'I' bit, and must be capable of
using the new GFA extension.

3) Security

While most of the regional registration request is protected by a
mobile-foreign authentication extension, one key piece (the Hierarchical
Foreign Agent Extension) is not.  Is a denial of service attack possible
by a MN at a different FA?  Maybe the replay protection between MN and
GFA will help here but I can imagine cases where that would not be
sufficient.

This draft seems incapable of leveraging any link-layer security that
may exist, such as in a cellular network.

-Pete


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 24 12:34:30 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12963
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 24 Aug 1999 12:34:30 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.697FAFA0@standards.nortelnetworks.com>; Tue, 24 Aug 1999 12:30:12 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 57026 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 24 Aug 1999 12:28:31
          -0400
Received: from dirty.research.bell-labs.com by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.2CCB8660@standards.nortelnetworks.com>; Tue, 24 Aug 1999 12:28:31
          -0400
Received: from scummy.research.bell-labs.com ([135.104.2.10]) by dirty; Tue Aug
          24 12:31:36 EDT 1999
Received: from king.research.bell-labs.com ([135.1.152.1]) by scummy; Tue Aug
          24 12:31:36 EDT 1999
Received: from notmafia.research.bell-labs.com.research.bell-labs.com (notmafia
          [135.1.152.230]) by king.research.bell-labs.com (Postfix) with SMTP
          id 6160457036; Tue, 24 Aug 1999 11:31:37 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <5104D4DBC598D211B5FE0000F8FE7EB20243274C@mbtlipnt02.btlabs.bt.co.uk>
X-Mailer: VM 6.33 under Emacs 19.34.2
Message-ID:  <19990824163137.6160457036@king.research.bell-labs.com>
Date:         Tue, 24 Aug 1999 11:31:37 -0500
Reply-To: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Subject:      [MOBILE-IP] Darwinian evolution of proxy tunnelling...
X-To:         guilhem.ensuque@BT.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <5104D4DBC598D211B5FE0000F8FE7EB20243274C@mbtlipnt02.btlabs.bt.co.uk>
Content-Transfer-Encoding: 7bit

Hi, Guilhem,

"G. Ensuque" <guilhem.ensuque@BT.COM> (GE) writes:

GE> Hi all

GE> This is just to test my understanding: could the insiders correct
GE> me if I am wrong...

GE> Am I right to assume the following Darwinian evolution path for the idea of
GE> having 'daisy-chained' tunnels through proxies?

GE> Hierarchical FA --> TEP --> regionalized tunnel mgt --> THEMA

I'm not sure I would draw the picture quite that way.  THEMA definitely
derives from TEP and is a form of hierarchical FAs, but I would say
that the recent "Regionalized Tunnel" draft is on a separate branch.
The key distinguishing feature is that of transparency.

THEMA was originally conceived to solve a techno-political problem of
separation of the cellular link-layer termination point from foreign
agent functionality.  It provides a nice interface to FAs that is
independent of the link layer used to access the network.  While it is
also (incidentally) capable of serving as a hierarchical or regional
mobility solution, I am not at all sure that such architectures are
really justified.  Every one of these drafts makes the claim that they
enhance performance and scalability, but given the likely coverage areas
of link-layer termination points in wireless networks, and given some
of the work pointed out by Gerry Maguire:

> The simulations which we have done have gone down to 10m sized cells
> and there does not seem to be excessive traffic for managing the
> mobility of the mobile hosts (see
> http://www.it.kth.se/~maguire/JT-Liu-lic-thesis.pdf
> and
> http://www.it.kth.se/~aschmidt/DA.pdf
> for more details).

I am not convinced that the complexity of tree-like "regional
mobility" solutions are really justified.

So maybe the Previous FA extension will be enough to provide fast
handoff.  You still might need something like THEMA, though, depending
on which vendors supply your wireless equipment vs. which supply your
packet network equipment, and which of them have Mobile IP expertise.

Also none of the regional registration approaches solve the problem of
latency when we move between different administrative domains.  For
that we need either agreements between adjacent domains that allow the
Previous FA extension to work, or changes in the underlying wireless
transmission technologies that allow simultaneous link-layer
connections to two different networks.  That way a new registration
could be set up before the old one is torn down.

-Pete


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 24 12:56:30 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13903
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 24 Aug 1999 12:56:29 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.7ED9D030@standards.nortelnetworks.com>; Tue, 24 Aug 1999 12:52:17 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 57087 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 24 Aug 1999 12:50:31
          -0400
Received: from dirty.research.bell-labs.com by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.3F7701B0@standards.nortelnetworks.com>; Tue, 24 Aug 1999 12:50:30
          -0400
Received: from grubby.research.bell-labs.com ([135.104.2.9]) by dirty; Tue Aug
          24 12:52:07 EDT 1999
Received: from king.research.bell-labs.com ([135.1.152.1]) by grubby; Tue Aug
          24 12:52:07 EDT 1999
Received: from notmafia.research.bell-labs.com.research.bell-labs.com (notmafia
          [135.1.152.230]) by king.research.bell-labs.com (Postfix) with SMTP
          id 9854857036 for <mobile-ip@standards.nortelnetworks.com>; Tue, 24
          Aug 1999 11:52:08 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <5104D4DBC598D211B5FE0000F8FE7EB202432757@mbtlipnt02.btlabs.bt.co.uk>
X-Mailer: VM 6.33 under Emacs 19.34.2
Message-ID:  <19990824165208.9854857036@king.research.bell-labs.com>
Date:         Tue, 24 Aug 1999 11:52:08 -0500
Reply-To: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
Comments:     Resent-From: Pete McCann <mccap@research.bell-labs.com>
Comments:     Originally-From: Pete McCann <mccap@research.bell-labs.com>
From: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Subject:      [MOBILE-IP] THEMA and GRE
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <5104D4DBC598D211B5FE0000F8FE7EB202432757@mbtlipnt02.btlabs.bt.co.uk>
Content-Transfer-Encoding: 7bit

Hi, Guilhem,

"G. Ensuque" <guilhem.ensuque@BT.COM> (GE) writes:

GE> Hi all
GE> This is a question to the THEMA gurus.

GE> I don't really understand why we need Tunnel IDs in THEMA. Is this to make
GE> it look more like GPRS's GTP?

Not really - the Tunnel IDs are to distinguish MNs that might have
overlapping private addresses.  Any similarity to GTP is purely
coincidental.

GE> Also, in what field exactly are Tunnel IDs inserted in the GRE header?

In the Key field of the GRE header.

-Pete


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Wed Aug 25 16:25:02 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10926
	for <mobileip-archive@LISTS.IETF.ORG>; Wed, 25 Aug 1999 16:25:01 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.B1CB8790@standards.nortelnetworks.com>; Wed, 25 Aug 1999 16:20:06 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 58982 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 25 Aug 1999 16:19:42
          -0400
Received: from mail.cc.hut.fi by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.3CFCAFD0@standards.nortelnetworks.com>; Wed, 25 Aug 1999 16:09:41
          -0400
Received: from beta.hut.fi (jtm@beta.hut.fi [130.233.224.51]) by mail.cc.hut.fi
          (8.9.3/8.9.3) with ESMTP id XAA29423; Wed, 25 Aug 1999 23:13:14 +0300
          (EET DST)
Received: (from jtm@localhost) by beta.hut.fi (8.9.1a/8.9.1) id XAA06467; Wed,
          25 Aug 1999 23:13:11 +0300 (EET DST)
X-Mailer: ELM [version 2.4 PL21]
Content-Type: text
Message-ID:  <199908252013.XAA06467@beta.hut.fi>
Date:         Wed, 25 Aug 1999 23:13:08 +0200
Reply-To: Jari T Malinen <jtm@CC.HUT.FI>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Jari T Malinen <jtm@CC.HUT.FI>
Subject:      Re: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
X-To:         mccap@RESEARCH.BELL-LABS.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <19990824155934.BCE6E57036@king.research.bell-labs.com> from
              "Pete McCann" at Aug 24, 99 10:59:34 am

Hello, Pete,

> I> http://www.ietf.org/internet-drafts/draft-ietf-mobileip-reg-tunnel-01.txt
>
> I read through this draft and I have a couple of problems with it.
>
> 1) I do not believe it can correctly handle MNs with private IP addresses.

Right, as far as I understood, the support is not there and would be
reconsidered in the future after the private addressing issues
hopefully clear out. Then, I would vouch for the use of GRE tunnels
which would be straightforward even here. In Oslo there was a comment
that disapproved with the idea of relying on GRE tunnels. Why was that?

> 2) Complexity
>
> Do we really need to expose all of this machinery to MNs?  It seems to
> me that a greater degree of transparency (like that provided by THEMA)
> would provide a cleaner architecture.

Perhaps, though decision making needed in the MN is simple.  And both
a non-regional-aware MN and a similar HA can be used with a regional FA
hierarchy alhough they do not use the localized location updates.

> 3) Security
>
> While most of the regional registration request is protected by a
> mobile-foreign authentication extension, one key piece (the Hierarchical
> Foreign Agent Extension) is not.  Is a denial of service attack possible
> by a MN at a different FA?  Maybe the replay protection between MN and
> GFA will help here but I can imagine cases where that would not be
> sufficient.

Correct me if I am wrong, but isn't it easy to cause a DOS attack, anyway?
Besides a misconfigured microwave oven in the WLAN environment,
what if an attacker, call it MN2, snoops the address of the victim
MN, has a conspiring HA2, and sends a location update to the FA
which redirects the home link to HA2? MN2 and HA2 naturally use
the same shared secret. What if the MN uses itself (an alias interface,
perhaps), as HA2? How about this with a RFC-only FA?

> This draft seems incapable of leveraging any link-layer security that
> may exist, such as in a cellular network.

This does not prevent from statically configuring link-layer encryption,
at least in a WLAN environment. To get other security aspects besides
privacy, which was considered out of scope for the Mobile IP protocol,
maybe use of a network-level solution, such as the IPSec would be more
in line with the spirit of this draft?

Key management assisting the use of link-level security would be nice,
but aren't such extensions independent enough from the actual issue of
the draft so that they could be defined in another draft, in the regkey,
perhaps?

> -Pete

--jari

Jari Malinen (http://www.cs.hut.fi/~jtm)
Researcher, HUT/CS Lab. Tel. +358 9 451 4774, fax +358 9 451 5351.


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Wed Aug 25 17:44:44 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12940
	for <mobileip-archive@LISTS.IETF.ORG>; Wed, 25 Aug 1999 17:44:43 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.E2DE8B60@standards.nortelnetworks.com>; Wed, 25 Aug 1999 17:40:13 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 59068 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 25 Aug 1999 17:39:30
          -0400
Received: from mail.cc.hut.fi by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.634455C0@standards.nortelnetworks.com>; Wed, 25 Aug 1999 17:29:30
          -0400
Received: from beta.hut.fi (jtm@beta.hut.fi [130.233.224.51]) by mail.cc.hut.fi
          (8.9.3/8.9.3) with ESMTP id AAA20775; Thu, 26 Aug 1999 00:33:03 +0300
          (EET DST)
Received: (from jtm@localhost) by beta.hut.fi (8.9.1a/8.9.1) id AAA08962; Thu,
          26 Aug 1999 00:32:59 +0300 (EET DST)
X-Mailer: ELM [version 2.4 PL21]
Content-Type: text
Message-ID:  <199908252132.AAA08962@beta.hut.fi>
Date:         Thu, 26 Aug 1999 00:32:48 +0200
Reply-To: Jari T Malinen <jtm@CC.HUT.FI>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Jari T Malinen <jtm@CC.HUT.FI>
Subject:      Re: [MOBILE-IP] Darwinian evolution of proxy tunnelling...
X-To:         mccap@RESEARCH.BELL-LABS.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <19990824163137.6160457036@king.research.bell-labs.com> from
              "Pete McCann" at Aug 24, 99 11:31:37 am

Hello, Pete and Guilhem

> Pete McCann wrote
>
> Hi, Guilhem,
>
> "G. Ensuque" <guilhem.ensuque@BT.COM> (GE) writes:
>
> GE> Hi all
>
> GE> This is just to test my understanding: could the insiders correct
> GE> me if I am wrong...
>
> GE> Am I right to assume the following Darwinian evolution path for the idea of
> GE> having 'daisy-chained' tunnels through proxies?
>
> GE> Hierarchical FA --> TEP --> regionalized tunnel mgt --> THEMA
>
> I'm not sure I would draw the picture quite that way.  THEMA definitely
> derives from TEP and is a form of hierarchical FAs, but I would say
> that the recent "Regionalized Tunnel" draft is on a separate branch.
> The key distinguishing feature is that of transparency.

I would also like to mention another important distinguishing point,
the separation of concerns. The regionalized tunnel mgmt. draft does
not seem to assume any special support from the link-level. What if we
want to set up heterogeneous networks where we do have localized
location updates among devices from multiple vendors and among
multiple link-level technologies spanning over multiple subnets among
multiple administrative domains using legacy equipment (we are using a
"legacy" network level, the IPv4, after all)? Can we do all these with
THEMA?  The regionalized tunnel draft seems not to be designed with
multi-organization support in mind, but its principles seem not
impossible to expand over organization borders. Also, the separation
of concerns might affect the ease of evolution in standards and
implementations, in particular when using open environments.

> THEMA was originally conceived to solve a techno-political problem of
> separation of the cellular link-layer termination point from foreign
> agent functionality.  It provides a nice interface to FAs that is
> independent of the link layer used to access the network.  While it is
> also (incidentally) capable of serving as a hierarchical or regional
> mobility solution, I am not at all sure that such architectures are
> really justified.  Every one of these drafts makes the claim that they
> enhance performance and scalability, but given the likely coverage areas
> of link-layer termination points in wireless networks, and given some
> of the work pointed out by Gerry Maguire:
>
> > The simulations which we have done have gone down to 10m sized cells
> > and there does not seem to be excessive traffic for managing the
> > mobility of the mobile hosts (see
> > http://www.it.kth.se/~maguire/JT-Liu-lic-thesis.pdf
> > and
> > http://www.it.kth.se/~aschmidt/DA.pdf
> > for more details).

These texts seem interesting, but returning to your point,
perhaps the amount of traffic caused by location management is not so much
an issue here as is the network latency between the FA and the HA.

> I am not convinced that the complexity of tree-like "regional
> mobility" solutions are really justified.
>
> So maybe the Previous FA extension will be enough to provide fast
> handoff.  You still might need something like THEMA, though, depending
> on which vendors supply your wireless equipment vs. which supply your
> packet network equipment, and which of them have Mobile IP expertise.

I also hope we could have a very simple protocol.  Maybe your
consideration is true in some environments, but what if we add the
private networks, must we guarantee communication among all FAs that
are in separate private or protected access networks as might be
needed with the PFA extension? We might want to use private address
spaces for access point FAs just to minimize the use of public
addresses in the access network organization.

> Also none of the regional registration approaches solve the problem of
> latency when we move between different administrative domains.  For
> that we need either agreements between adjacent domains that allow the
> Previous FA extension to work, or changes in the underlying wireless
> transmission technologies that allow simultaneous link-layer
> connections to two different networks.  That way a new registration
> could be set up before the old one is torn down.

I wonder if this is strictly true. In a WLAN environment we could
think of a nested organization, say a university, where a set of
laboratories have agreed on a set of link-level parameters that allow
for roaming on a "public-access" channel between independently
administered small organizations within/under a larger
organization. Simultaneous inter-organizational link-layer connections
could also be thought of when a MN has multiple network interfaces,
say a WLAN and a low-speed wide-area wireless access.  Or, consider a
set of small businesses in a business park. The hierarchical structure
could follow, say, the structure of the domain names with the GFA
provided by a "big" organization, or a common ISP. A hierarchical
solution seems feasible for such settings.

> -Pete

Regards,

--jari

Jari Malinen (http://www.cs.hut.fi/~jtm)
Researcher, HUT/CS Lab. Tel. +358 9 451 4774, fax +358 9 451 5351.


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Wed Aug 25 18:38:36 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14112
	for <mobileip-archive@LISTS.IETF.ORG>; Wed, 25 Aug 1999 18:38:36 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.740ECD50@standards.nortelnetworks.com>; Wed, 25 Aug 1999 18:34:23 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 59226 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Wed, 25 Aug 1999 18:32:27
          -0400
Received: from dirty.research.bell-labs.com by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.2E330B20@standards.nortelnetworks.com>; Wed, 25 Aug 1999 18:32:26
          -0400
Received: from scummy.research.bell-labs.com ([135.104.2.10]) by dirty; Wed Aug
          25 18:35:27 EDT 1999
Received: from king.research.bell-labs.com ([135.1.152.1]) by scummy; Wed Aug
          25 18:35:27 EDT 1999
Received: from notmafia.research.bell-labs.com.research.bell-labs.com (notmafia
          [135.1.152.230]) by king.research.bell-labs.com (Postfix) with SMTP
          id 4408057033; Wed, 25 Aug 1999 17:35:26 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <19990824155934.BCE6E57036@king.research.bell-labs.com>
            <199908252013.XAA06467@beta.hut.fi>
X-Mailer: VM 6.33 under Emacs 19.34.2
Message-ID:  <19990825223527.4408057033@king.research.bell-labs.com>
Date:         Wed, 25 Aug 1999 17:35:27 -0500
Reply-To: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Subject:      Re: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
X-To:         Jari T Malinen <jtm@cc.hut.fi>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <199908252013.XAA06467@beta.hut.fi>
Content-Transfer-Encoding: 7bit

Hi, Jari,

Jari T Malinen <jtm@cc.hut.fi> (JTM) writes:

JTM> In Oslo there was a comment that disapproved with the idea of
JTM> relying on GRE tunnels. Why was that?

I suspect it was the fact that GRE is only an Informational RFC.  I
hope that GRE or something like it can be moved forward in the near
future; these kinds of tunnels seem to require the extra
demultiplexing information.

JTM> what if an attacker, call it MN2, snoops the address of the victim
JTM> MN, has a conspiring HA2, and sends a location update to the FA
JTM> which redirects the home link to HA2? MN2 and HA2 naturally use
JTM> the same shared secret. What if the MN uses itself (an alias interface,
JTM> perhaps), as HA2? How about this with a RFC-only FA?

You are correct that an RFC-2002 compliant FA may be attacked in this
way.  However, a simple work-around is to maintain a separation
between traffic from different link-layer addresses.  In the cellular
environment, we are assured that these link-layer addresses are indeed
authentic.  My point was simply that passing through a IP-in-IP tunnel
destroys this information - it is unavailable to the GFA even if it
was available at the FA.

>> This draft seems incapable of leveraging any link-layer security that
>> may exist, such as in a cellular network.

JTM> This does not prevent from statically configuring link-layer encryption,
JTM> at least in a WLAN environment. To get other security aspects besides
JTM> privacy, which was considered out of scope for the Mobile IP protocol,
JTM> maybe use of a network-level solution, such as the IPSec would be more
JTM> in line with the spirit of this draft?

Yes, you could use IPsec but that places a greater processing burden on
the MN.

JTM> Key management assisting the use of link-level security would be nice,
JTM> but aren't such extensions independent enough from the actual issue of
JTM> the draft so that they could be defined in another draft, in the regkey,
JTM> perhaps?

Key management and authenticated roaming will be necessary for
commercial deployment of Mobile IP; the visited network will want to
ensure that it gets paid for the services used.  Yes, these protocols
should be independent of regionalized registrations but any protocol
used in the access network should make sure not to destroy information
needed to ensure security properties.

-Pete


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 26 07:21:18 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09630
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 26 Aug 1999 07:21:17 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.D5E9DE10@standards.nortelnetworks.com>; Thu, 26 Aug 1999 7:15:54 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 59626 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 26 Aug 1999 07:14:48
          -0400
Received: from penguin.wise.edt.ericsson.se (194.237.142.110) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.482EDE00@standards.nortelnetworks.com>; Thu, 26 Aug 1999
          7:04:47 -0400
Received: from era-t.ericsson.se (koff.ericsson.se [147.214.173.137]) by
          penguin.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.3) with SMTP id
          NAA22722; Thu, 26 Aug 1999 13:08:17 +0200 (MET DST)
Received: from e00105a2d1ed7 by era-t.ericsson.se
          (SMI-8.6/LME-DOM-2.2.5(ERA/T)) id NAA19494; Thu, 26 Aug 1999 13:08:17
          +0200
X-Sender: erajoaa@era-t.ericsson.se
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-ID:  <3.0.32.19990826130756.00ac4af0@era-t.ericsson.se>
Date:         Thu, 26 Aug 1999 13:07:56 +0200
Reply-To: Annika Jonsson <annika.jonsson@ERICSSON.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Annika Jonsson <annika.jonsson@ERICSSON.COM>
Subject:      Re: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
X-cc:         mccap@RESEARCH.BELL-LABS.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hello Pete,

At 10:59 1999-08-24 -0500, Pete McCann wrote:
>Internet-Drafts@IETF.ORG (I) writes:
>
>I> http://www.ietf.org/internet-drafts/draft-ietf-mobileip-reg-tunnel-01.txt
>
>I read through this draft and I have a couple of problems with it.
>
>1) I do not believe it can correctly handle MNs with private IP addresses.
>

You are right, this draft does not address the problem of private IP
addresses. But hopefully it will work well toghether with whatever solution
comes out of the discussions about private addresses.

>
>2) Complexity
>
>Do we really need to expose all of this machinery to MNs?  It seems to
>me that a greater degree of transparency (like that provided by THEMA)
>would provide a cleaner architecture.
>
>In this draft, the MN must explicitly realize that it is on a
>regionalized network by looking at the 'I' bit, and must be capable of
>using the new GFA extension.
>

Yes, if it wants to use regional tunnels. RFC2002 MN:s are also supported,
but without regional tunnels.

THEMA handles the case when the MN and the FA are not on the same link. In
the regional tunnel mgmt. draft we assume that they are, and that regional
tunnels are managed by Mobile IP messages. In that case the MN must be
aware of the regional tunnel mgmt. since the replay protection is not
synchronised with the HA in that case.

>3) Security
>
>While most of the regional registration request is protected by a
>mobile-foreign authentication extension, one key piece (the Hierarchical
>Foreign Agent Extension) is not.  Is a denial of service attack possible
>by a MN at a different FA?  Maybe the replay protection between MN and
>GFA will help here but I can imagine cases where that would not be
>sufficient.
>

The Hierarchical Foreign Agent Extension can not be protected by a
mobile-foreign authentication extension, since it is added by a FA.  But
the Hierarchical Foreign Agent Extension can not be changed on the way to
the GFA since we assume that there exist established security associations
among a GFA and the foreign agents beneath it. We have not specified how
this is used, it could be IPSec, or maybe a FA-FA authentication extension
should be defined?

A MN2 at a different FA can not pretend to be MN1 since the GFA will detect
that the mobile-foreign authentication extension is not correct even if it
does not cover the Hierarchical Foreign Agent Extension.

>This draft seems incapable of leveraging any link-layer security that
>may exist, such as in a cellular network.
>

It doesn't assume it, but it doesn't prevent the use of such link-layer
security.

Thanks for your comments,
Annika

>-Pete
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 26 08:55:26 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14338
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 26 Aug 1999 08:55:25 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.218FF180@standards.nortelnetworks.com>; Thu, 26 Aug 1999 8:51:05 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 59757 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 26 Aug 1999 08:49:43
          -0400
Received: from hoemlsrv.firewall.lucent.com (192.11.226.161) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.F0B6E870@standards.nortelnetworks.com>; Thu, 26 Aug 1999
          8:49:43 -0400
Received: from hoemlsrv.firewall.lucent.com (localhost [127.0.0.1]) by
          hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id IAA12501
          for <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Thu, 26 Aug 1999
          08:53:18 -0400 (EDT)
Received: from uk0006exch001p.wins.lucent.com (h135-86-160-146.lucent.com
          [135.86.160.146]) by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3)
          with ESMTP id IAA12466 for <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>;
          Thu, 26 Aug 1999 08:53:17 -0400 (EDT)
Received: by uk0006exch001p.uk.lucent.com with Internet Mail Service
          (5.5.2448.0) id <PZY5H4KQ>; Thu, 26 Aug 1999 13:53:09 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Message-ID:  <976F7C55E3B2D111A0720008C728549C020A47BD@en0060exch001u.uk.lucent.com>
Date:         Thu, 26 Aug 1999 13:53:14 +0100
Reply-To: "Casati, Alessio (Alessio)" <acasati@LUCENT.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "Casati, Alessio (Alessio)" <acasati@LUCENT.COM>
Subject:      Re: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
X-To:         Annika Jonsson <annika.jonsson@ERICSSON.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

> >2) Complexity
> >
> >Do we really need to expose all of this machinery to MNs?  It seems to
> >me that a greater degree of transparency (like that provided by THEMA)
> >would provide a cleaner architecture.
> >
> >In this draft, the MN must explicitly realize that it is on a
> >regionalized network by looking at the 'I' bit, and must be capable of
> >using the new GFA extension.
> >
>
> Yes, if it wants to use regional tunnels. RFC2002 MN:s are also supported,
> but without regional tunnels.
>
For an operator it may be important to make
regional tunnels work independent of the
MIP stack used. Transparent and Compulsory solutions
(like Thema) are not prone to MN dependencies, i.e.
the operator decides what the behaviour of the network
is. In addition, there's the potential in Thema (and TEP it
borrows from)to support non MIP stack equipped terminals
in accessing networks the operator itself can provide
access to (e.g. internet access). If these two things
I mentioned look good from
an operator point of view, this may make the case
for reaching an understanding of what is the problem we
are trying to solve via regionalized tunnels and
which are the requirements the solution to the
problem should satisfy. Opinions?

Alessio


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 26 11:24:42 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22183
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 26 Aug 1999 11:24:41 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.FA412E40@standards.nortelnetworks.com>; Thu, 26 Aug 1999 11:20:18 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 59931 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 26 Aug 1999 11:19:31
          -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.DE12AC30@standards.nortelnetworks.com>; Thu, 26 Aug 1999 11:19:31
          -0400
Received: from engmail1.Eng.Sun.COM ([129.146.1.13]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id IAA12764; Thu, 26 Aug 1999 08:22:49
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.103.37]) by
          engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          IAA28415; Thu, 26 Aug 1999 08:22:48 -0700 (PDT)
Received: from finesse by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id IAA09170;
          Thu, 26 Aug 1999 08:22:46 -0700
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: TfKSj1IRRINRcPwtHs7c0Q==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc
Message-ID:  <199908261522.IAA09170@hsmpka.eng.sun.com>
Date:         Thu, 26 Aug 1999 08:22:42 -0700
Reply-To: Charles Perkins <Charles.Perkins@eng.sun.com>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Charles Perkins <Charles.Perkins@eng.sun.com>
Subject:      Re: [MOBILE-IP] question; my new affiliation
X-To:         esra.yagmur@turkcell.com.tr
X-cc:         ietf@ietf.org
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hello Yagmur,

The IETF agrees to standardize protocols by a process that is
not directly dependent upon sponsorship or support by particular
companies.  Mobile IP does not itself depend upon sponsorship.
However, if you read the mailing list, you will see contributions
from engineers that work at many famous companies.  These companies
may be considered to support the Mobile IP standardization effort,
by enabling their engineers to support that effort.

For information about the mobile-ip working group, please
consult the following URL:
        http://www.ietf.org/html.charters/mobileip-charter.html

Regards,
Charlie P.

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

I am changing my affiliation.  My new e-mail address will be:
                Charles E. Perkins <charliep@iprg.nokia.com>
I am also reachable at <charliep@computer.org>

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


> From: "ESRA YAGMUR  (S&NT-TMO)" <esra.yagmur@turkcell.com.tr>
> To: ietf@ietf.org
> Subject: question
> Date: Thu, 26 Aug 1999 16:02:36 +0300
> MIME-Version: 1.0
>
> Hi,
>
> Is there any partiular company sponsoring or supporting ietf about mobile
> IP?
>
> Thanks
> Yagmur
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 26 12:15:14 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23795
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 26 Aug 1999 12:15:13 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.FAE22500@standards.nortelnetworks.com>; Thu, 26 Aug 1999 12:10:26 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 60042 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 26 Aug 1999 12:08:33
          -0400
Received: from mercury.Sun.COM by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.B7402630@standards.nortelnetworks.com>; Thu, 26 Aug 1999 12:08:32
          -0400
Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id JAA03911; Thu, 26 Aug 1999 09:10:37
          -0700 (PDT)
Received: from hsmpka.eng.sun.com (hsmpka.Eng.Sun.COM [129.146.63.47]) by
          engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id
          JAA21489; Thu, 26 Aug 1999 09:10:36 -0700 (PDT)
Received: from finesse by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id JAA22008;
          Thu, 26 Aug 1999 09:10:25 -0700
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: mvCJLtaSh53Z/+z5VhTNsQ==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc
Message-ID:  <199908261610.JAA22008@hsmpka.eng.sun.com>
Date:         Thu, 26 Aug 1999 09:10:26 -0700
Reply-To: Charles Perkins <Charles.Perkins@eng.sun.com>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Charles Perkins <Charles.Perkins@eng.sun.com>
Subject:      Re: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
X-To:         Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
X-cc:         annika.jonsson@ERICSSON.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hello Pete,

You wrote:

>>I> http://www.ietf.org/internet-drafts/draft-ietf-mobileip-reg-tunnel-01.txt
>>                              ..........
>>1) I do not believe it can correctly handle MNs with private IP addresses.

Annika wrote:

> addresses. But hopefully it will work well together with whatever
> solution comes out of the discussions about private addresses.
> You are right, this draft does not address the problem of private IP

I wanted to reinforce Annika's point here.  Our intention was to
make a self-contained draft that could handle private addresses,
but which does not itself private addresses.  Making the separation
between the concepts was an illuminating and at times frustrating
process, which caused us to reject several alternative approaches
(and, in fact, in my cloudy recollection of Oslo it eventually
caused us to require the `I' flag ).

We feel that the regional draft can progress separately, but that
any such approach must be designed on the basis of the best current
understanding about how to handle private addresses.  So, for
instance, we believe that the current regional draft would be friendly
to any necessary extension for handling GRE tunnels, or for specifying
ways that foreign agents might taking home agent addresses into
consideration when delivering decapsulated packets.

Furthermore, we hope that such regional operations will be
taken into consideration as part of the inevitable discussion
about private addresses, so that as ideas emerge about private
addresses, people will also try to understand how regional
registration can work with private addresses.  The best way
to do this is to have an active effort for regional registration
going on at the same time.  For instance, if the home agent address
is important for routing packets to a mobile node, the GFA may
be required to change only the destination IP address of the IP
header when re-encapsulating packets for a lower-level care-of address.
Or, working group discussion may instead indicate the need for
an additional encapsulation, or a modified version of the minimal
encapsulation header, or ...?

>> 3) Security
>>                      .........
>> This draft seems incapable of leveraging any link-layer security that
>> may exist, such as in a cellular network.

This is an interesting observation, but isn't directly related
to regional registration.  Instead, I believe it is the departure
point for a very wide-ranging discussion about whether or not
Mobile IP itself is capable of leveraging link-layer security.

I think that mixing in link-layer security mechanisms with regional
registration mechanisms is mixing together operations from different
protocol levels in a suboptimal way.  On the other hand, it clearly
has applications in today's real world.

Regards,
Charlie P.

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

I am changing my affiliation.  My new e-mail address will be:
                Charles E. Perkins <charliep@iprg.nokia.com>
I am also reachable at <charliep@computer.org>

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


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 26 15:08:18 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27530
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 26 Aug 1999 15:08:16 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.2D8022B0@standards.nortelnetworks.com>; Thu, 26 Aug 1999 15:03:38 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 60234 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 26 Aug 1999 15:02:25
          -0400
Received: from dirty.research.bell-labs.com by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.015D75C0@standards.nortelnetworks.com>; Thu, 26 Aug 1999 15:02:24
          -0400
Received: from grubby.research.bell-labs.com ([135.104.2.9]) by dirty; Thu Aug
          26 15:05:48 EDT 1999
Received: from king.research.bell-labs.com ([135.1.152.1]) by grubby; Thu Aug
          26 15:05:48 EDT 1999
Received: from notmafia.research.bell-labs.com.research.bell-labs.com (notmafia
          [135.1.152.230]) by king.research.bell-labs.com (Postfix) with SMTP
          id 8092757037; Thu, 26 Aug 1999 14:05:49 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <19990824163137.6160457036@king.research.bell-labs.com>
            <199908252132.AAA08962@beta.hut.fi>
X-Mailer: VM 6.33 under Emacs 19.34.2
Message-ID:  <19990826190549.8092757037@king.research.bell-labs.com>
Date:         Thu, 26 Aug 1999 14:05:49 -0500
Reply-To: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Subject:      Re: [MOBILE-IP] Darwinian evolution of proxy tunnelling...
X-To:         Jari T Malinen <jtm@cc.hut.fi>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <199908252132.AAA08962@beta.hut.fi>
Content-Transfer-Encoding: 7bit

Hi, Jari,

Jari T Malinen <jtm@cc.hut.fi> (JTM) writes:

>> that the recent "Regionalized Tunnel" draft is on a separate branch.
>> The key distinguishing feature is that of transparency.

JTM> I would also like to mention another important distinguishing point,
JTM> the separation of concerns. The regionalized tunnel mgmt. draft does
JTM> not seem to assume any special support from the link-level.

By the way, neither does THEMA - it simply propagates a unique
identifier back to the GFA.

JTM> What if we want to set up heterogeneous networks where we do have
JTM> localized location updates among devices from multiple vendors
JTM> and among multiple link-level technologies spanning over multiple
JTM> subnets among multiple administrative domains using legacy
JTM> equipment (we are using a "legacy" network level, the IPv4, after
JTM> all)? Can we do all these with THEMA?

I don't think either of the proposals are intended to be used across
administrative domains.  THEMA was certainly intended to be used with
diverse link-layers; in fact it decouples the link-layer specific
equipment from the (somewhat complex) FA functionality with a fairly
simple interface.  In contrast, the leaf FAs in the regionalized
tunnel approach need to implement the whole range of FA functionality
including dealing with authentication servers - an area that is
rapidly changing, to say the least.

>> > The simulations which we have done have gone down to 10m sized cells
>> > and there does not seem to be excessive traffic for managing the
>> > mobility of the mobile hosts (see
>> > http://www.it.kth.se/~maguire/JT-Liu-lic-thesis.pdf
>> > and
>> > http://www.it.kth.se/~aschmidt/DA.pdf
>> > for more details).

JTM> These texts seem interesting, but returning to your point,
JTM> perhaps the amount of traffic caused by location management is not so much
JTM> an issue here as is the network latency between the FA and the HA.

Yes, this latency is an issue, which is why we need the Previous FA
extension or networks that support simultaneous dual connectivity for
smooth handoff.

>> I am not convinced that the complexity of tree-like "regional
>> mobility" solutions are really justified.
>>
>> So maybe the Previous FA extension will be enough to provide fast
>> handoff.  You still might need something like THEMA, though, depending
>> on which vendors supply your wireless equipment vs. which supply your
>> packet network equipment, and which of them have Mobile IP expertise.

JTM> I also hope we could have a very simple protocol.  Maybe your
JTM> consideration is true in some environments, but what if we add the
JTM> private networks, must we guarantee communication among all FAs that
JTM> are in separate private or protected access networks as might be
JTM> needed with the PFA extension? We might want to use private address
JTM> spaces for access point FAs just to minimize the use of public
JTM> addresses in the access network organization.

All the more reason to keep those FAs invisible to the MNs.  Think
about it - do you really want your first-hop IP router to have a
private address, when you are accessing the public Internet or a
private network with a completely different address space?

-Pete


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 26 15:28:31 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27819
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 26 Aug 1999 15:28:26 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.FF7D63C0@standards.nortelnetworks.com>; Thu, 26 Aug 1999 15:23:50 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 60325 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 26 Aug 1999 15:22:45
          -0400
Received: from smtprch1.nortel.com (192.135.215.14) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.D91E8B50@standards.nortelnetworks.com>; Thu, 26 Aug 1999
          15:22:45 -0400
Received: from zrchh190 by smtprch1.nortel.com; Thu, 26 Aug 1999 14:16:04 -0500
Received: from zrchb200.us.nortel.com (actually zrchb200) by zrchh190; Thu, 26
          Aug 1999 14:29:38 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2448.0) id
          <R26Y8QPA>; Thu, 26 Aug 1999 14:23:40 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Message-ID:  <61DEB565F616D31187880000F805A8D5817F17@crchy270.us.nortel.com>
Date:         Thu, 26 Aug 1999 14:23:37 -0500
Reply-To: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Basavaraj Patil <bpatil@NORTELNETWORKS.COM>
Subject:      [MOBILE-IP] IETF46: Timeslot Requests
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hello,

The IETF has now opened the doors for scheduling WG meetings for
IETF46. If you require a time slot to present to the Mobile IP WG at this
IETF please send in your request either to me or Phil Roberts. Please
include the following information in your request:

1) Name of presenter
2) Presentation (or I-D) title
3) I-D name
4) Amount of time you need

Cheers,
Basavaraj Patil

For more info on IETF46: http://ietf.org/meetings/meetings.html
----------------------------------------------------------------------------
---------------
I will be on sabbatical all of September and will be out of e-mail
range.
----------------------------------------------------------------------------
----------------


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 26 15:40:18 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28053
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 26 Aug 1999 15:40:15 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.AE51E690@standards.nortelnetworks.com>; Thu, 26 Aug 1999 15:35:52 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 60362 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 26 Aug 1999 15:34:26
          -0400
Received: from crufty.research.bell-labs.com by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.7A8762E0@standards.nortelnetworks.com>; Thu, 26 Aug 1999 15:34:26
          -0400
Received: from grubby.research.bell-labs.com ([135.104.2.9]) by crufty; Thu Aug
          26 15:37:44 EDT 1999
Received: from king.research.bell-labs.com ([135.1.152.1]) by grubby; Thu Aug
          26 15:37:44 EDT 1999
Received: from notmafia.research.bell-labs.com.research.bell-labs.com (notmafia
          [135.1.152.230]) by king.research.bell-labs.com (Postfix) with SMTP
          id 5B79057013; Thu, 26 Aug 1999 14:37:36 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <199908261610.JAA22008@hsmpka.eng.sun.com>
X-Mailer: VM 6.33 under Emacs 19.34.2
Message-ID:  <19990826193736.5B79057013@king.research.bell-labs.com>
Date:         Thu, 26 Aug 1999 14:37:36 -0500
Reply-To: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Subject:      Re: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
X-To:         Charles Perkins <Charles.Perkins@eng.sun.com>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <199908261610.JAA22008@hsmpka.eng.sun.com>
Content-Transfer-Encoding: 7bit

Hi, Charles,

Charles Perkins <Charles.Perkins@eng.sun.com> (CP) writes:

I> http://www.ietf.org/internet-drafts/draft-ietf-mobileip-reg-tunnel-01.txt
>>> ..........
>>> 1) I do not believe it can correctly handle MNs with private IP addresses.

CP> Annika wrote:

>> addresses. But hopefully it will work well together with whatever
>> solution comes out of the discussions about private addresses.
>> You are right, this draft does not address the problem of private IP

CP> I wanted to reinforce Annika's point here.  Our intention was to
CP> make a self-contained draft that could handle private addresses,
CP> but which does not itself private addresses.  Making the separation
CP> between the concepts was an illuminating and at times frustrating
CP> process, which caused us to reject several alternative approaches
CP> (and, in fact, in my cloudy recollection of Oslo it eventually
CP> caused us to require the `I' flag ).

CP> We feel that the regional draft can progress separately, but that
CP> any such approach must be designed on the basis of the best current
CP> understanding about how to handle private addresses.  So, for
CP> instance, we believe that the current regional draft would be friendly
CP> to any necessary extension for handling GRE tunnels, or for specifying
CP> ways that foreign agents might taking home agent addresses into
CP> consideration when delivering decapsulated packets.

Ok, I hope we can agree on some mechanisms.

CP> Furthermore, we hope that such regional operations will be
CP> taken into consideration as part of the inevitable discussion
CP> about private addresses, so that as ideas emerge about private
CP> addresses, people will also try to understand how regional
CP> registration can work with private addresses.  The best way
CP> to do this is to have an active effort for regional registration
CP> going on at the same time.

Some vendors already claim to handle private addresses, with the
simple mechanism of using the HA address and MN link-layer address as
unique identifiers.  While not formally part of any standard, this
approach could easily be implemented by an otherwised RFC2002
compliant FA.  I think this is understood pretty well and I think we
should be careful not to break this approach when we separate FA from
GFA.

CP> For instance, if the home agent address
CP> is important for routing packets to a mobile node, the GFA may
CP> be required to change only the destination IP address of the IP
CP> header when re-encapsulating packets for a lower-level care-of address.

But a similar mechanism must be introduced for the reverse traffic
path.  An IP-in-IP encapsulated packet addressed from FA to GFA does
not contain enough information.

CP> Or, working group discussion may instead indicate the need for
CP> an additional encapsulation, or a modified version of the minimal
CP> encapsulation header, or ...?

GRE encapsulation? :)

>>> 3) Security
>>> .........
>>> This draft seems incapable of leveraging any link-layer security that
>>> may exist, such as in a cellular network.

CP> This is an interesting observation, but isn't directly related
CP> to regional registration.  Instead, I believe it is the departure
CP> point for a very wide-ranging discussion about whether or not
CP> Mobile IP itself is capable of leveraging link-layer security.

Well, it is at least partly related to regional registration if some
information that is available to an RFC 2002 node is not available to
a regional GFA.

CP> I think that mixing in link-layer security mechanisms with regional
CP> registration mechanisms is mixing together operations from different
CP> protocol levels in a suboptimal way.

I agree that separation of concerns between layers is important, but
I'm not trying to write a protocol that violates modularity.  I'm
simply pointing out that some security properties depend on the proper
mapping of link-layer IDs to tunnels or IP addresses.  Security
concerns intrinsically violate layers - e.g., a firewall must be aware
of on which interface a packet arrived in order to implement policy.

CP> On the other hand, it clearly
CP> has applications in today's real world.

Yes.

I also hope we can get some idea from real-world vendors & carriers on
just how important it is to solve the "micro-mobility" problem in this
way: that is, at the IP layer, and in a way that's visible to MNs.
How big is the problem we are trying to solve?  How much extra
location management traffic/latency are we really talking about?  Keep
in mind that base stations do not terminate IP traffic in 2G or 3G
cellular networks - this is done further up in the network, meaning IP
handoffs are less frequent.

-Pete


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 26 16:12:13 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28560
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 26 Aug 1999 16:12:12 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.06245D90@standards.nortelnetworks.com>; Thu, 26 Aug 1999 16:06:58 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 60438 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 26 Aug 1999 16:05:50
          -0400
Received: from dumburken.it.kth.se by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.DDB43150@standards.nortelnetworks.com>; Thu, 26 Aug 1999 16:05:50
          -0400
Received: (from maguire@localhost) by dumburken.it.kth.se (8.9.3/8.9.3) id
          WAA25820; Thu, 26 Aug 1999 22:09:23 +0200 (MET DST)
References: <199908261610.JAA22008@hsmpka.eng.sun.com>
            <19990826193736.5B79057013@king.research.bell-labs.com>
Message-ID:  <199908262009.WAA25820@dumburken.it.kth.se>
Date:         Thu, 26 Aug 1999 22:09:23 +0200
Reply-To: Gerald Maguire <maguire@IT.KTH.SE>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gerald Maguire <maguire@IT.KTH.SE>
Subject:      Re: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
X-To:         mccap@RESEARCH.BELL-LABS.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <19990826193736.5B79057013@king.research.bell-labs.com> (message
              from Pete McCann on Thu, 26 Aug 1999 14:37:36 -0500)

Pete stated:
     Keep
     in mind that base stations do not terminate IP traffic in 2G or 3G
     cellular networks - this is done further up in the network, meaning IP
     handoffs are less frequent.

While this was perhaps true in 2G, it need not be true for all
3G. Especially if basestations are connected via IP (such as in the
case of ICEBERG) - why should you carry all this traffic up to a few
choke points - rather than route it as directly as possible.

This is especially true for the case of picocellular cells (for
example at home) where much of the traffic might not even need to
leave the house if it could be gatewayed more directly. Consider the
case of GSM on the Net type installations in offices - where much of
the traffic will be within the company but perhaps to a device on
another type of link - why should it go back to an gateway out of the
company (even if the actually MSC functionality is not located at the
company's site -- since the mobility management traffic is much
smaller than the actual channel traffic it is feasible to provide a
local BTS infrastructure, but put all the HLR, VLR, etc. functions
elsewhere.). {Although I should point out that there is a two board
Ericsson AXE-10 equivalent called Hatchet or MicroMTX, see the
upcoming talk by Per Bergqvist, Ericsson Radio AB
         http://www.erlang.se/erlang/sure/main/news/euc99.shtml
Erlang is also used to implement the GGSN and SGSN for Ericsson's GPRS.
So potentially one could have a very compact 2G system.
}


In an environment where there is a mix of WLAN and 2G (or 3G) overlays
- the mobility will have to be handled at the IP layer - since the
link layers can't talk to each other directly.

So I am not convinced that the rate of handoffs will be all that
low. Considering that I walk through at least 3 different DECT
environments when I walk 150m to the nearest hot dog vendor - I would
expect that in the future there will be at least this number of Mobile
IP networks that I will walk through.

Chip


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 26 17:26:19 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29908
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 26 Aug 1999 17:26:18 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.86783020@standards.nortelnetworks.com>; Thu, 26 Aug 1999 17:22:08 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 60581 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 26 Aug 1999 17:20:25
          -0400
Received: from crufty.research.bell-labs.com by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.48C75760@standards.nortelnetworks.com>; Thu, 26 Aug 1999 17:20:25
          -0400
Received: from grubby.research.bell-labs.com ([135.104.2.9]) by crufty; Thu Aug
          26 17:22:23 EDT 1999
Received: from king.research.bell-labs.com ([135.1.152.1]) by grubby; Thu Aug
          26 17:22:22 EDT 1999
Received: from notmafia.research.bell-labs.com.research.bell-labs.com (notmafia
          [135.1.152.230]) by king.research.bell-labs.com (Postfix) with SMTP
          id 76E8057013; Thu, 26 Aug 1999 16:22:14 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <199908261610.JAA22008@hsmpka.eng.sun.com>
            <19990826193736.5B79057013@king.research.bell-labs.com>
            <199908262009.WAA25820@dumburken.it.kth.se>
X-Mailer: VM 6.33 under Emacs 19.34.2
Message-ID:  <19990826212214.76E8057013@king.research.bell-labs.com>
Date:         Thu, 26 Aug 1999 16:22:14 -0500
Reply-To: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Subject:      Re: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
X-To:         Gerald Maguire <maguire@IT.KTH.SE>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <199908262009.WAA25820@dumburken.it.kth.se>
Content-Transfer-Encoding: 7bit

Gerald Maguire <maguire@IT.KTH.SE> (GM) writes:

GM> So I am not convinced that the rate of handoffs will be all that
GM> low. Considering that I walk through at least 3 different DECT
GM> environments when I walk 150m to the nearest hot dog vendor - I would
GM> expect that in the future there will be at least this number of Mobile
GM> IP networks that I will walk through.

Ok, so perhaps I am being influenced by some of the architectural
biases of my current employer. :)

Anyway, most of the examples you gave were indoor or low-mobility
(walking pace) environments.  What will be the actual rate of handoff?
Won't vanilla Mobile IP (possibly with Previous FA extensions) be able
to keep up?

-Pete


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 26 18:03:42 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00866
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 26 Aug 1999 18:03:41 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.B3909570@standards.nortelnetworks.com>; Thu, 26 Aug 1999 17:59:11 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 60624 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 26 Aug 1999 17:57:54
          -0400
Received: from dumburken.it.kth.se by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.85211250@standards.nortelnetworks.com>; Thu, 26 Aug 1999 17:57:53
          -0400
Received: (from maguire@localhost) by dumburken.it.kth.se (8.9.3/8.9.3) id
          AAA26072; Fri, 27 Aug 1999 00:01:27 +0200 (MET DST)
References: <199908261610.JAA22008@hsmpka.eng.sun.com>
            <19990826193736.5B79057013@king.research.bell-labs.com>
            <199908262009.WAA25820@dumburken.it.kth.se>
            <19990826212214.76E8057013@king.research.bell-labs.com>
Message-ID:  <199908262201.AAA26072@dumburken.it.kth.se>
Date:         Fri, 27 Aug 1999 00:01:27 +0200
Reply-To: Gerald Maguire <maguire@IT.KTH.SE>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gerald Maguire <maguire@IT.KTH.SE>
Subject:      Re: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
X-To:         mccap@research.bell-labs.com
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <19990826212214.76E8057013@king.research.bell-labs.com> (message
              from Pete McCann on Thu, 26 Aug 1999 16:22:14 -0500 (CDT))

Given that a reasonable walking rate is about 3m/sec (while a driver
on the interstate in NJ is perhaps moving 10 times this speed -- on a
good day) this means that for indoor picocells that I can walk through
some of them (such as a 10m cell) before I will have heard the second
Mobile IP beacon and in many cases before I can even get a DHCP
assigned COA (should I know that I have entered a new cell)! For
details of the COA timing measurments see:

    Jon-Olov Vatn and Gerald Q. Maguire Jr., "The effect of using
    co-located care-of addresses on macro handover delay", Fourteenth
    Nordic Tele-traffic Seminar (NTS 14), August 18 - 20, 1998, Lyngby,
    Denmark.

    which can be fetched from:  http://www.it.kth.se/~vatn/

Working in a building with multiple wireless infrastructures and with
a variety of access points (often with in a few meters of each other)
it is not hard to change which infrastructure provides you the best
service (in some cases without even moving yourself - but because
someone or something else has moved). So I think the rate at which you
can have intersystem handoffs is rather fast in comparison to some of
the current Mobile IP mechanisms.

Chip


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 26 18:46:22 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01381
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 26 Aug 1999 18:46:21 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.B6F77F70@standards.nortelnetworks.com>; Thu, 26 Aug 1999 18:42:14 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 60662 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 26 Aug 1999 18:40:24
          -0400
Received: from dirty.research.bell-labs.com by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.757C3130@standards.nortelnetworks.com>; Thu, 26 Aug 1999 18:40:24
          -0400
Received: from grubby.research.bell-labs.com ([135.104.2.9]) by dirty; Thu Aug
          26 18:44:00 EDT 1999
Received: from king.research.bell-labs.com ([135.1.152.1]) by grubby; Thu Aug
          26 18:43:59 EDT 1999
Received: from notmafia.research.bell-labs.com.research.bell-labs.com (notmafia
          [135.1.152.230]) by king.research.bell-labs.com (Postfix) with SMTP
          id B82B257013; Thu, 26 Aug 1999 17:43:59 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <199908261610.JAA22008@hsmpka.eng.sun.com>
            <19990826193736.5B79057013@king.research.bell-labs.com>
            <199908262009.WAA25820@dumburken.it.kth.se>
            <19990826212214.76E8057013@king.research.bell-labs.com>
            <199908262201.AAA26072@dumburken.it.kth.se>
X-Mailer: VM 6.33 under Emacs 19.34.2
Message-ID:  <19990826224359.B82B257013@king.research.bell-labs.com>
Date:         Thu, 26 Aug 1999 17:43:59 -0500
Reply-To: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Subject:      Re: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
X-To:         Gerald Maguire <maguire@it.kth.se>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <199908262201.AAA26072@dumburken.it.kth.se>
Content-Transfer-Encoding: 7bit

Hi, Chip,

Gerald Maguire <maguire@it.kth.se> (GM) writes:

GM> Given that a reasonable walking rate is about 3m/sec (while a driver
GM> on the interstate in NJ is perhaps moving 10 times this speed -- on a
GM> good day) this means that for indoor picocells that I can walk through
GM> some of them (such as a 10m cell) before I will have heard the second
GM> Mobile IP beacon and in many cases before I can even get a DHCP
GM> assigned COA (should I know that I have entered a new cell)! For
GM> details of the COA timing measurments see:

GM>     Jon-Olov Vatn and Gerald Q. Maguire Jr., "The effect of using
GM>     co-located care-of addresses on macro handover delay", Fourteenth
GM>     Nordic Tele-traffic Seminar (NTS 14), August 18 - 20, 1998, Lyngby,
GM>     Denmark.

GM>     which can be fetched from:  http://www.it.kth.se/~vatn/

Yes, I read this when you posted it previously.  Maybe the lesson is
to fix the speed of DHCP, as suggested in the paper, or not to use
DHCP at all.

GM> Working in a building with multiple wireless infrastructures and with
GM> a variety of access points (often with in a few meters of each other)
GM> it is not hard to change which infrastructure provides you the best
GM> service (in some cases without even moving yourself - but because
GM> someone or something else has moved). So I think the rate at which you
GM> can have intersystem handoffs is rather fast in comparison to some of
GM> the current Mobile IP mechanisms.

If you consider the case of FA-COA, and
solicitation/advertisement/registration sent immediately upon
link-layer handoff, this is not so clear to me.

In any case, assuming we have the Previous FA functionality working,
we have already eliminated the latency of the FA-HA roundtrip from the
interval between handoff and data reception.  In this case
regionalized handoffs only contribute a reduction in traffic to and
load at the HA.  Maybe what is needed is not a hierarchical tunneling
approach but rather a way to regulate the rate at which location
updates are forwarded to the HA.

-Pete


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Thu Aug 26 18:57:21 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01461
	for <mobileip-archive@LISTS.IETF.ORG>; Thu, 26 Aug 1999 18:57:20 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.41B2D410@standards.nortelnetworks.com>; Thu, 26 Aug 1999 18:53:16 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 60691 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Thu, 26 Aug 1999 18:51:17
          -0400
Received: from auemlsrv.firewall.lucent.com (192.11.223.161) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.FAB686B0@standards.nortelnetworks.com>; Thu, 26 Aug 1999
          18:51:17 -0400
Received: from auemlsrv.firewall.lucent.com (localhost [127.0.0.1]) by
          auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id SAA23433
          for <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Thu, 26 Aug 1999
          18:54:54 -0400 (EDT)
Received: from uk0006exch001p.wins.lucent.com (h135-86-160-146.lucent.com
          [135.86.160.146]) by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3)
          with ESMTP id SAA23412 for <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>;
          Thu, 26 Aug 1999 18:54:53 -0400 (EDT)
Received: by uk0006exch001p.uk.lucent.com with Internet Mail Service
          (5.5.2448.0) id <RWMN57QF>; Thu, 26 Aug 1999 23:54:32 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Message-ID:  <976F7C55E3B2D111A0720008C728549C020A47D1@en0060exch001u.uk.lucent.com>
Date:         Thu, 26 Aug 1999 23:50:25 +0100
Reply-To: "Casati, Alessio (Alessio)" <acasati@LUCENT.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "Casati, Alessio (Alessio)" <acasati@LUCENT.COM>
Subject:      Re: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Gerald,

> While this was perhaps true in 2G, it need not be true for all
> 3G. Especially if basestations are connected via IP (such as in the
> case of ICEBERG) - why should you carry all this traffic up to a few
> choke points - rather than route it as directly as possible.
>
On the contrary TDMA systems (GSM/EDGE/ANSI136) may be
more amenable than
UMTS and CDMA2000 (CDMA based 3G) in handling IP close to the
BTS.

This is due to the 3G RAN architectures
that foresee the need of a frame selector/distributor
to handle soft handover.

Economical (and performance) reasons suggest the
frame selector/distributor not to cover a very limited area.

Hence IP will 'emerge' from the lower layers at points
among which it's safe to state handoffs cannot occur very
frequently.

[...]

> In an environment where there is a mix of WLAN and 2G (or 3G) overlays
> - the mobility will have to be handled at the IP layer - since the
> link layers can't talk to each other directly.
>
It's a fair one.
Anyway it's quite a common understanding
that intersystem HO should be possibly
"rate limited", not to mention
interdomain&system HO.

> So I am not convinced that the rate of handoffs will be all that
> low. Considering that I walk through at least 3 different DECT
> environments when I walk 150m to the nearest hot dog vendor - I would
> expect that in the future there will be at least this number of Mobile
> IP networks that I will walk through.
>
I don't expect one to experience too frequent
HO in going to a Hot dogs
vendor, unless one is really hungry
(in which case HO disruptions may not be what
one would really most care about :).

Alessio


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 27 03:35:32 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19131
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 27 Aug 1999 03:35:31 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.885E2D90@standards.nortelnetworks.com>; Fri, 27 Aug 1999 3:30:38 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 60991 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 27 Aug 1999 03:29:20
          -0400
Received: from hosaka.smallworks.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.F3ABBB00@standards.nortelnetworks.com>; Fri, 27 Aug 1999 3:19:19
          -0400
Received: from auemlsrv.firewall.lucent.com (auemail1.lucent.com
          [192.11.223.161]) by hosaka.smallworks.com (8.9.1/8.9.1) with ESMTP
          id CAA08854 for <mobile-ip@hosaka.smallworks.com>; Fri, 27 Aug 1999
          02:22:52 -0500 (CDT)
Received: from auemlsrv.firewall.lucent.com (localhost [127.0.0.1]) by
          auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id DAA29901
          for <mobile-ip@hosaka.smallworks.com>; Fri, 27 Aug 1999 03:22:51
          -0400 (EDT)
Received: from ihgp4.ih.lucent.com (h135-1-27-104.lucent.com [135.1.27.104]) by
          auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id DAA29874
          for <mobile-ip@hosaka.smallworks.com>; Fri, 27 Aug 1999 03:22:49
          -0400 (EDT)
Received: by ihgp4.ih.lucent.com (8.8.8+Sun/EMS-1.4 sol2) id CAA08240; Fri, 27
          Aug 1999 02:22:27 -0500 (CDT)
Received: by ihgp4.ih.lucent.com (8.8.8+Sun/EMS-1.4 sol2) id OAA10063; Thu, 26
          Aug 1999 14:15:34 -0500 (CDT)
Original-From: bohdan@ihgp.ih.lucent.com
Content-Type: text
Message-ID:  <199908261915.OAA10063@ihgp4.ih.lucent.com>
Date:         Thu, 26 Aug 1999 14:15:34 -0500
Reply-To: bbodnar@LUCENT.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: bbodnar@LUCENT.COM
Subject:      [MOBILE-IP]
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

                         CALL FOR PAPERS
            Applied Telecommunication Symposium (ATS)

Part of the 2000 Advanced Simulation Technologies Conference (ASTC 2000)
                    April 16 through 20, 2000
                    Wyndham City Center Hotel
                        Washington, D.C.

     "Telecommunication Modeling, Analysis and Simulation --
                      Evolution for Change"

Part of 2000 Advanced Simulation Technologies Conference (ASTC 2000)

                        ATS Organizers:

General Chair  Dr. Bohdan Bodnar, Lucent Technologies, Inc.
               bbodnar@lucent.com
Co-chair       Dr. Ariel Sharon, Lucent Technologies, Inc.
               asharon@lucent.com
Program Chair  Dr. George Kraft, Illinois Institute of Technology
               kraft@stuart.iit.edu

The Applied Telecommunication Symposium (ATS) is an international
forum for the exchange of technical knowledge and presentation of
original papers on  analysis  of  telecommunication  systems  and
technologies.   It  is  intended  for  professionals,  engineers,
software developers, managers, and others interested in  cellular
and packet traffic characteristics, analysis of telecommunication
networks, and practitioners operating telecommunication networks.
We   are  looking  for  innovative  technical  papers  describing
projects,  applications,  and  research  and   development   work
pertinent to telecommunication.  The following tracks (with track
chairs listed) will be held; the topics are representative of the
track, but are not necessarily exclusive to that track:

                            WIRELESS

TRACK CHAIRS:  Dr. Hassan Rajeai,  Perfosim AB
               Dr. Mohsen Guizani, University of Missouri

- CDMA / TDMA
- GSM
- Third Generation Wireless
- Wireless Data
- Cell Traffic
- MSC Engineering

                 NETWORK MANAGEMENT AND SECURITY

TRACK CHAIRS:  Mr. Keith Stanley, Lucent Technologies, Inc.
               Dr. Axel Lehmann, Universitet der Bundeswehr Munchen

- Operations, Administration, Maintenance
- Overload control
- Load balancing
- Influence of security measures on network performance

           TELECOMMUNICATIONS BUSINESS AND REGULATION

TRACK CHAIRS:  Dr. George Kraft, Illinois Institute of Technology
               Mr. Howard, Bernett, Mitretek Corporation

- Cost modeling
- Call center operations
- Billing models
- E-commerce

                     NETWORKS AND MULTIMEDIA

TRACK CHAIRS:   Mr. Howard Bernett, Mitretek Corporation
                Dr. Kevin Ryan, Lucent Technologies, Inc.

- Internet
- Network performance
- Traffic characterization
- Packet switch architecture evaluation

                       MODELING TECHNIQUES

TRACK CHAIRS  Ms. Kamala Murti, Lucent Technologies, Inc.
              Dr. R. Radhakrishna Pillai, Kent Ridge Digital Labs

- Simulation techniques
- Acceleration methods
- Traffic synthesis
- Combined simulation/analytic procedures

PAPER SUBMISSION:

Abstracts  may  be  submitted  either   electronically   or   via
conventional  mail.   E-mail is preferred for abstract submission
(e-mail address: bbodnar@lucent.com); postscript,  Adobe  Acrobat
(.pdf)  format,  Word, or plaintext are preferred.  If submitting
via conventional mail, send the abstract to:

Dr. Bohdan Bodnar
Lucent Technologies, Inc.
2000 N Naperville Rd. Naperville, IL 60566, USA

The abstract must contain the following information:

- Names of all authors (identify the contact author)
- Affiliation of all authors
- E-mail addresses of all authors
- Conventional mail addresses of all authors
- First and second choice tracks

Reception of the abstract will be acknowledged via e-mail  within
three business days.

                        IMPORTANT DATES:

* Abstract/Draft Paper due                      October 31, 1999
* Notification of Acceptance sent               November 30, 1999
* Camera-ready Paper due                        January 8, 2000

Further information is available at
http://www.scs.org/confernc/astc00/text/ats-cfp.html

Sponsored by The Society for Computer Simulation International
P. O. Box 17900 San Diego, CA 92177-7900, USA
Tel 858-277-3888
Fax 858-277-3930
E-mail scs@scs.org
http://www.scs.org


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 27 03:46:12 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19202
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 27 Aug 1999 03:46:12 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.136F4350@standards.nortelnetworks.com>; Fri, 27 Aug 1999 3:41:41 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 61029 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 27 Aug 1999 03:39:55
          -0400
Received: from arthur.axion.bt.co.uk by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.D25CF010@standards.nortelnetworks.com>; Fri, 27 Aug 1999 3:39:52
          -0400
Received: from cbtlipnt02.btlabs.bt.co.uk by arthur (local) with ESMTP; Fri, 27
          Aug 1999 08:42:26 +0100
Received: by cbtlipnt02.btlabs.bt.co.uk with Internet Mail Service (5.5.2448.0)
          id <RVZYR9WM>; Fri, 27 Aug 1999 08:42:12 +0100
X-Mailer: Internet Mail Service (5.5.2448.0)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Message-ID:  <5104D4DBC598D211B5FE0000F8FE7EB202432766@mbtlipnt02.btlabs.bt.co.uk>
Date:         Fri, 27 Aug 1999 08:42:15 +0100
Reply-To: guilhem.ensuque@BT.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "G. Ensuque" <guilhem.ensuque@BT.COM>
Subject:      [MOBILE-IP] 3G RAN and IP mobility
X-To:         acasati@LUCENT.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Hi all

on the question of 3G frame selection/distribution...

I find it a bit ironical that it is the same team that has proposed AAL2
switching for the RAN in UMTS (I don't know how this is handled in
Cdma2000), and Cellular IP in this working group (Ericsson Traffic Analysis
and Network Performance Laboratory, Budapest, Hungary).

If I understand things correctly, the requirements for AAL2 switching in the
RAN come from the peculiarities of CDMA in outdoor operation (near-far
problem --> power control --> soft HO/macro diversity --> synchronisation
--> need to 'quickly' transport bit frames from the splitting point in the
RAN down to the BS in the active set)

I think it would be very interesting to compare the transport performance of
AAL2 switching and a 'per-host entry forwarding' scheme such as Cellular IP
or HAWAII... for use in a 3G RAN

Personally (<DISCLAIMER>this is not necessarily a BT view </DISCLAIMER>), I
think that AAL2 switching is very ugly in the RAN since it requires not only
an ATM stack, but also Ericsson's new AAL2 Switching stuff, which is an
additional layer of complication, and is horrendously based on an extension
of good old B-ISDN (urg!).

This complexity will prevent from using UMTS Node Bs (e.g. TDD mode) in a
private environment, and as already pointed out by Gerald Maguire, it would
be nice to handle the mobility in pico cellular environments (WLAN,
HiperLAN, DECT, UMTS TDD...) with an IP-based scheme.

So if we can find an IP scheme that handles the requirements of CDMA, I
think we would hold the Holy Grail of 4G mobile communications. The
requirements on the transport protocol in the RAN are (from a paper I am
currently writing) are:

1.      The transport protocol must provide on-demand connectivity from any
RNC (~BSC) to arbitrary 'neighbour' Node Bs (~BTS) or RNCs.
2.      During handover, connectivity between the S-RNC (the RNC that does
the frame selection) and new members of an MT's active set must be
established within the delay bounds implied by the subscribed-to end-to-end
QoS (in the case of voice service, this may require association setup times
of less than e.g. 100ms).
3.      The transport protocol must provide tight synchronisation of L1 bit
frames transmitted on diversity sub-paths from the splitting point in the
downlink direction, so that radio Tx is synchronised between the Node Bs in
the active set (this may require to determine and guarantee an appropriate
delay/jitter behaviour on the diversity sub-paths). Uplink transport of bit
frames from the Node Bs to the combining point may not require such a tight
synchronisation, depending on the subscribed-to QoS for the upper layer
end-to-end service.
4.      The transport protocol must be able to meet the aggregate QoS
requirements of all MS's connected to the UTRAN.
Sorry, I have gotten a bit long...

BTW, Gerald, do you have an URL for the ICEBERG stuff ?

Guilhem Ensuque

Mobility Futures Unit                           guilhem.ensuque@bt.com
B55-131B
BT Advanced Communications Technology Centre
Adastral Park, Martlesham Heath
IPSWICH IP5 3RE                              Tel: +44 1473 645 232
UK                                                   Fax: +44 1473 646 885



> -----Original Message-----
> From: Casati, Alessio (Alessio) [SMTP:acasati@LUCENT.COM]
> Sent: 26 August 1999 23:50
> To:   MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
> Subject:      Re: [MOBILE-IP] I-D
> ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
>
> Gerald,
>
> > While this was perhaps true in 2G, it need not be true for all
> > 3G. Especially if basestations are connected via IP (such as in the
> > case of ICEBERG) - why should you carry all this traffic up to a few
> > choke points - rather than route it as directly as possible.
> >
> On the contrary TDMA systems (GSM/EDGE/ANSI136) may be
> more amenable than
> UMTS and CDMA2000 (CDMA based 3G) in handling IP close to the
> BTS.
>
> This is due to the 3G RAN architectures
> that foresee the need of a frame selector/distributor
> to handle soft handover.
>
> Economical (and performance) reasons suggest the
> frame selector/distributor not to cover a very limited area.
>
> Hence IP will 'emerge' from the lower layers at points
> among which it's safe to state handoffs cannot occur very
> frequently.
>
> [...]
>
> > In an environment where there is a mix of WLAN and 2G (or 3G) overlays
> > - the mobility will have to be handled at the IP layer - since the
> > link layers can't talk to each other directly.
> >
> It's a fair one.
> Anyway it's quite a common understanding
> that intersystem HO should be possibly
> "rate limited", not to mention
> interdomain&system HO.
>
> > So I am not convinced that the rate of handoffs will be all that
> > low. Considering that I walk through at least 3 different DECT
> > environments when I walk 150m to the nearest hot dog vendor - I would
> > expect that in the future there will be at least this number of Mobile
> > IP networks that I will walk through.
> >
> I don't expect one to experience too frequent
> HO in going to a Hot dogs
> vendor, unless one is really hungry
> (in which case HO disruptions may not be what
> one would really most care about :).
>
> Alessio


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 27 05:17:11 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21149
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 27 Aug 1999 05:17:11 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.CBB86CA0@standards.nortelnetworks.com>; Fri, 27 Aug 1999 5:12:44 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 61068 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 27 Aug 1999 05:11:22
          -0400
Received: from sirius.ctr.columbia.edu by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.9A741EA0@standards.nortelnetworks.com>; Fri, 27 Aug 1999 5:11:22
          -0400
Received: from comet.columbia.edu (sweetpea.comet.columbia.edu [128.59.68.61])
          by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) with ESMTP id FAA03734;
          Fri, 27 Aug 1999 05:14:51 -0400 (EDT)
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
References: <5104D4DBC598D211B5FE0000F8FE7EB202432766@mbtlipnt02.btlabs.bt.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID:  <37C683E3.42751EA7@comet.columbia.edu>
Date:         Fri, 27 Aug 1999 05:26:11 -0700
Reply-To: campbell@comet.columbia.edu
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "Andrew T. Campbell" <campbell@comet.columbia.edu>
Organization: Center for Telecommunications Research
Subject:      Re: [MOBILE-IP] 3G RAN and IP mobility
X-To:         guilhem.ensuque@BT.COM
X-cc:         cellularip@comet.columbia.edu
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

Hello  Guilhem:

"G. Ensuque" wrote:
>
> Hi all
>
> on the question of 3G frame selection/distribution...
>
> I find it a bit ironical that it is the same team that has proposed AAL2
> switching for the RAN in UMTS (I don't know how this is handled in
> Cdma2000), and Cellular IP in this working group (Ericsson Traffic Analysis
> and Network Performance Laboratory, Budapest, Hungary).
>

For the record your irony is tadd misplaced old chap.

Cellular IP is a project between Columbia University
with support from industry. Cellular IP has no notion of
circuits/ adaptation layers or influence there of. Its a layer
3 routing protocol that supports fast handoff
and passive connectivity for packet data developed at
Columbia initially with Andras Valko (Ericsson) and other Ph.D.
students including Javier Gomez, Chieh-Yih Wan and
Sanghyo Kim. It is a key part of Andras'
thesis which he completed at Columbia. His thesis
will be available later this fall on the Cellular IP
web page - once he is through the process.

The Cellular IP Project at Columbia
has nothing to do with AAL2 or the push for
that in RAN. Cellular IP and ATM/AAL2 in
the same breath - what a slur ;-)

As a footnote Columbia University will release the source code
for Cellular IP to the public domain this fall and hope to
demonstrate the network at MOMUC99. The code for the testbed and
NS2 environments will be available as freeware. The Cellular IP Project
at Columbia is broadly investigating the notion of a
"IP-based mobile telecommunication networks" that take a different
tact from 2.5/3G approaches. We are working on support for
wireless IP QOS and middleware services. The Cellular IP project
is more broadly supported by Ericsson, Intel and IBM.

On a *personal* note I think ATM/signaling is a very poor choice for the
RAN
and wireless in general. Cellular IP's soft-state
routing/switching would give good handoff performance
and one can build wireless IP QOS on that foundation too.
In addition there is no explicit signaling; so
SS7 et al evaporates. I have always considered
that Cellular IP could be refined for the mobile, RAN, core and
gateways as a basic transport and (in-band) signaling technology.

We have recently published a paper on some simulation results
of the protocol. We hope to publish results from our testbed
demonstrator (which are very promising in terms of performance)
in due course.

The NS2 paper is not on our project page but you will find the
PDF file on my pubs page. Look for:

"On the Analysis of Cellular IP Access Networks" , Proc. 6th IFIP
International
Workshop on Protocols for High Speed Networks , Salem, 25-27 August
1999.

Thanks for listening.

--
Andrew
http://comet.columbia.edu/~campbell


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 27 05:32:39 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21415
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 27 Aug 1999 05:32:38 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.E5EE8F30@standards.nortelnetworks.com>; Fri, 27 Aug 1999 5:27:47 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 61103 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 27 Aug 1999 05:25:52
          -0400
Received: from babelfish.axion.bt.co.uk by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.A1085090@standards.nortelnetworks.com>; Fri, 27 Aug 1999 5:25:52
          -0400
Received: from cbtlipnt02.btlabs.bt.co.uk by babelfish.axion.bt.co.uk (local)
          with ESMTP; Fri, 27 Aug 1999 10:28:43 +0100
Received: by cbtlipnt02.btlabs.bt.co.uk with Internet Mail Service (5.5.2448.0)
          id <RVZYSBGL>; Fri, 27 Aug 1999 10:28:27 +0100
X-Mailer: Internet Mail Service (5.5.2448.0)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Message-ID:  <5104D4DBC598D211B5FE0000F8FE7EB202432767@mbtlipnt02.btlabs.bt.co.uk>
Date:         Fri, 27 Aug 1999 10:28:30 +0100
Reply-To: guilhem.ensuque@BT.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "G. Ensuque" <guilhem.ensuque@BT.COM>
Subject:      Re: [MOBILE-IP] 3G RAN and IP mobility
X-To:         campbell@comet.columbia.edu
X-cc:         cellularip@comet.columbia.edu
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Andrew,

Sorry for the irony, I don't want to ignite a flame war and I should have
acknowledged the fact Cellular IP comes from Columbia.

Especially that I totally agree with your views and have great hopes for
technologies like cellular IP which I think have the potential to provide a
unified IP mobility mechanism for the future heterogeneous wireless
environment where macro CDMA (FDD) will co-habit with both kegacy TDMA 2G
and pico cellular '4G' such as TDD-CDMA, Hiperlan (1 and 2), IEEE 802.11 at
5GHz, Bluetooth...

My comment came from the fact that I find AAL2 switching horrible and that
the rationale behind it is supported by people from the same Hungarian team
as Andras Valko:

see 'Applying ATM/AAL2 as a Switching Technology in 3rd Generation Mobile
Access Networks' IEEE Comms Mag, June 99, by G. Eneroth, G. Fodor, G.
Leijonhufvud, A. Racz, I. Szabo

A paper by Andras Valko is even referenced to support AAL2 switching ('Voice
QoS in 3rd Generation Mobile Systems' by A. Valko, A. Racz and G. Fodor, to
appear in JSAC)

Guilhem

> -----Original Message-----
> From: Andrew T. Campbell [SMTP:campbell@comet.columbia.edu]
> Sent: 27 August 1999 13:26
> To:   guilhem.ensuque@BT.COM
> Cc:   MOBILE-IP@STANDARDS.NORTELNETWORKS.COM;
> cellularip@comet.columbia.edu
> Subject:      Re: [MOBILE-IP] 3G RAN and IP mobility
>
>
> Hello  Guilhem:
>
> "G. Ensuque" wrote:
> >
> > Hi all
> >
> > on the question of 3G frame selection/distribution...
> >
> > I find it a bit ironical that it is the same team that has proposed AAL2
> > switching for the RAN in UMTS (I don't know how this is handled in
> > Cdma2000), and Cellular IP in this working group (Ericsson Traffic
> Analysis
> > and Network Performance Laboratory, Budapest, Hungary).
> >
>
> For the record your irony is tadd misplaced old chap.
>
> Cellular IP is a project between Columbia University
> with support from industry. Cellular IP has no notion of
> circuits/ adaptation layers or influence there of. Its a layer
> 3 routing protocol that supports fast handoff
> and passive connectivity for packet data developed at
> Columbia initially with Andras Valko (Ericsson) and other Ph.D.
> students including Javier Gomez, Chieh-Yih Wan and
> Sanghyo Kim. It is a key part of Andras'
> thesis which he completed at Columbia. His thesis
> will be available later this fall on the Cellular IP
> web page - once he is through the process.
>
> The Cellular IP Project at Columbia
> has nothing to do with AAL2 or the push for
> that in RAN. Cellular IP and ATM/AAL2 in
> the same breath - what a slur ;-)
>
> As a footnote Columbia University will release the source code
> for Cellular IP to the public domain this fall and hope to
> demonstrate the network at MOMUC99. The code for the testbed and
> NS2 environments will be available as freeware. The Cellular IP Project
> at Columbia is broadly investigating the notion of a
> "IP-based mobile telecommunication networks" that take a different
> tact from 2.5/3G approaches. We are working on support for
> wireless IP QOS and middleware services. The Cellular IP project
> is more broadly supported by Ericsson, Intel and IBM.
>
> On a *personal* note I think ATM/signaling is a very poor choice for the
> RAN
> and wireless in general. Cellular IP's soft-state
> routing/switching would give good handoff performance
> and one can build wireless IP QOS on that foundation too.
> In addition there is no explicit signaling; so
> SS7 et al evaporates. I have always considered
> that Cellular IP could be refined for the mobile, RAN, core and
> gateways as a basic transport and (in-band) signaling technology.
>
> We have recently published a paper on some simulation results
> of the protocol. We hope to publish results from our testbed
> demonstrator (which are very promising in terms of performance)
> in due course.
>
> The NS2 paper is not on our project page but you will find the
> PDF file on my pubs page. Look for:
>
> "On the Analysis of Cellular IP Access Networks" , Proc. 6th IFIP
> International
> Workshop on Protocols for High Speed Networks , Salem, 25-27 August
> 1999.
>
> Thanks for listening.
>
> --
> Andrew
> http://comet.columbia.edu/~campbell


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 27 05:39:07 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21456
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 27 Aug 1999 05:39:06 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.E2295460@standards.nortelnetworks.com>; Fri, 27 Aug 1999 5:34:51 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 61145 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 27 Aug 1999 05:33:27
          -0400
Received: from sirius.ctr.columbia.edu by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.AFEAC7E0@standards.nortelnetworks.com>; Fri, 27 Aug 1999 5:33:26
          -0400
Received: from comet.columbia.edu (sweetpea.comet.columbia.edu [128.59.68.61])
          by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) with ESMTP id FAA04105;
          Fri, 27 Aug 1999 05:36:22 -0400 (EDT)
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
References: <5104D4DBC598D211B5FE0000F8FE7EB202432767@mbtlipnt02.btlabs.bt.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID:  <37C688EE.67207AC3@comet.columbia.edu>
Date:         Fri, 27 Aug 1999 05:47:42 -0700
Reply-To: campbell@comet.columbia.edu
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "Andrew T. Campbell" <campbell@comet.columbia.edu>
Organization: Center for Telecommunications Research
Subject:      Re: [MOBILE-IP] 3G RAN and IP mobility
X-To:         guilhem.ensuque@bt.com
X-cc:         cellularip@comet.columbia.edu
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

I once worked on ATM, before that x.25, before that I
built sand castles on the beach an Blackpool. So what!

guilhem.ensuque@bt.com wrote:
>
> Andrew,
>
> Sorry for the irony, I don't want to ignite a flame war and I should have
> acknowledged the fact Cellular IP comes from Columbia.
>
> Especially that I totally agree with your views and have great hopes for
> technologies like cellular IP which I think have the potential to provide a
> unified IP mobility mechanism for the future heterogeneous wireless
> environment where macro CDMA (FDD) will co-habit with both kegacy TDMA 2G
> and pico cellular '4G' such as TDD-CDMA, Hiperlan (1 and 2), IEEE 802.11 at
> 5GHz, Bluetooth...
>
> My comment came from the fact that I find AAL2 switching horrible and that
> the rationale behind it is supported by people from the same Hungarian team
> as Andras Valko:
>
> see 'Applying ATM/AAL2 as a Switching Technology in 3rd Generation Mobile
> Access Networks' IEEE Comms Mag, June 99, by G. Eneroth, G. Fodor, G.
> Leijonhufvud, A. Racz, I. Szabo
>
> A paper by Andras Valko is even referenced to support AAL2 switching ('Voice
> QoS in 3rd Generation Mobile Systems' by A. Valko, A. Racz and G. Fodor, to
> appear in JSAC)
>
> Guilhem
>
> > -----Original Message-----
> > From: Andrew T. Campbell [SMTP:campbell@comet.columbia.edu]
> > Sent: 27 August 1999 13:26
> > To:   guilhem.ensuque@BT.COM
> > Cc:   MOBILE-IP@STANDARDS.NORTELNETWORKS.COM;
> > cellularip@comet.columbia.edu
> > Subject:      Re: [MOBILE-IP] 3G RAN and IP mobility
> >
> >
> > Hello  Guilhem:
> >
> > "G. Ensuque" wrote:
> > >
> > > Hi all
> > >
> > > on the question of 3G frame selection/distribution...
> > >
> > > I find it a bit ironical that it is the same team that has proposed AAL2
> > > switching for the RAN in UMTS (I don't know how this is handled in
> > > Cdma2000), and Cellular IP in this working group (Ericsson Traffic
> > Analysis
> > > and Network Performance Laboratory, Budapest, Hungary).
> > >
> >
> > For the record your irony is tadd misplaced old chap.
> >
> > Cellular IP is a project between Columbia University
> > with support from industry. Cellular IP has no notion of
> > circuits/ adaptation layers or influence there of. Its a layer
> > 3 routing protocol that supports fast handoff
> > and passive connectivity for packet data developed at
> > Columbia initially with Andras Valko (Ericsson) and other Ph.D.
> > students including Javier Gomez, Chieh-Yih Wan and
> > Sanghyo Kim. It is a key part of Andras'
> > thesis which he completed at Columbia. His thesis
> > will be available later this fall on the Cellular IP
> > web page - once he is through the process.
> >
> > The Cellular IP Project at Columbia
> > has nothing to do with AAL2 or the push for
> > that in RAN. Cellular IP and ATM/AAL2 in
> > the same breath - what a slur ;-)
> >
> > As a footnote Columbia University will release the source code
> > for Cellular IP to the public domain this fall and hope to
> > demonstrate the network at MOMUC99. The code for the testbed and
> > NS2 environments will be available as freeware. The Cellular IP Project
> > at Columbia is broadly investigating the notion of a
> > "IP-based mobile telecommunication networks" that take a different
> > tact from 2.5/3G approaches. We are working on support for
> > wireless IP QOS and middleware services. The Cellular IP project
> > is more broadly supported by Ericsson, Intel and IBM.
> >
> > On a *personal* note I think ATM/signaling is a very poor choice for the
> > RAN
> > and wireless in general. Cellular IP's soft-state
> > routing/switching would give good handoff performance
> > and one can build wireless IP QOS on that foundation too.
> > In addition there is no explicit signaling; so
> > SS7 et al evaporates. I have always considered
> > that Cellular IP could be refined for the mobile, RAN, core and
> > gateways as a basic transport and (in-band) signaling technology.
> >
> > We have recently published a paper on some simulation results
> > of the protocol. We hope to publish results from our testbed
> > demonstrator (which are very promising in terms of performance)
> > in due course.
> >
> > The NS2 paper is not on our project page but you will find the
> > PDF file on my pubs page. Look for:
> >
> > "On the Analysis of Cellular IP Access Networks" , Proc. 6th IFIP
> > International
> > Workshop on Protocols for High Speed Networks , Salem, 25-27 August
> > 1999.
> >
> > Thanks for listening.
> >
> > --
> > Andrew
> > http://comet.columbia.edu/~campbell

--
Andrew
http://comet.columbia.edu/~campbell


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 27 05:57:12 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21545
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 27 Aug 1999 05:57:12 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.6747A0F0@standards.nortelnetworks.com>; Fri, 27 Aug 1999 5:52:53 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 61176 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 27 Aug 1999 05:51:28
          -0400
Received: from dent.axion.bt.co.uk by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.34A26360@standards.nortelnetworks.com>; Fri, 27 Aug 1999 5:51:28
          -0400
Received: from cbtlipnt01.btlabs.bt.co.uk by dent (local) with ESMTP; Fri, 27
          Aug 1999 10:53:43 +0100
Received: by cbtlipnt01.btlabs.bt.co.uk with Internet Mail Service (5.5.2448.0)
          id <QL8D7RM0>; Fri, 27 Aug 1999 10:53:42 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Message-ID:  <5104D4DBC598D211B5FE0000F8FE7EB202432768@mbtlipnt02.btlabs.bt.co.uk>
Date:         Fri, 27 Aug 1999 10:53:24 +0100
Reply-To: guilhem.ensuque@BT.COM
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "G. Ensuque" <guilhem.ensuque@BT.COM>
Subject:      Re: [MOBILE-IP] 3G RAN and IP mobility
X-To:         campbell@comet.columbia.edu
X-cc:         cellularip@comet.columbia.edu
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Andrew

OK, OK ... I am maybe a bit young and naive. Sorry for all the fuss...
But please, don't let the irony overshadow the main point:

I don't want the company I am working for to buy loads of ATM switches just
because an old-fashioned idea from researchers that have now changed their
focus has been adopted in the 3GPP standards, and then find out that there
is a better, cheaper, more efficient solution that is available in the same
timeframe.

Clearly, what would be great to work towards is a protocol that can replace
AAL2 switching in the RAN and integrates well with the rest of the Internet.
Cellular IP or HAWAI are major steps in that direction.

What is important is the performance issue, so could we discuss the
following requirements:

1.      The transport protocol must provide on-demand connectivity from any
RNC (~BSC) to arbitrary 'neighbour' Node Bs (~BTS) or RNCs.
2.      During handover, connectivity between the S-RNC (the RNC that does
the frame selection) and new members of an MT's active set must be
established within the delay bounds implied by the subscribed-to end-to-end
QoS (in the case of voice service, this may require association setup times
of less than e.g. 100ms).
3.      The transport protocol must provide tight synchronisation of L1 bit
frames transmitted on diversity sub-paths from the splitting point in the
downlink direction, so that radio Tx is synchronised between the Node Bs in
the active set (this may require to determine and guarantee an appropriate
delay/jitter behaviour on the diversity sub-paths). Uplink transport of bit
frames from the Node Bs to the combining point may not require such a tight
synchronisation, depending on the subscribed-to QoS for the upper layer
end-to-end service.
4.      The transport protocol must be able to meet the aggregate QoS
requirements of all MS's connected to the UTRAN.



> -----Original Message-----
> From: Andrew T. Campbell [SMTP:campbell@comet.columbia.edu]
> Sent: 27 August 1999 13:48
> To:   guilhem.ensuque@bt.com
> Cc:   MOBILE-IP@STANDARDS.NORTELNETWORKS.COM;
> cellularip@comet.columbia.edu
> Subject:      Re: [MOBILE-IP] 3G RAN and IP mobility
>
>
> I once worked on ATM, before that x.25, before that I
> built sand castles on the beach an Blackpool. So what!
> http://comet.columbia.edu/~campbell


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 27 06:39:18 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21785
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 27 Aug 1999 06:39:18 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.474A7BF0@standards.nortelnetworks.com>; Fri, 27 Aug 1999 6:34:56 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 61216 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 27 Aug 1999 06:33:47
          -0400
Received: from ihemlsrv.firewall.lucent.com (192.11.222.161) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.1DE01130@standards.nortelnetworks.com>; Fri, 27 Aug 1999
          6:33:47 -0400
Received: from ihemlsrv.firewall.lucent.com (localhost [127.0.0.1]) by
          ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id GAA12098
          for <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Fri, 27 Aug 1999
          06:37:25 -0400 (EDT)
Received: from uk0006exch001p.wins.lucent.com (h135-86-160-146.lucent.com
          [135.86.160.146]) by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3)
          with ESMTP id GAA12083 for <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>;
          Fri, 27 Aug 1999 06:37:25 -0400 (EDT)
Received: by uk0006exch001p.uk.lucent.com with Internet Mail Service
          (5.5.2448.0) id <RWMN6F7D>; Fri, 27 Aug 1999 11:37:17 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Message-ID:  <976F7C55E3B2D111A0720008C728549C020A47D3@en0060exch001u.uk.lucent.com>
Date:         Fri, 27 Aug 1999 11:37:22 +0100
Reply-To: "Casati, Alessio (Alessio)" <acasati@LUCENT.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: "Casati, Alessio (Alessio)" <acasati@LUCENT.COM>
Subject:      Re: [MOBILE-IP] 3G RAN and IP mobility
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

I think that a protocol that satisfies the requirements is
right AAL2 :)

For instance, that radio frames must be transported on links between the
RNC/SDU and the RF gear and IP on its own, without AAL2 equivalent
multiplexing functionality built on top of that, can't do much.

Anyway, this discussion is not particularly fitting in the Mobile IP
list context :).

Since access networks are (have been) defined elsewhere, here we have
to define how to support mobility among them. It's the case that for now
(and for good) we are likely not to need smarter things than
a previous FA extension to make MIP perform well.

In the future there will be certainly time to discuss about
other aspects that we don't have to cope with now.


alessio


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 27 08:02:38 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24231
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 27 Aug 1999 08:02:38 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.E3A025D0@standards.nortelnetworks.com>; Fri, 27 Aug 1999 7:58:03 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 61307 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 27 Aug 1999 07:56:45
          -0400
Received: from mail.cc.hut.fi by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.B4A66410@standards.nortelnetworks.com>; Fri, 27 Aug 1999 7:56:44
          -0400
Received: from gamma.hut.fi (tweckstr@gamma.hut.fi [130.233.224.52]) by
          mail.cc.hut.fi (8.9.3/8.9.3) with ESMTP id PAA21477; Fri, 27 Aug 1999
          15:00:19 +0300 (EET DST)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Message-ID:  <Pine.OSF.4.10.9908271435490.31359-100000@gamma.hut.fi>
Date:         Fri, 27 Aug 1999 15:00:18 +0300
Reply-To: =?ISO-8859-1?Q?Tom_Weckstr=F6m?= <tweckstr@CC.HUT.FI>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: =?ISO-8859-1?Q?Tom_Weckstr=F6m?= <tweckstr@CC.HUT.FI>
Subject:      Re: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
X-To:         Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <19990826224359.B82B257013@king.research.bell-labs.com>
Content-Transfer-Encoding: 8BIT

        Hello all and Pete,

I am glad the new regional tunneling draft has had such a stimulating
effect on the discussions of Mobile IP mailing list. :-)

A hierarchical MIP is not a piece of cake, we all know that for sure.
I believe the hierarchical solution has its advantages that are worth
striving for regardless of the complex questions involved.

Pete, this one from your comments amazed me:

On Thu, 26 Aug 1999, Pete McCann wrote:

mccap >In any case, assuming we have the Previous FA functionality working,
mccap >we have already eliminated the latency of the FA-HA roundtrip from the
mccap >interval between handoff and data reception.  In this case
mccap >regionalized handoffs only contribute a reduction in traffic to and
mccap >load at the HA.

Eliminating the latency of FA-HA roundtrip is just one of the advantages
of the hierarchical model. I do not know the "Previous FA functionality"
very well, but I assume it doesn't provide the other advantages that the
hierarchical model has.

The reduction of signaling traffic is a very important advantage of the
hierarchical model.
Imagine, thousands of Mobile Nodes roaming in a congress center or at an
airport, for example. It would be too much asked to order people turn
their MNs off while they rush for presentations or their flights. This
kind of mobility would create quite a lot of signaling traffic. This
traffic would unnecessarily load both the agents of the MIP system and the
Internet in general, if non-hierarchical model was used.

One can always argue that all the services foreign and home agents
can be clustered or otherwise load balanced, but shouldn't we look for a
model where such tricks are no longer needed? Furthermore, this approach
would not save us from loading the Internet core with MIP signaling.

mccap >  Maybe what is needed is not a hierarchical tunneling
mccap >approach but rather a way to regulate the rate at which location
mccap >updates are forwarded to the HA.

You are right - partly. ;-)
Namely, we do need a method for reducing the number of location update
messages that travel through the Internet from foreign network to the HA,
but there already is a solution at hand - it is the hierarchical Mobile
IP. :-)

Comments are welcome.

Best regards,
                Tom


--
        Tom Weckström           Dynamics group
                                Helsinki University of Technology
                                dynamics@cs.hut.fi
                                http://www.cs.hut.fi/Research/Dynamics/


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 27 10:57:53 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04366
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 27 Aug 1999 10:57:53 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.65B1CCA0@standards.nortelnetworks.com>; Fri, 27 Aug 1999 10:53:29 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 61660 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 27 Aug 1999 10:52:21
          -0400
Received: from dirty.research.bell-labs.com by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.3D1B7AC0@standards.nortelnetworks.com>; Fri, 27 Aug 1999 10:52:21
          -0400
Received: from scummy.research.bell-labs.com ([135.104.2.10]) by dirty; Fri Aug
          27 10:54:51 EDT 1999
Received: from king.research.bell-labs.com ([135.1.152.1]) by scummy; Fri Aug
          27 10:54:50 EDT 1999
Received: from notmafia.research.bell-labs.com.research.bell-labs.com (notmafia
          [135.1.152.230]) by king.research.bell-labs.com (Postfix) with SMTP
          id 0A97157013; Fri, 27 Aug 1999 09:54:51 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <19990826224359.B82B257013@king.research.bell-labs.com>
            <Pine.OSF.4.10.9908271435490.31359-100000@gamma.hut.fi>
X-Mailer: VM 6.33 under Emacs 19.34.2
Message-ID:  <19990827145452.0A97157013@king.research.bell-labs.com>
Date:         Fri, 27 Aug 1999 09:54:52 -0500
Reply-To: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Subject:      Re: [MOBILE-IP] I-D ACTION:draft-ietf-mobileip-reg-tunnel-01.txt
X-To:         =?ISO-8859-1?Q?Tom_Weckstr=F6m?= <tweckstr@cc.hut.fi>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <Pine.OSF.4.10.9908271435490.31359-100000@gamma.hut.fi>
Content-Transfer-Encoding: 7bit

Hi, Tom,

=?ISO-8859-1?Q?Tom_Weckstr=F6m?= <tweckstr@cc.hut.fi> (TW) writes:

TW> Pete, this one from your comments amazed me:

I certainly didn't intend to amaze anyone... perhaps I was a little bit
unclear.

TW> On Thu, 26 Aug 1999, Pete McCann wrote:

mccap> In any case, assuming we have the Previous FA functionality working,
mccap> we have already eliminated the latency of the FA-HA roundtrip from the
mccap> interval between handoff and data reception.  In this case
mccap> regionalized handoffs only contribute a reduction in traffic to and
mccap> load at the HA.

TW> Eliminating the latency of FA-HA roundtrip is just one of the advantages
TW> of the hierarchical model. I do not know the "Previous FA functionality"
TW> very well, but I assume it doesn't provide the other advantages that the
TW> hierarchical model has.

TW> The reduction of signaling traffic is a very important advantage of the
TW> hierarchical model.
TW> Imagine, thousands of Mobile Nodes roaming in a congress center or at an
TW> airport, for example. It would be too much asked to order people turn
TW> their MNs off while they rush for presentations or their flights. This
TW> kind of mobility would create quite a lot of signaling traffic. This
TW> traffic would unnecessarily load both the agents of the MIP system and the
TW> Internet in general, if non-hierarchical model was used.

My original point still holds - I named two advantages to the regional
schemes, and you haven't brought up any new ones.  One is eliminating
latency of a handoff (the time between handoff and traffic reception),
and the other is reduction in signaling messages across the global
Internet and at the HA.  I claimed above that the Previous FA
extension can be used to provide the first feature.  Now let's talk
about the second.

TW> One can always argue that all the services foreign and home agents
TW> can be clustered or otherwise load balanced, but shouldn't we look for a
TW> model where such tricks are no longer needed? Furthermore, this approach
TW> would not save us from loading the Internet core with MIP signaling.

I agree (partially) - I wasn't advocating that we increase the
capacity of the HAs to deal with increased traffic.  Let me point out,
though, that FAs are faced with all the signaling traffic even in the
regional schemes.

mccap>   Maybe what is needed is not a hierarchical tunneling
mccap> approach but rather a way to regulate the rate at which location
mccap> updates are forwarded to the HA.

TW> You are right - partly. ;-)
TW> Namely, we do need a method for reducing the number of location update
TW> messages that travel through the Internet from foreign network to the HA,
TW> but there already is a solution at hand - it is the hierarchical Mobile
TW> IP. :-)

Sure, these schemes are one way to reduce traffic, but there may be
others.  For instance, what if we added a flag to a registration
request that said, "don't propagate this request to the HA just yet".
These kinds of registrations would contain only the Previous FA
extension.  Then the MN could selectively (according to some
predefined rate) send registrations to the HA or the previous FA as
needed and according to whatever load the HA could handle.  This seems
like a much simpler approach than the hierarchical tunnels and also
eliminates the centralized GFA that must de-tunnel/re-tunnel all
traffic passing through it.

-Pete


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Fri Aug 27 22:12:01 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20960
	for <mobileip-archive@LISTS.IETF.ORG>; Fri, 27 Aug 1999 22:12:00 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.8A56D060@standards.nortelnetworks.com>; Fri, 27 Aug 1999 22:07:23 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 62836 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Fri, 27 Aug 1999 22:05:59
          -0400
Received: from mail.cc.hut.fi by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.F23BB760@standards.nortelnetworks.com>; Fri, 27 Aug 1999 21:55:59
          -0400
Received: from beta.hut.fi (jtm@beta.hut.fi [130.233.224.51]) by mail.cc.hut.fi
          (8.9.3/8.9.3) with ESMTP id EAA28276; Sat, 28 Aug 1999 04:59:38 +0300
          (EET DST)
Received: (from jtm@localhost) by beta.hut.fi (8.9.1a/8.9.1) id EAA23668; Sat,
          28 Aug 1999 04:59:38 +0300 (EET DST)
X-Mailer: ELM [version 2.4 PL21]
Content-Type: text
Message-ID:  <199908280159.EAA23668@beta.hut.fi>
Date:         Sat, 28 Aug 1999 04:59:36 +0200
Reply-To: Jari T Malinen <jtm@CC.HUT.FI>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Jari T Malinen <jtm@CC.HUT.FI>
Subject:      Re: [MOBILE-IP] Darwinian evolution of proxy tunnelling...
X-To:         mccap@RESEARCH.BELL-LABS.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <19990826190549.8092757037@king.research.bell-labs.com> from
              "Pete McCann" at Aug 26, 99 02:05:49 pm

Hello, Pete

First, let me state that I find your design elegant in simplicity and
that I still have wishes for improvement for the regional tunneling
(not to speak of our implementation). However, I still also have
questions about your design.

> >> that the recent "Regionalized Tunnel" draft is on a separate branch.
> >> The key distinguishing feature is that of transparency.
>
> JTM> I would also like to mention another important distinguishing point,
> JTM> the separation of concerns. The regionalized tunnel mgmt. draft does
> JTM> not seem to assume any special support from the link-level.
>
> By the way, neither does THEMA - it simply propagates a unique
> identifier back to the GFA.

Correct me if I am wrong, bud doesn't it occur in THEMA that a lowest
SFA forwards packets based on link-layer address of the MN? Is this
not against requirements for IPv4 routers?

Longer explanation: My earlier term "Special requirements for the
link-layer" is perhaps inaccurate. I mean there is the requirement for
first-hop routing to be based on link-layer addresses (and isn't the
possibility to support private MN addresses with FA decapsulation on
the same link based on this?).  Put in implementor's terms: at least
in Linux's IPv4 "policy-based routing" that has comments on being "as
specified in RFC 1812" (Class trees in Chap. 5.2.4.3), it seems
problematic (but maybe doable) to have rule-based routing using a link
address.  Is it not the case that RFC 1812 does not require
link-address-based routing from conformant routers but rather
separates the concerns there?

Another question stemming from the use of link-layer in identification
of the endpoint in THEMA: FA caches the bindings by a link-layer address
identifier.  If we tech-roam between two SFAs connected to the same FA,
e.g. from DSSS WLAN to IrDA so that our link-address changes, do we not
experience the FA-HA latency in THEMA while not in the regional tunneling?

> I don't think either of the proposals are intended to be used across
> administrative domains.  THEMA was certainly intended to be used with
> diverse link-layers; in fact it decouples the link-layer specific
> equipment from the (somewhat complex) FA functionality with a fairly
> simple interface.  In contrast, the leaf FAs in the regionalized
> tunnel approach need to implement the whole range of FA functionality
> including dealing with authentication servers - an area that is
> rapidly changing, to say the least.

Maybe, though the use of CAs should probably not be a requirement but
an option used when the policy of the access network needs AAA-based security?
The machinery could be thought to be there for making multiple alternatives
for security and configuration (we need not change implementation when
splitting/joining components to regional structures, a very simple
reconfiguration of a similar component is sufficient, this from the
"administrator's point of view").. When speaking of logical components, I
think you are right, the lower FA as such may have less use for some
parts of the FA functionality.

> Yes, this latency is an issue, which is why we need the Previous FA
> extension or networks that support simultaneous dual connectivity for
> smooth handoff.

Yes we may use both of these, or hierarchies, or a combination of them.
They reflect different approaches with pros and cons in both, perhaps?
Regional tunneling, by the way, can be used with the route optimization.

> >> I am not convinced that the complexity of tree-like "regional
> >> mobility" solutions are really justified.
>
> JTM> I also hope we could have a very simple protocol.  Maybe your
> JTM> consideration is true in some environments, but what if we add the
> JTM> private networks, must we guarantee communication among all FAs that
> JTM> are in separate private or protected access networks as might be
> JTM> needed with the PFA extension? We might want to use private address
> JTM> spaces for access point FAs just to minimize the use of public
> JTM> addresses in the access network organization.
>
> All the more reason to keep those FAs invisible to the MNs.  Think
> about it - do you really want your first-hop IP router to have a
> private address, when you are accessing the public Internet or a
> private network with a completely different address space?

True, a first hop address can hide a public address, if any private
intranet address. But, if we want to conserve addresses, maybe a
private Internet-address (local?), e.g. 10.*.*.*, can be reused
several times over as the first-hop address with no danger for
ambiguity for public-network Mobile IP, while a similar range could
be defined a "private" intranet subspace (i.e. when the CN is from
an intranet).



Regards,

--jari


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Sun Aug 29 09:25:02 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29424
	for <mobileip-archive@LISTS.IETF.ORG>; Sun, 29 Aug 1999 09:25:02 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.BA3E6B80@standards.nortelnetworks.com>; 29 Aug 1999 9:20:25 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 63586 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Sun, 29 Aug 1999 09:18:29
          -0400
Received: from leonis.nus.edu.sg by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.0F0251B0@standards.nortelnetworks.com>; 29 Aug 1999 9:08:28 -0400
Received: from localhost (engp7643@localhost) by leonis.nus.edu.sg
          (8.9.3/8.6.9/CNS-3.5) with SMTP id VAA21825; Sun, 29 Aug 1999
          21:10:43 +0800 (SST)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-ID:  <Pine.SGI.4.02.9908292007480.8208-100000@leonis.nus.edu.sg>
Date:         Sun, 29 Aug 1999 21:10:43 +0800
Reply-To: Foo Chun Choong <engp7643@LEONIS.NUS.EDU.SG>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Foo Chun Choong <engp7643@LEONIS.NUS.EDU.SG>
Subject:      Re: [MOBILE-IP] QoS [diff-serv or int-serv/RSVP],
              and Windows MIP implementation
X-To:         Rob Goode <goode@nc3a.nato.int>
X-cc:         eit@nc3a.nato.int, Guilhem.Tardy@CRC.CA
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <199908231012.MAA27558@comsun21.nc3a.nato.int>

Hi Rob,

My apologies for the late reply.

Yes, having the sources for these technologies (MIP, QoS, IPv6, etc) on
the Windows platform would be very valuable for us researchers.

There's source code for an IPv6 stack in NT, just check out Microsoft
Research's web site (a link to this site is also available at our NUS MIP
web page). AFAIK, no free source codes available for MIP and QoS on
Windows yet.

We're hoping to release the MIP on Windows source code developed here at
NUS this coming November.
However, due to the interest of the MIP community, we may have an earlier
pre-release of the source code, maybe in about 2-3 weeks from now. This
earlier release will be an alpha release meant for developers only, and is
not meant for actual deployment (Code currently has many limitations,
hard-coded stuff, lack of install docs, which we hope to solve in future
releases of the code). An announcement will be made on this list once we're
ready for the pre-release.

Regarding mobile routers support using MIP, what are the implementations
of MIP that you have tested so far that can support this feature?

I've actually hacked our NUS MIPv4 Linux code to support mobile networks
using MIP.
We used two methods (which work independently of each other) to provide
support for mobile networks under MIP. One method used was to make the MN
NAT/IP masq-enabled. The other method that we used was to augment the MIP
protocol, the main idea is that the HA will now additionally tunnel any
packets to the FA if it's next hop gateway is the MN. Each of the methods has
its own advantages and disadvantages, for example the first method
supports private addresses, while the second method supports the recursive use
of MIP. (Am actually hoping to write an ID to elaborate further on this if
time permits).
The code will be included in version 3.1 of Linux NUS MIPv4, which we are
planning to officially release at the end of this year.

We at NUS would also greatly welcome others in the MIP community who are
interested in joining to help in the NUS MIP project. Extra help is always
welcome 8-).

Foo Chun Choong,
The NUS Mobile IP Project, http://mip.ee.nus.edu.sg
National University of Singapore

On Mon, 23 Aug 1999, Rob Goode wrote:

> Dear Foo Chun Choong,
>
> We at NC3A have a testbed looking at emerging internet technologies,
> specifically mobile IP, QoS and IPv6 and I would be interested
> in some open source for these technologies on the Windows platform
> as that is the most widely deployed platform in our organisation.
>
> I would have a high interest in MIP on windows, especially in
> source form, as my interest is in mobile routers (or mobile
> hosts with two interfaces and IP forwarding enabled) which I
> find tends not to be a standard function of most implementations,
> and hence tends to require (small) source code modifications. Our
> current interest is in MIP for IPv4, until MIPv6 becomes more
> widely implemented.
>
> Cheers,
>
> Rob Goode
> Principal Scientist
> Communications Techniques Branch,
> Communications Systems Division,
> NC3A
> PO Box 2501 CD
> The Hague
> The Netherlands
>
>
> > MIME-Version: 1.0
> > Date: Sat, 21 Aug 1999 21:51:24 +0800
> > From: Foo Chun Choong <engp7643@LEONIS.NUS.EDU.SG>
> > Subject: [MOBILE-IP] QoS [diff-serv or int-serv/RSVP], and Windows MIP
> implementation
> > X-To: Guilhem.Tardy@CRC.CA
> > X-cc: mattyc@leonis.nus.edu.sg, chuakc@cwc.nus.edu.sg
> > To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
> >
> > Hi Guilhem,
> >
> > We at NUS have done some work regarding MIPv4 and RSVP/int-serv
> > integration. Some documents regarding this can be obtained from
> > http://mip.ee.nus.edu.sg/slcchua.ps.gz , slcfoo.ps.gz , and slcloh.ps.gz
> > The source code for the prototype implementation that we've developed here
> > at NUS to support MIP/RSVP/int-serv integration can be obtained from
> > http://mip.ee.nus.edu.sg/v3.0beta
> >
> > BTW, we would also like to gauge the interest of the MIP community regarding
> an
> > implementation of MIP on Windows. We have developed a prototype implementation
> > of MN on Win95, and the agents on NT, and are contemplating an open-source
> > release of the source code for these if there's a big enough demand for it.
> >
> > Regards,
> > Foo Chun Choong,
> > NUS Mobile IP project, http://mip.ee.nus.edu.sg
> > National University of Singapore
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 30 00:11:49 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06573
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 30 Aug 1999 00:11:49 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.9721DA70@standards.nortelnetworks.com>; Mon, 30 Aug 1999 0:07:04 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 64061 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 30 Aug 1999 00:05:57
          -0400
Received: from mail0.u-aizu.ac.jp by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.09325CE0@standards.nortelnetworks.com>; 29 Aug 1999 23:55:56 -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
          MAA24260; Mon, 30 Aug 1999 12:59:28 +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 MAA00675; Mon, 30 Aug
          1999 12:59:27 +0900 (JST)
X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
References: <Pine.SGI.4.02.9908292007480.8208-100000@leonis.nus.edu.sg>
Content-Type: multipart/alternative;
              boundary="------------047943D97D9CAD90C312F042"
Message-ID:  <37CA019F.ECD36E6A@u-aizu.ac.jp>
Date:         Mon, 30 Aug 1999 12:59:27 +0900
Reply-To: sarikaya@U-AIZU.AC.JP
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Behcet Sarikaya <sarikaya@U-AIZU.AC.JP>
Organization: University of Aizu
Subject:      Re: [MOBILE-IP] Windows MIPV6 implementations
X-To:         Foo Chun Choong <engp7643@LEONIS.NUS.EDU.SG>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

--------------047943D97D9CAD90C312F042
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

Are there any public domain MIP v6, i.e. Mobile IP v6 implementations on Windows
(98/NT/2000) platform and on Solaris 7? The ones I am familiar are for FreeBSD (CMU
Monarch) and Linux (Lancaster), maybe they are not uptodate with the latest kernels.

--
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



--------------047943D97D9CAD90C312F042
Content-Type: text/html; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Are there any public domain MIP v6, i.e. Mobile IP v6 implementations on
Windows (98/NT/2000) platform and on Solaris 7? The ones I am familiar
are for FreeBSD (CMU Monarch) and Linux (Lancaster), maybe they are not
uptodate with the latest kernels.
<pre>--&nbsp;
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&nbsp;
Home page:&nbsp; <A HREF="http://www.u-aizu.ac.jp/~sarikaya/">http://www.u-aizu.ac.jp/~sarikaya/</A>
email: sarikaya@u-aizu.ac.jp</pre>
&nbsp;</html>

--------------047943D97D9CAD90C312F042--


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 30 11:11:12 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04123
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 30 Aug 1999 11:11:11 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.AEFED7E0@standards.nortelnetworks.com>; Mon, 30 Aug 1999 11:06:18 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 64923 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 30 Aug 1999 11:06:01
          -0400
Received: from omega.cisco.com by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.A4E19450@standards.nortelnetworks.com>; Mon, 30 Aug 1999 11:06:01
          -0400
Received: (from gdommety@localhost) by omega.cisco.com (8.8.8-Cisco List
          Logging/8.8.8) id IAA02653; Mon, 30 Aug 1999 08:09:16 -0700 (PDT)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-ID:  <199908301509.IAA02653@omega.cisco.com>
Date:         Mon, 30 Aug 1999 08:09:16 -0700
Reply-To: Gopal Dommety <gdommety@CISCO.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Gopal Dommety <gdommety@CISCO.COM>
Subject:      Re: [MOBILE-IP] Windows MIPV6 implementations
X-To:         sarikaya@U-AIZU.AC.JP
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <37CA019F.ECD36E6A@u-aizu.ac.jp> from "Behcet Sarikaya" at Aug
              30, 99 12:59:27 pm
Content-Transfer-Encoding: 7bit

Check the microsoft research site. I remember to have seen an IPv6
implementation.

-Gopal


>
> --------------047943D97D9CAD90C312F042
> Content-Type: text/plain; charset=iso-2022-jp
> Content-Transfer-Encoding: 7bit
>
> Are there any public domain MIP v6, i.e. Mobile IP v6 implementations on Windows
> (98/NT/2000) platform and on Solaris 7? The ones I am familiar are for FreeBSD (CMU
> Monarch) and Linux (Lancaster), maybe they are not uptodate with the latest kernels.
>
> --
> 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
>
>
>
> --------------047943D97D9CAD90C312F042
> Content-Type: text/html; charset=iso-2022-jp
> Content-Transfer-Encoding: 7bit
>
> <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
> <html>
> Are there any public domain MIP v6, i.e. Mobile IP v6 implementations on
> Windows (98/NT/2000) platform and on Solaris 7? The ones I am familiar
> are for FreeBSD (CMU Monarch) and Linux (Lancaster), maybe they are not
> uptodate with the latest kernels.
> <pre>--&nbsp;
> 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&nbsp;
> Home page:&nbsp; <A HREF="http://www.u-aizu.ac.jp/~sarikaya/">http://www.u-aizu.ac.jp/~sarikaya/</A>
> email: sarikaya@u-aizu.ac.jp</pre>
> &nbsp;</html>
>
> --------------047943D97D9CAD90C312F042--
>


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 30 12:42:25 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07415
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 30 Aug 1999 12:42:24 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.6B824F80@standards.nortelnetworks.com>; Mon, 30 Aug 1999 12:37:28 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 65074 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 30 Aug 1999 12:36:13
          -0400
Received: from crufty.research.bell-labs.com by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.3F15C850@standards.nortelnetworks.com>; Mon, 30 Aug 1999 12:36:13
          -0400
Received: from scummy.research.bell-labs.com ([135.104.2.10]) by crufty; Mon
          Aug 30 12:38:05 EDT 1999
Received: from king.research.bell-labs.com ([135.1.152.1]) by scummy; Mon Aug
          30 12:38:04 EDT 1999
Received: from notmafia.research.bell-labs.com.research.bell-labs.com (notmafia
          [135.1.152.230]) by king.research.bell-labs.com (Postfix) with SMTP
          id BE9C257036; Mon, 30 Aug 1999 11:38:00 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <19990826190549.8092757037@king.research.bell-labs.com>
            <199908280159.EAA23668@beta.hut.fi>
X-Mailer: VM 6.33 under Emacs 19.34.2
Message-ID:  <19990830163800.BE9C257036@king.research.bell-labs.com>
Date:         Mon, 30 Aug 1999 11:38:00 -0500
Reply-To: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Pete McCann <mccap@RESEARCH.BELL-LABS.COM>
Subject:      Re: [MOBILE-IP] Darwinian evolution of proxy tunnelling...
X-To:         Jari T Malinen <jtm@cc.hut.fi>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <199908280159.EAA23668@beta.hut.fi>
Content-Transfer-Encoding: 7bit

Hi, Jari,

Jari T Malinen <jtm@cc.hut.fi> (JTM) writes:

JTM> Correct me if I am wrong, bud doesn't it occur in THEMA that a lowest
JTM> SFA forwards packets based on link-layer address of the MN?

Essentially you are correct: the link-layer address is mapped to a
TunnelID.

JTM> Is this not against requirements for IPv4 routers?

It may be, but those SFAs are not really routers.  In general I think
it would be more helpful if the Mobile IP community realized that FAs
are more like NASes than like routers.

JTM> Longer explanation: My earlier term "Special requirements for the
JTM> link-layer" is perhaps inaccurate. I mean there is the requirement for
JTM> first-hop routing to be based on link-layer addresses (and isn't the
JTM> possibility to support private MN addresses with FA decapsulation on
JTM> the same link based on this?).

Yes.  For an implementation to properly support private MN addresses,
it must use link-layer demultiplexing to distinguish packets.  This
shouldn't be a new concept for any NAS that implements tunneling.

JTM> Put in implementor's terms: at least
JTM> in Linux's IPv4 "policy-based routing" that has comments on being "as
JTM> specified in RFC 1812" (Class trees in Chap. 5.2.4.3), it seems
JTM> problematic (but maybe doable) to have rule-based routing using a link
JTM> address.  Is it not the case that RFC 1812 does not require
JTM> link-address-based routing from conformant routers but rather
JTM> separates the concerns there?

Again, maybe it's improper to try to use a general purpose IP routing
engine for this piece of the architecture.  We are building access
servers, not routers.

JTM> Another question stemming from the use of link-layer in identification
JTM> of the endpoint in THEMA: FA caches the bindings by a link-layer address
JTM> identifier.  If we tech-roam between two SFAs connected to the same FA,
JTM> e.g. from DSSS WLAN to IrDA so that our link-address changes, do we not
JTM> experience the FA-HA latency in THEMA while not in the regional tunneling?

You are correct that such a movement would need to be visible to the
MN, in contrast to movements on the same link technology.  This would
be a new appearance of the MN requiring a new registration.  However,
the FA-HA latency might be avoided by using other mechanisms.

>> In contrast, the leaf FAs in the regionalized
>> tunnel approach need to implement the whole range of FA functionality
>> including dealing with authentication servers - an area that is
>> rapidly changing, to say the least.

JTM> Maybe, though the use of CAs should probably not be a requirement
JTM> but an option used when the policy of the access network needs
JTM> AAA-based security?

Some form of AAA will be needed for commercial deployment scenarios
such as cellular networks.  Service providers like to get paid for
usage of their network.

JTM> The machinery could be thought to be there for making multiple
JTM> alternatives for security and configuration (we need not change
JTM> implementation when splitting/joining components to regional
JTM> structures, a very simple reconfiguration of a similar component
JTM> is sufficient, this from the "administrator's point of
JTM> view").. When speaking of logical components, I think you are
JTM> right, the lower FA as such may have less use for some parts of
JTM> the FA functionality.

Right - I am speaking also from an equipment manufacturer's point of
view.  The leaf devices are made by someone who understands the access
technology, such as wireless links.  The FAs should be made by someone
who knows & can keep up with the emerging AAA, VPN, and Internet
roaming technologies.  It may be desirable to decouple these
components, even when no IP-layer micro-mobility is needed.

>> do you really want your first-hop IP router to have a
>> private address, when you are accessing the public Internet or a
>> private network with a completely different address space?

JTM> True, a first hop address can hide a public address, if any private
JTM> intranet address. But, if we want to conserve addresses, maybe a
JTM> private Internet-address (local?), e.g. 10.*.*.*, can be reused
JTM> several times over as the first-hop address with no danger for
JTM> ambiguity for public-network Mobile IP, while a similar range could
JTM> be defined a "private" intranet subspace (i.e. when the CN is from
JTM> an intranet).

Will a MN be able to do proper movement detection, if two consecutive
FAs have the same address?

I don't think it's wise to place a restriction on the addresses that
can be used by intranets just so we can make this scheme work, if
that's what you are suggesting.  It seems to me we should just handle
the traffic properly in the first place.

-Pete


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Mon Aug 30 20:46:58 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18567
	for <mobileip-archive@LISTS.IETF.ORG>; Mon, 30 Aug 1999 20:46:58 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.227A14A0@standards.nortelnetworks.com>; Mon, 30 Aug 1999 20:42:11 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 65588 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Mon, 30 Aug 1999 20:40:16
          -0400
Received: from inet-vrs-02.microsoft.com (131.107.3.124) by
          standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP
          id <0.DD8F1B10@standards.nortelnetworks.com>; Mon, 30 Aug 1999
          20:40:15 -0400
Received: from 157.54.9.104 by inet-vrs-02.microsoft.com (InterScan E-Mail
          VirusWall NT); Mon, 30 Aug 1999 17:19:16 -0700 (Pacific Daylight Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2448.0) id <R9R5KR30>;
          Mon, 30 Aug 1999 17:18:59 -0700
X-Mailer: Internet Mail Service (5.5.2448.0)
Message-ID:  <4D0A23B3F74DD111ACCD00805F31D810145158B5@RED-MSG-50>
Date:         Mon, 30 Aug 1999 17:19:12 -0700
Reply-To: Richard Draves <richdr@MICROSOFT.COM>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Richard Draves <richdr@MICROSOFT.COM>
Subject:      Re: [MOBILE-IP] QoS [diff-serv or int-serv/RSVP],
              and Windows MIP implementation
X-To:         Foo Chun Choong <engp7643@LEONIS.NUS.EDU.SG>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

> There's source code for an IPv6 stack in NT, just check out Microsoft
> Research's web site (a link to this site is also available at
> our NUS MIP
> web page). AFAIK, no free source codes available for MIP and QoS on
> Windows yet.

Our MSR IPv6 release includes correspondent-node support for Mobile IPv6.

Rich


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 31 02:37:17 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03953
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 31 Aug 1999 02:37:17 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.0F7AFD70@standards.nortelnetworks.com>; Tue, 31 Aug 1999 2:32:25 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 65739 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 31 Aug 1999 02:32:15
          -0400
Received: from iabgfw (194.139.245.2) by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.A3D60890@standards.nortelnetworks.com>; Tue, 31 Aug 1999 2:22:14
          -0400
Received: by iabgfw; id IAA08769; Tue, 31 Aug 1999 08:30:47 +0200 (MET DST)
Received: from iabgmh.iabg.de(10.255.255.2) by iabgfw.iabg.de via smap (V4.2)
          id xma008720; Tue, 31 Aug 99 08:30:22 +0200
Received: from iabgvw.iabg.de ([10.255.255.8]) by iabgmh.iabg.de (Post.Office
          MTA v3.5.1 release 219 ID# 127-59214U1600L300S0V35) with ESMTP id de
          for <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Tue, 31 Aug 1999
          08:30:22 +0200
Received: from iabgdns.iabg.de (localhost [127.0.0.1]) by iabgvw.iabg.de
          (8.8.8+Sun/8.8.8) with ESMTP id IAA07469 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Tue, 31 Aug 1999 08:30:21
          +0200 (MET DST)
Received: from cc31pc01 by iabgdns.iabg.de (8.8.8+Sun/SMI-SVR4) id IAA28154;
          Tue, 31 Aug 1999 08:30:21 +0200 (MET DST)
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Priority: normal
X-mailer: Pegasus Mail for Win32 (v2.54DE)
Message-ID:  <199908310630.IAA28154@iabgdns.iabg.de>
Date:         Tue, 31 Aug 1999 08:25:30 +0000
Reply-To: heissenhuber@iabg.de
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
Comments:     Authenticated sender is <heissenhuber@iabgmh.iabg.de>
From: Florian Heissenhuber <heissenhuber@iabg.de>
Organization: IABG mbH
Subject:      Re: [MOBILE-IP] Windows MIPV6 implementations
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <37CA019F.ECD36E6A@u-aizu.ac.jp>
Content-Transfer-Encoding: 7BIT

On the Microsft Research site is an IPv6 stack for Windows NT / 2000
that implemtents the Mobile IP functionality of the correspondent
node. See http://www.research.microsoft.com/msripv6

I don't know any other Mobile IPv6 implementations for Windows NT /
2000.

Regards,

Florian Heissenhuber



> Are there any public domain MIP v6, i.e. Mobile IP v6 implementations on Windows
> (98/NT/2000) platform and on Solaris 7? The ones I am familiar are for FreeBSD (CMU
> Monarch) and Linux (Lancaster), maybe they are not uptodate with the latest kernels.
>
> --
> 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
>
>
__________________________________________________________________

Florian Heissenhuber                Phone+49 89 60883539
IABG mbH                            Fax  +49 89 60882845
Einsteinstr. 20                     heissenhuber@iabg.de
85521 Ottobrunn                     http://www.iabg.de
Germany


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 31 05:14:55 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04839
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 31 Aug 1999 05:14:54 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.0629E180@standards.nortelnetworks.com>; Tue, 31 Aug 1999 5:09:38 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 65852 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 31 Aug 1999 05:08:29
          -0400
Received: from lorraine.loria.fr by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.DD211EC0@standards.nortelnetworks.com>; Tue, 31 Aug 1999 5:08:29
          -0400
Received: from loria.fr (antibes.loria.fr [152.81.12.73]) by lorraine.loria.fr
          (8.9.3/8.9.3/8.9.3/JCG-DG) with ESMTP id LAA26602 for
          <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>; Tue, 31 Aug 1999 11:12:16
          +0200 (MET DST)
X-Mailer: Mozilla 4.03 [fr] (WinNT; I)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------6E20A5F8122F9181E58CBB4C"
Message-ID:  <37CB9C6E.2A2560F8@loria.fr>
Date:         Tue, 31 Aug 1999 11:12:15 +0200
Reply-To: Isabelle Chrisment <Isabelle.Chrisment@LORIA.FR>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Isabelle Chrisment <Isabelle.Chrisment@LORIA.FR>
Subject:      [MOBILE-IP] Last Call For Participation in Mobile-IPv6
              Connectathon]
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM

Il s'agit d'un message multivolet au format MIME.
--------------6E20A5F8122F9181E58CBB4C
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit




>                     CALL FOR PARTICIPATION
>
>                     MOBILE IPv6 CONNECTATHON
>
>                     September 15-  17, 1999,
>                     LORIA, Nancy, France
>
>
> The G6 group is organizing a mobile-IPv6 connectathon in France, in
> Nancy,
> on September 15, 16 & 17 1999. Nancy is located in the east of France.
> If you have mobile-IPv6 code and would like to participate to this
> event complete the enclosed  registration form before the 4th of  SEPTEMBER 1999
> (last deadline) .
>
> Further information is available at http://www.loria.fr/~ichris/mobipv6
>
>
> REGISTRATION FORM FOR  MOBILE-IPv6 CONNECTATHON'99
>
>
> Workshop Date : Septembre 15  - September 17 1999
> The reception of participants will begin September 15, from 10.00 am to
> 10.30 am.
> The workshop will be ended  September 17, at  midday.
>
> Conference Location  INRIA-LORIA/ Nancy
>                      615 rue du Jardin Botanique
>                      BP 101
>                      54602 Villers-Lès-Nancy
>                      url : http://www.loria.fr
>
> Registration form to be completed and forwarded to re@loria.fr
>
> _______________________________________________________________________________
> Name (first, middle, last)
>
> _______________________________________________________________________________
> Affiliation (for badge)
>
> _______________________________________________________________________________
> Title/Job Function
>
> _______________________________________________________________________________
> Address
>
> _______________________________________________________________________________
> City                               Prov/State
> Zip Code
>
> _______________________________________________________________________________
> Country
>
> _______________________________________________________________________________
> Telephone
>
> _______________________________________________________________________________
> Fax
>
> _______________________________________________________________________________
> E-mail
>
> Participation in the Dinner   :
> (9/16/1999)                     Yes  __
>                                 No   __
>
> Date/Time of arrival   :
>
> Date/Time of departure :
>

--------------6E20A5F8122F9181E58CBB4C
Content-Type: message/rfc822
Content-Disposition: inline

Return-Path: <owner-ipng@sunroof.eng.sun.com>
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
        by lorraine.loria.fr (8.9.3/8.9.3/8.9.3/JCG-DG) with ESMTP id LAA25561
        for <Isabelle.Chrisment@loria.fr>; Mon, 23 Aug 1999 11:05:31 +0200 (MET DST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
        by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA04721;
        Mon, 23 Aug 1999 00:42:22 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
        by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id AAA04966;
        Mon, 23 Aug 1999 00:42:20 -0700 (PDT)
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id AAA19356
        for ipng-dist; Mon, 23 Aug 1999 00:35:40 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
        by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id AAA19349
        for <ipng@sunroof.eng.sun.com>; Mon, 23 Aug 1999 00:35:30 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
        by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id AAA23953
        for <ipng@sunroof.eng.sun.com>; Mon, 23 Aug 1999 00:35:31 -0700 (PDT)
Received: from lorraine.loria.fr (lorraine.loria.fr [152.81.1.17])
        by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA19454
        for <ipng@sunroof.eng.sun.com>; Mon, 23 Aug 1999 01:35:29 -0600 (MDT)
Received: from loria.fr (antibes.loria.fr [152.81.12.73])
        by lorraine.loria.fr (8.9.3/8.9.3/8.9.3/JCG-DG) with ESMTP id JAA20367;
        Mon, 23 Aug 1999 09:35:28 +0200 (MET DST)
Message-ID: <37C0F9C0.457E20DA@loria.fr>
Date: Mon, 23 Aug 1999 09:35:28 +0200
From: Isabelle Chrisment <Isabelle.Chrisment@loria.fr>
X-Mailer: Mozilla 4.03 [fr] (WinNT; I)
MIME-Version: 1.0
To: ipng@sunroof.eng.sun.com, MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Subject: Call For Participation in Mobile-IPv6 Connectathon
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-ipng@sunroof.eng.sun.com
Precedence: bulk
Content-Transfer-Encoding: 8bit

CALL FOR PARTICIPATION

                    MOBILE IPv6 CONNECTATHON

                    September 15-  17, 1999,
                    LORIA, Nancy, France


The G6 group is organizing a mobile-IPv6 connectathon in France, in
Nancy,
on September 15, 16 & 17 1999. Nancy is located in the east of France.
If you have mobile-IPv6 code and would like to participate to this
event complete the enclosed  registration form before END OF AUGUST.

Further information is available at http://www.loria.fr/~ichris/mobipv6


REGISTRATION FORM FOR  MOBILE-IPv6 CONNECTATHON'99


Workshop Date : Septembre 15  - September 17 1999
The reception of participants will begin September 15, from 10.00 am to
10.30 am.
The workshop will be ended  September 17, at  midday.

Conference Location  INRIA-LORIA/ Nancy
                     615 rue du Jardin Botanique
                     BP 101
                     54602 Villers-Lès-Nancy
                     url : http://www.loria.fr

Registration form to be completed and forwarded to re@loria.fr

_______________________________________________________________________________
Name (first, middle, last)

_______________________________________________________________________________
Affiliation (for badge)

_______________________________________________________________________________
Title/Job Function

_______________________________________________________________________________
Address

_______________________________________________________________________________
City                               Prov/State
Zip Code

_______________________________________________________________________________
Country

_______________________________________________________________________________
Telephone

_______________________________________________________________________________
Fax

_______________________________________________________________________________
E-mail



Participation in the Dinner   :
(9/16/1999)                     Yes  __
                                No   __



Date/Time of arrival   :

Date/Time of departure :
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to majordomo@sunroof.eng.sun.com
--------------------------------------------------------------------



--------------6E20A5F8122F9181E58CBB4C--


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 31 17:46:56 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01797
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 31 Aug 1999 17:46:56 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.21298FD0@standards.nortelnetworks.com>; Tue, 31 Aug 1999 17:42:00 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 66940 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 31 Aug 1999 17:41:22
          -0400
Received: from mail.cc.hut.fi by standards.nortelnetworks.com (LSMTP for
          Windows NT v1.1a) with SMTP id
          <0.A4346280@standards.nortelnetworks.com>; Tue, 31 Aug 1999 17:31:21
          -0400
Received: from beta.hut.fi (jtm@beta.hut.fi [130.233.224.51]) by mail.cc.hut.fi
          (8.9.3/8.9.3) with ESMTP id AAA12020; Wed, 1 Sep 1999 00:35:12 +0300
          (EET DST)
Received: (from jtm@localhost) by beta.hut.fi (8.9.1a/8.9.1) id AAA16613; Wed,
          1 Sep 1999 00:35:08 +0300 (EET DST)
X-Mailer: ELM [version 2.4 PL21]
Content-Type: text
Message-ID:  <199908312135.AAA16613@beta.hut.fi>
Date:         Wed, 1 Sep 1999 00:34:50 +0200
Reply-To: Jari T Malinen <jtm@CC.HUT.FI>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Jari T Malinen <jtm@CC.HUT.FI>
Subject:      Re: [MOBILE-IP] Darwinian evolution of proxy tunnelling...
X-To:         mccap@RESEARCH.BELL-LABS.COM
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  <19990830163800.BE9C257036@king.research.bell-labs.com> from
              "Pete McCann" at Aug 30, 99 11:38:00 am

Hi, Pete,

> JTM> Is the link-level routing not against requirements for IPv4 routers?
>
> It may be, but those SFAs are not really routers.  In general I think
> it would be more helpful if the Mobile IP community realized that FAs
> are more like NASes than like routers.
>
> .. I am speaking also from an equipment manufacturer's point of
> view.  The leaf devices are made by someone who understands the access
> technology, such as wireless links.  The FAs should be made by someone
> who knows & can keep up with the emerging AAA, VPN, and Internet
> roaming technologies.  It may be desirable to decouple these
> components, even when no IP-layer micro-mobility is needed.
>
>> [Private addresses in leaf FAs]
>
> Will a MN be able to do proper movement detection, if two consecutive
> FAs have the same address?
>
> I don't think it's wise to place a restriction on the addresses that
> can be used by intranets just so we can make this scheme work, if
> that's what you are suggesting.  It seems to me we should just handle
> the traffic properly in the first place.

The _requirement_ that all regional-aware access points would do
link-level routing would raise the bar for Mobile IP deployment on the
datacom networks.  Given that virtually all current host-routers would
either need custom routing engines or simply would not be acceptable
alternatives for custom hardware access points would make such
deployment expensive.  To become the great unificator between the
telecom and datacom worlds, means to ensure popularity in the latter
should also be considered.

Also to require strictly correct use of leaf FA addressing makes it
hard to do large picocellular environments with Mobile IPv4 due to the
need for either customization of all the leaf routing engines or too
many public addresses. I could imagine using a private/local network
among my desktop IrDA devices (without having a customized routing
engine on all those with FA) if I can guarantee no conflicting
addresses exist there.

I think the vast variety of possible setups where Mobile IP might be
of use do make the case for alternative approaches, at least for the
moment. So maybe we are making "Darwinian" comparisons of cats and
dogs when both currently have their place in the ecosystem :-)

> -Pete

Regards,

--jari

Jari Malinen (http://www.cs.hut.fi/~jtm)
Researcher, HUT/CS Lab. Tel. +358 9 451 4774, fax +358 9 451 5351.


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 31 18:34:03 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02771
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 31 Aug 1999 18:34:03 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.930721C0@standards.nortelnetworks.com>; Tue, 31 Aug 1999 18:28:08 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 67037 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 31 Aug 1999 18:26:27
          -0400
Received: from gunpowder.stanford.edu by standards.nortelnetworks.com (LSMTP
          for Windows NT v1.1a) with SMTP id
          <0.F0D15D40@standards.nortelnetworks.com>; Tue, 31 Aug 1999 18:16:27
          -0400
Received: (qmail 24348 invoked by alias); 31 Aug 1999 22:20:27 -0000
Received: (qmail 24338 invoked from network); 31 Aug 1999 22:20:26 -0000
Received: from thermite.stanford.edu (171.64.67.72) by gunpowder.stanford.edu
          with SMTP; 31 Aug 1999 22:20:26 -0000
X-Mailer: exmh version 2.0.2
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-ID:  <19990831222027.24347.qmail@gunpowder.stanford.edu>
Date:         Tue, 31 Aug 1999 15:21:50 -0700
Reply-To: Xinhua Zhao <zhao@CS.STANFORD.EDU>
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: Xinhua Zhao <zhao@CS.STANFORD.EDU>
Subject:      Re: [MOBILE-IP] QoS [diff-serv or int-serv/RSVP],
              and Windows MIP implementation
X-To:         Foo Chun Choong <engp7643@LEONIS.NUS.EDU.SG>
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
In-Reply-To:  Your message of "Sun, 29 Aug 1999 21:10:43 +0800." 
              <Pine.SGI.4.02.9908292007480.8208-100000@leonis.nus.edu.sg>

Foo Chun,

I have a few comments on the support for mobile routers using MIP.

I believe that RFC2002-compliant MIP implementations should be able
to support mobile networks without protocol changes. See below.

Foo Chun Choong wrote:
> Hi Rob,
>
> My apologies for the late reply.
>
> Yes, having the sources for these technologies (MIP, QoS, IPv6, etc) on
> the Windows platform would be very valuable for us researchers.
>
> There's source code for an IPv6 stack in NT, just check out Microsoft
> Research's web site (a link to this site is also available at our NUS MIP
> web page). AFAIK, no free source codes available for MIP and QoS on
> Windows yet.
>
> We're hoping to release the MIP on Windows source code developed here at
> NUS this coming November.
> However, due to the interest of the MIP community, we may have an earlier
> pre-release of the source code, maybe in about 2-3 weeks from now. This
> earlier release will be an alpha release meant for developers only, and is
> not meant for actual deployment (Code currently has many limitations,
> hard-coded stuff, lack of install docs, which we hope to solve in future
> releases of the code). An announcement will be made on this list once we're
> ready for the pre-release.
>
> Regarding mobile routers support using MIP, what are the implementations
> of MIP that you have tested so far that can support this feature?
>
> I've actually hacked our NUS MIPv4 Linux code to support mobile networks
> using MIP.
> We used two methods (which work independently of each other) to provide
> support for mobile networks under MIP. One method used was to make the MN
> NAT/IP masq-enabled. The other method that we used was to augment the MIP
> protocol,

I think the Mobile IP protocol itself actually doesn't need to be augmented
at all.

If we treat the whole network behind the mobile router (which is a mobile
host) just like any other static network at the mobile router's home network
and advertise its reachability through this mobile router at the mobile
router's home network, there isn't really any need for special support.
The only difference between a "mobile network" and any other normal network
is that the router to this particular network happens to be mobile. So,
instead of using regular IP to forward packets to a regular host in order
to reach a normal network, we need to use MIP to forward packets to the
mobile router first.

Therefore, it is still a question of how to reach a mobile node rather
than a whole "mobile network". Supporting "mobile network" is really an
issue of supporting mobile router. I don't see a need to expose to the
outside world the fact that the network is mobile other than the fact
that the router to it is actually mobile.

Of course, the above model still supports that the nodes within the
network behind the mobile router can be mobile. Again, no special
changes are required here. The fact that the care-of address is in a
"mobile network" just makes no difference.

My view is that current MIP implementations that are RFC 2002 compliant
should be able to support mobile routers, hence "mobile networks".
The only tricky thing is in the mobile node implementation. It should
enable a mobile node to act as a regular node (maintaining regular
routing table etc.) for certain traffic instead of simply behaving as a
host away from home which then blindly forwards all packets through an FA.
This support of duality for mobile nodes has actually been a focus of
MosquitoNet Mobile IP implementation we have been experimenting here,
though not specifically geared towards supporting mobile networks.

Best regards,

Xinhua

===========================================================
Xinhua Zhao              MosquitoNet Mobile Computing Group
Room 416, Gates Building 4A            zhao@cs.stanford.edu
Stanford University                    phone: (650)723-9427
Stanford, CA 94305                     fax:   (650)725-2588


> the main idea is that the HA will now additionally tunnel any
> packets to the FA if it's next hop gateway is the MN. Each of the methods has
> its own advantages and disadvantages, for example the first method
> supports private addresses, while the second method supports the recursive use
> of MIP. (Am actually hoping to write an ID to elaborate further on this if
> time permits).
> The code will be included in version 3.1 of Linux NUS MIPv4, which we are
> planning to officially release at the end of this year.
>
> We at NUS would also greatly welcome others in the MIP community who are
> interested in joining to help in the NUS MIP project. Extra help is always
> welcome 8-).
>
> Foo Chun Choong,
> The NUS Mobile IP Project, http://mip.ee.nus.edu.sg
> National University of Singapore
>
> On Mon, 23 Aug 1999, Rob Goode wrote:
>
> > Dear Foo Chun Choong,
> >
> > We at NC3A have a testbed looking at emerging internet technologies,
> > specifically mobile IP, QoS and IPv6 and I would be interested
> > in some open source for these technologies on the Windows platform
> > as that is the most widely deployed platform in our organisation.
> >
> > I would have a high interest in MIP on windows, especially in
> > source form, as my interest is in mobile routers (or mobile
> > hosts with two interfaces and IP forwarding enabled) which I
> > find tends not to be a standard function of most implementations,
> > and hence tends to require (small) source code modifications. Our
> > current interest is in MIP for IPv4, until MIPv6 becomes more
> > widely implemented.
> >
> > Cheers,
> >
> > Rob Goode
> > Principal Scientist
> > Communications Techniques Branch,
> > Communications Systems Division,
> > NC3A
> > PO Box 2501 CD
> > The Hague
> > The Netherlands
> >
> >
> > > MIME-Version: 1.0
> > > Date: Sat, 21 Aug 1999 21:51:24 +0800
> > > From: Foo Chun Choong <engp7643@LEONIS.NUS.EDU.SG>
> > > Subject: [MOBILE-IP] QoS [diff-serv or int-serv/RSVP], and Windows MIP
> > implementation
> > > X-To: Guilhem.Tardy@CRC.CA
> > > X-cc: mattyc@leonis.nus.edu.sg, chuakc@cwc.nus.edu.sg
> > > To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
> > >
> > > Hi Guilhem,
> > >
> > > We at NUS have done some work regarding MIPv4 and RSVP/int-serv
> > > integration. Some documents regarding this can be obtained from
> > > http://mip.ee.nus.edu.sg/slcchua.ps.gz , slcfoo.ps.gz , and slcloh.ps.gz
> > > The source code for the prototype implementation that we've developed here
> > > at NUS to support MIP/RSVP/int-serv integration can be obtained from
> > > http://mip.ee.nus.edu.sg/v3.0beta
> > >
> > > BTW, we would also like to gauge the interest of the MIP community regarding
> > an
> > > implementation of MIP on Windows. We have developed a prototype implementation
> > > of MN on Win95, and the agents on NT, and are contemplating an open-source
> > > release of the source code for these if there's a big enough demand for it.
> > >
> > > Regards,
> > > Foo Chun Choong,
> > > NUS Mobile IP project, http://mip.ee.nus.edu.sg
> > > National University of Singapore
> >


From owner-mobile-ip@STANDARDS.NORTELNETWORKS.COM  Tue Aug 31 21:37:07 1999
Received: from standards.nortelnetworks.com (standards.nortelnetworks.com [137.118.21.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05176
	for <mobileip-archive@LISTS.IETF.ORG>; Tue, 31 Aug 1999 21:37:07 -0400 (EDT)
Received: from standards (137.118.21.16) by standards.nortelnetworks.com (LSMTP for Windows NT v1.1a) with SMTP id <0.58DCB1D0@standards.nortelnetworks.com>; Tue, 31 Aug 1999 21:32:38 -0400
Received: from STANDARDS.NORTELNETWORKS.COM by STANDARDS.NORTELNETWORKS.COM
          (LISTSERV-TCP/IP release 1.8d) with spool id 67405 for
          MOBILE-IP@STANDARDS.NORTELNETWORKS.COM; Tue, 31 Aug 1999 21:30:43
          -0400
Received: from hongkong.com (202.84.12.129) by standards.nortelnetworks.com
          (LSMTP for Windows NT v1.1a) with SMTP id
          <0.AE6B13F0@standards.nortelnetworks.com>; Tue, 31 Aug 1999 21:20:42
          -0400
Received: (fmail 11594 invoked by uid 1300); 1 Sep 1999 01:24:18 -0000
Content-Transfer-Encoding: 8bit
Message-ID:  <19990901012418.11591.fmail@hongkong.com>
Date:         Wed, 1 Sep 1999 01:24:18 -0000
Reply-To: perica@hongkong.com
Sender: "IP Routing for Wireless/Mobile Hosts (mobile-ip)"
              <MOBILE-IP@STANDARDS.NORTELNETWORKS.COM>
From: perica@hongkong.com
Subject:      [MOBILE-IP] Mobile IP mailing list
To: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 8bit

Dear Sir,

I am a network engineer in Hong Kong and would like to obtain the latest news regarding mobile IP.

May I join the mailing list of mobile IP ?

Thanks !

Best regards,

Perica

___________________________________________________________________________
Get your hongkong.com freemail at http://www.hongkong.com
Free newsletters center at http://post4u.hongkong.com


